Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work for a company that is using a scanstate, loadstate type USMT migration script. Their script references 3 variables: UserID, Source, and TargetComputer.

The script .cmd works just fine (which was created by other people). But I was asked for help on tying the list of user, computer name, etc into the script for each user, which needs to run on its own.

We have a list of user ID's with their Computer Name, and New computer name, But we need to run the script easily (with the variables tying in) without having to retype those variables manually every time.

The list is in an excel document. And the cmd us essentially a psexec onto the target (original, and new) computers. The exec is running a batch file which scanstates, or loadstates.

There are two cmds, obviously one being the scan, and the other being the load.

Fairly simple if run with 1. But we are curious about doing this for thousands of users.

Please let me know..

share|improve this question

closed as not a real question by John Gardeniers, growse, Scott Pack, Ward, mdpc Nov 16 '12 at 17:16

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.