Jun 22, 2017 Lists well-known security identifiers in Windows operating systems. Note Added in Windows Vista and Windows Server 2008; SID: S-1-4 Name: Non-unique. I have imaged a Vista laptop using UltraBac Gold and I need to change the SID. I am going to try using sysprep but I do not want to make any other changes.
Macgyverated wrote: I was under the impression that joining a Windows PC to a domain took care of creating a unique SID. When we started up our company, I cloned roughly 40 PCs with the same non-sysprep OEM image, changed the Product key to one of the other 39 OEM disks I had purchased, and then joined them to the domain. Here I am 4 years later with no issues. Now, once I implemented a WSUS server, I did have SusClientID issues as Larry pointed out, a fixed based on his link.
Two things: 1) What you did is illegal, breaking the MS licensing agreement. You are not legally allowed to image and deploy from an OEM installation. 2) When did you create the image? Was it before the initial power on, before being asked for the user name and all that? Because if so, yes, that was after a sysprep, because that's how they come from the factory - syspreped and ready for you to power on and use. Wrote: macgyverated wrote: I was under the impression that joining a Windows PC to a domain took care of creating a unique SID. When we started up our company, I cloned roughly 40 PCs with the same non-sysprep OEM image, changed the Product key to one of the other 39 OEM disks I had purchased, and then joined them to the domain.
Here I am 4 years later with no issues. Now, once I implemented a WSUS server, I did have SusClientID issues as Larry pointed out, a fixed based on his link. Two things: 1) What you did is illegal, breaking the MS licensing agreement.
You are not legally allowed to image and deploy from an OEM installation. 2) When did you create the image? Was it before the initial power on, before being asked for the user name and all that? Because if so, yes, that was after a sysprep, because that's how they come from the factory - syspreped and ready for you to power on and use. I can't speak to the legality of it.
Largely because It doesn't help that Microsoft's licensing is so freaking convoluted. But I will say this: Obviously you can't have multiple PCs using just one OEM product key. So I hand-assembled 40 white boxes. I loaded OEM onto one, set up an initial local account, and got Windows configured the way I wanted it (including installation and configuration of Open Office). Then, I cloned that disk to 39 other computers with the exact same hardware configuration. Pokemon Heart Gold Rom Usa Patched on this page. I had purchased 40 OEM disks at full retail price of $139 each.
After powering up each cloned PC, Windows did, in fact, allow me to go in and change the product key on each PC to one of the 39 remaining product keys on the disks I bought, and then I changed the name on each PC and joined it to the domain. So at the end of the day, the net outcome would be considered legit. The only difference is that I didn't spend 4+ hours installing and configuring each PC seperately. Microsoft still got all the money they had coming to them ($5560), and each PC is operating with a legit and unique product key.
I wasn't trying to screw MS or anyone else out of anything. If MS has a problem with that, then I would suggest they do something to vastly simplify and clarify the absolutely ridiculous licensing scenarios and lingo they have in place. Since I am the 'system builder' and hand assembled all the PCs from component parts (as apposed to loading the disk image up onto pre-built Dells for example), I am abiding by the requirement to provide end-user support for the systems I built, and I spent $139 on each PC for a legit OEM license, I can't see where they should have an issue with what I did. Macgyverated wrote: LarryG. Wrote: macgyverated wrote: I was under the impression that joining a Windows PC to a domain took care of creating a unique SID.