@lukebarone The postdownloadscripts were likely unable to do anything if your drive was full.
Posts made by Quazz
RE: N00b_Here: Plz help! New Setup for a company imaging solution
What kind of VM software do you use?
If you’re using virtualbox, make sure the network adapter is set to Bridged.
RE: CPU Usage high
no Tasks scheduled (due to it still not working for us, but thats a different story)
Seems rather relevant to me if FOGTaskSchedule is taking up so much CPU while not working.
What happens when you try to schedule a task?
When you restart apache, how long does it function normally before CPU goes to 100?
RE: Windows 10 1709 Fall Creators Update, AppX, and Sysprep
I personally haven’t had issues sysprepping 1709.
Is this a clean installation of 1709? (I’m guessing it is). Updating to new versions tends to give issues with sysprep.
I am going to guess the real issue lies with the copyprofile attempt and its inability to properly deal with the windows apps.
Try using defprof (small executable) as an alternative to copyprofile.
It will ask to install a service, specifically to handle the Windows apps.
RE: Windows 7 Image
@imagingmaster21 Based on https://support.microsoft.com/en-us/help/929834/error-message-when-you-try-to-run-the-bitlocker-drive-encryption-progr we now have some more insight on what’s going on.
By default, FOG removes the pagefile and hibernation file. Because the hibernation file is removed, the path in the BCD is incorrect and Bitlocker refuses to activate.
So, disable removing pagefile and hibernation under FOG Configuration -> FOG Settings -> General -> CAPTUREIGNOREPAGEHIBER (uncheck this).
Then you have to recapture the image so the hibernation file is included. You’re using Windows 7 and thus don’t have to worry abouy hybrid boot (as opposed to Windows 8 and newer where you have to disable Fast Startup in power options)
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Did you try capturing again after upgrading to 1.5? If not, please do so. (and if it still doesn’t resize after deployment, please post the contents of the partition files again)
There’s definitely some problems with your current image (such as your boot partition not being marked as unresizable)