Archive for the ‘Agent’ tag
If you’re running a VMware View proof of concept you might run into an issue which I’ve seen very rarely in the last few years. After a successful installation of all components you’re connecting to a virtual desktop for the first time and everything seems to be fine. You logoff the user and you may login again to your dedicated desktop from a automated pool. But then you spot that you’re getting a new desktop every time you logon to the View Manager. Strange you might think, because you’ve configured a dedicated desktop for the user. In the next step you login to the View Administrator and you check the configuration. It seems to be finde but then you figure out, that you can’t see the session information for a user who’s currently connected to a virtual desktop. I didn’t see this issue for a long time now but today my colleague Kim from the Global Desktop team came to me with it again. I thought it might be worth sharing the information with you so please go on with reading if you’re interested.
As I said, the session information for active sessions to the virtual desktops is not shown in the Session tab, which has the same root cause as the issue with the dedicated desktop described above.
The reason for this is a process which is not running, but needed on the virtual desktop. As you know may know there is a software component called the View Agent, which must run on the virtual desktop in order to connect to it via the View Manager/View Client. The View Agent manages loads of tasks on the virtual desktop, i.e. starts the PCoIP server, controls the USB redirection and also sending information about the current status/user to the broker component. And here is the root cause! The user/session information is managed by a process called wssm.exe which is running in the user’s context. This process will be started every time the operating system starts up, by a registry key called userinit.
When everything is ok, you’ll see the wssm.exe process via the Task Manager on your Windows box, if not, you should check the Windows registry key: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit.
Can you see the wssm.exe here? If not, this is your problem. But don’t worry if it is there and it’s still not working. In that case you should check if each entry is separated from each other by a comma. This issue may occur if you’re using software on the virtual desktop which modifies the userinit key. Sysprep for example could do that.
I’m really surprised that it works, but a guy from France got a Linux VM working with the VMware View Agent. I don’t speak French but what I get from his article is that he used Xrdp in the VM. I guess he used Wine, a Windows emulator for Linux to get the View Agent running. It’s awesome, check his blog. But don’t forget: This is highly unsupported.
Today two new articles for VMware View were created on VMware Knowledge Base which could help you if you have client or agent issues.
Since VMware View does only support Microsoft Active Directory Service as directory service, Novell eDirectory users need another way to get their environment working with the VMware virtual desktop infrastructure. First of all you will definitely need an Active Directory to integrate the View Manager with so that the users can logon and get authenticated. To get the users from the eDirectory in sync with the Active Directory you should use the standard Novell tools.