<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5 in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417652#M44531</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;B&gt;mlarrivee80&lt;/B&gt; ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P data-aura-rendered-by="48:65;a" style="margin-bottom: 20px;"&gt;Are you running Update Manager on a different machine then vCenter?&lt;/P&gt;&lt;P data-aura-rendered-by="48:65;a" style="margin-bottom: 20px;"&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jul 2018 19:59:30 GMT</pubDate>
    <dc:creator>RickVerstegen</dc:creator>
    <dc:date>2018-07-11T19:59:30Z</dc:date>
    <item>
      <title>Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417651#M44530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the error I get while running the migration assistant on my Windows 5.5 vCenter server.&amp;nbsp; VMware update manager is working correctly so my guess is that the database is available and working.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error messages: Error: Unable to connect to VMware Update Manager Database, Cannot proceed with migration&lt;/P&gt;&lt;P&gt;Resolution: Please check that VMware Update Manager Database is reachable before migration and Please make sure Migration Assistant is launched under service account for VMware Update Manager&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My guess is that my current account does not have enough permissions to access the database.&amp;nbsp; I'm currently running the migration assistant with my admin account which is a domain admin account with administrator rights locally on the machine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2018 14:52:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417651#M44530</guid>
      <dc:creator>mlarrivee80</dc:creator>
      <dc:date>2018-07-11T14:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417652#M44531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;B&gt;mlarrivee80&lt;/B&gt; ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P data-aura-rendered-by="48:65;a" style="margin-bottom: 20px;"&gt;Are you running Update Manager on a different machine then vCenter?&lt;/P&gt;&lt;P data-aura-rendered-by="48:65;a" style="margin-bottom: 20px;"&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2018 19:59:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417652#M44531</guid>
      <dc:creator>RickVerstegen</dc:creator>
      <dc:date>2018-07-11T19:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417653#M44532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have also faced the same issue when I was performing the migration from vCenter 5.5 to VCSA 6.5. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since in VCSA 6.5, Update manager is bundled with vCenter, You can can disable Update Manager from MOB page &amp;amp; proceed for migration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can follow below troubleshooting steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Take a snapshot of Vcenter machine&lt;/P&gt;&lt;P&gt;2) Stop Update manager service &amp;amp; disable the UM plugin&lt;/P&gt;&lt;P&gt;3) Remove the UM extension from vCenter MOB page by following below VMware KB article&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/1025360" title="https://kb.vmware.com/s/article/1025360"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) Extension for UM : &lt;SPAN style="color: rgba(77, 76, 76, 0.9); font-family: 'Courier New'; font-size: 12px;"&gt;com.vmware.vcIntegrity&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: rgba(77, 76, 76, 0.9); font-family: 'Courier New'; font-size: 12px;"&gt;Hope this helps!!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: rgba(77, 76, 76, 0.9); font-family: 'Courier New'; font-size: 12px;"&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2018 10:42:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417653#M44532</guid>
      <dc:creator>REC007</dc:creator>
      <dc:date>2018-07-12T10:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417654#M44533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the problem.&amp;nbsp; It was indeed a permission issue.&amp;nbsp; I had to run the migration assistant on the Winows vCenter server with another domain account.&amp;nbsp; From there I was able to access the VUm database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So basically, make sure that your account has enough permissions to access the database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2018 12:17:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417654#M44533</guid>
      <dc:creator>mlarrivee80</dc:creator>
      <dc:date>2018-07-12T12:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Migration-Assitant error during prechecks from Windows 5.5 to VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417655#M44534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you cannot access the DB, make sure that the user has SA permissions and that Replace process level permission is set as following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;gpedit.msc - Computer Configuration - Security Settings - Local Policy - User Rights assignment&lt;/P&gt;&lt;P&gt;Click on "Replace a process level token" and assign it to the user running the Migration assistant and/or the service user which you are using for vCenter DB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I had an error about something with Update Manager. Closed the Migration Assistant, opened it again and WORKED. (w/o changes, w/o reboot, w/o logging off and on).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Apr 2020 09:36:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Migration-Assitant-error-during-prechecks-from-Windows-5-5-to/m-p/1417655#M44534</guid>
      <dc:creator>justyjusty123</dc:creator>
      <dc:date>2020-04-23T09:36:34Z</dc:date>
    </item>
  </channel>
</rss>

