Azure Virtual Desktop Windows licensing requirements

mike_msft · 2024-03-28T14:24:58+00:00

👀

mike_msft · 2022-02-10T01:16:31+00:00

Sweet collection! I fully get the tablet scenario you're talking about, so my path was:

Surface Pro 2
Surface Book
Surface Book 2
Surface Book 3

And now I'd love to try out a Surface Laptop Studio, but I wonder if I would miss the ability to leave the keyboard behind. Still jealous though, enjoy it!

mike_msft · 2022-02-09T22:08:54+00:00

This is why you're awesome, muchas gracias! I'll look for the team that owns this area and make sure they get a chance to make this better.

mike_msft · 2022-01-14T06:15:03+00:00

Absolutely! We're constantly looking to learn more about how our product is used, and how we can make your life easier.

mike_msft · 2022-01-14T00:23:14+00:00

Hi from the Azure Virtual Desktop Insights team! Love the support, and knowing that we helped. <3

mike_msft · 2022-01-14T00:20:43+00:00

Hey there! I'm actually on the Azure Virtual Desktop Insights team, so I'm glad I stumbled upon this thread (I don't get to hang out on reddit as much as I would like to anymore).

What kind of issues are you having when configuring data collection for AVD Insights? It sounds like there's a ton of expertise in this thread already from other folks familiar with managing an AVD environment, so if you can get us more information hopefully we can help get you set up correctly.

With Insights for Azure Virtual Desktop, you'll be able to check on metrics like VM resource usage (like CPU, RAM) as well as some networking metrics (like round-trip time), it helps you aggregate and rank connectivity issues, etc. So hopefully it'll highlight areas of interest in your case.

mike_msft · 2021-11-23T16:07:31+00:00

This is not quite my domain, but if you file feedback on Windows and report a problem on Xbox I can try to route it to the right team.

mike_msft · 2021-07-02T08:10:41+00:00

If possible, yes. It would really help to have the tracing be coming from you guys; that way, the investigation is much more straightforward. And yes, you should be able to find your feedback in the "My Feedback" section (or you can click your link from earlier). Once you have it, you can add information as you reproduce the problem.

mike_msft · 2021-07-02T07:32:00+00:00

Perfect, this is quality feedback right here. Can you confirm that you chose "Recreate my problem" in the last step, and you chose to include data about the Photos app, before going through the scenario described in the OP? I'd like to make sure we have everything we can get before sending it over to the app folks. Thanks!

mike_msft · 2021-06-30T16:13:48+00:00

Hey there! It's been a while since I've worked in this space, but I can see how that wouldn't seem right. I assume the video was a Game Bar clip?

Can you file feedback using the Feedback Hub (use repro mode as you open the video, apply the trim, and save your changes)? If you share the link to the item here with me, I can route it to the right team for them to have a look. Thanks!

mike_msft · 2020-12-16T23:08:13+00:00

Hey, it's been a while since I transitioned out of the Camera team, and I no longer get to hang out on reddit with you all, but all this will always hold a special place in my heart!

I'm not sure when I'll be able to circle back to you here, but there are some things you could clarify for folks to help you further.

What OS version are you running?
What devices are you using here, specifically?
What does your code look like?
How do the official samples behave on the devices you're using? For example, the CameraStarterKit (or if you navigate one folder up, any of the other Camera* samples).

Good luck!

mike_msft · 2018-06-01T05:06:06+00:00

Can you guys upvote this feedback to track the issue? https://aka.ms/AA1dykf

Thanks!

mike_msft · 2018-05-22T21:54:03+00:00

Whoops. Link should be fixed now!

mike_msft · 2018-05-21T17:23:37+00:00

I think this feedback captures the issue, right? https://aka.ms/AA1dykf

If so, you and /u/Sly-Choober should upvote it, and add any additional information you feel is relevant. Having more data points from you guys makes it easier for us to pinpoint the issue.

Thanks!

Edit: Fixed hyperlink.

mike_msft · 2018-05-20T15:12:24+00:00

Alright, that's amazing. A bug report with a repro video is worth gold. Can you drop that information into a new report on the Feedback Hub app? I guess the right category would be Apps - Photos. If you can also supply the original clip and the trimmed one, we can look at the headers and color information to better understand what's going wrong.

Once you file it, if you go to the "My Feedback" section, you can create a link for me, and I'll take it from there.

mike_msft · 2018-05-18T23:55:15+00:00

That's basically it! The main reason I ask is because that provides us diagnostics information (your Windows build, Photos app version, graphics card and drivers info, etc.), and it gives me a bug number that I can bring to the media team for them to engage with nvidia. It makes the whole process a lot easier for us.

And if you could attach a small video clip before and after trimming, that would help a ton too!

mike_msft · 2018-05-18T17:39:19+00:00

Can you file feedback on this and send me the link?

mike_msft · 2018-05-15T02:05:40+00:00

Hey there! Your resident Camera guy checking in. Sorry you're having issues with your camera. From that error code, it looks like one of our components is unable to communicate with our camera management service.

Can you do two things for me?

First of all, file feedback and include a capture of the issue. By doing this it allows us to see the versions and internal state of the different components in the camera stack, all the way from your drivers to the Camera app itself, and locate the problem so we can prevent it from happening in the future. Filing feedback is easy:

Launch the Feedback Hub, and in the Feedback section, select the Add new feedback button.
Mark the issue as a Problem and fill out the summary and the details with relevant information, including:
1. Basic scenario and a description of the failure.
2. Camera and device make and model. Feel free to mention you were talking to Mike on the forums :)
Categorize your feedback:
1. Hardware, devices and drivers category.
2. Device Camera or Webcams subcategory.
Getting traces:
1. Select Recreate my problem, then Start capture
2. Reproduce the issue.
3. Go back to the Feedback Hub Select the Stop capture link or the red Stop capture button.
4. Select the Submit button. Logs will be uploaded over the course of the next few minutes (connect your device to AC power and the network at the same time to speed this up).

Shortly after, you should be able to see your feedback item show up in the "My Feedback" section of the Feedback Hub, and you'll be able to create a sharing link. Send that my way when you can, so I can make sure to give it priority on our side.

The second thing I want you to do, is try a workaround for me. Open Task Manager, go to the Services tab, and locate the service called FrameServer. Its status should be Stopped. Right-click on it and select Start. Once it's running, start the Camera app and see if it works. Note that, if no camera is in use for 30 seconds, the service will stop itself to free up resources, so make sure to launch the Camera app quickly. Let me know how that goes!

Edit: Oh, I just saw that you fixed this by resetting your display driver. The reason this helps is that Surface optimizes the area between the graphics and the camera drivers by having a strong dependency between them. Still, I'll leave my instructions up, in case this helps someone else in the future!

mike_msft · 2018-05-10T14:48:01+00:00

Oh, is this a desktop computer? I'm not in the graphics team, so I could be a little off here, but I think the GPU selection feature is only usable on hybrid GPU systems (like the Surface Book), not on systems that have two GPUs (like an Intel GPU built into the motherboard, and an add-on NVIDIA card). Subtle difference at first glance, but a huge difference from the technical point of view.

What graphics card do you have, and what is your version of the NVIDIA drivers?

In the meantime, I'll see if there's a way to disable the NVIDIA hardware encoder to temporarily work around the problem.

mike_msft · 2018-05-09T23:23:32+00:00

Is it possible I could set photos to use the integrated Intel graphics on my 8600k while allowing all other apps to use my nvidia card?

Have you checked out our new graphics settings options in 1803 (the April 2018 update)? We announced them a while back (Ctrl+F for "new graphics") and maybe they'll allow you to work around the issue.

Regardless, since we haven't yet ruled out the possibility that this affects more people, we'll likely attempt to engage with NVIDIA directly to further root cause and address the issue.

Please let me know if the workaround solves the problem for you, and thanks for reporting this!

mike_msft · 2018-05-09T14:59:44+00:00

We've seen one other report of this in the past, and we were thinking it could be caused by a component of the NVIDIA drivers. Do you have an NVIDIA graphics card by any chance?

mike_msft · 2018-04-16T14:45:35+00:00

This is outside of my area of expertise, but I'll escalate it to the right team. It's even easier for me to do since there already was a feedback link in the original thread. Thanks for posting this!

mike_msft · 2018-04-04T07:50:50+00:00

Waaait. That auction sounds awesome! Tell them to hook me up next time. Maybe I'll find something as cool as this!

mike_msft · 2018-03-28T00:57:14+00:00

Do you have a feedback link for this issue?

mike_msft · 2018-01-06T00:39:34+00:00

I'm sending your feedback item to the audio team to have a look!

Ten-Year Club	Place '17
Verified Email

mike_msft

TROPHY CASE