Category: The view agent reports that this desktop source is currently logging

How to solve the problem for a user that gets the message "No desktop source assigned for this desktop" when trying to connect to a desktop using the VMware View client. This message occurs when a user "disconnects" from a desktop rather than logging off. Hit the refresh button for the pool and the desktop status should return to "Available" and the user will be able to log in. If you want to prevent this from happening and having to go into the administrator page each time, you can edit the pool properties, and under "Automatically logoff after disconnect" you can choose: Immediately or After a certain amount of time.

These steps where created using VMware View 5. So depending on which version of View you have your layout may be different but you can accomplish the same result. Home Virtualization Virtualization How-tos. VMware View - No desktop source assigned for this desktop. Virtualization VMware. Dec 16, 1 Minute Read. Reply 0. Facebook Twitter Reddit LinkedIn.

the view agent reports that this desktop source is currently logging

Jake Litwin. Track Progress. Earn Credits. Step 2: Double click the pool and select the Inventory tab. Find the VM that is giving the user the error message and select it. Step 4: Prevent this from happening again. Read these nextThe Windows Virtual Desktop Spring update is currently in public preview. This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities.

This lets admins identify issues through a single interface. The service creates activity logs for both user and administrative actions. Each activity log falls under the following categories:.

Connections that don't reach Windows Virtual Desktop won't show up in diagnostics results because the diagnostics role service itself is part of Windows Virtual Desktop. Windows Virtual Desktop connection issues can happen when the user is experiencing network connectivity issues.

Azure Monitor lets you analyze Windows Virtual Desktop data and review virtual machine VM performance counters, all within the same tool. This article will tell you more about how to enable diagnostics for your Windows Virtual Desktop environment. Also, make sure to review the performance counter thresholds for a better understanding of your user experience on the session host. Before you can use Log Analytics, you'll need to create a workspace. To do that, follow the instructions in one of the following two articles:.

After you've created your workspace, follow the instructions in Connect Windows computers to Azure Monitor to get the following information:. Make sure to review permission management for Azure Monitor to enable data access for those who monitor and maintain your Windows Virtual Desktop environment. For more information, see Get started with roles, permissions, and security with Azure Monitor.

You can push diagnostics data from your Windows Virtual Desktop objects into the Log Analytics for your workspace. You can set up this feature right away when you first create your objects. Navigate to the object such as a host pool, app group, or workspace that you want to capture logs and events for. Select Add diagnostic setting in the menu that appears on the right side of the screen.

The options shown in the Diagnostic Settings page will vary depending on what kind of object you're editing. For example, when you're enabling diagnostics for an app group, you'll see options to configure checkpoints, errors, and management. For workspaces, these categories configure a feed to track when users subscribe to the list of apps. To learn more about diagnostic settings see Create diagnostic setting to collect resource logs and metrics in Azure.

Remember to enable diagnostics for each Azure Resource Manager object that you want to monitor.

Recipe of How To fix most VMware View Agent issues

Data will be available for activities after diagnostics has been enabled. It might take a few hours after first set-up. Enter a name for your settings configuration, then select Send to Log Analytics.

The name you use shouldn't have spaces and should conform to Azure naming conventions. As part of the logs, you can select all the options that you want added to your Log Analytics, such as Checkpoint, Error, Management, and so on. Log Analytics gives you the option to stream data to Event Hubs or archive it in a storage account. To learn more about this feature, see Stream Azure monitoring data to an event hub and Archive Azure resource logs to storage account. Once in your workspace, select Logs.

You can filter out your menu list with the Search function. For more detailed information about the tables stored in Azure Monitor Logs, see the Azure Monitor data refence. The following example queries show how the diagnostics feature generates a report for the most frequent activities in your system.

To review common error scenarios that the diagnostics feature can identify for you, see Identify and diagnose issues. Submit and view feedback for. Skip to main content.

the view agent reports that this desktop source is currently logging

Contents Exit focus mode.To give you a better idea of my test environment, I have a master connection server, a replica server and a security server. A typo, Not the most clever thing to do, but I assumed this would be easily solved. All looked fine on first inspection. I could connect to a desktop using the Horizon View Client both over the security server and directly over the Connection Broker bypassing the security server.

Today however I found out that yes, desktops were available for 2 out of 3 test pools but not for the third one! This was odd! It definitely was not the connection between the connection broker and security server, because all worked flawlessly for the other 2 pools. I should actually try to figure this out but I lack the time at the moment. But that is for later. If not for the solid information than for sure because he is a funny and very entertaining presenter!

Save my name, email, and website in this browser for the next time I comment. This site uses Akismet to reduce spam. Learn how your comment data is processed. Horizon View Horizon View 5. Next VMworld Barcelona — Pre-conference post. Leave a Reply Cancel reply Your email address will not be published.View solution.

If you are connecting through the VMWare horizon client (Recommended).

View Solution. Why EE? Courses Ask. Get Access. Log In. Web Dev. We help IT Professionals succeed at work. Last Modified: I have a VDI that will not allow entitled users to connect to. The error in the view client is "The view agent reports that this desktop source is currently disabled. Please contact your system administrator.

The one problem I do see that is a little puzzling is that the DNS name is changing from machine name to something else occasionally when I check on it. However I receive the same error on the view agent even when the proper name is showing.

Any help would be greatly appreciated. Start Free Trial. View Solution Only. Commented: The virtual desktop are registered in your active directory? VDI require active directory and is based on its services. Do you have the view agent installed in the virtual desktop?

The service for the view agent in the virtual desktop has started? However I receive the same error on the view agent Could you explain more detailed this, please. Where do you see this error? Unlock this solution and get a sample of our free trial. Author Commented: It was a workaround and not a solution. Was not able to identify why the unused VDI was using duplicate network information. Get your personalized solution.I had been a part of another in-place upgrade in the past that had almost been disastrous, so having the process down pat this time certainly eased the stress.

One thing our end users did notice though is a rather annoying issue when logging off a View Desktop. The desktop session had already terminated but when opening a console connection to the VM we noticed this message present on the machine. The only thing that had changed desktop wise was the removal of the View Agent for 5.

the view agent reports that this desktop source is currently logging

The worst part of this problem is it was completely random and while it affected some users more then others it almost completely was acting out with no identifiable pattern.

After a few weeks of keeping on top of the issue manually luckily it seems thanks to the tireless efforts of others adding the following registry entries. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. This caused the following issues: Users would be told that the previous session is still logging off when trying to login again.

Forcing a log off via the console or resetting the desktop was the only solution we had The only thing that had changed desktop wise was the removal of the View Agent for 5. Happy days. Share this: Twitter Facebook.

the view agent reports that this desktop source is currently logging

Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Post to Cancel. By continuing to use this website, you agree to their use. To find out more, including how to control cookies, see here: Cookie Policy.We have an old VDI environment which is View 5. The pool is a linked clone with 55 VDI's and we have around 47 or so connected at one time. They are all provisioned up front so around extra at any given time.

When I do a recompose on View 5 it will generally recompose the 7 that aren't being used first and have those fully available before it starts on the used ones. But, when I had my lab zero client, I would log into a VDI, do a recompose, and make sure my lab client got back in. Each time I did this I would get logged out of my lab vdi and immediately it would grab a newly recomposed vdi. I just recomposed in Horizon I have 4 zero clients each in a VDI. I did the recompose and all 4 got booted around the same time.

When they did, when they went to auto log back in via the zero client there were none available so it wasn't seamless. I had to wait a few minutes and then click connect and then it worked. Before this recompose, I tried having the setting "Minimum number of ready provisioned machines during View Composer maintenance operations:" and had that set to Are you on the most recent version of Horizon? I get this message; "The View agent reports that this desktop is currently logging off a previous session.

Please try again later. I don't know if this is a change in the agent or the connection server itself, but I do remember that you could log off a zero client and then grab a new desktop pretty much right away. Yea it's weird. This is still in dev so I have recomposed numerous times trying to figure out how to make this work the best. The one time I did a recompose, it did recompose a ton of VMs and had them availaable before it booted the 4 lab ones I have.

When it booted them there were 4 ready and they got right in. Two other times I tried I had different results. One time I had to wait about 3 minutes before one was ready and I only have 4 lab thin clients in this pool and still had to wait as all of them were being recomposed almost at the same time. And one other time the 4 got booted and happened to log into a non recomposed VDI so they eventually got booted again and then into a newly provisioned.

It would appear that the setting you are referencing does make a difference now.Disk Latency another Case Study.

These issues might happen after a View Agent upgrade or after a unsuccessful uninstallation of View Agent, specially if you are trialling Beta versions of the product. I thought would be good to share the solution. This step-by-step recipe should help you to fix VMware Agent issues in most situations. Skip to comment form. I cannot even uninstall the View agent. From the control panel, it started well to uninstall, then it hit a problem and it rolled back.

There are quite a number of log files, but not sure if uninstall write to the same log files. Much appreciate advice.

Collect Metrics and Logs from Amazon EC2 instances with the CloudWatch Agent

Thanks from Singapore. Wanted to share another potential solution. If the client spins and spins and then times out, remove the network adapter, close the settings, re-open and then re-add it. Worked like a champ — My issue was that after upgrading from Horizon View 5. Thanks for this excellent writeup! These issues might happen after a Vie…. Notify me of follow-up comments by email.

Notify me of new posts by email. Made with by Graphene Themes. Toggle navigation myvirtualcloud. Hope it helps someone! Leave a Reply Cancel reply Your email address will not be published. How to Size Nutanix Capacity… the Unofficial….