• Home
  • Community
  • Solutions
    • Gists
    • GitHub
  • About
    • About the author
    • Legal Disclosure
    • Privacy Statement
  • Contact
Start typing and press
Enter to search
  • RSS Feed
  • GitHub
  • Twitter
Follow
Skip to content

Modern IT – Cloud – Workplace

Enterprise Mobility and the Microsoft Cloud

open search form close search form
  • Home
  • Community
  • Solutions
    • Gists
    • GitHub
  • About
    • About the author
    • Legal Disclosure
    • Privacy Statement
  • Contact
Quick Assist Diagram
By: Oliver Kieselbach March 3, 2020January 3, 2021
Articles, Enterprise Mobility, Intune, Modern Management, PowerShell, Scripting, Security, WindowsElevation, PromptOnSecureDesktop, Quick Assist, QuickAssist, Remote Control, secpol.msc, Secure Desktop, Security Baseline, Teams Screen Sharing, UAC, User Account Control, Windows 10

Quick Assist the built-in Remote Control in Windows 10

Quick Assist application logo

If you are running an environment with a modern management strategy where your clients are highly mobile and managed by cloud services, your built-in direct connection based tools like RDP or Remote Assistance are limited in usability for supporting your devices. In general with the mobile workforce nowadays we can’t rely on solutions needing a direct connection between two devices.

The lesser known built-in Quick Assist from Windows 10 implements a different way of connecting to the remote client. The supporter connects to a Microsoft cloud service by starting Quick Assist and logging in with a Microsoft Account (MSA and AAD accounts supported). Quick Assist will hold a connection to the Microsoft cloud service and the supporter is given a connection code. The user who needs assistance also starts Quick Assist and connects the the same session by specifying the connection code. This way both clients can use outbound connections to the Microsoft cloud service and the cloud service is acting as a broker between both clients. This allows flexible connectivity to remote clients wherever they are. Even behind some firewalls we normally don’t have any issues to successfully build a connection. In fact this is the same approach all the third party vendors like AnyDesk, TeamViewer, BeyondTrust Remote Support (aka Bomgar), or LogMeIn are using with their remote support software products.

Quick Assist connection diagram

That’s great but why should I care about a remote support solution anyway if I have Teams?

That’s a valid point in times where collaboration tools like Microsoft Teams are available and we have screen sharing capabilities where we can give control to someone else:

Microsoft Teams and screen sharing with give control feature

The main issue is the elevation of privilege’s. I guess everyone is familiar with the User Account Control (UAC) in Windows. If you try to elevate a process from a standard user context you will be switched to the so called Secure Desktop, the dimmed desktop in the background is the Secure Desktop which can not easily be circumvented:

UAC dialog with the dimmed Secure Desktop

The Secure Desktop can not be handled by the collaboration tool Microsoft Teams. As soon as the Secure Desktop appears the shared screen looses track of the session and the remote supporter can’t control any UAC dialog:

Microsoft Teams screen sharing and no support for UAC dialogs

Actually this is the same for Quick Assist, as soon as you try to elevate a process as supporter you loose the session and you get a black “pause” screen like this:

Quick Assist black pause screen

Do I have to switch to third party software for elevation support?

It depends on what functionality you need for your support processes. Third party normally has a lot of functionality which is needed in enterprise environments like extensive logging/auditing etc. All third party products normally support also the elevation scenario, but there is a way to accomplish remote support even with the Windows 10 built-in Quick Assist solution. The simple solution here is to deactivate the “Secure Desktop” on your clients:

Registry value for PromptOnSecureDesktop

As soon as this is done, the elevation prompt will be visible in the Quick Assist session and can be controlled and the remote supporter can enter credentials for elevation. Instead of the black pause screen you will see the UAC prompt (without secure desktop):

Microsoft Quick Assist and a visible UAC dialog in standard user context

The downside is that the secure desktop is designed that no one can remote control the UAC dialog and inject something as the dialog is not running on the users interactive desktop. Without the secure desktop the UAC dialog is running like every other Windows dialog on the interactive desktop of the user. This makes the device vulnerable to UAC spoofing attacks. If you and your security department are feeling okay with that fact, you can re-configure the devices and get a working Remote Support solution out of the box from Microsoft built directly into Windows 10 called Quick Assist.

Okay wait but what about Microsoft Teams when I disable the secure desktop? Yes, it would be the logical conclusion that we are able to control the UAC dialog via Teams then also, but that’s not the case. You will see the dialog but you are unable to control it. You can’t enter credentials or click on any of the buttons:

Microsoft Teams screen sharing and UAC dialog

How to reconfigure my devices now?

To deactivate the prompt on the secure desktop, you can easily use a simple PowerShell script provided on my GitHub account and deploy it via Intune to your devices. I used an AAD device group for assignment here:

Intune PowerShell script deployment DisablePromptOnSecureDesktop

When successfully applied you will see it in the Intune portal:

Intune PowerShell script deployment status

The script is very simple and checks if the PromptOnSecureDesktop value is not 0 and will set it accordingly to 0. You can find the script here:

https://github.com/okieselbach/Intune/blob/master/DisablePromptOnSecureDesktop.ps1

You might have configured UAC already with a custom Intune profile or you use the Intune MDM Security Baseline for Windows 10. The baseline will configure the UAC to a more strict default for standard users to deny UAC requests:

MDM security baseline UAC standard user prompt behavior

So, you might need to adjust these policies. You can also implement the same behavior by configuring the Intune profile without using the PowerShell script. As already mentioned and shown above, the Microsoft security recommendation for UAC is not to disable the secure desktop. As security is always a trade off between usability and security, you have to adjust from time to time some settings for your organizational needs. If your user support needs this and the security department is taking that risk, you can move forward with this solution.

This might help if Quick Assist provides you enough functionality to support your processes, or if you not have the budget for an additional remote support tool. But actually there are some remote support tools which are quite affordable and providing way more functionality and don’t require to turn of Secure Desktop, one of the candidates here is AnyDesk.

A last goodie and small side note, there is a keyboard shortcut to open Quick Assist via:

[Ctrl] + [Win] + [Q]

And because Quick Assist is available from the beginning you can call it very early in the process. In the next screenshot I have used the keyboard shortcut during enrollment in the Autopilot user ESP phase (sorry for the german Quick Assist window):

Quick Assist during Enrollment and user ESP phase

I hope this helps if you are looking for a cheap built-in solution to get Quick Assist to work even with elevation and UAC prompts.

Happy supporting of your user base.

UPDATE 2020-04-22:

Many thanks to one of my blog readers (Tomasz) who mentioned this approach in the comments! I will show the approach to disable Secure Desktop during a remote session when you have enabled the local Administrator account or any other additional local admin account on the target device. Meaning you can keep the local admin credential and do not provide them to the user. It gets a little hacky but it can help people in times of WFH to have another way of enabling elevation for remote support, when no management channel else like MDM, GPO, internet-based software management is available.

The solution relies on the fact that the “run as different user” does not show an UAC dialog on secure desktop. I’ll quickly demonstrate the way to disable the UAC with the help of this fact. Hold Shift while right click on PowerShell and choose “Run as different user”:

Run as different user context menu

Now you will get a run as dialog without Secure Desktop:

run as different user dialog

Here you can type in a local admin account or the built-in Administrator account if your devices have it enabled. You will get a PowerShell running in the context of the .\localadmin in my case:

PowerShell running as differnt admin user and secpol.msc

In that PowerShell I’m still not able to do task which require elevation as you can see with my first command “reg add” to write to HKLM. But interestingly I’m able to open secpol.msc as you can see. In the normal user session secpol.msc can’t be opened, you get this dialog:

secpol.msc access denied

With the ability to open secpol without UAC you can modify the Prompt for Secure Desktop policy to disable the Secure Desktop and UAC will be shown on the interactive desktop again:

secpol.msc disabled Secure Desktop and UAC Dialog

If you have an enabled the built-in local Administrator account, you can use that one for run as different user:

runs ad dialog with built-in local Administrator account

and you will get a PowerShell which is automatically elevated (as long as you run the Windows default UAC settings):

PowerShell running as built-in local Administrator account with elevation

Elevation can be seen in the title and my reg add to HKLM succeeded this time. That way you can modify the the reg key for Secure Desktop directly, or again use secpol.msc to modify it.

Yeah, this approach needs a local admin account but if you have one and do not have any other management channel this might be your rescue.

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Pinterest (Opens in new window)

Related

Articles, Enterprise Mobility, Intune, Modern Management, PowerShell, Scripting, Security, WindowsElevation, PromptOnSecureDesktop, Quick Assist, QuickAssist, Remote Control, secpol.msc, Secure Desktop, Security Baseline, Teams Screen Sharing, UAC, User Account Control, Windows 10

Post navigation

Intune application targeting for Windows 10 Win32 apps explained
Delivery Optimization with Intune and Microsoft Connected Cache (MCC)
54 replies to Quick Assist the built-in Remote Control in Windows 10
  1. Nigel Brown says:
    March 4, 2020 at 3:32 pm

    Anyway go leverage this for unattended access?

    Reply
    1. Oliver Kieselbach says:
      March 4, 2020 at 3:37 pm

      No not with Quick Assist, it is bound to the code and approvals from the user. Which is for most people a good thing as and users need to be in control, but I understand that companies also have requirements for unattended solutions. With Quick Assist I don’t see any chance to accomplish this.

      Reply
  2. Ricardo Czernotzky says:
    March 9, 2020 at 11:52 am

    This tool works very well. It would so be great if you could limit the usage rights via policy to people from the same tenant or even specific user groups (e.g. helpdesk) to prevent abuse by fraudsters.

    Reply
  3. Jose says:
    April 15, 2020 at 9:42 pm

    I’m trying to configure this via OMA-URI, not sure why it doesn’t apply. thoughts? ./Vendor/MSFT/Policy/Config/LocalPoliciesSecurityOptions/UserAccountControl_BehaviorOfTheElevationPromptForStandardUsers == Integer == 3

    Reply
    1. Oliver Kieselbach says:
      April 16, 2020 at 9:53 am

      Hi Jose,

      via a custom OMA-URI you should use: ./Vendor/MSFT/Policy/Config/LocalPoliciesSecurityOptions/UserAccountControl_SwitchToTheSecureDesktopWhenPromptingForElevation = 0 (Interger) to disable the Secure Desktop.

      Reference:
      https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions#localpoliciessecurityoptions-useraccountcontrol-switchtothesecuredesktopwhenpromptingforelevation

      best,
      Oliver

      Reply
      1. Jose says:
        April 16, 2020 at 12:37 pm

        Thank you Oliver, I’ll give it a try

  4. Tom Zajac says:
    April 15, 2020 at 11:52 pm

    I am sorry to tell you that this advice is not valid when you are accessing computer, where logged user is just a standard user.
    In that case you are not able to turn off UAC via altering registry settings.
    In fact everything that will require admin privileges will end up displaying UAC.
    So if your user is just a standard user, you will not be able to do anything.
    This days most of the users will be using standard account not admin, unless they use account that was created when Windows was installed. In that case will have and admin privileges….
    I believe you should mention that in your article, that you can use above method only when user has admin privileges already…

    Reply
    1. Oliver Kieselbach says:
      April 16, 2020 at 10:15 am

      Hi Tom,

      that’s not true the solution does work with logged on standard users. check the picture with Quick Assist and the UAC dialog it even shows that the user is not in administrator mode meaning the current logged on user is standard user. Without this capability it wouldn’t be a worth to mention, as you also mentioned almost every enterprise is running with standard users nowadays. Try it yourself, just go to a device with standard user, change the regkey (it will be recognized on the fly) and start the Quick Assist session, you will see the UAC can be controlled from the supporter and he can enter some valid admin credentials.

      best,
      Oliver

      Reply
  5. Wes M. says:
    April 20, 2020 at 6:41 am

    Oliver, thank you for this article, its clarity, and for adding the OMA-URI policy in the comments. As you know with the current state of COVID19 policies and regulations, this will be a boon to support my users remotely and can be undone once we have returned from quarantine. Thank you so much

    Reply
  6. Harjit Dhaliwal says:
    April 21, 2020 at 5:20 pm

    So, here’s the caveat. A standard user cannot save the registry change in order to get the required assistance with Quick Assist. The scenario is a remote user who can’t install the VPN client due to UAC and therefore can’t connect to the work domain to get policies and what not. It’s a Catch-22 situation and the issue many are struggling with with the recent WFH situation. If anyone has some suggestions or workarounds to make this work, I’d love to hear it. Thanks.

    Reply
    1. Wesley M. says:
      April 21, 2020 at 6:22 pm

      I think this requires some form of remote management MDM set up before hand. We’re using intune so it was just a matter of pushing the policy or a powershell script to change the registry entry.

      If you weren’t set up for remote management of your devices before, you’re in a pretty bad position for this. You may have to locally configure new machines with aremote management/MDM solution configured and setup some type of physical machine swap out process.

      Reply
    2. Tomasz Zajac says:
      April 22, 2020 at 4:23 am

      Dear Harjit Dhaliwal

      I used solutions listed below. Worked for me.
      It works best if you have credential to local admin, and even better if this is built in local admin.

      First I checked who is the admin by using command: ”net users”
      Then used admin account (that I have credentials to) to run cmd as that admin user.
      While in cmd box running as admin user, I have issued command “secpol.msc”
      This opened box\window with local security polices and under “local polices” –> “Security options” point to policy that says: “User Account Control: Switch to the secure desktop when…”
      and change that to disable. Apply etc.

      After that you will still get UAC prompt, however is popping as a box for typing admin credentials and is not dimming the desktop.

      This way you can see UAC prompt while remoting via Quick Assist, and open things by right click and open as admin etc.

      if this still not work for you, then only way is to use local admin account to activate built in administrator account and use that account for everything else, as build in administrator account is not triggering UAC prompt, and all commands issue with this account are accepted and issued without elevating etc.

      Reply
      1. Oliver Kieselbach says:
        April 22, 2020 at 8:23 am

        That’s an interesting approach, I think I will update the post later to show this nice little workaround with some screenshots. Thanks for sharing Tomasz.

  7. Trang Dao says:
    May 20, 2020 at 12:13 pm

    Hi Oliver, do you know if the text prompt can be modified that the remote user sees and needs to accept it?

    Reply
    1. Oliver Kieselbach says:
      May 20, 2020 at 12:24 pm

      Hi,

      I’m not aware of any method to modify this…

      best,
      Oliver

      Reply
  8. Gts says:
    May 20, 2020 at 4:30 pm

    Wonder what are the impact on disabling secure desktop?

    With regards to Tomasz suggestion not sure how you were able to disable the securedesktop remotly, when you run cmd as admin you would have prompted for uac?

    Reply
    1. Oliver Kieselbach says:
      May 20, 2020 at 4:46 pm

      Hi Gts,

      I’ve written about the impact in one of the paragraphs. The main impact is that your device is vulnerable to UAC spoofing attacks. If your security department is okay with that you’re good to go if not it’s not a solution for you. Tomasz approach needs a local administrator account and with that prerequisite you are able to make a QuickAssist session and use this local admin via the run-as way of process creation in this case the cmd and you will not see the normal UAC dialog you will see the run-as dialog which is not on the secure desktop but in case of the secedit command it still allows to modify the setting even if no UAC dialog was upfront. So, with this approach you are able to modify the SecureDesktop setting in a QuickAssist session so that you are able to proceed with a turned off secure desktop and you are able to interact with regular UAC dialogs in the existing and new QuickAssist sessions. The UAC dialogs are not shown on the secure desktop after the modification. All this is not needed if you have a management channel like Intune. It would be the case if you have to support a device where you not have a working management channel to reconfigure the secure desktop setting. Try it yourself, follow my instruction and use QuickAssist and connect to a LAB VM for example. You can verify the behavior I described easily.

      best,
      Oliver

      Reply
      1. RG says:
        May 20, 2020 at 5:09 pm

        Thank you for the quick response and not sure what you mean by “All this is not needed if you have a management channel like Intune” as I do have intune and UAC is an issue with quick connect. As you described above I am concerned tunning off secure desktop completly.

      2. Oliver Kieselbach says:
        May 20, 2020 at 5:15 pm

        The „All this is needed …“ reference was in regards to the Tomasz suggestion. If you have Intune you don’t need this, your decision is only are you willing to take the risk of disabling the SecureDesktop or not. I think the risk needs to be looked at, and in addition to cost, and usability gain in case of support. Like always in IT the answer is it depends of your situation and security demands 🙂

  9. Geoff Jones (@nopslider) says:
    June 2, 2020 at 10:47 am

    Rather than disabling the Secure Desktop, run PowerShell as your admin user (as above) and elevate using the following command:

    start-process powershell –verb runAs

    Ask the user to click ‘yes’ and you’ve got an elevated shell.

    Reply
    1. Oliver Kieselbach says:
      June 3, 2020 at 9:55 am

      Also a good way of achieving the goal 👍

      Reply
    2. RG says:
      June 29, 2020 at 11:37 am

      start-process powershell –verb runAs —– prmoted for the UAC in secure desktop where i couldnt see the prompt through the quick assist

      i also tried to create a shortcut and shift+rightclick run as an admin which also didnt elevate with admin (however i was able to type the admin details)

      i would like to acieve with secure desktop

      the uac policy is set for prompt for credentials in secure desktop in microsoft baseline

      Reply
      1. Oliver Kieselbach says:
        July 7, 2020 at 10:58 am

        Hey RG,

        I really think there is no way currently to use it with enabled Secure Desktop. There would be a way when QuickAssist would support UIAccess. Remote Assistance is supporting UIAccess and is able to turn of Secure Desktop to run successful. See here: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/user-account-control-allow-uiaccess-applications-to-prompt-for-elevation-without-using-the-secure-desktop. Quick Assis sadly does not support this feature.

        best,
        Oliver

  10. DeltaSM says:
    July 16, 2020 at 11:16 am

    Hello,

    I tried Tomasz solution which is to disable Secure Desktop through the use of secpol.msc (or gpedit.msc). I used a local administrator to do that and I succeeded. However, even if secure desktop seems to be disabled, I still have UAC popups on remote computer (which is normal of course) BUT I still have a black screen on Quick Assist.

    I also checked the registry and the key is set on “0”.

    What’s wrong in my case? FYI, I’m using Windows 10 v1803 64bits.

    Regards,

    DeltaSM

    Reply
    1. Oliver Kieselbach says:
      July 21, 2020 at 9:24 am

      Hey DeltaSM,

      that’s interesting, looks like the setting does not take into effect. Honestly, I’m not aware of any other setting which could still block you. The only thing I could imagine is maybe a GPO, MDM policy or something similar, always resetting your setting back to 1, but obviously I think that would have be seen from your side. But worth a double check it would be, to verify if there is no other policy resetting your key. Another idea I don’t have at the moment.

      best,
      Oliver

      Reply
      1. DeltaSM says:
        July 22, 2020 at 9:29 am

        Hello Olivier,

        First of all, thank your for your answer.

        The concerned computer is not part of a domain. It’s in WORKGROUP with no GPO, MDM or other policies applied. It’s a simple Windows installation with a limited rights user.

        Maybe our Windows 10 version (1803) is too old?

        This issue is not a problem anymore but it’s always interesting to report a bug 🙂

        Regards,

        DeltaSM

      2. Oliver Kieselbach says:
        July 22, 2020 at 9:38 am

        Interesting… I would not expect Windows 10 version 1803 to behave differently here as this UAC setting is available since Vista time and I think there were no major changed in UAC until now. Hmmm 🤫… really no idea why this happened. I guess to finally clarify it, a 1803 device would be needed to be deployed and then the we would have to try to reproduce the issue for further detailed analysis. But I think that should only be done if it introduces a major issue.

  11. DeltaSM says:
    July 22, 2020 at 10:44 am

    I will try to reproduce this problem one day once I have some free time 🙂 But for now, it’s not a problem anymore.

    Regards,

    DeltaSM

    Reply
  12. Pingback: Quick Assist Windows 10 – Soporte Remoto para Microsoft Intune – Deployment MX
  13. RG says:
    October 4, 2020 at 11:57 am

    Wonder if there is a policy in Intune to block non intune/non company devices to establish the connection with quick assist?

    wonder if its the remote assistance policies in the admx (seems its not applied currently and the behaviour is quick assist is enabled)

    Reply
    1. Oliver Kieselbach says:
      October 7, 2020 at 11:34 am

      Hey RG,

      I’m not aware of any config to control this. If this is a must have you might have to look into other solutions like AnyDesk where it is possible as far as I know to accomplish something like this.

      best,
      Oliver

      Reply
  14. Alexander says:
    November 6, 2020 at 2:46 pm

    Hello Oliver,

    It is possible to bypass the UAC for a specific App with Intune?

    best,

    Alex

    Reply
    1. Oliver Kieselbach says:
      November 10, 2020 at 6:42 pm

      Hey Alexander,

      no not really during execution. If the app requests elevated permission and UAC is enabled you will see the UAC prompt. During installation you typically run the installer in System context, this way you will not have any problems during installation and no UAC.

      best,
      Oliver

      Reply
  15. Pingback: Quick Assist the built-in Remote Control in Windows 10 – Modern IT – Cloud – Workplace – More Stuff 2 Read [Quite Sparsely]
  16. Tomi says:
    January 27, 2021 at 10:00 am

    Built-in Windows administrator account (SID ending -500) has some special permission to bypass UAC.

    Reply
  17. Pingback: Using ConfigMgr Run Scripts and Microsoft Quick Assist to Repair a Broken Domain Trust Relationship - A Square Dozen
  18. Nicola says:
    March 9, 2021 at 12:49 pm

    Hi Olivier, that’s really great article. I came across it at the right time, as our third party licenses are coming to their anniversary date!

    Before starting the deployment at our end, can you tell me how “Quick Assist” manages different Keyboard Layouts?
    Say that the supporter is using a German Keyboard layout and the the supported user is on French keyboard layout, will be quick assist be of any help?

    Thanks in advance!

    Tschuss!

    Nicola

    Reply
    1. Oliver Kieselbach says:
      March 11, 2021 at 1:48 pm

      Hi Nicola,

      Quick Assist uses the helper’s keyboard layout. So, the helper should not have problems during the remote session.

      best,
      Oliver

      Reply
      1. Nicola Guarino says:
        March 11, 2021 at 2:09 pm

        Awesome Olivier, thanks a lot!
        We will definitevily give it a try then ✌

  19. Pingback: Windows 10: after gaining remote access, remotely start Quick Assist as .Administrator without UAC, or temporarily disable UAC – Windows Questions
  20. Kannan says:
    April 26, 2021 at 1:41 pm

    anyone know why all of sudden why am I getting this on Quick Assist?

    “An error has occurred

    We’ve run into a problem. An error has caused screen sharing to end or we cannot establish a connection. Please close Quick Assist and try again later.”

    Reply
    1. Oliver Kieselbach says:
      April 26, 2021 at 1:45 pm

      Oh not seen so far… not aware of any issues with QA. Does not sound like a Config intercepting here like security setting. In that case I would expect immediate unsuccessful connection attempts. Maybe a Service side issue… see if it persists and open a ticket if still broken tomorrow or the day after tomorrow.

      Reply
  21. Support Agent says:
    April 26, 2021 at 2:01 pm

    Hello:

    Thank you for the post. Do you know if there is anyway to do any to log Quick Assist activity on managed devices?

    Reply
    1. Oliver Kieselbach says:
      April 26, 2021 at 2:16 pm

      Actually I‘m not aware of any logging… I will also have a look and if I find something I will post it here

      Reply
  22. Iforti says:
    May 11, 2021 at 5:27 am

    Hi all

    Anyone can provide a URI command for Quick Assist, please?

    Im trying this “file:///C:/Windows/System32/quickassist.exe” but it’s prompting me to save the exe file

    Let’s say I wanted to send a link for Quick Assist to my grandpa through email, so I don’t need to tell him to go through the procedure (Start, then type Quick Assist and click the Quick Assist app) instead I would just send him the link through email and he would open and run the app (Quick Assist) automatically just by clicking that link?

    Thanks in advance

    Reply
    1. Oliver Kieselbach says:
      May 11, 2021 at 7:57 am

      Hey Iforti,

      this won’t work. This is what most e-mail client nowadays trying to prevent as it would be too easy to fool people and make them run a malicious apps/code. I would really suggest to tell the other participant just to click WIN + Ctrl + Q. This is the easiest way in my opinion to get it started. Thats what I do and works good for me.

      best,
      Oliver

      Reply
  23. Iforti says:
    May 11, 2021 at 2:50 pm

    Oliver

    Thank you

    Reply
  24. hamdy says:
    June 10, 2021 at 7:58 pm

    is there limited time for run quick assist ?
    coase I use it and stopping each one hour

    Reply
    1. Oliver Kieselbach says:
      June 15, 2021 at 7:50 pm

      Hey hamdy,

      that’s a good question I’m not aware of a time limit but this may absolutely the case.

      best,
      Oliver

      Reply
  25. Ken says:
    June 17, 2021 at 8:58 pm

    Is there a way to create a watermark on Quick Assist that displays while connected to the remote user?

    Reply
    1. Oliver Kieselbach says:
      June 17, 2021 at 8:59 pm

      I’m sorry nothing available that I‘m aware of.

      Reply
  26. Tony says:
    July 16, 2021 at 9:40 am

    Hi Oliver,
    Great article. Are you able to copy and paste between screens using Quick Assist?
    Many thanks,

    Reply
    1. Oliver Kieselbach says:
      July 16, 2021 at 10:01 am

      Hi Tony,

      there is a feature called “Instruction Channel”, with that you can transfer commands between supporter and requester…

      best,
      Oliver

      Reply
  27. Thank You says:
    September 23, 2022 at 3:42 pm

    precise and clear with instructions.

    Reply

Leave a Reply Cancel reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Modern IT

IT influenced by Cloud and modern infrastructure principals. Always managed and up to date. Working from everywhere without barriers.

MVP - Microsoft Most Valuable Professional

 

Top Posts

  • Autopilot Manager with additional automation
  • Comprehensive guide to managing macOS with Intune
  • The easy way to deploy device certificates with Intune
  • Intune Policy Processing on Windows 10 explained
  • Triggering Intune Management Extension (IME) Sync

I blog on MSEndpointMgr.com from time to time too, check my content there about Modern Management or visit my Community page.

Follow me on Twitter

My Tweets

Tags

.net ADMX Automation AutoPilot Autopilot Manager Azure Azure AD AzureAD Azure Automation Azure Blob Storage Azure Web App BGInfo BitLocker BitLocker CSP Blob Storage Certificate certificate profile Company Portal ConfigMgr configuration profile Configuration Service Provider CSP Deep Dive Delivery Optimization device certificates DiagnosticLog Diagnostics DOGroupId Edge EMSAgent Endpoint Analytics Event GK HSTI Hyper-V IME Intune Intune Management Extension intunewin IntuneWinAppUtil IntuneWinAppUtilDecoder Language Experience Pack Log Analytics Logic Apps Marketplace MDM MDT MEMPowered Microsoft Graph OMA-DM OMA-URI OOBE P2P PBR Policy CSP PowerShell PowerShell Scripts Push-button reset Runbook SCEP SCEPman Security SideCar SyncML TPM Troubleshooting vbs Win32 Win32 Apps Windows Windows 10 Windows Autopilot Windows Insider Windows Update WUfB

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 6,129 other subscribers

Some links

Podcasts with me:

065 – Ignite 2021H1 Recap

061 – Oliver Kieselbach über Autopilot by Hairless in the Cloud

039 – Top 10 Take-Aways Ignite 2019 mit Oliver Kieselbach

GeekSprech Podcast Folge 41 – Microsoft Ignite MVP Recap

GeekSprech(EN) Podcast Episode 34 – Windows 10 Microsoft Ignite Announcements

GeekSprech Podcast Folge 29 – Modern Management

Webcasts with me:

GK Mechanics – Modern Windows Provisioning

Friends

emptydc.com
marcoscheel.de
stephanwaelde.com
walla.link
karstenkleinschmidt.de

Archives

  • January 2023 (1)
  • October 2022 (1)
  • September 2022 (3)
  • August 2022 (1)
  • July 2022 (1)
  • March 2022 (1)
  • December 2021 (1)
  • July 2021 (1)
  • March 2021 (1)
  • February 2021 (1)
  • January 2021 (1)
  • December 2020 (2)
  • November 2020 (3)
  • September 2020 (1)
  • July 2020 (1)
  • May 2020 (1)
  • April 2020 (1)
  • March 2020 (2)
  • February 2020 (2)
  • January 2020 (1)
  • October 2019 (1)
  • August 2019 (1)
  • July 2019 (3)
  • April 2019 (2)
  • March 2019 (1)
  • January 2019 (1)
  • December 2018 (1)
  • October 2018 (2)
  • September 2018 (1)
  • August 2018 (1)
  • July 2018 (2)
  • March 2018 (2)
  • February 2018 (4)
  • January 2018 (3)
  • November 2017 (4)
Blog at WordPress.com.
  • Follow Following
    • Modern IT - Cloud - Workplace
    • Join 222 other followers
    • Already have a WordPress.com account? Log in now.
    • Modern IT - Cloud - Workplace
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Copy shortlink
    • Report this content
    • View post in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...
 

    Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
    To find out more, including how to control cookies, see here: Cookie Policy