@Wayne-Workman Ok. I’ll try that. I disabled that node for right now to get my immediate imaging tasks done. I’ll try that though later this afternoon if I get time. Thanks!!

I think I went through this before but I can’t seem to find my previous posts about it. Ugh…

Thanks!!

Cheers!

@Wayne-Workman We do. 🙂 I tried that, we’ll see what happens! As you know our domain setup needs improvement. I’m doing my best to straighten it out. Ugh!

@BedCruncher said in Host does not boot into PXE after reboot:

@Joe-Gill
I would suggest setting network boot as first priority and then setting a timeout of 5 seconds on the menu so that if there is no task, then at most your boot time is impacted maybe 40 seconds.

You can also “hide” the fog boot menu. It’s an option inside Web Interface -> FOG Configuration -> iPXE Boot Menu

There’s also the “no menu” option.

There’s a hide timeout, and a regular timeout. The regular time out applies when hiding isn’t being used.

@Wayne-Workman Sounds good. I appreciate the advice! I’m just glad it installed. 🙂

Hi,

normally every common installer has silent parameters, if not just googling will bring you sites that may list such parameters, even when hidden. So installing software is in normal not more then a single batch line.

One example: http://www.itninja.com/

Regards X23

@Joe-Gill Yep. Correct until Tom makes another change to it.

@Wayne-Workman I have done this with the MAK key. That works fine. We just wanted to switch over to KMS. Which with our script snap-in it seems to be activating just fine now. I still need to refine it though. I think I’m going to add @Mentaloid’s suggestions to my existing script. I do believe that will finalize automation. 🙂

@Tom-Elliott I have tried a VBScript and have been unable to run it on the domain without having admin rights. How would I set admin rights with VBscript?

@Wayne-Workman I thought about something like that but did not know if it would work or not.

I’ll be working on this stuff more later this week. I may try that.

Cheers,

Joe Gill

@Wayne-Workman See post! I just updated it. Ha!

OP had AntiVirus installing inside SetupComplete.cmd before the FOG Client was re-enabled and started. The specific AntiVirus installation caused a reboot, which left the SetupComplete.cmd un-finished, and therefore all these other problems happened.

Consider building a snapin for the AntiVirus, which will auto-queue for any computer that is told to image and has the snapin associated with it, and the snapin will deploy after imaging is completed.

@Joe-Gill We need people to find odd problems. It’s good for the project.

@Joe-Gill Well, I suppose the first thing to try is this group that failed - but by itself, without other multi-cast tasks running. See what happens.

@Wayne-Workman
"“make sure that both the server and node (via logviewer–>multicast show that multicast session is actually tasked…I’ve had to cancel both active multicast task and active tasks, along with restarting FOGMulticastManager on both server and node, after killing mysql (TASK=8). Restart multicast tasking and it should start right up. I’ve even done a travel node, and can swear to it working. The key is making sure the logviewer multicast from server and node, show same tasking”

That’s all I got, not sure how to elaborate much more.

@Tom-Elliott

Thanks Tom! I’ll check it out!

I have no idea where to put this in the wiki.

For those who may come across this same problem…

I updated my BIOS and it resolved the problem.

Thanks @Tom-Elliott!

I updated this afternoon. I’ll be pushing more images out this evening and tomorrow. I’ll let you know how it goes. I appreciate all of your help!

Cheers,

Joe

@Tom-Elliott

No problem!! 🙂

@george1421
I"m betting it’s the order in which the script performs it’s tasks. I have the fog client reactivation set at the very end of the script. I’ll try adjusting the script and re-imaging.

This image is being used on identical hardware for this test.

@JoeG I have debated on just installing AV with a plugin. We’ve installed it with group policy in the past. It does work that way.

We have had a multitude of issues this summer and I’m trying to just get things ironed out on the last part of my installs before the school year starts next month. I’ve been thrown into the role of network admin after many years of being out of the tech world and I"ve been trying to learn the “proper” way of doing things.

Thanks for all of the advice!!! I appreciate the help!

Cheers,

Joe

@Joe-Gill How is it better to do it manually, when powershell can do the same identical thing but faster and in mass and without visiting each computer? It’s simple:
Remove-Computer -UnjoinDomaincredential Domain01\Admin01 -PassThru -Verbose -Restart
https://technet.microsoft.com/en-us/library/hh849816.aspx

Only thing to remember is to definitely delete the snapin after you’re done with it, because it’s associated it’ll run every time you image - which would cause problems.