windows 10 fog service
-
we are looking at deploying windows 10 within school but have found that the fog service is not working and auto adding to active directory , it worked fine with windows 7 , i upgraded the image but now it doesn’t , has anybody else experienced this?
thanks -
it seems this is only happening for updates , works fine on fresh installs
-
We would need to know what version of FOG you’re using, and exactly what version of the fog client. If you look at the cloud in the top left of the web interface, it has a number in it’s corner.
-
Have you checked the FOG service log file on the client yet?
-
it is version 1.2.0 and version 3.0 or fog service
thanks -
@Jamie-Read said:
it is version 1.2.0 and version 3.0 or fog service
thanksThe legacy client (the fog client you’re using) was written during XP’s time. It’s no surprise it doesn’t work on Windows 10. And updates/patches to the legacy client have been discontinued.
We have a new client. It’s quite amazing. And right now, it’s only available to FOG Trunk users. Fog Trunk is the developmental version of fog.
Several others and myself have used fog trunk in production for quite some time. It’s fairly stable, and works with newer hardware, and there are massive improvements to both security and performance. That said, minor bugs come and go. You just report them here and the developers take care of them, usually posting a patch within hours. (compared to microsoft posting a patch to a publically known problem 9 to 14 months later, same goes for Google, Android, and Apple).
Let me know if you’d like to try it out.
-
@Wayne-Workman said:
Let me know if you’d like to try it out.
Let me help here, you want to try it out.
You can probably get windows 10 imaging working on the older version of FOG, but if you want everything to work flawlessly, you’re going to need to update, and it’s pretty darn easy.Here are some posts to help out
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
https://forums.fogproject.org/topic/6331/automating-git-updates-for-fog
https://forums.fogproject.org/topic/6010/msi-silent-install/2
https://forums.fogproject.org/topic/4250/new-client-progress -
the version of fog is 1.2.0 and the fog tray is version 0.1
-
@Wayne-Workman thanks for this , it would benifit us alot if we could give it a try
thanks -
@Jamie-Read Look here for instructions: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
make sure you do a db backup first, or a snapshot, or whatever you need.
-
I’m having a similar problem. I updated to the latest trunk build, and when I try to install the new client it says “Failed to download CA certificate” then backs out of the installer.
-
@nlaplante Are you using the FQDN of the Fog server during installation, or the FOG Server’s IP address? What version of FOG? Could host antivirus be causing it?
-
@Wayne-Workman and @nlaplante were you able to solve it? I am stuck at the same spot and can’t seem to get it to work. I have tried
Server Adress:
fog-server
http://X.X.X.X/fog-server
http://X.X.X.X/
X.X.X.X
X.X.X.X/fog-serverWeb Root:
/fog
http://X.X.X.X/fog
X.X.X.X/fogboth Enable FOG tray and Put Log File in Root is checked.
I am running version 7649
-
@dat So… when installing the fog client, you put in just the FOG server’s IP, or it’s name if you have an “A” record created in DNS. In the FOG Web Interface, you would supply your AD information in the FOG Configuration -> FOG Settings -> AD area.
-
@Wayne-Workman I am just using the IP address. I have tried http://xxx.xxx.185.79/ and xxx.xxx.185.79 with no luck. am I doing it wrong?
-
@dat said in windows 10 fog service:
@Wayne-Workman I am just using the IP address. I have tried http://xxx.xxx.185.79/ and xxx.xxx.185.79 with no luck. am I doing it wrong?
Yes, you are. Just put in the IP. nothing else. Loose the http stuff. If JUST the IP address isnt’ working, I’d question if the fog server is even installed right, or if firewall or SELinux is preventing communication.
-
@Wayne-Workman thanks. That worked!
-
@dat What worked?
-
-
@dat
Just a side note.
If you make a dns cname/alias of the name fog-server for your fog server then the default options will always work.
Which makes scripting a bit easier. Granted you can add command-line options for your fog server ip or hostname if you choose. I just find it much easier if you make the default options work.If you don’t know what a cname/alias is or how to make it, how it’s done depends on what type of dns and or dhcp server you’re using.