Here is what I have:

- ESXi4.1

- vCenter 4.1, brand new install

- I created a new VM (Virtual Hardware v. 7, VMXNET3 NIC) which I am going to use as a template and installed Windows Server 2008 R2 from an ISO image I downloaded from Microsoft.

- Installed Windows updates and made a couple minor customization i.e. disabled UAC, firewall, IE ESC etc.

- created new guest customization specification for Windows 2008 R2 with standard parameters

     Registration info...

     Computer name - use Virtual Machine name

     Product Key - blank (tried to use KMS key as well which did not make any difference)

     Server license mode - per Seat. (tried without it as well)

     Admin Password - Standard local admin password for my company

     Time Zone - GMT

     Run Once - empty

     Join Workgroup (the template server is not on the domain)

     Generate SID.

- powered off VM

When I clone VM and use customization template it does not work. According to Tasks & Events it gets stuck at:

Started customization of VM test4. Customization log located at
C:\Windows\TEMP\vmware-imc\guestcust.log in the guest OS.

Exactly the same customization template works fine for Windows Server 2008 SP2.

What am I doing wrong?

Hello,

I have been trying to install a PSC inside my embedded vCenter 6 so I can move to a seperated model. The first install of the 2nd PSC failed and it is showing up in the webclient yet I cannot remove it. When i run vdcleavefed I get "leave federation cleanup failed. error 13 - confidentiality required"

See the pic I am trying to remove the highlighted PSC.

Hi people,

I have implemented vCenter Server 6 WEB appliance and tried to import self signed SSL Machine certificate, in order to access on vCenter web interface using that certificate for HTTPS. Certificate was signed by Windows Server 2008 CA with template configured using these instrustions: Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0 (2112009) | VMware KB. Also, I tried to import Comodo Trial Positive SSL certificate with same issue - couldn't import it.

I used the VMCA script for certificate management and also tried to import them manually using this procedure: vSphere 6.0 Documentation Center. In both cases, process crashed during vmware-vpxd service restarting process. VMCA script exited with rolling-back old certificates. After trying to manual replace certificates using commands certool and vecs-cli, I tried to start vmware-vpxd service using command service vmware-vpxd start. It produced following output:

virtual:~ # service vmware-vpxd start

vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

Waiting for the embedded database to start up: success

Executing pre-startup scripts...

vmware-vpxd: Starting vpxd by administrative request.

success

vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

Waiting for vpxd to initialize: ..........................................................Fri Jun 17 14:19:51 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-19-51

[INFO] writing vpxd process dump retry:2 Time(Y-M-D H:M:S):2016-06-17 12:19:48

.Fri Jun 17 14:20:13 CEST 2016 Captured live core: /var/core/live_core.vpxd.7892.06-17-2016-14-20-13

[INFO] writing vpxd process dump retry:1 Time(Y-M-D H:M:S):2016-06-17 12:20:01

.failed

failed

vmware-vpxd: vpxd failed to initialize in time.

End of the /var/log/messages log file contains following:

2016-06-17T14:10:04.149368+02:00 virtual vmware-vpxd: VC SSL Certificate does not exist, it will be generated by vpxd

2016-06-17T14:10:04.158972+02:00 virtual root: RHTTPPROXY_HTTP_PORT = 80

2016-06-17T14:10:04.168334+02:00 virtual root: RHTTPPROXY_HTTPS_PORT = 443

2016-06-17T14:10:04.748884+02:00 virtual vmware-vpxd: Starting vpxd by administrative request.

2016-06-17T14:10:05.811146+02:00 virtual vmware-vpxd: Waiting for vpxd to start listening for requests on 8089

2016-06-17T14:10:11.068787+02:00 virtual kernel: [ 8262.100377] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32356 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:10:41.045286+02:00 virtual kernel: [ 8292.062481] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32645 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:11.392806+02:00 virtual kernel: [ 8322.396547] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=280 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:11:41.380687+02:00 virtual kernel: [ 8352.368229] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=593 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:11.508805+02:00 virtual kernel: [ 8382.477595] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=905 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:12:41.124668+02:00 virtual kernel: [ 8412.078362] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1173 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:11.068788+02:00 virtual kernel: [ 8442.006593] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1480 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:13:41.052756+02:00 virtual kernel: [ 8471.975786] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=1805 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:10.948713+02:00 virtual kernel: [ 8501.859385] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2068 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:14:41.048793+02:00 virtual kernel: [ 8531.942485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2336 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:01.102632+02:00 virtual /usr/sbin/cron[6935]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:15:10.976770+02:00 virtual kernel: [ 8561.853765] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=2622 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:15:41.220689+02:00 virtual kernel: [ 8592.076813] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:fc:4d:d4:d2:e5:a9:08:00 SRC=192.168.0.23 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5745 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:16:10.988809+02:00 virtual kernel: [ 8621.836572] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:3c:97:0e:32:f7:1c:08:00 SRC=192.168.0.80 DST=192.168.0.255 LEN=229 TOS=0x00 PREC=0x00 TTL=128 ID=16631 PROTO=UDP SPT=138 DPT=138 LEN=209

2016-06-17T14:16:41.200814+02:00 virtual kernel: [ 8652.031163] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3292 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:11.040715+02:00 virtual kernel: [ 8681.856944] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3595 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:17:41.012706+02:00 virtual kernel: [ 8711.812066] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=3808 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:10.948718+02:00 virtual kernel: [ 8741.730820] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4046 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:18:40.936986+02:00 virtual kernel: [ 8771.705858] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4360 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:11.024790+02:00 virtual kernel: [ 8801.777535] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=4647 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:19:41.144770+02:00 virtual kernel: [ 8831.881485] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=5909 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:01.147104+02:00 virtual /usr/sbin/cron[13172]: (root) CMD ( /usr/sbin/iiad.sh >/dev/null 2>&1)

2016-06-17T14:20:01.153980+02:00 virtual /usr/sbin/cron[13171]: (root) CMD ([ -x /usr/lib64/sa/sa1 ] && exec /usr/lib64/sa/sa1 -S ALL 1 1)

2016-06-17T14:20:01.157092+02:00 virtual /usr/sbin/cron[13175]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)

2016-06-17T14:20:01.163979+02:00 virtual /usr/sbin/cron[13170]: (root) CMD ( test -x /usr/sbin/cloudvm_ram_size_periodic && /usr/sbin/cloudvm_ram_size_periodic >/dev/null 2>&1)

2016-06-17T14:20:11.664891+02:00 virtual kernel: [ 8862.387284] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6251 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:20:23.877678+02:00 virtual vmware-vpxd: vpxd failed to initialize in time.

2016-06-17T14:20:41.260666+02:00 virtual kernel: [ 8891.967607] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6551 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:10.940726+02:00 virtual kernel: [ 8921.632250] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=6906 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:21:41.452588+02:00 virtual kernel: [ 8952.121422] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:8d:f4:26:08:00 SRC=192.168.0.51 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=22577 PROTO=UDP SPT=137 DPT=137 LEN=58

2016-06-17T14:22:11.080638+02:00 virtual kernel: [ 8981.739467] IPfilter Dropped: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:24:7c:8a:09:08:00 SRC=192.168.0.94 DST=192.168.0.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7505 PROTO=UDP SPT=137 DPT=137 LEN=58

Please help me, tell me where I made mistake. Thank you in advance.

Hello,

A brief idea of my test lab environment:

vCenter Servers:

vc1 - Registered to psc1 in Site1

vc2 - Registered to psc2 in Site2

External Platform Services Controllers:

psc1 - Site1

psc2 - Site2

SSO Domain: vsphere.local

I upgraded from vCenter Server 5.5 Update 3d to vCenter Server 6.0 Update 2. The vCenter servers in 5.5 had integrated / embedded SSO's and all the services running on the same machine and were in linked mode before the upgrade and I removed them from linked mode before the upgrade. They were upgraded to vCenter Server 6.0 with Embedded PSC and they automatically entered Enhanced Linked Mode (ELM).

After the step above, I deployed 2 external PSC's psc1 and psc2 in replication mode with vc1 and vc2 in the same site's Site1 and Site2 respectively. I then migrated the embedded psc's of both the vCenter Servers to their respective external psc replication partners by running the command cmsso-util reconfigure --repoint-psc "psc1/psc2" --username administrator --domain-name "vsphere.local" --passwd "administrator_password". This operation completed successfully and my vCenter's were reconfigured as vCenter Server with External PSC.

After this, I followed VMware KB article 2127057 (Determining replication agreements and status with the Platform Services Controller 6.0 (2127057) | VMware KB) to make the 2 external psc's psc1 and psc2 replication partners of each other by running the command vdcrepadmin -f createagreement -2 -h psc2.clifford.local -H psc1.clifford.local -u administrator -w "administrator_password". I ran this command from psc2. This operation also completed successfully and when I query the replication status of the replication partners psc1 and psc2, there is nothing wrong. However after restarting my vSphere Infrastructure, I see that vc1, psc1 and psc2 have all their services started successfully.

vc2 services seem to be failing to start, especially the VMware Component Manager service which is required for many other services to start. The VMware HTTP Reverse Proxy service starts successfully and I don't have any IIS role / feature installed on my machine. The error message that occurs while trying to manually start the service is as attached as file Error2.JPG in the discussion. The error from the Windows Event Log is as attached as file Error3.JPG in the discussion.

Please let me know how do I resolve this issue at the earliest.

I need to know how to produce performance excel spreadsheets for all VMs at once.

Anyone?

Hi All

I have a problem with the peformance tab not showing any data for VMs & hosts. I have done a fair bit of searching on this problem and not found an answer yet. My thoughts is that its a vCenter database problem because when I login directly to an ESXi host I can get the performance stats from the tab in question.

I have recently upgraded our three ESXi hosts from 5.0 to 5.1 build 838463 and created an new copy of vCenter 5.1 and connected the hosts to the new copy of vCenter. As far as I know the performace stats were working on 5.0 and looks like they have stopped working after the upgrade. I upgraded the hosts using update manager and installed the ISO image from Dell that included the VIB for hardware monitoring.

Environment:

3x Dell R710, 128GB RAM each

ESXi 5.1 Build 838463 Enterprise Plus

vCenter 5.1 build 880146 Standard

Please let me know if you have any ideas or suggestions, I have attached a screenshot of the graphs showing no data.

Regards,

Andrew

Let's use this thread to upload screenshots for vSphere Client (HTML5) related discussions.

Hi every one,

i have join the vCenter node to our Domain

and reboot the VM appliance vCenter.After that, i check and it's ok vCenter Appliance is join our Active directory domaine Windows Server 2003.

Now,i try to add a new source identity, i have an error: Provided credentials are not valid

this is my configuration when i try to add a new source

• identity source type: Active Directory as LDAP Server
• Name: ourdomain.com
• Base DN for users: OU=Users,DC=OURDOMAIN,DC=COM
• Domain name: OURDOMAIN.COM
• Domain alias: OURDOMAIN
• Base DN for groups: OU=Users,DC=OURDOMAIN,DC=COM
• Primary server URL: ldap://DC1.OURDOMAIN.COM:389
• Secondary server URL:
• Username: Administrateur@ourdomain.com
• Password: PasswordofAdministrateur

When i click test connection, it's work i have seccuessfuly test but whene i try to add this source i have this error: Provided credentials are not valid

Any one can help me please ?

Best regards

As reported in http://communities.vmware.com/message/2020222 we are still experiencing the issue with vpxd consuming huge amounts of RAM and causing severe vCenter slowness.  This has gotten much worse recently.  We are hoping to renew the conversation on this, as it is becoming intollerable, and our efforts have so far failed. 

Configuratoin: VMware vCenter Server 5.0, update 1, version 5.0.0 build 623373.  Running on Windows Server 2008 R2 Standard SP1, in a virtual machine with 4 vCPUs and 8 GB of memory, SQL database on same machine.

When the issue opccurs, the main vCenter executable, vpxd.exe uses up all available memory, causing severe vCenter slowness, to the point where vSphere Client cannot connect, tasks fail due to timeouts, remote desktop to the machine are extremely slow and almost completely unusable.  After stop/start of vpxd.exe service, or restart the Windows VM, the issue initially clears, but then returns later. We are now seeing this more than once per day, sometime 3 - 4 times in a single day.

In more detail:

- Windows task manager reports 99% of  memory is consumed.  Typically, this is around 6.5 GB of memory consumed  by vpxd.exe.

- Before the issue occurs, vpxd is typically consuming around 330 MB memory (reasonable)

- Other large consumers are sqlservr.exe around 1.0 GB, java.exe around 820 MB + 380 MB (there are two processes), tomecat6.exe 690 MB.  We think these are probably normal, and they do not grow out of control like vpxd does.

- During the issue, CPU also becomes very high, near 100%, as seen through vSphere Client performance

- VM is running current VMware tools (8.6.5, build 652272)

Things we have tried:

- Upgraded to vCenter Server 5.0u1

- Rebalanced vCPUs (as suggested in other thread).  Initially was 4 CPUs on 1 socket, changed to 2 CPUs on 1 socket, now 4 CPUs split across 2 sockets.

- Moved to VM version 8

- Set service to autostart, delayed

- General cleanup -- removed a bunch of servies we are not using (Orchestrator, Update Manger...)

Any further suggestions, known issues, FIXES, whatever would be helpful! 

-- PeterB

Hi, all

I want to understand "Status: degraded".

But I can not see an explanation on CLI manual.

[FYI]

It state can see "esxcli storage core device list" command.

naa.60060480000290105757533030363837:
   Display Name: EMC Fibre Channel Disk (naa.60060480000290105757533030363837)
   Has Settable Display Name: true
   Size: 2
   Device Type: Direct-Access
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/naa.60060480000290105757533030363837
   Vendor: EMC    
   Model: SYMMETRIX      
   Revision: 5773
   SCSI Level: 4
   Is Pseudo: true
   Status: degraded <-----Here!!!!!
   Is RDM Capable: true
   Is Local: false
   Is Removable: false
   Is SSD: false
   Is Offline: false
   Is Perennially Reserved: false
   Thin Provisioning Status: unknown
   Attached Filters:
   VAAI Status: unknown
   Other UIDs: vml.0200fa00006006048000029010575753303036383753594d4d4554

Thanks

I've been struggling with this- ensuring that our users have the minumum permissions on our ESX VC system. When we first set up our first ESX cluster and VC, we gave everyone VM Admin permissions on their own folders and VM's, as well as VM Admin privs on the datacenter, cluster and host server (without propagating thos permissions past past the host server).  This allows users to mess with VM advanced settings, like CPU affinity, which screws up Vmotion on the ESX cluster.  So, what I've done is clone the VM Admin role and remove anything that allows the user to edit advanced settings on the VM, or anything on the host except create/remove VM's.  So far, All of the users can edit their VM's (but not the advanced settings), take and manage snapshots- they can do everything they need except clone a VM.

The way permissions are set up: put the most permissions at the top of the heiarchy, and then limiting them as you drill down the ladder (something VMware tech support had us do when we initially set up our system two years ago).  For the sake of the explaination, we'll call my altered VM Admin role as Company User.

On the Hosts and Clusters view, the typical user has Company User privs On the Hosts and Clusters object, which is propogated down to the datacenter object, cluster object and host server objects.  At the Host server, the role is changed to not propogate any further.  On any datacenterthat the user is not supposed to access, the permissions are change to "no access".

  On the Folders and Templates view, the Company User role is assigned to the user at the Folder and Templates object, and allowed to propogate down through the datacenter object.  On each of the folders under the datacenter object, the user is either change to "no access" if they're not supposed to access that folder, or the permission is allowed to propogate.

Here's the permissions I have set up on the Company User role:

• Global

• Cancel Task

• Host

• Local Operations

• Create Virtual Machine

• Delete Virtual Machine

• Virtual Machine

• Inventory

• Create

• Remove

• Move

• Interaction

• Power On

• Power Off

• Suspend

• Reset

• Answer Question

• Console Interaction

• Device Connection

• Configure CD Media

• Configure Floppy Media

• Tools Install

• Configuration

• Rename

• Add Existing Disk

• Add New Disk

• Remove Disk

• Change CPU COunt

• Memory

• Add/Remove Device

• Modify Device Settings

• Settings

• Upgrade Virtual Hardware

• Reset Guest Information

• State

• Create Snapshot

• Revert Snapshot

• Remove Snapshot

• Rename Snapshot

• Provisioning

• Custommize Clone

• Clone

• Create Template from VM

• Deply Template

• Clone Template

• Mark as template

• Mark as virtual machine

• read customization specifications

• Allow Disk Access

• Resource

• Migrate

• Relocate

• Scheduled Task

• Create Tasks

• Remove Task

• Run Task

• Modify Task

Finally, this is a VirtualCenter 2.5.0 build 104215, and the ESX servers are running ESX 3.5.0 build 120512

Hi,

In the normal Windows based vCenter, there are options to set log rotation settings for the syslog service to which the ESXi-hosts are logging.

I can't find this option in the vCenter Appliance. Does it do this automatically? Or do I need to do manual scripting for this?

Has anyone seen this error when trying to remove a replication agreement?

I have 6 PSCs in my domain and was removing some excess agreements. It seems like I am only getting this error when trying to remove agreements from a particular PSC

have an interesting situation in our VMware Infrastructure.   We have what appears to be 2 DataCenters observed in our vCenter Server 5.5.  All hosts are ESXi5.5.

I have always worked vMotion under the belief that I could not vMotion a VM in one DataCenter into a host on another DataCenter.   Each DataCenter supports different vLan subnets.  However, in our situation that appears NOT to be true.   We have been able to vMotion a VM from DataCenter2 to DataCenter1.   The odd thing is that we CAN NOT vMotion the other way around.  So, vMotion is only one way. 

I thought this might be explained by looking at the way the switches are setup in each DataCenter.  

DataCenter1:   Hosts on this DataCenter are setup with standard virtual switches. 

DataCenter2.   Hosts on this DataCenter are setup with dvSwitches

I don't see any VMports or management network assigned to the IP addresses on either DataCenter. 

The shared storage also is different and that is what I would expect since each DataCenter hosts its own SAN.

So, I'm confused.  How is it that a VM can vMotion across DataCenters?

Can anyone please describe to me what the difference is between Health Status Changed and Health Status Monitoring?  They both seem to be alerts for vCenter "service".  Any help greatly appreciated.  Thanks.

Health Status Changed

Default alarm to monitor changes to service and extension health status

Health Status Monitoring

Default alarm to monitor changes in overall health status. See vCenter Service Status on the Home view for more details.

BigD

Hello.

Have big problem with vSphere client

Today i press button Clear SSL certificate in IE on my Windows 7 OS

Then i faced with strange issue

I'm trying connect to vm console (client connected to vCenter) and i have an error ssl verification failure for "ip" due to a host thumbprint mismatch.

It's happend again then i trying to connect directly to ESXI

vCenter version 5.0,ESXi 5.0

What I tried to do - clear SSL ignore by regedit, reinstall vSphere client - it's not resolve a problem

I'm still not able to connect to any VM console

I'm trying connect from websphere - no luck,same error

Then i install client on different machine - all running ok

Hi all,

Trying to install and external PSC appliance 6.0 u1.  Put in the info and click next to start the install and it sits there for a few minutes and fails.  At the bottom of the vcsa_0000.log is the following:

2015-11-20 09:35:40.590700 --prop:guestinfo.cis.appliance.time.tools-sync=True

2015-11-20 09:35:40.590700 --prop:guestinfo.cis.clientlocale=en

2015-11-20 09:35:40.590700 --targetSSLThumbprint=*

2015-11-20 09:38:40.857317 Progress Controller: [VCSA ERROR] - Progress callback error

2015-11-20 09:46:53.767685 Progress Controller: Closing the installation wizard

Not sure what the issue is here.  I Googled the error and got nothing.

Hello

I have recently upgraded our VMware estate to 5.5, however we use a virtual machine as the VSphere server. This has caused an issue because I have upgraded the VMware hardware to V10 and I would like to change the VM's settings...however if you power off the vm (to change the settings) I lose web management (because it is hosted from the VSphere server) and I cant use the Windows "fat client" to change the settings because you get the following error message "You cannot use the VSphere client to edit the settings of virtual machines of version 10 or higher, use the VSphere Web Client to edit the settings of this machine"

It is a complete catch 22

Any advice?

Hi,

When VM console opened in vSphere Client, mouse is really lagging even after VMware Tools being installed, keyboard input lags a little bit, is there a solution to this?

Thanks,

William

Hi.

Instead of hijacking other one's thread having the same problem I decided to start a new thread, so sorry for double posting.

After promoting a new DC and demoting the old one we have the problem that VCenter 5.1a no longer starts.

Taking a look at the imsTrace.log file of SSOServer we see the following line:

Caused by: javax.resource.spi.ResourceAdapterInternalException: Unable to create managed connection olddc.ourdomain.com:3268

As we can see SSO still tries to contact the old dc now beeing a simple member server instead of the new one - the question is why?

We checked health of AD by running DCDIAG and BPA both not seeing any problems. Additionally we checked DNS by hand to ensure that no SRV or any other records are present which reference the old DC. Also all other AD dependent services like Exchange, SharePoint, DFS run without issue and do not indicate any problems.

We also found the krb5.conf file of SSO which still references the old DC by the following entry:

[realms]
OURDOMAIN.COM = {
    kdc = olddc.ourdomain.com
    default_domain = OURDOMAIN.COM
}

However changing that entry does not solve the problem because after a short period this entry is replaced automagically by ??? - that's the question.

Mybe someon else has some ideas what to check next.

Cheers.