Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Deploying a personality fails with odd error

Updated: 21 May 2010 | 1 comment
Adam Collett's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I am using Deployment Solution to do the following as part of one single job



Gather personality of target Windows XP system to a file on the Deployment Server

Reboot to automation and run scripted install of Windows Vista Enterprise

Copy over the NETDOM command to C:\Windows\System32

Run a script to add the machine to the Active Directory domain in the correct OU

Deploy the saved personality back to the machine now it is running Vista.



The final part of the task has failed with the error

"The process cannot access the file because it is being used by another process."

The status code is 32



Am I trying to do something outside of the remit of Deployment Solution or is there a common reason this might be happening?



Running Deployment Solution 6.9SP1, Server 2003, SQL 2005



Thanks



Adam

Comments

Adam Collett's picture
13
Nov
2008
0 Votes 0
Login to vote

Found that the personality package needs certain switches adding to the task under "Additional command-line switches"



In the name you should have something like .\Saved Personalities\%COMPNAME%.exe



The ones to use are -qm -p:Password -nr



This runs the personality file with -qm for quiet, minimized -p:Password if you have a password set on the personality file and -nr for no reboot after the personality has been installed.



Now the deploy personality task runs correctly