mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-20 17:27:23 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jdvpn
This commit is contained in:
commit
a658190d61
@ -30,7 +30,7 @@ Initiating a reset will return the device to the last cumulative Windows update,
|
|||||||
- Local admins on the device
|
- Local admins on the device
|
||||||
- Configurations from MDM or the Settings app
|
- Configurations from MDM or the Settings app
|
||||||
|
|
||||||
**To reset a Surface Hub**
|
**To reset a Surface Hub from Settings**</br>
|
||||||
1. On your Surface Hub, open **Settings**.
|
1. On your Surface Hub, open **Settings**.
|
||||||
|
|
||||||

|

|
||||||
@ -43,8 +43,18 @@ Initiating a reset will return the device to the last cumulative Windows update,
|
|||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
**To reset a Surface Hub from Windows Recovery Environment**</br>
|
||||||
|
On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device will automatically reboot and try again. But if this operation fails repeatedly, the device will be automatically locked to protect user data. To unlock it, you must reset the device from [Windows Recovery Environment](https://technet.microsoft.com/en-us/library/cc765966(v=ws.10).aspx) (Windows RE).
|
||||||
|
|
||||||
|
To reset a Surface Hub from Windows RE:
|
||||||
|
|
||||||
|
1. From the welcome screen, toggle the Surface Hub's power switch 3 times. Wait a few seconds between each toggle. See the [Surface Hub Site Readiness Guide](https://www.microsoft.com/surface/support/surface-hub/surface-hub-site-readiness-guide) for help with locating the power switch.
|
||||||
|
2. The device should automatically boot into Windows RE. Select **Advanced Repair**.
|
||||||
|
3. Select **Reset**.
|
||||||
|
4. If prompted, enter your device's BitLocker key.
|
||||||
|
|
||||||
**Important Note**</br>
|
**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.
|
Performing a device reset may take up to 2 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.
|
After the reset, Surface Hub restarts the [first run program](first-run-program-surface-hub.md) again.
|
||||||
|
|
||||||
|
@ -4,6 +4,7 @@ description: Microsoft System Center 2012 R2 Configuration Manager supports depl
|
|||||||
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
ms.assetid: 2dfb2f39-1597-4999-b4ec-b063e8a8c90c
|
||||||
keywords: deployment, task sequence, custom, customize
|
keywords: deployment, task sequence, custom, customize
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
|
localizationpriority: high
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
|
@ -5,6 +5,7 @@ ms.assetid: 837f009c-617e-4b3f-9028-2246067ee0fb
|
|||||||
keywords: deploy, tools, configure, script
|
keywords: deploy, tools, configure, script
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
|
localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
author: mtniehaus
|
author: mtniehaus
|
||||||
|
@ -6,6 +6,7 @@ keywords: configure, deploy, upgrade
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
|
localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: mtniehaus
|
author: mtniehaus
|
||||||
---
|
---
|
||||||
|
@ -29,6 +29,7 @@ When MDT is integrated with Configuration Manager, the task sequence takes addit
|
|||||||
|
|
||||||
The task sequence uses instructions that allow you to reduce the number of task sequences in Configuration Manager and instead store settings outside the task sequence. Here are a few examples:
|
The task sequence uses instructions that allow you to reduce the number of task sequences in Configuration Manager and instead store settings outside the task sequence. Here are a few examples:
|
||||||
- The following settings instruct the task sequence to install the HP Hotkeys package, but only if the hardware is a HP EliteBook 8570w. Note that you don't have to add the package to the task sequence.
|
- The following settings instruct the task sequence to install the HP Hotkeys package, but only if the hardware is a HP EliteBook 8570w. Note that you don't have to add the package to the task sequence.
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
[Settings]
|
[Settings]
|
||||||
Priority=Model
|
Priority=Model
|
||||||
@ -36,6 +37,7 @@ The task sequence uses instructions that allow you to reduce the number of task
|
|||||||
Packages001=PS100010:Install HP Hotkeys
|
Packages001=PS100010:Install HP Hotkeys
|
||||||
```
|
```
|
||||||
- The following settings instruct the task sequence to put laptops and desktops in different organizational units (OUs) during deployment, assign different computer names, and finally have the task sequence install the Cisco VPN client, but only if the machine is a laptop.
|
- The following settings instruct the task sequence to put laptops and desktops in different organizational units (OUs) during deployment, assign different computer names, and finally have the task sequence install the Cisco VPN client, but only if the machine is a laptop.
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
[Settings]
|
[Settings]
|
||||||
Priority= ByLaptopType, ByDesktopType
|
Priority= ByLaptopType, ByDesktopType
|
||||||
|
@ -6,6 +6,7 @@ keywords: install, configure, deploy, deployment
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
|
localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
author: mtniehaus
|
author: mtniehaus
|
||||||
---
|
---
|
||||||
|
@ -5,6 +5,7 @@ ms.assetid: acf091c9-f8f4-4131-9845-625691c09a2a
|
|||||||
keywords: deploy, deployment, replace
|
keywords: deploy, deployment, replace
|
||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.mktglfcycl: deploy
|
ms.mktglfcycl: deploy
|
||||||
|
localizationpriority: high
|
||||||
ms.sitesec: library
|
ms.sitesec: library
|
||||||
localizationpriority: high
|
localizationpriority: high
|
||||||
ms.pagetype: mdt
|
ms.pagetype: mdt
|
||||||
|
@ -85,6 +85,7 @@ If you consistently get the error "Windows BitLocker Drive Encryption Informatio
|
|||||||
In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you have downloaded the [Add-TPMSelfWriteACE.vbs script](https://go.microsoft.com/fwlink/p/?LinkId=167133) from Microsoft to C:\\Setup\\Scripts on DC01.
|
In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you have downloaded the [Add-TPMSelfWriteACE.vbs script](https://go.microsoft.com/fwlink/p/?LinkId=167133) from Microsoft to C:\\Setup\\Scripts on DC01.
|
||||||
1. On DC01, start an elevated PowerShell prompt (run as Administrator).
|
1. On DC01, start an elevated PowerShell prompt (run as Administrator).
|
||||||
2. Configure the permissions by running the following command:
|
2. Configure the permissions by running the following command:
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
cscript C:\Setup\Scripts\Add-TPMSelfWriteACE.vbs
|
cscript C:\Setup\Scripts\Add-TPMSelfWriteACE.vbs
|
||||||
```
|
```
|
||||||
@ -106,10 +107,12 @@ cctk.exe --tpm=on --valsetuppwd=Password1234
|
|||||||
### Add tools from HP
|
### Add tools from HP
|
||||||
|
|
||||||
The HP tools are part of HP System Software Manager. The executable file from HP is named BiosConfigUtility.exe. This utility uses a configuration file for the BIOS settings. Here is a sample command to enable TPM and set a BIOS password using the BiosConfigUtility.exe tool:
|
The HP tools are part of HP System Software Manager. The executable file from HP is named BiosConfigUtility.exe. This utility uses a configuration file for the BIOS settings. Here is a sample command to enable TPM and set a BIOS password using the BiosConfigUtility.exe tool:
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
BIOSConfigUtility.EXE /SetConfig:TPMEnable.REPSET /NewAdminPassword:Password1234
|
BIOSConfigUtility.EXE /SetConfig:TPMEnable.REPSET /NewAdminPassword:Password1234
|
||||||
```
|
```
|
||||||
And the sample content of the TPMEnable.REPSET file:
|
And the sample content of the TPMEnable.REPSET file:
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
English
|
English
|
||||||
Activate Embedded Security On Next Boot
|
Activate Embedded Security On Next Boot
|
||||||
|
@ -140,6 +140,7 @@ Make sure the account you are using has permissions to run runbooks on the Orche
|
|||||||
|
|
||||||
1. On PC0001, log on as **CONTOSO\\MDT\_BA**.
|
1. On PC0001, log on as **CONTOSO\\MDT\_BA**.
|
||||||
2. Using an elevated command prompt (run as Administrator), type the following command:
|
2. Using an elevated command prompt (run as Administrator), type the following command:
|
||||||
|
|
||||||
``` syntax
|
``` syntax
|
||||||
cscript \\MDT01\MDTProduction$\Scripts\Litetouch.vbs
|
cscript \\MDT01\MDTProduction$\Scripts\Litetouch.vbs
|
||||||
```
|
```
|
||||||
|
Loading…
x
Reference in New Issue
Block a user