|
Posted by Eric Eickhoff on August 12, 2005, 4:12 pm
Please log in for more thread options
Peter,
See if this helps:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/html/45297f03-7ff2-41c6-99cc-66ca1cc88569.asp
-Eric
>I searched around a bit for this, but didn't see any specific
> mention. I have a Win2k3 installation -- a single server, in
> production, so it can't be down for a reinstall. SP1 apparently killed
> COM -- all sorts of components failed to start, but the only trace I
> have is an unknown informational message from the COM system (my
> security log rolled when I backed out the service pack).
> At a guess, the new security behavior doesn't like my settings, but I
> can't trace it to file system, registry, or local security policy. Gee,
> MS wouldn't happen to have an add-only security template for SP1,
> that'll add the minimum necessary security elements to start the OS?
> It's tough to troubleshoot once the service pack is applied, because
> half of the services, MMC snap-ins, and properties dialogs fail to
> open. It's a bloody delicate house of cards, but at least it's a...
> fairly robust house of cards.
> I wouldn't expect file system or registry security, as I didn't make
> significant changes to those (if any) -- but I did have a lot of fun
> with the local security policy.
> I also dug around on Microsoft's site, but didn't locate specific
> information on the security changes -- just general info. I'd
> appreciate any pointers or suggestions.
>
> Peter E. Fry
| 
XML Sitemap