Beginning with Commander 9.4.0, Snow has deprecated the built-in Join Domain workflow step in response to Microsoft hardening and deprecation of DCOM, which was used to perform this action. To continue to accommodate customers who require a Join Domain step in their completion workflow, Snow released a module for joining a VM to a domain in the workflow process which uses WinRM.
After adding the module to the workflow, user may run into the error Computer 'MachineName' failed to join the domain 'DomainName' from its current workgroup 'WorkgroupName' with the following error message: A specified logon session does not exist. it may have already been terminated" as shown below:
The vcommander.log file will show the error as follows:
This error could be an indication that the DomainAdmin credentials created for this module are not saved in the UPN format (username@domain.com).
This can be further confirmed by examining The Event Viewer in Windows on the target VM, which will show an Event ID error 1497 that reads "The machine MachineName attempted to join the domain DomainName but failed. The error code was 1312"
If the issue caused by an incorrect username format for the DomainAdmin credential, it can be remedied by logging into the Snow Commander admin portal and navigating to Configuration > Credentials and highlighting the DomainAdmin credential and clicking edit.
From here, modify the username to match the UPN formatting of user@domain.com, then click Ok to save. Retrying to failed step in Commander should result in a successful joining of the domain using the Join Domain - WinRM module.
See Also
Join Domain Guest OS Workflow Step Fails Due to Microsoft DCOM Update (snowsoftware.com)
Configuring the Join Domain Commander Workflow Module (snowsoftware.com)
Related Articles
Beacon task scheduler error: “A specified logon session does not exist” after installation 7Number of Views Configuring the Join Domain Commander Workflow Module 9Number of Views Normalize fails with error - BDNA User Console logon not authorized as service administrator 21Number of Views AWS adapter fails with error "Failed to find session variable externalID" after upgrading to 2019 R2 adapter 5Number of Views FlexNet Operations On-Premises error: getHibernateSession(): failed to get hibernate session :org.hibernate.exception.Gene… 23Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago