@Quazz We only have 3 images, and currently we are deploying the 32bit one. All the images are the same. plus this image in particular, is the one that was captured, as it is on the subnet where the master node resides.
Tomorrow i will be back at the building, so I will be able to dive into it more.
Create your master image either by running a fresh target system in audit mode OR use Microsoft’s free MDT tool to build your reference image.
Install all of the windows updates.
Install all of your third party applications
Make any custom configurations required to the reference image
Sysprep and power off your reference image
PXE boot your reference system into the FOG menu and register it (DO NOT let it boot from the hard driveP
Create your image reference in FOG
Connect your image reference to your reference host you registered in FOG
Schedule an image capture via the FOG console.
PXE boot your reference system againg and capture your reference image to the FOG server.
From there you will then select a system and deploy. The FOG server will push the image to the target computer and then reboot. Since you sysprep’d the image before you captured it, OOBE will run on the target system and configure it for the target hardware.
The accesscontrol plugin was an attempt to bring, you guessed it, access controls to fog, but it is very convoluted. I’ve been more tempted to just remove it as it was very complex to get working, and even with the plugin in it’s current state, it only works on a manual basis (meaning you have to code all the elements yourself.)
I know of a few people who actually are using it successfully (or somewhat so I suppose more accurate). That said, as you’re running into issues, I’d simply recommend disabling the plugin, unless you feel you want to code it for your environment. A potentially simpler way for you to fix this would be to remove the accesscontrol plugin you currently have, and rerun the FOG installer. This should help you with any issues, but like I said, I haven’t really put any work into it. There’s just too much to try to make it work properly at this point.
Node’s being done is an issue, I suppose, and I should really figure out a way to fix it. This isn’t a problem with login, as you noted. It’s more due to the timeouts that are designed to try to test if the page is accessible in the first place.