- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was the agent installed during audit mode setup when you created the master VM? Might be nothing but maybe its trying to run the service as a system account that's not available due to the name change.
Also you stated that you are using Windows 10 x64 but the install patch is x86. Could this be an issue? We're using instant-clones without a composer so I don't know about that agent but our Horizon Agent had to be installed in x64 architecture.
Best regards,
Raetke