FOG Multicast Issues / AD Join Issue
-
If you are using the client to join AD after imaging, do not join your image to the domain. More than likely that is causing your issue.
-
@Joe-Schmitt What’s crazy is that I didn’t have any issue (that I’m aware of) doing it that way before. I’ll start changing my images.
-
Nothing has changed concerning how the client binds a machine to the domain since v0.8 or so. Having your source image be part of the domain is a mess waiting to happen, especially if you didn’t sysprep.
Essentially all your machines post-imaged have the same security ids, the same domain binding and membership, the same everything. So right out of the gate post-imaged they would have massive domain membership conflicts.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@Joe-Schmitt Good to know now. It’ll be a mess to straighten out now.
I tested the theory out on one machine that was not joining the domain properly and added it to a workgroup. Rebooted and voila, it’s happily on the domain. I’ll have to go check everything. Live and learn.
Cheers!
-
@Joe-Schmitt said in FOG Multicast Issues / AD Join Issue:
Having your source image be part of the domain is a mess waiting to happen
Not just a mess waiting to happen, It’s an absolute disaster that will happen.
-
@Joe-Gill said in FOG Multicast Issues / AD Join Issue:
I might have 1 or 2 or 8 hosts out of a multicast session that do this. I haven’t had one session go perfect where every single host is successful from the beginning.
Is their any particular reason this occurs?Bad patch cables, bad drops, bad ports on the switch, loose connections. The simple things commonly cause this.
-
@Wayne-Workman More like a disaster that IS happening! smh… Live and learn. Better now to figure this out than once school is in session. Any advice on how to straighten it out? I’ll have to re-add everything that is out there… I’m assuming it’ll need to get corrected in AD…
Like I said, I’m the new guy… Arrf! -
@Joe-Gill I am in a different position in terms of setup than you are probably.
Personally, I’d delete all the computers from AD, correct the image, and then just re-image the building.
Why?
I have WOL turned on for all computers. I have NIC set as first boot option on all computers. I have all computers registered. I have all computers in the building connected to power and network. My FOG server is live, and on our production network.
You may be in a different situation though. You have to figure out what’s best for you.
-
Thanks for the advice. We’ll figure it out. I’m sure it’ll be more work but at least we’ll have a clean slate. The good thing is that all of the hosts have been registered with FOG server. So it won’t be as much work as it has been up until now. Plus the multicast issues have been mostly resolved so that’s a plus. Gotta stay positive!
Cheers!
-
@Joe-Gill It could be possible to use snapins to deploy a powershell script that would un-join all computers, give a reboot too using either powershell or the snapins reboot option. You’d delete all hosts from AD before this. Then, the FOG Client should just join them all back.
-
If you got that route, you must/should really use the built in snapin reboot option . That option exists for a reason.
-
@Wayne-Workman Thanks! That may be an option down the road. The other admin wasn’t too concerned. He said we will be re-doing our AD entirely next school year. At this point in the game, he seems fine with re-adding all the hosts manually to the domian… PITA in my opinion but… I guess it is what is is.
-
@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.aspxOnly 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.
