EdgeUpdateSetup (Edge services) via SCCM

%3CLINGO-SUB%20id%3D%22lingo-sub-1798165%22%20slang%3D%22en-US%22%3EEdgeUpdateSetup%20(Edge%20services)%20via%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1798165%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20a%20'special'%20way%20of%20updating%20Edge.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20do%20not%20allow%20to%20obtain%20Edge%20Updates%20straigth%20from%20the%20Web%2C%20via%20the%20clients%20update%20options.%3C%2FP%3E%3CP%3EFor%20the%20same%20reason%20we%20cannot%20use%20the%20new%20EDGE%20features%20of%20SCCM.%20(It%20bypasses%20the%20upstream%20WSUS%20server%20in%20the%20DMZ%2C%20and%20wants%20to%20go%20straight%20to%20the%20web%20too)%3C%2FP%3E%3CP%3EInstead%2C%20we%20use%20a%20Software%20Update%20Group%2C%20in%20SCCM%2C%26nbsp%3B%20to%20deploy%20the%20(stable)%20update%20to%20Edge.%20I%20manually%20check%20%22All%20Software%20Updates%22%20to%20link%20the%20new%20update%20to%20the%20Software%20Update%20Group%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20works%20OK%20for%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20I%20recently%20noticed%20that%20there%20is%20a%20challenge%20with%20the%20update%20of%20the%20Edge%20Update%20services.%3C%2FP%3E%3CP%3EApparently%20the%20EdgeUpdate%20can%20also%20contain%20updates%20to%20the%20EdgeUpdate%20services.%3C%2FP%3E%3CP%3EI%20can%20see%20attempts%20to%20install%20this%2C%20currently%20MicrosoftEdgeUpdateSetup_x86_1.3.135.49.exe%2C%20but%20these%20are%20'blocked'%20by%20our%20AV%20tools%2C%20as%20these%20utilize%20APPDATA.%3C%2FP%3E%3CP%3ETherefore%20we're%20still%20at%201.3.135.29%20for%20the%20EdgeUpdate%20services.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20create%20another%20SCCM%20thing%20to%20apply%20the%201.3.135.49.exe%2C%20but%20my%20question%20are%3A%3C%2FP%3E%3CP%3E-%20is%20the%20MicrosoftEdgeUpdateSetup_x86_1.3.135.49.exe%20included%20in%20the%20(stable)%20Edge%20Update%3F%3C%2FP%3E%3CP%3E-%20who%20is%20in%20control%20of%20installing%20this%2C%20Edge%2C%20the%20Edge%20Update%20or%3F%3F%3C%2FP%3E%3CP%3E-%20how%20can%20I%20handle%20this%20in%20a%20more%20proper%20way%3F%3F%3F%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

We've a 'special' way of updating Edge. 

We do not allow to obtain Edge Updates straigth from the Web, via the clients update options.

For the same reason we cannot use the new EDGE features of SCCM. (It bypasses the upstream WSUS server in the DMZ, and wants to go straight to the web too)

Instead, we use a Software Update Group, in SCCM,  to deploy the (stable) update to Edge. I manually check "All Software Updates" to link the new update to the Software Update Group etc.

 

This works OK for us.

 

However, I recently noticed that there is a challenge with the update of the Edge Update services.

Apparently the EdgeUpdate can also contain updates to the EdgeUpdate services.

I can see attempts to install this, currently MicrosoftEdgeUpdateSetup_x86_1.3.135.49.exe, but these are 'blocked' by our AV tools, as these utilize APPDATA.

Therefore we're still at 1.3.135.29 for the EdgeUpdate services.

 

I will create another SCCM package to apply the 1.3.135.49.exe, but my question are:

- is the MicrosoftEdgeUpdateSetup_x86_1.3.135.49.exe included in the (stable) Edge Update?

- who is in control of installing this, Edge, the Edge Update or??

- how can I handle this in a more proper way?????

0 Replies