Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Deployment Anywhere change unattend.xml file

Created: 20 Feb 2013 • Updated: 21 Feb 2013 | 2 comments

hi,

I have a problem with the task to deploy anywhere.

I installed the DS 7.1 sp1 mr1 and I captured an windows 7 professional sp1 ghost image, with the following jobs:
- Reboot to automation
- Prepare for Image Capture
- Reboot to production

Then, I tried to make a distribution test of the captured image using the following job:

- Reboot to automation
- Deploy image (selected deploy anywhere, custom unattend.xml)
in particular in the unattend.xml file, I modified the field @ compname with token  %serialnum%

after the deployment phase is finished, I checked the file:

X: \ unattend.xml
D: \ windows \ panther \ unattend.xml
D: \ windows \ system32 \ sysprep \ unattend.xml

and that the name of the computer is properly set with the serial number.

When the  deploy anywhere phase ends,in the unattend.xml files of  D: partition, the computer name turns out to be the same as the computer name of the master image. When the computer will reboot to production, the name of the PC remains the master image and also the guid does not change.

I tried to make a new image capture and redistribute by selecting Generate Sysprep configuration file using inventory data, but the problem persists.

I also tried to delete the inventory "master" computer, eliminating any backup information, but the problem persists.

does anyone have any idea

thanks

Operating Systems:

Comments 2 CommentsJump to latest comment

SJ_Davide's picture

i have resolved the problem.

specifically, the job was incorrect because task "reboot to automation" not needed.

i used an incorrect symantec guide but I solved by contacting support.

Thomas Baird's picture

SJ - please point out the guide you followed.  I'm pretty sure I reviewed one like it yesterday, and I need to bring to the attention of our doc team the reality of this situation.  You're the 3rd person I've heard from in as many weeks with the exact same problem.  IMO, this needs to be resolved ASAP.

Thanks!!  Please post here to warn others, AND send me an email.  Please.

Thomas Baird
Enthusiast for making things better!