Topics created by ckasdf

@ckasdf Are you still onto this?

So following the link in list item #1, I ran into some issues. I created the fog.patch.man.reg file as directed, copying the quoted text into the file and chmod’ing it to 755. Your step 4 mentions editing fog.postinit, which is a file I don’t have. I wondered if you were missing a step that indicated to run the patch script, so I ran it with # ./fog.patch.man.reg and got the following output:

./fog.patch.man.reg: line 12: /usr/share/fog/lib/funcs.sh: No such file or directory Testing path for our fixed file at fog.reg.man.fix ./fog.patch.man.reg: line 15: debugPause: command not found Failed to find file [fog.reg.man.fix] sorry. Copy Failed ./fog.patch.man.reg: line 26: debugPause: command not found

I am thinking that my issue is possibly advice in this forum thread, which suggests that it’s safe to delete the contents of /images/dev/. The thread is from 2016, so perhaps dev gained more purpose than a temporary dumping ground for in-progress captures? I arrived at that thread some time ago, for the same reason as the OP - I was running out of disk space and found out it was because of occasionally-failing captures. Deleted the contents of the folder and everything was good again.

Following the link to list item #2, “Using scripts” was a non-starter. I have /opt/fog, but don’t have utils within that directory. Instead, I have log, service, and snapins. I ran find -iname *image* and didn’t find FOGMountBootImage.sh in the results.

I followed the instructions in the “By Hand” section for Version 1.0.0 and up. I had trouble running mount -o loop init{,_32} initmountdir as CentOS didn’t like that command, so I made the assumption that it was trying to mount two directories within initmountdir (init & init_32). I ran that command as such:

mount -o loop init initmountdir/init mount -o loop init_32 initmountdir/init_32

I then navigated to initmountdir/init{,_32}/bin and changed each fog.man.reg to the file I had created. It sort of worked after I packed everything up, in that things did change, but the registration didn’t act as expected. I entered a hostname as requested, left image ID blank and hit Enter, then it went to a blank line. I waited, but eventually hit Enter again, which then asked if I wanted to associate with groups. After that, when I hit Enter, it dropped to a new blank line, but didn’t continue the form. I possibly have a malformed file (I had a few errors along the way, fixed based on my knowledge of what was wrong). If you’d like, I can attach it. Any thoughts on some of the other issues above?

Also, I was wondering, how would I create a new menu entry, so that my tests show up as a separate item from the primary full registration?

Hey George,

No worries on the delays. Work’s been busy for me too, but today is slow finally.

I realize I messed up how I explained things. I was creating a template host with the same exact name as the group. After not being able to get it working, I tried your example name of TemplHost01 for both a new group and new host. I set the details on the host, added it to the group, and still nothing.

So I just tried again today, and the functionality is working as expected. Curious … I wonder it just needed a little more time. I’ll play with it a bit more and see if everything seems to be good.

Yeah, it definitely seems to be working better now, including with groups/host-templates that I name. I’m not sure what was happening the other day.

One thing which seems like a bug: if I’m in a group and I navigate to Membership to then search for and add additional hosts, it only adds one at a time even if I click the checkbox for multiple.

@ckasdf said in Errors in Apache log and www-error.log:

Perhaps those are less errors, and more just warnings?

Abdolutely but it’s still imporant to get rid of those to not cause any confusion when we tell people to consult the logs when looking for an error.

Is LDAP login possible with the current build?

While I have not tested it myself in our test environment lately I am fairly sure it does work. I remember others posting questions on this in the forums and did succeed.

If so, I’ll open a new post requesting help with that.

Probably not too bad of an idea. Doesn’t cost much extra and it’s good to keep things sorted a bit so people find answers more easily themselves.

Just a quick hint: Are you able to connect to your LDAP using the same credentials in a tool like ldapbrowser?

I just updated, and it was much easier than I originally anticipated. 🙂 Thanks again!

Thanks for the insight! I copied one of my build images to a test-copy, then made two changes. I then ran sysprep /generalize /reboot /unattend and allowed the VM to sysprep and reboot to see what happens. I didn’t capture it to run it through FOG, but I imagine the results will be mirrored once I do.

I noticed that your unattend file didn’t contain a reference to SetupComplete. Therefore, I edited unattend.xml to remove the <Component> block that contained <AutoLogon> and <LogonCommands> (within which was contained the reference to SetupComplete.cmd).

I moved unattend.xml to the Panther directory at your suggestion. When I ran sysprep, I tested it without defining a file, and sure enough, it picked it up with no problem.

After allowing sysprep to do its job, I logged in as the local admin (since I didn’t have FOG to join the domain for me), and no command windows popped up to try running SetupComplete as the local user. SetupComplete didn’t appear in the Startup tab of Task Manager. FOGService was set to Automatic and was Running. In other words, the things that weren’t supposed to be happening no longer were, and the things that were supposed to happen WERE! 🙂

 

By the way, slightly on the topic, I know the wiki suggests restarting the computer with a command in SetupComplete after enabling the FOG Client, but Microsoft’s documentation suggests this is a bad idea:

Warning You cannot reboot the system and resume running SetupComplete.cmd. You should not reboot the system by adding a command such as shutdown -r. This will put the system in a bad state.

My SetupComplete file contains two lines:

sc config FOGService start= auto
net start FOGService

It seems to still restart if needed, so maybe the shutdown line can be removed?

 

Thanks to @fry_p, @george1421, and @Sebastian-Roth for your contributions in helping me figure out this strange issue!

Thanks for the suggestions, George, that sounds reasonable. I’ll do some testing on that when I get a moment! 🙂

They do occasionally have different or old BIOS versions, which I update after Windows is finished loading. But they all have the same settings.

@george1421 You weren’t kidding about the 10 minutes, that was easy! There was another article on DNSMASQ that I had looked at before putting up this post, which looked mega complicated. Likely it was intended to do more than just PXE stuff. I haven’t deployed anything, but I registered a computer successfully after booting to PXE, so now I just have to migrate from laptop to server. w00t!

@Borega Try this file: https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_SnapinPack_empty_dirs.dll

Should have the fix in it as well.