Yes, I did. That does resync the entire profile (image). But VMware has left a gap in the Auto Deploy design, since there is no clear or clean way to purge stale items from the cache. Talking with VMware, this was acknowledged as a gap... a pretty significant one.
Re: Remove build image, i.e. stale VIBs, no longer referenced, in Auto Deploy cache?
vCenter Db Migration Plan
I must migrate the vCenter databases to a different datacenter. The databases reside on a separate VM from the vCenter server. Going from SQL 2005 Std SQL 2014 Std, on a 5.1 U3b vCenter. I'm attempting to follow http://kb.vmware.com/kb/7960893. Here is my migration plan. I'm referring to the KB articles for the individual steps:
Stop VMware services on the vCenter server.
Backup existing SQL Dbs on the old SQL server with SQL Management Studio http://kb.vmware.com/kb/2045528.
Using SQL Management Studio on the new SQL server, restore the databases.http://kb.vmware.com/kb/2012138
Update the vCenter server SSO settings to reflect change of the host name of the database server http://kb.vmware.com/kb/2033516.
Update the vCenter server System DSN to the new database server location http://kb.vmware.com/kb/1003928
- What sort of ODBC driver considerations are there going to be from 2005 Std to 2014 Std from the vCenter server. I installed the MS ODBC Driver 11 which supports SQL 2014 on the vCenter server. Download Microsoft® ODBC Driver 11 for SQL Server® - Windows from Official Microsoft Download Center Should that be sufficient?
Restart vCenter services and log into vSphere client.
Verify jobs and stored procedures on the SQL server http://kb.vmware.com/kb/2033096
Verify Update Manager functionality http://kb.vmware.com/kb/1015223.
Another item that may be of no consequence is that the Update Manager, vCenter, and Inventory Services db all fall under the same database name, so they are not broken out. The tables for each of the three databases are all present in the one database. I only have the RSA and one other Db present to backup and restore.
Thanks
ESXi 5.5 build 2718055 ISO Image
Hi All,
Does any one has got ESXi 5.5 build 2718055 ISO Image, we are looking for the same.
Looking forward to hearing from you.
Regards,
Ajay
Re: ESXi 5.5 build 2718055 ISO Image
create an account on myvmware if you don't have one, download a build older Thant the one you're looking for then patch it.
vCenter installation fails at invsvc service
Hi everyone,
I don't if here is the proper place for this question, but I need some help with this, I'm trying to install VMware vCenter Server 6.0, but it fails with the message that i couldn't start the Inventory Service, I'd checked everything, the DB, the ODBC, but it still displays this message, I don't know how to workaround this, please Can you help me with this?
Thank you in advance!
Re: Building the ultimate vSphere home laboratory
I have looked at your website before, you mentioned that you were taking a break, are you bringing the site back? I do admit the step by step home lab was highly detailed and organized, now that I'm taking vm classes... iItwill be great
Migrate hosts from 5.1 to 6.0
I have 3 hosts that I am replacing. I have the Essentials licensing. Will be moving from 5.1 to 6.0. What are my options for moving the guests to the new hosts?
Re: Migrate hosts from 5.1 to 6.0
hi,
- Upgrade vcenter to 6
- shutdown the vms of one host
- rdmove the vms from inventory
- remove the host from vcenter
- connect the new esxi6 host and select the released license
- configure it if not already done (storage, network, ...)
- register the vms
- power them on
Next host.
Assuming you have shared storage, if not you'll probable need to use VMware converter and it will be much slower.
HOpe this helps.
Cheers.
Re: vCenter installation fails at invsvc service
Hi,
Can you please refer below given KB article may be useful.
Regards,
Ganesh GV
How to properly change a vcenter domain
Hello,
My goal is to update my vcenter configuration so it is using a different active directory domain. My concern is how this will affect both the production VMs as well as how it will affect Veeam backups accessing those VMs. I am running vCenter 5.5.0 with ESXi hosts at version 5.5.0. My primary question is...is there a way to migrate vCenter to a new domain without causing interruption to the production network? My next question would be, is there a way to remap Veeam backups so they don't have to all perform full backups?
Re: SSL-Updater tool Vmware 5.5 error
I had to renew my internal based certificates, as I follow best practice and don't use self sign certs. The Funny part is we've set up so much alerting now here to be proactive vs reactive. So when I got in on Monday after a couple failed backup jobs, I discovered that the account i had setup couldn't login into vCenter, and neither could I. Even though everything showed green on my monitoring board. Turns out all errors were telling me my certificates had expired (Doh! I don't have monitoring for the certs on these!)
Quickly reading my setup documentation, I hit the same snag here, and called support.. turns out I had nested another folder in this one labeled SSLtool5.5. Which turned out to have the same scripts but updated?
Not exactly sure, turns out this one worked fine. I attempted to find a direct link to the latest version of the tool on VMware download page, I finally did find it under the specific vCenter instance, I guess they have a set version of the tool for each specific releases of vCenter, including specific updates.. I got the from the 3e update list of vcenter (direct link)
I'd suggest trying to grab the latest version of the tool if you can. Renewing SSL certificates was the most painful thing ever in vCenter 5.5, 24+ Steps and you hit this wall in step 5 a.
As I mentioned I got lucky and happened to have another version of the tool I placed in a 5.5 folder. Sorry I didn't provide a MD5 hash but I'm not sure how many iterations of this script they have (It is a batch script after-all, Where's the powershell at?)
Re: How to properly change a vcenter domain
If you only change a DNS name of existing vCenter, then, you should just modify its name (the way it's added to a backup console) using this script.
Otherwise (if it's going to be a migration to a new vCenter), you will have to utilize this tool.
Cheers.
Help with VCSA embedded_vCSA_on_VC.json Template
I've been deploying a vCenter 6.02 to and ESXi with no problem but I am running into issue deploying to another vcenter. I am using the embedded_vCSA_on_VC.json and keep getting error failed to find target specified...My problem seems to be with vc.datacenter and vc.target parameter.
Destination vCenter Structure:::
VCenter
-- Test-Datacenter - only 1 datacenter
------- Cluster1 -- Only 1 cluster inside datacenter
------------ESXI01.LAB.COM - one of the ESX inside cluster 1
JSON FILE ::::
"datacenter": ["Datacenters","Test-Datacenter"],
"target": ["Cluster1","ESX01.LAB.COM"]
Error: when running VCSA-DEPLOY.exe
Failed to find target specified "/Datacenters/Test-Datacenter/host/Cluster1/ESX01.LAB.COM"
Note: in the target it insertes "host" between the datacenter and target values... Ive tried everything still cant get past this error. Anyone can help please..
Opened a VMWARE Case last week not getting any response.
Link to document i am using:
maximum video resolution
hi
is there any way to increase vm's video memory more than 128mb to have very high resolutions like 4k*4k or 8k*8k?
Re: vCenter 6 - DB upgrade
Hi
I have a 5.5 database and I want to install 6.0 cleanly on a new VM, will the DB be upgraded as well from 5.5 to 6.0?
I am getting the same error as you in the precheck with "db.clobber:no", using SQL Server 2012 SP2 external DB.
vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014
Hi Everyone,
Could anybody please assist on the below details.
On saturday, we tried migrating vCenter server DB from SQL server 2005full edition to SQL server 2014 full edition and performed following tasks has been performed as per the below link,
- Taken the snapshot of the vCenter VM
- Stopped the VMware vCenter server services/VMware Virtual Management Services/VMware update Manager services
- Taken the backup of the two DBs(vCenter server, VMware update manager) from the existing SQL server 2005
- Restored two DBs successfully on the new SQL server 2014
- Updated the ODBC connection for the vCenter server & VMware update Manager to point on the new SQL server 2014, tested the connection it was successful
- Updated the vcdb properties on the vCenter server VM
- Started the VMware vCenter server services, it failed to start and given the error
Windows could not start the VMware VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.
- For your information, I forget to stop the VMware vCenter server Inventory services, vSphere Profile Driven Storage service before taking the backup of the DBs running on SQL server 2005, would that be the issue preventing vCenter service to start after the restoration?
- Tried the restarting both the VMware vCenter server Inventory services, vSphere Profile Driven Storage service after the restoration but still the same
Much appreciate if anyone kindly assist me on this
Thanks,
Vignesh
Re: vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014
Have you updated the SQL client to the latest version ? And which account you're using in vCenter Server services ? Can you share the vpxd.log ?
Re: vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014
Hi Vignesh, Hope you have already verified the port 1433 is open on new SQL 2014 Database server. Regards, Balakrishna
Re: vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014
Hi Richardson,
Thanks for the reply.
Yes I have updated to SQL Server Native Client 11.0 or is there any other ODBC driver there for SQL server 2014, please advise
We are using local system account in the vCenter server services.
Regarding the vpxd.log, we have reverted to the current snapshot so cannot get the vpxd.log after the migration
Kindly help to advise me on this
Regards,
Vignesh
Re: vCenter server service cannot start after migrating the DB from SQL server 2005 to SQL server 2014
Hi Balakrishna,
Thanks for your reply.
Yes have verified the port 1433 open on the new SQL 2014 DB server and did check the SQL services was started and running.
Is there any other thing that we need to check, pleae advise.
Regards,
Vignesh