Page 16 of 52 FirstFirst ... 6141516171826 ... LastLast

  1. Join Date : Sep 2015
    Posts : 3
    Windows 10
       2015-09-05 #150

    Kari said: View Post
    I have now removed the warnings from the tutorial and added this note instead:

    Note   Note
    Please notice before proceeding!

    Since the launch, I have now (August 17th 2015) tested various Sysprep scenarios quite extensively. Customizing Windows with the CopyProfile component set to True (Parts Three, Four and Five in this tutorial) was causing issues in earlier builds of Windows 10. Either the Sysprep failed directly, or it caused an endless reboot loop when in OOBE (Part Nine), or it disabled the Start and Search / Cortana when done.

    I now get 100% success rate and can replicate a successful Sysprep run with this simple workaround, Sysprep working perfectly every time and customization / generalization with CopyProfile set to True working perfectly:

    • Disconnect your technician machine used for customizing the Windows image completely from all networks before starting the installation
    • Be sure that you install Windows 10 without entering the product key and without any whatsoever network connection
    • When booted to Audit Mode desktop (Part Two), you can connect the machine to the network to download and install Windows ADK and software
    • As Windows is not activated when booted to Audit Mode when following these guidelines you cannot customize the theme. Use a Windows themepack file instead, for instance creating the theme (colors, backgrounds, sounds, screensaver) you'd like to use for the default user profile on another computer and applying the themepack file on the technician machine before the Sysprep

    You can now run Sysprep normally and without issues.


    Kari


    Whit this procedure OneDrive still not working and the Desktop link in the quick access of my pc not working to.
    I use windows 10 pro build 10240!
      My System SpecsSystem Spec


  2. Join Date : Sep 2015
    Posts : 4
    Windows 10
       2015-09-07 #151

    nicelife90 said: View Post
    Whit this procedure OneDrive still not working and the Desktop link in the quick access of my pc not working to.
    I use windows 10 pro build 10240!
    Kari,
    Maybe you are doing something in your procedure that I have not yet tested: you are not activating the windows with the built-in administrator account! Perhaps the windows activation with the built-in administrator account is the reason for the decline in the search bar.
    Without my computer and I cannot test at the time. I ask the Kari and the others that are running sysprep without activating the windows with the built-in administrator account and verify that the bar search will work.
    To activate the Windows after OOBE to add the product key in your answer files in step specialize and run it with sysprep.

    Example:

    Obs.: with the settings below in OOBE is necessary enter only with the name of the user. I've added some links to the taskbar.
    I have copied the shortcut windows defender to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\System Tools\

    HTML Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DoNotCleanUpNonPresentDevices>false</DoNotCleanUpNonPresentDevices>
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
            <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipRearm>0</SkipRearm>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipAutoActivation>false</SkipAutoActivation>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <CopyProfile>true</CopyProfile>
                <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>0416:00010416</InputLocale>
                <SystemLocale>00000416</SystemLocale>
                <UILanguage>00000416</UILanguage>
                <UserLocale>00000416</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>
                <TaskbarLinks>
                    <Link0>%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\System Tools\Windows Defender.lnk</Link0>
                    <Link1>%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\CyberLink Power2Go 9\CyberLink Power2Go 9.lnk</Link1>
                    <Link2>%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Google Chrome\Google Chrome.lnk</Link2>
                </TaskbarLinks>
                <TimeZone>E. South America Standard Time</TimeZone>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:e:/operating_systems/win10pro_x64/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
      My System SpecsSystem Spec


  3. Join Date : Sep 2015
    Posts : 1
    Win 10 pro
       2015-09-11 #152

    Hi Kari.
    Thank you for a great guide, I seem to run into problems.
    I created the answer file and also deployed a win 10 through my deployment server but if I put in the licence key the local user admin account is disabled and also the account that i created when I installed the image, how to go around that, I have around 150 computers so I really try to make the installation as automaticlly as possible.


    Kind regards Lars
      My System SpecsSystem Spec


  4. Join Date : Oct 2013
    A Finnish ex-pat in Germany
    Posts : 9,068
    Windows 10 Pro
       2015-09-11 #153

    duferdias said: View Post
    Maybe you are doing something in your procedure that I have not yet tested: you are not activating the windows with the built-in administrator account! Perhaps the windows activation with the built-in administrator account is the reason for the decline in the search bar.
    The sysprep seems to have a minor bug; if any user accounts exist when the machine is sysprepped, the existing user in most cases lose both the Start and the Search.

    As far as I know there's no other workaround than not to sysprep an existing Windows installation but instead only use sysprep in Audit Mode before any user accounts have been created, or create a new user account to replace the not working one and copy the data over. Start and Search will work on all new user accounts created after the sysprep.

    Due this bug I cannot recommend using sysprep on an existing installation.

    Psypher DK said: View Post
    Hi Kari.
    Thank you for a great guide, I seem to run into problems.
    I created the answer file and also deployed a win 10 through my deployment server but if I put in the licence key the local user admin account is disabled and also the account that i created when I installed the image, how to go around that, I have around 150 computers so I really try to make the installation as automaticlly as possible.
    I am sorry but I do not understand what you mean with "local user account is disabled". The sysprep does not disable local accounts but it by default disables the built-in administrator account.

    The easiest way to make the built-in administrator account active after the sysprep, when the OOBE boot is run is to add a so called Synchronous Command to the answer file to activate it when the initial end user boots to desktop first time.

    To do this, add the net user Administrator /active:yes command from the Insert menu in Windows System Image Manager to the answer file like this:
    Click image for larger version. 

Name:	2015-09-11_13h04_28.png 
Views:	221 
Size:	45.4 KB 
ID:	36877

    Kari
    Last edited by Kari; 2015-09-11 at 12:58.
      My System SpecsSystem Spec


  5. Join Date : Sep 2015
    Posts : 2
    Windows 7 Enterprise
       2015-09-11 #154

    Remove Edge from the Taskbar permanently


    I'm setting up an image for my office and the higher up's have requested that Edge not be available on the Taskbar. How do I get it off of the default profiles taskbar so that any other user account logins will not have it either? I've already figured out how to add additional taskbar icons via the unattend.xml file during sysprep, but that has no effect on the Edge links availability.
      My System SpecsSystem Spec


  6. Join Date : Jul 2015
    Posts : 147
    Windows 10 x64
       2015-09-11 #155

    Kari, if you go into Audit Mode like you always do, create a new user account, log out of the Administrator account, login to that new user account, customize the account, and then Sysprep it like you always do, do you have the Start and Search problem?
      My System SpecsSystem Spec


  7. Join Date : Oct 2013
    A Finnish ex-pat in Germany
    Posts : 9,068
    Windows 10 Pro
       2015-09-11 #156

    jfreemont said: View Post
    Kari, if you go into Audit Mode like you always do, create a new user account, log out of the Administrator account, login to that new user account, customize the account, and then Sysprep it like you always do, do you have the Start and Search problem?
    To be honest, I have never even tried that. I really see no point in it. Anyway, I do not have any Start and Search issues when customizing the default profile in Audit Mode, creating users in answer file and sysprepping, or create the user in OOBE.

    When I customize the default user profile, I want to do it once for all future user accounts created on any system I deploy that image to, regardless of the the name of the user.
      My System SpecsSystem Spec


  8. Join Date : Jul 2015
    Posts : 147
    Windows 10 x64
       2015-09-12 #157

    Kari said: View Post
    To be honest, I have never even tried that. I really see no point in it. Anyway, I do not have any Start and Search issues when customizing the default profile in Audit Mode, creating users in answer file and sysprepping, or create the user in OOBE.

    When I customize the default user profile, I want to do it once for all future user accounts created on any system I deploy that image to, regardless of the the name of the user.
    How can you say there is no point in it? You would do it because the method you are describing is only good in a simple office. In public/kiosk computers where there will be no other user accounts, creating a user account before Sysprep is important. Making a user after Sysprep is no good for those computers...

    I will test later if making the user in Audit Mode fixes the issue and report back.I will be using 10532 because it is the newest.
      My System SpecsSystem Spec


  9. Join Date : Oct 2013
    A Finnish ex-pat in Germany
    Posts : 9,068
    Windows 10 Pro
       2015-09-12 #158

    jfreemont said: View Post
    How can you say there is no point in it?
    How can I say that? Like this, read my lips : It is totally absolutely most profoundly extremely pointless!

    jfreemont said: View Post
    You would do it because the method you are describing is only good in a simple office. In public/kiosk computers where there will be no other user accounts, creating a user account before Sysprep is important. Making a user after Sysprep is no good for those computers...
    In that case create the user in answer file. Creating a user in Audit Mode, then signing out from the built-in admin account to customize that account, and only then sysprep, I would never do that in any circumstances. The correct procedure is to use the sysprep and answer file to create users if they are needed in the image, or if a no users image is needed forget it.

    Kari


    EDIT:

    Like this, creating a password protected local admin and a standard guest user without password:
    Click image for larger version. 

Name:	2015-09-13_01h59_58.png 
Views:	466 
Size:	92.1 KB 
ID:	37189

    Extract from the answer file:

    Code:
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>VABpAHQAeQBzAG8AZgB0ADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Main user</Description>
                            <DisplayName>Admin</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Admin</Name>
                        </LocalAccount>
                        <LocalAccount wcm:action="add">
                            <Description>Kiosk user</Description>
                            <DisplayName>Guest User</DisplayName>
                            <Group>Users</Group>
                            <Name>Guest User</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>
    Last edited by Kari; 2015-09-12 at 19:15.
      My System SpecsSystem Spec


  10. Join Date : Jul 2015
    Posts : 147
    Windows 10 x64
       2015-09-12 #159

    Kari said: View Post
    How can I say that? Like this, read my lips : It is totally absolutely most profoundly extremely pointless!


    In that case create the user in answer file. Creating a user in Audit Mode, then signing out from the built-in admin account to customize that account, and only then sysprep, I would never do that in any circumstances. The correct procedure is to use the sysprep and answer file to create users if they are needed in the image, or if a no users image is needed forget it.

    Kari


    EDIT:

    Like this, creating a password protected local admin and a standard guest user without password:
    Click image for larger version. 

Name:	2015-09-13_01h59_58.png 
Views:	466 
Size:	92.1 KB 
ID:	37189

    Extract from the answer file:

    Code:
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>VABpAHQAeQBzAG8AZgB0ADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Main user</Description>
                            <DisplayName>Admin</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Admin</Name>
                        </LocalAccount>
                        <LocalAccount wcm:action="add">
                            <Description>Kiosk user</Description>
                            <DisplayName>Guest User</DisplayName>
                            <Group>Users</Group>
                            <Name>Guest User</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>
    That won't work. If you need programs to be set a certain way, you can't do that because you are not supposed to open programs in Audit Mode. If you open some programs in Audit Mode and it copies those settings to default profile, you are going to have problems. We tried your method with Illustrator CS6, and we had a TON of problems because the settings are for Administrator account and not the new user.

    So we started to create the user before Sysprep, make customizations, then Sysprep. Tada! No problems. Works in WinXP/Vista/7/8/8.1. Also worked with RTM 10240 Win10, but I have not tried recent builds. I suspect an update is causing the Search and Start problem.
      My System SpecsSystem Spec


 
Page 16 of 52 FirstFirst ... 6141516171826 ... LastLast


Similar Threads
Tutorial Category
Default User Profile - Customize in Windows 10
How to Customize Default User Profile for New Accounts in Windows 10 Default User Profile is stored in a hidden folder in main profile folder Users. When a new user is created, either when installing Windows or any time later, Windows uses this...
Tutorials
Customize the Windows 10 Log-On and Log-Off Screen
how Customize the Windows 10 Log-On and Log-Off Screen in Build 10240? i like a black color! :confused:
Customization
Sysprep fails - Windows 10 build 10162
Hello Guys I'm trying to sysprep a Windows 10 Enterprise build 10162 so that i can capture, but i'm getting some errors and hope you guys have some sort of solution. I've tried removing The upgrade key in HKLM system, but that didn't help. ...
Installation and Setup
Sysprep fails fatally Windows 10 10122
I've tried to go into AUDIT mode to change the User profiles over to a different HDD on 10122. I get a fatal sysprep error. All i've used is an answer file with User profiles set to I:\Users Program Data is not moved, copyprofile not set. Only...
Installation and Setup
NCC Group to audit OpenSSL for security holes
Read more: NCC Group to audit OpenSSL for security holes | ZDNet
Windows 10 News
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:53.
Find Us
Twitter Facebook Google+



Windows 10 Forums