|
Problems or Messages |
Solutions |
|---|---|
|
Authentication error when verifying the controller connection while setting up the controller on the source. |
The account used to add a workload needs to be allowed by this policy. See Group Policy and User Rights. |
|
Failure to determine whether .NET Framework is installed (with exception The trust relationship between this workstation and the primary domain failed). |
Check whether the Remote Registry service on the source is enabled and started. See also Troubleshooting Discovery for Windows Workloads. |
Because of the way that PlateSpin Forge interacts with the source workload’s operating system, it requires the administrator account that is used to add a workload to have certain user rights on the source machine. In most instances, these settings are defaults of group policy; however, if the environment has been locked down, the following user rights assignments might have been removed:
Bypass Traverse Checking
Replace Process Level Token
Act as part of the Operating System
In order to verify that these Group Policy settings have been set, you can run gpresult /v from the command line on the source machine, or alternately RSOP.msc. If the policy has not been set, or has been disabled, it can be enabled through either the Local Security Policy of the machine or through any of the Domain Group Policies being applied to the machine.
You can refresh the policy immediately by using gpupdate /force.
Issue: When you attempt to set up a protection for a Windows server, the following error is displayed:
[Source] Two or more volumes have the same serial number. Change the serial numbers so that they are unique and rediscover the machine.
Workaround: This problem can occur if the Volume Serial Numbers for two or more volumes are the same. PlateSpin Forge requires the serial numbers to be unique.
To resolve this issue, modify the serial numbers for the data volumes as appropriate, and then rediscover the machine. For information about how to use Windows native tools to modify the serial numbers, see KB Article 7921101.