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

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

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

Vom 07.03.2017 bis zum 08.03.2017 wurden 32 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 08.03.2017 vom Typ: Troubleshooting
Titel: Unable to power on virtual machine enabled with virtual graphic processing unit (vGPU)

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Logging in to tenant fails after adding authenticated proxy config in VAMI in vRealize Automation 7.x

Am 07.03.2017 vom Typ: How to
Titel: Cloning and converting virtual machine disks with vmkfstools

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Virtual machines residing on NFS storage become unresponsive during a snapshot removal operation

Am 07.03.2017 vom Typ: Troubleshooting
Titel: vCenter Server Appliance (VCSA), vSphere Data Protection (VDP) Appliance or vSphere Management Assistant (vMA) has no network connection after re-registering, cloning, or restoring from backup

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Inconsistent datastore labels in cluster

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Unable to release the acquired trigger and/or clone task stuck in queued state in VMware Horizon DaaS

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Applying a branding to the Enterprise Center

Am 07.03.2017 vom Typ: Troubleshooting
Titel: VMs running on ESXi 5.5 with vShield endpoint activated fails during snapshot operations

Am 07.03.2017 vom Typ: Informational
Titel: Running modify install in the VMware vCenter Site Recovery Manager on Windows server 2012 fails with the error: Setup requires User Access Control (UAC) to be disabled while changing the existing installation

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Backup and Restore Overview for the vCenter Server 6.x

Am 07.03.2017 vom Typ: How to
Titel: Running a manual integrity check in VMware vSphere Data Protection (VDP)

Am 07.03.2017 vom Typ: Troubleshooting
Titel: „Conflicting VMFSdatastores“ error in vCenter Server 6.0

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Configuration options related to event syslog messages

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Adding a Secondary NSX Manager to the Primary NSX Manager fails

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error: Type ‚com.vmware.vim.binding.vim.dvs.PortConnection‘ not found

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Migrate Auto Deploy service from one vCenter Server instance on Windows to another

Am 07.03.2017 vom Typ: How to, Troubleshooting
Titel: Migrating VMFS 5 datastore to VMFS 6 datastore

Am 07.03.2017 vom Typ: Troubleshooting
Titel: ESXi host fails with intermittent NMI PSOD on HP ProLiant Gen8 servers

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Communication timeout when viewing license groups in vRealize Operations Manager 6.x

Am 07.03.2017 vom Typ: Troubleshooting
Titel: How to convert Active Directory users to VMware Identity Manager users in vRealize Log Insight 4.3

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Horizon DaaS desktop deployment times out at 90%

Am 07.03.2017 vom Typ: Troubleshooting
Titel: FTP server or network issues can cause a backup or restore operation to fail

Am 07.03.2017 vom Typ: Informational
Titel: Important information about the new ESXi 6.5 USB driver vmkusb, and the legacy USB drivers

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Email notifications are not being sent to group ID in vRA

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Backup to SFTP server fails in NSX-V 6.3.x

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Unable to increase the screen resolution in a Workstation virtual machine

Am 07.03.2017 vom Typ: How to
Titel: Using Windows network settings with Horizon FLEX virtual machines

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Unable to calculate the placement for the VM when DRS is disabled for this cluster

Am 07.03.2017 vom Typ: How to
Titel: Modifying Cloud Pod Architecture home site behavior

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Tenant administrator loses permissions to manage items under Directories Management in vRealize Automation 7.x

Am 07.03.2017 vom Typ: Troubleshooting
Titel: Restarting the View Agent service on a launched desktop causes the desktop status to change to Invalid IP address

Ausführliche Auflistung:

Titel: Unable to power on virtual machine enabled with virtual graphic processing unit (vGPU)

Knowledgebase Nr: 2126577

Kategorie: Troubleshooting

Aktualisiert: 08.03.2017

Für Produkte: VMware ESXi 6.0.x, VMware Horizon 6 version 6.1.x

Link zum Artikel: 2126577

Beschreibung:
Virtual machine fails to power on when virtual graphic processing unit (vGPU) is enabled. In the vSphere console, you see this error:“The amount of graphics resource available in the parent resource pool is insufficient for the operation. An error was received from the ESX host while powering on VM vm-name. Failed to start the virtual machine. Module DevicePowerOn power on failed. Could not initialize plugin „“ for vGPU ‚grid_k120q‘. vGPU ‚grid_k120q‘ is not recognized.“
… Für weitere Details den Link zum Artikel anklicken

Titel: Logging in to tenant fails after adding authenticated proxy config in VAMI in vRealize Automation 7.x

Knowledgebase Nr: 2144067

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vRealize Automation 7.0.x, VMware vRealize Automation 7.1.x, VMware vRealize Automation 7.2.x

Link zum Artikel: 2144067

Beschreibung:
Logging in to a tenant fails after adding authenticated proxy config in VAMI When using the vsphere.local, the login page comes up. Although no local users have access to the tenant so they are unable to log on On the Tenant Login page, when trying to use their login domain or the default tenant, you see the error similar to:Error Unable to get metadata In the /storage/log/vmware/horizon/connector.log file of the VMware vRealize Automation 7.x appliance, you see entries similar to:2016-02-05…
… Für weitere Details den Link zum Artikel anklicken

Titel: Cloning and converting virtual machine disks with vmkfstools

Knowledgebase Nr: 1028042

Kategorie: How to

Aktualisiert: 07.03.2017

Für Produkte: 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, VMware vSphere CLI 4.0, VMware vSphere CLI 5.0, VMware vSphere Management Assistant 4.0, VMware vSphere Management Assistant 5.0, VMware vSphere Management Assistant 5.1

Link zum Artikel: 1028042

Beschreibung:
This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another.
… Für weitere Details den Link zum Artikel anklicken

Titel: Virtual machines residing on NFS storage become unresponsive during a snapshot removal operation

Knowledgebase Nr: 2010953

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware ESX 4.0.x, VMware ESX 4.1.x, 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

Link zum Artikel: 2010953

Beschreibung:
When using NFSv3 to mount NFS datastores, and a VADP-enabled backup solution, such as VMware Data Recovery, that uses the hot-add method, you experience these symptoms: During a snapshot creation or removal operation, virtual machines residing on NFS storage become unresponsive. When removing snapshots after backing up a virtual machine residing on an NFS datastore using a backup application, the virtual machine becomes unresponsive for approximately 30 seconds. Removing snapshots after…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Server Appliance (VCSA), vSphere Data Protection (VDP) Appliance or vSphere Management Assistant (vMA) has no network connection after re-registering, cloning, or restoring from backup

Knowledgebase Nr: 2012451

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vCenter Server Appliance 5.0.x, VMware vCenter Server Appliance 5.1.x, VMware vCenter Server Appliance 5.5.x, VMware vCenter Server Appliance 6.0.x, VMware vSphere Data Protection 5.1.x, VMware vSphere Management Assistant 5.0, VMware vSphere Management Assistant 5.1, VMware vSphere Management Assistant 5.5

Link zum Artikel: 2012451

Beschreibung:
After unregistering or registering the vCenter Server Appliance, vSphere Data Protection appliance or the vSphere Management Assistant (vMA) and selecting I copied it, the Appliance is unable to set an IP address. After restoring the vCenter Server Appliance, vSphere Data Protection appliance or the vMA from backup or cloning the appliance fails set an IP address. When powering on the Appliance you see errors on the console:Waiting for mandatory devices: eth0 __NSC__29 28 27 26 25 24 23 22…
… Für weitere Details den Link zum Artikel anklicken

Titel: Inconsistent datastore labels in cluster

Knowledgebase Nr: 1002681

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware ESX 3.5.x, VMware ESXi 3.5.x Embedded, VMware ESXi 3.5.x Installable, VMware ESXi 6.0.x, VMware VirtualCenter 2.5.x

Link zum Artikel: 1002681

Beschreibung:
The datastore names appear with extra parenthesis in some ESX hosts sharing the same storage. For example, if datastore-volume is the datastore name, in hosts with this issue the name appears as datastore-volume(1) The storage appears same when viewed through the Virtual Infrastructure Client, either when connecting directly to host or through VirtualCenter. This issue is only seen in the Service Console, the performance of the virtual machines are not affected and the paths are consistent…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to release the acquired trigger and/or clone task stuck in queued state in VMware Horizon DaaS

Knowledgebase Nr: 2100111

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Link zum Artikel: 2100111

Beschreibung:
Cannot release acquired trigger and/or clone task stuck in queued state. In the VMware Horizon DaaS tenant log, you see entries similar to: 2011-04-26 06:50:52,488 ERROR [org.quartz.core.ErrorLogger]-[dtScheduler_QuartzSchedulerThread] An error occured while releasing trigger ‚DEFAULT.queuedTaskSchedulerSimpleTrigger’org.quartz.JobPersistenceException: Couldn’t release acquired trigger: ERROR: could not read block 2 of relation 1663/16386/16859: read only 0 of 8192 bytes [See nested…
… Für weitere Details den Link zum Artikel anklicken

Titel: Applying a branding to the Enterprise Center

Knowledgebase Nr: 2100193

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Link
zum Artikel: 2100193

Beschreibung:
This article provides steps to apply logo and/or colors to the admin portal and to customize the Enterprise Center for company.   Note: This article is applicable to the following products: VMware Horizon DaaS Bundle (VDI/RDSH Edition) VMware Horizon Air Cloud-Hosted VMware
Horizon DaaS On Premise Platform

Für weitere Details den Link zum Artikel anklicken

Titel: VMs running on ESXi 5.5 with vShield endpoint activated fails during snapshot operations

Knowledgebase Nr: 2095445

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 5.5.x, VMware vCloud Networking and Security 5.5.x

Link zum Artikel: 2095445

Beschreibung:
Virtual machines become unresponsive after snapshot operations (creation and consolidation). vShield endpoint drivers like vnetflt, vsepflt are used
within the virtual machine. The virtual machines are
running on ESXi 5.5. Depending on the CPU count the virtual machine can still be pingable. In the vmware.log file, located in the virtual machine directory, you see entries similar to:yyyy-mm-ddT17:06:22.229Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: Done with…
… Für weitere Details den Link zum Artikel anklicken

Titel: Running modify install in the VMware vCenter Site Recovery Manager on Windows server 2012 fails with the error: Setup requires User Access Control (UAC) to be disabled while changing the existing installation

Knowledgebase Nr: 2097033

Kategorie:
Informational

Aktualisiert: 07.03.2017

Für Produkte: VMware vCenter Site Recovery
Manager 5.8.x, VMware vCenter Site Recovery Manager 6.0.x

Link zum Artikel: 2097033

Beschreibung:
Running modify install in the VMware vCenter Site Recovery Manager 5.8 on Windows Server 2012 fails. You see the error:Setup requires User Access Control (UAC) to be disabled while changing the existing installationNote: UAC is disabled in Control panel > User accounts > Change User Account Control settings.
… Für weitere Details den Link zum Artikel anklicken

Titel: Backup and Restore Overview for the vCenter Server 6.x

Knowledgebase Nr: 2149237

Aktualisiert: 07.03.2017

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

Link zum Artikel: 2149237

Beschreibung:
This article provides an overview of Backup and Restore options available for the vCenter Server 6.x
… Für weitere
Details den Link zum Artikel anklicken

Titel: Running a manual integrity check in VMware vSphere Data Protection (VDP)

Knowledgebase Nr: 2067701

Kategorie: How to

Aktualisiert: 07.03.2017

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

Link zum Artikel: 2067701

Beschreibung:
The purpose of this article is to guide an advanced user through a manual integrity
check. This process should not be taken by those who do not understand the commands being preformed. This commands are taken care of by vSphere Data Protection (VDP) automatically.
… Für weitere Details den Link zum Artikel anklicken

Titel: „Conflicting VMFSdatastores“ error in vCenter Server 6.0

Knowledgebase Nr: 2148065

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

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

Link zum Artikel: 2148065

Beschreibung:
When upgrading ESXi from version 5.5 to 6.0, you experience these symptoms: ESXi host disconnects from vCenter Server. Unable to reconnect
ESXi host to vCenter Server. Removing the disconnected ESXi host from Cluster and trying to add it back to the same Cluster fails with the error:Conflicting VMFSdatastores vCenter Server allows the ESXi host to be added to another Cluster or directly to Datacenter, however removing and readding the peer host from the previously affected Cluster to newly…
… Für weitere Details den Link zum
Artikel anklicken

Titel: Configuration options related to event syslog messages

Knowledgebase Nr: 2147620

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 6.5.x

Link
zum Artikel: 2147620

Beschreibung:
This KB article provides information about the configuration options available when you enable the streaming of vCenter Server event syslog messages to a remote syslog server. By default, vCenter Server Appliance streams syslog messages to a local syslog server. You can also enable streaming of syslog
messages to a remote server. To avoid running out of space, vCenter Server does not store events in a file on the local syslog server.  You can use the following parameters to configure the…
… Für weitere Details den Link zum Artikel anklicken

Titel: Adding a Secondary NSX Manager to the Primary NSX Manager fails

Knowledgebase Nr:
2145937

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x

Link zum Artikel: 2145937

Beschreibung:
Unable to add Secondary NSX Manager to Primary NSX manager. After decommission of Secondary NSX Manager, Primary NSX Manager still
shows synchronization issues with the decommissioned NSX Manager.Changing VXLAN port of new secondary NSX Manager from default to another port value fails.
… Für weitere Details den Link zum Artikel anklicken

Titel: Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error:
Type ‚com.vmware.vim.binding.vim.dvs.PortConnection‘ not found

Knowledgebase Nr: 2145686

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vSphere Data Protection 6.1.x

Link zum Artikel: 2145686

Beschreibung:
When VMware vSphere Data Protection (VDP) 6.1.2 appliance is connected to a vSphere
distributed switch in VMware vCenter Server 5.5 or 6.0, you experience these symptoms: Deploying the VDP 6.1.2 plug-in fails. Cannot connect to the VDP appliance. In the virgo logs of the vSphere client, you see entries similar to:[ERROR] http-bio-9443-exec-9 Endpoint.AMF Cannot create class of type ‚com.vmware.vim.binding.vim.dvs.PortConnection‘.flex.messaging.MessageException: Cannot create class of type…
… Für weitere Details den Link zum Artikel anklicken

Titel: Migrate Auto Deploy service from one vCenter Server instance on Windows to another

Knowledgebase Nr: 2147636

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2147636

Beschreibung:
When you try to migrate а vCenter Single Sign-On 5.5 instance on Windows to an External Platform Services Controller 6.5 appliance, if Auto Deploy is running on the vCenter Single Sign-On 5.5 instance, you need to first migrate the Auto Deploy from that instance and then continue with the migration steps in Migrating vCenter Server for Windows to vCenter Server Appliance.
… Für weitere Details den Link zum Artikel anklicken

Titel: Migrating VMFS 5 datastore to VMFS 6 datastore

Knowledgebase Nr: 2147824

Kategorie: How to, Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 2147824

Beschreibung:
This article provides information on migrating existing VMFS 5 datastore to VMFS 6 datastore. VMFS 6 is the new filesystem of vSphere 6.5. The new filesystem supports 512e advanced format drives and is 4098 sector (4K) aligned. It also supports automatic UNMAP, which asynchronously tracks freed blocks and sends UNMAPs to backend storage in background. VMFS 5 and VMFS 6 can coexist. However, due to the changes done in VMFS 6 metadata structures to make it 4K aligned, you cannot inline/offline…
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host fails with intermittent NMI PSOD on HP ProLiant Gen8 servers

Knowledgebase Nr: 2149043

Aktualisiert: 07.03.2017

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

Link zum Artikel: 2149043

Beschreibung:
ESXi hosts running 5.5 p10, 6.0 p04, 6.0 U3, or 6.5 may fail with a purple diagnostic screen caused by non-maskable-interrupts (NMI) on HPE ProLiant Gen8 Servers.
… Für weitere Details den Link zum Artikel anklicken

Titel: Communication timeout when viewing license groups in vRealize Operations Manager 6.x

Knowledgebase Nr: 2147543

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vRealize Operations Manager 6.1.x, VMware vRealize Operations Manager 6.2.x, VMware vRealize Operations Manager 6.3.x, VMware vRealize Operations Manager 6.4.x

Link zum Artikel: 2147543

Beschreibung:
When you launch License Groups in vRealize Operations Manager 6.x, the page takes long time to load. You see the error message similar to:Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually.“ After clicking on OK you see the status message „No license groups available“
… Für weitere Details den Link zum Artikel anklicken

Titel: How to convert Active Directory users to VMware Identity Manager users in vRealize Log Insight 4.3

Knowledgebase Nr: 2148976

Aktualisiert: 07.03.2017

Link zum Artikel: 2148976

Beschreibung:
You must meet these conditions: You have enabled the vRealize Log Insight 4.3(vRLI) Active Directory (AD) integration features. You have enabled the vRealize Log Insight VMware Identify Manager (vIDM) integration features. Your VMware Identity Manager instance integrates with the same AD instance that is used by vRealize Log Insight with the AD integration feature.Note: Users may have different Extracted Fields, Saved Queries, Dashboards, etc depending on the method they choose to log in…
… Für weitere Details den Link zum Artikel anklicken

Titel: Horizon DaaS desktop deployment times out at 90%

Knowledgebase Nr: 2148893

Aktualisiert: 07.03.2017

Für Produkte: VMware Horizon DaaS 6.1.x, VMware Horizon DaaS Bundle (VDI/RDSH Edition) 6.1.x, VMware Horizon DaaS On Premise Platform 6.1.x

Link zum Artikel: 2148893

Beschreibung:
Horizon DaaS desktops time out at 90% during the deployment process. The desktops fail to join the domain. In the DaaS agent log, you see entries similar to: Failed to retrieve VMID, VMID is empty
… Für weitere Details den Link zum Artikel anklicken

Titel: FTP server or network issues can cause a backup or restore operation to fail

Knowledgebase Nr: 2147597

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2147597

Beschreibung:
Backup and restore operations tolerate transient network and server failure. However, sustained connectivity issues, or insufficient storage can cause the operation to fail.
… Für weitere Details den Link zum Artikel anklicken

Titel: Important information about the new ESXi 6.5 USB driver vmkusb, and the legacy USB drivers

Knowledgebase Nr: 2147650

Kategorie: Informational

Aktualisiert: 07.03.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2147650

Beschreibung:
In ESXi 6.5, the legacy USB drivers, including xhci, ehci-hcd, usb-uhci, usb, usb-storage, and so on, are replaced with a single USB driver named vmkusb. The vmkusb driver is loaded by default and it is applied to all the USB Host Controllers (XHCI/EHCI/UHCI/OHCI), USB Keyboard, Mass Storage, and supported USB NIC devices connected to the host.
… Für weitere Details den Link zum Artikel anklicken

Titel: Email notifications are not being sent to group ID in vRA

Knowledgebase Nr: 2149191

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vRealize Automation 6.2.x, VMware vRealize Automation 7.0.x, VMware vRealize Automation 7.1.x, VMware vRealize Automation 7.2.x

Link zum Artikel: 2149191

Beschreibung:
Email notifications are not being sent to group ID in vRealize Automation.
… Für weitere Details den Link zum Artikel anklicken

Titel: Backup to SFTP server fails in NSX-V 6.3.x

Knowledgebase Nr: 2149282

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware NSX for vSphere 6.3.x

Link zum Artikel: 2149282

Beschreibung:
In an NSX for vSphere 6.3.x environment, you experience these symptoms:NSX Backup to FTP failsYou see the error:unable to connect to server x.x.x.x at 22. Either server details are invalid or invalid credentials are presented (permission denied).
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to increase the screen resolution in a Workstation virtual machine

Knowledgebase Nr: 2146029

Aktualisiert: 07.03.2017

Für Produkte: VMware Workstation 11.x (for Windows)

Link zum Artikel: 2146029

Beschreibung:
Keine Beschreibung verfügbar.
… Für weitere Details den Link zum Artikel anklicken

Titel: Using Windows network settings with Horizon FLEX virtual machines

Knowledgebase Nr: 2146937

Kategorie: How to

Aktualisiert: 07.03.2017

Link zum Artikel: 2146937

Beschreibung:
This article provide steps to use Microsoft Windows network settings with Horizon FLEX virtual machines. Horizon FLEX allows companies to control and manage virtual machines. The Horizon FLEX security policies are primarily for managing the virtual ports and controlling the flow of data in and out of the virtual desktop container such as, blocking copy/paste, drag and drop, and USB device sharing. However, you may also want to limit your FLEX virtual machines to specified websites or limited…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to calculate the placement for the VM when DRS is disabled for this cluster

Knowledgebase Nr: 2148906

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware Site Recovery Manager 6.1.x

Link zum Artikel: 2148906

Beschreibung:
Calculating the placement for the virtual machine fails when DRS is disabled for this cluster. Failed to x-vC motion a VM while running the SRM recovery Plan with vPlex.
… Für weitere Details den Link zum Artikel anklicken

Titel: Modifying Cloud Pod Architecture home site behavior

Knowledgebase Nr: 2140012

Kategorie: How to

Aktualisiert: 07.03.2017

Für Produkte: VMware Horizon 7 version 7.0.x

Link zum Artikel: 2140012

Beschreibung:
In a Cloud Pod Architecture environment, a home site is the relationship between a user or group and a Cloud Pod Architecture site. Home site behavior in Horizon 7 version 7 is different than home site behavior in Horizon 6 version 6.x. Horizon 7 version 7 home site behavior: When a user who has a home site requests a desktop or application, View begins searching for desktops and applications on the user’s home site. If the user’s home site is unavailable or does not have resources to satisfy…
… Für weitere Details den Link zum Artikel anklicken

Titel: Tenant administrator loses permissions to manage items under Directories Management in vRealize Automation 7.x

Knowledgebase Nr: 2143798

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware vRealize Automation 7.0.x, VMware vRealize Automation 7.1.x, VMware vRealize Automation 7.2.x

Link zum Artikel: 2143798

Beschreibung:
When you remove directory containing a tenant administrator and add back the directory to vRealize Automation, you experience these symptoms: Tenant administrator in that directory loses permissions to manage items in the Directories Management. You see the error:User is not authorized to perform the task
… Für weitere Details den Link zum Artikel anklicken

Titel: Restarting the View Agent service on a launched desktop causes the desktop status to change to Invalid IP address

Knowledgebase Nr: 2144585

Kategorie: Troubleshooting

Aktualisiert: 07.03.2017

Für Produkte: VMware Horizon 7 version 7.0.x

Link zum Artikel: 2144585

Beschreibung:
If you restart the View Agent service on a launched desktop, the desktop status changes to „Invalid IP address“ in View Administrator.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-03-08T10:41:29+00:00März 8th, 2017|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