Topics created by gwhitfield

#wiki need to work on snapin pack article.

@Tom-Elliott Seems to have worked, thank you! Maybe I messed up the trunk upgrade last time somehow. Anyway, I’m showing 1.3RC now so that’s all I’m worried about

I suspect the reasoning it “hangs” waiting for input unless only one option is defined is the timeout -1.

@Wayne-Workman Thanks a ton for you offer to assist!!! I’m going to put these servers right. Need to read up on how environments change in Linux as I’m guessing it has to do with my problem. Live and learn! This should be marked solved I think as we can reasonable guess the problem is hidden in how the server was built/upgraded in the first place.

@Tom-Elliott Feeling like dullest knife in drawer. Update fixed everything just fine.

@Tom-Elliott Cool, thank you!

@Junkhacker @Quazz Thank you both ! I did try re-installing FOG on one server and it worked. Then I tried just restarting another server and that worked too. I then restarted ALL the affected servers and they all worked. Don’t know why the problem occurred, never seen that happen in 10 years so I guess I learned something today and I can sleep well tonight 🙂

@Tom-Elliott - THANK YOU!!

@Wayne-Workman Thank you, I’ll post if I see anything else happening.

@Tom-Elliott said:

Can you update to the latest and see if this is still happening?

Updating to 6549 seems to have worked, funny it didn’t ask me to update/upgrade the database, just went straight to login. But I’m deploying an image so I’m happy! Thank you!! I will try that first next time, just thought if it was working yesterday it should still be working if I didn’t make any changes.

@george1421 said:

@gwhitfield said:

I stopped being prompted for the IP address and I hope that’s a good thing, I’m pretty sure that happened when I changed the DHCP policies.

wiki hint: Under efi booting, if we are getting the ipxe kernel being delivered to the target computer but the ipxe kernel either doesn’t get the next server, boot file, or possibly an IP address we should dig into what architecture is being requested and what the dhcp server’s policy is configured to deliver. @Wayne-Workman

Added a note: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Step_3

you may want to look into the location plugin for your situation

Just to touch base, setting the Clone flag in deepfreze while imaging did NOT fix the issue.

I also want to clarify that it is NOT a FOG issue.

Faronics is aware of the issues with the thaw spaces and the beta test team is working on resolving the issue.

Awesome! Glad you got it working!:)