Since we are on Muster 9 (before we were still on 5) we loose the drive mapping on a machine after restart of the machine.
After restarting a machine it starts the render service and the machine comes available for rendering in the dispatcher.
When it gets a job, it starts rendering and then aborts because it can not find the mapped drive.
When i then restart the render service on the machine it works fine.
It happens with all of our render nodes and workstations.
No this is not a known problem. Check your renderclient.log file just after the first restart (when the Drive mappings is supposed to not being mapped), it should report a reason for not mapping the drive. Maybe when you restart the machine the network services are still not up on the drive mapping side ?
Well that’s part of the regular windows startup process, you can bypass the problem by configuring the drive mappings mounting at job startup instead of service startup, this will mount/unmount the drives before a job starts and I think they will be available at that moment