Great video Emad. Thank you. How would you have approached the migration had the original 5.5 sites been running in Link-mode? you scenario treats them as standalone deployment sites which then become part of the same SSO domain during the migration and thereby taking advantage of the Enhanced Link mode feature
Not if you are planning to do what this video is describing - migrating from v5.x (w/ SSO) to v6.x (PSC). While not explicitly stated here, in most cases where there is a Windows-based v5.x vCenter Server and VUM, the backing database is SQL Server. The v6.x vCenter Server appliances to do support SQL Server as a backend database.
I love the white board format, its the best way to try and explain the complicated upgrade like you explained.
Great information, and the overall process, might have to lab this up myself to see what it looks like in production.
Great Video but I think this is quite a specific environment and like the other comments made it quite a complex upgrade to follow.
Very Informative Video.
Great video Emad. Thank you. How would you have approached the migration had the original 5.5 sites been running in Link-mode? you scenario treats them as standalone deployment sites which then become part of the same SSO domain during the migration and thereby taking advantage of the Enhanced Link mode feature
Great explanation
Awesome Video!
Useful information!
It looks complicated but the explanation helps.
Great update.
Good video!
Excellent
very helpful
Good design consideration for SDDC
nice update
gr8 Video
Seems very complicated. Can't we just install the new VC and connect it to the old DB?
Not if you are planning to do what this video is describing - migrating from v5.x (w/ SSO) to v6.x (PSC). While not explicitly stated here, in most cases where there is a Windows-based v5.x vCenter Server and VUM, the backing database is SQL Server. The v6.x vCenter Server appliances to do support SQL Server as a backend database.
useful video
good update
#WhiteBoard4TheWin
Triple-Point-Tuesday at cloudcredibility.com. Thanks!