that damn copyprofile

[KK20]

So, if you accidentally image a bunch of machines and forget that you had copyprofile=true due to being uncaffeinated and forgetting that 1709 hates copyprofile, there is a quick fix; simply delete all the files in c:\Users\Default\AppData\Local\Microsoft\Windows\WebCache and away you go (till I can reimage properly).

 

Alternatively, for the OU you cunningly messed up in, run the following hacky batch file on startup (which will move the files rather than delete

 

@echo off
>nul 2>nul dir /a-d "%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WebCache\*" && (goto FILES_EXIST) || (goto END)
:FILES_EXIST
echo "*** Taking ownership ***"
icacls "%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WebCache\*" /setowner "Everyone" /T /C
echo "*** Setting Permissions ***"
icacls "%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WebCache\*" /t  /grant Everyone:F
echo "*** moving files - the flags will be copied over so hidden fodler ***"
robocopy "%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WebCache" "%programfiles%\webcache-backup" /MOV
:END

 

Windows 10 with lovely DOS era batch files. Makes me all fuzzy.

 

This is only good for NEW profiles created after the event though, existing profiles on the machines will still be borked (for us it was always edge and search that crashed)

[alfatec]

Why does 1709 hate copyprofile. We have 1709 images on 850 workstations, laptops etc and we used the copyprofile to create our base default profile. All seems to work fine, start menu is fine, edge is fine???

[KK20]

who knows. ask a dozen people and you will get a dozen answers. The same reason I had no issues with 1607 whilst others did.