1. Edge For Windows Server 2016
2. Edge For Windows 2016 Server
3. Microsoft Edge For Windows Server 2019
4. Edge For Server Download
5. Edge For Windows 8.1 Download
6. Edge Browser Download For 2016 Server
7. Free Microsoft Edge For Windows 7

The Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016, don't include Microsoft Edge or many other Universal Windows Platform (UWP) apps. These apps and their services are frequently updated with new functionality, and can't be supported on systems running the LTSB operating systems. I don't know if they will give official support for windows server 2008 R2 and up, but because windows server is based on the same windows NT kernel that home versions of windows like windows 7 (windows server 2008 R2) or windows 8.1 (windows server 2012 R2) or windows 10 (windows server 2016 and windows server 2019), it should work the same with minimal to no problems.

Applies to: IoT Edge 1.1

Try out Azure IoT Edge in this quickstart by deploying containerized code to a Linux on Windows IoT Edge device. IoT Edge allows you to remotely manage code on your devices so that you can send more of your workloads to the edge. For this quickstart, we recommend using your own device to see how easy it is to use Azure IoT Edge for Linux on Windows.

In this quickstart, you'll learn how to:

• Create an IoT hub.
• Register an IoT Edge device to your IoT hub.
• Install and start the IoT Edge for Linux on Windows runtime on your device.
• Remotely deploy a module to an IoT Edge device and send telemetry.

This quickstart walks you through how to set up your Azure IoT Edge for Linux on Windows device. Then, you'll deploy a module from the Azure portal to your device. The module you'll use is a simulated sensor that generates temperature, humidity, and pressure data. Other Azure IoT Edge tutorials build on the work you do here by deploying modules that analyze the simulated data for business insights.

Edge For Windows Server 2016

If you don't have an active Azure subscription, create a free account before you begin.

Note

IoT Edge for Linux on Windows is in public preview.

Prerequisites

Prepare your environment for the Azure CLI.

• Use the Bash environment in Azure Cloud Shell.

• If you prefer, install the Azure CLI to run CLI reference commands.

  • If you're using a local installation, sign in to the Azure CLI by using the az login command. To finish the authentication process, follow the steps displayed in your terminal. For additional sign-in options, see Sign in with the Azure CLI.

  • When you're prompted, install Azure CLI extensions on first use. For more information about extensions, see Use extensions with the Azure CLI.

  • Run az version to find the version and dependent libraries that are installed. To upgrade to the latest version, run az upgrade.

Create a cloud resource group to manage all the resources you'll use in this quickstart.

Make sure your IoT Edge device meets the following requirements:

• Editions

  • Windows 10 version 1809 or later; build 17763 or later
    • Professional, Enterprise, IoT Enterprise
  • Windows Server 2019 build 17763 or later

• Hardware requirements

  • Minimum Free Memory: 1 GB
  • Minimum Free Disk Space: 10 GB

Note

This quickstart uses Windows Admin Center to create a deployment of IoT Edge for Linux on Windows. You can also use PowerShell. If you wish to use PowerShell to create your deployment, follow the steps in the how-to guide on installing and provisioning Azure IoT Edge for Linux on a Windows device.

Create an IoT hub

Start by creating an IoT hub with the Azure CLI.

The free level of Azure IoT Hub works for this quickstart. If you've used IoT Hub in the past and already have a hub created, you can use that IoT hub.

The following code creates a free F1 hub in the resource group IoTEdgeResources. Replace {hub_name} with a unique name for your IoT hub. It might take a few minutes to create an IoT hub.

If you get an error because you already have one free hub in your subscription, change the SKU to S1. If you get an error that the IoT hub name isn't available, someone else already has a hub with that name. Try a new name.

Register an IoT Edge device

Register an IoT Edge device with your newly created IoT hub.

Create a device identity for your simulated device so that it can communicate with your IoT hub. The device identity lives in the cloud, and you use a unique device connection string to associate a physical device to a device identity.

IoT Edge devices behave and can be managed differently than typical IoT devices. Use the --edge-enabled flag to declare that this identity is for an IoT Edge device.

1. In Azure Cloud Shell, enter the following command to create a device named myEdgeDevice in your hub.

   If you get an error about iothubowner policy keys, make sure that Cloud Shell is running the latest version of the Azure IoT extension.

2. View the connection string for your device, which links your physical device with its identity in IoT Hub. It contains the name of your IoT hub, the name of your device, and a shared key that authenticates connections between the two.

3. Copy the value of the connectionString key from the JSON output and save it. This value is the device connection string. You'll use it to configure the IoT Edge runtime in the next section.

Install and start the IoT Edge runtime

Install IoT Edge for Linux on Windows on your device, and configure it with the device connection string.

1. Download Windows Admin Center.

2. Follow the prompts in the installation wizard to set up Windows Admin Center on your device.

3. Open Windows Admin Center.

4. Select the Settings gear icon in the upper-right corner, and then select Extensions.

5. On the Feeds tab, select Add.

6. Enter https://aka.ms/wac-insiders-feed into the text box, and then select Add.

7. After the feed has been added, go to the Available extensions tab and wait for the extensions list to update.

8. From the list of Available extensions, select Azure IoT Edge.

9. Install the extension.

10. When the extension is installed, select Windows Admin Center in the upper-left corner to go to the main dashboard page.

    The localhost connection represents the PC where you're running Windows Admin Center.

11. Select Add.

12. On the Azure IoT Edge tile, select Create new to start the installation wizard.

13. Continue through the installation wizard to accept the Microsoft Software License Terms, and then select Next.

14. Select Optional diagnostic data, and then select Next: Deploy. This selection provides extended diagnostics data that helps Microsoft monitor and maintain quality of service.

15. On the Select target device screen, select your desired target device to validate that it meets the minimum requirements. For this quickstart, we're installing IoT Edge on the local device, so choose the localhost connection. If the target device meets the requirements, select Next to continue.

16. ​Select Next to accept the default settings. The deployment screen shows the process of downloading the package, installing the package, configuring the host, and final setting up the Linux virtual machine (VM)​. A successful deployment looks like this:

17. Select Next: Connect to continue to the final step to provision your Azure IoT Edge device with its device ID from your IoT hub instance.

18. Paste the connection string you copied earlier in this quickstart into the Device connection string field. Then select Provisioning with the selected method​.

19. After provisioning is complete, select Finish to complete and return to the Windows Admin Center start screen. You should see your device listed as an IoT Edge device.

20. Select your Azure IoT Edge device to view its dashboard​. You should see that the workloads from your device twin in Azure IoT Hub have been deployed. The IoT Edge Module List should show one module running edgeAgent, and the IoT Edge Status should be active (running).

Your IoT Edge device is now configured. It's ready to run cloud-deployed modules.

Deploy a module

Manage your Azure IoT Edge device from the cloud to deploy a module that sends telemetry data to IoT Hub.

One of the key capabilities of Azure IoT Edge is deploying code to your IoT Edge devices from the cloud. IoT Edge modules are executable packages implemented as containers. In this section, you'll deploy a pre-built module from the IoT Edge Modules section of Azure Marketplace directly from Azure IoT Hub.

The module that you deploy in this section simulates a sensor and sends generated data. This module is a useful piece of code when you're getting started with IoT Edge because you can use the simulated data for development and testing. If you want to see exactly what this module does, you can view the simulated temperature sensor source code.

Follow these steps to deploy your first module from Azure Marketplace.

1. Sign in to the Azure portal and go to your IoT hub.

2. From the menu on the left, under Automatic Device Management, select IoT Edge.

3. Select the device ID of the target device from the list of devices.

4. On the upper bar, select Set Modules.

5. Under IoT Edge Modules, open the Add drop-down menu, and then select Marketplace Module.

6. In IoT Edge Module Marketplace, search for and select the Simulated Temperature Sensor module.

   The module is added to the IoT Edge Modules section with the desired running status. Philips usb devices driver download for windows.

7. Select Next: Routes to continue to the next step of the wizard.

8. On the Routes tab, remove the default route, route, and then select Next: Review + create to continue to the next step of the wizard.

   Note

   Routes are constructed by using name and value pairs. You should see two routes on this page. The default route, route, sends all messages to IoT Hub (which is called $upstream). A second route, SimulatedTemperatureSensorToIoTHub, was created automatically when you added the module from Azure Marketplace. This route sends all messages from the simulated temperature module to IoT Hub. You can delete the default route because it's redundant in this case.

9. Review the JSON file, and then select Create. The JSON file defines all of the modules that you deploy to your IoT Edge device. You'll see the SimulatedTemperatureSensor module and the two runtime modules, edgeAgent and edgeHub.

   Note

   When you submit a new deployment to an IoT Edge device, nothing is pushed to your device. Instead, the device queries IoT Hub regularly for any new instructions. If the device finds an updated deployment manifest, it uses the information about the new deployment to pull the module images from the cloud then starts running the modules locally. This process can take a few minutes.

10. After you create the module deployment details, the wizard returns you to the device details page. View the deployment status on the Modules tab.

    You should see three modules: $edgeAgent, $edgeHub, and SimulatedTemperatureSensor. If one or more of the modules has YES under SPECIFIED IN DEPLOYMENT but not under REPORTED BY DEVICE, your IoT Edge device is still starting them. Wait a few minutes, and then refresh the page.

View the generated data

In this quickstart, you created a new IoT Edge device and installed the IoT Edge runtime on it. Then you used the Azure portal to deploy an IoT Edge module to run on the device without having to make changes to the device itself.

The module that you pushed generates sample environment data that you can use for testing later. The simulated sensor is monitoring both a machine and the environment around the machine. For example, this sensor might be in a server room, on a factory floor, or on a wind turbine. The messages that it sends include ambient temperature and humidity, machine temperature and pressure, and a timestamp. IoT Edge tutorials use the data created by this module as test data for analytics.

From the command shell in Windows Admin Center, confirm that the module you deployed from the cloud is running on your IoT Edge device.

1. Connect to your newly created IoT Edge device.

   On the Overview page, you'll see the IoT Edge Module List and IoT Edge Status. You can see the modules that have been deployed and the device status.

2. Under Tools, select Command Shell. The command shell is a PowerShell terminal that automatically uses Secure Shell (SSH) to connect to your Azure IoT Edge device's Linux VM on your Windows PC.

3. To verify the three modules on your device, run the following Bash command:

4. View the messages being sent from the temperature sensor module to the cloud.

   Important

   IoT Edge commands are case-sensitive when they refer to module names.

You can also use the Azure IoT Hub extension for Visual Studio Code to watch messages arrive at your IoT hub.

Clean up resources

Edge For Windows 2016 Server

If you want to continue on to the IoT Edge tutorials, skip this step. You can use the device that you registered and set up in this quickstart. Otherwise, you can delete the Azure resources that you created to avoid charges.

If you created your virtual machine and IoT hub in a new resource group, you can delete that group and all the associated resources. If you don't want to delete the whole group, you can delete individual resources instead.

Important

Check the contents of the resource group to make sure that there's nothing you want to keep. Deleting a resource group is irreversible.

Use the following command to remove the IoTEdgeResources group. Deletion might take a few minutes.

Microsoft Edge For Windows Server 2019

You can confirm that the resource group is removed by using this command to view the list of resource groups.

Remove Azure IoT Edge for Linux on Windows

Use the dashboard extension in Windows Admin Center to uninstall Azure IoT Edge for Linux on Windows.

1. Connect to the IoT Edge device in Windows Admin Center. The Azure dashboard tool extension loads.

2. Select Uninstall. After Azure IoT Edge is removed, Windows Admin Center removes the Azure IoT Edge device connection entry from the Start page.

Note

Another way to remove Azure IoT Edge from your Windows system is to select Start > Settings > Apps > Azure IoT Edge > Uninstall on your IoT Edge device. This method removes Azure IoT Edge from your IoT Edge device, but leaves the connection behind in Windows Admin Center. To complete the removal, uninstall Windows Admin Center from the Settings menu as well.

Next steps

In this quickstart, you created an IoT Edge device and used the Azure IoT Edge cloud interface to deploy code onto the device. Now you have a test device generating raw data about its environment.

Next, set up your local development environment so that you can start creating IoT Edge modules that run your business logic.

Applies to: Configuration Manager (Current Branch)

The all-new Microsoft Edge is ready for business. Starting in Configuration Manager version 1910, you can now deploy Microsoft Edge, version 77 and later to your users. A PowerShell script is used to install the Edge build selected. The script also turns off automatic updates for Edge so they can be managed with Configuration Manager.

Deploy Microsoft Edge

Admins can pick the Beta, Dev, or Stable channel, along with a version of the Microsoft Edge client to deploy. Each release incorporates learnings and improvements from our customers and community.

Prerequisites for deploying

For clients targeted with a Microsoft Edge deployment:

• PowerShell Execution Policy can't be set to Restricted.

  • PowerShell is executed to perform the installation.

• The Microsoft Edge installer and CMPivot are signed with the Microsoft Code Signing certificate. If that certificate isn't listed in the Trusted Publishers store, you'll need to add it. Otherwise, the Microsoft Edge installer and CMPivot won’t run when the PowerShell execution policy is set to AllSigned.

The device running the Configuration Manager console needs access to the following endpoints for deploying Microsoft Edge:

Verify Microsoft Edge update policies

Configuration Manager version 1910

In version 1910, when Microsoft Edge is deployed, the installation script turns off automatic updates for Microsoft Edge so they can be managed with Configuration Manager. You can change this behavior using Group Policy. For more information, see Plan your deployment of Microsoft Edge and Microsoft Edge update policies.

Configuration Manager version 2002 and later

Starting in version 2002, you can create a Microsoft Edge application that's set up to receive automatic updates rather than having automatic updates disabled. This change allows you to choose to manage updates for Microsoft Edge with Configuration Manager or allow Microsoft Edge to automatically update. When creating the application, select Allow Microsoft Edge to automatically update the version of the client on the end user's device on the Microsoft Edge Settings page. If you previously used Group Policy to change this behavior, Group Policy will overwrite the setting made by Configuration Manager during installation of Microsoft Edge.

Create a deployment

Create a Microsoft Edge application using the built-in application experience, which makes Microsoft Edge easier to manage:

1. In the console, under Software Library, there's a new node called Microsoft Edge Management.

2. Select Create Microsoft Edge Application from either the ribbon, or by right-clicking on the Microsoft Edge Management node.

3. On the Application Settings page of the wizard, specify a name, description, and location for the content for the app. Ensure the content location folder you specify is empty.

4. On the Microsoft Edge Settings page, select:

   • The channel to deploy
   • The version to deploy
   • If you want to Allow Microsoft Edge to automatically update the version of the client on the end user's device (added in version 2002)

5. On the Deployment page, decide if you want to deploy the application. If you select Yes, you can specify your deployment settings for the application. For more information about deployment settings, see Deploy applications.

6. In Software Center on the client device, the user can see and install the application.

Log files for deployment

Update Microsoft Edge

Starting in Configuration Manager version 1910, you'll see a node called All Microsoft Edge updates under Microsoft Edge Management. This node helps you manage updates for all Microsoft Edge channels.

1. To get updates for Microsoft Edge, ensure you have the Updates classification and the Microsoft Edge product selected for synchronization.

2. In the Software Library workspace, expand Microsoft Edge Management and click on the All Microsoft Edge Updates node.

3. If needed, click Synchronize Software Updates in the ribbon to start a synchronization. For more information, see Synchronize software updates.

4. Manage and deploy Microsoft Edge updates like any other update, such as adding them to your automatic deployment rule. Some of the common updates tasks you can do from the All Microsoft Edge Updates node include:

Edge For Server Download

Microsoft Edge Management dashboard

(Introduced in version 2002)

Starting in Configuration Manager 2002, the Microsoft Edge Management dashboard provides you insights on the usage of Microsoft Edge and other browsers. In this dashboard, you can:

Edge For Windows 8.1 Download

• See how many of your devices have Microsoft Edge installed
• See how many clients have different versions of Microsoft Edge installed.
  • This chart doesn't include Canary Channel.
• Have a view of the installed browsers across devices
• Have a view of preferred browser by device
  • Currently for the 2002 release, this chart will be empty.

Prerequisites for the dashboard

Enable the following properties in the below hardware inventory classes for the Microsoft Edge Management dashboard:

• Installed Software - Asset Intelligence (SMS_InstalledSoftware)

  • Software Code
  • Product Name
  • Product Version

• Default Browser (SMS_DefaultBrowser)

  • Browser Program ID

• Browser Usage (SMS_BrowserUsage)

  • BrowserName
  • UsagePercentage

View the dashboard

From the Software Library workspace, click Microsoft Edge Management to see the dashboard. Change the collection for the graph data by clicking Browse and choosing another collection. By default your five largest collections are in the drop-down list. When you select a collection that isn't in the list, the newly selected collection takes the bottom spot on your drop-down list.

Known issues

Edge Browser Download For 2016 Server

Hardware inventory may fail to process

Hardware inventory for devices might fail to process. Errors similar to the one below may be seen in the Dataldr.log file:

Free Microsoft Edge For Windows 7

Mitigation: To work around this issue, disable the collection of the Browser Usage (SMS_BrowerUsage) hardware inventory class.

Next steps