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.
An error occurred while saving the commentAnil 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?Anil Chohan supported this idea ·
10 votesAnil Chohan shared this idea ·