mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
comment
This commit is contained in:
Greg Lindsay
@ -162,6 +162,7 @@ A reference image serves as the foundation for Windows 10 devices in your organi
|
||||
OSInstall=Y
|
||||
AdminPassword=pass@word1
|
||||
TimeZoneName=Pacific Standard Time
|
||||
OSDComputername=#Left("PC-%SerialNumber%",7)#
|
||||
JoinWorkgroup=WORKGROUP
|
||||
HideShell=YES
|
||||
FinishAction=SHUTDOWN
|
||||
|
||||
@ -418,7 +418,8 @@ If you have already completed steps in [Deploy Windows 10 in a test lab using Mi
|
||||
DoCapture=YES
|
||||
OSInstall=Y
|
||||
AdminPassword=pass@word1
|
||||
TimeZoneName=Pacific Standard Time
|
||||
TimeZoneName=Pacific Standard TimeZoneName
|
||||
OSDComputername=#Left("PC-%SerialNumber%",7)#
|
||||
JoinWorkgroup=WORKGROUP
|
||||
HideShell=YES
|
||||
FinishAction=SHUTDOWN
|
||||
@ -707,7 +708,7 @@ If you have already completed steps in [Deploy Windows 10 in a test lab using Mi
|
||||
|
||||
5. At the command prompt, type **explorer.exe** and review the Windows PE file structure.
|
||||
|
||||
7. The smsts.log file is critical for troubleshooting any installation problems that might be encountered. Depending on the deployment phase, the smsts.log file is created in different locations:
|
||||
6. The smsts.log file is critical for troubleshooting any installation problems that might be encountered. Depending on the deployment phase, the smsts.log file is created in different locations:
|
||||
- X:\windows\temp\SMSTSLog\smsts.log before disks are formatted.
|
||||
- x:\smstslog\smsts.log after disks are formatted.
|
||||
- c:\_SMSTaskSequence\Logs\Smstslog\smsts.log before the System Center Configuration Manager client is installed.
|
||||
@ -722,8 +723,49 @@ If you have already completed steps in [Deploy Windows 10 in a test lab using Mi
|
||||
|
||||
9. Close the Map Network Drive window, the Explorer window, and the command prompt.
|
||||
|
||||
4. The **Windows 10 Enterprise x64** task sequence is selected in the Task Sequenc Wizard. Click **Next** to continue with the deployment.
|
||||
10. The **Windows 10 Enterprise x64** task sequence is selected in the Task Sequenc Wizard. Click **Next** to continue with the deployment.
|
||||
|
||||
11. The task sequence will require several minutes to complete. You can monitor progress of the task sequence using the MDT Deployment Workbench under Deployment Shares > MDTProduction > Monitoring. The task sequence will:
|
||||
- Install Windows 10
|
||||
- Install the Configuration Manager client and hotfix
|
||||
- Join the computer to the contoso.com domain
|
||||
- Install any applications that were specified in the reference image
|
||||
|
||||
12. When Windows 10 installation has completed, sign in to PC4 using the **contoso\administrator** account.
|
||||
|
||||
13. Right-click **Start**, click **Run**, type **control appwiz.cpl**, press ENTER, click Turn Windows features on or off, and verify that **.NET Framework 3.5 (includes .NET 2.0 and 3.0)** is installed. This is a feature included in the reference image.
|
||||
|
||||
14. Shut down the PC4 VM.
|
||||
|
||||
## Refresh a client with Windows 10 using Configuration Manager
|
||||
|
||||
1. Verify that PC1 is in its original state, which was saved as a checkpoint in [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md).
|
||||
|
||||
2. If a PC1 checkpoint has not already been saved, then save a checkpoint by typing the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:
|
||||
|
||||
```
|
||||
Checkpoint-VM -Name PC1 -SnapshotName BeginState
|
||||
```
|
||||
|
||||
3. Sign in to PC using the contoso\administrator account and type the following at an elevated command prompt:
|
||||
|
||||
|
||||
|
||||
CCMSetup.exe /mp:PS1 /logon SMSSITECODE=AUTO
|
||||
|
||||
3. On SRV1, in the Configuration Manager console, in the Asset and Compliance workspace, right-click **Device Collections** and then click **Create Device Collection**.
|
||||
|
||||
4. Use the following settings in the **Create Device Collection Wizard**:
|
||||
- General > Name: **Install Windows 10 Enterprise x64**<BR>
|
||||
- Geneneral > Limiting collection: **All Systems**<BR>
|
||||
- Membership Rules > Add Rule: **Direct Rule**<BR>
|
||||
- The **Create Direct Membership Rule Wizard** opens, click **Next**<BR>
|
||||
- Search for Resources > Resource class: **System Resource**<BR>
|
||||
- Search for Resources > Attribute name: **Name**<BR>
|
||||
- Search for Resources > Value: **PC1**<BR>
|
||||
- Select Resources > Value: **PC1**<BR>
|
||||
|
||||
## Replace a client with Windows 10 using Configuration Manager
|
||||
|
||||
## Related Topics
|
||||
|
||||
|
||||
@ -14,11 +14,13 @@ author: greg-lindsay
|
||||
|
||||
- Windows 10
|
||||
|
||||
This guide contains instructions to configure a proof of concept (PoC) environment requiring a minimum amount of resources. The guide makes extensive use of Windows PowerShell and Hyper-V. Subsequent companion guides contain steps to deploy Windows 10 using the PoC environment. After completing this guide, see the following Windows 10 deployment guides:
|
||||
This guide contains instructions to configure a proof of concept (PoC) environment requiring a minimum amount of resources. The guide makes extensive use of Windows PowerShell and Hyper-V. Subsequent companion guides contain steps to deploy Windows 10 using the PoC environment. After completing this guide, see the following Windows 10 PoC deployment guides:
|
||||
|
||||
- [Step by step: Deploy Windows 10 in a test lab using MDT](windows-10-poc-mdt.md)<BR>
|
||||
- [Step by step: Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md)<BR>
|
||||
|
||||
The PoC deployment guides are intended to provide a demonstration of Windows 10 deployment tools and processes for IT professionals that are not familiar with these tools, and those that are interested in configuring a proof of concept environment for their own purposes. The instructions in this guide should not be used in a production setting, and are not meant to replace the instructions found in production deployment guidance.
|
||||
|
||||
Approximately 3 hours are required to configure the PoC environment. You will need a Hyper-V capable computer running Windows 8.1 or later with at least 16GB of RAM. Detailed [requirements](#hardware-and-software-requirements) are provided below. You will also need to have a [Microsoft account](https://www.microsoft.com/account) to use for downloading evaluation software.
|
||||
|
||||
Windows PowerShell commands are provided to set up the PoC environment quickly. You do not need to be an expert in Windows PowerShell to complete the steps in the guide, however you are required to customize some commands to your environment.
|
||||
@ -31,7 +33,7 @@ Hyper-V is installed, configured and used extensively in this guide. If you are
|
||||
|
||||
This guide contains instructions for three general procedures: Install Hyper-V, configure Hyper-V, and configure VMs. If you already have a computer running Hyper-V, you can use this computer and skip the first procedure. In this case, your virtual switch settings must be modified to match those used in this guide, or the steps in this guide can be modified to use your existing Hyper-V settings.
|
||||
|
||||
After completing the instructions in this guide, you will have a PoC environment that enables you to test Windows 10 deployment procedures with current tools, as documented in subsequent guides. Links are provided to download trial versions of Windows Server 2012, Windows 10 Enterprise, and all deployment tools necessary to complete the lab.
|
||||
After completing the instructions in this guide, you will have a PoC environment that enables you to test Windows 10 deployment procedures by following instructions in companion guides that are written to use the PoC environment. Links are provided to download trial versions of Windows Server 2012, Windows 10 Enterprise, and all deployment tools necessary to complete the lab.
|
||||
|
||||
Topics and procedures in this guide are summarized in the following table. An estimate of the time required to complete each procedure is also provided. Time required to complete procedures will vary depending on the resources available to the Hyper-V host and assigned to VMs, such as processor speed, memory allocation, disk speed, and network speed.
|
||||
|
||||
@ -250,6 +252,8 @@ w10-enterprise.iso
|
||||
|
||||
### Convert PC to VM
|
||||
|
||||
>Important: Do not attempt to use the VM resulting from the following procedure as a reference image. Also, to avoid conflicts with existing clients, do not start the VM outside the PoC network.
|
||||
|
||||
<TABLE BORDER=2><TR><TD>
|
||||
If you do not have a PC available to convert to VM, perform the following steps to download an evaluation VM:
|
||||
<BR>
|
||||
|
||||
Reference in New Issue
Block a user