Camero's Posts

So, you changed the IP and Hostname to static, while configuring the appliance(i.e after initial deployment). I see no problem with this step. Can you check if the "hostname" is same and as... See more...
So, you changed the IP and Hostname to static, while configuring the appliance(i.e after initial deployment). I see no problem with this step. Can you check if the "hostname" is same and as expected after reboot of the vCSA and when the service fails to start. and also does the forwardlookup and reverse lookup works for the IP and hostname you assigned in the above step. shell>hostname shell>nslookup <IP/FQDN>
Vinay, It is not an error. The message prompt is to check if the user would like to allow the plugin "vmware-CSD"  to run or not. The plugin is needed for various operations and usecases. U... See more...
Vinay, It is not an error. The message prompt is to check if the user would like to allow the plugin "vmware-CSD"  to run or not. The plugin is needed for various operations and usecases. User would need the plugin to run if the windows session credentials are used to log in to the vcenter server. And in vcenter 6.0 (and lower versions) plugin is needed for OVF & data store related operations. Hope that helps.
Can you provide the snippet of logs where you see the error in vpxd logs located at vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\V... See more...
Can you provide the snippet of logs where you see the error in vpxd logs located at vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\ vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:\ProgramData\VMware\VMware VirtualCenter\Logs\ KB: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021804 
Can you please confirm if your environment where the vCSA is being deployed satisfies the requirements as mentioned in the following documentation 1. System Requirements for the vCenter Server... See more...
Can you please confirm if your environment where the vCSA is being deployed satisfies the requirements as mentioned in the following documentation 1. System Requirements for the vCenter Server Appliance and Platform Services Controller Appliance and the sub topics 2. Prerequisites for Deploying the vCenter Server Appliance or Platform Services Controller Appliance
Can you check if the vCSA has joined the Domain from CLI. /opt/likewise/bin/domainjoin-cli query and if it is already joined the domain, then try the below steps in order to correct the b... See more...
Can you check if the vCSA has joined the Domain from CLI. /opt/likewise/bin/domainjoin-cli query and if it is already joined the domain, then try the below steps in order to correct the behavior In disjoint domain namespace the domain users might fail to authenticate after you update to vSphere 6.5 Update 1 After you update a Platform Services Controller Appliance to vSphere 6.5 Update 1, in the disjoint domain namespace the users might fail  to authenticate. 1. Log in to the Platform Services Controller Appliance as root and activate the bash shell. 2. Leave the domain by running the /opt/likewise/bin/domainjoin-cli leave command. 3. Reboot the appliance. 4. Delete the computer account on the Active Directory. 5. Log in to the appliance again and enable the bash shell. 6. Join to the domain by running the following command /opt/likewise/bin/domainjoin-cli join domain-name domain_admin_user for example: /opt/likewise/bin/domainjoin-cli join vmware.com administrator 7. Reboot the appliance. Release notes link: VMware vCenter Server 6.5 Update 1 Release Notes
Can you check the following logs for any errors and cut paste the error portion firstbootInfrastructure.log vMon.log and any event failures from Event Viewer which has description simila... See more...
Can you check the following logs for any errors and cut paste the error portion firstbootInfrastructure.log vMon.log and any event failures from Event Viewer which has description similar to "Windows cannot log you on because your profile cannot be loaded...." or "Windows cannot copy file..." and check if the system as the following user profile created "C:\Users\vapiEndpoint"
Seems to work now. May be an intermittent issue, please try one more time and confirm if it works.  .
>5.  Computer name and FQDN names are the same.  Server name is VC651, FQDN name is VC651.domain.com.  The FQDN resolves over DNS forward lookup Can you confirm the reverse lookup works for IP t... See more...
>5.  Computer name and FQDN names are the same.  Server name is VC651, FQDN name is VC651.domain.com.  The FQDN resolves over DNS forward lookup Can you confirm the reverse lookup works for IP to FQDN ? please make sure the reverse lookup returns the IP Documentation: DNS Requirements for vCenter Server and Platform Services Controller on Windows Windows requirements: vCenter Server for Windows Requirements
Can you refer to the white paper https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-vcenter6-performance-white-paper.pdf and also the KB Slow vCenter Server ... See more...
Can you refer to the white paper https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-vcenter6-performance-white-paper.pdf and also the KB Slow vCenter Server performance after increasing the performance data statistics collection level to more than 2 (200388… and alter the performance rollup level.
the problem is VMwareSTS service is not starting during the update. Can you please attach the VMwareSTS logs at the time 2017-08-09T18:15:13 from the SSO folder  at C:\ProgramData\VMware\vCenter... See more...
the problem is VMwareSTS service is not starting during the update. Can you please attach the VMwareSTS logs at the time 2017-08-09T18:15:13 from the SSO folder  at C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSservice\logs\ from vminst-con.log === 2017-08-09T18:15:13.346Z   ERROR Starting service: VMwareSTS, Exception: (2, 'StartService', 'The system cannot find the file specified.') Error executing start on service VMwareSTS. Details {     "resolution": null,     "detail": [         {             "args": [                 "VMwareSTS"             ],             "id": "install.ciscommon.service.failstart",             "localized": "An error occurred while starting service 'VMwareSTS'",             "translatable": "An error occurred while starting service '%(0)s'"         }     ],     "componentKey": null,     "problemId": null } Service-control failed. Error {     "resolution": null,     "detail": [         {             "args": [                 "VMwareSTS"             ],             "id": "install.ciscommon.service.failstart",             "localized": "An error occurred while starting service 'VMwareSTS'",             "translatable": "An error occurred while starting service '%(0)s'"         }     ],     "componentKey": null,     "problemId": null } ===
You may look at the following places for logs to check an obvious errors VMware vSphere 5.0 Client %userprofile%\AppData\Local\VMware\vpx\viclient*.log Update manager: C:\Prog... See more...
You may look at the following places for logs to check an obvious errors VMware vSphere 5.0 Client %userprofile%\AppData\Local\VMware\vpx\viclient*.log Update manager: C:\ProgramData\VMware\VMware Update Manager\Logs\
For reference... https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2149266 that may help resolve the issue.
Have you restarted the update manager service after re-registering the vCenter server ? if not. then please do restart the update manger service.
Before upgrading the vcenter server, Can you check if the vCenter server is up and running and you are able to connect to the vCenter. If yes, then try restarting the vCenter service and do the c... See more...
Before upgrading the vcenter server, Can you check if the vCenter server is up and running and you are able to connect to the vCenter. If yes, then try restarting the vCenter service and do the connection test one more time and then proceed with the upgrade.
EvgeniyL, Your question is not clear. Can you refer to the following document consisting various topology that vCenter supports Supported and deprecated topologies for VMware vSphere 6.5 ... See more...
EvgeniyL, Your question is not clear. Can you refer to the following document consisting various topology that vCenter supports Supported and deprecated topologies for VMware vSphere 6.5 (2147672) | VMware KB and provide us more details on the problem you are having. Also, you may want to refer to following documentation 1. Enhanced Linked Mode Overview 2. vCenter Server and Platform Services Controller Deployment Types 3. Introduction to vSphere Installation and Setup
MTomasko Any reason why the Update manager is still at 55U3 and not the same version as the vCenter Server Appliance version 55u3e ? Could you please upgrade the Update manager to the same ... See more...
MTomasko Any reason why the Update manager is still at 55U3 and not the same version as the vCenter Server Appliance version 55u3e ? Could you please upgrade the Update manager to the same version as vCenter server i.e., 55u3e  in your case and let us know the configuration works. Update manager 55u3e: VMware vCenter Server 5.5 Update 3e Release Notes
Attach the logs to this thread ... If you need to scrub/change any confidential info like IP's, system name etc.. please do before attaching the logs here ..
Would you be able to provide the install logs here ?
Your plan of upgrade looks good as there are only two PSCs and are replicating. Once completion of migration of data from OLD PSCs to the newly deployed PSCs you may proceed with the upgrade of t... See more...
Your plan of upgrade looks good as there are only two PSCs and are replicating. Once completion of migration of data from OLD PSCs to the newly deployed PSCs you may proceed with the upgrade of the VCs. ===From the documentation=== Important: For topologies with external Platform Services Controller instances, you must upgrade the replicating Platform Services Controller instances in a sequence. After the successful upgrade of all Platform Services Controller instances in the domain, you can perform concurrent upgrades of multiple vCenter Server appliances that point to a common external Platform Services Controller instance. === Please refer to the documentation for step by step approach & other important info. doc: Upgrading the vCenter Server Appliance and Platform Services Controller Appliance Supported topologies in 6.5 :  Supported and deprecated topologies for VMware vSphere 6.5 (2147672) | VMware KB Important Info to consider before upgrading to 6.5: Important information before upgrading to vSphere 6.5 (2147548) | VMware KB Best practices for upgrading to vCenter server 6.5: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147686
vCSA upgrade (i.e major version) is always out  of place upgrade, which means a new Appliance is deployed and the data from existing/old appliance is migrated to the newly deployed appliance. F... See more...
vCSA upgrade (i.e major version) is always out  of place upgrade, which means a new Appliance is deployed and the data from existing/old appliance is migrated to the newly deployed appliance. For any minor version updates the inplace update is applicable. Differences Between vSphere Upgrades and Updates   please refer to the documentation for upgrading to to vCSA 6.0 from 5.x  : About the vCenter Server Appliance Upgrade Process