The unmanaged switch works until I can get into the switches to enable a different STP.

The switch did not support any faster methods of STP, or they did not work. Disabling STP altogether is a calculated risk that we took, and it has fixed the problem.

This issue is solved.

The unmanaged switch works until I can get into the switches to enable a different STP.

Understood. I’ll see what I can do and report back. I won’t be in that lab for a few hours.

Thanks, george. I’ll see if I can get that done. I might not be able to, though. Is there any workaround that I can use to get this running until I’m able to make the change?

Hey all,

Unfortunately this looks like a duplicate of https://forums.fogproject.org/topic/4048/dhcp-lease-timeout-issue, but that happened about two years ago. I’m trying to set up FOG in a lab that has Spanning Tree enabled, so switches won’t open the port for about fifteen seconds after the NIC comes up. The FOG init tries to get a DHCP lease a few times, fails, then prompts to reboot the system.

In the linked forum post, it’s stated that a 60 second timeout was added. I assume that this changed at some point. How would I be able to add this delay back so that I’m able to successfully use FOG tools on them?

That is absolutely possible via [URL=‘http://www.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server’]ProxyDHCP[/URL]. However, I’ve been fighting with it since clients seem to get the wrong next-server (DHCP options 66/67) if it’s not set via Windows DHCP.

I have a UEFI device. Unfortunately, the biggest problem with ProxyDHCP is that iPXE tries to download the ipxe.conf file from the main DNS server instead of the ProxyDHCP server in my environment.

[CODE]The following errors occured
Update ID: 162 - 0

Database Error:

Can’t DROP ‘stID’; check that column/key exists
Database SQL:

ALTER TABLE fog.snapinTasks DROP INDEX stID
Update ID: 162 - 1

Database Error:

Can’t DROP ‘stID_2’; check that column/key exists
Database SQL:

ALTER TABLE fog.snapinTasks DROP INDEX stID_2
Update ID: 162 - 2

Database Error:

Can’t DROP ‘stJobID’; check that column/key exists
Database SQL:

ALTER TABLE fog.snapinTasks DROP INDEX stJobID
Update ID: 162 - 3

Database Error:

Can’t DROP ‘stJobID_2’; check that column/key exists
Database SQL:

ALTER TABLE fog.snapinTasks DROP INDEX stJobID_2
Update ID: 162 - 4

Database Error:

Can’t DROP ‘stJobID_3’; check that column/key exists
Database SQL:

ALTER TABLE fog.snapinTasks DROP INDEX `stJobID_[/CODE]

I haven’t found any issues with the way FOG functions with this update, but it did throw these errors. Upgraded from 3012.

If you have a volume licensing product key (And would like to use your MAK), then put it in the unattend.xml file and never worry about this problem.

If not, we get into some fun times.

First, you’ll have to put the KMS client setup key in the unattend.xml file. You can find those over [URL=‘https://technet.microsoft.com/en-us/library/jj612867.aspx’]here[/URL].
Next, you’ll get jbob’s updated .dll file attached to the post [URL=‘http://fogproject.org/forum/threads/windows-7-activation-proposal.10745/#post-29648’]here[/URL].
You’ll want to replace the hostnamechanger.dll in your image with this new one. To do this, you’ll have to turn off the FOG Client Service via the Services management console (services.msc) and paste the new file over the old one, which I believe is in ‘C:\Program Files (x86)\FOG’, then reboot the machine (for good measure).

That should be all you need.

I got on Hangouts with Tom last night and we figured it out. Fixed in 2944.