We changed our pools (names and what not). i have users that have multiple pool assignments but they will only connect to the last desktop. i have tried a hard reset of the client same issue. has anyone seen this before? any help would be appreciated.
Wyse P25 wants to only connect to the last desktop.
Windows 10 Linked clone pool Desktop stuck in Customizing status
I am trying to create Linked clone pool using Windows 10.
Through VC I can see that sysprep Customizing is succeeded, and Desktop have joined the domain too.
But in View Pool, it is showing as Customizing, and after waiting for long, it gets recreated again and same thing happen again.
Just for information, same View, VC and customization is working fine with Windows 7.
Any pointers for this ?
How to fix error " ssl connection was shut down while reading " ?
Hi everyone !
My company use VMware View 5.2 and I was deloyment it .
However, at computer of user. sometimes display " ssl connection was shut down while reading " and if user click on button "OK" the will be disconnect VDI .
So, i have question ! How to fix error "ssl connection was shut down while reading " ?
Thanks !
View 7.8 Client Disconnect message
Any way to configure the full client disconnect message? Sounds foreboding to users the way it is written: "Are you sure you want to disconnect from this desktop. You may lose your work, the desktop will be shutdown in 1440 minutes." Yes, that is our standard force idle disconnect time but we're talking just a disconnect. The older, simpler message of only asking if a user wants to disconnect is better.
I can't find anything in Default Configurations, GPOs to configure that message. Thanks.
Windows 10 v1607 VDI vm3dmp.sys BSOD
Yesterday I was suddenly disconnected from my Windows 10 v1607 VDI and when reconnecting was just seeing a black screen.
After about 1-2 minutes or so I was able to reconnect & noticed it had rebooted prompting me to check Event Log for gems:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xffffe0fe07a00000, 0x0000000000000002, 0x0000000000000000, 0xfffff80ee2d55760). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: bf05cd81-5e7d-4190-93af-dab35bee3049.
The MEMORY.DMP suggests vm3dmp.sys was the faulting module (process: VMBlastW.exe).
Thought's on how best troubleshoot this further?
Environment:
- ESXi 6.5.0, 4564106
- Horizon View 7.2.0 build-5735293
- VM: Windows 10 v1607 without GPU attached (2 vCPUs, 12GB)
- Using Blast
- USB auto connect enabled
- Dual monitor setup with display scaling enabled
- No writable volumes; No AppVolumes
The full details of the analysis are in the file attached to avoid 4 screens of text; happy to paste text if requested.
Te computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xffffe0fe07a00000, 0x0000000000000002, 0x0000000000000000, 0xfffff80ee2d55760). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: bf05cd81-5e7d-4190-93af-dab35bee3049.
Is VMware working to improve agent and tools upgrade process?
Although we have a few separate Horizon environments running anywhere from 7.2 to 7.8, and we have been using this for some time now, there are still portions of Horizon that are unclear. My main complaint has to do with the process one must take in order to upgrade the underlying VMware software [on full clones] based on the information received from:
- the team that originally implemented Horizon 6 and
- the consultant we engaged to implement Horizon 7 and
- VMware support while working through a bug we discovered some time ago.
I'm completely open to the possibility that we're simply ill-informed/misinformed and if that is the case I'd appreciate a kind nudge in the correct direction.
Assuming the below is not that far off base, does VMware have on their roadmap a line item to improve this process?
Whenever a new version of VMware Tools is available, I find process for updating VMware Tools on the VM's rather arduous:
- Uninstall the AppVolumes Agent if applicable
- Reboot
- Uninstall the HorizonAgent
- Reboot
- Uninstall GPU Driver if applicable
- Reboot
- Upgrade VMware Tools
- I've been told by VMware support to actually Uninstall VMware Tools, reboot then install the updated version but I'm open to the possibility that this is only for specific, older, versions of VMware Tools.
- Reboot
- Install GPU Driver if applicable
- I've been told this has to happen before the Horizon Agent because there are 3D components in the agent that need to detect the GPU in order for them to be installed & setup correctly.
- Install updated version of the Horizon Agent
- Reboot
- Install the AppVolumes agent if applicable
If we only need to update the Horizon Agent, it's only slightly less painful:
- Uninstall the AppVolumes Agent if applicable
- Reboot
- Uninstall the Horizon Agent
- Reboot
- Install updated version of the Horizon Agent
- Reboot
- Install AppVolumes Agent if applicable
Window borders missing after running VMware OS Optimization Tool
After running the VMware OS Optimization Tool we see that the dark borders around windows are missing. To explain what i mean, here is a picture of 2 Explorer windows on top of each other.
I have tried to disable a lot of options within the tool, but i can't realy figure out what item is causing this. Does anyone have a clue?
viewdbchk on Horizon 7.3.2
We use viewdbchk every now and again to cleanup pools in Horizon, when the View Admin console is having issues doing such. Just like everyone else. However, since the move to 7.3.2, we can't seem to run it.
According to the release notes there was a change:
- In Horizon 7 version 7.2 or later, the viewDBChk tool will not have access to vCenter or View Composer credentials and will prompt for this information when needed.
This is fine, we know what credentials to use. When we run the command though ("viewdbchk --removeMachine --machineName Xyz --noErrorCheck"), and are prompted for our service account password for vCenter (https://vcenter.fqdn:443/dsk) and for Composer (https://composer.fqdn:18443), when we enter, no characters show not even masked (this might be by design), and when we hit enter to confirm anyway, we are greeted with "ERROR: Cannot get password for user "service_account".
We know the password, we even tested it separately. Anything we can provide within the command differently perhaps?
Thanks in advance.
Best path to migrate vCenter, View Connection, View Composer, VMs for OS upgrade
Hi all,
I'm sure someone has had to do this before and could tell me the caveats when migrating a Horizon VDI environment to new VMs. This will include a SQL Server, View Composer, View Connection, and vCenter (not VCSA). I have read a few and one that I'm thinking about implementing goes in this order: SQL Databases, View Composer, View Connection (in replica mode to existing server), then vCenter.
All hardware will be the same. At some point I'll need to disconnect from the existing vCenter and connect the hosts to the new vCenter server and that is essentially my question is when is the best point to make that switch? If the order mentioned is best then it's obviously at the end but is this truly the best order?
I'm no expert and would appreciate any guidance from someone who has successfully done this.
Linux vmware-view disconnects from desktop after launch.
I am not able to connect to desktop using Linux client. I've tried 4.9, 4.10, 5.0 versions installed from available bundles following previous uninstallation.
Fresh Fedora installation does not help.
Connection from Android tablet works fine - version 4.10.
Did anyone face this issue and knows how to solve it?
Running Fedora 29.
Connection logs show:
2019-05-02 13:46:54.144+02:00: vmware-view 22919| TaskCombiner: SetResult for CdkGetLaunchItemConnectionTask(DONE).
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): CreateMKSInterface: Remote MKS not yet present, queueing CheckForMount
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): Caught child exit with status 0x500, requesting container exit
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): Remote MKS network connection status changed: DISCONNECTED
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): ProcessPollCb: received exit request, shutting down...
2019-05-02 13:47:05.939+02:00: vmware-view 22919| rmksContainer(23089): Killing vmware-remotemks child: 5a35
2019-05-02 13:47:05.942+02:00: vmware-view 22919| rmksContainer(23089) died.
2019-05-02 13:47:05.942+02:00: vmware-view 22919| rmksContainer(23089) exited with status: 5
vmware-mks-2252.log looks interesting:
2019-05-03T08:36:35.924+02:00| main| I125: VDPPLUGIN: pcoip_client: connecting to target
2019-05-03T08:36:35.924+02:00| main| I125: Peer reported input preferences 0x1.
2019-05-03T08:36:35.924+02:00| main| I125: Peer has no preferred mouse mode.
2019-05-03T08:36:35.924+02:00| main| I125: Peer reported input capabilities 0x2.
2019-05-03T08:36:35.924+02:00| main| I125: Peer supports absolute mouse.
2019-05-03T08:36:35.950+02:00| mks| W115: VDPPLUGIN: pcoip_client: disconnect reason code 5: VDPCONNECT_C
ONNECTION_LOST
2019-05-03T08:36:35.950+02:00| mks| I125: MKSRoleMain: Disconnected from server.
2019-05-03T08:36:35.950+02:00| mks| I125: MKSRoleMain: Disconnected from server with error code 5.
Unable to change dpi with dpi synchronization enabled
We are using vmware thin clients, horizon client 4.10.0, agent 7.7.0. Some of our users that can't see well and want a higher dpi. The only way we have found to accomplish this is to disable dpi synchronization and set their dpi on login through a windows gpo.
However, disabling dpi synchronization is problematic because some other users work both on thin client and remotely. When dpi synchroniztaion is disabled their client dpi setting is ignored and their remote dpi is always 100% regardless of client settings.
Display scaling does not fix this, as it only decreases resolution instead of increasing dpi. We have not found a way to match remote dpi to client dpi without dpi synchronization.
Is there any way to either:
*change remote dpi at all when dpi synchronization is enabled, or
*set remote dpi equal to client dpi when dpi synchronization is disabled.
Thanks in advance
How to change Vcenter address in Horizon vdi 6.
Vmware Profile Migration .v2 to .v6
We have been getting errors when we migrate user profiles for v2 profiles to v6 profiles. Do you have to be a Domain Admin in order for this to work. It says successful but the log file looks like the one on .V2 to .v5 (VDI View profile migration) . I wanted to have clarification from vmware as it is not in any documentation.
Thanks
VMware Horizon View 7.4 with Windows 10 LTSB 1607 - Black screen after deployment
We have Horizon View 7.4 on a vSphere 6.5 environment and Windows 10 VDI.
Windows 10 is deployed through MDT, works fine, even when composing a VDI, first start / logon works fine, after a reboot no screen anymore, via vSphere Console black screen with mouse pointer. VMware tools is running, i can do a graceful shutdown / reboot. Also remote registry works, eventviewer, file explorer, services etc etc etc. but no screen. also no screen as an administrator local / rdp does not matter.
It is always after the first "run" of Windows 10, after a reboot it does not work anymore..
Any thoughts?
Monitor and Alert on problem vms and hosts
Currently the environment we have is 6.0.1 build-2088845, apparently we like to walk into hornet nest. However I'm trying to find a way to alert us when we have problem vms or hosts in this environment and coming up short. We have an old version of Solarwinds (SAM) but again need to know what individuals use today to alert them and to stay proactive please.
Administrator account used for QuickPrep does not have sufficient
Hi ALL,
I am facing the issue when i am provisoning linked clones i am getting below error, can some one help to resolve this problem.
Administrator account used for QuickPrep does not have sufficient permissions
what version of view agent is support in 7.0.1
we are running horizon 7.0.1 and have a requirement for virtual printing on a physical PC but don't get the option for virtual printer in view agent 7.4 and below.
I have been told that agent version 7.6 and above offers this which it does but now i am having issues connecting over a session.
Is agent 7.6 supported with horizon 7.0.1?
SSL error on connecting to server
I have a Win10 PC and a Win10 laptop that I use VMware Horizon Client (v4.8) to connect work's VDI server over the past year. Today, on my PC the VMware client is reporting a SSL error when I click to connect to the VDI server (error happens before any auth prompts). However, my laptop doesn't have the issue and is able to connect through ok. Both PC and laptop are on the same home network.
I've had a look at the logs but I don't understand most of it so hoping someone can point out what could be wrong.
Things I have tried on my PC:
- Change SSL confguration to "Do not verify server identity certificates"
- Uninstalled VMware Horizon Client - reboot - reinstall with latest v4.8 installer from vmware.com - reboot
This is the extract from vmware-horizon-viewclient-2018-06-25-160039.txt attached (server name and IP replaced).
I tested connecting to any valid domain name not running vmware infrastructure and appears to get the same SSL error so it just appears the SSL error just a general error if there is no SSL handshake? I can confirm my work's VDI server is working though because as I mentioned I can connect to it from my Win10 laptop fine.
What else can I do?
Browser corruption and firefox xpcom error
Having a issue with my desktops in Horizon View. After 2-3 days of running, users will report that both chrome and firefox no longer work. Chrome will just not launch and firefox will get a "can't load XPCOM" error. If I recompose the desktop it works again for another 2-3 days. The XPCOM error affects every user that logs in to that desktop, the Chrome issue appears to be user specific. We are using UEM and App Volumes. Horizon View version is 7.6, issue happening on Windows 10 1607 and 1709. Hoping someone else has came across this issue and help point us in the right direction. Thanks
-Craig
Windows display scale to vmware display scaling
Since upgrading one of our users client version from v3.5 we have noticed an issue when having the Windows Display Scale set to 125% zoom the VM now has a reduced resolution indicative of the resolution of one with said zoom level, so a 1920x1080 host machine screen would provide a ~1600x750 resolution.
This particular user was using 2 screens, one was 1920x1200 the other was 1920x1080, display scaling from VMware was enabled and was proven so by changing the size of a "large window" and seeing the resolution change. the function of 2 screens is a requirement - I have seen the fix for the surface pro was to adjust the RTAV registry keys for srcWCamFrameWidth and height however I cant see a way to set 2 resolutions for 2 screens.
Client version: 4.7, tested with 4.4 also
Agent version 6.0.1
Any ideas would be appreciated.