it has been OK, not played for a week or so. come back and not working. using FOG server to deploy other machines (old images with new agent)
Have completed the certs and it’s still an issue
it has been OK, not played for a week or so. come back and not working. using FOG server to deploy other machines (old images with new agent)
Have completed the certs and it’s still an issue
7166
just looking into one machine at the moment due to new image, not a lot using new fog server.
Tom Elliott, got me thinking about a “copy” of our windows DHCP server on another DC, that was a backup to when we had issues.
this DHCP is never to be switched on and it’s approx 3 years out of date.
Guess what, somehow (someone) has authorised this scope.
Thanks to everyone who helped.
have checked twice, no reservation.
Also works after pause, thought that would still resolve incorrect reservation info.
it’s back in the office now and still doing it, so not switch equipment.
We had a fog server .032 on IP 192.168.47.254 (currently unplugged)
New server called (Latest SVN) on IP 192.168.39.6
One machine out there is stuck in a boot loop. Now the strange this is it’s getting to TFTP and it’s got the OLD server IP listed.
fails and restarts. also strange is if I pause boot at step of “Configuring” for a few seconds then continue it picks up the correct IP.
(it also fails if old FOG is plugged in)
I have never entered the IP of the old fog into the new fog
i have checked and no DHCP entries exist for this host.
I have deleted and recreate the host in FOG in case of custom loaders
Any Idea’s?
Please note this image is NOT from the console, just an example of the bootup issue location.
Yep you are correct.
not sure how I missed it. I searched for my hostname in the reg with no matches.
It was 64 and i didn’t look under the Wow6432Node folder.
Oh well, thanks
on the old version there was an ini file to control setting of FOG service.
how would you update the hostname / IP in the new fog service
With build 7108
Thanks
i’ve moved the client to use the new server by editting the host file.
client runnin service from 0.32 pointing at Dev FOG =
https://forums.fogproject.org/topic/4191/fog-client-problems/2
Please advise
you chaps are the best. !
yeh an upgrade would be best when we go live with fog when released.
So playing with SVN 7098
we currently use 0.32 on site. do I need to update the FogService from the old version?
Well i’m now up to date as of SVN (unknown number at moment)
Anyway, this did not resolve the issue on it’s own but changing the PXE options worked just fine. Exit to 1st HDD.
i guess would have worked before but it’s better now anway.
Thanks
lol, OK i’ll update that too and report back sometime next week.
Sounds like a plan. I’ll complete anyway and report back next week sometime.