<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vsphere 7.0U1c on blogs.hareeshkg.com</title>
    <link>https://blogs.hareeshkg.bid/categories/vsphere-7.0u1c/</link>
    <description>Recent content in Vsphere 7.0U1c on blogs.hareeshkg.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © blogs.hareeshkg.com 2025 reserved</copyright>
    <lastBuildDate>Sun, 20 Dec 2020 12:00:07 +0000</lastBuildDate><atom:link href="https://blogs.hareeshkg.bid/categories/vsphere-7.0u1c/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Advanced Cross-vCenter vMotion</title>
      <link>https://blogs.hareeshkg.bid/post/advanced-cross-vcenter-vmotion/</link>
      <pubDate>Sun, 20 Dec 2020 12:00:07 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/advanced-cross-vcenter-vmotion/</guid>
      <description>
        
          
            &lt;p&gt;VMware had initially launched a fling version called “&lt;a href=&#34;https://flings.vmware.com/cross-vcenter-workload-migration-utility&#34;&gt;Cross vCenter Workload Migration Utility&lt;/a&gt;” which was used by a lot of VMware administrators/customers to migrate workloads/VMs between two vCenters which are managed individually (not under the same SSO domains). This advanced “Cross-vCenter vMotion”, a.k.a. XVM  GUI tool is now natively built into vSphere  7.0U1c which allows bulk transfer of VMs between vCenter instances without the need of any additional fling/plugin installation. XVM does not depend on linked mode, which means that the vcenter servers can be in a separate SSO domains and can be used for migration between vCenter servers on-premise (VC to VC) and in the cloud (VC to VMC on any cloud platforms).&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
