It seems like you have an X-Large appliance deployed.
Storage Requirements for the vCenter Server Appliance
(if you want to confirm it should have 24 vCPU and 56GB RAM Hardware Requirements for the vCenter Server Appliance )
That's correct according to what VMware can provide, now, I'm not sure if that design is correct for your environment, but that should be checked with the team or people who implemented
Warm regards
Same issue here.... no scp support
The 7.0 documentation doesn’t mention SCP, it matches the screenshot: File-Based Backup and Restore of vCenter Server
The same documentation for 6.5 does include SCP.
Is it possible to install a wildcard SSL Certificate issued by GoDaddy for the vCenter Server, to make the communication secure.
If possible how to do it.
Thank you
Moderator: Thread moved to the vCenter Server area.
Unfortunately I have found that my collegue has used the X-Large Storage Size with Thick disks, but the VCenter is configured for small enviroment (5 host).
What's the best way to change this configuration? Migration, switching to Thin (using storage vmotion) or something else?
Thanks
Manuel
Hello
My VAMI Update Manager lists 7.0.1.00000 as an available update.
Can the complete upgrade process be done though Update Manager now?
I have only tried upgrading vCenter by downloading the GUI-installer and running this through my client PC.
Thank you.
I've seen many ways to increase resources on a VCSA but not to take resources for VCSA, you might try to do it, but I'm to100% sure if it's going to work. (also, if you are using vSAN there is no thick or thin, just storage policies and objects)
In my humble opinion: what you might do is this:
1. take a file based backup of you VCSA
File-Based Backup and Restore of vCenter Server Appliance
2. deploy a new instance of VCSA in the SAME VERSION, this time please set it to small.
3. Restore backup files on the new VCSA (prior to the restore, please shut down original VCSA having taken note of which host is the VM running in case you need to power it back on.)
I know that in VSAN there are only storage policy, but actually the VCenter was configured as Thick, and as you see the 2 disks of 1.4TB are filles less than 1%, but on vsanDatastore the 2 disks are of 1.4TB.
The default storage policy is with 0% space reservation, so thin, but this configuration on VCenter seems to win VS storage policy.
Also, usually when I use VCenter Converter to convert VM that are not VSAN native, on Thick disks I have a VSAN Health Warning about the presence of Thick disks with Thin storage policy, but in this case of VCenter I doesn't have this warning.
I will try the Storage Vmotion to convert to Thin the VDisks and will update the conversation.
Apart of storage size, there are something different configured when you choose X-Large deployment? Like log retention or something else?
Hi, no luck as yet and would be interested if anyone has managed to achieve LDAPs.
I set a new v6.7 test environment i.e. new AD/DNS, vcenter Server and ESXi. All on a flat network with no firewall or NAT. I have no issue with the LDAP configuration but when i attempt to change to LDAPs have the 'network connection' message.
Hi, no luck as yet and would be interested if anyone has managed to achieve LDAPs.
I set a new v6.7 test environment i.e. new AD/DNS, vcenter Server and ESXi. All on a flat network with no firewall or NAT. I have no issue with the LDAP configuration but when i attempt to change to LDAPs have the 'network connection' message.
I suspect the issue is with the certificate itself. I've tried two methods via export and openSSL and then to add to LDAPs. I'm not not a certificate SME, but installed Certificate Services on the DC which according to documentation auto configures for LDAPs. This is the only grey area, and clarity or documentation on configuring the DC for Certificate Services and then exporting a certifcate for vCenter server lDAPs will help.
For now i've parked this issue, and am considering upgrading to vSphere 7 next month and review again, however, any progress will help.
My VAMI Update Manager lists 7.0.1.00000 as an available update.
Unless someone knows better, I'd consider this a bug.
According to the documentation, upgrading is done using e.g. the GUI wizard. Other users mentioned, that after updating to 6.7.0.45100 the 7.0.1 option is gone.
André
Wildcard certs are not supported with vCenter.
As a.p mentioned, this is definitely a bug, the upgrade between major versions is always performed using the GUI wizard.
Thanks! This solved my issue!
Hi DonSkoD,
Seems like some kind of a bug. It seems another user upgraded to 6.7 U3k(45100) and 7.0 U1 was no longer listed --> https://communities.vmware.com/thread/643982
Hope that helps
Hello,
I recently downloaded the trial of VCSA 7U1a. I seem to be having issues with setting up the Server. I have tried the windows install to the ip address and the included OVF with no luck. Below are is the error I am getting with the OVF. I also have the logs from the windows install, But don't know what to look at specifically
Thanks!
Update... The VMFS in question seems to be my NAS. I am using a NFS share for the datastore. Why would this be causing issues? The install seems to be running on an Old HDD that I have just fine.
Please attach the mentioned installer log to see whether it contains helpful details.
André
Can you let me know how you rolled back.
I tried but kept getting error. But no specific error.
Thanks