@ckasdf This is very strange you are getting an “Access is denied” because setupcomplete.cmd runs in the local system permission context. This is indeed the issue I think. So in my eyes, the hostname changer in the fog service is running fine, but the service is failing to start with the setupcomplete.cmd script thus causing your issue. The screenshots that I asked for pretty much mirror my setup.

So unfortunately I myself cannot recommend anything but to rebuild the image as it seems the local system account is borked. @Sebastian-Roth @Wayne-Workman @george1421 may have other ideas because they are actual wizards.

@ckasdf Please do the following for me. Log into the FOG web gui and search for the host. Select the host and click the “Service settings” tab. Please take a screenshot of this so I may compare to my setup.

Please also, while in the web gui, click on the three gears icon (Client settings) and pick the task reboot tab. Please let us know which boxes are ticked.

Finally, please click on the wrench (FOG Configuration) and click on FOG Settings on the left column. Scroll down to the FOG Client - Task reboot heading and click on it. Please let us know what is checked there.

@ckasdf I realized I was only looking at the beginning of the log and replied before I read enough. So it looks like it is authenticating properly as of 5/9. Let me look for a few moments, but chances are you followed proper protocol when you migrated.

@ckasdf I am seeing some authentication issues in the log. If you did migrate from an old server to a new one, please take a look at this article from the wiki https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server
I believe you can follow the first set of instructions (copying the ssl directory from the old server to the new one and rerunning the installer). I would strongly advise against recreating the CA (second set of instructions in this part of the article) because it will essentially break all existing fog client installations.
If you do not have access to the old server, I think someone else may have to help as that is beyond my knowledge.

@fry_p said in Issue joining domain & activating Windows after deployment:

If all else fails, please post the contents of your fog.log from a pc that is not automatically rebooting.

Doing this will help our friends diagnose the issue. You can find it either at C:\fog.log or at C:\Program Files (x86)\FOG\fog.log depending on where you chose when you installed the client.

@Sebastian-Roth I can give you an example as to why. I work in a school district and I would like to create a group for the 200 wing at the high school in FOG. So I go to the search bar and type “HS2”, bringing up all of the 200 wing hosts. Cool. I use the select all checkbox on the host list results and go to the bottom to create a group or add it to an existing group. Everything on this page looks good.

When I go to the group and select membership, I see all of the “HS2” hosts I selected but there are other hosts I did not select in the group. They are always the hosts that have been registered since the last Database maintenance.

The funny thing about this is if I create a new group, select membership, check the box for hosts that can be added and use that search box, it only adds the ones I search for.

I suppose this could be more of a bug report at this point. I can provide screenshots/logs on Monday if needed, perhaps earlier if I remote in this weekend at all. I just assumed this was normal FOG maintenance.

Well done boys! I’ll be sure to give my server a good ol’ update soon!

Hi all,
First and foremost, congrats on the 1.5.6 release! I will try to convince my boss to upgrade soon!
I had a question about the viability and potential harm in creating a script that would periodically run the (safe) database maintenance commands from the wiki.

My question is really should I do this? Is there anything this could mess up if it runs regularly? Right now I sporadically copy and paste them from the wiki into bash manually, but I am all about the automation of tasks like this. I typically only do this when I notice issues with adding to groups, but also periodically when I update fog or do OS updates on the server.

If you guys don’t think it is harmful (I still accept that I will be doing this at my own risk), I can write up a simple script and maybe even share it here!

Thanks as always!

Since setupcomplete is running after the image, I am assuming this was not an OEM version of windows as it wouldn’t automatically run at all. It seems to be hanging on part of it. My recommendation is to start simple. According to the wiki, the setupcomplete.cmd file should contain the following:

sc config FOGService start= auto
shutdown -t 0 -r

I see you have some customization for your environment in your current one. I would omit those for testing.

Please also try to reset the encryption data on the host. This can be done from the host management page on a yellowish button at the top.

If all else fails, please post the contents of your fog.log from a pc that is not automatically rebooting.

@luis-acacio said in Filesystem check error after capturing W10 image.:

I’ve tried to follow these tutorials but they are missing a lot of information… they’re just awful. Specially the one in the wiki.

I feel as if I may need to clarify something for you. I understand you may be frustrated, but the FOG Project is an open source solution that is not only free and designed/maintained completely by a small group of very intelligent volunteers, but also has top notch support on these forums that rivals paid support contracts.

Admittedly, the wiki is outdated. This is because these few developers are working on continuously improving fog and running a full fledged helpdesk for free, so it is understandable that the knowledge base takes the back burner. I assure you that every issue I have ever posted about in these forums was solved in an appropriate time-frame.

I don’t speak for the project and the only way I am involved in it is solely as a user, but I hope you now have some insight into the reasons behind the shortcomings of the wiki and I hope your issue is resolved soon and to your liking.