Thank you. Do you know if the legacy client would have the same issue?

Just putting this out there I have not seen anyone post about it if anyone has I apologize but I have found that the Fog Client from 1.3.0 will cause Windows 7 to fail on initial setup after sysprep.

I’m trying to get a image pushed up for a Lenovo G580 and when it starts to boot in to fog it comes up with
ERROR MUX INFO call failed
Mounting File System…Mount:RPC: Remote system error - Network is unreachable mount: mounting (IP Address):/images/dev/ on /images failed: Bad file descriptor
Fatal Error: Failed to mount NFS Volume

I mean that sounds to me like it can not get to the fog server but I can hook another laptop up to the same network port and image it just fine so I know my fog server isn’t down. I also tried 2 other Kernels one being the latest and they did the same thing.

Anyone have any ideas?

How dose FOG go about renaming im just trying to find a better solution than having to remove it from AD and then rename in fog. I need to get it set up to rename it in one place and it take effect everywhere.

So I have the Hostname Changer working my computers and getting there names changed and joining the domain just fine but if I need to change a computer name after imaging I do it from FOG Manager and it changes locally but not in AD. Dose anyone have any info on how I can get it to take the new name in AD from just changing it on the Manager?