23.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

//23.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

23.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

Vom 22.12.2016 bis zum 23.12.2016 wurden 18 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 22.12.2016 vom Typ: How to, Staff Picks, Video
Titel: How to upgrade license keys in My VMware

Am 22.12.2016 vom Typ: Informational, Staff Picks
Titel: How to view and update Support Requests in My VMware

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Cannot remount a datastore after an unplanned permanent device loss (PDL)

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Site Recovery Manager (SRM) 5.0.3 Test Failover fails to auto-mount the datastore

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Connecting the vSphere Data Protection appliance to vCenter Server fails with the error: No space left on device

Am 22.12.2016 vom Typ: How to
Titel: Changing an ESXi/ESX host root password

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Creating a quiesced snapshot of a Windows 2008 virtual machine fails with the error: Snapshot 0 failed: Failed to quiesce the virtual machine

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Error „Failed to add user: cm to group: cis“ while installing Platform Services Controller (PSC) Appliance 6.5

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Container related errors occurs after restarting one or more clustered vRA nodes

Am 22.12.2016 vom Typ: Troubleshooting
Titel: „The user associated with the DSN has insufficient privileges“ when upgrading from vCenter Server 5.x to 6.x

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Disabling VSS quiesced application based snapshots in virtual machine

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Single Source Information for Affected Products of VMware Security Advisories

Am 22.12.2016 vom Typ: Troubleshooting
Titel: vCenter SRM 5.0 Replication status shows as not active after configuration has completed successfully

Am 22.12.2016 vom Typ: Troubleshooting
Titel: VDDK crashes while trying to open disk using VixDiskLib_OpenEx

Am 22.12.2016 vom Typ: Troubleshooting
Titel: How to file a Proactive Support Request in MyVMware

Am 22.12.2016 vom Typ: Troubleshooting
Titel: Detect and Update Duplicate Names of Distributed Virtual Switches and Distributed Virtual Portgroups before Upgrading vCenter Server

Am 22.12.2016 vom Typ: Informational
Titel: VIO Admin role is global in scope after it is assigned

Am 22.12.2016 vom Typ: How to
Titel: Enabling the config option vmxnet3FlapThrottleRate in a virtual machine

Ausführliche Auflistung:

Titel: How to upgrade license keys in My VMware

Knowledgebase Nr: 2006974

Kategorie: How to, Staff Picks, Video

Aktualisiert: 22.12.2016

Link zum Artikel: 2006974

Beschreibung:
A product version upgrade is applicable when a new version of the same product is available. To upgrade a product to the most current version, your Support and Subscription contract must be current and active when the new product version is released. While under contract, there is no cost associated with a version upgrade. When a new version of a product becomes available, you will receive an alert that you are entitled to the new version of your current product. If you do not receive an…
… Für weitere Details den Link zum Artikel anklicken

Titel: How to view and update Support Requests in My VMware

Knowledgebase Nr: 2007048

Kategorie: Informational, Staff Picks

Aktualisiert: 22.12.2016

Link zum Artikel: 2007048

Beschreibung:
Viewing Support Request history The Support Request History page is available to Super Users, Procurement Contacts, Administrators, or users with View Support Requests permissions for the account. For more information about permissions, see Understanding user permissions in My VMware (2006977) If you have the correct permissions, log in to My VMware and click Support > Support Request History. You can view all open and closed Support Requests and these details: Support Request number …
… Für weitere Details den Link zum Artikel anklicken

Titel: Cannot remount a datastore after an unplanned permanent device loss (PDL)

Knowledgebase Nr: 2014155

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2014155

Beschreibung:
After a storage device has unexpectedly unpresented from the storage array, you are unable to mount it again. This issue occurs when there was a running virtual machine when the storage device went offline. An ESXi 5.x host cannot mount the storage after the LUN is online again. In the vmkernel.log file, you see entries similar to:cpu36:5590)Vol3: 1665: Error refreshing FD resMeta: Device is permanently unavailablecpu34:5590)VC: 1449: Device rescan time 165 msec (total number of devices…
… Für weitere Details den Link zum Artikel anklicken

Titel: Site Recovery Manager (SRM) 5.0.3 Test Failover fails to auto-mount the datastore

Knowledgebase Nr: 2074608

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware vCenter Site Recovery Manager 5.0.x

Link zum Artikel: 2074608

Beschreibung:
Test Failover fails to auto-mount the datastore on ESXi hosts Rescan after the failed Test failover mounts the volume on ESXi hosts Test Failover may work for the first time after the host on the DR site is rebooted and may work consecutively. When performing Test Failover, you see the error:“Error – Failed to recover datastore ‚DatastoreName‘. VMFS volume residing on recovered devices „DeviceNumber“ and expected to be auto-mounted during HBA rescan cannot be found“
… Für weitere Details den Link zum Artikel anklicken

Titel: Connecting the vSphere Data Protection appliance to vCenter Server fails with the error: No space left on device

Knowledgebase Nr: 2042185

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware vSphere Data Protection 5.1.x, VMware vSphere Data Protection 5.5.x, VMware vSphere Data Protection 6.0.x

Link zum Artikel: 2042185

Beschreibung:
vSphere Data Protection (VDP) appliance fails to connect to vCenter Server. Manually starting the dpnctl services fails. When you reboot the VDP appliance, you see the error:No space left on device In the /usr/local/avamar/var/vdr/server_logs/vdr-server.log file, you see entries similar to: 2012-12-21 18:13:00,965 WARN [Timer_vc]-vi.VCenterEventProcessor: resetVIAccess failed to set read-timeout java.rmi.RemoteException – VI SDK invoke exception:java.net.SocketException: Network is…
… Für weitere Details den Link zum Artikel anklicken

Titel: Changing an ESXi/ESX host root password

Knowledgebase Nr: 1004659

Kategorie: How to

Aktualisiert: 22.12.2016

Für Produkte: VMware ESX 2.5.x, VMware ESX 3.0.x, VMware ESX 3.5.x, VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 3.5.x Embedded, VMware ESXi 3.5.x Installable, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 1004659

Beschreibung:
For security reasons, it may be necessary to change the password for the root user on an ESXi/ESX host after installation. This article provides steps to change the root password.
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating a quiesced snapshot of a Windows 2008 virtual machine fails with the error: Snapshot 0 failed: Failed to quiesce the virtual machine

Knowledgebase Nr: 2015181

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware ESX 4.1.x, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2015181

Beschreibung:
Cannot create a quiesced snapshot of a Windows 2008 virtual machine. Creating a quiesced snapshot of a Windows 2008 virtual machine fails. In the vmware.log file of the affected virtual machine, you see entries like this:XXXX-03-08T04:10:09.790Z| vmx| SnapshotVMXTakeSnapshotComplete done with snapshot ‚test4‘: 0XXXX-03-08T04:10:09.790Z| vmx| SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine. (40).XXXX-07-01T15:30:43.244Z| vmx| ToolsBackup: not enough…
… Für weitere Details den Link zum Artikel anklicken

Titel: Error „Failed to add user: cm to group: cis“ while installing Platform Services Controller (PSC) Appliance 6.5

Knowledgebase Nr: 2148354

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2148354

Beschreibung:
Installing PSC Appliance 6.5 onto a newly created ESXi Server, the installation may fail with the following error in stage 2 section during PSC setup. If the setup fails during Component Manager’s security configuration, following error follows the above. An error occurred while performing security operation: ‚Failed to add user: cm to group: cis‘ Could not configure the Component Manager security settings. Error ‚Services might not be working as expected‘ In the /var/log/messages of the …
… Für weitere Details den Link zum Artikel anklicken

Titel: Container related errors occurs after restarting one or more clustered vRA nodes

Knowledgebase Nr: 2148212

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Für Produkte: VMware vRealize Automation 7.2.x

Link zum Artikel: 2148212

Beschreibung:
In a vRealize Automation 7.2 clustered environment, when one or more nodes are restarted, the Container service misbehave with symptoms: Inconsistent data collected where some of the Docker host containers are not discovered. It is possible to have situation when on a Docker host there are 10 containers available and in Admiral not all of them are discovered and visible. Randomly failing requests with message similar to:javax.net.ssl.SSLHandshakeException: General SSLEngine problem. …
… Für weitere Details den Link zum Artikel anklicken

Titel: „The user associated with the DSN has insufficient privileges“ when upgrading from vCenter Server 5.x to 6.x

Knowledgebase Nr: 2114754

Aktualisiert: 22.12.2016

Für Produkte: VMware vCenter Server 6.0.x, VMware vCenter Server 6.5.x

Link zum Artikel: 2114754

Beschreibung:
Upgrading the VMware vCenter Server from 5.x to 6.x fails while validating the database. You see the error:Error : The user associated with the DSN has insufficient privileges.Resolution: Provide sufficient privileges for the user by granting the user the following permissions:* VIEW SERVER STATE* VIEW ANY DEFINITION
… Für weitere Details den Link zum Artikel anklicken

Titel: Disabling VSS quiesced application based snapshots in virtual machine

Knowledgebase Nr: 2146204

Aktualisiert: 22.12.2016

Link zum Artikel: 2146204

Beschreibung:
This article provide steps to disable VSS quiesced application based snapshots.
… Für weitere Details den Link zum Artikel anklicken

Titel: Single Source Information for Affected Products of VMware Security Advisories

Knowledgebase Nr: 2078735

Aktualisiert: 22.12.2016

Link zum Artikel: 2078735

Beschreibung:
This article provides a single consolidated list of all Security Advisory details released since 2012. For more information on current Security Advisories, see VMware Security Advisories.
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter SRM 5.0 Replication status shows as not active after configuration has completed successfully

Knowledgebase Nr: 2000213

Kategorie: Troubleshooting

Aktualisiert: 22.12.2016

Link zum Artikel: 2000213

Beschreibung:
VMware vCenter Site Recovery Manager (SRM) 5.0 deployed with vSphere Replication shows a replication status of Not Active. The status is not active even after the configuration of vSphere Replication completes successfully. Initial Replication or Ongoing Replication tasks fail with the warning:No VR servers found for replication The vSphere Replication Management Server (VRMS) on the protected site reports the replication state as Not Active:2012-02-16 01:26:40.794 TRACE…
… Für weitere Details den Link zum Artikel anklicken

Titel: VDDK crashes while trying to open disk using VixDiskLib_OpenEx

Knowledgebase Nr: 2148392

Aktualisiert: 22.12.2016

Link zum Artikel: 2148392

Beschreibung:
VDDK crashes intermittently while trying to open a disk using VixDiskLib_OpenEx. The crash dump reports Stack trace error similar…
… Für weitere Details den Link zum Artikel anklicken

Titel: How to file a Proactive Support Request in MyVMware

Knowledgebase Nr: 2146880

Aktualisiert: 22.12.2016

Link zum Artikel: 2146880

Beschreibung:
This article provides guidelines for filing a Proactive Support Request in MyVMware.
… Für weitere Details den Link zum Artikel anklicken

Titel: Detect and Update Duplicate Names of Distributed Virtual Switches and Distributed Virtual Portgroups before Upgrading vCenter Server

Knowledgebase Nr: 2147547

Aktualisiert: 22.12.2016

Für Produkte: VMware vCenter Server 6.5.x, VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2147547

Beschreibung:
vSphere 6.5 allows only unique names across all Distributed Virtual Switches and Distributed Virtual Portgroups in the same network folder. Earlier versions of vSphere allowed a Distributed Virtual Switch and a Distributed Virtual Portgroup to have the same name. If you attempt to upgrade from a version that allows duplicate names, the upgrade fails.Upgrading a vSphere environment that does not have a unique name will experience these symptoms:Upgrading the vCenter Server will fail with the…
… Für weitere Details den Link zum Artikel anklicken

Titel: VIO Admin role is global in scope after it is assigned

Knowledgebase Nr: 2147534

Kategorie: Informational

Aktualisiert: 22.12.2016

Link zum Artikel: 2147534

Beschreibung:
This article provides information about the impact of granting VIO admin rights on projects. Note: If you assign Admin rights to a user, they can read/edit/change/manage any project.
… Für weitere Details den Link zum Artikel anklicken

Titel: Enabling the config option vmxnet3FlapThrottleRate in a virtual machine

Knowledgebase Nr: 2148348

Kategorie: How to

Aktualisiert: 22.12.2016

Link zum Artikel: 2148348

Beschreibung:
This article provides steps to enable the config option vmxnet3FlapThrottleRate to throttle the number of port enable/disable events from vmxnet3 backend.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2016-12-23T09:13:38+00:00Dezember 23rd, 2016|Knowledgebase|
Um unsere Webseite für Sie optimal zu gestalten und fortlaufend verbessern zu können, verwenden wir Cookies. Durch die weitere Nutzung der Webseite stimmen Sie der Verwendung von Cookies zu. Weitere Informationen zu Cookies erhalten Sie in unserer Datenschutzerklärung. Sie können die Erfassung Ihrer Daten durch Google Analytics verhindern, indem Sie auf folgenden Link klicken. Es wird ein Opt-Out-Cookie gesetzt, der die Erfassung Ihrer Daten bei zukünftigen Besuchen dieser Website verhindert. Weitere Einstellungen Ok

Google Analytics deaktivieren

Verbiete Google Analytics, mich zu verfolgen