70Pcs imaging all unbranded

dijsil · Jan 29, 2019, 1:47 PM

I work in a company that have approx 70pcs however they are all unbranded so I cannot just download the model drivers of all motherboards.

I am thinking of start using Fog for my deployment as it seems fairly straight forward to configure.

If I create a golden image on a virtual machine, when I boot from the pcs to pull image will they still work and then if I have missing drivers I can install manually after the image is deployed.

Scott B · Jan 29, 2019, 7:48 AM

@dijsil said in 70Pcs imaging all unbranded:

on a virtual machine, when I boot from the pcs to pull image will they still work and then if I have missing drivers I can install manually after the image is deployed.

I’m assuming your using Windows? Windows generic drivers should get the PC to boot after an image but you will have unknown devices under device manager if they are unknown to windows. I’ve pulled down our normal sysprep image down on some unique devices and this was the case. You can always add drivers to your windows install on your sysprep image as well.

george1421 · Jan 29, 2019, 1:50 PM

Yes that will work as you intended. Win10 does a pretty good job at selecting the best common drivers for the hardware especially if the hardware is a few years old.

dijsil · Jan 29, 2019, 8:59 AM

Yes all os will be windows 10, thanks, am currently installing Fog server and got stuck in the below:

bootfile name (what should I write in the DC option 067)
Will it work if I have a Fog server(192.168.0.xxx), DHCP (192.168.0.xxx) on a different network subnet to the client (192.168.10.xxx) - both networks can communicate with each other.

george1421 · Jan 29, 2019, 8:05 PM

@dijsil To answer your questions:

The boot file depends on the firmware mode of the target computer. If you have a bios based computer then the boot file is typically undionly.kpxe if your target computer is uefi based then the typical boot file is ipxe.efi.
Yes having the serves on one subnet and the workstations on another is not a problem. You just need to be sure that for the scope of 192.168.10.x you have the boot server and boot file set properly. Most modern PXE ROMS support pxe booting across subnets. The early ones didn’t.

If your dhcp server is linux or Microsoft 2012 or newer, you can have your dhcp server automatically send the right boot file based on the target computer. The instructions for setting this up can be found here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

dijsil · Jan 30, 2019, 8:50 AM

@george1421 cool thanks, managed to get it up and running and tested across different network all seems ok, tested with undionly.kpxe and managed to boot from network

now trying to follow some guides on how to create an image with an unattended setup.

dijsil · Jan 30, 2019, 9:16 AM

I would like to set the image clean with just windows updates and removing the stupid games and extra stuff that comes with windows 10 and then after its deployed it automatically pulls the software that are placed inside a particular folder on the file server and installs them (so that the software setup placed is always the latest version).

How can I achieve that I know that I can setup GPO however they might take time to deploy, I would like to setup some sort of script(ideally also placed on the file server so that it can be amended when needed) so that on the first boot after being imaged it reads the script that is on the file server and the apps that specify the scrip are installed

ragnurenson · Jan 30, 2019, 11:11 AM

@dijsil You can do using snapins. You can snapin a bath script to do this.
https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
Hope this can help you,

george1421 · Jan 30, 2019, 1:30 PM

@dijsil said in 70Pcs imaging all unbranded:

I would like to set the image clean with just windows updates and removing the stupid games and extra stuff that comes with windows 10 and then after its deployed it automatically pulls the software that are placed inside a particular folder on the file server and installs them (so that the software setup placed is always the latest version).

This next bit is outside of the scope of the FOG Project. But I can say the “right” place to start here is with Microsoft’s Deployment Toolkit (MDT). With MDT (free) you can create your golden image and by using the lite touch process you can end up with a capture ready image with FOG or what ever deployment tool you might use. It sure beats setting up an image in audit mode by hand. With MDT you can automate software installs and windows update application. We use that method to create our golden images (one for bios and one for uefi systems) by simply changing the configuration of the VM that we build the golden image on. For the MDT “server” you don’t need to use a server OS a Win10 system works just fine for your MDT server. Then couple your golden image with your custom unattend.xml file then sysprep and capture with FOG and then deploy.

My golden image is ~25GB in size and I can go from bare metal to a user ready system in about 15 minutes. I did choose to go with a fat image for speed of deployment and in reality our core applications don’t change that frequently. With Microsoft’s twice a year feature upgrade, the base OS changes more often then our application suite.

As for getting rid of the Windows crapware. That one is going to be a bit touch. M$ doesn’t really want companies to do that. There are some automated scripts that can be integrated into MDT like the decrapifier from Spiceworks Community (don’t get it from any other place) that when tuned properly will remove most of the windows “extra” applications. Using LTSB version of Windows use to be an option but M$ is now crippling that to keep certain office productivity applications from installing.

As for post deployment application installations, you can use FOG built in snapin installation tool. In my case I don’t use snapins but use a third party tool call PDQ Deploy. The paid for version can be hooked into your FOG deployment by having a snapin call PDQ Deploy to activate a push deployment of a single application or application group. The PDQ Deploy (free version) will also work but you will need to manually kick off the post install applications.

dijsil · Feb 1, 2019, 5:41 AM

thanks all, I installed windows 10 on a virtual machine on my server, did the changes in audit mode and sysprepped it using the unattended file (followed this video https://www.youtube.com/watch?v=SeZj1jTn2Jg ) my question is my virtual os is switched off and I need to take an image. How can I do that as when I booted to network I only have deploy image and not backup image or something like that.

I tried from fog server and going to capture image however most probably it will not work if my pc is on the network boot fog page or switched off am I right? How can I capture image after sysprepping it.

thanks for your reply @george1421 one step at a time after capturing image will fiddle on how to deploy the apps

ragnurenson · Feb 1, 2019, 11:48 AM

@dijsil If I am right, you have your golden machine with the OS installed, configured and with sysprepped, after all this, you shutdown the vm. This is the right time to upload the image to the FOG server. You must to create a upload image task for this machine, and if you have it in the fog server configured like a host, the machine will boot WOL, and load the FOG client, for upload the image to the server.

This is the image you must to deploy later to the other machines. You don’t need to make nothing more before upload the image, as long the image is a capture of the OS.

george1421 · Feb 1, 2019, 12:28 PM

@dijsil said in 70Pcs imaging all unbranded:

I tried from fog server and going to capture image however most probably it will not work if my pc is on the network boot fog page or switched off am I right? How can I capture image after sysprepping it.

First let me say that @ragnurenson is spot on with his instructions.

Since you built the golden image by hand in audit mode, I would have made a suggestion before you sysprep’d it. Take a vm snapshot of the image before running sysprep. That gives you an option to backup if something needs to be tweaked in your image. Since you built it by hand your only option now is to start over if you need to tweak. I suggest this because I had to tweak my golden image many times when I was first creating it.

For me I have my build out VM registered with FOG. Since I use MDT to build my golden image, the default boot device is the cdrom which is where I have the MDT iso mounted. The second device in the boot order is PXE boot. When I want to create the golden image I have it boot from the cdrom, when I want to capture the image I untick the mount cdrom in the configuration then it pxe boots. When I’m ready to capture the image I sysprep it with the command line option to have sysprep power off the VM. Its important to ensure the VM is powered off correctly and not just shutdown via the start button. If you don’t have sysprep power off the VM use the shutdown -f -s -t 0 command to ensure windows is powered off correctly. Once the VM is shutdown, then I go to the FOG console and schedule a capture task and ensure that I tick the power off after capture option in the scheduled task. If you miss this the golden image VM will reboot after capture and start WinSetup and OOBE loosing any chance to “adjust things” in the golden image. Once the task is scheduled then I untick the cdrom mount option in the configuration and let the golden image VM pxe boot. The VM sees the scheduled FOG capture and uploads it image to the FOG server then powers off.

dijsil · Feb 1, 2019, 3:16 PM

I took a vm snapshot just before I sysprep, I am still trying to enter all the answerfile in order to have an automatic installation as I also would like to just keep the built in admin user enabled with a password and no other user configured on the system.

in order to had it captured I selected the capture icon, forced the task to begin, waited 5 mins and as soon as I started the VM it went straight to imaging.

george1421 · Feb 1, 2019, 5:16 PM

@dijsil said in 70Pcs imaging all unbranded:

forced the task to begin, waited 5 mins

I’m not sure I understand about forcing a task to begin?? When you schedule a task for immediate execution the task should be running waiting for the target computer. It will sit and wait until the target checks in even if its 7 days latter it will be still waiting.

As for the 5 minute wait. The task it launched immediately. There is no need to wait, schedule the capture and pxe boot that fast.

george1421 · Feb 1, 2019, 5:19 PM

@dijsil with the unattend.xml file, just fwiw, there are some pretty good online unattend.xml file generators like this one: http://www.windowsafg.com/ if you use one, just don’t include confidential information like license keys or anything that can personally identify your company. Make the data appropriately. What these tools do is give you a great baseline unattend.xml file to start your customization. The rest you can do by hand or with WAIK.

dijsil · Feb 3, 2019, 9:59 AM

@george1421 thanks managed to get it working. Issue I am encountering now is when the image is ready how fog will deploy images through pdq using snippets

george1421 · Feb 3, 2019, 1:02 PM

@dijsil https://forums.fogproject.org/topic/9577/webcast-imaging-with-fog-managing-with-pdq

dijsil · Feb 4, 2019, 6:12 AM

not sure why but when deploying the image I am encountering this issue when joining the pc with domain.

after installing outlook it is freezing on opening page

installing sage same issue
when clicking on start and start typing the typing doesn’t come

when logging in with local admin user everything works fine. sfc /scannow didn’t fix the issue, after deloying and doing sysprep again it is working fine, so I guess it has to do with the unattended file.

I downloaded the file from: http://www.windowsafg.com/ and choose (Win10 MBR as my pcs are using Bios mode Legacy) and the only thing I amended was the first part so that it would copy the profile settings to the default profile

<!--*************************************************
Windows 10 Answer File Generator
Created using Windows AFG found at:
;http://www.windowsafg.com

Installation Notes
Location: MT
Notes: Enter your comments here...


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
**************************************************-->

<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <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">
            <WindowsFeatures>
                <ShowInternetExplorer>true</ShowInternetExplorer>
            </WindowsFeatures>
            <CopyProfile>true</CopyProfile>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:D:/Sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0809:00000809</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" 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">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0809:00000809</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Type>Primary</Type>
<Size>100</Size>
</CreatePartition>
<CreatePartition wcm:action="add">
<Extend>true</Extend>
<Order>2</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>System Reserved</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
<TypeID>0x27</TypeID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>OS</Label>
<Letter>C</Letter>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
<UserData>
<AcceptEula>true</AcceptEula>
<FullName>Administrator</FullName>
<Organization></Organization>
<ProductKey>
<Key>W269N-WFGWX-YVC9B-4J6C9-T83GX</Key>
</ProductKey>
</UserData>
</component>
<component name="Microsoft-Windows-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">
<DiskConfiguration>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Type>Primary</Type>
<Size>100</Size>
</CreatePartition>
<CreatePartition wcm:action="add">
<Extend>true</Extend>
<Order>2</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>System Reserved</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
<TypeID>0x27</TypeID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>OS</Label>
<Letter>C</Letter>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
<UserData>
<AcceptEula>true</AcceptEula>
<FullName>Administrator</FullName>
<Organization></Organization>
<ProductKey>
<Key>W269N-WFGWX-YVC9B-4J6C9-T83GX</Key>
</ProductKey>
</UserData>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-LUA-Settings" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<EnableLUA>true</EnableLUA>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-LUA-Settings" 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">
<EnableLUA>true</EnableLUA>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" 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>1</SkipRearm>
</component>
</settings>
<settings pass="generalize">
<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>1</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0809:00000809</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<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>0809:00000809</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" 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>true</SkipAutoActivation>
</component>
<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>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-SQMApi" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Microsoft-Windows-SQMApi" 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">
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>-PC</ComputerName>
<ProductKey>W269N-WFGWX-YVC9B-4J6C9-T83GX</ProductKey>
</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">
<ComputerName>-PC</ComputerName>
<ProductKey>W269N-WFGWX-YVC9B-4J6C9-T83GX</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>MYPASSWORD</Value>
<PlainText>true</PlainText>
</Password>
<Enabled>true</Enabled>
<Username>Administrator</Username>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>123456789</Value>
<PlainText>true</PlainText>
</Password>
<Description></Description>
<DisplayName>Administrator</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization></RegisteredOrganization>
<RegisteredOwner>Administrator</RegisteredOwner>
<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Description>Control Panel View</Description>
<Order>1</Order>
<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v StartupPage /t REG_DWORD /d 1 /f</CommandLine>
<RequiresUserInput>true</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<Description>Control Panel Icon Size</Description>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v AllItemsIconView /t REG_DWORD /d 0 /f</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>3</Order>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cmd /C wmic useraccount where name="Administrator" set PasswordExpires=false</CommandLine>
<Description>Password Never Expires</Description>
</SynchronousCommand>
</FirstLogonCommands>
<TimeZone>W. Europe Standard Time</TimeZone>
</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">
<AutoLogon>
<Password>
<Value>MYPASSWORD</Value>
<PlainText>true</PlainText>
</Password>
<Enabled>true</Enabled>
<Username>Administrator</Username>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<SkipUserOOBE>true</SkipUserOOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>MYPASSWORD</Value>
<PlainText>true</PlainText>
</Password>
<Description></Description>
<DisplayName>Administrator</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization></RegisteredOrganization>
<RegisteredOwner>Administrator</RegisteredOwner>
<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Description>Control Panel View</Description>
<Order>1</Order>
<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v StartupPage /t REG_DWORD /d 1 /f</CommandLine>
<RequiresUserInput>true</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<Description>Control Panel Icon Size</Description>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel" /v AllItemsIconView /t REG_DWORD /d 0 /f</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>3</Order>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cmd /C wmic useraccount where name="Administrator" set PasswordExpires=false</CommandLine>
<Description>Password Never Expires</Description>
</SynchronousCommand>
</FirstLogonCommands>
<TimeZone>W. Europe Standard Time</TimeZone>
</component>
</settings>
</unattend>

sudburr · Feb 4, 2019, 9:02 AM

Add this to your C:\Windows\Setup\Scripts\SetupComplete.cmd

REM "C:\Windows\Setup\Scripts\SetupComplete.cmd is executed as final step of coming out of Sysprep under SYSTEM account"
REM "Clean up problems caused by using COPYPROFILE=TRUE"
rd /s /q "C:\Users\Administrator\AppData\Local\Microsoft\Windows\WebCache"
rd /s /q "C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache"
del /f /q /a:sh "C:\Users\Administrator\AppData\Local\Microsoft\Windows\WebCacheLock.dat"

rd /s /q "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache"
rd /s /q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache"
del /f /q /a:sh "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat"

dijsil · Feb 4, 2019, 9:28 AM

This post is deleted!

70Pcs imaging all unbranded

232

12.0k

17.3k

155.2k