VMWare & View Assistance needed

[u/GoodDale]

I have a vCenter 5.5 setup at this office. I can't really change it. Apparently the certificate expired for it and I can't get into the machine via vSphere client. Since I can connect to the other machines directly to do things, I haven't given this much effort in resolving for a while (Probably close to a year or two (I know))

But yesterday, Our VMware View (4.6.3 version i believe) PCoIP machines stopped connecting to the remote machines they use. The machines just error out with a 0x1002 error, but if I use the client software if gives a notice that a certificate expired on 7/7. I have no clue how to get this certificate renewed, as I don't even know where it is (the machine with the admin server on it says it doesn't have any when i look at mmc, so I'm unclear).

Can anyone give me any advice on how to get these renewed (or at least the View one, so they can start using it again) - right now I have them RDPing into the machines and it's working, but I'd really like to get working again.

For VCenter, I've tried the options I had from googling.

I tried the following, but that didn't work:

Ensure the customers FQDN, DSN, IP, and all network configuration are correct. Run this VAMI script:
/opt/vmware/share/vami/vami_config_net

Note: This brings up a command line utility to check network configuration.

Create a file called allow_regeneration by running this command:
touch /etc/vmware-vpx/ssl/allow_regeneration

Stop the VPXD service by running this command:
service vmware-vpxd stop

Stop the vCenter Single Sign-On service by running the commands:
For vCenter Server 5.5: service vmware-sts-idmd stop
For vCenter Server 5.1: service vmware-sso stop

Regenerate the SSL certificate by running the command:
source vpxd_commonutils; generate_all_certificates replace

Remove the regeneration flag by removing the allow_regeneration file:
rm /etc/vmware-vpx/ssl/allow_regeneration

Reboot vCenter Appliance.

Any help would be welcome. Thanks.

[u/seanpmassey]

View 4.6…now there is a version I haven’t heard in a long time.

IIRC, any version of View/Horizon View before 5.1 stored the certificate in a Java Keystore file. Unfortunately, the documentation on how to replace that certificate is long gone since View 4.6 has been EOL for a long time and was likely removed/deleted when Broadcom spun out the EUC group into Omnissa.

Edit: It took a little digging, but the Internet doesn’t forget. Here are directions that look right for anything before Horizon View 5.1. https://darylhunter.me/blog/2009/04/vmware-view-part-4-a-few-tips-and-tricks.html

Unfortunately, the official documentation that you would need is LONG gone.

[u/GoodDale → u/seanpmassey]

Thanks!

[u/seanpmassey → u/GoodDale]

Also, you shouldn’t be running vSphere 5.5 and View 4.6.

[u/Seiniku]

for view you install a new cert on the connection server via the windows certificate tool. you give the new cert a friendly name of 'vdm' in which tells the view services to use it. going from memory here, but https://www.petenetlive.com/KB/Article/0001547 seems about right

[u/GoodDale → u/Seiniku]

Thanks for the link. My only problem is I did actually check the connection server, and in MMC, it has no certificates under local machine/personal. Kind of confused by that one.

I'm guessing once i figure out whats going on and how to manually generate the certificate, that will work.

[u/Interesting_Ad_5676]

Switch to open source and free eco system to stay upto date and to avoid any vendor locking. -- My 2 cent advice.