VMware Communities: Message List

Hello all,

vCenter // vSphere 6.7.0.41000

Can you change the password requirements displayed for the vCenter Server Appliance Management interface?

I understand you can specify SSO Password Policy settings in the vSphere client; However the Appliance Management Interface (:5480) appears to have its own password policy settings unaffected by the vSphere Client vCenter SSO settings. You can view these settings by logging in to the Appliance Management portal as root where you'll see an Administration tab on the left.

For example, from shell I can create a new localos account with a 6 character password and log in to Appliance Management with that account, even though my SSO Password Policy settings specify 8 characters.

Thank you for any help offered.

SQL is remote to the vCenter server. I ran netstat on the SQL server and it shows that SQL is listening on port 1433

I checked vpxd.cfg and it is pointed to the correct data source.

<odbc>

<dbtype>external</dbtype>

</odbc>

Respect !

you havent update your environment for the last 7 years ? hope it is not production

You may not see a reason as this isn't mandatory to supply and there are various ways of performing the reboot.

You would have to modify one or more components of the underlying Photon OS which isn't supported and really shouldn't be done. The VAMI should only be used by administrators for upgrade/troubleshooting procedures and so thus doesn't really need to be subjected to a password policy. Normal users should not be in the VAMI.

Yes, its production and critical application running on the VM. The reason they didnt updated due to migration plan to Cloud.

Thanks

vmk

You should look at vPostgres logs. vpxd-svcs service is dependent on vPostgres.

Is PSC internal or external

If it is external then check time between VC and PSC.

32-bit DSN is not necessary for vCenter (it is probably for Update Manager). But both have the same name......can you change name of 32bit DSN? Maybe it will help

And check on 64bit DSN if you have correct DB configured (vCEnter DB instead of master DB)

It does not let you reboot unless you enter a reason!

T_16,

You will find this info logged under Events, not Tasks.

Lars

Alyc Helms,

To update the vCenter License you will need to login to the vSphere web Client. Choose Menu, Administration, Licensing.

From this view you will see the "+Add New Licenses" option.

In this wizard you will add the new license to the repository. After finishing you can og to the Assets tab and use "Assign License" to get the new license into usage.

Good Luck!

Lars

Curious how the community is handling their vCenter version upgrades. Are you typically doing in-place upgrades for minor update revisions and then deploying fresh when you get to a major version release or are you just doing in-place upgrades all the time? For my environment (400 hosts / 7000 virtual machines / 4 vCenter instances) we have been performing in-place upgrades since 5.5 (windows) to where we are today which is 6.5 (vcsa). I am currently in a holding pattern to see when the next major release will come and deciding how that upgrade process will develop out. The only thing that has always worried me about the new deployment is handling all of the distributed virtual switches in the environment since it adds a layer of risk when dealing with it. I am curious to see how others are handling upgrades. Thanks in advance for the comments.

Most customers are on the vCSA where major version upgrades (6.5 => 6.7) are essentially new deployments from an appliance/OS perspective but are effectively migrations from the application's perspective. This is made super simple in the vCSA with automation handling everything for you. Simply put, there are very few reasons why one would want to do a manual re-deploy of a vCSA across major versions.

This is what I would have thought as well, but I have heard from various internal vmware people that they still recommend new fresh deployments on major version upgrades and wanted to see if the community shared that thought.

I have never heard such a recommendation from any VMware employees, even anecdotally, after the vCSA came to market. Not saying there aren't some reasons for this, but it definitely is neither generally recommended nor a widespread practice.

I agree with Vijay, vPostgres logs can give you a clue why it fails to start.

Do you have enough disk space on this Windows machine? if you don't, the vPostgres won't start, and this could cause other "dependent" services to fail to start.

G'Day all,

I'm in the process of doing the upgrade now from VCSA 6.5 to 6.7, after the Stage 2 pre-upgrade checks have run it shows an issue with "External Extensions" such as Dell OpenManage Integration (the server is a Dell R740 with the Dell ESXi6.5U3 A01 release installed fresh) and vRealize Orchestration Manager which appears to hav ebeen installed but never used and is currently off.

My question is, can I ignore this issue and let the upgrade run or do I have to remove some components to guarantee success?

Thanks

Sid

Ignore is right option because in future if there is need VRops plugin then again need to install.

Hi all,

i am facing a strange issue with 4 new Dell R740 Hosts currently running ESXi 6.7.0 Update 3 (Build 15018017). All sensors are no longer available as soon as a Server is added to VCenter 6.7.0 Build 13007421.

Failed - The Operation is not supported on the object.

I have added two Servers and i cannot retrieve Health Information since. The remaining two are not connected to VCenter yet and the sensor Information can be retrieved without any issue.

Wbem has been checked and watchdog restarted.

VCenter will be updated soon so it might fix the issue.

Any help would be appreciated.

Thanks,

Mat

Appliance Management Interface - Change Password Policy Requirements?

Re: VMWare Inventory Service is not able to start

Re: upgrade path from vCenter 5.0 to 5.5 or 6.5

Re: VCSA 6.7 Reboot reason

Re: Appliance Management Interface - Change Password Policy Requirements?

Re: upgrade path from vCenter 5.0 to 5.5 or 6.5

Re: 503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:0x00000259977f60c0] _serverNamespace = / action = Allow _pipeName =\\.\pipe\vmware-vpxd-webserver-pipe)

Re: 503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:0x00000259977f60c0] _serverNamespace = / action = Allow _pipeName =\\.\pipe\vmware-vpxd-webserver-pipe)

Re: VMWare Inventory Service is not able to start

Re: VCSA 6.7 Reboot reason

Re: VCSA 6.7 Reboot reason

Re: vCenter licensing

Upgrade/Fresh Deployment Query

Re: Upgrade/Fresh Deployment Query

Re: Upgrade/Fresh Deployment Query

Re: Upgrade/Fresh Deployment Query

Re: 503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec:0x00000259977f60c0] _serverNamespace = / action = Allow _pipeName =\\.\pipe\vmware-vpxd-webserver-pipe)

VCSA 6.5 to 6.7 upgrade question

Re: VCSA 6.5 to 6.7 upgrade question

Hardware Monitoring issue vCenter 6.7