Update vmware-physical-manage-mobility-service.md

Author: Rajeswari-Mamilla

articles/site-recovery/vmware-physical-manage-mobility-service.md

@@ -32,12 +32,25 @@ You set up mobility agent on your server when you use Azure Site Recovery for di
 
 ## Update Mobility service through powershell script on Windows server
 
+Before you start ensure that the configuration server, scale-out process servers, and any master target servers that are a part of your deployment are updated before you update the Mobility Service on protected machines.
+
 Use following script to upgrade mobility service on a server through power shell cmdlet
 
 ```azurepowershell
 Update-AzRecoveryServicesAsrMobilityService -ReplicationProtectedItem $rpi -Account $fabric.fabricSpecificDetails.RunAsAccounts[0]
 ```
 
+## Update mobility service manually on each protected server
+
+1. Before you start ensure that the configuration server, scale-out process servers, and any master target servers that are a part of your deployment are updated before you update the Mobility Service on protected machines.
+
+2. [Locate the agent installer](vmware-physical-mobility-service-overview.md#locate-installer-files) based on the operating system of the server.
+
+>[!IMPORTANT]
+> If you are replicating Azure IaaS VM from one Azure region to another, don't use this method. Refer to [our guidance](azure-to-azure-autoupdate.md) for information on all available options.
+
+3. Copy the installation file on to the protected machine, and run it to update the mobility agent.
+
 ## Update account used for push installation of Mobility service
 
 When you deployed Site Recovery, to enable push installation of the Mobility service, you specified an account that the Site Recovery process server uses to access the machines and install the service when replication is enabled for the machine. If you want to update the credentials for this account, follow [these instructions](vmware-azure-manage-configuration-server.md#modify-credentials-for-mobility-service-installation).