FOG 1.6 with fog-agent 0.1.6, agent renames all PC's to the same golden image name when not using sysprep

[rdr]

Hi,

I am testing FOG server 1.6 (latest) to use in our PC labs. Installed Windows 10 and all the required apps to the one of the PC’s (MMF-LAB2-00). Then imported all hosts with a simple CSV file (MAC,HOST NAME). Then installed latest fog-agent and approved it in FOG server UI. So far so good. I created a capture task and captured the image from the host MMF-LAB2-00. Then created a deployment task for the remaining PC’s. Deployments also worked without any problem.

The problem is after a few minutes, there appeared a popup messages on the desktops that is saying FOG agent will rename the computer with the name “MMF-LAB2-00”. And all the PC’s rebooted with the name MMF-LAB2-00 insted of their names on FOG server, MMF-LAB2-01, 02, 03 etc.

So what am I doing wrong here? Is sysprep mandatory for fog client? Why the fog agent does not poll the name that is matched with its MAC address in FOG UI?

Regards,

Rahman

[Tom Elliott]

@rdr the fog agent is brand new and is attempting to modernize how the client did things. I wasn’t fully ready for people to be testing it live quite yet, though glad to have people doing so.

I suspect the identity.json is from that of the original machine and it’s using that as the marker for all the machines you’ve deployed to. Since that identity was for that machine, all machines are currently thinking they are that machine.

[rdr]

@Tom-Elliott Thanks for answer. So do you suggest to use FOG client instead of FOG agent? Or use the agent properly? If I decie to use the agent, should I delete the identity.json file before capturing the image? Then I need to approve all the agents of deployed images after deployment tasks?

[Tom Elliott]

@rdr You found a real bug. Sysprep is not needed, and it would not have helped.

Cause: the image carries the agent’s key and certificate from MMF-LAB2-00.
The agent compared the machine’s SMBIOS identity with that key only when it
had no certificate. A deployed copy has one, so every PC connected as
MMF-LAB2-00 and took its name.

fog-agent 0.1.7, released today, makes the check on every start.

To fix the PCs you already deployed:

• Go to FOG Configuration > FOG Settings > General Settings and set
  FOG_AGENT_DESIRED_VERSION to 0.1.7. Every enrolled agent updates itself,
  including each PC that thinks it is MMF-LAB2-00.
• After the update, each PC sees that it is not MMF-LAB2-00, makes a new
  key, and enrolls as itself. FOG matches it to its host by MAC.
• If FOG deployed to that host in the last 24 hours, the enrollment is
  approved automatically. If not, approve it under Hosts > Pending Agents.
  The agent then renames the PC to its name in FOG.

Please post back whether the names come right.