Does VMware supports link mode of Different versions of vCenter?
Does it needs that vCenter IPs are in the same range IP range or subnet, or it doesnt matter as long IPs are routable and can ping each other?
Does VMware supports link mode of Different versions of vCenter?
Does it needs that vCenter IPs are in the same range IP range or subnet, or it doesnt matter as long IPs are routable and can ping each other?
we have vcenter 5.5 u2 and esxi 5.5 cluster. Some servers have performance problems. User says memory is not enough. These servers are RedHat 6 or RedHat 7. Virtual machine has 24 gb memory and user says 24 gb full and also 7 gb swap . but i checked the vcenter memory tab and vrealize. The server used max 20 gb of memory in the last week so vcenter and vrealize says memory is enough for this virtual machine. I have read as many articles as I am now, but for sure I didn't understand what value was correct. Did you have experience. The end user is telling the truth? should I increase ram ? I don't know who I should believe
I have one vm and it has 4 snapshot but Someone deleted the one snapshot file while the server was down . now i cant open vm so is there any solution ? we have no backup.
error code :
File /vmfs/volumes/58de2da4-c6bc78ac-9643-5cf3fc9414d0/test-clone/test-clone-000002.vmdk was not found
Hi,
I downloaded the vSphere SDK 6.0.0-2561048. And run "run.bat" under SDK\vsphere-ws\java\JAXWS.
command: > run.bat com.vmware.general.GetHostName --url https://[my vcenter IP]/sdk --username [my username] --password [my password].
It returned error:
ERROR: could not connect: login fault : The server sent HTTP status code 404: Not Found
I confirmed that my username and password is correct and have right privilege.
My vCenter is 6.0.0, 3018524.
I tried the same command on another vCenter, it returned the ESXi hosts information.
Can someone tell me what did I miss in the vCenter which returned error?
Thanks!
Hi all,
Doing a deployment of a new vCenter 6.0 U3a we are getting Failed to initialize VMware Certificate Authority - Error 100004 ( popup title install.vmafd.vmca_selfcafailed ) . Not gonna paste from the logs unless needed. . We checked DNS entries/ DB connection / everything else that we could think of ,
I think I found the issue. We are able to install on the same OS / same settings vCenter 6.0 U2a . Done several revert to snapshot and reproduced the scenario several times - each time getting the same conclusion : vCenter 6.0U2a works , u3/u3a does not Work.
So what I saw is that openssl version was changed. My ideea is that we are missing a hotfix on the Windows VM ( which is Windows 2008 R2 patched with security hotfixes only ) . So now I'm trying to see what might be the hotfix that we need ( taking in consideration that we can't just put all patches ) .
Have also a SR opened to VMware, so far no solution .
Any ideas, anyone ?
Thank you.
Hey im having a proble with vmware vsphere 4.1
when i go to install update manager i cant get a 32 bit dsn and i pressed install a sql server 2005 instance but that will overwrite the exsisting SQLEXP_VIM database.
What should i do?
Hi,
even if I start vCenter with https://vcenter/vsphere-client/?locale=en_US all alarms and tasks are in German language, but I'd like to have it in English.
How is it possible to change this on a vCenter 6 Appliance?
Regards Wolfgang
For security issues, my customer wants to know where to find access logs for vcenter and esxi. Would it be possible for a vcenter to send an email every time an access is made? Thanks in advance.
Hello Team,
I have a customer who have upgraded vCenter from 6.0 to 6.5.
But the python version is still 2.7.11 which has vulnerability as mentioned below.
*Summary:*
This host is running Cpython and is
prone to man in middle attack and arbitrary code execution Vulnerabilities.
*Insight:*
The multiple flaws exist due to the smtplib
library in CPython does not return an error when StartTLS fails and integer
overflow error in the 'get_data' function in 'zipimport.c' script.
*Impact:*
Successful exploitation will allow
man-in-the-middle attackers to bypass the TLS protections and remote attackers
to cause buffer overflow.
*Impact Level:* Application
*Affected Software/OS:*
Cpython before 2.7.12, 3.x before 3.4.5,
and 3.5.x before 3.5.2 on Windows.
*Vulnerability Detection Method:*
Get the installed version with the help of
detect NVT and check the version is vulnerable or not.
Installed version: 2.7.11
Fixed version: 2.7.12
I have done a test by fresh installation of vCenter 6.5 and the vulnerability is gone since we have python 2.7.12 is installed.
Now my question is how do I install python version 2.7.12 or upgrade the python version from 2.7.11 to 2.7.12
I am running the most current versions of eveything.
ESX 4.0 Update 1
and the latest builds of vcenter server and client.
My workstation is running server 2008 x64
I am using remote desktop (RDP) to go from my client workstation into a VM that is running vcenter client.
The VM is server 2008 R2.
When trying to work inside any console session from within the vi client my mouse disappears as soon as I click inside the console window. The mouse still works. If I right click somewhere I see menus pop up, etc. It's just that the pointer completely vanishes. (the cursor is visible during the ctrlaltdel logon screen)
Through means of troubleshooting here are the things that I have found out.
When VMware tools is not installed the problem does not occur (but the mouse is choppy so this isn't a fix)
When VMware tools IS installed, but the pointing device driver is changed from "vmware pointing device" to "PS/2 compatible mouse" the problem does not occur
When VMware tools IS installed and the pointing device driver is the default "vmware pointing device" and "enable pointer shadow" is enabled in the mouse properties the problem does not occur. However by enabling the pointer shadow it makes my mouse rather choppy, so this still isn't a solution.
It looks as though there is something funky going on when using 2008 in conjuction with RDP and working inside VM consoles.
Has anyone else seen this behavior?
I'm currently trying to remove vCenter completely from a server that had a botched install. The installation said it completed successfully, but most of the vCenter modules never actually installed and instead loaded my services window with a bunch of non-functional VMWare services. The uninstallation completes almost to the end and then I get a window popup with: "VMware vCenter Server 6.0.0 - Internal Error 2755. 1605, <Path>\VMWare-vCenter-Server.msi"
This is running on a newly installed/updated Windows 2012R12 server - any ideas on how to proceed, or manually remove all vCenter remnants, so I can reinstall again?
Thanks in advance!
Morning all
I'm trying to get the below 3 commands into the same CSV, would any kind powershell soul care to help?
The below gives an out put of all the associated Tags a VM has:
$tagCat = @()
$tagTab = @{}
foreach($tag in (Get-VM | Get-TagAssignment)){
$tagCat += $tag.Tag.Category.Name
$key = $tag.Entity.Name
if($tagTab.ContainsKey($key)){
` $val = $tagTab.Item($key)
}
else{
$val = @{}
}
$val.Add($tag.Tag.Category.Name,$tag.Tag.Name)
$tagTab[$key] = $val
}
$tagCat = $tagCat | Sort-Object -Unique
$tags = foreach($row in ($tagTab.GetEnumerator() | Sort-Object -Property Key)){
$obj = New-Object PSObject -Property @{
VM = $row.Key
}
$tagCat | %{
$obj | Add-Member -Name $_ -Value $row.Value[$_] -MemberType NoteProperty
}
$obj
}
$tags | Export-Csv c:\temp\tags.csv -NoTypeInformation -UseCulture
I'd like this merging with the below two:
get-vm | % { get-view $_.id } | select Name, @{ Name="ToolsVersion"; Expression={$_.config.tools.toolsVersion}},@{ Name="ToolStatus"; Expression={$_.Guest.ToolsVersionStatus}}
get-vm -Name pxgbssc1vmc001 | select version
So ultimatley I have a CSV with VM name, associated tags, VMware tools version/status and VM hardware version.
Thanks in advance!
Ollie
we are using two vcenter 6.5 . two vcenter joined same domain controller and same networl . now i want to create linked mode both server. how to setup all. i cant find any step by step document. so i dont want to install all vcenter again so just need edit and setup linked mode for our vcenters
I have integrated Active Directory and assign the permission to AD users but still i am unable to login with AD users in vSphere web client
Hi,
I tried install VMware Client Integration Plugin 6.0 for deploy new vCenter Server VA and I received this error:
There is a problem with this Windows Installer package.
A program run as part of the setup did finish as expected.
Contact your support personnel or package vendor.
On the background is a window with status:
Installing certificates and starting services...
In folder %TEMP% is log file vmmsi.log_<date_time>_Failed.log
Key data:
14:24:29:296]: Executing op: ActionStart(Name=CsdServiceInstall,Description=Installing certificates and starting service...,)
Action 14:24:29: CsdServiceInstall. Installing certificates and starting service...
MSI (s) (60:34) [14:24:29:306]: Executing op: CustomActionSchedule(Action=CsdServiceInstall,ActionType=3090,Source=C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe,Target=--install,)
CustomAction CsdServiceInstall returned actual error code 3 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (60:34) [14:24:29:936]: Note: 1: 1722 2: CsdServiceInstall 3: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe 4: --install
MSI (s) (60:34) [14:24:29:936]: Note: 1: 2205 2: 3: Error
MSI (s) (60:34) [14:24:29:936]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install
MSI (s) (60:34) [14:24:32:005]: Note: 1: 2205 2: 3: Error
MSI (s) (60:34) [14:24:32:005]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (60:34) [14:24:32:005]: Product: VMware Client Integration Plug-in 6.0.0 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CsdServiceInstall, location: C:\Program Files (x86)\VMware\Client Integration Plug-in 6.0\vmware-csd.exe, command: --install
Unfortunately I couldn't find out the reason of error from this log.
After my extremely long researching I find out
that subprocess vmware-csd (creating keys and certificetes) logs into the folder C:\ProgramData\VMware\CIP\csd\logs
Example of the log file (csd_000x.log) in troublefree installation:
[2015-03-16 16:30:39] [INFO] Certificate registered!!!
[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.
[2015-03-16 16:30:39] [INFO] Changes to the hosts file were successful.
[2015-03-16 16:30:39] [INFO] Successful install of CSD protocol handler.
In my case log file ended:
[2015-03-16 16:30:39] [INFO] Certificate registered!!!
There were missing records about some modification of file hosts.
Reason:
Installer will fail, if the file hosts.bak exists there before running installation of VMware Client Integration Plugin 6.0 !
Solution:
Rename or delete file hosts.bak in folder C:\Windows\System32\drivers\etc\
Good Luck.
P.S.
Deacivate any antivirus before starting the installation of VMware Client Integration Plugin 6.0
We have setup a testing environment to perform an upgrade from vSphere 5.5 to 6.0 U3
Have updated one vcenter from 5.5 to 6.0 U3 and try to test custom certificates. All infrastructure servers are installed on Windows 2008 R2 Standard (Vcenter, AD/CA, SQL)
Tried to follow this article Replacing a vSphere 6.x Machine SSL certificate with a Custom Certificate Authority Signed Certificate (2112277) | VMwar…
We have created certificates template using this article as guide Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0 (2112009) | VMware KB
Creating a new template for vSphere 6.0 to use for Machine SSL and Solution User certificates
Connecting to the CA server, you will be generating the certificates from through an RDP session.
Click Start > Run, type certtmpl.msc, and click OK.
In the Certificate Template Console, under Template Display Name, right-click Web Server and click Duplicate Template.
In the Duplicate Template window, select Windows Server 2003 Enterprise for backward compatibility.
Note: If you have an encryption level higher than SHA1, select Windows Server 2008 Enterprise.
Click the General tab.
In the Template display name field, enter vSphere 6.0 as the name of the new template.
Click the Extensions tab.
Select Application Policies and click Edit.
Select Server Authentication and click Remove, then OK.
Note: If Client Authentication exists, remove this from Application Policies as well.
Select Key Usage and click Edit.
Select the Signature is proof of origin (nonrepudiation) option. Leave all other options as default.
Click OK.
Click the Subject Name tab.
Ensure that the Supply in the request option is selected.
Click OK to save the template.
Proceed to Adding a new template to certificate templates section in the article to make the newly created certificate template available.
On Vcenter server 6.0U3 (Embeded PSC) we run the certificat manager tool to generate CRS records, we have used option 1 and 5 as our goal is to use custom certificates.
We followed this article to get certificates from Microsoft CA Obtaining vSphere certificates from a Microsoft Certificate Authority (2112014) | VMware KB
Note: this is a simple lab environment so there is no intermediate CA only the root one on Windows 2008R2
We copied certificates to the new vcenter and tried to import Machine SSL certificate and got the above error
Previous Machine_SSL_CERT Subject alternative name does not match new Machine_SSL_Certificate Subject alternative name
We tried to use san:dns=fqdn..... using attributes box from CA to specify a unique SAN but got same error
Have attached the certtool.cfg file and certificate manager log. Any help would be appreciated
I'm not sure where to go next with this, hoping someone can offer advice...
This is a fresh install of vCenter 5.5 and an existing ESXi 5.5 server. I see my ESXi host and all details in the web console, but it shows up as "not responding". I can successfully disconnect/reconnect but every time, 60-90 seconds after successful reconnect it goes back to "not responding".
FYI:
Is there anything else I can test or do to isolate what could be causing this? I'm happy to provide any needed additional details.
Can anyone point me in the right direction for where the logs files are that I can see failed login attempts to the web client?
Thanks in advance.
Hi All,
For the life of me I cannot work out how the hell this happened, but I now have multiple services that cannot start reporting an incorrect username and/or password.
I can't seem to find anywhere where these details would be defined so they can be verified. This is the latest build of vCenter Server 6.5 on a fully patched Windows Server 2012 R2 server.
Service Status check shows the following:
C:\Program Files\VMware\vCenter Server\bin>service-control --status --all
Running:
VMWareAfdService VMWareCertificateService VMWareDirectoryService VMwareComponentManager VMwareDNSService VMwareIdentityMgmtService VMwareSTS VServiceManager content-library rhttpproxy vimPBSM vmon vmonapi vmsyslogcollector vmware-cis-config vmware-license vmware-perfcharts vmware-psc-client vmwareServiceControlAgent vpxd vpxd-svcs vsan-health
Stopped:
EsxAgentManager VMWareCAMService mbcs vapiEndpoint vmware-autodeploy-waiter vmware-imagebuilder vmware-network-coredump vsphere-ui vspherewebclientsvc
When trying to run "service-control --start vsphere-client" from an elevated command prompt, the vMon log shows the following:
2017-01-31T23:02:09.998+11:00| vthread-5| I125: Received request to get service state for vmon
2017-01-31T23:02:09.998+11:00| vthread-5| E110: Service vmon not found.
2017-01-31T23:02:10.012+11:00| vthread-5| I125: Received request to get service state for vsphere-client
2017-01-31T23:02:10.023+11:00| vthread-5| I125: Received request to get service state for vsphere-client
2017-01-31T23:02:10.035+11:00| vthread-5| I125: Received start for vsphere-client
2017-01-31T23:02:10.035+11:00| vthread-5| I125: Constructed command : "C:\Program Files\VMware\vCenter Server/visl-integration/usr/sbin/cloudvm-ram-size.bat" -J vsphere-client -O C:\ProgramData\VMware\vCenterServer\data/vmware-vmon/vsphere-client.start.cmd
2017-01-31T23:02:10.036+11:00| vthread-5| I125: Setting working dir of process to C:\Program Files\VMware\vCenter Server/virgo/server.
2017-01-31T23:02:10.037+11:00| vthread-5| E110: Failed to Logon as vsphere-client user. Error: The user name or password is incorrect
2017-01-31T23:02:10.037+11:00| vthread-5| E110: Service vsphere-client pre-start command could not started.
If anyone can assist in rectifying this stuff up, that'll be greatly appreciated
Many thanks in advance!
Cheers,
Ray
Hi,
I am running the latest version of vCenter 6.5 with the latest version of ESXi 6.5 on the hosts.
I have the VMRC installed
When I open a remote console with VMRC and go to full screen and then back to window I get the following logged in Recent Tasks
Name: VirtualMachine.setDisplayTopology.label
Status: The operation is not supported on the object
Going to full screen doesn't generate this. Only going back to window from full screen.
Any ideas?