scouser_steve
Contributor
Contributor

vCenter 8.0 U2

Hi,

 

We are about to install vCenter for the first time, but noted that vCenter 8.0 Update 2 was announced a short time ago and wondered if we should wait for the latest version to be released or install now and upgrade. Reason for holding off would be that 8.0 U2 has "vSphere Identity Federation with Azure AD" and we'd like to utilise this feature rather than using AD authentication via LDAPS.

The official announcement states "Announcing vSphere Q3 2023 Release" - Q3 ends in a couple of weeks, so does anyone have an idea of an exact release date and if it's best to hold for now?

Many thanks,

Steve

Reply
0 Kudos
pmichelli
Hot Shot
Hot Shot

They never tell us when things are going to release.

Upgrade to U1 now, get used to all things v8 and then upgrade to U2 when it ships.  The process takes less than an hour.

Make sure you have backups of your current vCenter from the VCSA and also power it off and take a cold snapshot. Don't take a live one.

Then you have nothing to worry about if something goes amiss. Even if you went straight to U2, you'll still be using AD over LDAPS until you re-configure it to use Azure. So I see no benefit of waiting.

battybishop
Hot Shot
Hot Shot

I'd totally agree, install 8u1 as it's stable and wait till the first couple of patches for 8u2 before going to it

pmichelli
Hot Shot
Hot Shot

Excellent point. You DO NOT want to be a beta tester for VMware. Many of us are still upset over the SD card fiasco with 7.0U2. I killed and replaced over 10 SD cards in a 4 month period until I could replace all my servers with SSD drives.

Install U1 then patch it to the latest U1 iteration. Get used to the install / patching process. 

Let other people figure out the inevitable bugs and shortcomings of U2 and the once U2b or something comes out, upgrade to it.

I have been working with VMware products for over 15 years. I've seen the good, the bad and the ugly. Their releases lately leave a lot to be desired in their initial state.

 

markey165
Hot Shot
Hot Shot

Also agree. if you are installing vCenter for the first time, you'll probably want to do at least one round of build it up and tear it down, whilst you get everything how you want it and document your build process. 

I would crack on and start doing that with the vCenter that is available now. If U2 comes out in the meantime, do your final build with that version and implement AAD as an identity provider then. Everything else will pretty much be the same.

 

Even changing from one identity provider to another isn't that big a deal. I'm sure U2 will work just fine, but only you can decide whether to go with U2 off the bat, or wait a while until any potential issues that might or might not arise, are ironed out. 

 

HTH

 

_____________________________________________
If this post helps you, please leave Kudo | or mark this reply as an answer
scouser_steve
Contributor
Contributor

Thanks for all the replies, it totally makes sense to build it 'now' and change the auth method later once U2 is available (or at least a later iteration of U2), completely understand the reasons not to go for an initial build version, but assumed more to do with initial v8.0 rather than v8.0 update 'x'.

 

Thanks again,

 

Steve

Reply
0 Kudos
markey165
Hot Shot
Hot Shot

If nothing else @scouser_steve its good practise!

 

Especially if you're deploying vCenter or vSphere for the first time. You'll need a few practice runs get the build and configuration right :ok_hand::smiling_face_with_smiling_eyes:

_____________________________________________
If this post helps you, please leave Kudo | or mark this reply as an answer
Reply
0 Kudos
maksym007
Expert
Expert

We have separate test environment where we can test it and after grace period to decide implement it on prod or not

Reply
0 Kudos