Customize Windows 10 Image in Audit Mode with Sysprep  

Page 59 of 70 FirstFirst ... 949575859606169 ... LastLast

  1. Posts : 4
    Windows 10 (and older)
       #580

    georg49 said:
    ....... After Sysprep/Shutdown the configured Master-Disk (with the "copyprofile" option in the unattend.xml) open the the Image offline and delete the Folder "INetCache" in the "Default"-profile

    Path: [Driveletter]:\Users\Default\AppData\Local\Microsoft\Windows\INetCache

    !!! >>>> Correction: The delete has to be done for the "Administrator" profile but not the "Default".
    Cause: The copyprofile will be performed only during the next boot of the system. Bevore that the INetCache-folder of the Default profile is empty of course. And according to my later expiriences you only have to delete the file "counters2.dat" in the Folder. This seems to be the reason of the problem.

    If you already have a system with the faulty copyprofile-copied "counters2.dat" in this case you would delete it in the "Default" profile and/or any other userprofile. But not at the signed in userprofile cause the file is locked.

    Hint: At "https://technet.microsoft.com/en-us/sysinternals/pendmoves.aspx" you find a tool/solution to delete a file at next reboot. It only makes a single registry-entry which you may extract into a delete-counters2.reg file for further usage independant from the tool.
    I applied & tested it for C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache\counters2.dat and that works. This way it's not necessary to offline-edit the deployed image after shutdown.
    <<<<< End of correction
    fiyahflash said:
    Confirmed that deleting C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache, C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat, as well as C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache from the Administrator account that was created via MDT when the system booted, resolved the search issues for any new users that logged on to the system (both non-domain and domain).Trying to figure out now how to resolve this from MDT, in order to remove this manual stepLoading the WIM file into DISM shows that the C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache is not present.

    Found the solution over at Technet Forums: Windows 10 Creators - sysprep image
    Hi fiyahflash
    I made a correction to my former post. There I pointed to the wrong path rsp. userprofile. Sorry if that made troubles to got it to work.

    Thank you for the tip about the solution in TechNet. But the SetupComplete.cmd does not work for "OEM" versions , cause this option is deactivated there. For such versions I added an alternative solution, which could work in general.

    According to my tests I didn't find any issues with WebCache folder and WebCacheLock.dat or other stuff in the INetCache folder except the counters2.dat file. But it may not be a mistake to delete them also. Important: It has to be done in the "Default" profile after the system was rebooted but otherwise in the "Administrator" profile in an offline-image-modification before reboot or if using the sysinternals "movefile.exe" tool rsp. "PendingFileRenameOperations" option in registry.
      My Computer


  2. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #581

    Kari said:
    Yes, it is possible and can be done exactly as told on that article you linked to. Personally I think that it is not necessary, especially when talking about private users, home or small networks and Windows 10 which is extremely capable to find out correct drivers by itself.

    Kari
    Thanks, Kari. Yes, it does find drivers, but most are MS generic ones. I want to install specific drivers for devices/peripherals/components for a specific MoBo.
      My Computers


  3. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #582

    HippsieGypsie said:
    Thanks, Kari. Yes, it does find drivers, but most are MS generic ones. I want to install specific drivers for devices/peripherals/components for a specific MoBo.
    If image will only be used on matching hardware, you can simply install all drivers in Audit Mode, then add <PersistAllDeviceInstalls>true>PersistAllDeviceInstalls> in answer file, in Pass 3 Generalize. This keeps drivers even when /generalize switch is used with Sysprep.

    To use PersistAllDeviceInstalls, add this code extract to your answer file:

    Code:
    <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">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
        </component>
    </settings>

    Another option is to generalize image normally, then add drivers to offline image with DISM: Add and Remove Drivers to an Offline Windows Image
    Kari
      My Computer


  4. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #583

    Kari said:
    If image will only be used on matching hardware, you can simply install all drivers in Audit Mode, then add <PersistAllDeviceInstalls>true>PersistAllDeviceInstalls> in answer file, in Pass 3 Generalize. This keeps drivers even when /generalize switch is used with Sysprep.

    To use PersistAllDeviceInstalls, add this code extract to your answer file:

    Code:
    <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">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
        </component>
    </settings>

    Another option is to generalize image normally, then add drivers to offline image with DISM: Add and Remove Drivers to an Offline Windows Image
    Kari
    Thank you for all that, Kari. :)

    Yes, I understand > Specific drivers to match specific hardware. I'll take the other option in consideration also.
      My Computers


  5. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #584

    HippsieGypsie said:
    Yes, I understand > Specific drivers to match specific hardware. I'll take the other option in consideration also.
    This quote about sums it up why I do not like keeping / installing drivers on custom image, preferring a completely generalized hardware independent image:

    Hardware-configuration changes that are likely to cause problems

    When using the PersistAllDeviceInstalls setting, any hardware change can potentially cause problems. Some changes are more likely to cause problems than others.

    Low risk
    For these types of hardware changes, you may be able to work around potential driver conflicts and still use the PersistAllDeviceInstalls setting:
    • CPUs with different clock speed.
    • Amount of memory.
    • Hard disk capacity.
    • External input devices, such as keyboards and mice.
    • Monitors.

    Medium risk
    For these types of hardware changes, we recommend that you do not use the PersistAllDeviceInstalls setting:
    • Video cards.
    • Storage drives and media readers, such as optical drives and card readers.
    • Internal or integrated bus devices, such as USB or 1394 devices.

    High risk
    For major hardware changes, do not use the PersistAllDeviceInstalls setting:
    • Motherboard chipset or CPU brand.
    • Storage controllers.
    • Form-factor changes, such as from desktop to laptop or from laptop to desktop.
    • Keyboard-layout changes, such as from a standard 101-key keyboard to a Japanese 106-key keyboard.
    • Any other devices that are in the enumeration path of the Windows boot volume.


    Types of problems that can occur with a hardware-configuration change

    Even seemingly minor changes to the hardware or hardware configuration can cause severe or easily-overlooked problems, such as the following:
    • System instability.
    • Inability to use some of the basic or extended functionality of a device.
    • Extended boot times and extended installation times.
    • Misnamed devices in the Devices and Printers folder, Device Manager, and other device-related user interfaces.
    • Severe system problems that leave the computer in a non-bootable state.
    From Maintain Driver Configurations When Capturing a Windows Image

    Kari
      My Computer


  6. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #585

    Kari said:
    This quote about sums it up why I do not like keeping / installing drivers on custom image, preferring a completely generalized hardware independent image:

    Kari
    Thanks again for that, Kari. Don't plan on changing out any of my hardware, but I see the risk if something does need replacing, then I might be in deep doodoo.
      My Computers


  7. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #586

    That quote is from article written for Windows 7. Windows 10 can handle dissimilar hardware better, but for the most the article still applies.
      My Computer


  8. Posts : 15,480
    Windows10
       #587

    Kari said:
    That quote is from article written for Windows 7. Windows 10 can handle dissimilar hardware better, but for the most the article still applies.
    Yeah, Windows 10 driver handling is such that many put an hdd from one pc into a different one, and often works. With Windows 7 (and to lesser degree 8), it was hit or miss if it worked, and even when it did you often get strange issues which are nit easy to track down.

    Of course, good old sysprep is the 'recommended' way to go.

    I installed the infamous 16125 in hyper-v and just tried native booting the vhdx from host pc, and it just worked first time without any driver issues apart from Bluetooth driver needing to be installed.
      My Computer


  9. Posts : 11
    Windows 10 1703
       #588

    I am looking to create a similar image without an OOBE. But, the reboot goes into an infinite loop.
    Please help.
      My Computer


  10. Posts : 11
    Windows 10 1703
       #589

    I am looking to create a similar image without an OOBE. But, the reboot goes into an infinite loop.
    Please help.
      My Computer


 

Tutorial Categories

Customize Windows 10 Image in Audit Mode with Sysprep Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
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:06.
Find Us




Windows 10 Forums