Better USMT Management (Scheduling, External Storage Ability, etc.)
We’d like to improve schedulling and automated tasks across the board on the K2000.
I’m not as enthusiastic about supporting user state migration to non-K2000 storage. The advantage of the K2000 is that everything’s centralized. We already have export of user state in 3.3. If the problem is not having enough native storage on the K2000, we’ve heard that loud and clear.
8 years later and I still agree that USMT on SDA/K2000 needs some love!
More/or custom USMT XML options, more storage/network storage, scheduling would all be great.
Hope you don’t mind but I would like to add the following to this request?
Due to network security we disable SMB V1. The k2000 uses SMB v1 for USMT (Most organizations have SMB v1 blocked now and Microsoft even recommends it is no longer used)
Can Quest Switch the USMT process to use SMB v2 or v3?
This is my only concern with the k2000, unfortunately it is a big concern with us and is making us consider SCCM for the upcoming year.
Anil Chohan commented
The main problem with the k2000 is USMT scanstates cannot be captured to replication sites. So for companies with multiple sites this feature is almost useless.
Plus the fact that you cannot upload custom config.xml files to capture extra information. unless this has changed in k2000 v3.6?
I would like to see more granular control over options in the USMT scan template details.
Sam LaRoche commented
Add abilty USMT config files and/or full USMT support. For example, to migrate files from/to a specific location
Nolan Fleenor commented
I would like to see the ability to use USMT to back up to an RSA and recover from an RSA, without involving the K2000. We have several remote offices, that we cannot backup to the K2000 and synch down to the RSA, due their limited bandwidth issues.
Patrick Schild commented
The storage space is a major concern for me. Is there any update on that?
The ability to schedule user profile captures, and the ability to increase storage. The size of the 2000 is too small to manage a large number of profiles.