Best posts made by moses

Greetings,

I’ve been using FOG for a little while now and where I work, we buy PCs that typically come with either an OEM Windows 7 license or Windows 8 with downgrade rights to 7. FOG handles retail or volume keys fine using the FOG client, but this won’t work for these OEM licenses or downgrade right installs.

So I made myself a little SetupComplete script about a year ago that lets us quickly clean image these PCs and activate Windows the same way the OEM does when they arrive on our doorstep sysprep’d from the factory.

You can read about how to do this yourself here, but I wrote a version that might suit FOG Project fans.

What it does:

• You select the manufacturer of the PC (or use the new “automatic mode”)
• The script identifies the edition (Home Premium, Professional, etc) and installs the corresponding OEM cert and key
• Verifies that activation was successful
• Starts up the FOG client service

It’s written in Batch and it’s messy, but it works. Feel free to fork it to make improvements, or open an issue on Github if you discover a bug.

Cheers!

---

For now, you can view the FOG Edition of the script on Github:
https://github.com/mgiljum/Windows7-OEM-Activator/tree/FOG-Edition

Or you can download it directly here (just be sure check the README.md
https://github.com/mgiljum/Windows7-OEM-Activator/archive/FOG-Edition.zip

Note: the “Non-FOG” edition of the script (can be found on Github) does the same thing, it just doesn’t start/stop the FOG service or come packaged nicely with a SetupComplete.cmd template.

Disregard. I found the issue.

This server was migrated from a backup, and the backup had my old FTP password in there. Updated the master storage node with the correct, new password, page loaded fine.

Oh wow…I originally asked the onsite tech to boot a client to see if he got the Fog boot menu…

…he was rebooting the storage node. Sigh…

Never mind, guys. Thanks anyway.

It would be great to have an option to disable replication during certain times. Where I work we replicate over an MPLS link that doesn’t have a lot of bandwidth, and all of it needs to be reserved during the day for production stuff.

However, at night or on the weekends is fair game for doing our backups, network discovery tasks, etc. It would be nice to be able to go into FOG and schedule times at which the FOG replication becomes enabled.

Note: Right now I’m doing this using cron (simply disabling replication service at a certain time), so I know that’s an option here, but it would be nice to have it built in. I’m sure I’m not the only person who might use it.

This update resolved getting to the web interface, but I still get a 500 error when trying to get to the Log Viewer.

After updating the node in question (despite it failing at “Restarting apache2 for fog vhost”), replication has been fixed.

@Tom-Elliott That did the trick!

That is, after I mistook the interface name “eno1” for “en01”. I should really go to bed.

In the settings for the image, is it set to a re-sizable image type?
If yes, under Images > List all Images, is the Image Size on Client smaller than the hard drive size you’re attempting to deploy it to?

@Sebastian-Roth Actually in giving me that suggestion, I found the issue. I have a Tomato router that I use for DHCP, and I misread the Wiki when it shows how to set up that for PXE. I used the wrong boot file:

dhcp-boot=pxelinux.0,,192.168.1.201

Where it should have been:

dhcp-boot=undionly.kpxe,,192.168.1.201

Made that change, and bingo.

Thanks all for your help!

@Tom-Elliott Sure, updTing now

Found the problem. Motherboard battery was dead and the power went out yesterday. Date was reset to 2005.

Corrected the date and HTTPS works again, and installed NTP to cover my ass.

Modified /tftpboot/default.ipxe to the correct IP, and that fixed the problem for now, but not sure if it will become a problem again after updating (ie. a database value somewhere that will overwrite it).