@GregorS
The problem is with your server. Notice the log lines

 14.12.2015 12:53 Data::RSA ERROR: Certificate validation failed
 14.12.2015 12:53 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid)
 14.12.2015 12:53 Middleware::Authentication ERROR: Could not authenticate
 14.12.2015 12:53 Middleware::Authentication ERROR: Certificate is not from FOG CA

@Tom-Elliott would be able to help you debug why your server certs are incorrect.

@Brian-David that shortcut should not exist. FOGUserService is responsible for starting the tray. What is the registry value of

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FOG\Tray If you are on a 32 bit system, remove the Wow6432Node.

This is bug. I normally see this in my development builds if I don’t increment the product version.

Can you check if a “FOGUserService” process is running when you log in?

Are you restarting the computer after installing the client?

@Kiweegie GPO is your best bet. One msiexec to remove the old client, and then another to install the new one.

Sounds like a possible sever error. @Tom-Elliott

As for why you get #!im when you go their manually, that url in the log is a POST request with hidden data in it (the encrypted token / key)

@jmeyer

The client automatically updates itself whenever you upgrade the server.

@jmeyer , v0.9.9 is released. This should fix your issue. Can you confirm this when you get a chance?

@Wayne-Workman v0.9.8 will suffer from the same issue. I found why this is happening and after I test the patch I’ll release v0.9.9

Our current builds use “admin” as the username for the web portal.

@zavo v0.9.8 released. This should correct this issue. Can you confirm when you have a chance?

@zavo Thank you so much for reporting this. While working on this bug, I came across the reason why I was never able to get my v0.10 builds running on Windows! It was a problem with the authentication handshake stalling the Windows Service Controller. I’m currently re-designing how/when authentication happens in the client and will retrofit the patch onto v0.9.X shortly.

This patch will also prevent the service from killing VM network connections for the first few minutes after windows starts.

@Scott-B we have something similar planned for FOG 2.0. However, for 1.X we don’t want to add any more features (this one would take some significant time). Our focus now is to solely get 1.X as stable as possible for a 1.3 release.

@zavo , the problem is that the server still has an active encryption session from last boot, so re-authentication is not running. I’ll push a patch in a couple days (I need to ensure it won’t accidentally denial of service the server if there are errors on the server side).

https://github.com/FOGProject/fog-client/issues/32

@raymondub said:

ing an up to date documentation for the new client to install printers. Is it still working in the same way ?
I got problem with the ntprint.inf.

It still works the same way. This tool will help you get the printer information needed for the fog-server configuration:
https://github.com/FOGProject/fog-client/releases/download/0.9.7/PrinterManagerHelper.exe

@raymondub What doc are you looking for?

Is the legacy client still installed on the machine? You have to remove the old client from a computer before installing the new one.

@Psycholiquid
Here’s all the CLI options for the client

msiexec /i FOGService.msi /quiet USETRAY="0" HTTPS="0" WEBADDRESS="192.168.1.X" WEBROOT="/" ROOTLOG="0"

Firstly, all options are optional. Here’s what they all do

• USETRAY: defaults to "1", if "0" the tray will be hidden
• HTTPS: defaults to "0", if "1" the client will use HTTPS (not recommended)
• WEBADDRESS: defaults to "fog-server", this is the ip/dns name of your server
• WEBROOT: defaults to "/fog"
• ROOTLOG defaults to "0", if "1" the fog.log will be at C:\fog.log, otherwise %PROGRAMFILES%\FOG\fog.log

So for your question:

msiexec /i FOGService.msi /quiet USETRAY="0" WEBADDRESS="XX.XX.XX.XX"

@Rusty This is the best guide that has been written so far. It does include some text on fog server setup, so skip to the “WORKSTATION IMAGE CREATION” section

https://forums.fogproject.org/uploads/files/1443813159297-imaging-server.pdf