Machine requests fail when Microsoft Distributed Transaction Coordinator (DTC) remote transactions are disabled on Windows server machines.


If you provision a machine when remote transactions are disabled on the Model Manager portal or the SQL Server, the request will not complete. Data collection fails and the machine request remains in a state of CloneWorkflow.


DTC Remote Transactions are disabled in the IaaS SQL Instance used by the vRealize Automation system.


  1. Launch Windows Server Manager to enable DTC on all vRealize servers and associated SQL servers.

    In Windows 7, navigate Start > Administrative Tools > Component Services.


    Ensure that all Windows servers have unique SIDs for MSDTC configuration.

    In addition, the IaaS Manager Service host must be able to resolve the NETBIOS name of the IaaS SQL Server database host. If it cannot resolve the NETBIOS name, add the SQL Server NETBIOS name to the Manager Service machine /etc/hosts file and restart the Manager Service.

  2. Open all nodes to locate the local DTC, or the clustered DTC if using a clustered system.

    Navigate Component Services > Computers > My Computer > Distributed Transaction Coordinator.

  3. Right click on the local or clustered DTC and select Properties.
  4. Click the Security tab.
  5. Select the Network DTC Access option.
  6. Select the Allow Remote Client and Allow Remote Administration options.
  7. Select the Allow Inbound and Allow Outbound options.
  8. Enter or select NT AUTHORITY\Network Service in the Account field for the DTC Logon Account.
  9. Click OK.
  10. Remove machines that are stuck in the Clone Workflow state.
    1. Log in to the vRealize Automation product interface.


    2. Navigate to Infrastructure > Managed Machines.
    3. Right click the target machine.
    4. Select Delete to remove the machine.