Post Download Scripts not running / HDD not being resized
Further to my SysPrep not working and Start Menu not loading correctly issue from before, I now have a new issue.
With my old Answer file, I would set the Administrator password, and I assumed it would enable it… Nope, it didn’t! And FOG did not automatically join my domain (the
C:\fog.logfile mentions NOTHING with the domain name, or
hostname, anywhere). So I created a new user in my answer file, and redeployed. The new user was created, but I couldn’t log in. After troubleshooting, I found out the hard drive partition/volume was still shrunk down to 29GB. I expanded it, rebooted, then I could log in.
The FOG service is running. When I view the host in the Fog web page, Hostname Changer is enabled (as it should be), and I re-typed the username and password for the Domain section, just in case. No change. Fog is running at 1.3.4. The image type is Windows 10, disk type is “1 - Single disk, resizeable”
On the server, I have my storage set to
/images(as per the default). I created the folder
postdownloadscripts/inside there, permissions set to allow the
foguser access to do whatever:
/images/postdownloadscripts# ls -lah total 24K drwxrwxrwx 2 fog img 4.0K Jan 11 15:00 . drwxrwxrwx 32 fog img 4.0K Jan 12 15:48 .. -rwxr-xr-x 1 fog img 2.5K Jan 15 09:34 fog.drivers -rwxr-xr-x 1 fog img 562 Jan 10 11:59 fog.log -rwxrwxrwx 1 fog img 233 May 31 2016 fog.postdownload -rwxr-xr-x 1 fog img 1.7K Jan 10 12:02 fog.postinstall
Where can I look for information on why the scripts are not running? Or why the hard drive partition is not being expanded automatically?
This feels much better!
Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly.
A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice
OK, I’ll update, then report back. Thank you.
Wayne Workman last edited by Wayne Workman
Fog is running at 1.3.4.
First, please update to FOG 1.4.4. This is the latest stable release and is what we are supporting. There’s been literally hundreds of bugs fixed between the version you’re using and current stable (and a hundred more fixed upstream). There’s a very high chance the problem will go away if you used the latest stable version.