<?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: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins in vSphere Upgrade &amp; Install Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630043#M30425</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mike.... this is the craziest thing.&lt;/P&gt;&lt;P&gt;My fix was to run queries on the vCenter database.&lt;/P&gt;&lt;P&gt;After VMWare plowed through my logs a few times, they found some issues that were in a KB artilcle &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2007231&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After running the queries and rebooting both SQL and vCenter server, all was well &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Feb 2012 18:12:31 GMT</pubDate>
    <dc:creator>spf62</dc:creator>
    <dc:date>2012-02-14T18:12:31Z</dc:date>
    <item>
      <title>Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630034#M30416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So I am about ready to start upgrading my 4.1 U1 datacenter to v5. And I have a couple last questions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My DB is SQL 2008, but it's not local; we have a DB server that hosts a number of DBs for various applications. The 2 days "What's new in v5" class I took used local DBs. Having it non-local should not be an issue, I don't think. It should Just Work, right? (presuming I tell it to upgrade the database, as I should)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My vCenter currently runs as a LOCALSYSTEM account; should I change it to use a domain account? (we run Win 2008 AD) If so, are there special access rights I should grant to it (such as Local Administrator)? I have an account I use, that is a member of the AD group "ESX Admins", to run PowerCLI scripts with, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, the v4 vSphere client should connect to the newly upgraded vCenter? It's installed on a number of our employee's machines; will they still be able to connect, or will they need to upgrade their client before accessing the new v5 vCenter?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, we have one 3rd party vCenter plugin, from Emulex, for upgrading the firmware on the FC cards. Do I need to uninstall this before upgrading, or will the upgrade process just automatically disable any 3rd party plugins it finds? (I realize I will have to go get the v5 plugin and install it, after the upgrade is done)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK, so that was a bit more than a "couple". &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; Just want to be thorough ...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2012 19:50:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630034#M30416</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-02-03T19:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630035#M30417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I do not know if you have reviewed the upgtrade - it should answer most of your questions &lt;A href="http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf"&gt;http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Feb 2012 20:16:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630035#M30417</guid>
      <dc:creator>weinstein5</dc:creator>
      <dc:date>2012-02-03T20:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630036#M30418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Check out here, you might be benefit of what I did.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://communities.vmware.com/thread/345105"&gt;http://communities.vmware.com/thread/345105?tstart=0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrading vCenter 4.1 to vCenter 5.0 what about SQL Express 2005&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Feb 2012 10:08:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630036#M30418</guid>
      <dc:creator>habibalby</dc:creator>
      <dc:date>2012-02-04T10:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630037#M30419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, but I don't use SQL Express; it's SQL 2008 R2 Enterprise (64bit), so it's definitely a supported SQL version for upgrading. And it's not a database in-place upgrade, as the database is not on the vCenter server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did what you did (upgrade from in-place SQL 2005 Express to remote SQL 2008 Enterprise) last year.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Feb 2012 15:54:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630037#M30419</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-02-06T15:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630038#M30420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can you please install sql Express componnent , because I have seen some times it create problem once installed component or after activating service problem solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;_______________________________&lt;BR /&gt;Affirmation without discipline is the beginning of delusion.&lt;BR /&gt;&lt;IMG alt="http://imagicon.info/cat/5-59/vbsmile.png" class="jive-image" src="http://imagicon.info/cat/5-59/vbsmile.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Feb 2012 20:38:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630038#M30420</guid>
      <dc:creator>adelisa</dc:creator>
      <dc:date>2012-02-06T20:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630039#M30421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"can you please install sql Express componnent , because I have seen some times it create problem once installed component or after activating service problem solved."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry, no, I can not. We don't use local SQL installations except for specific large database needs. So we will be using our current database, which is hosted on another server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Feb 2012 13:16:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630039#M30421</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-02-07T13:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630040#M30422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Michael,&lt;/P&gt;&lt;P&gt;We have the exact same setup as you: seperate SQL 2008 server, vCenter 4.1, both vm's.&lt;/P&gt;&lt;P&gt;I tried upgrading in place and it failed. My Virtual center service wont start.&lt;/P&gt;&lt;P&gt;I hasd to revert back to my snaps and start over.&lt;/P&gt;&lt;P&gt;So far I haven't had any luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also tried uninstalling vCenter completely from my VC Server (which is also 2008 r2). Installing vCenter 5 from scratch. Still fails although it says Finished.&lt;/P&gt;&lt;P&gt;Again my VC service doesnt start.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you had any luck with your upgrade? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2012 13:45:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630040#M30422</guid>
      <dc:creator>spf62</dc:creator>
      <dc:date>2012-02-09T13:45:47Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630041#M30423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I haven't done my upgrade yet; I have an important production database server to virtualize this weekend, so I won't be trying to upgrade until next week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used to have my vCenter as a VM, but we had weird problems, so I&amp;nbsp; migrated it to a physical machine, and the problems went away. Don't know if they were related, or if I had just screwed up my original install as a VM, but now my vCenter is a physical box. And the SQL 2008 server is also a physical box (as it also hosts other databases for other apps).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for the 3rd party plugin (Emulex OneCommand), I uninstalled it, on advice of Emulex Tech Support (who are very helpful, BTW, even on support via email). So now I have a "clean" installation, to try upgrading. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will report back, when I have more results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you called VMware about your problems?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2012 14:27:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630041#M30423</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-02-09T14:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630042#M30424</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just did my update this morning. Went exactly as the seminar showed, and the documents list. Personally, I was shocked. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; I stopped the vCenter services, than ran the upgrade, and it all Just Worked. Then I updated the vSphere client, then updated the Update Manager. All this was on the vCenter server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then I updated the vSphere client, and Update client, on my workstation, and it all Just Worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Downtime was under 30 minutes, probably under 20 ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Had a little bit of trouble, as the update manager was giving an error that it could not download patch definitions, but that turned out to be a problem with Internet access on the vCenter server; once I resolved that, the check for new patches Just Worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it looks like I am good to go. I will give it a week or so, to continue running with my ESX 4.1 U1 servers, before I start planning the final steps, about upgrading to ESXi v5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then I get to do the fun parts about migrating to new SAN storage, formatted as VMFS v5, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good times ahead!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest running that pre-upgrade host checker. Luckily, mine ran clean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And keep Support's phone number handy, just in case. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2012 16:56:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630042#M30424</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-02-14T16:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630043#M30425</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mike.... this is the craziest thing.&lt;/P&gt;&lt;P&gt;My fix was to run queries on the vCenter database.&lt;/P&gt;&lt;P&gt;After VMWare plowed through my logs a few times, they found some issues that were in a KB artilcle &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;2007231&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After running the queries and rebooting both SQL and vCenter server, all was well &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2012 18:12:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630043#M30425</guid>
      <dc:creator>spf62</dc:creator>
      <dc:date>2012-02-14T18:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630044#M30426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;A _jive_internal="true" class="jiveTT-hover-user jive-username-link active_link" href="https://communities.vmware.com/people/MichaelLeone" id="jive-32468327,183,257,233,304,523"&gt;MichaelLeone&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;were you using vDS? I want to upgrade my vCenter to 5.0 that has vDS but I am not sure it&amp;nbsp; the vDS during the upgrade won't work and communication for VMs will be down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any idea thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2012 15:17:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630044#M30426</guid>
      <dc:creator>escapem2</dc:creator>
      <dc:date>2012-03-15T15:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading vCenter 4.1 to 5 that uses remote SQL DB and 3rd party plugins</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630045#M30427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, I am not using any distributed switches. I wish I was, it can make adding a new host a lot easier. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2012 19:12:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-vCenter-4-1-to-5-that-uses-remote-SQL-DB-and-3rd-party/m-p/2630045#M30427</guid>
      <dc:creator>MichaelLeone</dc:creator>
      <dc:date>2012-03-15T19:12:19Z</dc:date>
    </item>
  </channel>
</rss>

