Merge pull request #58177 from Rajeswari-Mamilla/master

Documentation changes

Author: itechedit

articles/site-recovery/media/vmware-azure-manage-process-server/LoadBalance.png

@@ -218,9 +218,16 @@ For configuration server deployments before May 2016, certificate expiry was set
 2. The expiry date appears under **Configuration Server health**.
 3. Select **Renew Certificates**.
 
-## Update Windows licence
+## Refresh Configuration server
 
-The licence provided with the OVF template is an evaluation licence valid for 180 days. For uninterrupted usage, you must activate Windows with a procured licence.
+1. In the Azure portal, navigate to **Recovery Services Vault** > **Manage** > **Site Recovery Infrastructure** > **For VMware & Physical machines** > **Configuration Servers**
+2. Click on the configuration server you wish to refresh.
+3. On the blade with details of chosen configuration server, click **More** > **Refresh Server**.
+4. Monitor the progress of the job under **Recovery Services Vault** > **Monitoring** > **Site Recovery jobs**.
+
+## Update Windows license
+
+The license provided with the OVF template is an evaluation license valid for 180 days. For uninterrupted usage, you must activate Windows with a procured license.
 
 ## Failback requirements
 

articles/site-recovery/media/vmware-azure-manage-process-server/LoadPS.PNG

@@ -27,7 +27,41 @@ Upgrade an process server running on premises, or in Azure (for failback purpose
 > [!NOTE]
   Typically, when you use the Azure Gallery Image to create a process server in Azure for the purposes of failback, it's running the latest version available. The Site Recovery teams release fixes and enhancements on a regular basis, and we recommend you keep process servers up-to-date.
 
+## Balance the load on process server
 
+To balance load between two process servers,
+
+1. Navigate to **Recovery Services Vault** > **Manage** > **Site Recovery Infrastructure** > **For VMware & Physical machines** > **Configuration Servers**.
+2. Click on the configuration server to which the process servers are registered with.
+3. List of process servers registered to the configuration servers are available on the page.
+4. Click on the process server on which you wish to modify the workload.
+
+    ![LoadBalance](media/vmware-azure-manage-process-server/LoadBalance.png)
+
+5. You can either use **Load Balance** or **Switch** options, as explained below, as per the requirement.
+
+### Load balance
+
+Through this option, you can select one or more virtual machines and can transfer them to another process server.
+
+1. Click on **Load balance**, select target process server from the drop down. Click **OK**
+
+    ![LoadPS](media/vmware-azure-manage-process-server/LoadPS.PNG)
+
+2. Click on **Select machines**, choose the virtual machines you wish to move from current process server to the target process server. Details of average data change are displayed against each virtual machine.
+3. Click **OK**. Monitor the progress of the job under **Recovery Services Vault** > **Monitoring** > **Site Recovery jobs**.
+4. It takes 15 minutes for the changes to reflect post successful completion of this operation OR [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) for immediate effect.
+
+### Switch
+
+Through this option, entire workload protected under a process server is moved to a different process server.
+
+1. Click on **Switch**, select the Target process server, click **OK**.
+
+    ![Switch](media/vmware-azure-manage-process-server/Switch.PNG)
+
+2. Monitor the progress of the job under **Recovery Services Vault** > **Monitoring** > **Site Recovery jobs**.
+3. It takes 15 minutes for the changes to reflect post successful completion of this operation OR [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) for immediate effect.
 
 ## Reregister a process server
 

articles/site-recovery/media/vmware-azure-manage-process-server/Switch.PNG

@@ -17,6 +17,7 @@ Installation of Mobility service is a key step during Enable Replication. The su
 * Credential/Privilege errors
 * Connectivity errors
 * Unsupported Operating systems
+* VSS installation failures
 
 When you enable replication, Azure Site Recovery tries to push install mobility service agent on your virtual machine. As part of this, Configuration server tries to connect with the virtual machine and copy the Agent. To enable successful installation, follow the step by step troubleshooting guidance given below.
 
@@ -36,13 +37,10 @@ If you wish to modify the credentials of chosen user account, follow the instruc
 ## **Connectivity check (ErrorID: 95117 & 97118)**
 
 * Ensure you are able to ping your Source machine from the Configuration server. If you have chosen scale-out process server during enable replication, ensure you are able to ping your Source machine from process server.
-  * From Source Server machine command line, use Telnet to ping the configuration server/ scale-out process server with https port (default 9443) as shown below to see if there are any network connectivity issues or firewall port blocking issues.
+  * From Source Server machine command line, use Telnet to ping the configuration server/ scale-out process server with https port (135) as shown below to see if there are any network connectivity issues or firewall port blocking issues.
 
-     `telnet <CS/ scale-out PS IP address> <port>`
-
-  * If you are unable to connect, allow inbound port 9443 on the configuration server/ scale-out process server.
+     `telnet <CS/ scale-out PS IP address> <135>`
   * Check the status of service **InMage Scout VX Agent – Sentinel/Outpost**. Start the service, if it is not running.
-
 * Additionally, for **Linux VM**,
   * Check if latest openssh, openssh-server, and openssl packages are installed.
   * Check and ensure that Secure Shell (SSH) is enabled and is running on port 22.
@@ -93,6 +91,43 @@ Another most common reason for failure could be due to unsupported operating sys
 
 To learn about which operating systems are supported by Azure Site Recovery, refer to our [support matrix document](vmware-physical-azure-support-matrix.md#replicated-machines).
 
+## VSS Installation failures
+
+VSS installation is a part of Mobility agent installation. This service is used in the process of generating application consistent recovery points. Failures during VSS installation can occur due to multiple reasons. To identify the exact errors, refer to **c:\ProgramData\ASRSetupLogs\ASRUnifiedAgentInstaller.log**. Few common errors and the resolution steps are highlighted in the following section.
+
+### VSS error -2147023170 [0x800706BE] - exit code 511
+
+This issue is mostly seen when an anti-virus software is blocking the operations of Azure Site Recovery services. To resolve this,
+
+1. Exclude all folders mentioned [here](vmware-azure-set-up-source.md#exclude-antivirus-on-the-configuration-server).
+2. Follow the guidelines published by your anti-virus provider to unblock the registration of DLL in Windows.
+
+### VSS error 7 [0x7] - exit code 511
+
+This is a runtime error and is caused due to insufficient memory to install VSS. Ensure to increase the disk space for successful completion of this operation.
+
+### VSS error -2147023824 [0x80070430] - exit code 517
+
+This error occurs when Azure Site Recovery VSS Provider service is [marked for deletion](https://msdn.microsoft.com/en-us/library/ms838153.aspx). Try to install VSS manually on the source machine by running the following command line
+
+`C:\Program Files (x86)\Microsoft Azure Site Recovery\agent>"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"`
+
+### VSS error -2147023841 [0x8007041F] - exit code 512
+
+This error occurs when Azure Site Recovery VSS Provider service database is [locked](https://msdn.microsoft.com/en-us/library/ms833798.aspx).Try to install VSS manually on the source machine by running the following command line
+
+`C:\Program Files (x86)\Microsoft Azure Site Recovery\agent>"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"`
+
+### VSS exit code 806
+
+This error occurs when the user account used for installation does not have permissions to execute the CSScript command. Provide necessary permissions to the user account to execute the script and retry the operation.
+
+### Other VSS errors
+
+Try to install VSS provider service manually on the source machine by running the following command line
+
+`C:\Program Files (x86)\Microsoft Azure Site Recovery\agent>"C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd"`
+
 ## Next steps
 
 [Learn how](vmware-azure-tutorial.md) to set up disaster recovery for VMware VMs.