Thank you. yes, you are right the problem is NOT the “//” but SPT on the switch that caused “udhcpc failed”. the solution is posted here:
https://forums.fogproject.org/topic/12248/udhcpc-failed/4
Tested imaging with a dumb switch, and everything worked.
Set up FOG svn destribution, it worked like a charm. 
@Sebastian-Roth I just saw the netdom command at end of wiki, will use that to debug. Thanks.
@Sebastian-Roth I have a real fully qualified domain name, just used “mylocation.mycompany.com” here as example. DNS resolves the domain name.
The set up I used is based on fog wiki:
https://wiki.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting
On FOG server, under either group or just a host, you can specify domain and OU. something like this:
domain is “mylocation.mycompany.com”
OU are “OU=level3,OU=level2,OU=top,DC=mylocation,DC=mycompany,DC=com”
On the AD: we would have tree looks like this:
mylocation.mycompany.com
->top
–>level2
—>level3
the PCs would all be under OU three.
I have tested to use just one OU (top), but still the same, no PCs in OU “top”.
Image capture, multicast & direct deployment are smooth, the issue is with PCs get lost on AD after joining AD, also, they are not going into specified OU.
However, the PCs are in the domain and users can login with domain accounts. The strange thing is that PCs are NOT found anywhere on AD; not in the default OU, not in the specified OU, or anyway along the line. When try to remove PCs from AD using Powershell, it fails with error that computer SID not registered with AD. This might explain why it is not found on AD, also, why the domain users can still log on. To remove PCs from AD, have to use “system” GUI interface. Once it is removed from the domain, add PC using Powershell works again & will put the PC into the correct OU on AD.
Please help. Thank you.
Thank you. yes, you are right the problem is NOT the “//” but SPT on the switch that caused “udhcpc failed”. the solution is posted here:
https://forums.fogproject.org/topic/12248/udhcpc-failed/4
Tested imaging with a dumb switch, and everything worked.
@Cheetah2003 Have you tried to “Reset Encryption Data” after you update the MAC? List “all hosts”, click on the one MAC is changes, the select “Reset Encryption Data”.
Originally thought I miss configured somewhere, so after couple days on the old server and going nowhere, I setup a new server with Ubuntu 18.04 & just FOG 1.5.7.2 ( and let FOG installed all the additional software ); logging into sever is fine. On clients, during PXE boot, they get IPs and find the next sever listed, but is getting the error message “unable to access http://<sever>/fog//index.php” from the FOG server. The double “//” in front of index.php is the problem. I have went through php files in /var/www/fog, but can’t identify which one is giving this. Please help. Thank you.
Just got mine working with FOG svn destribution. The problem with FOG 1.2.0 is likely the kernel can’t support the hardware. In my case the network card.
Set up FOG svn destribution, it worked like a charm.
I am having problem getting FOG 1.2 working with Dell 7040. Appears the FOG kernel doesn’t support the network card in 7040. Getting “failed to mount NFS” “Network unreachable”. The same FOG setup works fine on Dell 790, 7010 and older PCs for both win7 and win10. Any suggestions?