Active directory Join issue
-
@anthonyglamis said:
With the new client 0.9.10 do the new clients intended to be deployed and auto joined to the domain need to be created in AD before deployment?
No. When they join, they will appear in the default OU, whatever that’s configured as. On an unchanged AD setup, this is the “computers” OU. I always change mine though.
-
@Wayne-Workman So what if I restore one of my laptops to factory default? The reason I say is we don’t use WAIK, or sysprep. Let’s say I create a master golden image, but it is time to update it for instance adding an additional program. Once the image is created can I manipulate it if I ever had to?
-
@anthonyglamis said:
Once the image is created can I manipulate it if I ever had to?
In a way, yes.
You’d un-check the domain joining checkbox for a host, download your image, make your changes, and then re-upload.
When you re-upload, if you do not change the image assigned, it will write over your old image. You can create a new image and assign the new image to the host, and upload to that if you want. That way lets you keep both the old image and the new image - but it takes up space. This is what I do, if you were wondering. Space is cheap.
-
@Wayne-Workman Just deployed my image. I unchecked add to domain and it imaged and did not join to AD. The log output states: “Authentication error. CA is not from the fog server”. Any suggestions on next testing steps?
I can attempt to perform a factory reset for my most heavily used model, build an image, install the client service , register the host and capture. -
@anthonyglamis No need, just uninstall the fog client and then reinstall. Reboot a few times and see if the errors go away.
Make sure you set your /opt/fog/.fogsettings caCreated to yes so this doesn’t happen again.
Also, I forgot to ask earlier, but is there a reason why your fog ftp credentials are blank in that file?
-
@Wayne-Workman I updated the .fogsettings file to reflect “yes”;
The ftp credentials were left blank upon install. If I change this does it also have to be changed on the fog server? -
@anthonyglamis yes. There’s a article all about ftp. “Troubleshoot FTP” in the wiki.
-
@Wayne-Workman Currently I am not receiving an error file not found, but I assume I want a password in that field for added security. Thanks again for the input.
Now I am curious. Would FTP mismatch in credentials cause the error “image store corrupt”? I know what happened. The d1.mbr file was not created on that image. Duh…at least I’m starting to recognize some of these issues. Capturing again. This time I am trying Single disk (re sizable)
-
@Wayne-Workman I just finished reading your post and the FTP WIKI. I apologize I don’t think I was understanding what you were referring to. So in my storage node settings the FTP path must match, as well as the user name and password. Thanks for the heads up. I have updated all the info. Straight from the WIKI.
Web Interface -> Storage Management -> Your storage node -> Management Username & Management Password Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD The local 'fog' user's password on the Linux FOG server /opt/fog/.fogsettings -> storageftpuser & storageftppass (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.) -
@Wayne-Workman @Arrowhead-IT @Tom-Elliott
Just wanted to update. I noticed the capture on my “golden” image yesterday did not capture or create the 1d.mbr file. I updated Fog today to the latest revision, 6136 (I just noticed there is another) recaptured, and checked for the 1d.mbr file and to my surprise the d1.partions file was there as well. Fog deployed this image to another laptop with success as well as auto joining to AD. I think I am getting the hang of Fog. I want to test a few more platforms. I will update, and if successful we can set this thread as solved!
Once I determine that capturing and deploying is stable I will perform my own write up. I understand that most of the info is in the WIKI, but some of it is outdated. The instructions still list fog 0.32, which if you remember the beginning of this thread, that’s what I started with
-
@anthonyglamis said:
Once I determine that capturing and deploying is stable I will perform my own write up.
Good documentation is a vital part of any software solution - open source or not.
So is a helpful and acive forums
-
@Wayne-Workman Update. OK I have been able to test further. Capturing, deploying, and auto join to AD is working fine. Thank you everyone for all your help! This is a pretty powerful program. I am having printer setup issues, however I will either start another thread or jump in on an ongoing printer thread. You can set this thread as solved.
