A very quick post to serve as a memory jogger in the future – we had a desktop pool all of a sudden have desktops show ‘configuration error’ after finishing cloning.
Monitoring the reclone process for a test we could see the desktop sit on ‘starting other agent services’ for a few minutes before settling on ‘configuration error’
We’d recently moved the pair of Horizon connection servers to a new cluster so naturally assumed something was amiss from this process – but the problem had only manifested in the main production pool.
Through a process of troubleshooting we ruled out template by cloning it into another OU successfully in another pool
Investigation of the Horizon logs on the failing desktops showed an Azure AD join error which led us to suspect there was a newly introduced configuration change on the OU.
The customer investigated and confirmed that this was the issue, once corrected the desktops functioned properly.