Patch Management Group

 View Only
  • 1.  Deploy Windows 10 Feature 1709 Updates

    Posted Jan 30, 2018 03:55 PM

    Does anybody use Dell Data Protect Encryption for their workstations while trying to use Altiris ITMS 8.0 to push Windows 10 1709 feature updates?



  • 2.  RE: Deploy Windows 10 Feature 1709 Updates

    Posted Feb 01, 2018 08:29 AM

    Is this a general question, or is there a problem related to it?

    Thanks!



  • 3.  RE: Deploy Windows 10 Feature 1709 Updates

    Posted Feb 01, 2018 09:33 AM

    My question is targeted for any users that is pushing out Windows 10 features updates (using ITMS 8.0) while their clients are encrypted with Dell Data Protect?

     



  • 4.  RE: Deploy Windows 10 Feature 1709 Updates

    Posted Feb 01, 2018 09:57 AM

    Yes, we use DDPE (Hardware / SED encryption) and ITMS 8.1.  We have not started deployment of 1709 yet but have done deployments of the 1703 feature update.  I should note we are not using patch management for this update, we have developed a custom install script.  The primary reeason for this is to control the install timing and messaging to the user with a custom HTA wrapper.  

    We've not run into any upgrade issues related to DDPE.  If you have, please share with the community.

    Joe



  • 5.  RE: Deploy Windows 10 Feature 1709 Updates

    Posted Feb 01, 2018 11:30 AM

    We use Dell Data Protect encryption (Software / File Encryption) I have followed their documentation on how to prepare the update, however their process creates an *.wim file. (http://www.dell.com/support/article/us/en/19/sln298382/dell-encryption-for-windows-best-practices-windows-10-upgrade-migration?lang=en )

     

    Altiris doesn’t use a Wim file to deploy the images with Patch Management, so I tried to manually (Windows 10 ADK toolkit) convert the wim to an iso. (https://www.techwalla.com/articles/how-to-convert-a-wim-file-to-an-iso-file)

     

    Next I would add the ISO to the Software Update/Patch Policy, however when it’s apply/install the patch it fails. (https://support.symantec.com/en_US/article.DOC9422.html )