Will get a JSON response that can be used to figure out what channels and which versions are available. Using PowerShell and Invoke-WebRequest on There it states that the above URL must be allowed which is good since that means it will likely not be changed or removed in the near future. Trying a common search engine failed this time so decided to fire up Fiddler in my LAB to see what URL:s ConfigMgr was talking with.īingo! That was what I was looking for, searching for that URL instead gave a hit here: But since ConfigMgr seemed to have an automated way of identifying the latest version and downloading it I though that there must be a way to replicate this with PowerShell.įirst I needed to figure out from where ConfigMgr got the file. Of course there is always the option to manually download the latest file from and then manually replace and update the Edge Application.

However since applications tend to have security fixes and bugfixes it can be a good idea to keep the source Application somewhat up to date as well. So what does this mean and it is a problem? Well not really, if it is allowed to auto update it will update itself as soon as it is deployed or if allow auto update isn't selected but updates are available via WSUS/CM it will eventually get to that version. The MSI file for Edge Chromium and a PowerShell file that will handle the installation. So once created it will download two files to the path that was choosen during the wizard. However once this package is created it will always install the version that was chosen and 'latest' only means the latest version at time of creation. Here there is also an option to select that once the browser is installed that it will auto update itself. In Microsoft Endpoint Configuration Manager you can create an Edge Application using a Wizard that will download the latest (or a specific) version.

Download edge for business