@Tom-Elliott I did it before your response… I saw it was the same results as I had done through root using an external boot device… Oddly though, once it completed I restarted the job normally and it actually COMPLETED!!! THANK YOU SO MUCH!!!

Yeah… That AD setting for host name actually kept the snapins from running at all… It just kept rebooting every few minutes after I logged in. Once I unchecked it, the snapins ran after i logged in again … whew!!!

@JJ-Fullmer @Tom-Elliott I was going off of this for the services that should be running…



I haven’t messed with anything AD since it’s not joined. I can give ita try though…
Tried. Makes no difference. I also disabled a bunch of the FOG Services that I didn’t need,
These are the only ones running besides the one from AD that you said should be turned on

@Tom-Elliott I’ve now updated the Fog Server and uninstalled rebooted, re-installed the client and rebooted. I re-captured the image again and proceeded to image a different VM… Same result. The snapin won’t run until I log in.
The hostname has changed by the time I login, but snapins don’t run until (as I stated above) I log in.
Is this as expected?

@JJ-Fullmer THANK YOU for geting back to me!
These? They seem by default set to work…



There’s nothing in AD

Yup, as soon as I logged in, it did it’s thing 100%… This can’t be right?
fog.log

I’m looking at a vm on it’s 7th reboot. It has the client, I’m almost 110% sure it’ll run through the snapin as soon as I log in. Is it suposed to wait for me to log in? I thought when i installed the service it would have the required permissions to do what it needs to? or am I completely wrong about it?

@JJ-Fullmer no domain. I get a feeling it’s a permission thing. The double reboot is actually more… I let it go a few times as a test. It’ll keep rebooting until I log in and the snapin runs. Once the snapin runs, the client changes the host name as it’s supposed to…
I would’ve sworn it was doing it without my logging in… I think before I added the account creation to the snapin…

@Tom-Elliott Yeah, I’ve tried all afternoon. I only have the script doing 3 things now. Create an admin account, delete my account and then make the pc immutable using overlayroot.
After the install it just reboots once the VM has checked in (same as earlier). It will continue to reboot until I log in.
Once I actually log into the system the snapin seems to be able to do what it’s supposed to.
While I was waiting for the snapin to kickin (while I’m logged in) I checked the hostname… still no change.
Is there a trick to installing the client that I missed maybe? I followed the instructions and downloaded the .exe …
Note: The namechange DOES run after I actually log in and the snapin reboots the VM twice and when I log in it seems to have changed it

@Tom-Elliott Sorry it took me a bit, I’ve been trying to figure it out… I keep getting these weird reboots while the snapins are trying to run, I see it checks in and reboots… then it reboots a couple more times and seems to finally run the snapin (still working on the script)… The hostname isn’t changed though… fog.log

@Tom-Elliott That’s what I meant by the scripts… I’ve used the snapins to delete my personal admin account and create a generic one and make the host immutable. Those are generic enough for groups of machines being imaged. I was hoping for something other than having to create a script with the new hostname embedded, a different one for each new imaged machine.
Snapins can’t be made to be visible to the user (admin doing the imaging) can they? Right after imaging there can be a script that prompts the admin doing the imaging what the hostname will be and if they want to create new user as well? (our admins are primarily winders… linux is new to them).