+1 On Wed, 30 Dec 2009 10:38:33 -0600, Sam Cayze wrote:
>I've been imaging systems for over 10 years now; never used/needed >NewSID... >Sam > >________________________________ >From: [email protected] [mailto:[email protected]] >Sent: Wednesday, December 30, 2009 10:07 AM >To: NT System Admin Issues >Subject: NewSID not needed....Wow >http://blogs.technet.com/markrussinovich/archive/2009/1 1/03/3291024.aspx >The New Best Practice >It's a little surprising that the SID duplication issue has gone >unquestioned for so long, but everyone has assumed that someone else >knew exactly why it was a problem. To my chagrin, NewSID has never >really done anything useful and there's no reason to miss it now that >it's retired. Note that Sysprep resets other machine- specific state >that, if duplicated, can cause problems for certain applications like >Windows Server Update Services (WSUS), so Microsoft's support policy >will still require cloned systems to be made unique with Sysprep > > >This is a little surprising, but good to know and it is written by the >guy who wrote the NewSID code...(Mark Russinovich) > >Read the whole article if your curious. > >,Josh > > >~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >~ <http://www.sunbeltsoftware.com/Business/VIPRE- Enterprise/> ~ Regards, Charles --- Charles Figueiredo PhD Integrated Solutions - Enhancing Small Business Systems --- ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
