SOLVED

Automatic Updates in BETA-Channel

%3CLINGO-SUB%20id%3D%22lingo-sub-828546%22%20slang%3D%22en-US%22%3EAutomatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-828546%22%20slang%3D%22en-US%22%3E%3CP%3Edoes%20the%20BETA-Channel%20Version%20of%20Edge%20auto-updates%20too%3F%20(similar%20to%20the%20dev%20channel%3F)%3C%2FP%3E%3CP%3Ebecause%20we%20would%20like%20to%20test%20a%20sccm-deploying%20with%20the%20MSI-package%20of%20the%20BETA.%20and%20if%20edge%20is%20auto-updating%2C%20every%20time%20SCCM%20would%20perform%20a%20downgrade%20-%26gt%3B%20not%20very%20cool....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-832054%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-832054%22%20slang%3D%22en-US%22%3E%3CP%3EThey%20send%20auto%20updates%20through%20for%20Beta%20too.%20In%20other%20words%20you%20don't%20have%20to%20manually%20re-download%20the%20browser%20or%20download%20the%20update%20builds%20every%20time%20there's%20an%20update.%20Beta%20is%20only%20updated%20about%20every%20six%20weeks%20or%20so%20(with%20smaller%20security%20or%20minor%20type%20updates%20like%20everyone's%20browser%20is%20breaking%20and%20crashing%20so%20a%20revision%20update%20is%20went%20through%20a%20few%20days%20after%20the%20original%20update).%20Windows%20Task%20Scheduler%20has%20a%20Microsoft%20schedule%20set%20in%20too%20auto%20update%20MS%20programs.%20There's%20also%20an%20update%20folder%20for%20Edg%3CSPAN%3Ee%20in%20your%20Windows%20Directory.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F129477i617CC5E741AF6F05%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.png%22%20title%3D%22Capture.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F129479iAC991327F0BC36D4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222.JPG%22%20title%3D%222.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834127%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834127%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F398861%22%20target%3D%22_blank%22%3E%40_Sandro_%3C%2FA%3E%26nbsp%3Byou%20like%20to%20configure%20the%20Update%20Policy%20to%20disable%20Updates%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-update-policies%23updatedefault%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-update-policies%23updatedefault%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834316%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834316%22%20slang%3D%22en-US%22%3E%3CP%3Emille%20grazie%20%3B)i%20hope%2C%20they%20will%20provide%20a%20function%20in%20the%20GPO%20for%20the%20future.%20we%20would%20like%20to%20control%20the%20update%20deployment%20like%20other%20updates%20during%20our%20SCCM%20environment.%20i%20don't%20like%20beta-testing%20in%20the%20user%20environment%20%3B)%3C%2Fimg%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373791%22%20target%3D%22_blank%22%3E%40ItalianAce%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834319%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834319%22%20slang%3D%22en-US%22%3E%3CP%3Ehmmm%20i'm%20not%20sure%2C%20but%20you%20refer%20to%20the%20standard%20GPO%20of%20the%20%22normal%22%20Edge%20Browser%20and%20not%20the%20Chromium%20Engine.%20I%20don't%20think%20this%20will%20work%20with%20the%20BETA%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60488%22%20target%3D%22_blank%22%3E%40Gunnar%20Haslinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-834338%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-834338%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F398861%22%20target%3D%22_blank%22%3E%40_Sandro_%3C%2FA%3E%26nbsp%3Bno%2C%20I%20don't%20refer%20to%20the%20GPO%20for%20the%20old%2Fnormal%20Edge%20Browser%2C%20see%20at%20the%20top%20of%20the%20Page%2C%20it%20clearly%20says%20%22%3CSPAN%3EThis%20article%20applies%20to%20Microsoft%20Edge%20version%2077%20or%20later.%22%20%3D%26gt%3B%20This%20is%20definitely%20Edge%20beta%20based%20on%20Chromium%20and%20not%20the%20%22regular%20EdgeHTML%22%20Version.%20In%20regular%20EdgeHTML%20there%20was%20no%20UpdateManager%20and%20no%20policy%20for%20the%20UpdateManager.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-839167%22%20slang%3D%22en-US%22%3ERe%3A%20Automatic%20Updates%20in%20BETA-Channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-839167%22%20slang%3D%22en-US%22%3Eyes%2C%20you%20are%20right!%20sorry%20didnt%20see%20this%20hint.%20i%20have%20imported%20the%20amdx-policy%20template%20but%20the%20update-policy%20was%20not%20shown...%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

does the BETA-Channel Version of Edge auto-updates too? (similar to the dev channel?)

because we would like to test a sccm-deploying with the MSI-package of the BETA. and if edge is auto-updating, every time SCCM would perform a downgrade -> not very cool....

6 Replies
Highlighted

They send auto updates through for Beta too. In other words you don't have to manually re-download the browser or download the update builds every time there's an update. Beta is only updated about every six weeks or so (with smaller security or minor type updates like everyone's browser is breaking and crashing so a revision update is went through a few days after the original update). Windows Task Scheduler has a Microsoft schedule set in too auto update MS programs. There's also an update folder for Edge in your Windows Directory. 

 

Capture.png

 

2.JPG

 

 

Highlighted
Best Response confirmed by Steve Rugh (Microsoft)
Solution
Highlighted

mille grazie ;) i hope, they will provide a function in the GPO for the future. we would like to control the update deployment like other updates during our SCCM environment. i don't like beta-testing in the user environment ;) @ItalianAce 

Highlighted

hmmm i'm not sure, but you refer to the standard GPO of the "normal" Edge Browser and not the Chromium Engine. I don't think this will work with the BETA? @Gunnar Haslinger 

Highlighted

@_Sandro_ no, I don't refer to the GPO for the old/normal Edge Browser, see at the top of the Page, it clearly says "This article applies to Microsoft Edge version 77 or later." => This is definitely Edge beta based on Chromium and not the "regular EdgeHTML" Version. In regular EdgeHTML there was no UpdateManager and no policy for the UpdateManager.

Highlighted
yes, you are right! sorry didnt see this hint. i have imported the amdx-policy template but the update-policy was not shown...