/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hello,

We recently started deploying Windows 10 into our environment and have run into a few issues regarding cumulative and feature updates causing issues. What are your best practices on how to prepare and handle these updates. We currently are having to redo the settings since the update resets everything, is there better methods to reapply these? I know there are ways to handle this through Software within the K1000.

What are you guys and gals doing to make these updates seamless and to reduce downtime for end users.

Thanks,
1 Comment   [ + ] Show comment

Comments

  • http://www.itninja.com/blog/view/upgrading-from-windows-7-8-to-windows-10-via-k1000-script

    check this.

    basicaly create a managed install / script and add it to userportal. let users trigger it from user portal when the want it. like they leave office for the day or something like this.

    See setup.exe command line here:
    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options

    maybe check how you do or not do your updates. maybe do some configurations / config files instead just running plain setup


Answers

0
Hi,
I can't speak for KASE, but generally your best bet would be to use the LTSB / LTSC version of Windows 10. There is no downtime unless your patching causes problems... of course you don't get all the newest "Bells and Whistles"... but you don't get any problems like those caused by in-place updating / feature updating.
There is no guarantee that an in-place upgrade will work, even with testing you will have clients that "Die" occasionally.
As for the settings your "Upgrade / Deployment" job / task (or whatever it's called in KACE) should be doing any customisation after the upgrade / update for anything that is not covered during the migration of the user settings (i.e. system wide settings), in other words your custom functions within a job / task. Obviouslky you find these out during the "extensive" testing before deciding on the feature update...
Even using SCCM (MS Product) there are more or less always problems with user specific settings / configuration.

(Don't kill the messenger!)

Cheers
Phil
Answered 04/05/2018 by: Pressanykey
Red Belt

Share