Configuration manager console for windows 10.Deploy Windows 10 in a test lab using Configuration Manager

Looking for:

- Install SCCM Admin Console On Windows 10 - the Sysadmin Channel 

Click here to DOWNLOAD

   

 

What is Configuration Manager? - Configuration Manager | Microsoft Docs.

 

Details Version:. File Name:. Date Published:. File Size:. System Requirements Supported Operating System. Install Instructions To enable Company Portal app functionality a registry key must be present on target devices. This allows the Configuration Manager agent to communicate with the Company Portal app.

Deploy the registry value specified above to all clients on which the Company Portal app will be installed. This can be done via Group Policy, the Compliance Settings feature of Configuration Manager, or any other method applicable in your organization.

Deploy the Company Portal app. You can deploy this app to Windows 8 or Windows 8. In this first deployment scenario, you'll deploy Windows 10 using PXE. This scenario creates a new computer that doesn't have any migrated users or settings.

In the Task Sequence Wizard, provide the password: pass word1 , and then select Next. A command prompt will open. At the command prompt, type explorer. The smsts. Depending on the deployment phase, the smsts. Note: If a reboot is pending on the client, the reboot will be blocked as long as the command window is open.

In the explorer window, select Tools and then select Map Network Drive. Don't map a network drive at this time. If you need to save the smsts. Select Next to continue with the deployment. The task sequence will require several minutes to complete. The task sequence will:. Right-click Start , select Run , type control appwiz.

This feature is included in the reference image. The following two procedures 1 Replace a client with Windows 10 and 2 Refresh a client with Windows 10 have been exchanged in their order in this guide compared to the previous version.

If this is your first time going through this guide, you won't notice any change, but if you have tried the guide previously then this change should make it simpler to complete. Before you start this section, you can delete computer objects from Active Directory that were created as part of previous deployment procedures.

There should be at least two computer accounts present in the contoso. It's not required to delete the stale entries, this action is only done to remove clutter. In the replace procedure, PC1 won't be migrated to a new OS.

It's simplest to perform this procedure before performing the refresh procedure. After you refresh PC1, the OS will be new. The next replace procedure doesn't install a new OS on PC1 but rather performs a side-by-side migration of PC1 and another computer PC4 , to copy users and settings from PC1 to the new computer.

Select OK and then select Next to continue. On the Settings Package page, browse and select the Windows 10 x64 Settings package. If an error is displayed at this stage, it can be caused by a corrupt MDT integration. This VM represents a new computer that will replace PC1. In a real-world scenario, you must determine the MAC address of the new computer.

Verify that the PC1 VM is running and in its original state, which was saved as a checkpoint and then restored in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit.

If you haven't already saved a checkpoint for PC1, then do it now. If you don't see the computer account for PC1, select Refresh in the upper right corner of the console. The Client column indicates that the Configuration Manager client isn't currently installed. This procedure will be carried out next.

This command requires an elevated command prompt , not an elevated Windows PowerShell prompt. It might be necessary to manually remove these settings if they are present.

For more information, see Manual removal of the Configuration Manager client. From an elevated command prompt, type:. Verify that both services were stopped successfully, then type the following command at an elevated command prompt:. To install the Configuration Manager client as a standalone process, type the following command at an elevated command prompt:.

During client installation, files will be downloaded here. You can periodically open this file in notepad, or you can type the following command at an elevated Windows PowerShell prompt to monitor installation progress:. Installation might require several minutes, and display of the log file will appear to hang while some applications are installed.

This behavior is normal. When setup is complete, verify that CcmSetup is existing with return code 0 is displayed on the last line of the ccmsetup. If you're viewing the log file in Windows PowerShell, the last line will be wrapped. On PC1, open the Configuration Manager control panel applet by typing the following command from a command prompt:. The client will report that it has found the PS1 site.

A common reason the client can't locate the site code is because a previous configuration exists. This node will be added under Devices. You might have to refresh the view and wait few minutes for the client to appear here.

It might take several minutes for the client to fully register with the site and complete a client check. When it's complete you will see a green check mark over the client icon as shown above. To refresh the client, select it and then press F5 or right-click the client and select Refresh. Double-click the Install Windows 10 Enterprise x64 device collection and verify that the PC1 computer account is displayed. On the Select Source page, choose Import single computer and select Next.

Select Next , and on the User Accounts page choose Capture and restore specified user accounts , then select the yellow starburst next to User accounts to migrate. Select Browse and then under Enter the object name to select type user1 and select OK twice. In the Assets and Compliance workspace, select User State Migration and review the computer association in the display pane. Right-click the association in the display pane and then select Specify User Accounts.

You can add or remove user account here. Select OK. Right-click the association in the display pane and then select View Recovery Information. You'll see that a recovery key has been assigned, but a user state store location hasn't.

Select Close. Verify that PC4 is displayed in the collection. You might have to update and refresh the collection, or wait a few minutes, but don't proceed until PC4 is available. Don't proceed until this name is displayed. On PC1, open the Configuration Manager control panel applet by typing the following command in a command prompt:. This method is one that you can use to run a task sequence in addition to the Client Notification method that will be demonstrated in the computer refresh procedure.

You should see an alert that new software is available. Setup will install the OS using the Windows 10 Enterprise x64 reference image, install the configuration manager client, join PC4 to the domain, and restore users and settings from PC1. Save checkpoints for all VMs if you wish to review their status at a later date. This action isn't required, as checkpoints do take up space on the Hyper-V host. So you can't return to a previous checkpoint only on the PC1 VM without a conflict.

Therefore, if you do create a checkpoint, you should do this action for all VMs. The computer will restart several times during the installation process. Installation includes downloading updates, reinstalling the Configuration Manager Client Agent, and restoring the user state. You can view status of the installation in the Configuration Manager console by accessing the Monitoring workspace, clicking Deployments , and then double-clicking the deployment associated with the Install Windows 10 Enterprise x64 collection.

Under Asset Details , right-click the device and then select More Details. Select the Status tab to see a list of tasks that have been performed. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode.

Table of contents. Important This guide uses the proof of concept PoC environment, and some settings that are configured in the following guides: Step by step guide: Deploy Windows 10 in a test lab Deploy Windows 10 in a test lab using the Microsoft Deployment Toolkit Complete all steps in these guides before you start the procedures in this guide.

Note If the request to add features fails, retry the installation by typing the command again. Note If the internal network adapter, assigned an IP address of Note Since we aren't installing applications in this test lab, there's no need to enable the Windows Update Pre-Application Installation step. Note If content distribution isn't successful, verify that sufficient disk space is available.

Tip Complete this section slowly. There are a large number of similar settings from which to choose. Note The following two procedures 1 Replace a client with Windows 10 and 2 Refresh a client with Windows 10 have been exchanged in their order in this guide compared to the previous version. Note Before you start this section, you can delete computer objects from Active Directory that were created as part of previous deployment procedures. Note If an error is displayed at this stage, it can be caused by a corrupt MDT integration.

Tip If you don't see the computer account for PC1, select Refresh in the upper right corner of the console. Note This command requires an elevated command prompt , not an elevated Windows PowerShell prompt. Note It might take several minutes for the client to fully register with the site and complete a client check. Submit and view feedback for This product This page. View all page feedback.

In this article. Install Microsoft Endpoint Configuration Manager. Download Microsoft Endpoint Configuration Manager, configure prerequisites, and install the package. Prepare for Zero Touch installation.

 

- Console extensions for Configuration Manager - Configuration Manager | Microsoft Docs

 

The All Windows 10 ARM64 platform is available in the list of supported OS versions on objects with requirement rules or applicability lists. If you previously selected the top-level Windows 10 platform, this action automatically selected both All Windows 10 bit and All Windows 10 bit. OS deployment isn't supported, except for a feature update task sequence. Starting in version , you can deploy a task sequence with a feature update to a Windows 10 on ARM64 device.

For more information, see Deploy a feature update with a task sequence. You can update and service Windows Insider builds. This ability is provided as a convenience to our customers. While this functionality should work, the support for it is best effort. Configuration Manager might not issue a hotfix for this functionality if it ceases to function.

To provide feedback on Windows Insider, use the Feedback Hub. If you manually customize a reference computer that runs Windows 10, version 20H2, and then use capture media , Windows Sysprep fails with the following entry in the sysprep. This issue happens when you sign in to the device and create a user profile. Use the default image file install. Use the task sequence to apply configurations at run time.

Create a task sequence to capture an OS. Remove appx packages for the signed-in user before you use capture media. For more information, see Sysprep fails after you remove or update Microsoft Store apps that include built-in Windows images. This can be done via Group Policy, the Compliance Settings feature of Configuration Manager, or any other method applicable in your organization.

Deploy the Company Portal app. You can deploy this app to Windows 8 or Windows 8. Note: The Company Portal app may take up to 15 minutes after installation before it is fully operational Recommendations and Best Practices Consider the following when deploying the Company Portal app in your environment.

The Company Portal app utilizes the default Application Catalog Website Point assigned to the device when communicating with the Configuration Manager infrastructure.

If you have multiple primary sites in a hierarchy, we strongly recommend adding a set of Application Catalog roles for each of the primary sites, and using Automatic detection to control the default Application Catalog Website Points. When the user browses the list of applications in the Company Portal, the app will display the applications that have been made available to the user, similar to the Configuration Manager Application Catalog functionality.

In the tool, select File , select Open , and then open the distmgr. If errors are present, they will be highlighted in red:. The log file is updated continuously while Configuration Manager is running. Close CMTrace when done. You'll see the following line in distmgr. If you have a bitmap. Otherwise, use the following step to copy a branding image. On the Options page, under Platform choose x64 , and select Next.

It will take a few minutes to generate the boot image. Use the CMTrace application to view the distmgr. In the trace tool, select Tools on the menu and choose Find. For example:. Double-click Zero Touch WinPE x64 under Content Status in the console tree and verify that a status of Successfully distributed content is displayed on the Success tab.

Review the distmgr. The third is the new boot image with DaRT. If you've already completed steps in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then you've already created a Windows 10 reference image.

In this case, skip to the next procedure in this guide: Add a Windows 10 OS image. If you've not yet created a Windows 10 reference image, complete the steps in this section. The first step in creating a deployment share is to mount this file on SRV1.

To open the deployment workbench, select Start , type deployment , and then select Deployment Workbench. Right-click the Operating Systems node, and then select New Folder. Name the new folder Windows Complete the wizard using default values and select Finish. Right-click the Windows 10 folder created in the previous step, and then select Import Operating System.

For purposes of this test lab, we won't add applications, such as Microsoft Office, to the deployment share. For more information about adding applications, see Add applications. The next step is to create a task sequence to reference the OS that was imported.

Use the following settings for the New Task Sequence Wizard:. To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step. Select the Task Sequence tab. A new group will be added under Tattoo. To see the name change, select Tattoo , then select the new group again. Under Select the roles and features that should be installed , select.

NET Framework 3. NET 2. Enable Windows Update in the task sequence by clicking the Windows Update Post-Application Installation step, clicking the Options tab, and clearing the Disable this step checkbox. Since we aren't installing applications in this test lab, there's no need to enable the Windows Update Pre-Application Installation step. However, you should enable this step if you're also installing applications. The next step is to configure the MDT deployment share rules. Select Apply and then select Edit Bootstrap.

Replace the contents of the Bootstrap. The update process will take 5 to 10 minutes. When it has completed, select Finish.

Accept the default values on the Capture Image page, and select Next. OS installation will complete after 5 to 10 minutes and then the VM will reboot automatically. Allow the system to boot normally, don't press a key. The process is fully automated. Other system restarts will occur to complete updating and preparing the OS. Setup will complete the following procedures:. This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host and your network's download speed.

After some time, you'll have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. Make sure there's no space at the end of the location or you'll get an error. Select Windows 10 Enterprise x64 and monitor the status of content distribution until it's successful and no longer in progress.

Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh. Processing of the image on the site server can take several minutes. This action adds a new step immediately after Set Status 5. In this case, skip the first four steps below and begin with step 5 to edit CustomSettings. Select the Monitoring tab, select the Enable monitoring for this deployment share checkbox, and then select OK.

For example, the following option will capture settings from all user accounts:. In this first deployment scenario, you'll deploy Windows 10 using PXE. This scenario creates a new computer that doesn't have any migrated users or settings.

In the Task Sequence Wizard, provide the password: pass word1 , and then select Next. A command prompt will open. At the command prompt, type explorer. The smsts. Depending on the deployment phase, the smsts. Note: If a reboot is pending on the client, the reboot will be blocked as long as the command window is open. In the explorer window, select Tools and then select Map Network Drive.

Don't map a network drive at this time. If you need to save the smsts. Select Next to continue with the deployment.