Hello,
vSphere 6.7
Horizon View 7.5.0
Windows 10 Pro 1709
I created a pool "Automated Desktop Pool", "Dedicated", "Full Virtual Machines". VM naming pattern: PC-VDI{n:fixed=2}.
All machines now Available, but why machine name does not match dns name? And why number in machine name does not match number in dns name??
It looks like you've created another pool before in the same subnet.
As a first step, please check whether there are still DNS records registered for the old names in your DNS server(s).
André
DNS server do not have this names.
Neither in the Forward, nor in the Reverse lookup zones? That's indeed strange.
André
This bug not related to the DNS server.
"DNS Name" really is computer Windows name.
Why is it different from VM name?
Have you followed this guide step by step?
Best Practices for Delivering Microsoft Office 365 in VMware Horizon 7 | VMware
We have office 365 locally installed in our gold image. We are on build: Version 1803 (Build 9126.2259). So far no issues with account errors. We do not capture the credentials path you listed with UEM and login is persistent.
Yes I have followed that guide. Are you using Azure SSO or just password syncing?
We use ADFS
We are not using ADFS so that is why that path needs to be captured by UEM.
its not normal behavior , try to delete desktops from the pool and delete DNS records and re-provision again, would this solve the issue ?
Hi
Wondering if anyone has a mouse capture issue with their horizon view client.
I'm running:
Mojave beta 6
Horizon View Client 4.6 (also tried 3.2, 4.01, 4.2, 4.3, 4.4, 4.51, 4.7 black screen, and 4.8 black screen)
I can see the remote end screen, but can't get the mouse to press buttons etc in the screen. As well I get weird mouse jumps to the screen centre.
Any help appreciated.
Thanks
System Preferences > Security & Privacy > Accessibility and make sure VMWare Horizon Client has a tick in the box.
Thanks! worked a charm...
I knew I saw a box come up when I first logged in, but just closed it. It must have been this...more fool me!
Can we increase memory of the linked clone VM if it is a dedicated pool?
Hi,
I am getting this message when trying to publish to an instant clone. Does anyone know where to figure out why this is happening? The image was pushed previously and worked fine. Added a bunch of software, made a clone and tried to push it again.
Image Publish initiated by SchedulePushImage for Pool standard_lab_pool failed for Image [VM=/VDI-Datacenter/vm/Test VMs/goldimage, Snapshot=/Clean Gold Image 2 Base Snap/Fixes_v3, State=PUBLISHING]
Does anyone know what the best practice is for how many clones to keep? My colleague deleted the previous clone before he tried to push this clone.
Thanks!
14.2 Did not fix this.
Thanks for the reply. That is a pity.
In the meantime we have added a scan exception for vmwsci.dll and are monitoring the results. Positive so far.
Let me know, vSphere version, ESXi build number, VMware Tools version, View Agent and View Client version and also Windows 10 build number.
yes, that's possible.
Hi,
We are having issues with Client Drive Redirection on Windows 10 1709. When users log in using the Horizon Client (Blast protocol), they are able to see a mapped drive which maps to the host's c:\users\<username> location. When a user initiates a copy/paste operation from the virtual desktop to the mapped drive, the Copy popup window gets stuck at 0% and when they click "This PC" in File Explorer, nothing shows up in the right pane. Once in a while, they also get a pop saying: \\tsclient\<username> is not accessible. Attempt to access invalid address. This happens for internal and external connection to the VDI. However, once in a while, copy/paste operations do work. When they do the problem above strikes after a couple of copy/paste operations.
This is the VDI setup:
I did notice that this DOES NOT happen in Windows 7. I am trying to migrate users off of Windows 7 but need this CDR problem resolved first. Has anyone ran into this issue? Thanks.
-Rob
