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.

I have to create an 894 output file. Normally we do this from our system as flat files, then map them. It's pretty easy. But in this case, the person who is supplying the data file, literally has the entire thing mapped into a valid 894 5010 UCS file (with proper ISA and GS fields).

Is there a way to load this into GENTRAN:Director? I tried a straight map from 894 to 894, hoping it would pick up the ISA ID and match it, but that didn't work. Then I tried the "process file..." option from the command menu, but that loaded the file in the "?in" drawer not ID'ing the partner it was supposed to be paired to (and more importantly, it's in the ?in not ?out error drawer).

I double checked and made sure I didn't have the ISA06 and ISA08 reversed or something, but ours is in 06 and the partners is in 08.

I'm about to just ask them to export a flat file I can map instead, but I feel thats going backwards, and this SHOULD be easy.

EDIT: Also, I just tried creating an export map for the 894 and mapped it to an inbound type document, flipped the IDs and my map worked fine, giving me a proper inbound document. grrrr.

EDIT 2: Well, I kind of got it working, but I can't believe that this is how its supposed to be done, so if anyone has a better way please let me know. What I did was I used the inbound document version with swapped IDs, changed the map to a turnaround type from an export type, then it generated an 894 in the workspace that was properly formatted for sending.

EDIT 3: Anyone know if theres a way to change the document name via an extended rule instead of standard? if so, whats the proper way to reference it?