3rd party Whitelisting Application Control and Windows OS Upgrades from SCCM

%3CLINGO-SUB%20id%3D%22lingo-sub-2150603%22%20slang%3D%22en-US%22%3E3rd%20party%20Whitelisting%20Application%20Control%20and%20Windows%20OS%20Upgrades%20from%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150603%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20being%20as%20ambiguous%20as%20possible%20because%20I%20do%20not%20want%20to%20identify%20the%20vendor%20or%20customer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20an%20admin%20for%20a%203rd%20party%20Application%20Control%20software%20with%20a%20client%20with%20a%20concern%3A%3C%2FP%3E%3CP%3EOS%3A%20Windows%2010%201909%2C%20upgrading%20to%2020H2%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20context%3A%20Automating%20Windows%20Upgrades.%20I%20use%203rd%20party%20software%20to%20manage%20the%20same%20software.%20Windows%20Updates%20work%20fine%2C%20as%20only%20a%20few%20execution%20control%20rules%20need%20to%20be%20created.%20Major%20OS%20Upgrades%20(1909%20to%2020H2%2C%20in%20this%20case)%20are%20largely%20blocked%2C%20which%20is%20by%20design%20since%20the%20Windows%20directory%20itself%20is%20protected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20customer%20has%20a%20strict%20governance%20on%20the%20software%20allowed%2Fwhitelisted.%20While%20my%20software%20has%20a%20specific%20mode%20that%20is%20designed%20for%20this%20type%20of%20upgrade%2C%20which%20by%20nature%20allows%20changes%20to%20be%20made%20to%20the%20system.%20Leaving%20the%20system%20in%20this%20mode%20longer%20than%20is%20required%20for%20the%20OS%20Upgrade%20is%20a%20security%20hole%20we%20need%20to%20avoid.%20We%20do%20this%20the%20Application%20to%20change%20to%20this%20mode%20in%20order%20to%20make%20the%20required%20changes%20to%20the%20OS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%2C%20SCCM%20creates%20a%20custom%20variable%20that%20my%20software%20scans%20for%2C%20and%20then%20executes%20the%20change%20on%20the%20system(s)%2C%20then%20creates%20another%20variable%20when%20the%20upgrade%20is%20complete%20to%20lock%20the%20system%20down%20again.%20I%20do%20not%20want%20to%20depend%20on%20SCCM%20for%20my%20deployments.%20I'm%20trying%20to%20remove%20an%20extra%20point%20of%20failure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20that%20leads%20to%20this%20ask%3A%20Is%20there%20any%20flag%2C%20change%2C%20or%20otherwise%20modification%20that%20occurs%2C%20with%20respect%20to%20Windows%2C%20before%20the%20upgrade%3F%20I'm%20effectively%20looking%20for%20something%20that%20I%20can%20detect%20or%20scan%20for%20reliably%20to%20automate%20changing%20modes%20from%20my%20own%20automation.%20Thank%20y'all%20for%20your%20time!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2150603%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Esccm%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eupdater%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpdates%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewhitelisting%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWSUS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Hello everyone!

 

I am being as ambiguous as possible because I do not want to identify the vendor or customer.

 

I am an admin for a 3rd party Application Control software with a client with a concern:

OS: Windows 10 1909, upgrading to 20H2

 

Some context: Automating Windows Upgrades. I use 3rd party software to manage the same software. Windows Updates work fine, as only a few execution control rules need to be created. Major OS Upgrades (1909 to 20H2, in this case) are largely blocked, which is by design since the Windows directory itself is protected.

 

The customer has a strict governance on the software allowed/whitelisted. While my software has a specific mode that is designed for this type of upgrade, which by nature allows changes to be made to the system. Leaving the system in this mode longer than is required for the OS Upgrade is a security hole we need to avoid. We do this the Application to change to this mode in order to make the required changes to the OS.

 

Currently, SCCM creates a custom variable that my software scans for, and then executes the change on the system(s), then creates another variable when the upgrade is complete to lock the system down again. I do not want to depend on SCCM for my deployments. I'm trying to remove an extra point of failure.

 

All that leads to this ask: Is there any flag, change, or otherwise modification that occurs, with respect to Windows, before the upgrade? I'm effectively looking for something that I can detect or scan for reliably to automate changing modes from my own automation. Thank y'all for your time!

0 Replies
www.000webhost.com