MrSlithy
asked on
Is this sysprep really sysprep
I have an associate that does something and I just need to verify it's right regarding Windows Sysprep on Windows 7.
We have a small shop and simply use Ghost to make our images. Here's what I do: 1. I set up my image like I want it. Then I make a copy, Then when I deploy to a new box I run sysprep first thing after putting the image on the new box. Nothing fancy, just generalize and reboot.
He sypreps his image first. He runs generalize and shutdown and THEN makes his image.
Of course I see advantages and disadvantages each way. I am aware of these, but the only thing I am wondering about is this: Is his method doing the same thing as far as randomizing the new box as mine does? The assumption here is that Sysprep does most of the prep and cleaning up BEFORE shutdown and does the randomization needed to make the computer UNIQUE after the reboot. These Windows 7 boxes are going into a 2008R2 AD environment. That is a valid assumption, isn't it?
We have a small shop and simply use Ghost to make our images. Here's what I do: 1. I set up my image like I want it. Then I make a copy, Then when I deploy to a new box I run sysprep first thing after putting the image on the new box. Nothing fancy, just generalize and reboot.
He sypreps his image first. He runs generalize and shutdown and THEN makes his image.
Of course I see advantages and disadvantages each way. I am aware of these, but the only thing I am wondering about is this: Is his method doing the same thing as far as randomizing the new box as mine does? The assumption here is that Sysprep does most of the prep and cleaning up BEFORE shutdown and does the randomization needed to make the computer UNIQUE after the reboot. These Windows 7 boxes are going into a 2008R2 AD environment. That is a valid assumption, isn't it?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The PROPER way to do things is sysprep FIRST, then make a copy, then deploy. I'm 95% certain that what you are doing is leaving the machines in a technically unsupported state while what he is doing is correct.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Lee, I saw the article. its funny though, I just dont see difference:
method1 to make image:
Method A
1. Clean install, set up apps. make image.
2. Copy image to different box(es) and run sysprep before joining domain and deployment
Method B
1. Clean install, set up apps, run sysprep/shutown. make image
2. Apply this image to new machines.
Thanks
Whats the difference?
Just trying to understand.
method1 to make image:
Method A
1. Clean install, set up apps. make image.
2. Copy image to different box(es) and run sysprep before joining domain and deployment
Method B
1. Clean install, set up apps, run sysprep/shutown. make image
2. Apply this image to new machines.
Thanks
Whats the difference?
Just trying to understand.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
footech, now that I understand. We dont use any more advanced deployment methods but I could see how it would HAVE to happen this way in these deployments. And I could also see how Microsoft doesn't seem to support my method in light of these more typical ways and the problems my method could cause because the complete automation of deployment is broken by someone needing to "sun sysprep" which cancels out the ability to automate.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Lee,
So we are making an assumption that, putting it into the same model computer means the same everything. But who knows what speck may have changed under the hood? Now THAT I understand. IT might be OK if I KNEW there was absolutely no difference in the computers between the one on which the image was made and the one I am placing the image on next, but that is not a good assumption to make. I guess I can argue it doesn't make a difference ASSUMING this that and the other thing, but better to Sysprep/shutdown/make image to be sure - - -especially if that's what MS wants.
Thanks
So we are making an assumption that, putting it into the same model computer means the same everything. But who knows what speck may have changed under the hood? Now THAT I understand. IT might be OK if I KNEW there was absolutely no difference in the computers between the one on which the image was made and the one I am placing the image on next, but that is not a good assumption to make. I guess I can argue it doesn't make a difference ASSUMING this that and the other thing, but better to Sysprep/shutdown/make image to be sure - - -especially if that's what MS wants.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah, I see it now. MAC address reference was a great way to get it into my head.
OK. I have a confession to make. I haven't deployed any the way I describe. But the subject came up and no one could really define the differences too well - - -at first.
Thanks
OK. I have a confession to make. I haven't deployed any the way I describe. But the subject came up and no one could really define the differences too well - - -at first.
Thanks