You need to delete HKLM\Software\MS\Windows\CurrentVersion\WindowsUpdate entries for SusClientID
Apparently Windows 2008 sysprep has got around this issue and resets the WSUS id for you On 8 July 2010 13:13, N Parr <npar...@mortonind.com> wrote: > One annoying thing I found is you won't see all the machines using the > same SID in WSUS. You will only see the last machine that talked to WSUS in > your computers listing. > > ------------------------------ > *From:* Anders Blomgren [mailto:chanks...@gmail.com] > *Sent:* Thursday, July 08, 2010 6:40 AM > > *To:* NT System Admin Issues > *Subject:* Re: Duplicate SID's > > Duplicate sids aren't that much of an issue, excepting the local user > security issue. Not running sysprep is an issue. It resets all sort of other > things. > > -Anders > > On Tue, Jul 6, 2010 at 8:08 PM, Kennedy, Jim <kennedy...@elyriaschools.org > > wrote: > >> Seems pretty authoritative that duplicate SID’s on machines in a domain >> are not a problem. Opinions gang? >> >> >> >> http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > > > > > > > > > -- "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
