Skeetneet Tracker

Re: ELX_bootbank_elx-esx-libelxima.so conflict between patch baseline and HP custom ISO.

Skeetneet — Fri, 02 Aug 2019 11:23:26 GMT

I ran into the same issue with some Synergy SY480 Compute nodes. Followed this guide:

https://www.servertrouble.com/the-host-returns-esxupdate-error-codes-1-check-the-update-manager-log-files-and-esxupdate-…

Command –

esxcli software vib list | grep ELX

Command Result –
elx-esx-libelxima.so 12.0.1108.0-03 ELX VMwareCertified 2018-08-23

Now to remove the VIB, use the command mentioned below.
Command –
esxcli software vib remove -n elx-esx-libelxima.so

For me this works. After the reboot I was able to scan the hosts and update them with UM.

root password

Skeetneet — Sun, 14 Oct 2018 09:27:26 GMT

Author : CHuser

URL : http:////docs.vmware.com/en/VMware-Identity-Manager/3.3/vidm_windows_install/GUID-001B4B5D-18DB-4B7B-AD56-4E988FCD52CC.html

Topic Name : Resetting Admin User Password for VMware Identity Manager for Windows

Publication Name : Installing and Configuring VMware Identity Manager for Windows

Product/Version : VMware Identity Manager/3.3

Question :

reset root password

Re: Getting Error "this horizon server expects to get your logon creds from another app server

Skeetneet — Tue, 07 Nov 2017 11:44:40 GMT

Yep, I think these are two separate issues. For the issue you're describing we've also logged a support request which is open for over 2 months now. We've installed a special debug-version of the Connection Server and sent the logs to Engineering. They are now investigating. When I've got an update I will let you know.

Re: Getting Error "this horizon server expects to get your logon creds from another app server

Skeetneet — Mon, 06 Nov 2017 16:09:28 GMT

Hi,

We've had this error too coming back after a certain period. After rebooting the vIDM appliances it seems to be fine again. We made a support request for this issue and VMware answered us with the following:

From log analysis we can see that this issue is related to metadata expiry
As an example say View Sync runs at 10am , this updates the View metadata in the vIDM service.

For the latest certificate lets say the metadata would expire before 10:00am say 9:30am so therefore this issue would be seen for 30 mins or until the next view sync would run and update the metadata in the vIDM service.

To resolve:

By default SAML metadata expires daily, you can increase the expiration time by 90 days.

1) Remove entries for pae-NameValuePair attribute on connection server and press okay.
cs-samlencryptionkeyvaliditydays=90
cs-samlsigningkeyvaliditydays=90

Change the Expiration Period for Service Provider Metadata http://pubs.vmware.com/horizon-71-view/topic/com.vmware.horizon-view.administration.doc/GUID-3E170C23-097F-46D0-82BD-7CACFF04FC9A.html

2) Re-add entries for pae-NameValuePair attribute on connection server and press okay.

3) After around 5 mins restart all of the connection servers in the environment.

4) When connection servers are back up and running do a manual sync of View from IDM

The changes will take effect from the next day. Meaning the new certificate generated next day will have the expiration as 90 days.

In 90 days time this process will automatically repeat itself.

Please let us know if the above resolves the "server expects to get your logon credentials from another application or server..........." issue.

Hope this helps.

Re: VMWare v6.0 to 6U1 or 6U2 Upgrade - External PSC - 1603 Errors on vCenter Server

Skeetneet — Tue, 27 Dec 2016 11:37:32 GMT

I've been struggling with this issue for two weeks when upgrading to U2A build 4541947, and finally support came through with a solution.

In our case, the cause was vCenter JRE not being updated correctly.

To workaround the issue, remove the contents of the jre and then perform the upgrade.

Steps:

Stop all vCenter services.
Take a backup of jre folder located at C:\Program Files\VMware\vCenter Server\
Empty the contents of jre folder except for the below files :

C:\Program Files\VMware\vCenter Server\jre\bin\libvecsjni.dll

C:\Program Files\VMware\\vCenter Server\jre\lib\ext\vmware-endpoint-certificate-store.jar

Perform an upgrade to vCenter Server Update 2a.

Re: vCenter 6.0 to 6u2 fails with error 1603

Skeetneet — Tue, 27 Dec 2016 11:36:33 GMT

I've been struggling with this issue for two weeks when upgrading to U2A build 4541947, and finally support came through with a solution.

In our case, the cause was vCenter JRE not being updated correctly.

To workaround the issue, remove the contents of the jre and then perform the upgrade.

Steps:

Stop all vCenter services.
Take a backup of jre folder located at C:\Program Files\VMware\vCenter Server\
Empty the contents of jre folder except for the below files :

C:\Program Files\VMware\vCenter Server\jre\bin\libvecsjni.dll

C:\Program Files\VMware\\vCenter Server\jre\lib\ext\vmware-endpoint-certificate-store.jar

Perform an upgrade to vCenter Server Update 2a.

Re: Using PowerShell to Deploy VMware Unified Access Gateway

Skeetneet — Mon, 10 Oct 2016 08:09:55 GMT

I've shuffled the [Horizon] and [WebReverseProxy] again and retried redeploying several times, but unfortunately still no bananas. I was wondering: are there any other users who are experiencing this same symptom? Mark, if it might be a misconfiguration, what could it be?

Re: Using PowerShell to Deploy VMware Unified Access Gateway

Skeetneet — Thu, 06 Oct 2016 13:12:33 GMT

Hi Mark,

Thank you for the awesome script, really takes away a lot of configuration work. I do have one question however: the configuration settings that I specify within the [Horizon] part and the [WebReverseProxy] part don't seem to get populated in the VM once it has been deployed. I've played around and put those two variables at different places in the .ini-file, but still the deployment won't set these values when the AP is being deployed. Do you have any idea what could be causing this?

Thanks.

Change displayname of vCenter 6.0 to something else than hostname?

Skeetneet — Wed, 30 Sep 2015 17:24:38 GMT

Hello fellow community members,

I've upgraded my test environment recently to a embedded Windows vCenter 6.0 setup. In our old 5.5 setup, the vCenter 'logical' name, was different from the hostname and this worked without any problem (also in Linked Mode). The vCenter server would be reachable through 'vcenter.myorganization.com', while the hostname of the server was 'vcenter1.myorganization.com', no problems at all. You could change this simply by renaming the vCenter in the hierarchy of the Hosts and Clusters or the VM's and Templates view.

In the new version however, it simply seems not possible to change the vCenter name to anything else than the hostname of de Windows system it resides on.

You can change it in the C# client via Administration --> vCenter Server Settings --> Runtime Settings.

This is also done via the Webclient in the vCenter Inventory list --> Settings --> Runtime Settings --> vCenter Server Name.

But.. every time you reboot the VM/server, this value is changed back to the hostname of the server.

So, I made a supportcall at VMware and spoke to a representative from India who had some trouble understanding my question, but eventually got it and gave me the following answer:

** Please do not change the subject line of this email if you wish to respond. **

Greetings!

Thank you for your time on the case.It was pleasant to assist you on this support request.I hope you were delighted with the service we provided to you.
Here is a brief summay of the query we discussed,for your reference:

Query:

Query regarding the change of FQDN while installing vCenter Server to name other than underlying system name.

Analysis:

As discussed, we should not change the FQDN to any other name.By design,it is recommended to be same as the underlying guest OS system name.
You would have to install the vCenter Server again in order to resolve the issue.

Recommendation:

You could change the underlying Guest OS system name and then have it as the FQDN.

Having said the above,as confirmed, I will proceed to move the support request to archived status.Please do not hesitate to contact us if you have any queries/concerns.

But still I'm wondering if other people have ran into this issue with vSphere 6.0 as well and maybe found a solution/workaround for it.

vSphere Web Client crashes on Chrome & IE, works fine in Firefox

Skeetneet — Fri, 07 Mar 2014 16:08:17 GMT

Hi fellow Vmware-guys,

I have been wrestling with this issue for over 2 days now and I'm totally out of options. I hope someone here could help me out.

When I try the vSphere Web Client interface of our second (linked-mode) vCenter-server in Chrome, it crashes. When I open it in IE9, I get an error page. When I open it in Firefox 27.0.1, all works fine.

We are currently running vCenter 5.5.0a on both the main and linked server. The c# client also has no problems when trying to log in to either vCenter server.

The access-log of the Web Client under C:\ProgramData\VMware\vSphere Web Client\serviceability\logs\access shows a normal 200 entry:

10.67.8.199 - - [07/Mar/2014:16:31:07 +0100] "GET /vsphere-client/admin-ui/AdminModule.swf HTTP/1.1" 200 77531

10.67.8.199 - - [07/Mar/2014:16:31:08 +0100] "POST /vsphere-client/endpoints/messagebroker/amfsecure HTTP/1.1" 200 1238

10.67.8.199 - - [07/Mar/2014:16:31:16 +0100] "POST /vsphere-client/endpoints/messagebroker/amfsecure HTTP/1.1" 200 2034

10.67.8.199 - - [07/Mar/2014:16:31:16 +0100] "POST /vsphere-client/endpoints/messagebroker/amfsecure HTTP/1.1" 200 1022

10.67.8.199 - - [07/Mar/2014:16:31:16 +0100] "POST /vsphere-client/endpoints/messagebroker/amfsecure HTTP/1.1" 200 1163

I do have a crash dump for Chrome, but my gut feeling tells me it might be something with the certificates used on the second server. However, they are all still valid.

Has anyone ever experienced this issue before?