After you run the SetDPMServer.exe executable with the -isNonDomainServer switch on the workgroup server, you can attach the DPM agent on the DPM server by using the Attach-NonDomainServer.ps1 Windows PowerShell command instead of running the wizard from the DPM console. To do this, you need to run the following command:
.Attach-NonDomainServer.ps1 -DpmServerName <DPMserverName> -PSName <ProtectedServerName> -UserName <userName> -Password <Password>
.Remove-ProductionServer.ps1 -DpmServerName <DPMserverName> -PSName <ProtectedServerName>.
You can also configure a workgroup computer after the agent is installed on the protected server, for example, in case you want to update the password for NTLM authentication. To do this, you need to run the SetDPMServer.exe command with the -isNonDomainServer switch, followed by the -updatePassword parameter, as follows:
SetDpmServer.exe -dpmServerName <serverName> -isNonDomainServer -updatePassword
Then, on the DPM server, you'll need to run the Update–NonDomainServerInfo.ps1 PowerShell cmdlet, as follows. This will refresh the agent information for the protected computer:
.Update–NonDomainServerInfo.ps1 -DpmServerName <DPMserverName> -PSName <ProtectedServerName> -NewPassword <Password>
Finally, if the protected server is in a workgroup or untrusted domain, then make sure that the password for the local user account on the DPM server and the protected server is set to never expire (Password never expires), otherwise the Agent Status in the DPM console will report with Error status when the password expires:
