This is necessary to prevent name collisions. This will prevent the clone from seeing the deployment it came out of. Please note that the Cloned VM will be stored in the same Resource Group as the deployment it was taken from but will be in a separate Virtual Network. Monitor the Notifications bell at the top of the page for Completion. The Deployment name should be in the form Clone-DeploymentName-SessionHostName-TimeStamp-RG with a product type of Clone Server.Once the cloning process has started, you can select the Deployments tab and then Refresh to show the Deployment in the deployment list.It will be listed as a “Create/Update Deployment” process. Once the Clone process starts you will be able to track progress of the cloning in the Notifications section. The cloning process should take less than 10 minutes. Pick the Server you wish to clone and Select the Actions dropdown > Select Clone > and then Confirm.On the Deployment Details page select the appropriate Collection (Desktop Collection/RemoteApp) that contains the session host image you want to clone. If you do not create a local user account, you will be unable to log into the cloned VM to update and sysprep it. Remember, you must add a local machine admin account, not a domain admin account before cloning your session host. Clone an existing Session Host Virtual Machine
0 Comments
Leave a Reply. |