@george1421 Finally got around to testing this. I was able to remove the unwanted options, no issues.
I was also able to get it set to join AD domain, but I wasn’t able to get it to pick an image or snapins. Is there a specific way that the values need to be entered?
@quinniedid There is a .msi version of the client that you could use to install the newer client with the correct address. Unsure if old client would need uninstalled first.
If you have a way to push out a PowerShell script, something like this might help.
$FOG = Get-WmiObject -Class Win32_Product | Where-Object -Property Name -EQ 'FOG Service'
$FOG.Uninstall()
$url = "http://<ip address>/fog/client/download.php?newclient"
$outfile = "FOGService.msi"
(New-Object System.Net.WebClient).DownloadFile($url, $outfile)
$ArgumentList = "/i $outfile /quiet USETRAY=""0"" WEBADDRESS=""<ip address>"" WEBROOT=""/fog"" /norestart"
Start-Process -FilePath MSIEXEC.exe -ArgumentList $ArgumentList -Wait
Start-Service -Name FOGService
Start-Sleep -Seconds 2
Restart-Computer -Force
I think this might already be possible by creating a new Storage Node/Group or modifying the existing. I haven’t done it, but it might be worth looking into until someone that actually knows what they are talking about responds.
@Satheesh So, I just checked my 1.4.0 test server and had the same thing. My only thought is that maybe they don’t want you putting DOMAIN\ into that field. There is the FOG_AD_DEFAULT_DOMAINNAME above it. Probably goes there.
So…
FOG_AD_DEFAULT_DOMAINNAME = DOMAIN
FOG_AD_DEFAULT_USER = USER
edit: Just checked my live server and I do not have the domain name in the user field. For domainname field I have domain.com
@Satheesh Upload all partitions. Pull back down on another HDD. Delete unwanted partitions, resize, etc… Capture the new image.
I have no idea if it’s possible to exclude a specific partition from uploading.
@tri_94 said in Active Directory Joining:
Having been using fog for a while and it seems to be really hit and miss for AD joining after image. I can get it to join if I wait till the machines are imaged and then un-tick and re-tick the box to send the command again.
Is there something I can do to solve this so it will image and join without the manual intervention afterwards.
Thanks
Which version of FOG are you running? The FOG Client included in 1.4.0 is supposed to increase the speed at which it renames and joins computers to the domain. I’d suggest updating to the latest stable build.
Spacing between “Open Source Computer Cloning Solution” and the icons needs increased. I actually like how in the current version that’s written in gray.
@cojohnson said in FOG 1.4.0 Officially Released:
You are an outstanding person Tom Elliott!!! I wish i could thank you personally!!!
There’s a donation button somewhere. 
@Almeida You no longer need to use FOGCrypt with your password. You can type it in plain text and it will encrypt itself.
If you are changing the default AD credentials for everything, you’ll still need to go back and change it on the existing hosts. You can do this by putting all hosts in one group, then clearing the AD settings, and then checking the box to enable it again. It should auto fill with the new defaults.
When you upgrade to FOG 1.4 it will also upgrade the client that is on the server; however, you can disable the module that auto updates the client on the machines. The old client should still work, but I would test the new client. There shouldn’t be any issues.
@zionda said in Help with Mass Hard drive cloning station:
Hi Guys,
I’m trying to build a cloning station and i was wondering if FOG is suitable for what i am afterI have a i7 PC that has multiple USB 3.0 ports
Each usb port has a Orico 4xBay SATA HDD connectedThe PC see’s 40 hard drives connected
Question is , is FOG capable loading a source image and deploy it on the HDDs connected simultaneously?
If so, is it also able to format the 40 HDDs?
Thank you !
Zion
In regards to the original question, it may be possible to assign each HDD to a virtual machine and deploy to each one. Can’t say I’d recommend doing that though.
Ok. We’ll stay at 14. I imagine the network admin wouldn’t like it if I updated the whole OS while still retaining the trunk snapshot (because it saves the changes to be able to revert.)
Just noticed the the directory that fog is in is /root/fogproject_trunk. Will there be any issues if I rename the directory to /root/fogproject/. Want to keep installation as inline with stock settings as possible.
edit: So, noticed that git isn’t installed on the trunk server. Not sure what he used when he set this up. I’ve always used git.
We don’t use the Power Management feature, so no issue there.
The live server is on Ubuntu 14.04.4. Would you recommend staying on 14 or maybe moving to 16?
Not a big deal for me. I’m not even the one who requested this, lol.
I’ve finally gotten approval to upgrade our live server from revision 5837 (dev branch that came out just before 1.3 RC’s).
Are there any expected or known issues that might arise?
I’ve disabled the client updater and a snapshot of the server will be taken prior to update, just in case. Wasn’t sure how FOG would like it if the hosts received the new client, but the server ended up getting rolled back.
So, I never did get this to work. I got busy and was unable to reply back while I was at work.
Some of those features are under the compatibility test option. There is the advanced menu, I’m not sure what’s in it, but you can have it show up for all hosts by toggling that option in the settings.
@Tom-Elliott said in New PXE menu entry: Deploy Image & Shutdown:
Ok. I’ve done the following.
root@hs-fog:~# wget -O /var/www/fog/lib/fog/bootmenu.class.php https://raw.githu busercontent.com/FOGProject/fogproject/working/packages/web/lib/fog/bootmenu.cla ss.php
--2017-05-17 23:03:43-- https://raw.githubusercontent.com/FOGProject/fogproject /working/packages/web/lib/fog/bootmenu.class.php
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.124.1 33
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.124. 133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 62089 (61K) [text/plain]
Saving to: ‘/var/www/fog/lib/fog/bootmenu.class.php’
/var/www/fog/lib/fo 100%[===================>] 60.63K --.-KB/s in 0.03s
2017-05-17 23:03:44 (1.97 MB/s) - ‘/var/www/fog/lib/fog/bootmenu.class.php’ save d [62089/62089]
root@hs-fog:~# reboot
After reboot I booted to pxe menu with a registered host and deployed an image to it with the modified “Deploy Image” option.
I then went to this address.
http://10.20.21.136/fog/service/ipxe/boot.php?mac=<hostmac>
And got the following results:
#!ipxe
set fog-ip 10.20.21.136
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.20.21.136/fog/ consoleblank=0 rootfstype=ext4 storage=10.20.21.136:/images/ storageip=10.20.21.136 mac=<hostmac> ftp=10.20.21.136 storage=10.20.21.136:/images/ storageip=10.20.21.136 osid=9 irqpoll hostname=<hostname> chkdsk=0 img=Windows10 imgType=n imgPartitionType=all imgid=1 imgFormat=0 PIGZ_COMP=-9 hostearly=1 type=down
imgfetch init_32.xz
boot
It’s deploying now. I don’t see the shutdown=1 option in there.
@Tom-Elliott I’ll test in the morning (8 hours from now) when I get back to my office. Although I could probably connect to VPN and deploy image into a VM.
edit: I ran the script and updated the file on my test server. Can’t access a computer on the correct vlan to deploy an image to. Will continue in the morning.
Would it be possible to select a default image and snapins and not have it show those options?