Pre-boot turn off in windows feature patch push

[Cody Dirrigle]

We are using Altiris 8.5 and SEE 11.3 and feature upgrades work great without having to run the special scripts to allow them to run if the device is encrypted. Yet you still need to send a command to enable the auto login feature which is a manul job we will have to push. Has anyone built this command into their patch managment when the feature upgrade tries to apply? It would be great if in the patch push you could have a detaction check for SEE 11.3, if its there run the command to allow 3 reboots for the feature windows upgrade. Not sure if something like that would even be possible? 

https://support.symantec.com/us/en/article.doc9422...

[Johannes Bedrech]

HI Cody,

Take a look at the following TECH Article: https://support.symantec.com/us/en/article.TECH252359.html

For more information about Windows 10 upgrade with these products (e.g., enabling the automatic logon feature during the upgrade process), see the following knowledge base articles:
How to upgrade computers encrypted with Symantec Encryption Desktop to a Windows 10 release
How to upgrade computers encrypted with Symantec Endpoint Encryption to a Windows 10 release

Hope this helps!

Network23

[Cody Dirrigle]

That is what I'm doing and it works, the snag being if you have pre-boot login turned on the update installs fine for the first part but feature releases need two to three reboots to complete, so the update applies but then stops due waiting for the login at the pre-boot screen

The work around for that is sending a disable pre-boot for 3 restarts but you have know every device that has SEE and if when they are going to get the feature update, be nice to have it apply through patching and do the check to see if it needs to disable pre-boot