Posts made by ITSolutions

@herrpommesfrite Does the computer account exist in AD already? If so can you delete it and see if it joins then?

@herrpommesfrite I know there has been a few updates with the client and I think one since 6677 that you are on, can you try updating to the latest as of now it looks like 7114. Also you might want to double check your settings in FOG.

• Make sure that the domain name is correct no spaces in front or behind the name “domain.com”
• Usename, for the new client doesn’t like the “domain\username” set up, should be just “username”
• The password needs to be entered in the FOG_AD_DEFAULT_PASSWORD field, best to clear the Legacy field just for sake of not needing it. There is no encrypting the password before entering it like in the old client setup. So enter the password in plain text and it will encrypt on save.
• For Testing purposes I would remove all OU settings, just to be sure that it isn’t an issue with a setting.

According to Microsoft and the error that you receive it is pointing toward a permissions issue with the account.

I know some of those steps seem simple but I have had many times I banged my head against a wall to solve a typo I made that I overlooked a million times.

Oh and a question I forgot to ask, what OS are you using, win7, 10, 8?

Can you join the machines manually using the AD username and password that you use have in FOG configuration? It looks to me that the 1326 was the username/password was wrong, now it looks like the account doesn’t have access to AD or at least the OU that use are trying to join to.

I would try manually add them with the account you use in FOG AD settings
Try a different AD account
Try a different OU setting in FOG or leave OU blank to just join to Computer OU

Also are you using the new client or old?

If you try to re-image the computer that you pulled the image from does it boot? If so that indicates the image is good. I would compare the BIOS settings on the machines, especially the HDD settings. I know that I have had issues that if you build the image on a machine set to ACHI and deploy to an ATA machine it will fail. Dell is really bad at have that setting being somewhat randomly assigned from the factory.

@FlowLive I guess the only question I am seeing is that you are asking how to determine if the machine is a laptop or desktop. The easiest way to accomplish this is to use a script as the snap in that will check if it is a laptop and if so run the installer from a share some where. If it is a desktop then no installer is run.

Natively there is no way to have FOG determine if the machine is a laptop. But if you know what machines are laptops as you add them, you can have machines belong to multiple groups, add all laptops to a Laptop group and apply only those 3 snapins with no other setting in that particular group. Not automatic, but does work.

I quite often use scripts instead of actual files for snap ins, mostly due to old limitations of snapins back in the .32 days, so I guess it is just an old habit.

@Wayne-Workman You want to be careful using wireless as a determination for laptops. All of our new desktops have wireless built in also. They are the micro PC’s from Dell, the 3020M’s.

@Sebastian-Roth @Wayne-Workman I think an adjustable time would be nice though. Hard coding in a time might not be best for everyone, I am not a seasoned programmer but coding a field in the DB along the same lines as the FOG_SERVICE_CHECKIN_TIME to give the time a value doesn’t seem like it should be much harder. FOG_CRON_TASK_EXPIRY. Having it a global value, and not per task I think would be fine.

That way it could be set in a fashion of every night run this task, if task hasn’t been run in X min delete task. This would allow a task to run at anytime through the night, but expire before morning when the computer would be used.

@GFm Good to know, thanks for testing and reporting back.

@ch3i @GFm you might want to note that this will also change the grace period anytime FOG needs to restart the systems too. So If you send an image it could take 20 min to restart and start to image, this will most likely give 20 min before restarting if you change the host name and may also be the case if you join to AD. Not sure if that will effect you or not but wanted to be sure that you were aware of that.

You indicate that you are using the latest version of FOG are you using 1.2 or the trunk “1.3”?

This seems like a cool tool, but not sure that it would be a big help for most cases. This includes your particular issue, if your internet was slowed to 1mb on your end then having multiple channels pulling the same information wouldn’t make it any faster. This is more helpful when there is a bottle neck on the senders side where they can serve from multiple copies of the same files or am I missing something?

@dureal99d 1.3 is not fully released yet. The trunk build is refereed to as 1.3 and is very stable, but still in a beta stage. I would recommend if you are starting off in FOG to start with the trunk if you can.

Did you recently update your trunk version? Was it working before the update? This can happen if your /opt/fog/snapins/CA and or /opt/fog/ssl get removed. Check to see if they are there and if there are any files in them. The files will be hidden files

@Vanlue-IT-Guy @Wayne-Workman has a pretty good rough outline on how to transfer the images over to the new box. But if you are only worried about keeping the images and no database I would go a slightly different route. It will take a little more time but get all your images converted tot he new partclone from partimage that previous versions used. The first thing is find a spare machine that has a big enough drive to hold your largest image(doesn’t matter if it is the same model or brand). Then pull each image down from the old FOG server, DO NOT let the machine reboot to the image and then create the image definition on your new machine and push it up tot he new machine. You will have to do that with each image.

The quicker way is with @Wayne-Workman’s suggestion of using NFS, as FOG is already set up for it. Have both machines on, and on the new machine run this part of his notes:

---- using NFS ------
cd /
mkdir tempMount
mount x.x.x.x:/images /tempMount


---copy images---
cd /tempMount
cp -R * /images

(assumes /images directory is already made)

--- unmount ----
umount /tempMount

Then in the web interface you can create the image definitions again, just use the same name as you did on the old server. I recommend using a separate drive for the /images. With a separate drive you could just pull the drive from your old FOG server and mount it to /images in the new server, no need to copy.

Yes and yes, but I would recommend updating the images to Partclone right a way also. To give you a how to a couple of questions though:

1. Are your images and FOG on the same drive or separate drives?
2. What OS are you using Ubuntu, Cent, Red hat?
3. Are you wanting to keep your database from your current FOG server or just the images?

@Tom-Elliott This could be needed for security purposes. A wipe will make sure the entire disk is over written before putting down an image. With just re-writing the image you can’t ensure that forensic tools won’t be able to recover old files. I can see what he is asking for, maybe if there was a way to modify the download task to do a normal or full wipe then download to give assurance that all data has been over written at least once. This should be able to be accomplished a couple of ways, either one have the fog inits run a normal wipe then run the download, or possibly with the a hooks you could have it auto create a deploy after the wipe finishes so when the client reboots it will pull the image automatically.

Sorry for not responding earlier, Yes this is solved. Thanks again for all the hard work @Developers and everyone else.

@treyw00 Are the vlans accessible to each other? If you can ping the FOG server from the other VLAN you should be okay with them on separate vlans. I am assuming that 10.65.224.104 is the FOG server IP? It shouldn’t contact the DHCP server, it is looking for the FOG server in order to get the PXE files and boot.

@forte647 You can change the default selection under FOG Configuration>iPXE Menu Customization You can check the box on Multi join for Default Item. As for logging in as @Wayne-Workman pointed out you would have to try that, but you could just create a user with a simple login, such as:
Username: A
Password: A
This would make it simple to log in without any modification to the server.

I ca help with your first question, but not the second. To restore an image to a second drive you can set that on the host page for each host, under general there is “Host Primary Disk” to change the drive you send the image to you change that field to /sda for the first drive /sdb for the second and so forth. You can run debug to find which drive shows up in which order on the particular machine.

As for the second part maybe someone else can help with that issue.