How to undo a Member Server Scenario (4267990)

A parallel isolated installation of KACE Desktop Authority commonly referred to as a "Member Server Scenario" may have been used for testing purposes and now it is desired to migrate that setup to use domain controllers instead of member servers.  This article contains the steps necessary for that migration from member servers to domain controllers.

 Do the following:

• Review the following registry value in one of the machines used for testing:

  HKLM
Key: Software\ScriptLogic\Device Agent\Global Settings
Value: Machine_Sysvol_Path
Type: REG_SZ
Data: \\MemberServerName\Sharename  

If this registry value exists, then it must be deleted from all the testing machines.  The user-based script may be used to automate the removal of this value as it is a setting solely used to instruct computer based management on where to locate the DA computer-based configuration files in the event that they will not be located in the default location.   

• Launch the KACE Desktop Authority Manager console and navigate to: Deployment Settings | Service Manager | Service Management and Uninstall the services on the Member Server and then delete the server from the Service Management grid.
• Add all of the DCs and install the Administrative Service (required) and the Update Service (optional, if needed).
• Set one of the servers as a replication target.
• Replicate all files by clicking on the replicate all files button on the lower left of the management console.
• Change the assigned logon script from the currently assigned script to the SLOGIC.bat script.

If there is another Desktop Authority server running an old version on the environment:

• Open the Desktop Authority Console on the old server and remove all the domain Controllers from Deployment Settings | Service Manager | Service Management.
• Stop and Disable the Desktop Authority services on the old server.

Note:  Both servers have a share named SLogic$, SLScripts$ and SLDAClient$.  To avoid issues, it is best practice to uninstall the old console or at least disable the shares on the originating server if the server will remain in the domain.