2 results found
70 votesunder review · John Karabaic responded
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 comment
443 votesunder review · Ken Galvin responded
This feature request is under review. We encourage others to vote for it to be considered in a future release.Anonymous supported this idea ·
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.