deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-07-02 18:53:41 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #2034 from MicrosoftDocs/sfc

Browse Source 
Fix issue with non-escaped characters and note indentation
This commit is contained in:
Greg Lindsay
2020-02-11 11:45:27 -08:00
committed by GitHub
parent c8af4a3854 36b484eace
commit 749beb7695
2 changed files with 16 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
devices/surface/surface-dock-firmware-update.md
View File

@ -61,10 +61,15 @@ This section describes how to install the firmware update.
You can use Windows Installer commands (Msiexec.exe) to deploy Surface Dock Firmware Update to multiple devices across your network. When using Microsoft Endpoint Configuration Manager or other deployment tool, enter the following syntax to ensure the installation is silent:
- **Msiexec.exe /i <name of msi> /quiet /norestart**
- **Msiexec.exe /i \<path to msi file\> /quiet /norestart**
For example:
```
msiexec /i "\\share\folder\Surface_Dock_FwUpdate_1.42.139_Win10_17134_19.084.31680_0.msi" /quiet /norestart
```
> [!NOTE]
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]". For example: Msiexec.exe /i <name of msi> /l*v %windir%\logs\ SurfaceDockFWI.log"
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]". For example: Msiexec.exe /i \<path to msi file\> /l*v %windir%\logs\ SurfaceDockFWI.log"
For more information, refer to [Command line options](https://docs.microsoft.com/windows/win32/msi/command-line-options) documentation.
@ -76,7 +81,7 @@ For more information, refer to [Command line options](https://docs.microsoft.com
You can use Intune to distribute Surface Dock Firmware Update to your devices. First you will need to convert the MSI file to the .intunewin format, as described in the following documentation: [Intune Standalone - Win32 app management](https://docs.microsoft.com/intune/apps/apps-win32-app-management).
Use the following command:
- **msiexec /i <name of msi> /quiet /q**
- **msiexec /i \<path to msi file\> /quiet /q**
## How to verify completion of the firmware update

21
windows/deployment/usmt/usmt-identify-users.md
View File

@ -10,7 +10,6 @@ ms.mktglfcycl: deploy
ms.sitesec: library
audience: itpro
author: greg-lindsay
ms.date: 04/19/2017
ms.topic: article
---
@ -21,9 +20,7 @@ It is important to carefully consider how you plan to migrate users. By default,
## In This Topic
- [Migrating Local Accounts](#bkmk-8)
- [Migrating Domain Accounts](#bkmk-9)
- [Command-Line Options](#bkmk-7)
## <a href="" id="bkmk-8"></a>Migrating Local Accounts
@ -36,8 +33,8 @@ Before migrating local accounts, note the following:
- [Be careful when specifying a password for local accounts.](#bkmk-8) If you create the local account with a blank password, anyone could log on to that account on the destination computer. If you create the local account with a password, the password is available to anyone with access to the USMT command-line tools.
> [!NOTE]
> If there are multiple users on a computer, and you specify a password with the **/lac** option, all migrated users will have the same password.
>[!NOTE]
>If there are multiple users on a computer, and you specify a password with the **/lac** option, all migrated users will have the same password.
## <a href="" id="bkmk-9"></a>Migrating Domain Accounts
@ -49,8 +46,8 @@ USMT provides several options to migrate multiple users on a single computer. Th
- [Specifying users.](#bkmk-8) You can specify which users to migrate with the **/all**, **/ui**, **/uel**, and **/ue** options with both the ScanState and LoadState command-line tools.
> [!IMPORTANT]  
> The **/uel** option excludes users based on the **LastModified** date of the Ntuser.dat file. The **/uel** option is not valid in offline migrations.
>[!IMPORTANT]  
>The **/uel** option excludes users based on the **LastModified** date of the Ntuser.dat file. The **/uel** option is not valid in offline migrations.
- [Moving users to another domain.](#bkmk-8) You can move user accounts to another domain using the **/md** option with the LoadState command-line tool.
@ -58,13 +55,11 @@ USMT provides several options to migrate multiple users on a single computer. Th
- [Renaming user accounts.](#bkmk-8) You can rename user accounts using the **/mu** option.
> [!NOTE]
> By default, if a user name is not specified in any of the command-line options, the user will be migrated.
>[!NOTE]
>By default, if a user name is not specified in any of the command-line options, the user will be migrated.
## Related topics
[Determine What to Migrate](usmt-determine-what-to-migrate.md)
[ScanState Syntax](usmt-scanstate-syntax.md)
[Determine What to Migrate](usmt-determine-what-to-migrate.md)<br>
[ScanState Syntax](usmt-scanstate-syntax.md)<br>
[LoadState Syntax](usmt-loadstate-syntax.md)