Thank you for your request. We are publishing information in a Knowledge Base article as Microsoft’s updates/patching practices evolve:
XP is dead, Windows 7 is dead in a few months, first 4 builds of Win 10 are already dead! Now Win 10 only has a 18 month lifecycle (spend 3 of those testing). Kace really needs to have better support for these annual/semi-annual build upgrades ASAP.
Over the coming releases, we will be revamping our targeting and scheduling pages. This a great example of where we will extend your ability to control what you are targeting and when it should be delivered.
It's 2019 now and this would still be a great feature to have! Being able to exclude an existing label like VIP, Virtual machines, etc would be much better than starting over with a brand new smart-label and trying to exclude stuff that way.
Kace is going to see Apple customers drop off if this is not implemented! Newer versions of MacOS block monolithic imaging and essentially require MDM style workflows.
Even if Kace just used something to leverage Apple's "Installapplication" protocol to push the Kace agent to newly boooted DEP devices would be a huge help. Someone has already done most of the work: https://github.com/erikng/installapplications Then supporting the basic DEP commands like remote wipe, lock, reboot, etc and Quest would be 80-90% of the way there!
Been doing lots of training for our new SMA. Here there is an annual certification or certificate requirement. It would be great if I could apply some of my Kace training to that by having an official certificate or full blown certification from Quest.
Thank you for your interest in this feature request. Please continue to vote this up to move it up in priority for future release consideration.
This request is under review for a future release. Please continue to vote to voice your support.
We’re looking at this after we get more K1000 synchronization built into the K2000.
4 years later and this is still an issue.
Doing a trial of SDA and just came across this issue. Would like to add my Microsoftupdatekb123456.msu file as a post install task. Will endup slipstreaming the updates into my base media using DISM but it's a hassle.
This is under consideration but not planned for the next release, Please continue voting if you’d like to see this feature prioritized for a future release.
Powershell support for SMA online scripting is targetted for a 2020 release.
The KACE Cloud MDM product added the ability to “Factory Reset” Mac (only) devices in August, 2019. We will continue to work towards this for Windows in 2020. KACE Cloud MDM is seamlessly integrated with KACE SMA.
This would be cool, but wouldn't the device still have to be checking in with SMA? Like on-site or have VPN enabled?
Guess a virtual K1000 could be in AWS or something.
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.
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.
Great idea. Can folks also provide links to other vendors’ tools?
Or we could just have other .ISO tools like this as PXE options, no need to have them in the KBE directly, although that could be nice too.
139 votesunder review · 11 comments · SDA (K2000) » Feature Enhancements · Flag idea as inappropriate… · Admin →
Wow, this is not implemented yet? Our users need their downloads folder and bookmarks to be migrated and those are not options in the current SDA USMT wizard.