Posts made by Joe Schmitt

I’m not seeing it:

And I’m on 3654.

The encryption is not optional. Making it so would open up quite a few security holes.

Just a heads up, calling recreate CA will cause all beta clients deployed to stop trusting your FOG server and will require a re-installation of the client / re-imaging.

I sent you a chat message a few days ago, can you double check if you got it?

My guess is that the security tokens are somehow becoming out of sync. Can you post the “Authentication” section of the client log when it messes up? (Preferably in a formatted code-block in the forum post)

Could be a bug where imaging a pc isn’t clearing the security token anymore. @Tom-Elliott ideas?

Go to the host on the web portal and click “Reset Encryption Data”.

What is the revision number? “latest” doesn’t mean much around here because we commit many times throughout the day. Preferably check the cloud in the upper left hand corner of the web portal, or get the commit hash (I’m assuming its 8442096388f0e044f19bc18b9c9e6a3c86f1022a )

General rule of thumb: post issues on the forum. Only telling a developer tends to make the issue get lost. I seem to remember Tom mentioning something about this to me awhile ago, but once again, I was never directly told nor shown logs so I forgot about it.

I’ll take a look at Samba NT domains (I may need your help for pre-release testing though).

Mind uploading the ini file in the etc folder of the client installation?

Problem solved. It was an issue with the installer.

Ubuntu is … a hassal and is kind of expected to haver some hiccups. I’d recommend using Cent OS or Fedora. Or if you are more comfortable with Ubuntu, 12.04 LTS is great, its actually what one of my development servers run on.

Just to back what Wayne was saying, my development servers live in a VMware vSphere cluster. I can guarantee you I am not using IDE HDDs.

What version of FOG? (1.3 is not released yet) You should be able to find the revision number in the installer / install logs.

You have two options:

1. Re-install the client (you MUST uninstall it manually first)
2. Make both FOG servers have the same CA keys, this will make the client trust either one.

Be sure to install that ca.cer.der file under Local System and as a Trusted Root Certificate Authority. What happened is that the client “pinned” an old format of the CA certificate that Tom released for a few versions in hopes of multiple FOG server support but was removed shortly after.

Can you open the certificate on windows and checked the “Issued to” and “Issued by” fields?

@holzfisch said:

http://192.168.1.14/fog/management/other/ssl/srvpublic.crt

Can you try downloading that file manually? If my understanding of the german is correct, it is saying that the computer could not establish a session with the server meaning it is possibly a network issue.

That error will always occur on the first run. As long as it still authenticates you are fine. What concerns me is the CA cert issue in the logs. It seems the handshake public key is missing. Tom will be able to help you regenerate it

Fixed and v0.8.2 released