/build/static/layout/Breadcrumb_cap_w.png

More about USMT, please

During our KBOX 2000 JumpStart, we uploaded USMT 4.0 (the User State Migration Tools for Windows 7/Vista) to our KBOX and it's ready to go. I know a lot about how USMT (4.0 and 3.01) works in the cold, cruel world, but not much about how it operates in the KBOX environment (KBOX 2000 or even used from a script in a KBOX 1000). And I didn't find much of this technical information in the manual or anywhere on kace.com.

Can we find out more about how the KBOX uses USMT? For examples:
- where does it store the userprofiles? how are they identified?
- are the userprofiles stored compressed or not? single instance storage or not?
- are the userprofiles stored encrypted?
- where are the USMT program files stored? (e.g., MigUser.xml)
- what are the actual command lines that run USMT's ScanState.exe and LoadState.exe, and where are the command (batch) files stored? (In other words, which XXXXState.exe parameters are used?)
- what about USMT logs: what logs are captured, at what level of verbosity (/v:), and where are they stored?

I'll offer a trade here: If someone from KACE will supply these technical details (and more!), I'd be happy to share my knowledge about USMT here as well. Sande

0 Comments   [ + ] Show comments

Answers (1)

Posted by: work@deploy 11 years ago
Senior White Belt
0

I also have the same questions.. Did u find some answers?

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ