![]() Then, I cloned that disk to 39 other computers with the exact same hardware configuration. 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). But I will say this: Obviously you can't have multiple PCs using just one OEM product key. Largely because It doesn't help that Microsoft's licensing is so freaking convoluted. You are not legally allowed to image and deploy from an OEM installation.Ģ) 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. ![]() Now, once I implemented a WSUS server, I did have SusClientID issues as Larry pointed out, a fixed based on his link.ġ) What you did is illegal, breaking the MS licensing agreement. 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. I was under the impression that joining a Windows PC to a domain took care of creating a unique SID. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |