mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 22:07:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jd-sandbox
This commit is contained in:
jdeckerMS
commit
c62fb7a5c7
@ -1,2 +1,6 @@
|
||||
# win-cpub-itpro-docs
|
||||
This repo hosts the WDG ITPro content that is published to TechNet.
|
||||
|
||||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
|
||||
|
||||
English Handoff Folder Structure Demo!
|
||||
|
||||
@ -65,25 +65,25 @@ All devices must be enrolled with Intune if you want to use the Windows Custom U
|
||||
|-------------|-------------------|-----------------|--------|
|
||||
|AllowAutofill|Windows 10 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowAutofill</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0.** Employees can’t use Autofill to complete form fields.</li><li>**1 (default).** Employees can use Autofill to complete form fields.</li></ul></li></ul>
|
||||
|AllowBrowser |Windows 10 or later |Mobile |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowBrowser</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0.** Employees can’t use Microsoft Edge.</li><li>**1 (default).** Employees can use Microsoft Edge.</li></ul></li></ul>|
|
||||
|AllowCookies |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowCookies</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Allows all cookies from all sites.</li><li>**1.** Blocks only cookies from 3rd party websites</li><li>**2.** Blocks all cookies from all sites.</li></ul></li></ul> |
|
||||
|AllowDeveloperTools |Windows 10, Version 1511 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowDeveloperTools</li><li>**Data type:** Integer</li><li>**Allowed values:**<ul><li>**0.** Employees can't use the F12 Developer Tools</li><li>**1 (default).** Employees can use the F12 Developer Tools</li></ul></li></ul> |
|
||||
|AllowDoNotTrack |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowDoNotTrack</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Stops employees from sending Do Not Track headers to websites requesting tracking info.</li><li>**1.** Employees can send Do Not Track headers to websites requesting tracking info.</li></ul></li></ul> |
|
||||
|AllowExtensions |Windows 10 Insider Preview |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowExtensions</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0.** Employees can’t use Edge Extensions.</li><li>**1 (default).** Employees can use Edge Extensions.</li></ul></li></ul> |
|
||||
|AllowInPrivate |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowInPrivate</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0.** Employees can’t use InPrivate browsing.</li><li>**1 (default).** Employees can use InPrivate browsing.</li></ul></li></ul> |
|
||||
|AllowPasswordManager |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowPasswordManager</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can't use Password Manager to save passwords locally.</li><li>**1.** Employees can use Password Manager to save passwords locally.</li></ul></li></ul> |
|
||||
|AllowPopups |Windows 10 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowPopups</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Turns off Pop-up Blocker, allowing pop-up windows.</li><li>**1.** Turns on Pop-up Blocker, stopping pop-up windows.</li></ul></li></ul> |
|
||||
|AllowSearchSuggestions<br>inAddressBar |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowSearchSuggestionsinAddressBar/</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can’t see search suggestions in the Address bar of Microsoft Edge.</li><li>**1.** Employees can see search suggestions in the Address bar of Microsoft Edge.</li></ul></li></ul> |
|
||||
|AllowSearchSuggestionsinAddressBar |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowSearchSuggestionsinAddressBar</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can’t see search suggestions in the Address bar of Microsoft Edge.</li><li>**1.** Employees can see search suggestions in the Address bar of Microsoft Edge.</li></ul></li></ul> |
|
||||
|AllowSmartScreen |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/AllowSmartScreen</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Turns off SmartScreen Filter.</li><li>**1.** Turns on SmartScreen Filter, providing warning messages to your employees about potential phishing scams and malicious software.</li></ul></li></ul> |
|
||||
|Cookies |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/Cookies</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Allows all cookies from all sites.</li><li>**1.** Blocks only cookies from 3rd party websites</li><li>**2.** Blocks all cookies from all sites.</li></ul></li></ul> |
|
||||
|EnterpriseModeSiteList |Windows 10 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/EnterpriseModeSiteList</li><li>**Data type.** String</li><li>**Allowed values:**<ul><li>Not configured.</li><li>**1 (default).** Use the Enterprise Mode Site List, if configured.</li><li>**2.** Specify the location to the site list.</li></ul></li></ul> |
|
||||
|Favorites |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/Favorites</li><li>**Data type.** String</li><li>**Allowed values:**<ul><li>Configure the **Favorite** URLs for your employees.<p>**Example:**<br>`<contoso.com>`<br>`<fabrikam.com>`<p>**Note**<br> URLs must be on separate lines and aren't shared between Microsoft Edge and Internet Explorer 11.</li></ul> |
|
||||
|FirstRunURL |Windows 10, Version 1511 or later |Mobile |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/ Browser/FirstRunURL</li><li>**Data type.** String</li><li>**Allowed values:**<ul><li>Configure the first run URL for your employees.<p>**Example:**<br>`<contoso.one>`</li></ul></li></ul> |
|
||||
|FirstRunURL |Windows 10, Version 1511 or later |Mobile |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/FirstRunURL</li><li>**Data type.** String</li><li>**Allowed values:**<ul><li>Configure the first run URL for your employees.<p>**Example:**<br>`<contoso.one>`</li></ul></li></ul> |
|
||||
|HomePages |Windows 10, Version 1511 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/HomePages</li><li>**Data type.** String</li><li>**Allowed values:**<ul><li>Configure the Home page URLs for your employees.<p>**Example:**<br>`<contoso.com/support><fabrikam.com/support>`</li></ul></li></ul> |
|
||||
|PreventAccessToAbout<br>FlagsInMicrosoftEdge |Windows 10 Insider Preview |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventAccessToAboutFlagsInMicrosoftEdge</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can access the about:flags page in Microsoft Edge.</li><li>**1.** Employees can't access the about:flags page in Microsoft Edge.</li></ul></li></ul> |
|
||||
|PreventSmartScreen<br>PromptOverride |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventSmartscreenPromptOverride</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can ignore SmartScreen warnings.</li><li>**1.** Employees can't ignore SmartScreen warnings.</li></ul></li></ul> |
|
||||
|PreventSmartScreen<br>PromptOverrideForFiles |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventSmartScreenPromptOverrideForFiles </li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can ignore SmartScreen warnings for files.</li><li>**1.** Employees can't ignore SmartScreen warnings for files.</li></ul></li></ul> |
|
||||
|PreventUsingLocalHostIP<br>AddressForWebRTC |Windows 10, Version 1511 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventUsingLocalHostIPAddressForWebRTC</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Shows an employee's LocalHost IP address while using the WebRTC protocol.</li><li>**1.** Doesn't show an employee's LocalHost IP address while using the WebRTC protocol.</li></ul></li></ul> |
|
||||
|SendIntranetTraffic<br>toInternetExplorer |Windows 10 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/SendIntranetTraffictoInternetExplorer/</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Automatically opens all websites, including intranet sites, using Microsoft Edge.</li><li>**1.** Automatically opens all intranet sites using Internet Explorer 11.</li></ul></li></ul> |
|
||||
|ShowMessageWhenOpening<br>InteretExplorerSites |Windows 10 Insider Preview |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/ShowMessageWhenOpeningSitesInInteretExplorer</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Doesn’t show an additional page in Microsoft Edge, stating that a site has been opened using Internet Explorer 11.</li><li>**1.** Shows an additional page in Microsoft Edge, stating that a site has been opened using Internet Explorer 11.</li></ul></li></ul> |
|
||||
|PreventAccessToAboutFlagsInMicrosoftEdge |Windows 10 Insider Preview |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventAccessToAboutFlagsInMicrosoftEdge</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can access the about:flags page in Microsoft Edge.</li><li>**1.** Employees can't access the about:flags page in Microsoft Edge.</li></ul></li></ul> |
|
||||
|PreventSmartScreenPromptOverride |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventSmartscreenPromptOverride</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can ignore SmartScreen warnings.</li><li>**1.** Employees can't ignore SmartScreen warnings.</li></ul></li></ul> |
|
||||
|PreventSmartScreenPromptOverrideForFiles |Windows 10, Version 1511 or later |Both |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventSmartScreenPromptOverrideForFiles </li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Employees can ignore SmartScreen warnings for files.</li><li>**1.** Employees can't ignore SmartScreen warnings for files.</li></ul></li></ul> |
|
||||
|PreventUsingLocalHostIPAddressForWebRTC |Windows 10, Version 1511 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/PreventUsingLocalHostIPAddressForWebRTC</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Shows an employee's LocalHost IP address while using the WebRTC protocol.</li><li>**1.** Doesn't show an employee's LocalHost IP address while using the WebRTC protocol.</li></ul></li></ul> |
|
||||
|SendIntranetTraffictoInternetExplorer |Windows 10 or later |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/SendIntranetTraffictoInternetExplorer</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Automatically opens all websites, including intranet sites, using Microsoft Edge.</li><li>**1.** Automatically opens all intranet sites using Internet Explorer 11.</li></ul></li></ul> |
|
||||
|ShowMessageWhenOpeningInteretExplorerSites |Windows 10 Insider Preview |Desktop |<ul><li>**URI full path.** ./Vendor/MSFT/Policy/Config/Browser/ShowMessageWhenOpeningSitesInInteretExplorer</li><li>**Data type.** Integer</li><li>**Allowed values:**<ul><li>**0 (default).** Doesn’t show an additional page in Microsoft Edge, stating that a site has been opened using Internet Explorer 11.</li><li>**1.** Shows an additional page in Microsoft Edge, stating that a site has been opened using Internet Explorer 11.</li></ul></li></ul> |
|
||||
|
||||
## Microsoft Edge and Windows 10-specific Group Policy settings
|
||||
These are additional Windows 10-specific Group Policy settings that work with Microsoft Edge.
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
### [Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
#### [Accessibility](accessibility-surface-hub.md)
|
||||
#### [Change the Surface Hub device account](change-surface-hub-device-account.md)
|
||||
#### [Device reset](device-reset-suface-hub.md)
|
||||
#### [Device reset](device-reset-surface-hub.md)
|
||||
#### [End a Surface Hub meeting with I'm Done](i-am-done-finishing-your-surface-hub-meeting.md)
|
||||
#### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
|
||||
#### [Manage settings with a local admin account](manage-settings-with-local-admin-account-surface-hub.md)
|
||||
|
||||
@ -29,7 +29,7 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
1. Sign in to Office 365 by visiting http://portal.office.com/admin/
|
||||
2. Provide the admin credentials for your Office 365 tenant. This will take you to your Office 365 Admin Center.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Once you are at the Office 365 Admin Center, navigate to **Users** in the left panel, and then click **Active Users**.
|
||||
|
||||
@ -37,13 +37,13 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
4. On the controls above the list of users, click **+** to create a new user. You'll need to enter a **Display name**, **User name**, **Password** and an email address for the recipient of the password. Optionally you can change the password manually, but we recommend that you use the auto-generated option. You also need to assign this account a license that gives the account access to Exchange and Skype for Business services.
|
||||
|
||||
|
||||
|
||||
|
||||
Click **Create**.
|
||||
|
||||
5. Once the account has been successfully created, click **Close** on the resulting dialog box, and you will see the admin center Active Users list again.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Select the user you just created from the **Active Users** list. You need to disable the Skype for Business license, because you can’t create a Skype Meeting Room with this option.
|
||||
|
||||
@ -51,7 +51,7 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
In the right panel you can see the account properties and several optional actions. The process so far has created a regular Skype account for this user, which you need to disable. Click **Edit** for the **Assigned license** section, then click the dropdown arrow next to the license to expand the details.
|
||||
|
||||
|
||||
|
||||
|
||||
From the list, uncheck **Skype for Business Online (plan 2)** (this license may vary depending on your organization), and click **SAVE**.
|
||||
|
||||
@ -59,39 +59,39 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
1. In the Office 365 Admin Center’s left panel, click **ADMIN**, and then click **Exchange**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. This will open another tab on your browser to take you to the Exchange Admin Center, where you can create and set the Mailbox Setting for Surface Hub.
|
||||
|
||||
|
||||
|
||||
|
||||
3. To create a Mobile Device Mailbox Policy, click **Mobile** from the left panel and then click **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
|
||||
|
||||
|
||||
|
||||
|
||||
4. To create a New Surface Hub mobile device mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name, provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). Make sure the policy does not require a password for the devices assigned to, so make sure **Require a Password** remains unchecked, then click **Save**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. After you have created the new mobile device mailbox policy, go back to the **Exchange Admin Center** and you will see the new policy listed.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Now, to apply the ActiveSync policy without using PowerShell, you can do the following: In the EAC, click **Recipients** > **Mailboxes** and then select a mailbox.
|
||||
|
||||
|
||||
|
||||
|
||||
7. In the Details pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
|
||||
|
||||
|
||||
|
||||
|
||||
8. The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
|
||||
|
||||
|
||||
|
||||
|
||||
9. Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
|
||||
|
||||
|
||||
|
||||
|
||||
### <a href="" id="create-device-acct-o365-complete-acct"></a>Use PowerShell to complete device account creation
|
||||
|
||||
@ -107,11 +107,11 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
|
||||
1. Run Windows PowerShell as Administrator.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Create a Credentials object, then create a new session that connects to Skype for Business Online, and provide the global tenant administrator account, then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. To connect to Microsoft Online Services, run:
|
||||
|
||||
@ -119,7 +119,7 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
Connect-MsolService -Credential $Cred
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
4. Now to connect to Skype for Business Online Services, run:
|
||||
|
||||
@ -127,7 +127,7 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
$sfbsession = New-CsOnlineSession -Credential $cred
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
5. Finally, to connect to Exchange Online Services, run:
|
||||
|
||||
@ -136,7 +136,7 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
"https://outlook.office365.com/powershell-liveid/" -Credential $cred -Authentication "Basic" –AllowRedirection
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
6. Now you have to import the Skype for Business Online Session and the Exchange Online session you have just created, which will import the Exchange and Skype Commands so you can use them locally.
|
||||
|
||||
@ -147,7 +147,7 @@ In order to run cmdlets used by these PowerShell scripts, the following must be
|
||||
|
||||
Note that this could take a while to complete.
|
||||
|
||||
|
||||
|
||||
|
||||
7. Once you’re connected to the online services you need to run a few more cmdlets to configure this account as a Surface Hub device account.
|
||||
|
||||
@ -180,11 +180,11 @@ Now that you're connected to the online services, you can finish setting up the
|
||||
|
||||
You will see the correct email address.
|
||||
|
||||
|
||||
|
||||
|
||||
2. You need to convert the account into to a room mailbox, so run:
|
||||
|
||||
|
||||
|
||||
|
||||
``` syntax
|
||||
Set-Mailbox $strEmail -Type Room
|
||||
@ -196,7 +196,7 @@ Now that you're connected to the online services, you can finish setting up the
|
||||
Set-Mailbox $strEmail -RoomMailboxPassword (ConvertTo-SecureString -String "<your password>" -AsPlainText -Force) -EnableRoomMailboxAccount $true
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
4. Various Exchange properties can be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
|
||||
|
||||
@ -205,7 +205,7 @@ Now that you're connected to the online services, you can finish setting up the
|
||||
Set-CalendarProcessing -Identity $acctUpn -AddAdditionalResponse $true -AdditionalResponse "This is a <tla rid="surface_hub"/> room!"
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
5. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
|
||||
|
||||
@ -260,11 +260,11 @@ You can use the Exchange Admin Center to create a device account:
|
||||
1. Sign in to your Exchange Admin Center using Exchange admin credentials.
|
||||
2. Once you are at the Exchange Admin Center (EAC), navigate to **Recipients** in the left panel.
|
||||
|
||||
|
||||
|
||||
|
||||
3. On the controls above the list of mailboxess, choose **+** to create a new one, and provide a **Display name**, **Name**, and **User logon name**, and then click **Save**.
|
||||
|
||||
|
||||
|
||||
|
||||
### <a href="" id="create-device-acct-exch-mbx-policy"></a>Create a mobile device mailbox policy from the Exchange Admin Center
|
||||
|
||||
@ -274,37 +274,37 @@ You can use the Exchange Admin Center to create a device account:
|
||||
|
||||
1. Go to the Exchange Admin Center.
|
||||
|
||||
|
||||
|
||||
|
||||
2. To create a mobile device mailbox policy, click **Mobile** from the left panel, then **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
|
||||
|
||||
|
||||
|
||||
|
||||
3. To create a new mobile device account mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). The policy must not be password-protected, so make sure **Require a Password** remains unchecked, then click **Save**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. After you have created the new mobile device mailbox policy, go back to the Exchange Admin Center and you will see the new policy listed.
|
||||
|
||||
|
||||
|
||||
|
||||
5. To apply the ActiveSync policy without using PowerShell, you can do the following:
|
||||
|
||||
- In the EAC, click **Recipients** > **Mailboxes** and select a mailbox.
|
||||
|
||||
|
||||
|
||||
|
||||
- In the **Details** pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
|
||||
|
||||
|
||||
|
||||
|
||||
- The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
|
||||
|
||||
|
||||
|
||||
|
||||
- Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
|
||||
|
||||
|
||||
|
||||
|
||||
### <a href="" id="create-device-acct-exch-powershell-conf"></a>Use PowerShell to configure the account
|
||||
|
||||
|
||||
@ -116,7 +116,7 @@ You can check online for updated versions at [Surface Hub device account scripts
|
||||
|
||||
Your infrastructure will likely fall into one of three configurations. Which configuration you have will affect how you prepare for device setup.
|
||||
|
||||
|
||||
|
||||
|
||||
- [Online deployment (Office 365)](online-deployment-surface-hub-device-accounts.md): Your organization’s environment is deployed entirely on Office 365.
|
||||
- [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md): Your organization has servers that it controls, where Active Directory, Exchange, and Skype for Business (or Lync) are hosted.
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Device reset (Surface Hub)
|
||||
description: You may wish to reset your Microsoft Surface Hub.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
redirect_url: https://technet.microsoft.com/en-us/itpro/surface-hub/device-reset-surface-hub
|
||||
keywords: reset Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -27,7 +28,10 @@ Initiating a reset will return the device to the last cumulative Windows update,
|
||||
- MDM enrollment
|
||||
- Domain join or Azure AD join information
|
||||
- Local admins on the device
|
||||
- Configurations from MDM or the Settings app.
|
||||
- Configurations from MDM or the Settings app
|
||||
|
||||
**Important Note**</br>
|
||||
Performing a device reset may take up to 6 hours. Do not interrupt the reset process. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
|
||||
After the reset, you'll be taken through the [first run program](first-run-program-surface-hub.md) again.
|
||||
|
||||
|
||||
47
devices/surface-hub/device-reset-surface-hub.md
Normal file
47
devices/surface-hub/device-reset-surface-hub.md
Normal file
@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Device reset (Surface Hub)
|
||||
description: You may wish to reset your Microsoft Surface Hub.
|
||||
ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
|
||||
keywords: reset Surface Hub
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: TrudyHa
|
||||
---
|
||||
|
||||
# Device reset (Surface Hub)
|
||||
|
||||
|
||||
You may wish to reset your Microsoft Surface Hub.
|
||||
|
||||
Typical reasons for a reset include:
|
||||
|
||||
- The device isn’t running well after installing an update.
|
||||
- You’re repurposing the device for a new meeting space and want to reconfigure it.
|
||||
- You want to change how you locally manage the device.
|
||||
|
||||
Initiating a reset will return the device to the last cumulative Windows update, and remove all local user files and configuration, including:
|
||||
|
||||
- The device account
|
||||
- MDM enrollment
|
||||
- Domain join or Azure AD join information
|
||||
- Local admins on the device
|
||||
- Configurations from MDM or the Settings app
|
||||
|
||||
**To reset a Surface Hub**
|
||||
1. On your Surface Hub, open **Settings**.
|
||||
2. Click **Update & Security**.
|
||||
3. Click **Recovery**, and then click **Reset Device**.
|
||||
|
||||
**Important Note**</br>
|
||||
Performing a device reset may take up to 6 hours. Do not interrupt the reset process. Interrupting the process will render the device inoperable, requiring warranty service to return to normal functionality.
|
||||
|
||||
After the reset, Surface Hub restarts the [first run program](first-run-program-surface-hub.md) again.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Manage Microsoft Surface Hub](manage-surface-hub.md)
|
||||
|
||||
[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
|
||||
@ -46,7 +46,7 @@ This is the first screen you'll see when you power up the Surface Hub for the fi
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -72,7 +72,7 @@ If no wired connection can be found, then the device will attempt to set up a wi
|
||||
|
||||
If your device does not detect a wired connection that it can use to connect to a network or the Internet, you will see this page. Here you can either connect to a wireless network, or skip making the network connection.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -97,7 +97,7 @@ If you want to connect to a secured wireless network from this page, click on th
|
||||
|
||||
This page will be shown when you've selected a secured wireless network.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -121,11 +121,11 @@ This page will be shown when the device detects a wired connection with limited
|
||||
|
||||
- You can select **Enter proxy settings** which will allow you to specify how to use the network proxy. You'll be taken to the next screen.
|
||||
|
||||
|
||||
|
||||
|
||||
This is the screen you'll see if you clicked **Enter proxy settings** on the previous screen.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -149,7 +149,7 @@ You can skip connecting to a network by selecting **Skip this step**. You'll be
|
||||
|
||||
This screen is purely informational, and shows which recommended settings have been enabled by default.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -170,7 +170,7 @@ On this page, the Surface Hub will ask for credentials for the device account th
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -192,7 +192,7 @@ If you skip setting it up now, you can add a device account later by using the S
|
||||
|
||||
If you click **Skip setting up a device account**, the device will display a dialog box showing what will happen if the device doesn't have a device account. If you choose **Yes, skip this**, you will be sent to the [Name this device page](#name-this-device).
|
||||
|
||||
|
||||
|
||||
|
||||
### What happens?
|
||||
|
||||
@ -211,7 +211,7 @@ The device will use the UPN or DOMAIN\\User name and password for the device acc
|
||||
|
||||
This page will only be shown if there's a problem. Typically, it means that the device account that you provided was found in Active Directory (AD) or Azure Active Directory (Azure AD), but the Exchange server for the account was not discovered.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -230,7 +230,7 @@ You can enable Exchange services for a device account later by using the Setting
|
||||
|
||||
If you click **Skip setting up Exchange services**, the device will display a dialog showing what will happen. If you choose **Yes, skip this**, then Exchange services will not be set up.
|
||||
|
||||
|
||||
|
||||
|
||||
### What happens?
|
||||
|
||||
@ -249,7 +249,7 @@ This page will be shown when:
|
||||
- Exchange supported protocols are not supported by the Surface Hub.
|
||||
- Exchange returns incorrect XML.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -273,7 +273,7 @@ If you choose to skip this check, the Surface Hub will stop looking for the Exch
|
||||
|
||||
This page asks you to provide two names that will be used for identifying the Surface Hub.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -307,7 +307,7 @@ Because every Surface Hub can be used by any number of authenticated employees,
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -348,7 +348,7 @@ Joining Azure AD has two primary benefits:
|
||||
1. Some employees from your organization will be able to access the device as admins, and will be able to start the Settings app and configure the device. People that have admin permissions will be defined in your Azure AD subscription.
|
||||
2. If your Azure AD is connected to a mobile device management (MDM) solution, the device will enroll with that MDM solution so you can apply policies and configuration.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -357,11 +357,11 @@ The following input is required:
|
||||
- **User's UPN:** The user principal name (UPN) of an account that can join Azure AD.
|
||||
- **Password:** The password of the account you’re using to join Azure AD.
|
||||
|
||||
|
||||
|
||||
|
||||
If you get to this point and don't have valid credentials for an Azure AD account, the device will allow you to continue by creating a local admin account. Click **Set up Windows with a local account instead**.
|
||||
|
||||
|
||||
|
||||
|
||||
### What happens?
|
||||
|
||||
@ -373,7 +373,7 @@ This page will ask for credentials to join a domain so that the Surface Hub can
|
||||
|
||||
Once the device has been domain joined, you must specify a security group from the domain you joined. This security group will be provisioned as administrators on the Surface Hub, and anyone from the security group can enter their domain credentials to access Settings.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
@ -385,7 +385,7 @@ The following input is required:
|
||||
|
||||
After the credentials are verified, you will be asked to type a security group name. This input is required.
|
||||
|
||||
|
||||
|
||||
|
||||
### What happens?
|
||||
|
||||
@ -401,7 +401,7 @@ If the join is successful, you'll see the **Enter a security group** page. When
|
||||
|
||||
If you decide not to use Azure Active Directory (Azure AD) or Active Directory (AD) to manage the Surface Hub, you'll need to create a local admin account.
|
||||
|
||||
|
||||
|
||||
|
||||
### Details
|
||||
|
||||
|
||||
@ -21,17 +21,17 @@ Use this procedure if you use Exchange on-prem.
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.<p>
|
||||
|
||||
|
||||
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
>**Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
|
||||
- Click **Finish** to create the account.
|
||||
|
||||
|
||||
|
||||
|
||||
2. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Office 365 admin center and verify that the account created in the previous steps has merged to online.
|
||||
|
||||
@ -223,17 +223,17 @@ Use this procedure if you use Exchange online.
|
||||
- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
|
||||
- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
|
||||
|
||||
>**Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
|
||||
|
||||
|
||||
|
||||
|
||||
- Click **Finish** to create the account.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Directory synchronization.
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Install apps on your Microsoft Surface Hub
|
||||
description: Admins can install apps can from either the Windows Store or the Windows Store for Business.
|
||||
ms.assetid: 3885CB45-D496-4424-8533-C9E3D0EDFD94
|
||||
keywords: [install apps, Windows Store, Windows Store for Business
|
||||
keywords: install apps, Windows Store, Windows Store for Business
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
|
||||
@ -37,7 +37,7 @@ The capabilities of your Surface Hub will depend on what other Microsoft product
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Meetings using Skype for Business</p></td>
|
||||
<td align="left"><p>Device account with Skype for Business (Lync 2010 or later) or Skype for Business Online, and a network connection so the account can be accessed.</p></td>
|
||||
<td align="left"><p>Device account with Skype for Business (Lync Server 2013 or later) or Skype for Business Online, and a network connection so the account can be accessed.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Web browsing through Microsoft Edge</p></td>
|
||||
|
||||
@ -30,7 +30,7 @@ If you joined your Surface Hub to an Azure Active Directory (Azure AD) subscript
|
||||
|
||||
Alternatively, the device can be enrolled like any other Windows device by going to **Settings** > **Accounts** > **Work access**.
|
||||
|
||||
|
||||
|
||||
|
||||
### Manage a device through MDM
|
||||
|
||||
|
||||
@ -29,7 +29,7 @@ In order to function properly, the Surface Hub must have access to a wired or wi
|
||||
- Can receive an IP address using DHCP
|
||||
- Open ports:
|
||||
- HTTPS: 443
|
||||
- HTTP: 8080
|
||||
- HTTP: 80
|
||||
|
||||
A wired connection is preferred.
|
||||
|
||||
@ -79,7 +79,7 @@ In order to ensure that your environment is ready for the Surface Hub, verify th
|
||||
- It must have these ports open:
|
||||
|
||||
- HTTPS: 443
|
||||
- HTTP: 8080
|
||||
- HTTP: 80
|
||||
|
||||
If your network runs through a proxy, you'll need the proxy address or script information as well.
|
||||
|
||||
|
||||
@ -58,9 +58,7 @@ In order to create and deploy provisioning packages, all of the following are re
|
||||
### <a href="" id="installing-wicd-prov-pkg"></a>Install the Windows Imaging and Configuration Designer
|
||||
|
||||
1. The Windows Imaging and Configuration Designer (ICD) is installed as part of the Windows 10 ADK. The installer for the ADK can be downloaded from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?LinkId=718147).
|
||||
>**Note** The ADK must be installed on a separate PC, not on the Surface Hub.
|
||||
|
||||
|
||||
>**Note** The ADK must be installed on a separate PC, not on the Surface Hub.
|
||||
|
||||
2. Run the installer, and set your preferences for installation. When asked what features you want to install, you will see a checklist like the one in the following figure. Note that **Windows Performance Toolkit** and **Windows Assessment Toolkit** should be unchecked, as they are not needed to run the ICD.
|
||||
|
||||
@ -73,7 +71,7 @@ In order to create and deploy provisioning packages, all of the following are re
|
||||
|
||||
All four of these features are required to run the ICD and create a package for the Surfact Hub.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Continue with the installer until the ADK is installed. This may take a while, because the installer downloads remote content.
|
||||
|
||||
@ -83,29 +81,29 @@ This example will demonstrate how to create a provisioning package to install a
|
||||
|
||||
1. On the PC that had the Windows 10 ADK installed, open ICD and choose the **New provisioning package** tile from the main menu.
|
||||
|
||||
|
||||
|
||||
|
||||
2. When the **New project** dialog box opens, type whatever name you like in the **Name** box. The **Location** and **Description** boxes can also be filled at your discretion, though we recommend using the **Description** box to help you distinguish among multiple packages. Click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
Select the settings that are **Common to all Windows editions**, and click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
When asked to import a provisioning package, just click **Finish.**
|
||||
|
||||
|
||||
|
||||
|
||||
3. ICD's main screen will be displayed. This is where you create the provisioning package. In the **Available customizations** pane, expand **Runtime settings** and then expand **Certificates**. Click **Root certificates**.
|
||||
|
||||
|
||||
|
||||
|
||||
In the center pane, you’ll be asked to specify a **CertificateName** for the Root certificate. You can set this to whatever you want. For the example, we've used the same name as the project. Click **Add**, and an entry will be added in the left pane.
|
||||
|
||||
4. In the **Available customizations** pane on the left, a new category has appeared for **CertificatePath** underneath the **CertificateName** you provided. There’s also a red exclamation icon indicating that there is a required field that needs to be set. Click **CeritficatePath**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. In the center pane, you’ll be asked to specify the path for the certificate. Enter the name of the .cer file that you want to deploy, either by typing or clicking **Browse**. It must be a root certificate. The provisioning package created will copy the .cer file into the package it creates.
|
||||
|
||||
@ -238,15 +236,15 @@ The following two methods for deploying provisioning packages apply to any kind
|
||||
3. Navigate to **System > Work Access**. Under the header **Related settings**, click on **Add or remove a management package**.
|
||||
4. Here, click the button for **Add a package**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Click **Removable media** from the dropdown list. You will see a list of available provisioning packages on the **Settings** page.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Choose your package and click **Add**.
|
||||
|
||||
|
||||
|
||||
|
||||
7. You may have to re-enter the admin credentials if User Access Control (UAC) asks for them.
|
||||
8. You’ll see a confirmation dialog box. Click **Yes, add it**. The certificate will be installed.
|
||||
|
||||
@ -43,7 +43,7 @@ Possible fixes for issues on the Surface Hub after you've completed the first-ru
|
||||
<p>The device account isn't configured to automatically accept/decline messages.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>Use PowerShell<code>cmdlet Set-CalendarProcessing $upn -AutomateProcessing AutoAccept</code>.</p>
|
||||
<p>Use PowerShell cmdlet <code>Set-CalendarProcessing $upn -AutomateProcessing AutoAccept</code>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -291,7 +291,7 @@ Possible fixes for issues with Surface Hub first-run program.
|
||||
</tr>
|
||||
<tr>
|
||||
<td rowspan="3">
|
||||
<div class="alert"><b>Note</b> <p class="note">People land on the page titled "There's a problem with this account" regarding ActiveSync.</p>
|
||||
<div><p>People land on the page titled "There's a problem with this account" regarding ActiveSync.</p>
|
||||
</div>
|
||||
<div> </div>
|
||||
</td>
|
||||
@ -456,7 +456,7 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Status Code</th>
|
||||
<th align="left">Hex Code</th>
|
||||
<th align="left">Mapping</th>
|
||||
<th align="left">User-Friendly Message</th>
|
||||
<th align="left">Action admin should take</th>
|
||||
@ -464,149 +464,148 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063532030</p></td>
|
||||
<td align="left"><p>0x85010002</p></td>
|
||||
<td align="left"><p>E_HTTP_DENIED</p></td>
|
||||
<td align="left"><p>The password must be updated.</p></td>
|
||||
<td align="left"><p>Update the password.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2147012867</p></td>
|
||||
<td align="left"><p>0x80072EFD</p></td>
|
||||
<td align="left"><p>WININET_E_CANNOT_CONNECT</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now. Wait a while and try again, or check the account settings.</p></td>
|
||||
<td align="left"><p>Verify that the server name is correct and reachable. Verify that the device is connected to the network.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2046817239</p></td>
|
||||
<td align="left"><p>0x86000C29</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_DEVICE_NOTPROVISIONED (policies don’t match)</p></td>
|
||||
<td align="left"><p>The account is configured with policies not compatible with Surface Hub</p>
|
||||
.</td>
|
||||
<td align="left"><p>The account is configured with policies not compatible with Surface Hub.</p></td>
|
||||
<td align="left"><p>Disable the <strong>PasswordEnabled</strong> policy for this account.</p>
|
||||
<p>We have a bug were we may surface policy errors if the account doesn’t receive any server notifications within the policy refresh interval.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2046817204</p></td>
|
||||
<td align="left"><p>0x86000C4C</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_MAXIMUMDEVICESREACHED</p></td>
|
||||
<td align="left"><p>The account has too many device partnerships.</p></td>
|
||||
<td align="left"><p>Delete one or more partnerships on the server.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2046817270</p></td>
|
||||
<td align="left"><p>0x86000C0A</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_SERVERERROR_RETRYLATER</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now.</p></td>
|
||||
<td align="left"><p>Wait until the server comes back online. If the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2063269885</p></td>
|
||||
<td align="left"><p>0x85050003</p></td>
|
||||
<td align="left"><p>E_CREDENTIALS_EXPIRED (Credentials have expired and need to be updated)</p></td>
|
||||
<td align="left"><p>The password must be updated.</p></td>
|
||||
<td align="left"><p>Update the password.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063269875</p></td>
|
||||
<td align="left"><p>0x8505000D</p></td>
|
||||
<td align="left"><p>E_AIRSYNC_RESET_RETRY</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now. Wait a while or check the account’s settings.</p></td>
|
||||
<td align="left"><p>This is normally a transient error but if the issue persists check the number of devices associated with the account and delete some of them if the number is large.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2046817258</p></td>
|
||||
<td align="left"><p>0x86000C16</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_USER_HASNOMAILBOX</p></td>
|
||||
<td align="left"><p>The mailbox was migrated to a different server.</p></td>
|
||||
<td align="left"><p>You should never see this error. If the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063532028</p></td>
|
||||
<td align="left"><p>0x85010004</p></td>
|
||||
<td align="left"><p>E_HTTP_FORBIDDEN</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now. Wait a while and try again, or check the account’s settings.</p></td>
|
||||
<td align="left"><p>Verify the server name to make sure it is correct. If the account is using cert based authentication make sure the certificate is still valid and update it if not.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2063400920</p></td>
|
||||
<td align="left"><p>0x85030028</p></td>
|
||||
<td align="left"><p>E_ACTIVESYNC_PASSWORD_OR_GETCERT</p></td>
|
||||
<td align="left"><p>The account’s password or client certificate are missing or invalid.</p></td>
|
||||
<td align="left"><p>Update the password and/or deploy the client certificate.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2046817238</p></td>
|
||||
<td align="left"><p>0x86000C2A</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_DEVICE_POLICYREFRESH</p></td>
|
||||
<td align="left"><p>The account is configured with policies not compatible with Surface Hub.</p></td>
|
||||
<td align="left"><p>Disable the PasswordEnabled policy for this account.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2063269886</p></td>
|
||||
<td align="left"><p>0x85050002</p></td>
|
||||
<td align="left"><p>E_CREDENTIALS_UNAVAILABLE</p></td>
|
||||
<td align="left"><p>The password must be updated.</p></td>
|
||||
<td align="left"><p>Update the password.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2147012894</p></td>
|
||||
<td align="left"><p>0x80072EE2</p></td>
|
||||
<td align="left"><p>WININET_E_TIMEOUT</p></td>
|
||||
<td align="left"><p>The network doesn’t support the minimum idle timeout required to receive server notification, or the server is offline.</p></td>
|
||||
<td align="left"><p>Verify that the server is running. Verify the NAT settings.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2063589372</p></td>
|
||||
<td align="left"><p>0x85002004</p></td>
|
||||
<td align="left"><p>E_FAIL_ABORT</p></td>
|
||||
<td align="left"><p>This error is used to interrupt the hanging sync, and will not be exposed to users. It will be shown in the telemetry if you force an interactive sync, delete the account, or update its settings.</p></td>
|
||||
<td align="left"><p>Nothing.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063532009</p></td>
|
||||
<td align="left"><p>0x85010017</p></td>
|
||||
<td align="left"><p>E_HTTP_SERVICE_UNAVAIL</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now. Wait a while or check the account’s settings.</p></td>
|
||||
<td align="left"><p>Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2046817267</p></td>
|
||||
<td align="left"><p>0x86000C0D</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_MAILBOX_SERVEROFFLINE</p></td>
|
||||
<td align="left"><p>Can’t connect to the server right now. Wait a while or check the account’s settings.</p></td>
|
||||
<td align="left"><p>Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063400921</p></td>
|
||||
<td align="left"><p>0x85030027</p></td>
|
||||
<td align="left"><p>E_ACTIVESYNC_GETCERT</p></td>
|
||||
<td align="left"><p>The Exchange server requires a certificate.</p></td>
|
||||
<td align="left"><p>Import the appropriate EAS certificate on the Surface Hub.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2046817237</p></td>
|
||||
<td align="left"><p>0x86000C2B</p></td>
|
||||
<td align="left"><p>E_NEXUS_STATUS_INVALID_POLICYKEY</p></td>
|
||||
<td align="left"><p>The account is configured with policies not compatible with Surface Hub.</p></td>
|
||||
<td align="left"><p>Disable the PasswordEnabled policy for this account.</p>
|
||||
<p>We have a bug were we may surface policy errors if the account doesn’t receive any server notifications within the policy refresh interval.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>-2063532027</p></td>
|
||||
<td align="left"><p>0x85010005</p></td>
|
||||
<td align="left"><p>E_HTTP_NOT_FOUND</p></td>
|
||||
<td align="left"><p>The server name is invalid.</p></td>
|
||||
<td align="left"><p>Verify the server name to make sure it is correct. If the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>-2063532012</p></td>
|
||||
<td align="left"><p>0x85010014</p></td>
|
||||
<td align="left"><p>E_HTTP_SERVER_ERROR</p></td>
|
||||
<td align="left"><p>Can’t connect to the server.</p></td>
|
||||
<td align="left"><p>Verify the server name to make sure it is correct. Trigger a sync and, if the issue persists, re-provision the account.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>0x80072ee7</p></td>
|
||||
<td align="left"></td>
|
||||
<td align="left"><p>0x80072EE7</p></td>
|
||||
<td align="left"><p>WININET_E_NAME_NOT_RESOLVED</p></td>
|
||||
<td align="left"><p>The server name or address could not be resolved.</p></td>
|
||||
<td align="left"><p>Make sure the server name is entered correctly.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>0x8007052f</p></td>
|
||||
<td align="left"></td>
|
||||
<td align="left"><p>0x8007052F</p></td>
|
||||
<td align="left"><p>ERROR_ACCOUNT_RESTRICTION</p></td>
|
||||
<td align="left"><p>While auto-discovering the Exchange server, a policy is applied that prevents the logged-in user from logging in to the server.</p></td>
|
||||
<td align="left"><p>This is a timing issue. Re-verify the account's credentials. Try to re-provision when they're correct.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>0x800c0019</p></td>
|
||||
<td align="left"></td>
|
||||
<td align="left"><p>0x800C0019</p></td>
|
||||
<td align="left"><p>INET_E_INVALID_CERTIFICATE</p></td>
|
||||
<td align="left"><p>Security certificate required to access this resource is invalid.</p></td>
|
||||
<td align="left"><p>Install the correct ActiveSync certificate needed for the provided device account.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>0x80072f0d</p></td>
|
||||
<td align="left"></td>
|
||||
<td align="left"><p>0x80072F0D</p></td>
|
||||
<td align="left"><p>WININET_E_INVALID_CA</p></td>
|
||||
<td align="left"><p>The certificate authority is invalid or is incorrect. Could not auto-discover the Exchange server because a certificate is missing.</p></td>
|
||||
<td align="left"><p>Install the correct ActiveSync certificate needed for the provided device account.</p></td>
|
||||
</tr>
|
||||
@ -616,12 +615,6 @@ This section lists status codes, mapping, user messages, and actions an admin ca
|
||||
<td align="left"><p>The domain provided couldn't be found. The Exchange server could not be auto-discovered and was not provided in the settings.</p></td>
|
||||
<td align="left"><p>Make sure that the domain entered is the FQDN, and that there is an Exchange server entered in the Exchange server text box.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>0x80072efd</p></td>
|
||||
<td align="left"></td>
|
||||
<td align="left"><p>Fail to connect to Exchange server as a result of a networking issue. It's possible the server was misspelled or it just couldn't be found.</p></td>
|
||||
<td align="left"><p>Make sure that the Exchange server ID is entered correctly, and that the device is connected to the right network.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
@ -68,7 +68,7 @@ You can use a standard RJ-11 (6P6C) connector to connect the Surface Hub serial
|
||||
|
||||
This diagram shows the correct pinout used for an RJ-11 (6P6C) to DB9 cable.
|
||||
|
||||
|
||||
|
||||
|
||||
## Command sets
|
||||
|
||||
|
||||
@ -25,33 +25,33 @@ If a wired network connection is not available, the Surface Hub can use a wirele
|
||||
1. On the Surface Hub, open **Settings** and enter your admin credentials.
|
||||
2. Click **System**, and then click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. If the network is secured, you'll be asked to enter the security key. Click **Next** to connect.
|
||||
|
||||
|
||||
|
||||
|
||||
### Review wireless settings
|
||||
|
||||
1. On the Surface Hub, open **Settings** and enter your admin credentials.
|
||||
2. Click **System**, click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. The system will show you the properties for the wireless network connection.
|
||||
|
||||
|
||||
|
||||
|
||||
### Review wired settings
|
||||
|
||||
1. On the Surface Hub, open **Settings** and enter your admin credentials.
|
||||
2. Click **System**, click **Network & Internet**, then click on the network under Ethernet.
|
||||
|
||||
|
||||
|
||||
|
||||
3. The system will show you the properties for the wired network connection.
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
# [Surface](index.md)
|
||||
## [Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)
|
||||
## [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
|
||||
## [Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md)
|
||||
## [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
## [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)
|
||||
## [Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)
|
||||
@ -12,4 +13,7 @@
|
||||
### [Step by step: Surface Deployment Accelerator](step-by-step-surface-deployment-accelerator.md)
|
||||
## [Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)
|
||||
## [Surface Dock Updater](surface-dock-updater.md)
|
||||
## [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
|
||||
### [Enroll and configure Surface devices with SEMM](enroll-and-configure-surface-devices-with-semm.md)
|
||||
### [Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
|
||||
|
||||
|
||||
@ -0,0 +1,145 @@
|
||||
---
|
||||
title: Deploy Surface app with Windows Store for Business (Surface)
|
||||
description: Find out how to add and download Surface app with Windows Store for Business, as well as install Surface app with PowerShell and MDT.
|
||||
keywords: surface app, app, deployment, customize
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: surface, store
|
||||
ms.sitesec: library
|
||||
author: miladCA
|
||||
---
|
||||
|
||||
#Deploy Surface app with Windows Store for Business
|
||||
|
||||
The Surface app is a lightweight Windows Store app that provides control of many Surface-specific settings and options, including:
|
||||
|
||||
* Enable or disable the Windows button on the Surface device
|
||||
|
||||
* Adjust the sensitivity of a Surface Pen
|
||||
|
||||
* Customize Surface Pen button actions
|
||||
|
||||
* Enable or disable Surface audio enhancements
|
||||
|
||||
* Quick access to support documentation and information for your device
|
||||
|
||||
If your organization is preparing images that will be deployed to your Surface devices, you may want to include the Surface app (formerly called the Surface Hub) in your imaging and deployment process instead of requiring users of each individual device to download and install the app from the Windows Store or your Windows Store for Business.
|
||||
|
||||
####Surface app overview
|
||||
|
||||
The Surface app is available as a free download from the [Windows Store](https://www.microsoft.com/en-us/store/apps/Surface/9WZDNCRFJB8P). Users can download and install it from the Windows Store, but if your organization uses Windows Store for Business instead, you will need to add it to your store’s inventory and possibly include the app as part of your Windows deployment process. These processes are discussed throughout this article. For more information about Windows Store for Business, see [Windows Store for Business](https://technet.microsoft.com/en-us/windows/store-for-business) in the Windows TechCenter.
|
||||
|
||||
##Add Surface app to a Windows Store for Business account
|
||||
|
||||
Before users can install or deploy an app from a company’s Windows Store for Business account, the desired app(s) must first be made available and licensed to the users of a business.
|
||||
|
||||
1. If you have not already done so, create a [Windows Store for Business account](https://www.microsoft.com/en-us/business-store).
|
||||
|
||||
2. Log on to the portal.
|
||||
|
||||
3. Enable offline licensing: click **Settings->Account Information**, and then select the **Show offline licensed apps to people shopping in the store** checkbox, as shown in Figure 1. For more information about Windows Store for Business app licensing models, see [Apps in Windows Store for Business](https://technet.microsoft.com/itpro/windows/manage/apps-in-windows-store-for-business#licensing_model).<br/> <br/>
|
||||
<br/>
|
||||
*Figure 1. Enable apps for offline use*
|
||||
|
||||
4. Add Surface app to your Windows Store for Business account by following this procedure:
|
||||
* Click the **Shop** menu.
|
||||
* In the search box, type **Surface app**, and then click the search icon.
|
||||
* After the Surface app is presented in the search results, click the app’s icon.
|
||||
* You are presented with a choice (select **Online** or **Offline**), as shown in Figure 2.<br/><br/>
|
||||
|
||||
|
||||
|
||||
*Figure 2. Select the Offline licensing mode and add the app to your inventory*
|
||||
|
||||
* Click **Offline** to select the Offline licensing mode.
|
||||
* Click **Get the app** to add the app to your Windows Store for Business inventory. As shown in Figure 3, you’ll see a dialog box that prompts you to acknowledge that offline apps can be deployed using a management tool or downloaded from the company’s inventory page in their private store.
|
||||
|
||||
|
||||
|
||||
*Figure 3. Offline-licensed app acknowledgement*
|
||||
* Click **OK**.
|
||||
|
||||
##Download Surface app from a Windows Store for Business account
|
||||
After you add an app to the Windows Store for Business account in Offline mode, you can download and add the app as an AppxBundle to a deployment share.
|
||||
1. Log on to the Windows Store for Business account at https://businessstore.microsoft.com.
|
||||
2. Click the **Manage->Inventory** menu. A list of all apps in your company’s private store is displayed, including the Surface app you added in the [Add Surface app to a Windows Store for Business account](#add-surface-app-to-a-windows-store-for-business-account) section of this article.
|
||||
3. Under **Actions**, click the ellipsis (**…**), and then click **Download for offline use** for the Surface app.
|
||||
4. Select the desired **Platform** and **Architecture** options from the available selections for the selected app, as shown in Figure 4.
|
||||
|
||||
|
||||
|
||||
*Figure 4. Download the AppxBundle package for an app*
|
||||
5. Click **Download**. The AppxBundle package will be downloaded. Make sure you note the path of the downloaded file because you’ll need that later in this article.
|
||||
6. Click either the **Encoded license** or **Unencoded license** option. Use the Encoded license option with management tools like System Center Configuration Manager or when you use Windows Imaging and Configuration Designer (Windows ICD). Select the Unencoded license option when you use Deployment Image Servicing and Management (DISM) or deployment solutions based on imaging, including the Microsoft Deployment Toolkit (MDT).
|
||||
7. Click **Generate** to generate and download the license for the app. Make sure you note the path of the license file because you’ll need that later in this article.
|
||||
|
||||
>**Note:** When you download an app for offline use, such as the Surface app, you may notice a section at the bottom of the page labeled **Required frameworks**. Your target computers must have the frameworks installed for the app to run, so you may need to repeat the download process for each of the required frameworks for your architecture (either x86 or x64) and also include them as part of your Windows deployment discussed later in this article.
|
||||
|
||||
Figure 5 shows the required frameworks for the Surface app.
|
||||
|
||||
|
||||
|
||||
*Figure 5. Required frameworks for the Surface app*
|
||||
|
||||
To download the required frameworks for the Surface app, follow these steps:
|
||||
1. Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
2. Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
|
||||
|
||||
>**Note:** Only the 64-bit (x64) version of each framework is required for Surface devices. Surface devices are native 64-bit UEFI devices and are not compatible with 32-bit (x86) versions of Windows that would require 32-bit frameworks.
|
||||
|
||||
##Install Surface app on your computer with PowerShell
|
||||
The following procedure provisions the Surface app onto your computer and makes it available for any user accounts created on the computer afterwards.
|
||||
1. Using the procedure described in the [How to download Surface app from a Windows Store for Business account](#how-to-download-surface-app-from-a-windows-store-for-business-account) section of this article, download the Surface app AppxBundle and license file.
|
||||
2. Begin an elevated PowerShell session.
|
||||
>**Note:** If you don’t run PowerShell as an Administrator, the session won’t have the required permissions to install the app.
|
||||
3. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –PackagePath <DownloadPath>\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath <DownloadPath>\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
|
||||
```
|
||||
|
||||
Where `<DownloadPath>` is the folder where you downloaded the AppxBundle and license file from the Windows Store for Business account.
|
||||
|
||||
For example, if you downloaded the files to c:\Temp, the command you run is:
|
||||
````
|
||||
Add-AppxProvisionedPackage –Online –PackagePath c:\Temp\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath c:\Temp\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
|
||||
```
|
||||
|
||||
4. The Surface app will now be available on your current Windows computer.
|
||||
Before the Surface app is functional on the computer where it has been provisioned, you must also provision the frameworks described earlier in this article. To provision these frameworks, use the following procedure in the elevated PowerShell session you used to provision the Surface app.
|
||||
5. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath <DownloadPath>\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx
|
||||
```
|
||||
6. In the elevated PowerShell session, copy and paste the following command:
|
||||
```
|
||||
Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath <DownloadPath>\Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx
|
||||
```
|
||||
|
||||
##Install Surface app with MDT
|
||||
The following procedure uses MDT to automate installation of the Surface app at the time of deployment. The application is provisioned automatically by MDT during deployment and thus you can use this process with existing images. This is the recommended process to deploy the Surface app as part of a Windows deployment to Surface devices because it does not reduce the cross platform compatibility of the Windows image.
|
||||
1. Using the procedure described [earlier in this article](#how-to-download-surface-app-from-a-windows-store-for-business-account), download the Surface app AppxBundle and license file.
|
||||
2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
|
||||
3. On the **Command Details** page of the New Application Wizard, specify the default **Working Directory** and for the **Command** specify the file name of the AppxBundle, as follows:
|
||||
|
||||
* Command:
|
||||
```
|
||||
Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle
|
||||
```
|
||||
* Working Directory: %DEPLOYROOT%\Applications\SurfaceApp
|
||||
|
||||
For the Surface app to function on the target computer, it will also require the frameworks described earlier in this article. Use the following procedure to import the frameworks required for the Surface app into MDT and to configure them as dependencies.
|
||||
1. Using the procedure described earlier in this article, download the framework files. Store each framework in a separate folder.
|
||||
2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
|
||||
3. On the **Command Details** page, type the file name of each application you downloaded in the **Command** field and the default Working Directory.
|
||||
|
||||
To configure the frameworks as dependencies of the Surface app, use this process:
|
||||
1. Open the properties of the Surface app in the MDT Deployment Workbench.
|
||||
2. Click the **Dependencies** tab, and then click **Add**.
|
||||
3. Select the check box for each framework using the name you provided in the New Application Wizard.
|
||||
|
||||
After import, the Surface app will be available for selection in the **Applications** step of the Windows Deployment Wizard. You can also install the application automatically by specifying the application in the deployment task sequence by following this process:
|
||||
1. Open your deployment task sequence in the MDT Deployment Workbench.
|
||||
2. Add a new **Install Application** task in the **State Restore** section of deployment.
|
||||
3. Select **Install a single application** and specify the **Surface App** as the **Application to be installed**.
|
||||
|
||||
For more information about including apps into your Windows deployments, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit).
|
||||
@ -0,0 +1,135 @@
|
||||
---
|
||||
title: Enroll and configure Surface devices with SEMM (Surface)
|
||||
description: Learn how to create a Surface UEFI configuration package to control the settings of Surface UEFI, as well as enroll a Surface device in SEMM.
|
||||
keywords: surface enterprise management
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
---
|
||||
|
||||
# Enroll and configure Surface devices with SEMM
|
||||
|
||||
With Microsoft Surface Enterprise Management Mode (SEMM), you can securely configure the settings of Surface UEFI on a Surface device and manage those settings on Surface devices in your organization. When a Surface device is managed by SEMM, that device is considered to be *enrolled* (sometimes referred to as activated). This article shows you how to create a Surface UEFI configuration package that will not only control the settings of Surface UEFI, but will also enroll a Surface device in SEMM.
|
||||
|
||||
For a more high-level overview of SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
#### Download and install Microsoft Surface UEFI Configurator
|
||||
The tool used to create SEMM packages is Microsoft Surface UEFI Configurator. You can download Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/en-us/download/details.aspx?id=46703) page in the Microsoft Download Center.
|
||||
Run the Microsoft Surface UEFI Configurator Windows Installer (.msi) file to start the installation of the tool. When the installer completes, find Microsoft Surface UEFI Configurator in the All Apps section of your Start menu.
|
||||
|
||||
>**Note**: Microsoft Surface UEFI Configurator is supported only on Windows 10.
|
||||
|
||||
## Create a Surface UEFI configuration package
|
||||
|
||||
The Surface UEFI configuration package performs both the role of applying a new configuration of Surface UEFI settings to a Surface device managed with SEMM and the role of enrolling Surface devices in SEMM. The creation of a configuration package requires you to have a signing certificate to be used with SEMM to secure the configuration of UEFI settings on each Surface device. For more information about the requirements for the SEMM certificate, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
To create a Surface UEFI configuration package, follow these steps:
|
||||
|
||||
1. Open Microsoft Surface UEFI Configurator from the Start menu.
|
||||
2. Click **Start**.
|
||||
3. Click **Configuration Package**, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Select Configuration Package to create a package for SEMM enrollment and configuration*
|
||||
|
||||
4. Click **Certificate Protection** to add your exported certificate file with private key (.pfx), as shown in Figure 2. Browse to the location of your certificate file, select the file, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
*Figure 2. Add the SEMM certificate and Surface UEFI password to a Surface UEFI configuration package*
|
||||
|
||||
5. When you are prompted to confirm the certificate password, enter and confirm the password for your certificate file, and then click **OK**.
|
||||
6. Click **Password Protection** to add a password to Surface UEFI. This password will be required whenever you boot to UEFI. If this password is not entered, only the **PC information**, **About**, **Enterprise management**, and **Exit** pages will be displayed. This step is optional.
|
||||
7. When you are prompted, enter and confirm your chosen password for Surface UEFI, and then click **OK**. If you want to clear an existing Surface UEFI password, leave the password field blank.
|
||||
8. If you do not want the Surface UEFI package to apply to a particular device, on the **Choose which Surface type you want to target** page, click the slider beneath the corresponding Surface Book or Surface Pro 4 image so that it is in the **Off** position. (As shown in Figure 3.)
|
||||
|
||||
|
||||
|
||||
*Figure 3. Choose the devices for package compatibility*
|
||||
|
||||
9. Click **Next**.
|
||||
10. If you want to deactivate a component on managed Surface devices, on the **Choose which components you want to activate or deactivate** page, click the slider next to any device or group of devices you want to deactivate so that the slider is in the **Off** position. (Shown in Figure 4.) The default configuration for each device is **On**. Click the **Reset** button if you want to return all sliders to the default position.
|
||||
|
||||
|
||||
|
||||
*Figure 4. Disable or enable individual Surface components*
|
||||
|
||||
11. Click **Next**.
|
||||
12. To enable or disable advanced options in Surface UEFI or the display of Surface UEFI pages, on the **Choose the advanced settings for your devices** page, click the slider beside the desired setting to configure that option to **On** or **Off** (shown in Figure 5). In the **UEFI Front Page** section, you can use the sliders for **Security**, **Devices**, and **Boot** to control what pages are available to users who boot into Surface UEFI. (For more information about Surface UEFI settings, see [Manage Surface UEFI settings](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-uefi-settings).) Click **Build** when you have finished selecting options to generate and save the package.
|
||||
|
||||
|
||||
|
||||
*Figure 5. Control advanced Surface UEFI settings and Surface UEFI pages with SEMM*
|
||||
|
||||
13. In the **Save As** dialog box, specify a name for the Surface UEFI configuration package, browse to the location where you would like to save the file, and then click **Save**.
|
||||
14. When the package is created and saved, the **Successful** page is displayed.
|
||||
|
||||
>**Note**: Record the certificate thumbprint characters that are displayed on this page, as shown in Figure 6. You will need these characters to confirm enrollment of new Surface devices in SEMM. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
|
||||
|
||||
|
||||
|
||||
*Figure 6. The last two characters of the certificate thumbprint are displayed on the Successful page*
|
||||
|
||||
Now that you have created your Surface UEFI configuration package, you can enroll or configure Surface devices.
|
||||
|
||||
>**Note**: When a Surface UEFI configuration package is created, a log file is created on the desktop with details of the configuration package settings and options.
|
||||
|
||||
## Enroll a Surface device in SEMM
|
||||
When the Surface UEFI configuration package is executed, the SEMM certificate and Surface UEFI configuration files are staged in the firmware storage of the Surface device. When the Surface device reboots, Surface UEFI processes these files and begins the process of applying the Surface UEFI configuration or enrolling the Surface device in SEMM, as shown in Figure 7.
|
||||
|
||||
|
||||
|
||||
*Figure 7. The SEMM process for configuration of Surface UEFI or enrollment of a Surface device*
|
||||
|
||||
Before you begin the process to enroll a Surface device in SEMM, ensure that you have the last two characters of the certificate thumbprint on hand. You will need these characters to confirm the device’s enrollment (see Figure 6).
|
||||
|
||||
To enroll a Surface device in SEMM with a Surface UEFI configuration package, follow these steps:
|
||||
|
||||
1. Run the Surface UEFI configuration package .msi file on the Surface device you want to enroll in SEMM. This will provision the Surface UEFI configuration file in the device’s firmware.
|
||||
2. Select the **I accept the terms in the License Agreement** check box to accept the End User License Agreement (EULA), and then click **Install** to begin the installation process.
|
||||
3. Click **Finish** to complete the Surface UEFI configuration package installation and restart the Surface device when you are prompted to do so.
|
||||
4. Surface UEFI will load the configuration file and determine that SEMM is not enabled on the device. Surface UEFI will then begin the SEMM enrollment process, as follows:
|
||||
* Surface UEFI will verify that the SEMM configuration file contains a SEMM certificate.
|
||||
* Surface UEFI will prompt you to enter to enter the last two characters of the certificate thumbprint to confirm enrollment of the Surface device in SEMM, as shown in Figure 8.
|
||||
|
||||
|
||||
|
||||
*Figure 8. Enrollment in SEMM requires the last two characters of the certificate thumbprint*
|
||||
|
||||
* Surface UEFI will store the SEMM certificate in firmware and apply the configuration settings that are specified in the Surface UEFI configuration file.
|
||||
|
||||
5. The Surface device is now enrolled in SEMM and will boot to Windows.
|
||||
|
||||
You can verify that a Surface device has been successfully enrolled in SEMM by looking for **Microsoft Surface Configuration Package** in **Programs and Features** (as shown in Figure 9), or in the events stored in the **Microsoft Surface UEFI Configurator** log, found under **Applications and Services Logs** in Event Viewer (as shown in Figure 10).
|
||||
|
||||
|
||||
|
||||
*Figure 9. Verify the enrollment of a Surface device in SEMM in Programs and Features*
|
||||
|
||||
|
||||
|
||||
*Figure 10. Verify the enrollment of a Surface device in SEMM in Event Viewer*
|
||||
|
||||
You can also verify that the device is enrolled in SEMM in Surface UEFI – while the device is enrolled, Surface UEFI will contain the **Enterprise management** page (as shown in Figure 11).
|
||||
|
||||
|
||||
|
||||
*Figure 11. The Surface UEFI Enterprise management page*
|
||||
|
||||
|
||||
## Configure Surface UEFI settings with SEMM
|
||||
|
||||
After a device is enrolled in SEMM, you can run Surface UEFI configuration packages signed with the same SEMM certificate to apply new Surface UEFI settings. These settings are applied automatically the next time the device boots, without any interaction from the user. You can use application deployment solutions like System Center Configuration Manager to deploy Surface UEFI configuration packages to Surface devices to change or manage the settings in Surface UEFI.
|
||||
|
||||
For more information about how to deploy Windows Installer (.msi) files with Configuration Manager, see [Deploy and manage applications with System Center Configuration Manager](https://technet.microsoft.com/library/mt627959).
|
||||
|
||||
If you have secured Surface UEFI with a password, users without the password who attempt to boot to Surface UEFI will only have the **PC information**, **About**, **Enterprise management**, and **Exit** pages displayed to them.
|
||||
|
||||
If you have not secured Surface UEFI with a password or a user enters the password correctly, settings that are configured with SEMM will be dimmed (unavailable) and the text Some settings are managed by your organization will be displayed at the top of the page, as shown in Figure 12.
|
||||
|
||||
|
||||
|
||||
*Figure 12. Settings managed by SEMM will be disabled in Surface UEFI*
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 106 KiB |
BIN
devices/surface/images/deploysurfapp-fig3-acknowledge.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig3-acknowledge.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
BIN
devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 79 KiB |
BIN
devices/surface/images/deploysurfapp-fig5-requiredframework.png
Normal file
BIN
devices/surface/images/deploysurfapp-fig5-requiredframework.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
BIN
devices/surface/images/deploysurfapp-figure1-enablingapps.png
Normal file
BIN
devices/surface/images/deploysurfapp-figure1-enablingapps.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB After Width: | Height: | Size: 98 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 68 KiB After Width: | Height: | Size: 103 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 96 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-diagnostic-kit-fig1-options.png
Normal file
BIN
devices/surface/images/surface-diagnostic-kit-fig1-options.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
devices/surface/images/surface-diagnostic-kit-fig2-testdepth.png
Normal file
BIN
devices/surface/images/surface-diagnostic-kit-fig2-testdepth.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
BIN
devices/surface/images/surface-diagnostic-kit-fig3-results.png
Normal file
BIN
devices/surface/images/surface-diagnostic-kit-fig3-results.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 111 KiB |
BIN
devices/surface/images/surface-diagnostic-kit-fig4-notes.png
Normal file
BIN
devices/surface/images/surface-diagnostic-kit-fig4-notes.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
BIN
devices/surface/images/surface-diagnostic-kit-gear-icon.png
Normal file
BIN
devices/surface/images/surface-diagnostic-kit-gear-icon.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 567 B |
BIN
devices/surface/images/surface-enroll-semm-fig1.png
Normal file
BIN
devices/surface/images/surface-enroll-semm-fig1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 87 KiB |
BIN
devices/surface/images/surface-ent-mgmt-fig2-securepackage.png
Normal file
BIN
devices/surface/images/surface-ent-mgmt-fig2-securepackage.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
BIN
devices/surface/images/surface-ent-mgmt-fig3-enabledisable.png
Normal file
BIN
devices/surface/images/surface-ent-mgmt-fig3-enabledisable.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
BIN
devices/surface/images/surface-ent-mgmt-fig5-success.png
Normal file
BIN
devices/surface/images/surface-ent-mgmt-fig5-success.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
BIN
devices/surface/images/surface-ent-mgmt-fig6-enrollconfirm.png
Normal file
BIN
devices/surface/images/surface-ent-mgmt-fig6-enrollconfirm.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 218 KiB |
BIN
devices/surface/images/surface-ent-mgmt-fig7-semmrecovery.png
Normal file
BIN
devices/surface/images/surface-ent-mgmt-fig7-semmrecovery.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 138 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig1.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig10.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig10.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 128 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig11.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig11.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 108 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig12.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig12.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 65 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig3.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 126 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig4.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig5.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig5.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 110 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig6.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig6.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 112 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig7.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig7.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig8.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig8.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
BIN
devices/surface/images/surface-semm-enroll-fig9.png
Normal file
BIN
devices/surface/images/surface-semm-enroll-fig9.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 66 KiB |
BIN
devices/surface/images/surface-semm-enrollment-fig2.png
Normal file
BIN
devices/surface/images/surface-semm-enrollment-fig2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 112 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig1.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig10.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig10.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 87 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig11.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig11.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig12.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig12.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 170 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig13.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig13.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig14.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig14.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 60 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig2.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig3.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig4.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig5.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig5.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 66 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig6.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig6.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 108 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig7.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig7.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig8.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig8.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 276 KiB |
BIN
devices/surface/images/surface-semm-unenroll-fig9.png
Normal file
BIN
devices/surface/images/surface-semm-unenroll-fig9.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 133 KiB |
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Surface (Surface)
|
||||
description: .
|
||||
description:
|
||||
ms.assetid: 2a6aec85-b8e2-4784-8dc1-194ed5126a04
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -43,45 +43,54 @@ For more information on planning for, deploying, and managing Surface devices in
|
||||
<td><p>Walk through the process of customizing the Surface out-of-box experience for end users in your organization.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p>[Deploy Surface app with Windows Store for Business](deploy-surface-app-with-windows-store-for-business.md)</p></td>
|
||||
<td><p>Find out how to add and download Surface app with Windows Store for Business, as well as install Surface app with PowerShell and MDT.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>[Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)</p></td>
|
||||
<td><p>Get a list of the available downloads for Surface devices and links to download the drivers and firmware for your device.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)</p></td>
|
||||
<td><p>Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)</p></td>
|
||||
<td><p>Get guidance and answers to help you perform a network deployment to Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)</p></td>
|
||||
<td><p>Read about the different methods you can use to manage the process of Surface Dock firmware updates.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)</p></td>
|
||||
<td><p>Explore the available options to manage firmware and driver updates for Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Manage Surface UEFI settings](manage-surface-uefi-settings.md)<p></td>
|
||||
<td><p>Use Surface UEFI settings to enable or disable devices, configure security settings, and adjust Surface device boot settings.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Data Eraser](microsoft-surface-data-eraser.md)</p></td>
|
||||
<td><p>Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)</p></td>
|
||||
<td><p>See how Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)</p></td>
|
||||
<td><p>Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Dock Updater](surface-dock-updater.md)</p></td>
|
||||
<td><p>Get a detailed walkthrough of Microsoft Surface Dock Updater.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Enterprise Management Mode](surface-enterprise-management-mode.md)</p></td>
|
||||
<td><p>See how this feature of Surface devices with Surface UEFI allows you to secure and manage firmware settings within your organization.
|
||||
</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ The Surface Dock firmware update process shown in Figure 1 follows these steps:
|
||||
|
||||
8. When the Surface Dock is disconnected for a second time, the Surface dock installs the firmware update to the DisplayPort chipset. This process takes up to 3 minutes to apply.
|
||||
|
||||
|
||||
|
||||
|
||||
*1- Driver installation can be performed by Windows Update, manual installation, or automatically downloaded with Microsoft Surface Dock Updater*
|
||||
|
||||
|
||||
@ -39,9 +39,9 @@ You will also find detailed information about the firmware of your Surface devic
|
||||
|
||||
- Touch Firmware
|
||||
|
||||
*Figure 1. System information and firmware version information*
|
||||
|
||||
|
||||
|
||||
*Figure 1. System information and firmware version information*
|
||||
|
||||
You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/en-us/support/install-update-activate/surface-update-history) for your device.
|
||||
|
||||
@ -59,21 +59,21 @@ On the **Security** page of Surface UEFI settings, you can set a password to pro
|
||||
|
||||
The password must be at least 6 characters and is case sensitive.
|
||||
|
||||
*Figure 2. Add a password to protect Surface UEFI settings*
|
||||
|
||||
|
||||
|
||||
*Figure 2. Add a password to protect Surface UEFI settings*
|
||||
|
||||
On the **Security** page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 3. Read more about [Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview) in the TechNet Library.
|
||||
|
||||
*Figure 3. Configure Secure Boot*
|
||||
|
||||
|
||||
|
||||
*Figure 3. Configure Secure Boot*
|
||||
|
||||
You can also enable or disable the Trusted Platform Module (TPM) device on the **Security** page, as shown in Figure 4. The TPM is used to authenticate encryption for your device’s data with BitLocker. Read more about [BitLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/bitlocker-overview) in the TechNet Library.
|
||||
|
||||
*Figure 4. Configure Surface UEFI security settings*
|
||||
|
||||
|
||||
|
||||
*Figure 4. Configure Surface UEFI security settings*
|
||||
|
||||
##Devices
|
||||
|
||||
@ -95,9 +95,9 @@ On the **Devices** page you can enable or disable specific devices and component
|
||||
|
||||
Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 5.
|
||||
|
||||
*Figure 5. Enable and disable specific devices*
|
||||
|
||||
|
||||
|
||||
*Figure 5. Enable and disable specific devices*
|
||||
|
||||
##Boot configuration
|
||||
|
||||
@ -115,9 +115,9 @@ You can boot from a specific device immediately, or you can swipe left on that d
|
||||
|
||||
For the specified boot order to take effect, you must set the **Enable Alternate Boot Sequence** option to **On**, as shown in Figure 6.
|
||||
|
||||
*Figure 6. Configure the boot order for your Surface device*
|
||||
|
||||
|
||||
|
||||
*Figure 6. Configure the boot order for your Surface device*
|
||||
|
||||
You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE Network Boot** option, for example when performing a Windows deployment using PXE where the PXE server is configured for IPv4 only.
|
||||
|
||||
@ -125,14 +125,14 @@ You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE
|
||||
|
||||
The **About** page displays regulatory information, such as compliance with FCC rules, as shown in Figure 7.
|
||||
|
||||
*Figure 7. Regulatory information is displayed on the About page*
|
||||
|
||||
|
||||
|
||||
*Figure 7. Regulatory information displayed on the About page*
|
||||
|
||||
##Exit
|
||||
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 8.
|
||||
|
||||
*Figure 8. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
|
||||
|
||||
|
||||
*Figure 8. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
|
||||
@ -65,24 +65,24 @@ After the creation tool is installed, follow these steps to create a Microsoft S
|
||||
|
||||
3. Click **Start** to acknowledge that you have a USB stick of at least 4 GB connected, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 1. Start the Microsoft Surface Data Eraser tool
|
||||
*Figure 1. Start the Microsoft Surface Data Eraser tool*
|
||||
|
||||
4. Select the USB drive of your choice from the **USB Thumb Drive Selection** page as shown in Figure 2, and then click **Start** to begin the USB creation process. The drive you select will be formatted and any existing data on this drive will be lost.
|
||||
>**Note:** If the Start button is disabled, check that your removable drive has a total capacity of at least 4 GB.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 2. USB thumb drive selection
|
||||
*Figure 2. USB thumb drive selection*
|
||||
|
||||
5. After the creation process is finished, the USB drive has been formatted and all binaries are copied to the USB drive. Click **Success**.
|
||||
|
||||
6. When the **Congratulations** screen is displayed, you can eject and remove the thumb drive. This thumb drive is now ready to be inserted into a Surface device, booted from, and wipe any data on the device. Click **Complete** to finish the USB creation process, as shown in Figure 3.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 3. Complete the Microsoft Surface Data Eraser USB creation process
|
||||
*Figure 3. Complete the Microsoft Surface Data Eraser USB creation process*
|
||||
|
||||
7. Click **X** to close Microsoft Surface Data Eraser.
|
||||
|
||||
@ -105,9 +105,9 @@ After you create a Microsoft Surface Data Eraser USB stick, you can boot a suppo
|
||||
|
||||
3. When the Surface device boots, a **SoftwareLicenseTerms** text file is displayed.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 4. Booting the Microsoft Surface Data Eraser USB stick
|
||||
*Figure 4. Booting the Microsoft Surface Data Eraser USB stick*
|
||||
|
||||
4. Read the software license terms, and then close the notepad file.
|
||||
|
||||
@ -123,9 +123,9 @@ After you create a Microsoft Surface Data Eraser USB stick, you can boot a suppo
|
||||
|
||||
7. If you typed **S** to begin the data erase process, the partition that will be erased is displayed, as shown in Figure 5. If this is correct, press **Y** to continue, or **N** to shut down the device.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 5. Partition to be erased is displayed in Microsoft Surface Data Eraser
|
||||
*Figure 5. Partition to be erased is displayed in Microsoft Surface Data Eraser*
|
||||
|
||||
8. If you pressed **Y** in step 7, due to the destructive nature of the data erasure process, an additional dialog box is displayed to confirm your choice.
|
||||
|
||||
|
||||
@ -13,17 +13,17 @@ author: miladCA
|
||||
# Microsoft Surface Deployment Accelerator
|
||||
|
||||
|
||||
Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.
|
||||
Microsoft Surface Deployment Accelerator (SDA) provides a quick and simple deployment mechanism for organizations to reimage Surface devices.
|
||||
|
||||
Microsoft Surface Deployment Accelerator includes a wizard that automates the creation and configuration of a Microsoft recommended deployment experience by using free Microsoft deployment tools. The resulting deployment solution is complete with everything you need to immediately begin the deployment of Windows to a Surface device. You can also use Microsoft Surface Deployment Accelerator to create and capture a Windows reference image and then deploy it with the latest Windows Updates.
|
||||
SDA includes a wizard that automates the creation and configuration of a Microsoft recommended deployment experience by using free Microsoft deployment tools. The resulting deployment solution is complete with everything you need to immediately begin the deployment of Windows to a Surface device. You can also use SDA to create and capture a Windows reference image and then deploy it with the latest Windows updates.
|
||||
|
||||
Microsoft Surface Deployment Accelerator is built on the powerful suite of deployment tools available from Microsoft including the Windows Assessment and Deployment Kit (ADK), the Microsoft Deployment Toolkit (MDT), and Windows Deployment Services (WDS). The resulting deployment share encompasses the recommended best practices for managing drivers during deployment and automating image creation and can serve as a starting point upon which you build your own customized deployment solution.
|
||||
SDA is built on the powerful suite of deployment tools available from Microsoft including the Windows Assessment and Deployment Kit (ADK), the Microsoft Deployment Toolkit (MDT), and Windows Deployment Services (WDS). The resulting deployment share encompasses the recommended best practices for managing drivers during deployment and automating image creation and can serve as a starting point upon which you build your own customized deployment solution.
|
||||
|
||||
You can find more information about how to deploy to Surface devices, including step-by-step walkthroughs of customized deployment solution implementation, on the Deploy page of the [Surface TechCenter](http://go.microsoft.com/fwlink/p/?LinkId=691693).
|
||||
|
||||
**Download Microsoft Surface Deployment Accelerator**
|
||||
|
||||
You can download the installation files for Microsoft Surface Deployment Accelerator from the Microsoft Download Center. To download the installation files:
|
||||
You can download the installation files for SDA from the Microsoft Download Center. To download the installation files:
|
||||
|
||||
1. Go to the [Surface Tools for IT](http://go.microsoft.com/fwlink/p/?LinkId=618121) page on the Microsoft Download Center.
|
||||
|
||||
@ -32,9 +32,9 @@ You can download the installation files for Microsoft Surface Deployment Acceler
|
||||
## Microsoft Surface Deployment Accelerator prerequisites
|
||||
|
||||
|
||||
Before you install Microsoft Surface Deployment Accelerator, your environment must meet the following prerequisites:
|
||||
Before you install SDA, your environment must meet the following prerequisites:
|
||||
|
||||
- Microsoft Surface Deployment Accelerator must be installed on Windows Server 2012 R2 or later
|
||||
- SDA must be installed on Windows Server 2012 R2 or later
|
||||
|
||||
- PowerShell Script Execution Policy must be set to **Unrestricted**
|
||||
|
||||
@ -44,45 +44,74 @@ Before you install Microsoft Surface Deployment Accelerator, your environment mu
|
||||
|
||||
- To support network boot, the Windows Server 2012 R2 environment must have Windows Deployment Services installed and configured to respond to PXE requests
|
||||
|
||||
- Access to Windows source files or installation media is required when you prepare a deployment with Microsoft Surface Deployment Accelerator
|
||||
- Access to Windows source files or installation media is required when you prepare a deployment with SDA
|
||||
|
||||
- At least 6 GB of free space for each version of Windows you intend to deploy
|
||||
|
||||
## How Microsoft Surface Deployment Accelerator works
|
||||
|
||||
|
||||
As you progress through the Microsoft Surface Deployment Accelerator wizard, you will be asked some basic questions about how your deployment solution should be configured. As you select the desired Surface models to be supported and apps to be installed (see Figure 1), the wizard will prepare scripts that download, install, and configure everything needed to perform a complete deployment and capture of a reference image. By using the network boot (PXE) capabilities of Windows Deployment Services (WDS), the resulting solution enables you to boot a Surface device from the network and perform a clean deployment of Windows.
|
||||
As you progress through the SDA wizard, you will be asked some basic questions about how your deployment solution should be configured. As you select the desired Surface models to be supported and apps to be installed (see Figure 1), the wizard will prepare scripts that download, install, and configure everything needed to perform a complete deployment and capture of a reference image. By using the network boot (PXE) capabilities of Windows Deployment Services (WDS), the resulting solution enables you to boot a Surface device from the network and perform a clean deployment of Windows.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 1: Select desired apps and drivers
|
||||
*Figure 1. Select desired apps and drivers*
|
||||
|
||||
When the Microsoft Surface Deployment Accelerator completes, you can use the deployment share to deploy over the network immediately. Simply boot your Surface device from the network using a Surface Ethernet Adapter and select the Surface deployment share you created with the Microsoft Surface Deployment Accelerator wizard. Select the **1- Deploy Microsoft Surface** task sequence and the wizard will walk you through an automated deployment of Windows to your Surface device.
|
||||
When the SDA completes, you can use the deployment share to deploy over the network immediately. Simply boot your Surface device from the network using a Surface Ethernet Adapter and select the Surface deployment share you created with the SDA wizard. Select the **1- Deploy Microsoft Surface** task sequence and the wizard will walk you through an automated deployment of Windows to your Surface device.
|
||||
|
||||
You can modify the task sequence in the MDT Deployment Workbench to [include your own apps](http://go.microsoft.com/fwlink/p/?linkid=691700), or to [pause the automated installation routine](http://go.microsoft.com/fwlink/p/?linkid=691701). While the installation is paused, you can make changes to customize your reference image. After the image is captured, you can configure a deployment task sequence and distribute this custom configuration by using the same network boot capabilities as before.
|
||||
|
||||
>**Note:** With Microsoft Surface Deployment Accelerator v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment.
|
||||
>**Note:** With SDA v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="use-microsoft-surface-deployment-accelerator-without-an-internet-connection--"></a>Use Microsoft Surface Deployment Accelerator without an Internet connection
|
||||
|
||||
|
||||
For environments where the Microsoft Surface Deployment Accelerator server will not be able to connect to the Internet, the required Surface files can be downloaded separately. To specify a local source for Surface driver and app files, select the **Copy from a local directory** option and specify the location of your downloaded files (see Figure 2). All of the driver and app files for your selected choices must be placed in the specified folder.
|
||||
For environments where the SDA server will not be able to connect to the Internet, the required Surface files can be downloaded separately. To specify a local source for Surface driver and app files, select the **Copy from a local directory** option and specify the location of your downloaded files (see Figure 2). All of the driver and app files for your selected choices must be placed in the specified folder.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 2. Specify a local source for Surface driver and app files
|
||||
*Figure 2. Specify a local source for Surface driver and app files*
|
||||
|
||||
You can find a full list of available driver downloads at [Download the latest firmware and drivers for Surface devices](deploy-the-latest-firmware-and-drivers-for-surface-devices.md)
|
||||
|
||||
>**Note:** Downloaded files do not need to be extracted. The downloaded files can be left as .zip files as long as they are stored in one folder.
|
||||
|
||||
>**Note:** Using files from a local directory is not supported when including Office 365 in your deployment share. To include Office 365 in your deployment share, select the **Download from the Internet** check box.
|
||||
|
||||
## Changes and updates
|
||||
|
||||
SDA is periodically updated by Microsoft. For instructions on how these features are used, see [Step-by-Step: Microsoft Surface Deployment Accelerator](https://technet.microsoft.com/en-us/itpro/surface/step-by-step-surface-deployment-accelerator).
|
||||
|
||||
>**Note:** To install a newer version of SDA on a server with a previous version of SDA installed, you only need to run the installation file for the new version of SDA. The installer will handle the upgrade process automatically. If you used SDA to create a deployment share prior to the upgrade and want to use new features of the new version of SDA, you will need to create a new deployment share. SDA does not support upgrades of an existing deployment share.
|
||||
|
||||
### Version 1.96.0405
|
||||
This version of SDA adds support for the following:
|
||||
* Microsoft Deployment Toolkit (MDT) 2013 Update 2
|
||||
* Office 365 Click-to-Run
|
||||
* Surface 3 and Surface 3 LTE
|
||||
* Reduced Windows Assessment and Deployment Kit (Windows ADK) footprint, only the following Windows ADK components are installed:
|
||||
* Deployment tools
|
||||
* Windows Preinstallation Environment (WinPE)
|
||||
* User State Migration Tool (USMT)
|
||||
|
||||
|
||||
### Version 1.90.0258
|
||||
This version of SDA adds support for the following:
|
||||
* Surface Book
|
||||
* Surface Pro 4
|
||||
* Windows 10
|
||||
|
||||
|
||||
### Version 1.90.0000
|
||||
This version of SDA adds support for the following:
|
||||
* Local driver and app files can be used to create a deployment share without access to the Internet
|
||||
|
||||
### Version 1.70.0000
|
||||
This version is the original release of SDA. This version of SDA includes support for:
|
||||
* MDT 2013 Update 1
|
||||
* Windows ADK
|
||||
* Surface Pro 3
|
||||
* Windows 8.1
|
||||
|
||||
|
||||
|
||||
|
||||
@ -26,17 +26,17 @@ For information about prerequisites and instructions for how to download and ins
|
||||
|
||||
3. Accept the End User License Agreement (EULA) by selecting the check box, and then click **Install**, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 1. SDA setup
|
||||
*Figure 1. SDA setup*
|
||||
|
||||
4. Click **Finish** to complete the installation of SDA.
|
||||
|
||||
The tool installs in the Surface Deployment Accelerator program group, as shown in Figure 2.
|
||||
The tool installs in the SDA program group, as shown in Figure 2.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 2. The Surface Deployment Accelerator program group and icon
|
||||
*Figure 2. The SDA program group and icon*
|
||||
|
||||
>**Note:** At this point the tool has not yet prepared any deployment environment or downloaded any materials from the Internet.
|
||||
|
||||
@ -45,7 +45,7 @@ Figure 2. The Surface Deployment Accelerator program group and icon
|
||||
## Create a deployment share
|
||||
|
||||
|
||||
The following steps show how you create a deployment share for Windows 10 that supports Surface Pro 3, Surface Pro 4, Surface Book, the Surface Firmware Tool, and the Surface Asset Tag Tool. As you follow the steps below, make the selections that are applicable for your organization. For example, you could choose to deploy Windows 10 to Surface Book only, without any of the Surface apps.
|
||||
The following steps show you how to create a deployment share for Windows 10 that supports Surface 3, Surface Pro 3, Surface Pro 4, Surface Book, the Surface Firmware Tool, the Surface Asset Tag Tool, and Office 365. As you follow the steps below, make the selections that are applicable for your organization. For example, you could choose to deploy Windows 10 to Surface Book only, without any of the Surface apps.
|
||||
|
||||
>**Note:** SDA lets you create deployment shares for both Windows 8.1 and Windows 10 deployments, but you can only create a single deployment share at a time. Therefore, to create both Windows 8.1 and Windows 10 deployment shares, you will need to run the tool twice.
|
||||
|
||||
@ -55,7 +55,14 @@ The following steps show how you create a deployment share for Windows 10 that
|
||||
|
||||
2. On the **Welcome** page, click **Next** to continue.
|
||||
|
||||
3. On the **Verify System** page, the SDA wizard verifies the prerequisites required for an SDA deployment share. This process also checks for the presence of the Windows Assessment and Deployment Kit (ADK) for Windows 10 and the Microsoft Deployment Toolkit (MDT) 2013 Update 1. If these tools are not detected, they are downloaded and installed automatically. Click **Next** to continue.
|
||||
3. On the **Verify System** page, the SDA wizard verifies the prerequisites required for an SDA deployment share. This process also checks for the presence of the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10 and the Microsoft Deployment Toolkit (MDT) 2013 Update 2. If these tools are not detected, they are downloaded and installed automatically. Click **Next** to continue.
|
||||
|
||||
>**Note:** As of SDA version 1.96.0405, SDA will install only the components of the Windows ADK that are required for deployment, as follows:
|
||||
* Deployment tools
|
||||
* User State Migration Tool (USMT)
|
||||
* Windows Preinstallation Environment (WinPE)</br></br>
|
||||
|
||||
>**Note:** As of SDA version 1.96.0405, SDA will install and use MDT 2013 Update 2. Earlier versions of SDA are compatible only with MDT 2013 Update 1.
|
||||
|
||||
4. On the **Windows 8.1** page, to create a Windows 10 deployment share, do not select the **Would you like to support Windows 8.1** check box. Click **Next** to continue.
|
||||
|
||||
@ -75,15 +82,17 @@ The following steps show how you create a deployment share for Windows 10 that
|
||||
|
||||
- **Local Path** – Specify or browse to the root directory of Windows 10 installation files. If you have an ISO file, mount it and browse to the root of the mounted drive. You must have a full set of source files, not just **Install.wim**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 3. Specify Windows 10 deployment share options
|
||||
*Figure 3. Specify Windows 10 deployment share options*
|
||||
|
||||
6. On the **Configure** page, select the check box next to each device or app that you want to include in your deployment share. Note that Surface Pro 4 and Surface Book only support Windows 10 and are not available for the deployment of Windows 8.1. The Surface Firmware Tool is only applicable to Surface Pro 3 and cannot be selected unless Surface Pro 3 drivers are selected, as shown in Figure 4. Click **Next** to continue.
|
||||
6. On the **Configure** page, select the check box next to each device or app that you want to include in your deployment share. Note that Surface Pro 4 and Surface Book only support Windows 10 and are not available for the deployment of Windows 8.1. The Surface Firmware Tool is only applicable to Surface 3 and Surface Pro 3 and cannot be selected unless Surface 3 or Surface Pro 3 drivers are selected, as shown in Figure 4. Click **Next** to continue.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 4. Selecting Surface Firmware Tool requires Surface Pro 3 drivers
|
||||
*Figure 4. Selecting Surface Firmware Tool requires Surface Pro 3 drivers*
|
||||
|
||||
>**Note:** You cannot select both Surface 3 and Surface 3 LTE models at the same time.
|
||||
|
||||
7. On the **Summary** page confirm your selections and click **Finish** to begin the creation of your deployment share. The process can take several minutes as files are downloaded, the tools are installed, and the deployment share is created. While the SDA scripts are creating your deployment share, an **Installation Progress** window will be displayed, as shown in Figure 5. A typical SDA process includes:
|
||||
|
||||
@ -105,9 +114,9 @@ The following steps show how you create a deployment share for Windows 10 that
|
||||
|
||||
- Creation of rules and task sequences for Windows deployment
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 5. The **Installation Progress** window
|
||||
*Figure 5. The Installation Progress window*
|
||||
|
||||
8. When the SDA process completes the creation of your deployment share, a **Success** window is displayed. Click **Finish** to close the window. At this point your deployment share is now ready to perform a Windows deployment to Surface devices.
|
||||
|
||||
@ -115,13 +124,15 @@ The following steps show how you create a deployment share for Windows 10 that
|
||||
|
||||
If you are unable to connect to the Internet with your deployment server, or if you want to download the Surface drivers and apps separately, you can specify a local source for the driver an app files at the time of deployment share creation. On the **Configure** page of the SDA wizard, select the **Copy from a Local Directory** check box, as shown in Figure 6. The **Download from the Internet** check box will be automatically deselected. Enter the folder location where you have placed the driver and app files in the **Local Path** field, as shown in Figure 6.
|
||||
|
||||
>**Note:** All of the downloaded driver and applications files must be located in the same folder. The driver and app files do not need to be extracted from the downloaded .zip files.
|
||||
>**Note:** All of the downloaded driver and applications files must be located in the same folder. If a required driver or application file is missing from the selected folder when you click **Next**, a warning is displayed and the wizard will not proceed to the next step.
|
||||
|
||||
|
||||
>**Note:** The driver and app files do not need to be extracted from the downloaded .zip files.
|
||||
|
||||
|
||||
>**Note:** Including Office 365 in your deployment share requires an Internet connection and cannot be performed if you use local files.
|
||||
|
||||
Figure 6. Specify the Surface driver and app files from a local path
|
||||
|
||||
|
||||
*Figure 6. Specify the Surface driver and app files from a local path*
|
||||
|
||||
>**Note:** The **Copy from a Local Directory** check box is only available in SDA version 1.90.0221 or later.
|
||||
|
||||
@ -159,9 +170,9 @@ Before you can create bootable media files within the MDT Deployment Workbench o
|
||||
|
||||
9. **exit** – Exits DiskPart, after which you can close the PowerShell or Command Prompt window.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 7. Use DiskPart to prepare a USB drive for boot
|
||||
*Figure 7. Use DiskPart to prepare a USB drive for boot*
|
||||
|
||||
>**Note:** You can format your USB drive with FAT32 from Disk Management, but you must still use DiskPart to set the partition as active for the drive to boot properly.
|
||||
|
||||
@ -177,15 +188,15 @@ After you have prepared the USB drive for boot, the next step is to generate off
|
||||
|
||||
4. Right-click the **Media** folder and click **New Media** as shown in Figure 8 to start the New Media Wizard.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 8. The Media folder of the SDA deployment share
|
||||
*Figure 8. The Media folder of the SDA deployment share*
|
||||
|
||||
5. On the **General Settings** page in the **Media path** field, enter or browse to a folder where you will create the files for the new offline media. See the example **E:\\SDAMedia** in Figure 9. Leave the default profile **Everything** selected in the **Selection profile** drop-down menu, and then click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 9. Specify a location and selection profile for your offline media
|
||||
*Figure 9. Specify a location and selection profile for your offline media*
|
||||
|
||||
6. On the **Summary** page verify your selections, and then click **Next** to begin creation of the media.
|
||||
|
||||
@ -195,9 +206,9 @@ After you have prepared the USB drive for boot, the next step is to generate off
|
||||
|
||||
9. Right-click the **Microsoft Surface Deployment Accelerator** deployment share folder, click **Properties**, and then click the **Rules** tab as shown in Figure 10.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 10. The Rules of the SDA deployment share
|
||||
*Figure 10. Rules of the SDA deployment share*
|
||||
|
||||
10. Use your mouse to highlight all of the text displayed in the text box of the **Rules** tab, and then press **Ctrl+C** to copy the text.
|
||||
|
||||
@ -229,15 +240,17 @@ After you have prepared the USB drive for boot, the next step is to generate off
|
||||
UserPassword=
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 11. The Bootstrap.ini file of MEDIA001
|
||||
*Figure 11. The Bootstrap.ini file of MEDIA001*
|
||||
|
||||
20. Close Bootstrap.ini and click **OK** in **MEDIA001** deployment share properties to close the window.
|
||||
|
||||
21. In the **Deployment Workbench** under the **Media** folder, right-click the newly created **MEDIA001** and click **Update Media Content**, as shown in Figure 12. This will update the media files with the content of the **Microsoft Surface Deployment Accelerator** deployment share.
|
||||
|
||||
Figure 12. Select **Update Media Content**
|
||||
|
||||
|
||||
*Figure 12. Select the Update Media Content option*
|
||||
|
||||
22. The **Update Media Content** window is displayed and shows the progress as the media files are created. When the process completes, click **Finish.**
|
||||
|
||||
@ -252,11 +265,11 @@ Your USB drive is now configured as bootable offline media that contains all of
|
||||
## SDA task sequences
|
||||
|
||||
|
||||
The SDA deployment share is configured with all of the resources required to perform a Windows deployment to a Surface device. These resources include Windows source files, image, Surface drivers, and Surface apps. The deployment share also contains two pre-configured task sequences, as shown in Figure 13. These task sequences contain the steps required to perform a deployment to a Surface device using the default Windows image from the installation media or to create a reference image complete with Windows updates and applications. To learn more about task sequences, see [MDT 2013 Update 1 Lite Touch components](http://technet.microsoft.com/en-us/itpro/windows/deploy/mdt-2013-lite-touch-components).
|
||||
The SDA deployment share is configured with all of the resources required to perform a Windows deployment to a Surface device. These resources include Windows source files, image, Surface drivers, and Surface apps. The deployment share also contains two pre-configured task sequences, as shown in Figure 13. These task sequences contain the steps required to perform a deployment to a Surface device using the default Windows image from the installation media or to create a reference image complete with Windows updates and applications. To learn more about task sequences, see [MDT 2013 Update 2 Lite Touch components](https://technet.microsoft.com/itpro/windows/deploy/mdt-2013-lite-touch-components).
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 13. Task sequences in the Deployment Workbench
|
||||
*Figure 13. Task sequences in the Deployment Workbench*
|
||||
|
||||
### Deploy Microsoft Surface
|
||||
|
||||
@ -286,7 +299,7 @@ The **2 – Create Windows Reference Image** task sequence is used to perform a
|
||||
|
||||
Like the **1 – Deploy Microsoft Surface** task sequence, the **2 – Create Windows Reference Image** task sequence performs a deployment of the unaltered Windows image directly from the installation media. Creation of a reference image should always be performed on a virtual machine. Using a virtual machine as your reference system helps to ensure that the resulting image is compatible with different hardware configurations.
|
||||
|
||||
>**Note:** Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information see [Deploy a Windows 10 image using MDT 2013 Update 1](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).
|
||||
>**Note:** Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and System Center Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information, see [Deploy a Windows 10 image using MDT 2013 Update 2](http://technet.microsoft.com/en-us/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).
|
||||
|
||||
|
||||
|
||||
@ -323,9 +336,9 @@ To instruct your Surface device to boot from the network, start with the device
|
||||
|
||||
4. Enter the domain credentials that you use to log on to the server where SDA is installed when you are prompted, as shown in Figure 14.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 14. The prompt for credentials to the deployment share
|
||||
*Figure 14. The prompt for credentials to the deployment share*
|
||||
|
||||
5. The Windows Deployment Wizard will start from the deployment share to walk you through the deployment process.
|
||||
|
||||
@ -343,15 +356,15 @@ To run the Deploy Microsoft Surface task sequence:
|
||||
|
||||
1. On the **Task Sequence** page, select the **1 – Deploy Microsoft Surface** task sequence as shown in Figure 15, and then click **Next.**
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 15. Select the **1 – Deploy Microsoft Surface** task sequence
|
||||
*Figure 15. Select the 1 – Deploy Microsoft Surface task sequence*
|
||||
|
||||
2. On the **Computer Details** page, type a name for the Surface device in the **Computer Name** box. In the **Join a domain** section, type your domain name and credentials as shown in Figure 16, and then click **Next**.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 16. Enter the computer name and domain information
|
||||
*Figure 16. Enter the computer name and domain information*
|
||||
|
||||
3. On the **Product Key** page, keep the **No product key is required** check box selected if you are deploying the same version and edition of Windows to your Surface devices as they came with from the factory. If you are deploying a different version or edition of Windows to the device, such as Windows Enterprise, select the licensing option that is applicable to your scenario.
|
||||
|
||||
@ -363,9 +376,9 @@ To run the Deploy Microsoft Surface task sequence:
|
||||
|
||||
7. On the **Ready** page, verify your selections and then click **Begin** to start the automated deployment to this device. The deployment will not require user interaction again. The Windows Deployment Wizard will close and an **Installation Progress** window is displayed to show progress of the task sequence as the image is applied and applications are installed (Figure 17).
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 17. The **Installation Progress** window
|
||||
*Figure 17. The Installation Progress window*
|
||||
|
||||
8. When the deployment task sequence completes, a **Success** window is displayed. Click **Finish** to complete the deployment and begin using your Surface device.
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ The [Microsoft Surface Diagnostic Toolkit](http://go.microsoft.com/fwlink/p/?Lin
|
||||
|
||||
- Surface Pro
|
||||
|
||||
>**Note:** Security software and built-in security measures in many email applications and services will block executable files that are transferred through email. To email the Surface Diagnostic Toolkit, attach the .zip archive file as downloaded from the Surface Tools for IT page without extracting it first. You can also create a custom .zip archive that contains the .exe file. (For example, if you want to localize the text as described in the [Localization](#localization) section of this article.)
|
||||
>**Note:** Security software and built-in security measures in many email applications and services will block executable files that are transferred through email. To email the Surface Diagnostic Toolkit, attach the archive file (.zip) as downloaded from the Surface Tools for IT page without extracting it first. You can also create a custom .zip archive that contains the .exe file. (For example, if you want to localize the text as described in the [Localization](#localization) section of this article.)
|
||||
|
||||
Running the Microsoft Surface Diagnostic Toolkit is a hands-on activity. The test sequence includes several tests that require you to perform actions or observe the outcome of the test, and then click the applicable **Pass** or **Fail** button. Some tests require connectivity to external devices, like an external display. Other tests use the built in Windows troubleshooters. At the end of testing, a visual report of the test results is displayed and you are given the option to save a log file or copy the results to the clipboard.
|
||||
|
||||
@ -49,17 +49,73 @@ To run a full set of tests with the Microsoft Surface Diagnostic Toolkit, you sh
|
||||
|
||||
- Room to move the Surface device around
|
||||
|
||||
- External speakers or headphones
|
||||
- External speakers or headphones with a 3.5mm stereo plug
|
||||
|
||||
>**Note:** The Microsoft Surface Diagnostic Toolkit tests verify only the hardware of a Surface device and do not test or resolve issues with the operating system or software.
|
||||
- A power adapter for your Surface device
|
||||
|
||||
>**Note:** The Microsoft Surface Diagnostic Toolkit tests verify only the hardware of a Surface device and do not resolve issues with the operating system or software.
|
||||
|
||||
## Configure test options
|
||||
|
||||
Before you select the tests you want to run, you can click the Tools  button in the upper right corner of the window (as shown in Figure 1) to access the Options section of the Microsoft Surface Diagnostic Toolkit. In the Options section, you can configure the depth of testing and logs, as well as the save location for log files. You can also create and use additional language files for the dialog of each test.
|
||||
|
||||
|
||||
|
||||
*Figure 1. The Tools button highlighted in upper right corner of window*
|
||||
|
||||
>**Note:** Any options you want to select must be specified before you run the tests. You cannot change the test options after the testing sequence has started.
|
||||
|
||||
####Test depth
|
||||
You can quickly select among three modes for testing and diagnostics by using the **Test Depth** page. The **Test Depth** page displays a slider with three possible positions, as shown in Figure 2. These positions determine which tests are run and what information is recorded without requiring you to select specific tests with the **Run Specific Tests** button. The three modes allow you to focus the tests of the Microsoft Surface Diagnostic Toolkit on hardware, software, or both hardware and software.
|
||||
|
||||
|
||||
|
||||
*Figure 2. The Test Depth slider to select the depth of data collection*
|
||||
|
||||
When you select a mode by using the Test Depth slider, a configuration file (.ini) with the same name as the Microsoft Surface Diagnostic Toolkit executable (.exe) file is created in the same folder. For example, if the Microsoft Surface Diagnostic Toolkit executable file is SurfaceDiagnosticToolkit.exe, the configuration file will be SurfaceDiagnosticToolkit.ini. When the executable file is run, the options will be automatically set by the configuration file. To run the Microsoft Surface Diagnostic Toolkit in a specific mode on multiple devices, ensure that the .ini file remains in the same folder with the .exe file used on each device.
|
||||
|
||||
When you run the Microsoft Surface Diagnostic Toolkit, you can still use the **Run Specific Tests** button to enable or disable specific tests. The tests selected on the **Please Select Tests to Run** page take priority over the tests enabled or disabled by the mode specified on the **Test Depth** page. When a mode is selected the tests that are applicable to that mode will be enabled by default and the tests that are not required for that mode will be disabled.
|
||||
|
||||
Each mode has a specific focus and records a different level of information in the log files, as follows:
|
||||
|
||||
* **Hardware and Software Focus.** This is the default mode for the Microsoft Surface Diagnostic Toolkit. In this mode all tests that are applicable to the device are run. This mode logs the most information and takes the most time.
|
||||
* **Software Experience Focus.** This mode collects information about the device and records it in the log file. No hardware tests are performed in this mode. The following tests are run in this mode:
|
||||
* Windows Update Check Test
|
||||
* Device Information Test
|
||||
* System Assessment Test
|
||||
* Crash Dump Collection Test
|
||||
* Modern Standby Test
|
||||
* **Hardware Validation Focus.** This mode tests the hardware of the device but does not collect system log files or device information. All diagnostic tests relevant to the device hardware are run in this mode. The exact tests that are run will vary from device to device depending on the hardware configuration. This mode logs the least information and requires the least amount of time.
|
||||
|
||||
|
||||
####Save location
|
||||
Use the **Browse** button on the **Save Location** page to select a default location for the Microsoft Surface Diagnostic Toolkit log files to be saved. When the tests complete the user will still be prompted to save a log file and a log file will not be saved automatically. The user must still click the **Save to File** button to save the log files. As with the Test Depth mode, this save location is stored in the Microsoft Surface Diagnostic Toolkit configuration (.ini) file and if the file does not exist, configuring this option will generate the file.
|
||||
|
||||
####Additional language
|
||||
Refer to the [Localization](#localization) section of this article for information about how to customize the dialog displayed during each test. On the **Additional Language** page, you can generate a localization file that you can use to customize the dialog during each test. You can also specify a specific localization file to be used with the Microsoft Surface Diagnostic Toolkit with the **Browse** button.
|
||||
|
||||
####Feedback
|
||||
You can use the form on the **Feedback** page to inform the product team of any problems that you encounter with the Microsoft Surface Diagnostic Toolkit or to provide any suggestions for how the Microsoft Surface Diagnostic Toolkit could be improved.
|
||||
|
||||
|
||||
|
||||
## The tests
|
||||
|
||||
|
||||
The Microsoft Surface Diagnostic Toolkit runs several individual tests on a Surface device. Not all tests are applicable to every device. For example, the Home button test is not applicable to Surface Pro 4 where there is no Home button. You can specify which tests to run, or you can choose to run all tests. For tests that require external devices (such as testing output to an external display) but you do not have the required external device at the time of the test, you are given the option to skip the test. If a test fails, you are prompted to continue or stop testing at that time.
|
||||
|
||||
When the testing completes, the **Test Results** page is displayed (as shown in Figure 3) and shows the status of each test: passed, failed, or inconclusive (skipped). You can choose to run the tests again; to save a log file, including any additional log files gathered by tests; or to copy the log file text to the clipboard.
|
||||
|
||||
|
||||
|
||||
*Figure 3. View of the results of the tests*
|
||||
|
||||
When the tests have completed, you can also add additional notes to the log files by clicking **Add additional feedback to results ->** on the **Test Results** page. Use the **Type any additional feedback about these tests** field on the **Test Results** page to add your notes, as shown in Figure 4.
|
||||
|
||||
|
||||
|
||||
*Figure 4. Add notes to the log file*
|
||||
|
||||
Notes that you type on this page are displayed in the log files after the results of the selected tests and before the **Files** section. The section header in the log files for these notes is named **User Feedback**.
|
||||
|
||||
#### Windows Update
|
||||
|
||||
This test checks for any outstanding Windows updates and will prompt you to install those updates before you proceed to other tests. It is important to keep a Surface device up to date with the latest Windows updates, including drivers and firmware for the Surface device. The success of some of the tests that are performed later in the task sequence depend on these updated drivers and firmware. You will be prompted to restart the device if required by Windows Update. If you must restart the device, you will need to start the Microsoft Surface Diagnostic Toolkit again.
|
||||
@ -213,7 +269,7 @@ Insert a micro SD or SD card when you are prompted. When the SD card is detected
|
||||
|
||||
#### Microphone test
|
||||
|
||||
This test displays the **Recording** tab of the Sound item in Control Panel. The test prompts you to monitor the meter that is displayed next to the **Microphone Array** recording device. A recommended test is to speak and watch for your speech to be detected in the meter. If the meter moves when you speak, the microphone is working correctly. For Surface Book you will be prompted to tap locations near the microphones. This tapping should produce noticeable spikes in the audio meter.
|
||||
This test displays a meter that shows the microphone sound level and records audio for a short period of time. Say a few words or make noise and make note that the meter displays the sound level accordingly. A countdown timer is displayed to indicate how much time is remaining for you to record sound. When the countdown timer expires, the recorded audio is played back. Verify that the words or noises sound clear and accurate, and then mark the test as passed or failed depending on the results.
|
||||
|
||||
#### Video out test
|
||||
|
||||
@ -231,11 +287,13 @@ After you receive a prompt to put the device in pairing mode, the test opens the
|
||||
|
||||
Use this test to verify that the cameras on your Surface device are operating properly. Images will be displayed from both the front and rear cameras, and the infrared camera on a Surface Pro 4. Continuous autofocus can be enabled on the rear camera. Move the device closer and farther away from an object to verify the operation of continuous autofocus.
|
||||
|
||||
>**Note:** You can also use the **Snapshot to Logs** option to save a snapshot of the video output to the log files.
|
||||
|
||||
#### Speaker test
|
||||
|
||||
>**Note:** Headphones or external speakers are required to test the headphone jack in this test.
|
||||
|
||||
This test plays audio over left and right channels respectively, both for the internal speakers and for speakers or headphones connected to the headphone jack. Mark each channel as a pass or fail as you hear the audio play.
|
||||
This test plays audio over left and right channels respectively, both for the internal speakers and for speakers or headphones connected through the headphone jack. Plug in your headphones or speakers to the 3.5mm stereo jack when prompted. The test will automatically detect that a sound playback device has been connected. Mark each channel as a pass or fail as you hear the audio play through the speakers or headphones.
|
||||
|
||||
#### Network test
|
||||
|
||||
@ -267,15 +325,21 @@ The compass detects which direction the Surface device is facing relative to nor
|
||||
|
||||
The ambient light sensor is used to automatically adjust screen brightness relative to the ambient lighting in the environment. Turn the device toward or away from a light source to cause the screen to dim or brighten in response increased or decreased light. The test automatically passes when the screen brightness automatically changes.
|
||||
|
||||
>**Note:** You can also block the ambient light from the sensor by holding your hand slightly in front of the light sensor, which is located directly next to the camera. Use the provided meter to determine if you are blocking light from the sensor.
|
||||
|
||||
#### Device orientation test
|
||||
|
||||
>**Note:** Before you run this test, disable rotation lock from the Action Center if enabled.
|
||||
|
||||
The device orientation sensor determines what the angle of the Surface device is, relative to the ground. Rotate the display 90 degrees or 180 degrees to cause the screen orientation to switch between portrait and landscape mode. The test automatically passes when the screen orientation switches.
|
||||
The device orientation sensor determines what the angle of the Surface device is, relative to the ground. Rotate the display 90 degrees or 180 degrees to cause the screen orientation to switch between portrait and landscape mode. If you have a Surface Type Cover or the Surface Book keyboard connected, you will be prompted to disconnect the Surface from the keyboard to allow screen rotation. The test automatically passes when the screen orientation switches.
|
||||
|
||||
#### Brightness test
|
||||
|
||||
This test cycles the screen through brightness levels from 0 percent to 100 percent, and then a message is displayed to confirm if the brightness level changed accordingly. You are then prompted to disconnect the power adapter. The screen should automatically dim when power is disconnected.
|
||||
This test cycles the screen through brightness levels from 0 percent to 100 percent, and then a message is displayed to confirm if the brightness level changed accordingly. You are then prompted to test for brightness reaction. To test the reaction of brightness when running on battery, disconnect the power adapter. The screen should automatically dim when power is disconnected.
|
||||
|
||||
#### Surface Dock test
|
||||
The Microsoft Surface Diagnostic Toolkit uses this test only if a Surface Dock is connected to the device. If a Surface Dock is detected, this test verifies that the Surface Dock driver firmware is updated. For more detailed analysis of Surface Dock firmware status and how to manually initiate the firmware update process, see the [Microsoft Surface Dock Updater](https://technet.microsoft.com/en-us/itpro/surface/surface-dock-updater) article.
|
||||
|
||||
|
||||
#### System assessment
|
||||
|
||||
@ -291,6 +355,19 @@ Performance and diagnostic trace logs are recorded from Performance Monitor for
|
||||
|
||||
If your Surface device has encountered an error that caused the device to fail or produce a blue screen error, this stage of the Microsoft Surface Diagnostic Toolkit records the information from the automatically recorded crash dump files in the diagnostic log. You can use these crash dump files to identify a faulty driver, hardware component, or application through analysis. Use the [Windows Debugging Tool](http://go.microsoft.com/fwlink/p/?LinkId=746488) to analyze these files. If you are not familiar with the analysis of crash dump files, you can describe your issue and post a link to your crash dump files (uploaded to OneDrive or another file sharing service) in the [Windows TechNet Forums](http://go.microsoft.com/fwlink/p/?LinkId=746489).
|
||||
|
||||
#### Connected standby text
|
||||
|
||||
>**Note:** This test is only available on Surface devices running Windows 8 or Windows 8.1.
|
||||
|
||||
If connected standby is enabled on the Surface device, this test passes automatically. If connected standby is not enabled, a failure is recorded for this test. Find out more about Connected Standby and Modern Standby at [Modern Standby](https://msdn.microsoft.com/library/windows/hardware/mt282515) on MSDN.
|
||||
|
||||
#### Modern standby test
|
||||
|
||||
>**Note:** This test is only available on Surface devices running Windows 10.
|
||||
|
||||
This test records log files of the power configuration for the Surface device using the **powercfg.exe /a** command. The test completes automatically and a failure is only recorded if the command does not run.
|
||||
|
||||
|
||||
## Command line
|
||||
|
||||
You can run the Microsoft Surface Diagnostic Toolkit from the command line or as part of a script. The tool supports the following arguments:
|
||||
@ -430,25 +507,26 @@ Surface_Diagnostic_Toolkit_1.0.60.0.exe “logpath=C:\Folder with spaces”
|
||||
## Localization
|
||||
|
||||
|
||||
By default, the Microsoft Surface Diagnostic Toolkit is available in English only. If you want to localize the text of the Microsoft Surface Diagnostic Toolkit prompts into another language, you can do so by creating a custom localization file. If the localization file exists, the Microsoft Surface Diagnostic Toolkit will override the default English text and use the text contained in the file instead. To create a localization file, follow these steps:
|
||||
By default, the Microsoft Surface Diagnostic Toolkit is available in English only. If you want to localize the text of the Microsoft Surface Diagnostic Toolkit prompts into another language, you can do so by creating a custom localization file. To create a new localization file (.locale), follow these steps:
|
||||
|
||||
1. Open Notepad.
|
||||
1. Click the Tools  button.
|
||||
2. Click the **Additional Language** page.
|
||||
3. Click the **Generate** button and the new .locale file is created.
|
||||
|
||||
2. Type the following line at the beginning of the file:
|
||||
The locale file that is created when you use these steps will have the same name as your executable file, even if it has been changed from the default. For example, if the Microsoft Surface Diagnostic Toolkit executable file is SurfaceDiagnosticToolkit.exe, the localization file would be SurfaceDiagnosticToolkit.locale. The locale file will be created in the same folder as the executable file. If a localization file with this name already exists, you will be prompted to overwrite the existing file. The file that is created when you click the **Generate** button is always generated in the default language, English.
|
||||
|
||||
``` syntax
|
||||
<root />
|
||||
```
|
||||
To customize the localization file, open the file in a text or XML editor such as Notepad. To edit the dialog for each test, replace the text for each phrase tag. (For example, `<phrase key="testdialog">text</phrase>`.) To use the file automatically when you start the Microsoft Surface Diagnostic Toolkit, simply save the file with the same name it had when it was created. To save the file for use with other instances of Microsoft Surface Diagnostic Toolkit, copy the file to another location or save the file with another name.
|
||||
|
||||
3. Save the file as SurfaceDiagnosticTool\_v1.0.60.0.locale in the same location where the Microsoft Surface Diagnostic Toolkit executable file is stored.
|
||||
If a localization file with the same name and in the same folder as the executable file is detected when Microsoft Surface Diagnostic Toolkit started, the alternate text specified in that localization file replaces the default dialog and prompts. If a custom localization file is not present or the file name is not the same as the executable file, the tool will default to English text. At any point you can also explicitly specify a localization file to be used by the Microsoft Surface Diagnostic Toolkit. To specify a localization file, follow these steps:
|
||||
1. Click the Tools  button.
|
||||
2. Click the **Additional Language** page.
|
||||
3. Click **Browse**.
|
||||
4. Browse to and select your custom localization file.
|
||||
|
||||
4. Run the Microsoft Surface Diagnostic Toolkit executable file, Surface\_Diagnostic\_Toolkit\_v1.0.60.0.exe. The SurfaceDiagnosticTool\_v1.0.60.0.locale file will be populated with all of the text from the default prompts.
|
||||
A custom localization file selected through this process does not need a specific name. After you select the custom localization file, the Microsoft Surface Diagnostic Toolkit will import the contents and write them to a .locale file with the same name as the .exe file, just like if you click the **Generate** button to create a new .locale file.
|
||||
|
||||
5. Open the SurfaceDiagnosticTool\_v1.0.60.0.locale file in Notepad and change the text of each prompt to your custom or localized text.
|
||||
>**Note:** If you import a localization file by clicking the **Browse** button, an existing localization file will be overwritten without prompting if that file has the same name as the Microsoft Surface Diagnostic Toolkit executable file.
|
||||
|
||||
6. Save the SurfaceDiagnosticTool\_v1.0.60.0.locale file.
|
||||
|
||||
>**Note:** The SurfaceDiganosticTool\_v1.0.60.0.locale file must be located in the same folder and have the same name other than the file extension as the Microsoft Surface Diagnostic Toolkit executable file to use the custom prompt text. The SurfaceDiganosticTool\_v1.0.60.0.locale is an .xml file and must use UTF-8 encoding.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -34,15 +34,15 @@ To update a Surface Dock with Microsoft Surface Dock Updater, follow these steps
|
||||
|
||||
- If the tool determines that the firmware of your Surface Dock is up to date, a **You have the latest firmware for this Surface Dock** message is displayed, as shown in Figure 1.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 1. Your Surface Dock firmware is up to date.
|
||||
*Figure 1. Your Surface Dock firmware is up to date*
|
||||
|
||||
- If Microsoft Surface Dock Updater determines that the firmware of your Surface Dock is not up to date, a **This Surface Dock is not running the latest firmware** message is displayed, as shown in Figure 2.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 2. Your Surface Dock firmware needs to be updated
|
||||
*Figure 2. Your Surface Dock firmware needs to be updated*
|
||||
|
||||
3. To begin the firmware update process, click **Update** on the **Surface Dock Firmware** page.
|
||||
|
||||
@ -50,27 +50,27 @@ To update a Surface Dock with Microsoft Surface Dock Updater, follow these steps
|
||||
|
||||
5. As the firmware update is uploaded to the Surface Dock, a **Progress** page is displayed, as shown in Figure 3. Do not disconnect the Surface Dock while firmware is being uploaded.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 3. Progress of firmware update upload to Surface Dock
|
||||
*Figure 3. Progress of firmware update upload to Surface Dock*
|
||||
|
||||
6. After the firmware update has successfully uploaded to the Surface Dock, you are prompted to disconnect and then reconnect the Surface Dock from the Surface device, as shown in Figure 4. The main chipset firmware update will be applied while the Surface Dock is disconnected.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 4. Disconnect and reconnect Surface Dock when prompted
|
||||
*Figure 4. Disconnect and reconnect Surface Dock when prompted*
|
||||
|
||||
7. When the main chipset firmware update is verified, the DisplayPort chipset firmware update will be uploaded to the Surface Dock. Upon completion, a **Success** page is displayed and you will again be prompted to disconnect the Surface Dock, as shown in Figure 5.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 5. Successful upload of Surface Dock firmware
|
||||
*Figure 5. Successful upload of Surface Dock firmware*
|
||||
|
||||
8. After you disconnect the Surface Dock the DisplayPort firmware update will be installed. This process occurs on the Surface Dock hardware while it is disconnected. The Surface Dock must remain powered for up to 3 minutes after it has been disconnected for the firmware update to successfully install. An **Update in Progress** page is displayed (as shown in Figure 6), with a countdown timer to show the estimated time remaining to complete the firmware update installation.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 6. Countdown timer to complete firmware installation on Surface Dock
|
||||
*Figure 6. Countdown timer to complete firmware installation on Surface Dock*
|
||||
|
||||
9. If you want to update multiple Surface Docks in one sitting, you can click the **Update another Surface Dock** button to begin the process on the next Surface Dock.
|
||||
|
||||
@ -83,9 +83,9 @@ To update a Surface Dock with Microsoft Surface Dock Updater, follow these steps
|
||||
|
||||
If the Surface Dock firmware update process encounters an installation error with either firmware update, the **Encountered an unexpected error** page may be displayed, as shown in Figure 7.
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 7. Firmware update installation has encountered an error
|
||||
*Figure 7. Firmware update installation has encountered an error*
|
||||
|
||||
Microsoft Surface Dock Updater logs its progress into the Event Log, as shown in Figure 8. If you need to troubleshoot an update through this tool, you will find Surface Dock events recorded with the following event IDs:
|
||||
|
||||
@ -97,9 +97,9 @@ Microsoft Surface Dock Updater logs its progress into the Event Log, as shown in
|
||||
| 12105 | Error |
|
||||
|
||||
|
||||
Figure 8. Surface Dock Updater events in Event Viewer
|
||||
|
||||
|
||||
|
||||
*Figure 8. Surface Dock Updater events in Event Viewer*
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
163
devices/surface/surface-enterprise-management-mode.md
Normal file
163
devices/surface/surface-enterprise-management-mode.md
Normal file
@ -0,0 +1,163 @@
|
||||
---
|
||||
title: Surface Enterprise Management Mode (Surface)
|
||||
description: See how this feature of Surface devices with Surface UEFI helps you secure and manage firmware settings within your organization.
|
||||
keywords: uefi, configure, firmware, secure, semm
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
---
|
||||
|
||||
# Microsoft Surface Enterprise Management Mode
|
||||
|
||||
Microsoft Surface Enterprise Management Mode (SEMM) is a feature of Surface devices with Surface UEFI that allows you to secure and manage firmware settings within your organization. With SEMM, IT professionals can prepare configurations of UEFI settings and install them on a Surface device. In addition to the ability to configure UEFI settings, SEMM also uses a certificate to protect the configuration from unauthorized tampering or removal.
|
||||
|
||||
>**Note**: SEMM is only available on devices with Surface UEFI firmware, such as Surface Pro 4 and Surface Book. For more information about Surface UEFI, see [Manage Surface UEFI Settings](https://technet.microsoft.com/en-us/itpro/surface/manage-surface-uefi-settings).
|
||||
|
||||
When Surface devices are configured by SEMM and secured with the SEMM certificate, they are considered *enrolled* in SEMM. When the SEMM certificate is removed and control of UEFI settings is returned to the user of the device, the Surface device is considered *unenrolled* in SEMM.
|
||||
|
||||
## Microsoft Surface UEFI Configurator
|
||||
|
||||
The primary workspace of SEMM is Microsoft Surface UEFI Configurator, as shown in Figure 1. Microsoft Surface UEFI Configurator is a tool that is used to create Windows Installer (.msi) packages that are used to enroll, configure, and unenroll SEMM on a Surface device. These packages contain a configuration file where the settings for UEFI are specified. SEMM packages also contain a certificate that is installed and stored in firmware and used to verify the signature of configuration files before UEFI settings are applied.
|
||||
|
||||
|
||||
|
||||
*Figure 1. Microsoft Surface UEFI Configurator*
|
||||
|
||||
>**Note**: Windows 10 is required to run Microsoft Surface UEFI Configurator
|
||||
|
||||
You can use the Microsoft Surface UEFI Configurator tool in three modes:
|
||||
|
||||
* [Surface UEFI Configuration Package](#configuration-package). Use this mode to create a Surface UEFI configuration package to enroll a Surface device in SEMM and to configure UEFI settings on enrolled devices.
|
||||
* [Surface UEFI Reset Package](#reset-package). Use this mode to unenroll a Surface device from SEMM.
|
||||
* [Surface UEFI Recovery Request](#recovery-request). Use this mode to respond to a recovery request to unenroll a Surface device from SEMM where a Reset Package operation is not successful.
|
||||
|
||||
|
||||
#### Download Microsoft Surface UEFI Configurator
|
||||
|
||||
You can download Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/en-us/download/details.aspx?id=46703) page in the Microsoft Download Center.
|
||||
|
||||
### Configuration package
|
||||
|
||||
Surface UEFI configuration packages are the primary mechanism to implement and manage SEMM on Surface devices. These packages contain a configuration file of UEFI settings specified during creation of the package in Microsoft Surface UEFI Configurator and a certificate file, as shown in Figure 2. When a configuration package is run for the first time on a Surface device that is not already enrolled in SEMM, it provisions the certificate file in the device’s firmware and enrolls the device in SEMM. When enrolling a device in SEMM, you will be prompted to confirm the operation by providing the last two digits of the SEMM certificate thumbprint before the certificate file is stored and the enrollment can complete. This confirmation requires that a user be present at the device at the time of enrollment to perform the confirmation.
|
||||
|
||||
|
||||
|
||||
*Figure 2. Secure a SEMM configuration package with a certificate*
|
||||
|
||||
See the [Surface Enterprise Management Mode certificate requirements](#surface-enterprise-management-mode-certificate-requirements) section of this article for more information about the requirements for the SEMM certificate.
|
||||
|
||||
>**Note**: You can also specify a UEFI password with SEMM that is required to view the **Security**, **Devices**, **Boot Configuration**, or **Enterprise Management** pages of Surface UEFI.
|
||||
|
||||
After a device is enrolled in SEMM, the configuration file is read and the settings specified in the file are applied to UEFI. When you run a configuration package on a device that is already enrolled in SEMM, the signature of the configuration file is checked against the certificate that is stored in the device firmware. If the signature does not match, no changes are applied to the device.
|
||||
|
||||
You can use Surface UEFI settings to enable or disable the operation of individual components, such as cameras, wireless communication, or docking USB port (as shown in Figure 3), and configure advanced settings (as shown in Figure 4).
|
||||
|
||||
|
||||
|
||||
*Figure 3. Enable or disable devices in Surface UEFI with SEMM*
|
||||
|
||||
|
||||
|
||||
*Figure 4. Configure advanced settings with SEMM*
|
||||
|
||||
You can enable or disable the following devices with SEMM:
|
||||
|
||||
* Docking USB Port
|
||||
* On-board Audio
|
||||
* Type Cover
|
||||
* Micro SD or SD Card Slots
|
||||
* Front Camera
|
||||
* Rear Camera
|
||||
* Infrared Camera, for Windows Hello
|
||||
* Bluetooth Only
|
||||
* Wi-Fi and Bluetooth
|
||||
* Trusted Platform Module (TPM)
|
||||
|
||||
You can configure the following advanced settings with SEMM:
|
||||
|
||||
* IPv6 support for PXE boot
|
||||
* Alternate boot order, where the Volume Down button and Power button can be pressed together during boot, to boot directly to a USB or Ethernet device
|
||||
* Lock the boot order to prevent changes
|
||||
* Support for booting to USB devices
|
||||
* Display of the Surface UEFI **Security** page
|
||||
* Display of the Surface UEFI **Devices** page
|
||||
* Display of the Surface UEFI **Boot** page
|
||||
|
||||
>**Note**: When you create a SEMM configuration package, two characters are shown on the **Successful** page, as shown in Figure 5.
|
||||
|
||||
|
||||
|
||||
*Figure 5. Display of the last two characters of the certificate thumbprint on the Successful page*
|
||||
|
||||
These characters are the last two characters of the certificate thumbprint and should be written down or recorded. The characters are required to confirm enrollment in SEMM on a Surface device, as shown in Figure 6.
|
||||
|
||||
|
||||
|
||||
*Figure 6. Enrollment confirmation in SEMM with the SEMM certificate thumbprint*
|
||||
|
||||
To enroll a Surface device in SEMM or to apply the UEFI configuration from a configuration package, all you need to do is run the .msi file on the intended Surface device. You can use application deployment or operating system deployment technologies such as [System Center Configuration Manager](https://technet.microsoft.com/library/mt346023) or the [Microsoft Deployment Toolkit](https://technet.microsoft.com/en-us/windows/dn475741). When you enroll a device in SEMM you must be present to confirm the enrollment on the device. User interaction is not required when you apply a configuration to devices that are already enrolled in SEMM.
|
||||
|
||||
### Reset package
|
||||
|
||||
A Surface UEFI reset package is used to perform only one task — to unenroll a Surface device from SEMM. The reset package contains signed instructions to remove the SEMM certificate from the device’s firmware and to reset UEFI settings to factory default. Like a Surface UEFI configuration package, a reset package must be signed with the same SEMM certificate that is provisioned on the Surface device. When you create a SEMM reset package, you are required to supply the serial number of the Surface device you intend to reset. SEMM reset packages are not universal and are specific to one device.
|
||||
|
||||
### Recovery request
|
||||
|
||||
In some scenarios, it may be impossible to use a Surface UEFI reset package. (For example, if Windows becomes unusable on the Surface device.) In these scenarios you can unenroll the Surface device from SEMM through the **Enterprise Management** page of Surface UEFI (shown in Figure 7) with a Recovery Request operation.
|
||||
|
||||
|
||||
|
||||
*Figure 7. Initiate a SEMM recovery request on the Enterprise Management page*
|
||||
|
||||
When you use the process on the **Enterprise Management** page to reset SEMM on a Surface device, you are provided with a Reset Request. This Reset Request can be saved as a file to a USB drive, copied as text, or read as a QR Code with a mobile device to be easily emailed or messaged. Use the Microsoft Surface UEFI Configurator Reset Request option to load a Reset Request file or enter the Reset Request text or QR Code. Microsoft Surface UEFI Configurator will generate a verification code that can be entered on the Surface device. If you enter the code on the Surface device and click **Restart**, the device will be unenrolled from SEMM.
|
||||
|
||||
>**Note**: A Reset Request expires two hours after it is created.
|
||||
|
||||
## Surface Enterprise Management Mode certificate requirements
|
||||
|
||||
>**Note**: The SEMM certificate is required to perform any modification to SEMM or Surface UEFI settings on enrolled Surface devices. If the SEMM certificate is corrupted or lost, SEMM cannot be removed or reset. Manage your SEMM certificate accordingly with an appropriate solution for backup and recovery.
|
||||
|
||||
Packages created with the Microsoft Surface UEFI Configurator tool are signed with a certificate. This certificate ensures that after a device is enrolled in SEMM, only packages created with the approved certificate can be used to modify the settings of UEFI. The following settings are recommended for the SEMM certificate:
|
||||
|
||||
* **Key Algorithm** – RSA
|
||||
* **Key Length** – 2048
|
||||
* **Hash Algorithm** – SHA-256
|
||||
* **Type** – SSL Server Authentication
|
||||
* **Key Usage** – Key Encipherment
|
||||
* **Provider** – Microsoft Enhanced RSA and AES Cryptographic Provider
|
||||
* **Expiration Date** – 15 Months from certificate creation
|
||||
* **Key Export Policy** – Exportable
|
||||
|
||||
It is also recommended that the SEMM certificate be authenticated in a two-tier public key infrastructure (PKI) architecture where the intermediate certification authority (CA) is dedicated to SEMM, enabling certificate revocation. For more information about a two-tier PKI configuration, see [Test Lab Guide: Deploying an AD CS Two-Tier PKI Hierarchy](https://technet.microsoft.com/library/hh831348).
|
||||
|
||||
>**Note**: You can use the following PowerShell script to create a self-signed certificate for use in proof-of-concept scenarios.
|
||||
To use this script, copy the following text into Notepad and save the file as a PowerShell script (.ps1). This script creates a certificate with a password of `12345678`.<br/><br/>The certificate generated by this script is not recommended for production environments.
|
||||
|
||||
```
|
||||
if (-not (Test-Path "Demo Certificate")) { New-Item -ItemType Directory -Force -Path "Demo Certificate" }
|
||||
if (Test-Path "Demo Certificate\TempOwner.pfx") { Remove-Item "Demo Certificate\TempOwner.pfx" }
|
||||
|
||||
# Generate the Ownership private signing key with password 12345678
|
||||
$pw = ConvertTo-SecureString "12345678" -AsPlainText -Force
|
||||
|
||||
$TestUefiV2 = New-SelfSignedCertificate `
|
||||
-Subject "CN=Surface Demo Kit, O=Contoso Corporation, C=US" `
|
||||
-Type SSLServerAuthentication `
|
||||
-HashAlgorithm sha256 `
|
||||
-KeyAlgorithm RSA `
|
||||
-KeyLength 2048 `
|
||||
-KeyUsage KeyEncipherment `
|
||||
-KeyUsageProperty All `
|
||||
-Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" `
|
||||
-NotAfter (Get-Date).AddYears(25) `
|
||||
-TextExtension @("2.5.29.37={text}1.2.840.113549.1.1.1") `
|
||||
-KeyExportPolicy Exportable
|
||||
|
||||
$TestUefiV2 | Export-PfxCertificate -Password $pw -FilePath "Demo Certificate\TempOwner.pfx"
|
||||
```
|
||||
|
||||
For use with SEMM and Microsoft Surface UEFI Configurator, the certificate must be exported with the private key and with password protection. Microsoft Surface UEFI Configurator will prompt you to select the SEMM certificate file (.pfx) and certificate password when it is required.
|
||||
|
||||
>**Note**: For organizations that use an offline root in their PKI infrastructure, Microsoft Surface UEFI Configurator must be run in an environment connected to the root CA to authenticate the SEMM certificate. The packages generated by Microsoft Surface UEFI Configurator can be transferred as files and therefore can be transferred outside the offline network environment with removable storage, such as a USB stick.
|
||||
148
devices/surface/unenroll-surface-devices-from-semm.md
Normal file
148
devices/surface/unenroll-surface-devices-from-semm.md
Normal file
@ -0,0 +1,148 @@
|
||||
---
|
||||
title: Unenroll Surface devices from SEMM (Surface)
|
||||
description: Learn how to unenroll a device from SEMM by using a Surface UEFI reset package or the Recovery Request option.
|
||||
keywords: surface enterprise management
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.pagetype: surface, devices, security
|
||||
ms.sitesec: library
|
||||
author: jobotto
|
||||
---
|
||||
|
||||
# Unenroll Surface devices from SEMM
|
||||
|
||||
When a Surface device is enrolled in Surface Enterprise Management Mode (SEMM), a certificate is stored in the firmware of that device. The presence of that certificate and the enrollment in SEMM prevent any unauthorized changes to Surface UEFI settings or options while the device is enrolled in SEMM. To restore control of Surface UEFI settings to the user, the Surface device must be unenrolled from SEMM, a process sometimes described as reset or recovery. There are two methods you can use to unenroll a device from SEMM—a Surface UEFI reset package and a Recovery Request.
|
||||
|
||||
>**Warning:** To unenroll a device from SEMM and restore user control of Surface UEFI settings, you must have the SEMM certificate that was used to enroll the device in SEMM. If this certificate becomes lost or corrupted, it is not possible to unenroll from SEMM. Back up and protect your SEMM certificate accordingly.
|
||||
|
||||
For more information about SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/en-us/itpro/surface/surface-enterprise-management-mode).
|
||||
|
||||
## Unenroll a Surface device from SEMM with a Surface UEFI reset package
|
||||
|
||||
The Surface UEFI reset package is the primary method you use to unenroll a Surface device from SEMM. Like a Surface UEFI configuration package, the reset package is a Windows Installer (.msi) file that configures SEMM on the device. Unlike the configuration package, the reset package will reset the Surface UEFI configuration on a Surface device to its default settings, remove the SEMM certificate, and unenroll the device from SEMM.
|
||||
|
||||
Reset packages are created specifically for an individual Surface device. To begin the process of creating a reset package, you will need the serial number of the device you want to unenroll, as well as the SEMM certificate used to enroll the device. You can find the serial number of your Surface device on the **PC information** page of Surface UEFI, as shown in Figure 1. This page is displayed even if Surface UEFI is password protected and the incorrect password is entered.
|
||||
|
||||
|
||||
|
||||
*Figure 1. The serial number of the Surface device is displayed on the Surface UEFI PC information page*
|
||||
|
||||
>**Note:** To boot to Surface UEFI, press **Volume Up** and **Power** simultaneously while the device is off. Hold **Volume Up** until the Surface logo is displayed and the device begins to boot.
|
||||
|
||||
To create a Surface UEFI reset package, follow these steps:
|
||||
|
||||
1. Open Microsoft Surface UEFI Configurator from the Start menu.
|
||||
2. Click **Start**.
|
||||
3. Click **Reset Package**, as shown in Figure 2.
|
||||
|
||||
|
||||
|
||||
*Figure 2. Click Reset Package to create a package to unenroll a Surface device from SEMM*
|
||||
|
||||
4. Click **Certificate Protection** to add your SEMM certificate file with private key (.pfx), as shown in Figure 3. Browse to the location of your certificate file, select the file, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
*Figure 3. Add the SEMM certificate to a Surface UEFI reset package*
|
||||
|
||||
5. Click **Next**.
|
||||
6. Type the serial number of the device you want to unenroll from SEMM (as shown in Figure 4), and then click **Build** to generate the Surface UEFI reset package.
|
||||
|
||||
|
||||
|
||||
*Figure 4. Use the serial number of your Surface device to create a Surface UEFI reset package*
|
||||
|
||||
7. In the **Save As** dialog box, specify a name for the Surface UEFI reset package, browse to the location where you would like to save the file, and then click **Save**.
|
||||
8. When the package generation has completed, the **Successful** page is displayed. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
|
||||
|
||||
Run the Surface UEFI reset package Windows Installer (.msi) file on the Surface device to unenroll the device from SEMM. The reset package will require a reboot to perform the unenroll operation. After the device has been unenrolled, you can verify the successful removal by ensuring that the **Microsoft Surface Configuration Package** item in **Programs and Features** (shown in Figure 5) is no longer present.
|
||||
|
||||
|
||||
|
||||
*Figure 5. The presence of the Microsoft Surface Configuration Package item in Programs and Features indicates that the device is enrolled in SEMM*
|
||||
|
||||
## Unenroll a Surface device from SEMM with a Recovery Request
|
||||
|
||||
In some scenarios, a Surface UEFI reset package may not be a viable option to unenroll a Surface device from SEMM (for example, where Windows has become unusable). In these scenarios you can unenroll the device by using a Recovery Request generated from within Surface UEFI. The Recovery Request process can be initiated even on devices where you do not have the Surface UEFI password.
|
||||
|
||||
The Recovery Request process is initiated from Surface UEFI on the Surface device, approved with Microsoft Surface UEFI Configurator on another computer, and then completed in Surface UEFI. Like the reset package, approving a Recovery Request with Microsoft Surface UEFI Configurator requires access to the SEMM certificate that was used to enroll the Surface device.
|
||||
|
||||
To initiate a Recovery Request, follow these steps:
|
||||
|
||||
1. Boot the Surface device that is to be unenrolled from SEMM to Surface UEFI.
|
||||
2. Type the Surface UEFI password if you are prompted to do so.
|
||||
3. Click the **Enterprise management** page, as shown in Figure 6.
|
||||
|
||||
|
||||
|
||||
*Figure 6. The Enterprise management page is displayed in Surface UEFI on devices enrolled in SEMM*
|
||||
|
||||
4. Click or press **Get Started**.
|
||||
5. Click or press **Next** to begin the Recovery Request process.
|
||||
>**Note:** A Recovery Request expires two hours after it is created. If a Recovery Request is not completed in this time, you will have to restart the Recovery Request process.
|
||||
6. Select **SEMM Certificate** from the list of certificates displayed on the **Choose a SEMM reset key** page (shown in Figure 7), and then click or press **Next**.
|
||||
|
||||
|
||||
|
||||
*Figure 7. Choose SEMM Certificate for your Recovery Request (Reset Request)*
|
||||
|
||||
7. On the **Enter SEMM reset verification code** page you can click the **QR Code** or **Text** buttons to display your Recovery Request (Reset Request) as shown in Figure 8, or the **USB** button to save your Recovery Request (Reset Request) as a file to a USB drive, as shown in Figure 9.
|
||||
|
||||
|
||||
|
||||
*Figure 8. A Recovery Request (Reset Request) displayed as a QR Code*
|
||||
|
||||
|
||||
|
||||
*Figure 9. Save a Recovery Request (Reset Request) to a USB drive*
|
||||
|
||||
* To use a QR Code Recovery Request (Reset Request), use a QR reader app on a mobile device to read the code. The QR reader app will translate the QR code into an alphanumeric string. You can then email or message that string to the administrator that will produce the reset verification code with Microsoft Surface UEFI Configurator.
|
||||
* To use a Recovery Request (Reset Request) saved to a USB drive as a file, use the USB drive to transfer the file to the computer where Microsoft Surface UEFI Configurator will be used to produce the Reset Verification Code. The file can also be copied from the USB drive on another device to be emailed or transferred over the network.
|
||||
* To use the Recovery Request (Reset Request) as text, simply type the text directly into Microsoft Surface UEFI Configurator.
|
||||
|
||||
8. Open Microsoft Surface UEFI Configurator from the Start menu on another computer.
|
||||
>**Note:** Microsoft Surface UEFI Configurator must run in an environment that is able to authenticate the certificate chain for the SEMM certificate.
|
||||
9. Click **Start**.
|
||||
10. Click **Recovery Request**, as shown in Figure 10.
|
||||
|
||||
|
||||
|
||||
*Figure 10. Click Recovery Request to begin the process to approve a Recovery Request*
|
||||
|
||||
11. Click **Certificate Protection** to authenticate the Recovery Request with the SEMM certificate.
|
||||
12. Browse to and select your SEMM certificate file, and then click **OK**.
|
||||
13. When you are prompted to enter the certificate password as shown in Figure 11, type and confirm the password for the certificate file, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
*Figure 11. Type the password for the SEMM certificate*
|
||||
|
||||
14. Click **Next**.
|
||||
15. Enter the Recovery Request (Reset Request), and then click **Generate** to create a reset verification code (as shown in Figure 12).
|
||||
|
||||
|
||||
|
||||
*Figure 12. Enter the Recovery Request (Reset Request)*
|
||||
|
||||
* If you displayed the Recovery Request (Reset Request) as text on the Surface device being reset, use the keyboard to type the Recovery Request (Reset Request) in the provided field.
|
||||
* If you displayed the Recovery Request (Reset Request) as a QR Code and then used a messaging or email application to send the code to the computer with Microsoft Surface UEFI Configurator, copy and paste the code into the provided field.
|
||||
* If you saved the Recovery Request (Reset Request) as a file to a USB drive, click the **Import** button, browse to and select the Recovery Request (Reset Request) file, and then click **OK**.
|
||||
|
||||
16. The reset verification code is displayed in Microsoft Surface UEFI Configurator, as shown in Figure 13.
|
||||
|
||||
|
||||
|
||||
*Figure 13. The reset verification code displayed in Microsoft Surface UEFI Configurator*
|
||||
|
||||
* Click the **Share** button to send the reset verification code by email.
|
||||
|
||||
17. Enter the reset verification code in the provided field on the Surface device (shown in Figure 8), and then click or press **Verify** to reset the device and unenroll the device from SEMM.
|
||||
18. Click or press **Restart now** on the **SEMM reset successful** page to complete the unenrollment from SEMM, as shown in Figure 14.
|
||||
|
||||
|
||||
|
||||
*Figure 14. Successful unenrollment from SEMM*
|
||||
|
||||
19. Click **End** in Microsoft Surface UEFI Configurator to complete the Recovery Request (Reset Request) process and close Microsoft Surface UEFI Configurator.
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@
|
||||
#### [Deploying the App-V 5.1 Sequencer and Client](deploying-the-app-v-51-sequencer-and-client.md)
|
||||
##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md)
|
||||
##### [About Client Configuration Settings 5.1](about-client-configuration-settings51.md)
|
||||
##### [How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
##### [How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
##### [How to Install the App-V 5.1 Client for Shared Content Store Mode](how-to-install-the-app-v-51-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](how-to-install-the-sequencer-51beta-gb18030.md)
|
||||
##### [How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-51-client-configuration-using-the-admx-template-and-group-policy.md)
|
||||
@ -81,11 +81,10 @@
|
||||
#### [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md)
|
||||
##### [Check Registry Keys before installing App-V 5.x Server](check-reg-key-svr.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V 5.1](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
##### [How to Use an App-V 4.6 SP1 Application From an App-V 5.1 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
#### [Maintaining App-V 5.1](maintaining-app-v-51.md)
|
||||
##### [How to Move the App-V Server to Another Computer 5.1](how-to-move-the-app-v-server-to-another-computer51.md)
|
||||
#### [Administering App-V 5.1 by Using PowerShell](administering-app-v-51-by-using-powershell.md)
|
||||
@ -141,7 +140,7 @@
|
||||
#### [Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md)
|
||||
##### [About Client Configuration Settings](about-client-configuration-settings.md)
|
||||
##### [How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
##### [How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
##### [How to Install the App-V 5.0 Client for Shared Content Store Mode](how-to-install-the-app-v-50-client-for-shared-content-store-mode.md)
|
||||
##### [How to Install the Sequencer](how-to-install-the-sequencer-beta-gb18030.md)
|
||||
##### [How to Modify App-V 5.0 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-50-client-configuration-using-the-admx-template-and-group-policy.md)
|
||||
@ -196,11 +195,10 @@
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](how-to-configure-the-client-to-receive-package-and-connection-groups-updates-from-the-publishing-server-beta.md)
|
||||
#### [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
##### [How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-50-application.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
##### [How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
##### [How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
#### [Maintaining App-V 5.0](maintaining-app-v-50.md)
|
||||
##### [How to Move the App-V Server to Another Computer](how-to-move-the-app-v-server-to-another-computer.md)
|
||||
#### [Administering App-V by Using PowerShell](administering-app-v-by-using-powershell.md)
|
||||
|
||||
@ -34,7 +34,7 @@ The following list displays what is new with App-V 5.0:
|
||||
|
||||
- **Connection Groups** - App-V 5.0 connection groups allow you to connect and run virtual applications interactively.
|
||||
|
||||
## <a href="" id="bkmk-diff-46-50"></a>Differences between App-4.6 and App-V 5.0
|
||||
## <a href="" id="bkmk-diff-46-50"></a>Differences between App-V 4.6 and App-V 5.0
|
||||
|
||||
|
||||
The following table displays some of the differences between App-V 4.6 and App-V 5.0:
|
||||
|
||||
@ -449,6 +449,8 @@ The App-V client supports the following versions of System Center Configuration
|
||||
|
||||
The following App-V and System Center Configuration Manager version matrix shows all officially supported combinations of App-V and Configuration Manager.
|
||||
|
||||
**Note:** Both App-V 4.5 and 4.6 have exited Mainstream support.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
@ -474,130 +476,6 @@ The following App-V and System Center Configuration Manager version matrix shows
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 CU1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5 SP1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 SP2</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6</p></td>
|
||||
<td align="left"><p>R2, SP1</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP1</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
<td align="left"><p>MSI-Wrapper-Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP1</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP2 HF4</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
|
||||
@ -24,7 +24,7 @@ The App-V 5.0 client is the component that runs a virtualized application on a t
|
||||
|
||||
[How to Uninstall the App-V 5.0 Client](how-to-uninstall-the-app-v-50-client.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ The App-V 5.1 client is the component that runs a virtualized application on a t
|
||||
|
||||
[How to Uninstall the App-V 5.1 Client](how-to-uninstall-the-app-v-51-client.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
[How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
ms.assetid: 5b7e27e4-4360-464c-b832-f1c7939e5485
|
||||
author: jamiejdt
|
||||
---
|
||||
|
||||
# How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer
|
||||
|
||||
**Note:** App-V 4.6 has exited Mainstream support. The following assumes that the App-V 4.6 SP3 client is already installed.
|
||||
|
||||
Use the following information to install the App-V 5.0 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md).
|
||||
|
||||
**To deploy the App-V 5.0 client and App-V 4.6 client on the same computer**
|
||||
|
||||
1. Install the App-V 5.0 SP3 client on the computer that is running the App-V 4.6 version of the client. For best results, we recommend that you install all available updates to the App-V 5.0 SP3 client.
|
||||
|
||||
2. Convert or re-sequence the packages gradually.
|
||||
|
||||
- To convert the packages, use the App-V 5.0 package converter and convert the required packages to the App-V 5.0 (**.appv**) file format.
|
||||
|
||||
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
|
||||
|
||||
For more information about publishing packages, see [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md).
|
||||
|
||||
3. Deploy packages to the client computers.
|
||||
|
||||
4. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
|
||||
5. Test that your App-V 5.0 packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
|
||||
|
||||
[Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,29 +1,27 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
author: jamiejdt
|
||||
title: How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
ms.assetid: 498d50c7-f13d-4fbb-8ea1-b959ade26fdf
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer
|
||||
|
||||
# How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
|
||||
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following information to install the Microsoft Application Virtualization (App-V) 5.1 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v51.md).
|
||||
|
||||
**To deploy the App-V 5.1 client and App-V 4.6.x client on the same computer**
|
||||
**To deploy the App-V 5.1 client and App-V 4.6 client on the same computer**
|
||||
|
||||
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687)
|
||||
1. Install the following version of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
|
||||
|
||||
2. Install the App-V 5.1 client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.1 client.
|
||||
2. Install the App-V 5.1 client on the computer that is running the App-V 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.1 client.
|
||||
|
||||
3. Convert or re-sequence the packages gradually.
|
||||
|
||||
@ -37,9 +35,9 @@ Use the following information to install the Microsoft Application Virtualizatio
|
||||
|
||||
5. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
|
||||
|
||||
@ -1,64 +0,0 @@
|
||||
---
|
||||
title: How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
description: How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
author: jamiejdt
|
||||
ms.assetid: 5b7e27e4-4360-464c-b832-f1c7939e5485
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer
|
||||
|
||||
|
||||
Use the following information to install the App-V 5.0 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md).
|
||||
|
||||
**To deploy the App-V 5.0 client and App-V 4.6.x client on the same computer**
|
||||
|
||||
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 2](http://go.microsoft.com/fwlink/?LinkId=262687)
|
||||
|
||||
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
|
||||
|
||||
2. Install the App-V 5.0 client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.0 client.
|
||||
|
||||
3. Convert or re-sequence the packages gradually.
|
||||
|
||||
- To convert the packages, use the App-V 5.0 package converter and convert the required packages to the App-V 5.0 (**.appv**) file format.
|
||||
|
||||
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
|
||||
|
||||
For more information about publishing packages, see [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md).
|
||||
|
||||
4. Deploy packages to the client computers.
|
||||
|
||||
5. Convert extension points, as needed. For more information, see the following resources:
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
- [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
- [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
|
||||
|
||||
6. Test that your App-V 5.0 packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
|
||||
|
||||
[Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,26 +1,26 @@
|
||||
---
|
||||
title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
author: jamiejdt
|
||||
title: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
description: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
ms.assetid: 3ae9996f-71d9-4ca1-9aab-25b599158e55
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
|
||||
Use the following procedure to migrate extension points from an App-V 4.6 SP2 package to a App-V 5.0 package using the deployment configuration file.
|
||||
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V 5.0 package using the deployment configuration file.
|
||||
|
||||
**Note**
|
||||
The following procedure does not require an App-V 5.0 management server.
|
||||
|
||||
|
||||
|
||||
**To migrate extension points from a package from an App-V 4.6 SP2 package to a converted App-V 5.0 package using the deployment configuration file**
|
||||
**To migrate extension points from a package from an App-V 4.6 package to a converted App-V 5.0 package using the deployment configuration file**
|
||||
|
||||
1. Locate the directory that contains the deployment configuration file for the package you want to migrate. To set the policy, make the following update to the **userConfiguration** section:
|
||||
|
||||
@ -52,14 +52,14 @@ The following procedure does not require an App-V 5.0 management server.
|
||||
|
||||
PS>**Publish-AppVClientPackage $pkg**
|
||||
|
||||
3. To test the migration, open the virtual application using asscoaited FTAs or shortcuts. The application opens with App-V 5.0. Both, the App-V 4.6 SP2 package and the converted App-V 5.0 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.0 package.
|
||||
3. To test the migration, open the virtual application using asscoaited FTAs or shortcuts. The application opens with App-V 5.0. Both, the App-V 4.6 package and the converted App-V 5.0 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.0 package.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[Operations for App-V 5.0](operations-for-app-v-50.md)
|
||||
|
||||
@ -60,7 +60,7 @@ The following procedure does not require an App-V 5.1 management server.
|
||||
## Related topics
|
||||
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[Operations for App-V 5.1](operations-for-app-v-51.md)
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
---
|
||||
title: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
description: How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
author: jamiejdt
|
||||
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
ms.assetid: dad25992-3c75-4b7d-b4c6-c2edf43baaea
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User
|
||||
|
||||
# How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following procedure to migrate packages created with App-V using the user configuration file.
|
||||
|
||||
@ -51,7 +51,7 @@ This procedure assumes that you are running the latest version of App-V 4.6.
|
||||
|
||||
[Operations for App-V 5.1](operations-for-app-v-51.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
description: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
title: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
description: How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
ms.assetid: f1d2ab1f-0831-4976-b49f-169511d3382a
|
||||
author: jamiejdt
|
||||
ms.assetid: f1d2ab1f-0831-4976-b49f-169511d3382a
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -9,15 +10,15 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User
|
||||
|
||||
# How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
Use the following procedure to revert an App-V 5.0 package to the App-V file format using the user configuration file.
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -25,7 +26,7 @@ Use the following procedure to revert an App-V 5.0 package to the App-V file for
|
||||
|
||||
PS>**Publish-AppVClientPackage $pkg –DynamicUserConfigurationPath** <path to user configuration file>
|
||||
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
|
||||
**Note**
|
||||
If you do not need the App-V 5.0 package anymore, you can unpublish the App-V 5.0 package and the extension points will automatically revert to App-V 4.6.
|
||||
@ -1,23 +1,23 @@
|
||||
---
|
||||
title: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
description: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
author: jamiejdt
|
||||
title: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
description: How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
ms.assetid: 2a43ca1b-6847-4dd1-ade2-336ac4ac6af0
|
||||
author: jamiejdt
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer
|
||||
|
||||
# How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following assumes that the App-V 4.6 SP3 client is already installed.
|
||||
|
||||
|
||||
Use the following procedure to revert extension points from an App-V 5.0 package to the App-V 4.6 SP2 file format using the deployment configuration file.
|
||||
Use the following procedure to revert extension points from an App-V 5.0 package to the App-V 4.6 file format using the deployment configuration file.
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 SP2 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.0 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -29,7 +29,7 @@ Use the following procedure to revert extension points from an App-V 5.0 package
|
||||
|
||||
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6 SP2 package.
|
||||
|
||||
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6 SP2.
|
||||
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
|
||||
|
||||
**Note**
|
||||
If you do not need the App-V 5.0 package anymore, you can unpublish the App-V 5.0 package and the extension points will automatically revert to App-V 4.6.
|
||||
@ -17,7 +17,7 @@ Use the following procedure to revert an App-V 5.1 package to the App-V file for
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -17,7 +17,7 @@ Use the following procedure to revert extension points from an App-V 5.1 package
|
||||
|
||||
**To revert a package**
|
||||
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md).
|
||||
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md).
|
||||
|
||||
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=<Package ID>**
|
||||
|
||||
@ -1,6 +1,7 @@
|
||||
---
|
||||
title: How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
description: How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
title: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
description: How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
ms.assetid: 4e78cb32-9c8b-478e-ae8b-c474a7e42487
|
||||
author: jamiejdt
|
||||
ms.assetid: 4e78cb32-9c8b-478e-ae8b-c474a7e42487
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
@ -9,21 +10,21 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Use an App-V 4.6 Application From an App-V 5.0 Application
|
||||
|
||||
# How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following applies to an App-V 4.6 SP3 package.
|
||||
|
||||
|
||||
Use the following procedure to run an App-V 4.6 SP2 application with App-V 5.0 applications on a standalone client.
|
||||
Use the following procedure to run an App-V 4.6 application with App-V 5.0 applications on a standalone client.
|
||||
|
||||
**To run applications on a standalone client**
|
||||
|
||||
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
|
||||
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.0 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md).
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.0 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md).
|
||||
|
||||
3. Add and provision the package using the App-V 5.0 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-beta-gb18030.md) and [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-50.md).
|
||||
|
||||
4. The converted application now runs using App-V 5.0 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.0 package and Adobe Acrobat is still running as an App-V 4.6 SP2 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
|
||||
4. The converted application now runs using App-V 5.0 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.0 package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
|
||||
|
||||
**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issu**e? Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ms.prod: w10
|
||||
|
||||
# How to Use an App-V 4.6 Application From an App-V 5.1 Application
|
||||
|
||||
*Note:** App-V 4.6 has exited Mainstream support. The following applies to an App-V 4.6 SP3 package.
|
||||
|
||||
Use the following procedure to run an App-V 4.6 application with App-V 5.1 applications on a standalone client.
|
||||
|
||||
@ -22,7 +23,7 @@ This procedure assumes that you are running the latest version of App-V 4.6.
|
||||
|
||||
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
|
||||
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md).
|
||||
2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md).
|
||||
|
||||
3. Add and provision the package using the App-V 5.1 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-51-gb18030.md) and [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-51.md).
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ With App-V 5.0 you can migrate your existing App-V 4.6 infrastructure to the mor
|
||||
Consider the following sections when you plan your migration strategy:
|
||||
|
||||
**Note**
|
||||
For more information about the differences between App-V 4.6 and App-V 5.0, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
For more information about the differences between App-V 4.6 and App-V 5.0, see the **Differences between App-V 4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Install the App-V 5.0 client with co-existence enabled.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md).</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V 5.0 packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
@ -117,7 +117,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
|
||||
|
||||
**Important**
|
||||
You must be running App-V 4.6 SP2 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
You must be running App-V 4.6 SP3 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
|
||||
|
||||
|
||||
|
||||
@ -139,7 +139,7 @@ There is no direct method to upgrade to a full App-V 5.0 infrastructure. Use the
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrade your environment to App-V 4.6 SP2.</p></td>
|
||||
<td align="left"><p>Upgrade your environment to App-V 4.6 SP3.</p></td>
|
||||
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -164,15 +164,14 @@ There is no direct method to upgrade to a full App-V 5.0 infrastructure. Use the
|
||||
|
||||
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V 5.0 client. The following links provide more information about performing these tasks.
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 SP2 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 SP2 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-50-for-a-specific-user.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 SP2 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 SP2 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
[How to Use an App-V 4.6 SP1 Application From an App-V 5.0 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-50-application.md)
|
||||
|
||||
## Got a suggestion for App-V?
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ However, you cannot migrate directly from App-V 4.x to App-V 5.1, you must migra
|
||||
**Note**
|
||||
App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V 5.1 packages.
|
||||
|
||||
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-V 4.6 and App-V 5.0 section** of [About App-V 5.0](about-app-v-50.md).
|
||||
|
||||
|
||||
|
||||
@ -241,7 +241,7 @@ The following table displays the recommended method for upgrading clients.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Install the App-V 5.1 client with co-existence enabled.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md).</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Sequence and roll out App-V 5.1 packages. As needed, unpublish App-V 4.6 packages.</p></td>
|
||||
@ -300,15 +300,14 @@ There is no direct method to upgrade to a full App-V 5.1 infrastructure. Use the
|
||||
|
||||
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V 5.1 client. The following links provide more information about performing these tasks.
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-sp2-package-to-app-v-51-for-a-specific-user.md)
|
||||
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
|
||||
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-all-users-on-a-specific-computer.md)
|
||||
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
|
||||
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-sp2-package-for-a-specific-user.md)
|
||||
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
|
||||
|
||||
[How to Use an App-V 4.6 Application From an App-V 5.1 Application](how-to-use-an-app-v-46-sp1-application-from-an-app-v-51-application.md)
|
||||
|
||||
## Got a suggestion for App-V?
|
||||
|
||||
|
||||
@ -20,22 +20,23 @@ Use the following information to plan how to migrate to App-V 5.0 from previous
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V 5.0 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
- If you are upgrading from a version earlier than App-V 4.6 SP2, upgrade to version App-V 4.6 SP3 first before upgrading to App-V 5.0 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
- App-V 5.0 supports only packages that are created using App-V 5.0, or packages that have been converted to the App-V 5.0 (**.appv**) format.
|
||||
|
||||
- App-V 5.0 SP3 only: If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-migrate-to-50sp3) for instructions.
|
||||
|
||||
## Running the App-V 5.0 client concurrently with App-V 4.6 SP2 or later
|
||||
## Running the App-V 5.0 client concurrently with App-V 4.6
|
||||
|
||||
|
||||
You can run the App-V 5.0 client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
You can run the App-V 5.0 client concurrently on the same computer with the App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V 5.0 format and publish both packages, when you have both clients running.
|
||||
- Convert an App-V 4.6 SP3 package to the App-V 5.0 format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.0 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.0 package to assume the file type associations and shortcuts from the App-V 4.6 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
@ -48,20 +49,12 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V 4.6 client type</th>
|
||||
<th align="left">App-V 5.0 client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V 5.0 RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
</tr>
|
||||
@ -78,37 +71,33 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V 5.0 client.
|
||||
- Install the App-V 4.6 client before you install the App-V 5.0 client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To get the deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
The following table provides link to the TechNet documentation about the releases. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 5.0 SP3](about-app-v-50-sp3.md)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -117,14 +106,14 @@ The following table provides links to the App-V 4.6.x client downloads and to th
|
||||
|
||||
For more information about how to configure App-V 5.0 client coexistence, see:
|
||||
|
||||
- [How to Deploy the App-V 4.6.x and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
- [How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
## <a href="" id="converting--previous-version--packages-using-the-package-converter-"></a>Converting “previous-version” packages using the package converter
|
||||
|
||||
|
||||
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V 5.0, review the following requirements:
|
||||
Before migrating a package, created using App-V 4.6 SP3 or earlier, to App-V 5.0, review the following requirements:
|
||||
|
||||
- You must convert the package to the **.appv** file format.
|
||||
|
||||
|
||||
@ -20,22 +20,23 @@ Use the following information to plan how to migrate to Microsoft Application Vi
|
||||
|
||||
Before you start any upgrades, review the following requirements:
|
||||
|
||||
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V 5.1 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
- If you are upgrading from a version earlier than App-V 4.6 SP2, upgrade to version App-V 4.6 SP3 first before upgrading to App-V 5.1 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
|
||||
**Note:** App-V 4.6 has exited Mainstream support.
|
||||
|
||||
- App-V 5.1 supports only packages that are created using App-V 5.0 or App-V 5.1, or packages that have been converted to the **.appv** format.
|
||||
|
||||
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V 5.1](about-app-v-51.md#bkmk-migrate-to-51) for instructions.
|
||||
|
||||
## Running the App-V 5.1 client concurrently with App-V 4.6 SP2 or later
|
||||
## Running the App-V 5.1 client concurrently with App-V 4.6
|
||||
|
||||
|
||||
You can run the App-V 5.1 client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
|
||||
You can run the App-V 5.1 client concurrently on the same computer with the App-V 4.6 SP3 client.
|
||||
|
||||
When you run coexisting App-V clients, you can:
|
||||
|
||||
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V 5.1 format and publish both packages, when you have both clients running.
|
||||
- Convert an App-V 4.6 SP3 package to the App-V 5.1 format and publish both packages, when you have both clients running.
|
||||
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.1 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
|
||||
- Define the migration policy for the converted package, which allows the converted App-V 5.1 package to assume the file type associations and shortcuts from the App-V 4.6 package.
|
||||
|
||||
### Supported coexistence scenarios
|
||||
|
||||
@ -48,20 +49,12 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V 4.6.x client type</th>
|
||||
<th align="left">App-V 4.6 client type</th>
|
||||
<th align="left">App-V 5.1 client type</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>App-V 5.1</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
|
||||
<td align="left"><p>App-V 5.1 RDS</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>App-V 5.1</p></td>
|
||||
</tr>
|
||||
@ -78,42 +71,38 @@ The following table shows the supported App-V coexistence scenarios. We recommen
|
||||
|
||||
To run coexisting clients, you must:
|
||||
|
||||
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V 5.1 client.
|
||||
- Install the App-V 4.6 client before you install the App-V 5.1 client.
|
||||
|
||||
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** > **Client Coexistence** node. To deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
|
||||
|
||||
**Note**
|
||||
App-V 5.1 packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V 5.1 and 4.X. However, App-V 5.1 packages cannot interact with App-V 4.X packages in the same virtual environment.
|
||||
App-V 5.1 packages can run side by side with App-V 4.6 packages if you have coexisting installations of App-V 5.1 and 4.6. However, App-V 5.1 packages cannot interact with App-V 4.6 packages in the same virtual environment.
|
||||
|
||||
|
||||
|
||||
### Client downloads and documentation
|
||||
|
||||
The following table provides links to the App-V 4.6.x client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
The following table provides links to the App-V 4.6 client downloads and to the TechNet documentation about the releases. The downloads include the App-V “regular” and RDS clients. The TechNet documentation about the App-V client applies to both clients, unless stated otherwise.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V version</th>
|
||||
<th align="left">Link to download the client</th>
|
||||
<th align="left">Link to TechNet documentation</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 2](http://www.microsoft.com/download/details.aspx?id=35513)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP2](http://technet.microsoft.com/library/jj680847.aspx)</p></td>
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>[Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 4.6 SP3](http://technet.microsoft.com/library/dn511019.aspx)</p></td>
|
||||
<td align="left"><p>[About Microsoft Application Virtualization 5.1](about-app-v-51.md)</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
@ -122,7 +111,7 @@ The following table provides links to the App-V 4.6.x client downloads and to th
|
||||
|
||||
For more information about how to configure App-V 5.1 client coexistence, see:
|
||||
|
||||
- [How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46x-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
- [How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
|
||||
|
||||
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user