mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
CI Update
This commit is contained in:
@ -84,7 +84,7 @@ MDT comes with nine default task sequence templates. You can also create your ow
|
||||
|
||||
**Note**
|
||||
It is preferable to use a complete build and capture instead of the Sysprep and Capture task sequence. A complete build and capture can be automated, whereas Sysprep and Capture cannot.
|
||||
|
||||
|
||||
- **Standard Client task sequence.** The most frequently used task sequence. Used for creating reference images and for deploying clients in production.
|
||||
- **Standard Client Replace task sequence.** Used to run User State Migration Tool (USMT) backup and the optional full Windows Imaging (WIM) backup action. Can also be used to do a secure wipe of a machine that is going to be decommissioned.
|
||||
- **Custom task sequence.** As the name implies, a custom task sequence with only one default action (one Install Application action).
|
||||
@ -110,7 +110,7 @@ MDT uses many log files during operating system deployments. By default the logs
|
||||
|
||||
**Note**
|
||||
The easiest way to view log files is to use Configuration Manager Trace (CMTrace), which is included in the [System Center 2012 R2 Configuration Manager Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=734717).
|
||||
|
||||
|
||||
## <a href="" id="sec12"></a>Monitoring
|
||||
|
||||
On the deployment share, you also can enable monitoring. After you enable monitoring, you will see all running deployments in the Monitor node in the Deployment Workbench.
|
||||
|
Reference in New Issue
Block a user