7.2 Add Workload - Discovery

Problems or Messages


“Discover Server Details {hostname}” FailedProgress: 0%Status: NotStarted

This error can occur for several reasons and each has a unique solution:

  • For environments using a local proxy with authentication, bypass the proxy or add the proper permissions. See knowledgebase article Q20339 for more details.

  • If local or domain policies restrict required permissions, follow the steps outlined in knowledgebase article Q20862.

Workload Discovery failed

“Could not find file output.xml


“Network path not found”

There are several possible reasons for the “Could not find file output.xml” error:

  • Anti-virus software on the source could be interfering with the discovery. Disable the anti-virus software to determine whether or not it is the cause of the problem. See Disabling Anti-Virus Software.

  • File and Printer Sharing for Microsoft Networks may not be enabled. Enable it under the Network Interface Card properties.

  • The C$ and/or Admin$ shares on the source may not be accessible. Ensure the Forge VM can access those shares. See Enabling File/Share Permissions and Access.

  • Change the flag ForceMachineDiscoveryUsingService to true in the web.config file in the \Program Files\PlateSpin Portability Suite Server\Web folder.

  • The Server and/or the Workstation service may not be running. If this is the case, enable them and set their startup mode to automatic.

  • The Windows remote registry service is disabled. Start the service and set the startup type to automatic.

7.2.1 Disabling Anti-Virus Software

When working with a source workload running anti-virus software, issues are sometimes encountered where the anti-virus software is blocking some of the Forge functionality. These problems primarily occur when adding the workload to be protected.As part of the process of adding the workload, Forge gathers a profile of the source. The profile contains information on the disks, operating system, software and services installed, along with other components. To perform this data gathering, Forge leverages a combination of WMI and Remote Registry calls. Some of the calls made can sometimes be interpreted as intrusions by anti-virus software, and could restrict access to the necessary data.In order to ensure functionality, it may be necessary to disable the anti-virus service prior to adding the workload.Anti-virus software can sometimes also lock access to certain files, allowing only certain processes or executables to access them. This can sometimes prevent Forge from replicating some files when using file-based protection. In this case, when configuring the protection of the workload, you are able to select services to disable – such as services installed and used by anti-virus software. These services are only disabled for the duration of the file transfer, and are restarted once the process completes. This is not necessary when performing VSS or BBT protection tasks.

7.2.2 Enabling File/Share Permissions and Access

To successfully protect a workload, Forge needs to successfully deploy and install the OFX Controller and, if using BBT, the block-based agent. When deploying those components to the workload being protected, as well as when gathering information about the workload during the “add workload” process, Forge uses the source machine’s administrative shares. Forge needs administrative access to the shares using either a local administrator account or a domain admin account for this to work.

Ensure that the Administrative shares are enabled.

  1. Right-click My Computer on the desktop and select Manage.

  2. Expand System Tools > Shared Folders > Shares

  3. In the Shared Folders you should see C$ and Admin$, among other shares.

    Once you have confirmed that the shares are enabled you need to ensure that they are accessible from the Forge Management VM.

From the Forge Management VM:

  1. Click Start > Run.

  2. Type server>\C$ and then click OK.

  3. If prompted for credentials, use the same credentials that will be used to add the workload in Forge.

    The directory is opened and you should be able to browse and modify the contents as desired.

  4. Repeat the process for all shares with the exception of the IPC$ share. The IPC$ share is used for credential validation and authentication purposes by Windows. It is not mapped to a folder or file on the workload, so the test will always fail, however the share should still be visible in the above test.

Forge will not modify the existing content of the volume, however it will create its own directory, to which it requires access and permissions.