bcetin

Hi, This may be very basic information but I cannot find the answer (and this is the windows "noob" forum heh ). When I run the scanstate tool from SCCM task sequence, it creates a USMT.MIG file in the StorePath. I will run this on many computers and StorePath is the same network location for all. So, how can I make this filename unique? Maybe something like USMT_<computername>.MIG or USMT_<MACaddress>.MIG (in case of a computer rename) but I cannot find the option to give a name to this file. And I will eventually use this filename for restore. Any advice? Maybe add a TS step for renaming it after scanstate finishes? Thanks.

Hi Peter, I had a look at the script and removed the hardlink options, modified it for saving files to a network location. Also added a network drive mapping at the start of the Task Sequence. I have also changed the OSDStateStorePath variable in TS to a shared folder. I will be trying to make this work. SMP can be used but we have many branches and do not want to deploy an SCCM server for just one role to very small locations consisting of 4-5 clients. I could replace the PXE role with some scripts and if I can also skip SMP role with USMT, there will be no need for an SCCM server in small locations. But if I fail these, of course I will need to go back to SMP and a site server to each location.

Hi, it's a great guide and gave me a headstart as our company will be migrating from XP to W7. I have a question about the offline mode; is it possible to use this method but saving the user data to a network folder instead of saving locally? Also after W7 migration, I would like to use this method in replacement scenarios (W7 to W7 but different hardware), so I will need to backup to a network location. If offline mode cannot do this, what is the method you would prefer, does USMT 4.0 support this in any other way? I do not want to use SMP. Thanks.