Upgrading 1.5 to 1.6 Client to Agent migration

[astrugatch]

I didn’t see something in the docs. If I missed it please let me know. We have been running 1.5.x versions and make heavy use of the fog client. We will be prepping to upgrade to 1.6.x in the near future but want to confirm the process of moving to the fog agent. Will currently fog client devices see the change and pull the agent or do we need to push the agent outside of fog server to get it in place?

[Tom Elliott]

@astrugatch Short answer: no, the existing FOG Client does not pull the agent by itself. You push the agent with the tool you already use to deploy software.

What happens when you upgrade the server

• Your legacy FOG Client installs keep working against 1.6. The server still serves the legacy client endpoints, so you can run both while you migrate.
• Nothing on the server needs to change first. Hosts, groups, snapins, printers, power schedules and module settings all carry over.
• The legacy Client Updater module is gone in 1.6. So the old client cannot update itself into the agent.
• The FOG server does not host the agent installer. It comes from the GitHub releases page: https://github.com/FOGProject/fog-agent/releases/latest

How to move a machine to the agent

Install the agent MSI on the machine. The MSI finds the legacy “FOG Service” and removes it for you. Do not run the two side by side.

For a silent push (GPO, PDQ, SCCM/Intune, or a script):

msiexec /i fog-agent-<version>-x64.msi /qn SERVER=https://your-fog-server/fog CAFINGERPRINT=<fingerprint> TOKEN=<token> /l*v C:\fog-agent-install.log

• SERVER is your web UI address with /fog on the end. Old scripts that use WEBADDRESS and WEBROOT still work.
• CAFINGERPRINT is the SHA-256 on the Root row of FOG Configuration → Certificates. Leave it out if your web UI uses a public or corporate certificate that the machines already trust.
• TOKEN is optional. Create one under Hosts → Agent Enrollment Tokens. With a token, the host enrolls with no click. Without one, each host waits under Hosts → Pending Agents until you approve it.

The FOG Client page in the 1.6 main menu shows the same command with your server address already filled in.

Images

You can put the agent in your image. Capture the machine as it is, no sysprep needed. A deployed clone detects that it is a different machine and enrolls as itself. If FOG deployed to that host in the last 24 hours, the server approves it automatically.

Docs

• Install and migrate: https://docs.fogproject.org/en/latest/installation/client/install-fog-agent (see “Moving from the legacy client”)
• What changes for an admin (printers, AD join, user tracking): https://docs.fogproject.org/en/latest/management/web/fog-agent
• Reference: https://docs.fogproject.org/en/latest/kb/reference/fog-agent-reference
• Troubleshooting: https://docs.fogproject.org/en/latest/kb/troubleshooting/fog-agent-troubleshooting

If an install fails, post C:\ProgramData\FOG\fog-agent.log and the msiexec log here.