mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-29 21:57:23 +00:00
Merge pull request #2181 from MicrosoftDocs/master
Publish 03/02/2020 10:30 am PST
This commit is contained in:
Rebecca Agiewich
GitHub
commit
dab37bbb38
@ -35,7 +35,7 @@ You must download the deployment folder (**EMIEWebPortal/**), which includes all
|
||||
|
||||
2. Install the Node.js® package manager, [npm](https://www.npmjs.com/).
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> You need to install the npm package manager to replace all the third-party libraries we removed to make the Enterprise Mode Site List Portal open-source.
|
||||
|
||||
3. Open File Explorer and then open the **EMIEWebPortal/** folder.
|
||||
@ -105,7 +105,7 @@ Create a new Application Pool and the website, by using the IIS Manager.
|
||||
|
||||
9. Double-click the **Authentication** icon, right-click on **Windows Authentication**, and then click **Enable**.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> You must also make sure that **Anonymous Authentication** is marked as **Enabled**.
|
||||
|
||||
10. Return to the **<<i>website_name</i>> Home** pane, and double-click the **Connection Strings** icon.
|
||||
@ -116,7 +116,7 @@ Create a new Application Pool and the website, by using the IIS Manager.
|
||||
|
||||
- **Initial catalog.** The name of your database.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> Step 3 of this topic provides the steps to create your database.
|
||||
|
||||
## Step 3 - Create and prep your database
|
||||
@ -216,7 +216,7 @@ Register the EMIEScheduler tool and service for production site list changes.
|
||||
|
||||
1. Open File Explorer and go to EMIEWebPortal.SchedulerService\EMIEWebPortal.SchedulerService in your deployment directory, and then copy the **App_Data**, **bin**, and **Logs** folders to a separate folder. For example, C:\EMIEService\.
|
||||
|
||||
>[!Important]
|
||||
> [!IMPORTANT]
|
||||
> If you can't find the **bin** and **Logs** folders, you probably haven't built the Visual Studio solution. Building the solution creates the folders and files.
|
||||
|
||||
2. In Visual Studio start the Developer Command Prompt as an administrator, and then change the directory to the location of the InstallUtil.exe file. For example, _C:\Windows\Microsoft.NET\Framework\v4.0.30319_.
|
||||
|
||||
@ -7,7 +7,8 @@ author: dansimp
|
||||
ms.prod: ie11
|
||||
ms.assetid: da659ff5-70d5-4852-995e-4df67c4871dd
|
||||
ms.reviewer:
|
||||
audience: itpro
manager: dansimp
|
||||
audience: itpro
|
||||
manager: dansimp
|
||||
ms.author: dansimp
|
||||
title: Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.2) (Internet Explorer 11 for IT Pros)
|
||||
ms.sitesec: library
|
||||
@ -62,15 +63,15 @@ Each XML file must include:
|
||||
|
||||
The following is an example of what your XML file should look like when you’re done adding your sites. For more info about how to create your XML file, see [Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md).
|
||||
|
||||
```
|
||||
```xml
|
||||
<site-list version="205">
|
||||
<!--- File creation header --->
|
||||
<!-- File creation header -->
|
||||
<created-by>
|
||||
<tool>EnterpriseSitelistManager</tool>
|
||||
<version>10240</version>
|
||||
<date-created>20150728.135021</date-created>
|
||||
</created-by>
|
||||
<!--- Begin Site List --->
|
||||
<!-- Begin Site List -->
|
||||
<site url="www.cpandl.com">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>MSEdge</open-in>
|
||||
@ -115,8 +116,3 @@ After you’ve added all of your sites to the tool and saved the file to XML, yo
|
||||
- [Download the Enterprise Mode Site List Manager (schema v.2)](https://go.microsoft.com/fwlink/p/?LinkId=716853)
|
||||
- [Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ current version of Internet Explorer.
|
||||
|
||||
Internet Explorer 11 replaces Internet Explorer 8, Internet Explorer 9, or Internet Explorer 10. If you decide you don’t want Internet Explorer 11, and you’re running Windows 7 SP1 or Windows Server 2008 R2 with SP1, you can uninstall it from the **View installed updates** section of the **Uninstall an update** page of the Control Panel.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> If a user installs Internet Explorer 11 and then removes it, it won’t be re-offered to that computer through Automatic Updates. Instead, the user will have to manually re-install the app.
|
||||
|
||||
## Internet Explorer 11 automatic upgrades
|
||||
@ -52,13 +52,13 @@ If you use Automatic Updates in your company, but want to stop your users from a
|
||||
|
||||
- **Download and use the Internet Explorer 11 Blocker Toolkit.** Includes a Group Policy template and a script that permanently blocks Internet Explorer 11 from being offered by Windows Update or Microsoft Update as a high-priority update. You can download this kit from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=40722).
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> The toolkit won't stop users with local administrator accounts from manually installing Internet Explorer 11. Using this toolkit also prevents your users from receiving automatic upgrades from Internet Explorer 8, Internet Explorer 9, or Internet Explorer 10 to Internet Explorer 11. For more information, see the [Internet Explorer 11 Blocker Toolkit frequently asked questions](../ie11-faq/faq-ie11-blocker-toolkit.md).
|
||||
|
||||
- **Use an update management solution to control update deployment.**
|
||||
If you already use an update management solution, like [Windows Server Update Services (WSUS)](https://docs.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) or the more advanced [Microsoft Endpoint Configuration Manager](https://go.microsoft.com/fwlink/?LinkID=276664), you should use that instead of the Internet Explorer Blocker Toolkit.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> If you use WSUS to manage updates, and Update Rollups are configured for automatic installation, Internet Explorer will automatically install throughout your company. This scenario is discussed in detail in the Knowledge Base article [here](https://support.microsoft.com/kb/946202).
|
||||
|
||||
Additional information on Internet Explorer 11, including a Readiness Toolkit, technical overview, in-depth feature summary, and Internet Explorer 11 download is available on the [Internet Explorer 11 page of the Microsoft Edge IT Center](https://technet.microsoft.com/microsoft-edge/dn262703.aspx).
|
||||
@ -81,12 +81,12 @@ Internet Explorer 11 will be released to WSUS as an Update Rollup package. There
|
||||
4. Click the rule that automatically approves an update that is classified as
|
||||
Update Rollup, and then click **Edit.**
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> If you don’t see a rule like this, you most likely haven’t configured WSUS to automatically approve Update Rollups for installation. In this situation, you don’t have to do anything else.
|
||||
|
||||
5. Click the **Update Rollups** property under the **Step 2: Edit the properties (click an underlined value)** section.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> The properties for this rule will resemble the following:<ul><li>When an update is in Update Rollups</li><li>Approve the update for all computers</li></ul>
|
||||
|
||||
6. Clear the **Update Rollup** check box, and then click **OK**.
|
||||
@ -105,7 +105,7 @@ Internet Explorer 11 will be released to WSUS as an Update Rollup package. There
|
||||
|
||||
13. Check to make sure that Microsoft Internet Explorer 11 is listed as an unapproved update.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> There may be multiple updates, depending on the imported language and operating system updates.
|
||||
|
||||
**Optional**
|
||||
@ -126,7 +126,7 @@ If you need to reset your Update Rollups packages to auto-approve, do this:
|
||||
|
||||
7. Click **OK** to close the **Automatic Approvals** dialog box.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> Because auto-approval rules are only evaluated when an update is first imported into WSUS, turning this rule back on after the Internet Explorer 11 update has been imported and synchronized to the server won’t cause this update to be auto-approved.
|
||||
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You must download the deployment folder (**EMIEWebPortal/**), which includes all
|
||||
|
||||
2. Install the Node.js® package manager, [npm](https://www.npmjs.com/).
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> You need to install the npm package manager to replace all the third-party libraries we removed to make the Enterprise Mode Site List Portal open-source.
|
||||
|
||||
3. Open File Explorer and then open the **EMIEWebPortal/** folder.
|
||||
@ -49,7 +49,7 @@ You must download the deployment folder (**EMIEWebPortal/**), which includes all
|
||||
|
||||
6. Go back up a directory, open the solution file **EMIEWebPortal.sln** in Visual Studio, open **Web.config** from **EMIEWebPortal/** folder, and replace MSIT-LOB-COMPAT with your server name hosting your database, replace LOBMerged with your database name, and build the entire solution.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> Step 3 of this topic provides the steps to create your database.
|
||||
|
||||
7. Copy the contents of the **EMIEWebPortal/** folder to a dedicated folder on your file system. For example, _D:\EMIEWebApp_. In a later step, you'll designate this folder as your website in the IIS Manager.
|
||||
@ -109,7 +109,7 @@ Create a new Application Pool and the website, by using the IIS Manager.
|
||||
|
||||
9. Double-click the **Authentication** icon, right-click on **Windows Authentication**, and then click **Enable**.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> You must also make sure that **Anonymous Authentication** is marked as **Enabled**.
|
||||
|
||||
## Step 3 - Create and prep your database
|
||||
@ -209,7 +209,7 @@ Register the EMIEScheduler tool and service for production site list changes.
|
||||
|
||||
1. Open File Explorer and go to EMIEWebPortal.SchedulerService\EMIEWebPortal.SchedulerService in your deployment directory, and then copy the **App_Data**, **bin**, and **Logs** folders to a separate folder. For example, C:\EMIEService\.
|
||||
|
||||
>[!Important]
|
||||
> [!IMPORTANT]
|
||||
> If you can't find the **bin** and **Logs** folders, you probably haven't built the Visual Studio solution. Building the solution creates the folders and files.
|
||||
|
||||
2. In Visual Studio start the Developer Command Prompt as an administrator, and then change the directory to the location of the InstallUtil.exe file. For example, _C:\Windows\Microsoft.NET\Framework\v4.0.30319_.
|
||||
|
||||
@ -64,8 +64,3 @@ Before you can use a site list with Enterprise Mode, you need to turn the functi
|
||||
- [Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.1)](add-multiple-sites-to-enterprise-mode-site-list-using-the-version-1-schema-and-enterprise-mode-tool.md)
|
||||
- [Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.2)](add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -49,11 +49,3 @@ IE11 uses the **One Box** feature, which lets users type search terms directly i
|
||||
> [!NOTE]
|
||||
> Depending on how you've set up your intranet search, the text entry might resolve to an intranet site. For more information about this, see [Intranet problems with Internet Explorer 11](intranet-problems-and-ie11.md).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ You can customize and install IEAK 11 on the following supported operating syste
|
||||
|
||||
- Windows Server 2008 R2 Service Pack 1 (SP1)
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> IEAK 11 does not support building custom packages for Windows RT.
|
||||
|
||||
|
||||
@ -44,13 +44,13 @@ You can customize and install IEAK 11 on the following supported operating syste
|
||||
|
||||
The IEAK 11 enables you to customize branding and settings for Internet Explorer 11. For PCs running Windows 7, the custom package also includes the Internet Explorer executable.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> Internet Explorer 11 is preinstalled on PCs running Windows 8. Therefore, the executable is not included in the customized package.
|
||||
|
||||
**Can IEAK 11 build custom Internet Explorer 11 packages in languages other than the language of the in-use IEAK 11 version?**
|
||||
Yes. You can use IEAK 11 to build custom Internet Explorer 11 packages in any of the supported 24 languages. You'll select the language for the custom package on the Language Selection page of the customization wizard.
|
||||
|
||||
>[!Note]
|
||||
> [!NOTE]
|
||||
> IEAK 11 is available in 24 languages but can build customized Internet Explorer 11 packages in all languages of the supported operating systems. To download IEAK 11, see [Internet Explorer Administration Kit (IEAK) information and downloads](../ie11-ieak/ieak-information-and-downloads.md).
|
||||
|
||||
**Q: Is there a version of the Internet Explorer Administration Kit (IEAK) supporting IE11?**<br>
|
||||
|
||||
@ -30,7 +30,7 @@ Deployment status summarizes detailed status into higher-level states to get a q
|
||||
|Deployment status |Description |
|
||||
|---------|---------|
|
||||
|Failed | The device encountered a failure during the update process. Note that due to latency, devices reporting this status may have since retried the update. |
|
||||
|Progress stalled | he device started the update process, but no progress has been reported in the last 7 days. |
|
||||
|Progress stalled | The device started the update process, but no progress has been reported in the last 7 days. |
|
||||
|Deferred | The device is currently deferring the update process due to Windows Update for Business policies. |
|
||||
|In progress | The device has begun the updating process for this update. This status appears if the device is in any stage of the update process including and after download, but before completing the update. If no progress has been reported in the last 7 days, devices will move to **Progress stalled**.** |
|
||||
|Update completed | The device has completed the update process. |
|
||||
@ -42,7 +42,7 @@ Deployment status summarizes detailed status into higher-level states to get a q
|
||||
Detailed status provides a detailed stage-level representation of where in the update process the device was last reported to be in relative to this specific update. Note that with the latency of deployment data, devices might have since moved on from the reported detailed status.
|
||||
|
||||
|
||||
|Detaild status |Description |
|
||||
|Detailed status |Description |
|
||||
|---------|---------|
|
||||
|Scheduled in next X days | The device is currently deferring the update with Windows Update for Business policies but will be offered the update within the next X days. |
|
||||
|Compatibility hold | The device has been placed under a *compatibility hold* to ensure a smooth feature update experience and will not resume the update until the hold has been cleared. For more information see [Feature Update Status report](update-compliance-feature-update-status.md#compatibility-holds) |
|
||||
@ -59,7 +59,7 @@ Detailed status provides a detailed stage-level representation of where in the u
|
||||
|Commit | The device, after a restart, is committing changes relevant to the update. |
|
||||
|Finalize succeeded | The device has finished final tasks after a restart to apply the update. |
|
||||
|Update successful | The device has successfully applied the update. |
|
||||
|Cancelled | The update was cancelled at some point in the update process. |
|
||||
|Cancelled | The update was canceled at some point in the update process. |
|
||||
|Uninstalled | The update was successfully uninstalled from the device. |
|
||||
|Rollback | The update failed to apply during the update process, causing the device to roll back changes and revert to the previous update. |
|
||||
|
||||
|
||||
@ -25,7 +25,10 @@ ms.custom: autopilot
|
||||
|
||||
To get started with Windows Autopilot, you should try it out with a virtual machine (VM) or you can use a physical device that will be wiped and then have a fresh install of Windows 10.
|
||||
|
||||
In this topic you'll learn how to set-up a Windows Autopilot deployment for a VM using Hyper-V. Note: Although there are [multiple platforms](administer.md) available to enable Autopilot, this lab primarily uses Intune.
|
||||
In this topic you'll learn how to set-up a Windows Autopilot deployment for a VM using Hyper-V.
|
||||
|
||||
> [!NOTE]
|
||||
> Although there are [multiple platforms](administer.md) available to enable Autopilot, this lab primarily uses Intune.
|
||||
|
||||
> Hyper-V and a VM are not required for this lab. You can also use a physical device. However, the instructions assume that you are using a VM. To use a physical device, skip the instructions to install Hyper-V and create a VM. All references to 'device' in the guide refer to the client device, either physical or virtual.
|
||||
|
||||
@ -121,7 +124,7 @@ To read more about Hyper-V, see [Introduction to Hyper-V on Windows 10](https://
|
||||
|
||||
Now that Hyper-V is enabled, we need to create a VM running Windows 10. We can [create a VM](https://docs.microsoft.com/virtualization/hyper-v-on-windows/quick-start/create-virtual-machine) and [virtual network](https://docs.microsoft.com/virtualization/hyper-v-on-windows/quick-start/connect-to-network) using Hyper-V Manager, but it is simpler to use Windows PowerShell.
|
||||
|
||||
To use Windows Powershell we just need to know two things:
|
||||
To use Windows PowerShell, we just need to know two things:
|
||||
|
||||
1. The location of the Windows 10 ISO file.
|
||||
- In the example, we assume the location is **c:\iso\win10-eval.iso**.
|
||||
@ -222,7 +225,7 @@ Ensure the VM booted from the installation ISO, click **Next** then click **Inst
|
||||
|
||||
|
||||
|
||||
>After the VM restarts, during OOBE, it’s fine to select **Set up for personal use** or **Domain join instead** and then choose an offline account on the **Sign in** screen. This will offer the fastest way to the desktop. For example:
|
||||
After the VM restarts, during OOBE, it’s fine to select **Set up for personal use** or **Domain join instead** and then choose an offline account on the **Sign in** screen. This will offer the fastest way to the desktop. For example:
|
||||
|
||||
|
||||
|
||||
@ -240,7 +243,8 @@ Click on the **WindowsAutopilot** VM in Hyper-V Manager and verify that you see
|
||||
|
||||
## Capture the hardware ID
|
||||
|
||||
>NOTE: Normally, the Device ID is captured by the OEM as they run the OA3 Tool on each device in the factory. The OEM then submits the 4K HH created by the OA3 Tool to Microsoft by submitting it with a Computer Build Report (CBR). For purposes of this lab, you are acting as the OEM (capturing the 4K HH), but you’re not going to use the OA3 Tool to capture the full 4K HH for various reasons (you’d have to install the OA3 tool, your device couldn’t have a volume license version of Windows, it’s a more complicated process than using a PS script, etc.). Instead, you’ll simulate running the OA3 tool by running a PowerShell script, which captures the device 4K HH just like the OA3 tool.
|
||||
> [!NOTE]
|
||||
> Normally, the Device ID is captured by the OEM as they run the OA3 Tool on each device in the factory. The OEM then submits the 4K HH created by the OA3 Tool to Microsoft by submitting it with a Computer Build Report (CBR). For purposes of this lab, you are acting as the OEM (capturing the 4K HH), but you’re not going to use the OA3 Tool to capture the full 4K HH for various reasons (you’d have to install the OA3 tool, your device couldn’t have a volume license version of Windows, it’s a more complicated process than using a PS script, etc.). Instead, you’ll simulate running the OA3 tool by running a PowerShell script, which captures the device 4K HH just like the OA3 tool.
|
||||
|
||||
Follow these steps to run the PS script:
|
||||
|
||||
@ -294,7 +298,8 @@ PS C:\HWID>
|
||||
|
||||
Verify that there is an **AutopilotHWID.csv** file in the **c:\HWID** directory that is about 8 KB in size. This file contains the complete 4K HH.
|
||||
|
||||
**Note**: Although the .csv extension might be associated with Microsoft Excel, you cannot view the file properly by double-clicking it. To correctly parse the comma delimiters and view the file in Excel, you must use the **Data** > **From Text/CSV** function in Excel to import the appropriate data columns. You don't need to view the file in Excel unless you are curious. The file format will be validated when it is imported into Autopilot. An example of the data in this file is shown below.
|
||||
> [!NOTE]
|
||||
> Although the .csv extension might be associated with Microsoft Excel, you cannot view the file properly by double-clicking it. To correctly parse the comma delimiters and view the file in Excel, you must use the **Data** > **From Text/CSV** function in Excel to import the appropriate data columns. You don't need to view the file in Excel unless you are curious. The file format will be validated when it is imported into Autopilot. An example of the data in this file is shown below.
|
||||
|
||||
|
||||
|
||||
@ -580,7 +585,10 @@ This will remove the device from Intune management, and it will disappear from *
|
||||
|
||||
|
||||
|
||||
The **Intune > Devices > All Devices** list and the **Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices** list mean different things and are two completely separate datastores. The former (All devices) is the list of devices currently enrolled into Intune. Note: A device will only appear in the All devices list once it has booted. The latter (Windows Autopilot Deployment Program > Devices) is the list of devices currently registered from that Intune account into the Autopilot program - which may or may not be enrolled to Intune.
|
||||
The **Intune > Devices > All Devices** list and the **Intune > Device Enrollment > Windows Enrollment > Windows Autopilot Deployment Program > Devices** list mean different things and are two completely separate datastores. The former (All devices) is the list of devices currently enrolled into Intune.
|
||||
|
||||
> [!NOTE]
|
||||
> A device will only appear in the All devices list once it has booted. The latter (Windows Autopilot Deployment Program > Devices) is the list of devices currently registered from that Intune account into the Autopilot program - which may or may not be enrolled to Intune.
|
||||
|
||||
To remove the device from the Autopilot program, select the device and click Delete.
|
||||
|
||||
@ -620,7 +628,7 @@ In this example, the computer supports SLAT and Hyper-V.
|
||||
|
||||
> If one or more requirements are evaluated as **No** then the computer does not support installing Hyper-V. However, if only the virtualization setting is incompatible, you might be able to enable virtualization in the BIOS and change the **Virtualization Enabled In Firmware** setting from **No** to **Yes**. The location of this setting will depend on the manufacturer and BIOS version, but is typically found associated with the BIOS security settings.
|
||||
|
||||
You can also identify Hyper-V support using [tools](https://blogs.msdn.microsoft.com/taylorb/2008/06/19/hyper-v-will-my-computer-run-hyper-v-detecting-intel-vt-and-amd-v/) provided by the processor manufacturer, the [msinfo32](https://technet.microsoft.com/library/cc731397.aspx) tool, or you can download the [coreinfo](https://technet.microsoft.com/sysinternals/cc835722) utility and run it, as shown in the following example:
|
||||
You can also identify Hyper-V support using [tools](https://blogs.msdn.microsoft.com/taylorb/2008/06/19/hyper-v-will-my-computer-run-hyper-v-detecting-intel-vt-and-amd-v/) provided by the processor manufacturer, the [msinfo32](https://technet.microsoft.com/library/cc731397.aspx) tool, or you can download the [Coreinfo](https://technet.microsoft.com/sysinternals/cc835722) utility and run it, as shown in the following example:
|
||||
|
||||
<pre style="overflow-y: visible">
|
||||
C:>coreinfo -v
|
||||
@ -637,7 +645,8 @@ VMX * Supports Intel hardware-assisted virtualization
|
||||
EPT * Supports Intel extended page tables (SLAT)
|
||||
</pre>
|
||||
|
||||
Note: A 64-bit operating system is required to run Hyper-V.
|
||||
> [!NOTE]
|
||||
> A 64-bit operating system is required to run Hyper-V.
|
||||
|
||||
## Appendix B: Adding apps to your profile
|
||||
|
||||
@ -645,7 +654,7 @@ Note: A 64-bit operating system is required to run Hyper-V.
|
||||
|
||||
#### Prepare the app for Intune
|
||||
|
||||
Before we can pull an application into Intune to make it part of our AP profile, we need to “package” the application for delivery using the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Intune-Win32-App-Packaging-Tool). After downloading the tool, gather the following three bits of information to use the tool:
|
||||
Before we can pull an application into Intune to make it part of our AP profile, we need to “package” the application for delivery using the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool). After downloading the tool, gather the following three bits of information to use the tool:
|
||||
|
||||
1. The source folder for your application
|
||||
2. The name of the setup executable file
|
||||
@ -686,7 +695,8 @@ On the **Program Configuration** blade, supply the install and uninstall command
|
||||
Install: msiexec /i "npp.7.6.3.installer.x64.msi" /q
|
||||
Uninstall: msiexec /x "{F188A506-C3C6-4411-BE3A-DA5BF1EA6737}" /q
|
||||
|
||||
NOTE: Likely, you do not have to write the install and uninstall commands yourself because the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Intune-Win32-App-Packaging-Tool) automatically generated them when it converted the .msi file into a .intunewin file.
|
||||
> [!NOTE]
|
||||
> Likely, you do not have to write the install and uninstall commands yourself because the [IntuneWinAppUtil.exe command-line tool](https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool) automatically generated them when it converted the .msi file into a .intunewin file.
|
||||
|
||||
|
||||
|
||||
@ -728,7 +738,8 @@ You will be able to find your app in your app list:
|
||||
|
||||
#### Assign the app to your Intune profile
|
||||
|
||||
**NOTE**: The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
|
||||
> [!NOTE]
|
||||
> The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
|
||||
|
||||
In the **Intune > Client Apps > Apps** pane, select the app package you already created to reveal its properties blade. Then click **Assignments** from the menu:
|
||||
|
||||
@ -796,7 +807,8 @@ Click **OK** and then click **Add**.
|
||||
|
||||
#### Assign the app to your Intune profile
|
||||
|
||||
**NOTE**: The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
|
||||
> [!NOTE]
|
||||
> The following steps only work if you previously [created a GROUP in Intune and assigned a profile to it](#assign-the-profile). If you have not done that, please return to the main part of the lab and complete those steps before returning here.
|
||||
|
||||
In the **Intune > Client Apps > Apps** pane, select the Office package you already created to reveal its properties blade. Then click **Assignments** from the menu:
|
||||
|
||||
|
||||
@ -3375,7 +3375,7 @@ This security group has not changed since Windows Server 2008.
|
||||
|
||||
### <a href="" id="bkmk-serveroperators"></a>Server Operators
|
||||
|
||||
Members in the Server Operators group can administer domain servers. This group exists only on domain controllers. By default, the group has no members. Memebers of the Server Operators group can sign in to a server interactively, create and delete network shared resources, start and stop services, back up and restore files, format the hard disk drive of the computer, and shut down the computer. This group cannot be renamed, deleted, or moved.
|
||||
Members in the Server Operators group can administer domain servers. This group exists only on domain controllers. By default, the group has no members. Members of the Server Operators group can sign in to a server interactively, create and delete network shared resources, start and stop services, back up and restore files, format the hard disk drive of the computer, and shut down the computer. This group cannot be renamed, deleted, or moved.
|
||||
|
||||
By default, this built-in group has no members, and it has access to server configuration options on domain controllers. Its membership is controlled by the service administrator groups, Administrators and Domain Admins, in the domain, and the Enterprise Admins group. Members in this group cannot change any administrative group memberships. This is considered a service administrator account because its members have physical access to domain controllers, they can perform maintenance tasks (such as backup and restore), and they have the ability to change binaries that are installed on the domain controllers. Note the default user rights in the following table.
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ ms.reviewer:
|
||||
The Microsoft PIN reset services enables you to help users recover who have forgotten their PIN. Using Group Policy, Microsoft Intune or a compatible MDM, you can configure Windows 10 devices to securely use the Microsoft PIN reset service that enables users to reset their forgotten PIN through settings or above the lock screen without requiring re-enrollment.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> The Microsoft PIN Reset service only works with Windows 10, version 1709 to 1809 with **Enterprise Edition**. The feature works with **Pro** edition with Windows 10, version 1903 and newer.
|
||||
> The Microsoft PIN Reset service only works with **Enterprise Edition** for Windows 10, version 1709 to 1809. The feature works with **Enterprise Edition** and **Pro** edition with Windows 10, version 1903 and newer.
|
||||
|
||||
### Onboarding the Microsoft PIN reset service to your Intune tenant
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ Download the installation and onboarding packages from Microsoft Defender Securi
|
||||
3. Set the deployment method to **Mobile Device Management / Microsoft Intune**.
|
||||
|
||||
>[!NOTE]
|
||||
>JamF falls under **Mobile Device Management**.
|
||||
>Jamf falls under **Mobile Device Management**.
|
||||
|
||||
4. In Section 2 of the page, select **Download installation package**. Save it as _wdav.pkg_ to a local directory.
|
||||
5. In Section 2 of the page, select **Download onboarding package**. Save it as _WindowsDefenderATPOnboardingPackage.zip_ to the same directory.
|
||||
|
||||
@ -62,7 +62,7 @@ In general you need to take the following steps:
|
||||
- [Manual deployment](linux-install-manually.md)
|
||||
- Third-party management tools:
|
||||
- [Deploy using Puppet configuration management tool](linux-install-with-puppet.md)
|
||||
- [Deploy using Ansbile configuration management tool](linux-install-with-ansible.md)
|
||||
- [Deploy using Ansible configuration management tool](linux-install-with-ansible.md)
|
||||
|
||||
### System requirements
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user