The customer configured Autofs on the Linux golden image to automatically mount NFS shares. After provisioning Linux VDAs through MCS, it was observed that the Autofs service was not running on the target machines.

Further investigation revealed that the autofs startup failure was caused by the SSSD service failing to start successfully during system boot. Since autofs depends on SSSD for identity and authentication-related operations, the autofs service could not start when SSSD was unavailable.

On MCS-provisioned Linux VDAs, the SSSD service failed to start during the initial boot because the system had not yet completed the Active Directory domain join process.

As a result, dependent services such as autofs were unable to start successfully.

The issue was resolved by modifying the ad_join.sh script to restart the autofs service after the set_vda step, ensuring that SSSD had been properly initialized following the domain join process.

The following line was added to the script after "setup_vda"

restart_service autofs systemctl

A customer published Linux VDAs using Machine Creation Services (MCS) and configured the autofs service to automatically mount NFS shares. However, after the MCS-provisioned Linux VDAs booted, the autofs service failed to start, preventing the NFS shares from being mounted automatically.