Now that Remote Assistance does not work and Quick Assist is the new way for remote help, How can i get it to work on my Remote Desktop Server?

[bswhipp]

Now that Remote Assistance does not work and Quick Assist is the new way for remote help, How can i get it to work on my Remote Desktop Server?

 

[ChatGPT]

To enable Quick Assist to work on a Remote Desktop Server (RDS), ensure you take the following steps for configuration:

---

1. Install Quick Assist on Your Remote Desktop Session Host​

Quick Assist is now available via the Microsoft Store, and you’ll need to install it to use it on RDS:

• Steps:
  1. Open the Microsoft Store in the RDS environment.
  2. Search for Quick Assist.
  3. Click Get to install Quick Assist. If the store is restricted by group policies in your RDS environment, consult with your IT admin to install permissible packages .

---

2. Ensure Required Dependencies Are Installed​

Quick Assist relies on Microsoft Edge WebView2 for proper functionality:

• Check if WebView2 Runtime is installed. If not:
  • Download the WebView2 Runtime from Microsoft's official site .
  • Install it on the RDS environment.

---

3. Manage Multi-Session Issues​

Quick Assist may not operate optimally in environments with multiple users logged in simultaneously. To mitigate this:

• Use dedicated VM sessions for users who require Quick Assist.
• Ensure the Quick Assist app is configured for single-user session environments where applicable.

---

4. Network and Port Configuration​

Quick Assist requires internet access for its session initialization and communication. Verify:

• Ports: Ensure incoming and outgoing ports like 443 (HTTPS) are open for Quick Assist server communication.
• Firewall: Configure your firewall to allow Quick Assist traffic if blocked.

---

5. Group Policies or Windows Admin Permissions​

For enterprise users, ensure Quick Assist is not being blocked by group policy:

• Open Group Policy Editor (gpedit.msc).
• Navigate to: Computer Configuration → Administrative Templates → Windows Components → Quick Assist.
• Set appropriate permissions to enable Quick Assist functionality.

---

6. Pin Quick Assist for Easier Access (Optional)​

To simplify access:

1. Launch Quick Assist after installing it.
2. Right-click its taskbar icon and select Pin to taskbar .

---

Troubleshooting Common Issues:​

1. Cannot Install on RDS Managed Session: Policies from IT admins may block external downloads (e.g., Microsoft Store). Ask the IT team to allow installation of Quick Assist or push it as part of automated updates or packages.
2. Error Codes for WebView2: If errors like Quick Assist failed to load WebView2 appear, verify its installation or reinstall it.
3. Slow Performance: Ensure your RDS server has adequate resources to handle both the RDS workload and Quick Assist sessions.

By following these steps, Quick Assist should work effectively in your Remote Desktop Server environment . Let me know if you encounter any specific issues!

 

[bswhipp]

Trying to install QA and it states it could not download after I run it as administrator.

 

[ChatGPT]

The error you're encountering during Quick Assist installation ("could not download") might be related to administrative permissions, group policy restrictions, or dependencies like WebView2. Here is a step-by-step guide to troubleshoot and resolve this issue:

---

1. Run with Elevated Permissions Correctly​

Even if running as an administrator, ensure it's done by:

• Right-clicking the installer or application and selecting Run as Administrator.
• Verify that your account has full administrative privileges. If not, switch to an admin account.

---

2. Install WebView2 Runtime​

Quick Assist relies on Microsoft Edge WebView2. If it isn’t installed, it will cause the application to fail. To resolve this:

• Download WebView2 Runtime:
  • Visit Microsoft WebView2 Runtime.
  • Install the runtime manually and retry the installation.

---

3. Check Group Policy or IT Restrictions​

In managed IT environments or Remote Desktop Servers (RDS), group policy settings can prevent downloads or installations. Here's what to check:

• Open gpedit.msc and navigate to:
  Computer Configuration → Administrative Templates → Windows Components → Microsoft Quick Assist
• Enable any settings allowing the installation or execution of Quick Assist.
• Ensure the Microsoft Store is not blocked or restricted.

---

4. Reset Microsoft Store Cache​

Sometimes, a corrupted cache can prevent installations. To reset it:

1. Press Windows + R to open the Run dialog.
2. Type wsreset.exe and hit Enter.
   • This will clear the Store cache. Restart your system afterward.

---

5. Ensure Connectivity to Required Endpoints​

Quick Assist communicates over the internet, including specific Microsoft endpoints. If a firewall or proxy blocks these, installation may fail:

• Add exceptions for Quick Assist connections or test installation on a direct internet connection.

---

6. Use the Microsoft Installer (Add-AppxPackage)​

If the store installer still fails, manually deploy Quick Assist using PowerShell:

• Open PowerShell as Administrator.
• Use the command:
  Add-AppxPackage -Path "<QuickAssistAppFilePath>"
  Replace <QuickAssistAppFilePath> with the path to the downloaded .Appx file if available. This might require downloading the appx package separately from the Microsoft resource links.

---

7. Look for Error Logs​

• Run the following in PowerShell to review installation-related logs:
  Get-AppxLog | Out-File "C:\Temp\QuickAssistLog.txt"
  Check the log file generated for details about the failure. Look for permission issues like 0x80070005 (access denied).

---

Additional Troubleshooting​

• If you're in a corporate or educational environment, reach out to your IT Administrator to ensure that Quick Assist is not blocked by policies or network restrictions.

These steps should resolve most Quick Assist installation issues in an RDS environment. Let me know if you hit further obstacles!

 

[bswhipp]

Can not find the appx

 

[ChatGPT]

It looks like you are trying to install Quick Assist but are unable to locate an .appx package for manual installation. Unfortunately, Microsoft does not currently provide an .appx installer for Quick Assist directly. Instead, it is distributed via the Microsoft Store. If downloading through the Store fails, you can try the following workarounds:

---

1. Re-enable Microsoft Store Access​

• If store access is restricted in your domain or RDS environment:
  1. Open gpedit.msc (Group Policy Editor).
  2. Navigate to:
     Computer Configuration > Administrative Templates > Windows Components > Store
  3. Ensure that the setting Turn off the Store application is set to Not Configured or Disabled.

2. Use the Microsoft Store for Business​

• Organizations can deploy Quick Assist through the Microsoft Store for Business, allowing IT administrators to push apps directly to RDS environments.

---

3. Clear Microsoft Store Cache​

• Corrupted cache files may prevent installation:
  1. Press Windows Key + R, type wsreset.exe, and hit Enter.
  2. Restart your system and retry the installation.

---

4. Manually Repair WebView2​

• Quick Assist depends on WebView2 components for rendering:
  1. Go to Microsoft WebView2 Runtime and download the runtime.
  2. Install this runtime, then retry the Quick Assist installation.

---

5. Install Using PowerShell (Add-AppxPackage Alternative)​

If you cannot obtain a manual .appx Quick Assist installer:

1. Search online for alternative official deployment options (e.g., .msixbundle) for enterprise environments.
2. If available, use the following PowerShell command to install:
   Add-AppxPackage -Path "C:\Path\To\AppxFile.msixbundle"

---

6. Check Microsoft Documentation​

• Microsoft continuously updates Quick Assist. If this is an update-specific issue, check Microsoft's official guide for the latest Quick Assist app deployment strategies.

If these steps fail due to limitations in your RDS environment, you might need to collaborate with your IT admin to resolve group policy blocks or firewall-related issues.

 

[bswhipp]

Looks like Microsoft will not allow it to be done on Servers.

 

[ChatGPT]

It appears that Microsoft Quick Assist may not be fully supported on Windows Server environments, particularly in scenarios where you are attempting installation on Remote Desktop Servers (RDS). This seems to be due to Microsoft's design choices and alignment with their intended use cases for Quick Assist:

---

Why Doesn't Quick Assist Work on RDS?​

1. Client-Centric Design: Quick Assist is optimized for Windows 10 and 11 environments as a client-based application, not for server-grade platforms like Windows Server.
2. Lack of RDS Session Integration: Quick Assist does not seem designed to handle multi-user environments on RDS effectively. This limits its applicability in server scenarios.
3. Microsoft Store Installation Dependency: Quick Assist requires installation through the Microsoft Store, which may not be available or fully functioning on Windows Server in certain organizations, especially in highly controlled environments.

---

Alternative Solutions for RDS and Server Environments:​

If Quick Assist won’t work due to these limitations, consider the following alternatives:

1. Remote Desktop Tools:
   • Continue using Remote Desktop Protocol (RDP) for user assistance. RDP is natively supported on Windows Server and supports persistent connections.
2. Third-Party Remote Tools:
   • Explore tools like TeamViewer, AnyDesk, or RustDesk, which are cross-compatible with server environments and allow advanced remote operations.
3. Legacy MSRA (Windows Remote Assistance):
   • Though MSRA (Microsoft Remote Assistance) is being phased out, it may still function in environments not impacted by the 24H2 update for basic remote support until a migration to alternate tools is complete.
4. Enterprise-Level Remote Support Solutions:
   • Consider adopting solutions like LogMeIn Rescue or Splashtop Business for robust remote support needs in an enterprise or server environment.

---

If your use case demands a Microsoft-native solution and Quick Assist is critical, reaching out to Microsoft support might provide clarity on future compatibility enhancements or available workarounds. Additionally, Quick Assist might eventually adapt to accommodate server environments if there's sufficient demand.