Why does DS mess with PC, even though it's straight capture?
Updated: 22 May 2010 | 2 comments
I noticed that even with a straight capture (no sysprep, scripts, etc. ran), DS seems to do something to the PC. Cause in the middle of its process, I've happened to log onto the PC, and see a Altiris pop-up come up saying that it's restoring the original computer. Huh? So it's messing with it to begin with. Why? Versus like other imaging apps it just straight captures.
Discussion Filed Under:
Comments
It is disabling networking. If you capture an image with everything as it was, then if you deploy that image to a different system, or multiple systems, then when they boot, they will all come up on the network as the same computer, which will cause network problems if multiple systems report to be the same computer.
So networking is disabled before the image is captured, so that when the image is deployed, those systems will not be active on the network until they are configured properly.
This means that the original system needs to be reconfigured after the image is captured, back to the original settings.
I think there are options in the image capture task to disable this, but I'm not sure.
In the Capture Image job you need to check the box next to "Do not boot to production" under Advanced. That way you can shut the computer down, start the Image job then boot the computer straight into automation to pull the image.
Would you like to reply?
Login or Register to post your comment.