![]() ![]() Sign back on to the computer, and start the Windows runtime-based apps to verify that your customizations work as intended.Īfter you validate your Windows runtime-based apps, reset the FilterAdministrationToken registry entry to 0. Select FilterAdministrationToken, and then type 1 as the value data. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken To test Windows Runtime-based apps, modify the registry as follows:įrom an elevated command prompt, run Regedit.exe. Verify that your customizations work as intended. For more information, see Boot Windows to Audit Mode or OOBE. Start the computer in audit mode by using an answer file or by pressing Ctrl+Shift+F3 when OOBE starts. To test the user profile customizations in audit mode Sign in to the computer by using the user account that was specified during OOBE, and verify that your apps and customizations appear. After you complete OOBE, the Windows start screen appears. To test the user profile customizations after OOBEĪfter Windows installs, go through OOBE and specify the computer name, user account name, and other items. To run Windows runtime-based apps in audit mode, you must modify a registry entry. You can go through Out-Of-Box Experience (OOBE) to test the user experience, or you can test the user customizations in audit mode.Īpps that are based on the Windows runtime won't start in audit mode because audit mode uses the built-in administrator account. Test the user profile customizationsĪfter you deploy the customized image to a destination computer, you can use that computer to test the user profile customizations. For more information, see Create bootable WinPE media and Capture and apply a Windows image using a single. Use DISM to capture and then deploy the Windows installation. To do this, start the computer in the Windows PE environment. For more information, see Sysprep (Generalize) a Windows installation.Īfter you generalize the image and the computer shuts down, capture the image. The Sysprep tool removes computer-specific information from the image, while it preserves the user profile settings that you configured. In this command, F is the letter of the USB flash drive or other removable media. On the reference computer, open an elevated command prompt, and then type this command: C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown /unattend:F:\CopyProfile.xml ![]() For example, you can copy the answer file to a USB drive. For more information, see Sideload Apps with DISM.Īfter you complete the customizations, insert the media that contains the CopyProfile answer file in the reference computer. However, you can create scripts to install additional non-provisioned apps. The number of provisioned Windows runtime-based apps that you can install is limited. Install Windows on a reference computer and start the computer in audit mode. If you install Windows by using another answer file, make sure that answer file doesn't have CopyProfile or any settings that create additional user accounts. Configure the default user profile settingsĬonfigure user settings in audit mode, and then generalize the Windows installation by using an answer file that has CopyProfile set to True. You'll use this answer file when you run Sysprep.įor more information, see Best Practices for Authoring Answer Files and Unattended Windows Setup Reference. Save this answer file as copyprofile.xml. In Windows SIM, create an answer file that has amd64_Microsoft-Windows-Shell-Setup_neutral\ added to Pass 4 - Specialize, and set CopyProfile to True. Create an answer file that includes the CopyProfile setting Now Windows will load the usual Default Applications settings from the oemdefaultassociations.xml file when a user signs in to Windows for the first time. These registry entries are present only after running CopyProfile. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |