is there instructions anywhere how to do this in the new releases?

If you are interested in participating in the Beta testing for this and other features associated with KACE SMA 10.2, please contact: KACE_BETA@quest.com and tell them that this is the feature in which you are most interested.
Note that you may need to allow the Beta Team to tether.
Thank you in advance for your kind consideration!

Any news on this important feature?

This is at the top of the priority list for patch/update feature requests for a future release.

We have many windows 10 machines in our environment that the K1000 will not patch because of microsoft's rapid release cycle. As of now the latest feature update updates to 1903 which is not supported by Kace 9.0 or 9.1. Kace needs to get its stuff together and get with it else they will lose customers. Microsoft's change to windows 10 versions necessitates that Kace also updates its software to keep up.

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.

Looks like support for office 365 patching has been added as of August 2018

The fact that I have to vote to have this feature added is troublesome. We need to be able to deploy Windows 10 versions via KACE.

With Windows 10 becoming the new standard OS for Enterprise computing, will the new update to the KACE K1000 include Feature updates for Windows 10 as part of patching? This helps to ensure overall security for Windows 10 client PCs.

We have been on Kace 1000 for the goal of easing the patching version. This needs to happen.

Now ... the patching burden is now a problem. If I need (1) a special script and share to deploy expected updates or (2) another patch product to fill in where Kace falls short, then we will do away with Kace altogether.

Even with using something like SCCM, you still have to have the ISO extract to deploy out the feature update:
https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-configuration-manager

"...On the Data Source page, type the path of the extracted .iso file of the new version of Windows 10 you’re deploying, and then click Next.

In this example, the Windows 10 Enterprise 1607 installation media is deployed to \contoso-cm01\Sources\Operating Systems\Windows 10 Enterprise\Windows 10 Enterprise - Version 1607...."

I was able to deploy feature updates using only the K1 in just 5 steps and it worked flawlessly on over 200 devices (some over very low bandwidth WAN connections). I like the idea of keeping the model of Updates vs Upgrades the way it is. It makes upgrade damage control a little easier.
I have documented here and hope this helps somebody. http://www.itninja.com/blog/view/applying-windows-10-feature-updates-with-kace

This really needs to be a priority with the frequency in which Microsoft is releasing these feature updates.
We moved away from WSUS/SCCM, to KACE, so I really don't want to stand up a WSUS server again to manage these. If I stood up WSUS again, I'd just do away with KACE.

I really hope this happens sooner than later. We purchased a 5 year subscription of KACE1000 based on the fact that it could completely replace WSUS (which is free i might add). I'm feeling ripped off right now. If I have to go back to WSUS to install Windows 10 Feature updates, I will be looking for a refund from Quest. I'm not a happy.

Really hope we can get this going soon, Quest... Microsoft has just released 1709, before we finished upgrading systems to 1703. Without the support of this through the SMA, via updates, it's going to take a lot more effort. If this can be downloaded via Windows update, I'm not sure why it can't be included in the SMA update catalog.

This is critical- the last thing I want to do is to support updates using WSUS and Kbox!! I'm sure a lot of people feel the same way!

We had to redeploy a WSUS server just for Feature Updates. Quest needs to figure this out asap.

Is this really not supported? Not good since we just purchased KACE

This would be a critical feature. With a 3-4 year life span for hardware, there needs to be a way to upgrade builds of Windows 10 without a full re-image each time MS deploys a new build

Agreed. With Microsoft only supporting each build of Windows 10 for 2~ years, this feature will be required. Either Kace needs to provide a solution or we'll have to consider a third party product. Thank you for considering this request.