Active directory Join issue
-
@Wayne-Workman said:
@Arrowhead-IT said:
Just make new images in the fog gui with the same settings and point them to the file names and they should work. Does that make sense?
People always mess that up.
Do I sound full of myself if I say that I never messed that up? Because well, I never messed that up. It just kinda worked as it should anytime I’ve done that.
Have you tried the FogApi powershell module? It's pretty cool IMHO
https://github.com/darksidemilk/FogApi
https://fogapi.readthedocs.io/en/latest/
https://www.powershellgallery.com/packages/FogApi
https://forums.fogproject.org/topic/12026/powershell-api-module -
@Arrowhead-IT said:
Do I sound full of myself if I say that I never messed that up? Because well, I never messed that up. It just kinda worked as it should anytime I’ve done that.
No. Would I sound full of myself if I said I haven’t, either? lol. But a lot of people have messed it up.
-
Wow this thread has a bunch of activity! Thanks for everyones help.
I captured an image late last night and checked /images for the d1.mbr file and it was present. I was able to deploy this image to another Lenovo E431 (this is windows 7 pro btw), however it did not join to AD, and interestingly enough it did not change the hostname either.
This is odd since yesterday Fog was actually successful in changing a hostname and adding one of our laptops to AD. Granted this was a PC we had taken off the domain in order to capture the image. We gave it a generic name LENOVO-E431-I3 and after capturing the image it would not let us change the name of the PC and kept rebooting. This of course was the client service doing it’s job. So in the Fog server we changed the hostname to what we wanted and boom after a reboot the hostname changer did it’s job and also added the laptop to AD.
I am looking at the fog .log and there is an authentication error more specifically this is from a deployed Win 7 image
--------------------------------Authentication--------------------------------
1/21/2016 10:27 AM Client-Info Version: 0.9.10
1/21/2016 10:27 AM Middleware::Communication URL: http://192.168.1.243/fog/management/other/ssl/srvpublic.crt
1/21/2016 10:27 AM Data::RSA FOG Server CA cert found
1/21/2016 10:27 AM Data::RSA ERROR: Certificate validation failed
1/21/2016 10:27 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
1/21/2016 10:27 AM Middleware::Authentication ERROR: Could not authenticate
1/21/2016 10:27 AM Middleware::Authentication ERROR: Certificate is not from FOG CA
1/21/2016 10:27 AM Service Sleeping for 120 seconds -
@anthonyglamis said:
Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified.
That’s the issue.
Try to reinstall the client on that image, and then re-upload and try again. If it’s still not working, try resetting the encryption on the problematic target host.
-
@Wayne-Workman
@Arrowhead-IT
Pertaining to the images I deleted from the Fog UI, they are still present in the /Images directory. So if I create a new image in the Fog UI and name the file the image name it adds. The file size is 0.0
Will this populate when I attempt to deploy the image to a new host? Just curious as I don’t want to deploy a 0.0 image size to one of my hosts lol -
@anthonyglamis said:
Will this populate when I attempt to deploy the image to a new host?
Yes. that field gets updated every time the image deploys or uploads.
-
@anthonyglamis @Wayne-Workman speaks the truth.
I would just add that there is a setting called FOG_FTP_IMAGE_SIZE in fog configuration → Fog Settings → General Settings
that you can enable. The size that says 0.0 is likely image size on client. If you enable FOG_FTP_IMAGE_SIZE then you will also see the compressed image size on the FOG server which I think will automatically update, but it might also need to be deployed first.I just like being able to see both sizes.
-
@anthonyglamis to add on, what you see by default in that field is how big a disk (approximately) you need to be able to image. The way it’s populated is as Wayne stated, through imaging tasks. There is also a field that, by default now, is hidden and will show how much space on disk it will use. If you enable viewing of the image, it should show a size which would then show you how much server disk space it’s using.
-
Come to think of it those images have the previous client service from 1.2.0, I’m guessing I will want to update the client service and capture again?
-
@anthonyglamis yes.
-
@Tom-Elliott
Do you need any information from me concerning the images I have that did not create the d1.mbr file? Just asking as I have to update the Fog server and start recapturing new images with the latest client. I essentially have no use for the previous images I created. -
OK so I’m having a brain fart today. I wanted to update to the latest version. I ran the install.sh and it rolled me back to 6032. Where is the latest version located?
Never mind, I was in the wrong folder. I am back on 6038, but would still like to upgrade to the latest version. I thought the installer would update.I used this link and SVN
-
@anthonyglamis if you are using svn to manage the trunk package, you change into the trunk folder and run
svn upthat will download the latest code from the subversion repository. Thencd binand then./installfog.shIf you are using git they have a comparable update command.
-
@george1421 Thanks! I completely missed that step.
-
@anthonyglamis I like scripting things. And I like sharing. Here’s how I do my fog updates with one command.
If you stick with svn, you can just change the git function in the script to do svn up instead of git pull and change the path variables too in the variable setting function. Or just use git, because sourceforge likes to crash.
https://forums.fogproject.org/topic/6331/automating-git-updates-for-fog -
@anthonyglamis you can but the new client is actually msi and has support for cli arguments to define configuration of the client. This means you can create a GPO to install the new client. Of course you still have to remove the old client first but I believe there’s a forum posting that discuss how to do this.
-
OK update time. I updated Fog to 6048. Captured 2 images with updated client service. Operating systems are Windows 7 pro. Models are Lenovo E431, and Dell Latitude 3450. The d1.mbr file was captured for both images.
The Dell 3450 just finished, however it did not join to AD. Attached is the log. I am getting an authentication error again. Not too sure what I might be doing wrong. I reset the encryption data for each host before the capture. I noticed that is an option in the group setting as well. Should I have done that?
0_1453407792520_3450fog.logThe Lenovo E431 partclone process didn’t even start. The error is “problem opening# Error is 2” Partition file missing /images/E431I3/d1p.img* the specified file does not exist.
In my /images directory that file is there, but it is named as follows:
itadmin@fogserver:/images/E431I3$ ls
d1.fixed_size_partitions d1.original.fstypes d1p2.img
d1.mbr d1.original.swapuuids d1p3.img
d1.minimum.partitions d1p1.img d1.partitions
Is this just a matter of renaming those files to what fog is looking for? Lol it will not boot not since the initial partclone process wipes the mbr. I’m bricking things left and right! Woop Woop! -
Updated to Fog 6050, installed the latest client service and installed the certificate from my server in my certificate store just to be sure. The dell 3450 instantly rebooted and joined to AD. I am starting over from scratch with new cert and client installed. Am taking two more captures now, and will deploy as soon as I’m done. Operating system Win 7 Pro, models are Dell3450-I5/Lenovo E431-I3.
I will update if these images work and join to AD. -
Apparently I have no idea what I am doing. I captured both images, tried to deploy them and I get this error
“an error has been detected no partition type passed (perform non resize restore)”
I don’t get what I might be doing wrong. Any ideas?The Dell 1d.mbr is 32Kb
Upon inspection of the d1.mbr file for my Lenovo E431 captured image it is 1 MB according to the Fog Wiki it should be 32 KBThe option Single disk, multiple partition will manage to upload/deploy all the partition of the disk. The OStype setted to Linux will copy a 32256 bytes MBR.
NOTE: setting a Windows 7 OStype, will clone a 512 bytes MBR: at the boot the system will show the string GRUB and then will hang!
With this configuration, after the image upload, in the directory /images of the fog server there should be a directory with the name selected for the image containing:
d1.mbr (the MBR: should be 32256 bytes) d1p1.img d1p2.img d1p4.imgthere are 1 file for partition, with the exception of the swap partition.
-
I realize you had a long and troubled day. So my questions may put you over the top.
Can you create a truth table from your testing thus far? (dell, full disk cap = No, dell, resizeable cap = Yes, Lenovo =No) there has to be some rational here.
Do you have one system that you can capture and deploy successfully?
Your issues are seeming to be multiple. The first is of course capture and deploy and then once deployed connecting to AD.
Its not clear quite yet in my mind is your issue with the new way fog is trying to capture images or the hardware them selves. Both of these systems are pretty new with new next gen components. If they are not reliable, do you have older systems you to setup a baseline with? I have seen recently with some of the newer lenovo, they have a built in small hard drive (16GB in size M.2 SSD) that seems to be causing some capture issues with other people. I’m not saying that is the issue with your lenovo its just one possibility.
