I am trying to generalize a Windows 7 configuration into an image for deployment on multiple workstations. NewSID no longer works and Ghost Walker also doesn't work. Running Sysprep just kicks the system into an infinite reboot.
The alternative option that was listed through the CloneZilla.org site (DRBL) still uses NewSID, which pretty much doesn't work (because I've tried it).
Is there an alternative besides Sysprep for changing SIDs on Windows 7 machines? Is there something else I need to do before I run Sysprep? Or am I just out of luck on this and have to manually configure all 100+ machines after I load the image via network and DART?
Any suggestions would be most appreciated. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WRT NewSID by Mark Russinovitch (SysInternals, now Microsoft), I'd encourage anyone interested in that SID thing to carefully read Mark's blog entry here: http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx
where he clearly explains why NewSID was never a good idea: that's because duplicated SIDs are not a problem by themselves. But, please read.
HTH,
Jean-Francois Nifenecker, Bordeaux
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am quite aware of Russinovitch's blog entry regarding NewSID and why it wasn't a good idea and whatnot. That isn't the problem.
The problem here is that having duplicate SIDs on our Active Directory either makes the AD explode or we occasionally have specific machines that have duplicate SIDs randomly drop out of the network. Making the AD explode isn't such a big deal for our group, having lab machines randomly drop out of the network simply because they have duplicate SIDs is unacceptable.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We try newsid tool in Windows 7 32bit and it works fine. Two notices: Either to disable UAC first or run newsid with administrator privilege can make newsid to work well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I am trying to generalize a Windows 7 configuration into an image for deployment on multiple workstations. NewSID no longer works and Ghost Walker also doesn't work. Running Sysprep just kicks the system into an infinite reboot.
The alternative option that was listed through the CloneZilla.org site (DRBL) still uses NewSID, which pretty much doesn't work (because I've tried it).
Is there an alternative besides Sysprep for changing SIDs on Windows 7 machines? Is there something else I need to do before I run Sysprep? Or am I just out of luck on this and have to manually configure all 100+ machines after I load the image via network and DART?
Any suggestions would be most appreciated. Thanks.
Hi,
WRT NewSID by Mark Russinovitch (SysInternals, now Microsoft), I'd encourage anyone interested in that SID thing to carefully read Mark's blog entry here:
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx
where he clearly explains why NewSID was never a good idea: that's because duplicated SIDs are not a problem by themselves. But, please read.
HTH,
Jean-Francois Nifenecker, Bordeaux
Hi Jean-Francois,
I am quite aware of Russinovitch's blog entry regarding NewSID and why it wasn't a good idea and whatnot. That isn't the problem.
The problem here is that having duplicate SIDs on our Active Directory either makes the AD explode or we occasionally have specific machines that have duplicate SIDs randomly drop out of the network. Making the AD explode isn't such a big deal for our group, having lab machines randomly drop out of the network simply because they have duplicate SIDs is unacceptable.
We try newsid tool in Windows 7 32bit and it works fine. Two notices: Either to disable UAC first or run newsid with administrator privilege can make newsid to work well.
Hi ceasar-sun,
Yeah, we turned off UAC and ran NewSID with admin privilege. We're still not sure why it threw the computers into an infinite reboot. =/