Fog Domain join issues
-
I’m aware of some issues with Windows 8 and hostname changer, though all tests I’ve been able to perform say it works. Other’s seem to only change the netbios name. I don’t know why this is. I can’t narrow it down either.
That all said,
As super chicken states, are you sending the domain name with the username? I’ve made it so you don’t have to do this anymore. This shouldn’t have any effect on hostname changing, but as I said, I don’t see the issue on Windows 8 as others are.
-
I have tried it both with the domain name and without the domain name with the same result. Currently I have removed the domain name and am just using the username. I will keep troubleshooting and let you know if I come up with anything.
Thanks for the reply!!
-
After some more tinkering I seem to have a little more information that might help to narrow this down.
- After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
- If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
- I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)
Hopefully this helps to narrow the problem down. I’ll continue to look into it.
Thanks
-
[quote=“Dekar, post: 29363, member: 19775”]After some more tinkering I seem to have a little more information that might help to narrow this down.
- After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
- If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
- I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)
Hopefully this helps to narrow the problem down. I’ll continue to look into it.
Thanks[/quote]
That would make a LOT of sense. Probably why I can’t replicate as I didn’t think to “sysprep” and test.
-
[quote=“Dekar, post: 29363, member: 19775”]After some more tinkering I seem to have a little more information that might help to narrow this down.
- After I sysprep my image (Windows 8.1, x64) and upload it, I can deploy this image and it will rename and join the domain as intended.
- If I then take the freshly imaged machine (imaged with the sysprepped image listed in #1)and add drivers, software, ect. and then upload it to fog as a separate image WITHOUT sysprepping it, I run into the problem every time.
- I am willing to bet that if I created an image from a fresh install straight from the windows 8 disc and never sysprepped it to begin with that after deploying it fog services would function as intended as well. (have not tested it yet, just a theory)
Hopefully this helps to narrow the problem down. I’ll continue to look into it.
Thanks[/quote]
That’s probably because after the sysprep process occurs, it intends to stay with that machine and those hardware unique identifiers, the purpose of the sysprep is to generalize the installation so it can be prepared for a new machine with different hardware unique identifiers. Yes also put it in an out of the box state and that is where Unattend files come in handy to get your installation back to how you intend the end user to see it.
I’m willing to bet that if you install the base windows 8 image and don’t sysprep you may run into the same issue. If not, it could be one of the drivers or programs you are installing after the sysprep process and before uploading again. Before you try to narrow down a problem driver, I have another solution, read on.
To join a machine to an active directory domain, it likes things to be unique.
I’m willing to bet that if you ran the sysprep process on image listed in step 2, and then push, you might see success in deploying and joining to a domain again.
Sysprep doesn’t REMOVE drivers, it just freshens the install so it is acceptable to drivers again so if you move it to a new hardware it is less likely to have problems, provided that windows is still able to supplement a driver for its use. So deploying the sysprepped image to install drivers is actually a wasted process. I set up a path variable for C:\Drivers and pack all my driver files and install files there so when Windows looks for drivers, BAM it find the right ones, if not I install them manually after installation (this is a specific and quirky model and there are few of them so I don’t waste my time to fix the driver in the folder… possibly laziness.)
-
My real goal with sysprepping was to have an image that is capable of being deployed to multiple computer models. What I was hoping to do (and maybe this is a flawed thought process) was to have an image that is sysprepped (to remove hardware unique drivers, add in activation keys, ect) so I could deploy it to the 20 different computer models I have. Then for each model I intended to install any missing/needed drivers and upload an image to fog for that model with drivers in-tact so when I deploy it, it is ready to go without being touched. Then I would end up with the following:
- “golden” sysprepped image that I can use for all computer models - current and future (always have an image ready)
- A “complete package” image (not sysprepped) for each model of computer I have (HP Elitebook 8440, HP Compaq DC7900, HP Elitebook 850, ect) this also allows me to have unique software added to these images so they are customized for the location (some software on these is as big as 50GB and does not work for group policy or snap-ins).
So really i’m not deploying sysprep to install drivers, in fact i’m doing quite the opposite. Really all the sysprepped image is for is to prevent having to pop a windows 8 disc into every model of computer and build an image from scratch. It gives me a good base that only needs drivers and miscellaneous software.
Does this sound like a reasonable approach, or am I going about this all wrong?
-
I’m not sure if i’m in the right place but anyway. I was having trouble after I upgraded to Fog 1.1. The Windows 7 64 images would join the domain. I messed around with some setting but still didn’t work. I changed the domain name from local.local to local and the user name from local\username to username and it joined without issue. Sorry if i’m not in the correct place.
Thanks for everything you have given us with the Fog project
-
[quote=“Dave Bagwell, post: 29462, member: 5315”]I’m not sure if i’m in the right place but anyway. I was having trouble after I upgraded to Fog 1.1. The Windows 7 64 images would join the domain. I messed around with some setting but still didn’t work. I changed the domain name from local.local to local and the user name from local\username to username and it joined without issue. Sorry if i’m not in the correct place.
Thanks for everything you have given us with the Fog project[/quote]
Take the “domain” part out of the username entirely or you could have issues down the road.
-
That is what I was trying to say, I removed the domain name from the username and the domain “.com” from the domain name under AD setting.
Thanks again
-
[quote=“Dave Bagwell, post: 29466, member: 5315”]That is what I was trying to say, I removed the domain name from the username and the domain “.com” from the domain name under AD setting.
Thanks again[/quote]
No problem, but you shouldn’t (necessarily) need to remove the .com part of the domain. If the base image is already attached to the domain, changing the domain name field would help.