Actual Virtual Desktops Registration key

Network Level Authentication (NLA) for Remote Desktop Connection is an optional IKEY, Your Duo RDP application's integration key. Note: Check out our product offerings to see which Windows 10 version checks all of your boxes. Requires a third-party app for a virtual desktop. Universal apps can be designed to run across multiple Microsoft product families with nearly identical code‍—‌including PCs, tablets, smartphones, embedded.

Actual Virtual Desktops Registration key -

Set-Clipboard

Now we have the key but it is only valid for 2 hours.

image

Now I go to my failed Windows 10 host and start the installation of the Agent.

image

If you don’t have the Agent installer you can download it. In this case I use a failed WVD host during deployment.

Download and install the Windows Virtual Desktop Agent.

imageimage

Use the Token in the installer

imageimage

The next installer is the bootloader 

Download and install the Windows Virtual Desktop Agent Bootloader.

image

 

imageimageimageimage

Now that the Agent and the Bootloader is installed. We need two more steps.

Download the Windows Virtual Desktop side-by-side stack and run the installer.

As a final step – Download this script to activate the side-by-side stack. Save this as powershell script “ps1” or run this directly.

image

image

After running the SxS components you and use the portal  https://rdweb.wvd.microsoft.com/webclient/index.html

image

In this setup I used the Full desktop – This is also default –

image

Running this in a Window or use the Remote app in your Windows

image

  • Download the Remote Desktop client here.
  • Install the client. You don’t need administrator privileges if you are only installing it for your own user account.
  • Open the newly installed Remote Desktop app.
  • On the Let’s get started screen, click Subscribe to subscribe to a feed.

imageimage

Installation source on a failed WVD host

image

 

[!IMPORTANT] To help secure your Windows Virtual Desktop environment in Azure, we recommend you don’t open inbound port 3389 on your VMs. Windows Virtual Desktop doesn’t require an open inbound port 3389 for users to access the host pool’s VMs. If you must open port 3389 for troubleshooting purposes, we recommend you use just-in-time VM access.

 

 

 

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Robert Smit MVP Linkedin profile

Google  : Robert Smit MVP profile

Like this:

LikeLoading...

Author: Robert Smit [MVP]

Robert Smit is Senior Technical Evangelist and is a current Microsoft MVP in Clustering as of 2009. Robert has over 20 years experience in IT with experience in the educational, health-care and finance industries. Robert’s past IT experience in the trenches of IT gives him the knowledge and insight that allows him to communicate effectively with IT professionals who are trying to address real concerns around business continuity, disaster recovery and regulatory compliance issues. Robert holds the following certifications: MCT - Microsoft Certified Trainer, MCTS - Windows Server Virtualization, MCSE, MCSA and MCPS. He is an active participant in the Microsoft newsgroup community and is currently focused on Hyper-V, Failover Clustering, SQL Server, Azure and all things related to Cloud Computing and Infrastructure Optimalization. Follow Robert on Twitter @ClusterMVP Or follow his blog https://robertsmit.wordpress.com Linkedin Profile Http://nl.linkedin.com/in/robertsmit Robert is also capable of transferring his knowledge to others which is a rare feature in the field of IT. He makes a point of not only solving issues but also of giving on the job training of his colleagues. A customer says " Robert has been a big influence on our technical staff and I have to come to know him as a brilliant specialist concerning Microsoft Products. He was Capable with his in-depth knowledge of Microsoft products to troubleshoot problems and develop our infrastructure to a higher level. I would certainly hire him again in the future. " Details of the Recommendation: "I have been coordinating with Robert implementing a very complex system. Although he was primarily a Microsoft infrastructure specialist; he was able to understand and debug .Net based complext Windows applications and websites. His input to improve performance of applications proved very helpful for the success of our project View all posts by Robert Smit [MVP]

Источник: https://robertsmit.wordpress.com/2019/11/20/step-by-step-windows-virtual-desktop-troubleshooting-manual-add-vm-to-hostpool-wvd-rds-azure-msignite-mvpbuzz-cloud/

Optimization for Microsoft Teams

Citrix delivers optimization for desktop-based Microsoft Teams (1.2.00.31357 or higher) using Citrix Virtual Apps and Desktops and Citrix Workspace app. By default, we bundle all the necessary components into the Citrix Workspace app and the Virtual Delivery Agent (VDA).

Our optimization for Microsoft Teams contains VDA-side HDX services and an API to interface with the Microsoft Teams hosted app to receive commands. These components open a control virtual channel (CTXMTOP) to the Citrix Workspace app-side media engine. The endpoint decodes and renders the multimedia locally, moving the Citrix Workspace app window back into the hosted Microsoft Teams app.

Authentication and signaling occur natively on the Microsoft Teams-hosted app, just like the other Microsoft Teams services (for example chat or collaboration). Audio/video redirection doesn’t affect them.

is a command and control virtual channel. That means that media isn’t exchanged between the Citrix Workspace app and the VDA.

Only client-fetch/client-render is available.

This video demo gives you an idea of how Microsoft Teams works in a Citrix virtual environment.

Optimization for Microsoft Teams demo

Microsoft Teams installation

Note:

We recommend installing the VDA before installing Microsoft Teams in the golden image. This installation order is needed for the ALLUSER=1 flag to take effect. If you installed Microsoft Teams in the virtual machine before installing the VDA, uninstall and reinstall Microsoft Teams. If you’re using App Layering, see For App Layering for more details.

We recommend that you follow the Microsoft Teams machine-wide installation guidelines and avoid using the .exe installer that installs Microsoft Teams in . Instead, install in by using the ALLUSER=1 flag from the command line.

This example also uses the ALLUSERS=1 parameter. When you set this parameter, the Teams Machine-Wide Installer appears in Programs and Features in the Control Panel and in Apps & features in Windows Settings for all users of the computer. All users can then uninstall Microsoft Teams if they have administrator credentials.

It’s important to understand the difference between ALLUSERS=1 and ALLUSER=1. You can use the ALLUSERS=1 parameter in non-VDI and VDI environments. Use the ALLUSER=1 parameter only in VDI environments to specify a per-machine installation.

In ALLUSER=1 mode, the Microsoft Teams application doesn’t auto-update whenever there’s a new version. We recommend this mode for non-persistent environments, such as hosted shared apps or desktops out of a Windows Server or Windows 10 random/pooled catalogs. For more information, see Install Microsoft Teams using MSI (VDI Installation section).

Suppose you have Windows 10 dedicated persistent VDI environments. You want the Microsoft Teams application to auto-update and prefer Microsoft Teams to install per-user under . In this case, use the installer or the MSI without ALLUSER=1.

For Remote PC

We recommend that you install Microsoft Teams version 1.4.00.22472 or higher, after installing the VDA. Otherwise, you need to sign out and sign in again for Microsoft Teams to detect the VDA as expected. Version 1.4.00.22472 or higher includes augmented logic executed at Microsoft Teams launch time and sign in time for VDA detection. These versions also include active session type identification (HDX, RDP or locally connected to the client machine). If you are locally connected, previous versions of Microsoft Teams might fail to detect and disable certain features or UI elements. For example, Breakout Rooms, pop out windows for meetings and chat, or meeting reactions.

In some Remote PC scenarios, when you reconnect to a previously non-optimized session from a new endpoint that supports HDX optimization, you might need to relaunch Microsoft Teams to support HDX optimization.

For App Layering

If using Citrix App Layering to manage VDA and Microsoft Teams installations in different layers, deploy this registry key on Windows VDAs before installing Microsoft Teams with ALLUSER=1. For information, see Optimization for Microsoft Teams with Citrix App Layering in the list of features managed through the registry.

Profile Management recommendations

We recommend using the machine-wide installer for Windows Server and Pooled VDI Windows 10 environments.

When the ALLUSER=1 flag is passed to the MSI from the command line (the machine-wide installer), the Microsoft Teams app installs under (~300 MB). The app uses for logs and (~600–700 MB) for user specific configurations, caching of elements in the user interface, and so forth.

Important:

If you don’t pass the ALLUSER=1 flag, the MSI places the Teams.exe installer and under . A registry key (TeamsMachineInstaller) is added under:

A subsequent user logon triggers the final installation in AppData instead.

Machine-wide installer

The following is an example of folders, desktop shortcuts, and registries created by installing Microsoft Teams machine-wide installer on a Windows Server 2016 64-bit VM:

Folder:

    Desktop Shortcut:

    Registry:

    • Name:
    • Type:
    • Value:

    Note:

    The registry location varies based on the underlying Operating Systems and bitness.

    Recommendations

    • We recommend disabling auto-start by deleting the Microsoft Teams registry keys. Doing so prevents many logons that occur at the same time (for example, at the beginning of your work day) from spiking up the VM’s CPU.
    • If the virtual desktop does not have a GPU/vGPU, we recommend setting Disable GPU hardware acceleration in the Microsoft Teams Settings to improve performance. This setting () is stored in in . You can use a logon script to edit that file and set the value to true.
    • If using Citrix Workspace Environment Management (WEM), enable CPU Spikes Protection to manage processor consumption for Microsoft Teams.

    Per-user installer

    When using the installer, the installation process differs. All the files are placed in AppData.

    Folder:

      Desktop shortcut:

      Registry:

      Best Practices

      The best practice recommendations are based on the use-case scenarios. Using Microsoft Teams with a non-persistent setup requires a profile caching manager for efficient Microsoft Teams runtime data synchronization. With a profile caching manager, the appropriate user-specific information (for example, user data, profile, and settings) is cached during the user session. Synchronize the data in these two folders:

        Microsoft Teams cached content exclusion list for non-persistent setup

        To reduce the user caching size to further optimize your non-persistent setup, exclude the files and directories from the Microsoft Teams caching folder as described in the Microsoft documentation.

        Use case: single-session scenario

        In this scenario, the end user uses Microsoft Teams in one location at a time. They don’t need to run Microsoft Teams in two Windows sessions at the same time. For instance, in a common virtual desktop deployment, each user is assigned to one desktop, and Microsoft Teams is deployed in the virtual desktop as one application. We recommend enabling the Citrix Profile container and redirecting per-user directories listed in Per-user installer into the container.

        1. Deploy the Microsoft Teams machine-wide installer (ALLUSER=1) in the golden image.
        2. Enable Citrix Profile Management and set up the user profile store with the proper permissions.
        3. Enable the following Profile Management policy setting: File system > Synchronization > Profile container – List of folders to be contained in profile disk.

          Profile container

          List all the per-user directories into this configuration. You can also configure these settings using the Citrix Workspace Environment Management (WEM) service.

        4. Apply the settings to the correct delivery group.
        5. Log in to validate the deployment.

        System requirements

        Minimum recommended version - Delivery Controller (DDCs) 1906.2

        If you’re using an earlier version, see Enable optimization of Microsoft Teams:

        Supported operating systems:

        • Windows Server 2022, 2019, 2016, 2012R2 Standard and Datacenter Editions, and with the Server Core option

        Minimum version - Virtual Delivery Agents (VDAs) 1906.2

        Supported operating systems:

        • Windows 10 64-bit, versions 1607 and higher. VM hosted apps are supported with Citrix Workspace app for Windows 2109.1 or later.
        • Windows Server 2022, 2019, 2016, and 2012 R2 (Standard and Datacenter Editions).

        Requirements:

        • BCR_x64.msi - the MSI that contains the Microsoft Teams optimization code and starts automatically from the GUI. If you’re using the command line interface for the VDA installation, don’t exclude it.

        Recommended version – Citrix Workspace app for Windows latest CR and Minimum version - Citrix Workspace app 1907 for Windows

        • Windows 8 and 10 (32-bit and 64-bit editions, including Embedded editions) (Support for Windows 7 stopped at Version 2006)
        • Windows 10 IoT Enterprise 2016 LTSB (v1607) and 2019 LTSC (v1809)
        • Processor (CPU) architectures supported: x86 and x64 (ARM is not supported)
        • Endpoint requirement: Approximately 2.2–2.4 GHz dual core CPU that can support 720p HD resolution during a peer-to-peer video conference call.
        • Dual or quad-core CPUs with lower base speeds (~1.5 GHz) equipped with Intel Turbo Boost or AMD Turbo Core that can boost up to at least 2.4 GHz.
        • HP Thin Clients verified: t630/t640, t730/t740, mt44/mt45.
        • Dell Thin Clients verified: 5070, 5470 Mobile TC.
        • 10ZiG Thin Clients verified: 4510 and 5810q.
        • For a complete list of verified endpoints, see Thin Clients.
        • Citrix Workspace app requires at least 600 MB free disk space and 1 GB RAM.
        • Microsoft .NET Framework minimum requirement is version 4.6.2. Citrix Workspace app automatically downloads and installs .NET Framework if it’s not present in the system.

        Administrators can enable/disable Microsoft Teams starting in optimized mode by changing the Teams Optimization policy. Users starting in optimized mode in Citrix Workspace app don’t have the option to disable Microsoft Teams.

        Minimum version - Citrix Workspace app 2006 for Linux

        For more information, see Optimization for Microsoft Teams in What’s new in 2006.

        Software:

        • GStreamer 1.0 or later or Cairo 2
        • libc++-9.0 or later
        • libgdk 3.22 or later
        • OpenSSL 1.1.1d
        • x64 Linux distribution

        Hardware:

        • Minimum 1.8 GHz dual-core CPU that can support 720p HD resolution during a peer-to-peer video conference call
        • Dual or quad-core CPU with a base speed of 1.8 GHz and a high Intel Turbo Boost speed of at least 2.9 GHz

        For a complete list of verified endpoints, see Thin Clients.

        For more information, see Prerequisites to install Citrix Workspace app.

        You can disable Teams optimization updating the value of field VDWEBRTC to Off in the file. The default is VDWEBRTC=On. After performing the update, restart the Session. (Root permission is required).

        Minimum version - Citrix Workspace app 2012 for Mac

        Supported operating systems:

        • macOS Catalina (10.15).
        • macOS Big Sur 11.0.1 or higher.

        Features supported:

        • Audio
        • Video
        • Screen sharing optimization (incoming and outgoing)

        Note:

        Citrix Viewer app requires access to MacOS Security & Privacy preferences for screen sharing to work. Users configure this preference in Apple menu > System preferences > Security & Privacy > Privacy tab > Screen recording and select Citrix Viewer.

        Microsoft Teams optimization works by default if the user has Citrix Workspace app 2012 or later and macOS 10.15.

        If you want to disable Microsoft Teams optimization, run this command in a terminal and restart Workspace app:

        Minimum version - Citrix Workspace app 2105.5 for ChromeOS

        Features supported:

        • Audio
        • Video
        • Screen sharing optimization (incoming and outgoing) - disabled by default. See these settings for instructions on how to turn it on.

        Feature matrix and version support

        FeatureWindows CRWindows 1912 LTSR (and CU1-CU4)Windows 1912 CU5 (or higher)MacLinuxChromeOS
        Audio/Video (P2P and conference)1907YesYes200920042105.5
        Screensharing1907YesYes201220062105.5 (1)
        i. Screen Indicator Red border2002YesYes20122006X
        ii. Limit capture to Desktop Viewer2009.5XYes20122006X
        iii. Multimonitor2106 (2)XX21062106X
        DTMF2102XYes (5)210121012111.1
        Proxy Server support2012 (3)XYes (3) (5)2104 (4)2101 (4)X
        1. Disabled by default, requires Admin to enable.
        2. CD Viewer in full screen mode only. SHIFT+F2 not supported.
        3. Negotiate/Kerberos, NTLM, Basic, and Digest. Pac files are also supported.
        4. Anonymous only.
        5. Only on Windows 10 Client OS.

        Enable optimization of Microsoft Teams

        To enable optimization for Microsoft Teams, use the Manage console policy described in Microsoft Teams redirection policy. It’s ON by default. In addition to this policy being enabled, HDX checks to verify that the version of the Citrix Workspace app is at least the minimum required version. If you enabled the policy and the Citrix Workspace app version is supported, the HKEY_CURRENT_USER\Software\Citrix\HDXMediaStream\MSTeamsRedirSupport registry key is set to 1 automatically on the VDA. Microsoft Teams reads the key to load in VDI mode.

        Note:

        If you’re using version 1906.2 VDAs or higher with older controller versions (for example, version 7.15) that don’t have the policy available in the Manage console (Studio), your VDA can still be optimized. HDX optimization for Microsoft Teams is enabled by default in the VDA.

        If you click About > Version, the Citrix HDX Optimized legend displays:

        Optimized for Citrix legend

        If you see Citrix HDX Not Connected, the Citrix API is loaded in Microsoft Teams. Loading the API is the first step toward redirection. But there’s an error in later parts of the stack. The error is most likely in the VDA services or the Citrix Workspace app.

        Not optimized for Citrix legend

        If you don’t see any legend, Microsoft Teams failed to load the Citrix API. Exit Microsoft Teams by right-clicking the notification area icon and restarting. Make sure that the Manage console policy isn’t set to Prohibited and that the Citrix Workspace app version is supported.

        No Citrix legend

        Important: session reconnects

        • You might need to relaunch Microsoft Teams to get an HDX optimized session when your connectivity changes. For example, if you are roaming from an unsupported endpoint (Workspace app for iOS, Android, HTML5, or old versions of Windows/Linux/Mac) to a supported one (Workspace app for Windows/Linux/Mac/ChromeOS), or vice versa.
        • When you roam from a local session to an HDX session, you need to relaunch Microsoft Teams to optimize with HDX. This is a Remote PC Access scenario.

        Network requirements

        Microsoft Teams relies on Media Processor servers in Office 365 for meetings or multiparty calls. In addition, Microsoft Teams relies on Office 365 Transport Relays for these scenarios:

        • Two peers in a point-to-point call do not have direct connectivity
        • A participant does not have direct connectivity to the media processor.

        So the network health between the peer and the Office 365 cloud determines the performance of the call.

        We recommend evaluating your environment to identify any risks and requirements that can influence your overall cloud voice and video deployment. Use the Skype for Business Network Assessment Tool to test if your network is ready for Microsoft Teams. For support information, see Support.

        Summary of key network recommendations for Real Time Protocol (RTP) traffic

        • Connect to the Office 365 network as directly as possible from the branch office.
        • If you must use any of the following at the branch office, make sure that RTP/UDP Teams traffic is unhindered.
          • Bypass proxy servers
          • Network SSL intercept
          • Deep packet inspection devices
          • VPN hairpins (use split tunneling if possible)
        • Plan for and provide sufficient bandwidth at the branch office.
        • Check each branch office for network connectivity and quality.

        The WebRTC media engine in the Workspace app (HdxTeams.exe or HdxRtcEngine.exe) uses the Secure Real-time Transport Protocol (SRTP) for multimedia streams that are offloaded to the client. SRTP provides confidentiality and authentication to RTP by using symmetric keys (128 bit) to encrypt media and control messages and uses the AES encryption cipher in counter mode.

        The following metrics are recommended for a positive user experience:

        MetricEndpoint to Office 365
        Latency (one way)< 50 msec
        Latency (RTT)< 100 msec
        Packet Loss<1% during any 15s interval
        Packet inter-arrival jitter<30ms during any 15s interval

        For more information, see Prepare your organization’s network for Microsoft Teams.

        In terms of bandwidth requirements, optimization for Microsoft Teams can use a wide variety of codecs for audio (OPUS/G.722/PCM G711) and video (H264).

        The peers negotiate these codecs during the call establishment process using the Session Description Protocol (SDP) Offer/Answer. Citrix minimum recommendations per user are:

        TypeBandwidthCodec
        Audio (each way)~ 90 kbpsG.722
        Audio (each way)~ 60 kbpsOpus*
        Video (each way)~ 700 kbpsH264 360p @ 30 fps 16:9
        Screen sharing~ 300 kbpsH264 1080p @ 15 fps

        * Opus supports constant and variable bitrate encoding from 6 kbps up to 510 kbps.

        Opus is the preferred codec for peer-to-peer calls between two optimized VDI users.

        G.722 and H264 are the preferred codecs for a VDI user joining a meeting.

        Important:

        Regarding performance, encoding is more expensive than decoding in terms of CPU use at the client machine. You can hardcode the maximum encoding resolution in Workspace app for Linux and Windows. See Encoder performance estimator and Optimization for Microsoft Teams.

        Proxy servers

        Depending on the location of the proxy, consider the following:

        • Proxy configuration on the VDA:

          If you configure an explicit proxy server in the VDA and route connections to localhost through a proxy, redirection fails. To configure the proxy correctly, you must select the Bypass proxy servers for local address setting in Internet Options > Connections > LAN Settings > Proxy Servers and make sure is bypassed.

          If you use a PAC file, your VDA proxy configuration script from the PAC file must return DIRECT for . If not, optimization fails. To make sure that the script returns DIRECT, use .

        • Proxy configuration on Citrix Workspace app:

          If the branch office is configured to access the internet through a proxy, these versions support proxy servers:

          • Citrix Workspace app for Windows version 2012 (Negotiate/Kerberos, NTLM, Basic, and Digest. Pac files are also supported)
          • Citrix Workspace app for Windows version 1912 CU5 (Negotiate/Kerberos, NTLM, Basic, and Digest. Pac files are also supported)
          • Citrix Workspace app for Linux version 2101 (anonymous authentication)
          • Citrix Workspace app for Mac version 2104 (anonymous authentication)

        Client devices with earlier releases of Citrix Workspace app can’t read proxy configurations. These devices send traffic directly to Office 365 TURN servers.

        Important:

        • Verify that the client device can connect to the DNS server to perform DNS resolutions. A client device must be able to resolve three Microsoft Teams TURN server’s FQDNs: , , and .
        • The location of the conference server is selected based on the first participant’s virtual desktop location (and not client).

        Call establishment and media flow paths

        When possible, the HDX WebRTC media engine in the Citrix Workspace app (HdxTeams.exe or HdxRtcEngine.exe) tries to establish a direct network Secure Real-time Transport Protocol (SRTP) connection over User Datagram Protocol (UDP) in a peer-to-peer call. If the UDP high ports are blocked, the media engine falls back to TCP/TLS 443.

        The HDX media engine supports ICE, Session Traversal Utilities for NAT (STUN), and Traversal Using Relays around NAT (TURN) for candidate discovery and establishing connection.

        Note that this means that the endpoint must be able to perform DNS resolutions.

        Consider a scenario where there is no direct path between the two peers or between a peer and a conference server and you are joining a multi-party call or meeting. In this scenario, the HdxRtcEngine.exe uses a Microsoft Teams transport relay server in Office 365 to reach the other peer or the media processor, where meetings are hosted. Your client machine must have access to three Office 365 subnet IP address ranges and four UDP ports (or TCP/TLS 443 as fallback if UDP is blocked). For more information, see the Architecture diagram in the Call setup and Office 365 URLs and IP address ranges ID 11.

        IDCategoryAddressesDestination Ports
        11Optimize required13.107.64.0/18, 52.112.0.0/14, 52.120.0.0/14UDP: 3478, 3479, 3480, 3481, TCP: 443 (fallback)

        These ranges contain both Transport Relays and media processors, front-ended by an Azure Load Balancer. The Microsoft Teams Transport Relays provide STUN and TURN functionality, but they are not ICE endpoints. Also, the Microsoft Teams Transport Relays don’t terminate media, TLS, or perform any transcoding. They can bridge TCP (if HdxRtcEngine.exe uses TCP) to UDP when they forward traffic to other peers or media processors.

        Workspace app WebRTC media engine contacts the closest Microsoft Teams Transport Relay in the Office 365 cloud. The media engine uses anycast IP and port 3478–3481 UDP (different UDP ports per workload, though multiplexing can happen) or 443 TCP/TLS for fallbacks. Call quality depends on the underlying network protocol. Because UDP is always recommended over TCP, we advise you to design your networks to accommodate UDP traffic in the branch office.

        If Microsoft Teams loaded in optimized mode and HdxRtcEngine.exe is running on the endpoint, ICE failures might cause a call setup failure or one-way-only audio/video. When a call can’t be completed or media streams aren’t full duplex, check the Wireshark trace on the endpoint first. For more information about the ICE candidate gathering process, see “Collecting logs” in the Support section.

        Note:

        If the endpoints don’t have internet access, the users might still be able to make a peer-to-peer call if they are both on the same LAN. Meetings fail. In this case, there’s a 30-second timeout before the call setup begins.

        Call setup

        Use this architecture diagram as a visual reference for the call flow sequence. The corresponding steps are indicated in the diagram.

        Architecture

        How optimization for Microsoft Teams works

        1. Start Microsoft Teams.
        2. Microsoft Teams authenticates to O365. Tenant policies are pushed down to the Microsoft Teams client, and relevant TURN and signaling channel information is relayed to the app.
        3. Teams detects that it’s running in a VDA and makes API calls to the Citrix JavaScript API.
        4. Citrix JavaScript in Microsoft Teams opens a secure WebSocket connection to WebSocketService.exe running on the VDA, which spawns WebSocketAgent.exe inside the user session.
        5. WebSocketAgent.exe instantiates a generic virtual channel by calling into the Citrix HDX Teams Redirection Service (CtxSvcHost.exe).
        6. Citrix Workspace app’s wfica32.exe (HDX engine) spawns a new process called HdxTeams.exe or HdxRtcEngine.exe, which is the new WebRTC engine used for Microsoft Teams optimization.
        7. Citrix media engine and Teams.exe have a 2-way virtual channel path and can start processing multimedia requests.

          —–User calls——

        8. Peer A clicks the call button. Teams.exe communicates with the Microsoft Teams services in Office 365, establishing an end-to-end signaling path with Peer B. Microsoft Teams asks HdxTeams for a series of supported call parameters (codecs, resolutions, and so forth, which is known as a Session Description Protocol (SDP) offer). These call parameters are then relayed using the signaling path to the Microsoft Teams services in Office 365 and from there to the other peer.
        9. The SDP offer/answer (single-pass negotiation) takes place through the signaling channel, and the ICE connectivity checks (NAT and Firewall traversal using STUN bind requests) complete. Then, Secure Real-time Transport Protocol (SRTP) media flows directly between HdxTeams.exe and the other peer (or Office 365 conference servers if it’s a meeting).

        Microsoft Phone System

        Phone System is Microsoft’s technology that enables call control and PBX in the Office 365 cloud with Microsoft Teams. Optimization for Microsoft Teams supports Phone System, using Office 365 Calling Plans or Direct Routing. With Direct Routing, you connect your own supported session border controller to the Microsoft Phone System directly without any additional on-premises software. Call queues, transfer, forward, hold, mute, and resume a call are supported.

        DTMF:

        Dual tone multi frequency (DTMF) is supported with these versions of Citrix Workspace app (or higher):

        • Citrix Workspace app for Windows version 2102
        • Citrix Workspace app for Windows LTSR 1912 CU5 (Windows 10 OS only)
        • Citrix Workspace app for Linux version 2101
        • Citrix Workspace app for Mac version 2101
        • Citrix Workspace app for Chrome OS version 2111.1

        When users start an optimized call using the Microsoft Teams client for the first time, they might notice a warning with the Windows firewall settings. The warning asks for users to allow communication for HdxTeams.exe or HdxRtcEngine.exe (HDX Overlay Teams).

        Firewall warning

        The following four entries are added under Inbound Rules in the Windows Defender Firewall > Advanced Security console. You can apply more restrictive rules if you want.

        Firewall inbound rules

        Microsoft Teams and Skype for Business Coexistence

        You can deploy Microsoft Teams and Skype for Business side by side as two separate solutions with overlapping capabilities. For more information, see Understand Microsoft Teams and Skype for Business coexistence and interoperability.

        Citrix RealTime Optimization Pack and HDX optimization for Microsoft Teams multimedia engines then honor the configuration set in your environment. Examples include island modes, Skype for Business with Microsoft Teams collaboration, and Skype for Business with Microsoft Teams collaboration and meetings.

        Peripheral access can be granted only to a single application at the time. For example, webcam access by the RealTime Media Engine during a call locks the imaging device during a call. When the device is released, it becomes available for Microsoft Teams.

        Teams and Skype coexistence

        Citrix SD-WAN: optimized network connectivity for Microsoft Teams

        Optimal audio and video quality require a network connection to the Office 365 cloud that has low latency, low jitter, and low packet loss. Backhauling of Microsoft Teams audio-video RTP traffic from Citrix Workspace app users at branch office locations to a data center before going to the internet can add excessive latency. It might also cause congestion on WAN links. Citrix SD-WAN optimizes connectivity for Microsoft Teams following Microsoft Office 365 network connectivity principles. Citrix SD-WAN uses the Microsoft REST-based Office 365 IP address and web service and proximate DNS to identify, categorize, and steer Microsoft Teams traffic.

        Business broadband internet connections in many areas suffer from intermittent packet loss, periods of excessive jitter, and outages.

        Citrix SD-WAN offers two solutions to preserve Microsoft Teams audio-video quality when network health is variable or degraded.

        • If you use Microsoft Azure, a Citrix SD-WAN virtual appliance (VPX) deployed in the Azure VNET provides advanced connectivity optimizations. These optimizations include seamless link failover and audio packet racing.
        • Citrix SD-WAN customers can connect to Office 365 through the Citrix Cloud Direct service. This service provides reliable and secure delivery for all internet-bound traffic.

        If the quality of the branch office internet connection isn’t a concern, it might be enough to minimize latency by steering Microsoft Teams traffic directly from the Citrix SD-WAN branch appliance to the nearest Office 365 front door. For more information, see Citrix SD-WAN Office 365 optimization.

        Citrix SD-WAN

        Gallery view and active speakers in Microsoft Teams

        Microsoft Teams supports Gallery, Large gallery, and Together mode layouts.

        Microsoft Teams displays a 2x2 grid with video streams of four participants (known as Gallery). In this case, Teams sends four video streams to the client device for decoding. When more than four participants share video, only the last four most active speakers appear on the screen.

        Microsoft Teams also provides the large gallery view with a grid up to 7x7. As a result, the Microsoft Teams conference server composites a single video feed and sends it to the client device for decoding, resulting in lower CPU consumption. This single, matrix-style feed might include users’ self-preview video as well.

        Lastly, Microsoft Teams supports Together mode, which is part of the new meeting experience. Using AI segmentation technology to digitally place participants in a shared background, Teams puts all participants in the same auditorium.

        The user can control these modes during a conference call by selecting Gallery, Large gallery, or Together mode layouts in the ellipses menu.

        Video layout

        Support for video aspect ratio constraints (CWA for Windows 2102, CWA for Linux 2106, CWA for MAC 2106 or higher):

        • The option Fill to frame is available in Gallery/Large Gallery View. This option crops the video size to fit it in the sub-window. Fit to frame, on the other hand, displays black bars (letterbox) on the sides of the video so there is no cropping.

        The following table provides a comparison of Gallery and Large Gallery layouts:

        Gallery view 2x2 (default)Large Gallery view
        Layout / GridDisplays a 2x2 grid with video streams of four participants. Only the last four most active speakers appear on the screen and other participants do not appear on the grid.Displays a 7x7 grid with video streams of 49 participants.
        Mixing techniqueA media router forwards individual streams from each participant to every user.A central conference server mixes and transcodes all audio or video to create a tailored composite layout for every participant. This introduces some additional latency.
        Active speakerThe new active speaker replaces the least active speaker in the grid.Displays all participants irrespective of whether they are active or inactive.
        Encoding at the endpointA single quality video stream. You can set the encoding resolution value on the client. For more information, see Encoder performance estimator and Optimization for Microsoft Teams. Quality is defined as resolution and frames per second. Currently, simulcast video is not supported.A single quality video stream. You can set the encoding resolution value on the client. For more information, see Encoder performance estimator and Optimization for Microsoft Teams.
        Decoding at the endpointEach participant gets up to four individual media streams. This increases CPU consumption at the endpoint by HdxRtcEngine.exe (for decoding/rendering).Each participant gets only a single stream for audio and video. This lowers the CPU consumption at the endpoint.
        Maximum resolution720p. When four participants are sharing video, the maximum resolution is 360p per video feed. If less than four participants are sharing video, then the resolution per video feed might be higher.720p for the composite layout or mixing. Each sender reduces resolution or upload bitrate because there is no need for a high-quality video stream per participant in a composite layout.
        ‘Slow-user’ problemSender modifies each modality’s (audio/video/screenshare) quality to the lowest common network quality among the participants. This multimedia stream is then forwarded to all other participants. As a result, a participant with poor network condition impacts the quality for everyone else in the call.Less susceptible to the lowest common network quality scenario. The conference server provides different qualities based on the network conditions of individual participants.
        Self-previewDisplays yourself in a small thumbnail in real time.Displays yourself in thumbnail and mixed with the rest of the video feeds. As a result, you might see yourself included in the main video layout with some additional delay.

        Screen sharing in Microsoft Teams

        Microsoft Teams relies on video-based screen sharing (VBSS), effectively encoding the desktop being shared with video codecs like H264 and creating a high-definition stream. With HDX optimization, incoming screen sharing is treated as a video stream. So if you are in the middle of a video call and the other peer starts to share the desktop, the original camera video feed is paused. Instead, the screen sharing video feed shows. The peer must then manually resume the camera sharing.

        Outgoing screen sharing is also optimized and offloaded to Citrix Workspace app. In this case, the media engine captures and transmits only the Citrix Desktop Viewer (CDViewer.exe) window, with a red border drawn around it. Any local application overlapping with Desktop Viewer is not captured.

        Note

        Set specific permission in Citrix Workspace app for Mac to enable screen sharing. For more information, see System Requirements.

        Multimonitor

        In cases where Desktop Viewer (CDViewer.exe) is in full-screen mode and spanning across multimonitor setups, Citrix Workspace app 2106 or higher (Windows/Linux/Mac) allows the screen picker to select the monitor to share.

        Known limitation:

        • If Desktop Viewer is disabled (either by editing the .ica file template or StoreFront web.config) or if Desktop Lock is being used, multimonitor selection isn’t available in the Microsoft Teams screen picker. SHIFT+F2 hotkey isn’t compatible with multimonitor screen sharing.
        • In Workspace app versions older than 2106, only the primary monitor is shared. You must drag the application in the virtual desktop to the primary monitor for the other peer on the call to see it.
        • Multimonitor screen sharing might not work if you configure Worspace app with the virtual monitor layout feature (logical partition of a single physical monitor). In this case, all virtual monitors are shared as a composite image.
        • Older versions of Workspace app for Windows (1907 up to 2008) also supports sharing of a local application running in the client machine, if it was overlaid on top of Desktop Viewer. This behavior was removed in 2009.6 or higher, and 1912 CU5 or higher.

        Screen sharing

        Screensharing from seamless application:

        If you’re publishing Microsoft Teams as a standalone, seamless application, screen sharing captures the local desktop of your physical endpoint. Citrix Workspace app minimum version 1909 is required.

        App sharing

        Starting with Citrix Workspace app for Windows 2109 and VDA 2109, Microsoft Teams supports screen sharing of specific apps running in the virtual session. To share a specific app:

        1. Navigate to the Microsoft Teams app within your remote session.
        2. Click Share content in your Microsoft Teams UI.
        3. Select an app to share in the meeting. The red border appears around an app you selected and the peers on the call can see the shared app.

        To share a different app, click Share content again and select a new app.

        Note:

        • This feature is available only after the roll-out of an update from Microsoft Teams. For information on ETA, see Microsoft page. When the update is rolled-out by Microsoft, you can check CTX253754 for the documentation update and the announcement.

        • If you minimize an app, Microsoft Teams displays the last image from the shared app. You can maximize the window to resume screen sharing.

        • Screen sharing depends on the VDA-side capturing of the window. The content is then relayed at a maximum rate of 30 frames per second to the Workspace app that forwards the content to the peers or conference server.

        App sharing for Microsoft Teams

        Known limitations with screen sharing of specific app:

        • Mouse pointer is not visible when you are screen sharing an app.
        • HDX 3D Pro is not supported.
        • Restart screen sharing if you resize the virtual desktop screen.
        • If you minimize an app when you are sharing it, only the app icon appears in the screen picker. The thumbnail of the app is not previewed in the screen picker. You cannot share the content and the red border does not appear until you maximize the app.

        Compatibility with app protection The screen sharing of a specific app is compatible with the app protection feature in HDX optimized Microsoft Teams. You can screen share a specific app, if you have launched the app or desktop from a delivery group that has app protection enabled.

        When you click Share content in the Microsoft Teams UI, the screen picker removes the Desktop option. You can only select the Window option to share any open app.

        Note:

        When you launch apps or desktops from a delivery group with app protection enabled, you are not able to see the incoming video or screen sharing.

        Peripherals in Microsoft Teams

        When optimization for Microsoft Teams is active, the Citrix Workspace app accesses the peripherals (headsets, microphones, cameras, speakers, and so forth). Then the peripherals are properly listed in the Microsoft Teams UI (Settings > Devices).

        Optimization mode for Microsoft Teams

        Microsoft Teams does not access the devices directly. Instead, it relies on Workspace app WebRTC media engine for acquiring, capturing, and processing the media. Microsoft Teams lists the devices for the user to select.

        The peripherals that are inserted while Microsoft Teams is active are not selected by default. You have to manually select the peripherals from the Settings > Devices screen of Microsoft Teams UI. After the peripheral is selected, Microsoft Teams caches the information of the peripherals. As a result, the peripherals are automatically selected when you reconnect to a session from the same endpoint.

        Recommendations:

        • Microsoft Teams certified headsets with built-in echo cancellation. In setups with multiple peripherals, where microphone and speakers are on separate devices, there might be an echo. An example is a webcam with a built-in microphone and a monitor with speakers. When using external speakers, place them as far as possible from the microphone and from any surface that might refract the sound into the microphone.
        • Microsoft Teams certified cameras, although Skype for Business certified peripherals are compatible with Microsoft Teams.
        • Citrix Workspace app media engine can’t take advantage of CPU offloading with webcams that perform on-board H.264 encoding -UVC 1.1 and 1.5.

        Note:

        Workspace app 2009.6 for Windows can now acquire peripherals with audio formats with 24-bit or with frequencies above 96 kHz.

        HdxTeams.exe (in Workspace app for Windows 2009 or older) supports only these specific audio device formats (channels, bit depth, and sample rate):

        • Playback Devices: up to 2 channels, 16 bit, frequencies up to 96,000 Hz
        • Recording Devices: up to 4 channels, 16 bit, frequencies up to 96,000 Hz

        Even if one speaker or microphone does not match the expected settings, device enumeration in Teams fails and None displays under Settings > Devices.

        Webrpc logs in HdxTeams.exe show this type of information:

        As a workaround, disable the specific device or:

        1. Open the Sound Control Panel (mmsys.cpl).
        2. Select the playback or recording device.
        3. Go to Properties > Advanced and change the settings to a supported mode.

        Fallback mode

        If Microsoft Teams fails to load in optimized VDI mode (“Citrix HDX Not Connected” in Teams/About/Version), the VDA falls back to legacy HDX technologies like webcam redirection and client audio and microphone redirection. If you are using a Workspace app version/platform OS that does not support Teams optimization, fallback registry keys do not apply. In fallback mode, the peripherals are mapped to the VDA. The peripherals appear to the Microsoft Teams app as if they were locally attached to the virtual desktop.

        You can now granularly control the fallback mechanism by setting the registry keys in the VDA. For information, see Microsoft Teams fallback mode in the list of features managed through the registry.

        This feature requires Teams version 1.3.0.13565 or later.

        To determine if you are in optimized or unoptimized mode when looking at the Settings > Devices tab in Teams, the main difference is the camera name. If Microsoft Teams loaded in unoptimized mode, legacy HDX technologies launch. The webcam name has the Citrix HDX suffix as shown in the following graphic. The speaker and microphone device names might be slightly different (or truncated) when compared to the optimized mode.

        Unoptimization mode for Microsoft Teams

        When legacy HDX technologies are used, Microsoft Teams doesn’t offload audio, video, and screen sharing processing to the endpoint’s Citrix Workspace app WebRTC media engine. Instead, HDX technologies use server-side rendering. Expect high CPU consumption on the VDA when you turn on video. Real-time audio performance might not be optimal.

        Known limitations

        Citrix limitations

        Limitations on Citrix Workspace app:

        • HID buttons - Answer and end call aren’t supported. Volume up and down are supported.
        • Secondary ringer (Teams > Settings > Devices) isn’t supported.
        • QoS settings in the Admin Center for Microsoft Teams don’t apply for VDI users.
        • App protection add-on feature for the Citrix Workspace app prevents outgoing screen sharing and blocks incoming screen share and video.

        Limitation on the VDA:

        • When you configure the Citrix Workspace app High DPI setting to Yes, the redirected video window appears out of place when the monitor’s DPI scaling factor is set to anything above 100%.

        Limitations on Citrix Workspace app and the VDA:

        • Outgoing screen sharing: Application sharing isn’t supported.
        • You can only control the volume of an optimized call using the volume bar on the client machine – not on the VDA.

        Microsoft limitations

        • The options to blur or customize the background aren’t supported.
        • A 3x3 gallery view isn’t supported. Microsoft Teams dependency – contact Microsoft for when to expect a 3x3 grid.
        • Interoperability with Skype for Business is limited to audio calls, no video modality.
        • Incoming and outgoing video stream maximum resolution is 720p. Microsoft Teams dependency – contact Microsoft for when to expect 1080p.
        • PSTN call ringback tone isn’t supported.
        • Media bypass for Direct Routing isn’t supported.
        • Only one video stream from an incoming camera or screen share stream is supported. When there’s an incoming screen share, that screen share is shown instead of the video of the dominant speaker.
        • Broadcast and live event producer and presenter roles aren’t supported. Attendee role is supported but not optimized (renders on the VDA instead).
        • The zoom in and zoom out function in Microsoft Teams isn’t supported.

        Citrix and Microsoft limitations

        • When doing screen sharing, the option include system audio isn’t available.
        • Pop out chat (also known as multi-window chat or the new meeting experience) isn’t supported.
        • Breakout rooms are supported for VDI participants. Microsoft Teams doesn’t support breakout rooms if the organizer is a VDI user.
        • Give control and take control: Not supported during a desktop screen sharing or application sharing session. Supported only during a PowerPoint sharing session.
        • E911 and Location-Based Routing are not supported.
        • Live captions and live transcriptions are not supported.

        Additional information

        The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Citrix product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content.

        DIESER DIENST KANN ÜBERSETZUNGEN ENTHALTEN, DIE VON GOOGLE BEREITGESTELLT WERDEN. GOOGLE LEHNT JEDE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG IN BEZUG AUF DIE ÜBERSETZUNGEN AB, EINSCHLIESSLICH JEGLICHER GEWÄHRLEISTUNG DER GENAUIGKEIT, ZUVERLÄSSIGKEIT UND JEGLICHER STILLSCHWEIGENDEN GEWÄHRLEISTUNG DER MARKTGÄNGIGKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN DRITTER.

        CE SERVICE PEUT CONTENIR DES TRADUCTIONS FOURNIES PAR GOOGLE. GOOGLE EXCLUT TOUTE GARANTIE RELATIVE AUX TRADUCTIONS, EXPRESSE OU IMPLICITE, Y COMPRIS TOUTE GARANTIE D'EXACTITUDE, DE FIABILITÉ ET TOUTE GARANTIE IMPLICITE DE QUALITÉ MARCHANDE, D'ADÉQUATION À UN USAGE PARTICULIER ET D'ABSENCE DE CONTREFAÇON.

        ESTE SERVICIO PUEDE CONTENER TRADUCCIONES CON TECNOLOGÍA DE GOOGLE. GOOGLE RENUNCIA A TODAS LAS GARANTÍAS RELACIONADAS CON LAS TRADUCCIONES, TANTO IMPLÍCITAS COMO EXPLÍCITAS, INCLUIDAS LAS GARANTÍAS DE EXACTITUD, FIABILIDAD Y OTRAS GARANTÍAS IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN FIN EN PARTICULAR Y AUSENCIA DE INFRACCIÓN DE DERECHOS.

        本服务可能包含由 Google 提供技术支持的翻译。Google 对这些翻译内容不做任何明示或暗示的保证,包括对准确性、可靠性的任何保证以及对适销性、特定用途的适用性和非侵权性的任何暗示保证。

        このサービスには、Google が提供する翻訳が含まれている可能性があります。Google は翻訳について、明示的か黙示的かを問わず、精度と信頼性に関するあらゆる保証、および商品性、特定目的への適合性、第三者の権利を侵害しないことに関するあらゆる黙示的保証を含め、一切保証しません。

        ESTE SERVIÇO PODE CONTER TRADUÇÕES FORNECIDAS PELO GOOGLE. O GOOGLE SE EXIME DE TODAS AS GARANTIAS RELACIONADAS COM AS TRADUÇÕES, EXPRESSAS OU IMPLÍCITAS, INCLUINDO QUALQUER GARANTIA DE PRECISÃO, CONFIABILIDADE E QUALQUER GARANTIA IMPLÍCITA DE COMERCIALIZAÇÃO, ADEQUAÇÃO A UM PROPÓSITO ESPECÍFICO E NÃO INFRAÇÃO.

        Источник: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html

        Products

        CCleaner logo

        CCleaner v5.87

        Optimize, clean, protect and speed up your PC

        Professional

        Inject instant speed into your machine by removing the unnecessary files taking up room on your hard drive. Clear out errors and broken settings to improve stability. Boost your browser and help protect your privacy by securely erasing tracking cookies and history.

        Includes:

        • Real-time monitoring
        • Scheduled cleaning

        So your PC stays clean without you having to do a thing!

        Buy Now

        Professional Trial

        Use CCleaner Professional for 14 days, for free. Once your trial is over you'll automatically drop down to CCleaner Free, so it won't cost you a thing.

        Download

        Free

        Install our standard version of CCleaner.

        Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution!

        Runs on Microsoft Windows 10, 8.1, and 7. Including both 32-bit and 64-bit versions.

        Back to top
        CCleaner logo

        CCleaner v1.18

        Optimize, clean, protect and speed up your Mac

        Professional

        Inject instant speed into your machine by removing the unnecessary files taking up room on your hard drive. Clear out errors and broken settings to improve stability. Boost your browser and help protect your privacy by securely erasing tracking cookies and history.

        Includes:

        • Real-time monitoring
        • Scheduled cleaning
        • Automatic updates

        So your Mac stays clean without you having to do a thing!

        Buy Now

        Free

        Install our standard version of CCleaner.

        Download

        Requires an Apple Mac running 64-bit macOS 10.10 and above.

        Back to top
        CCleaner Browser - product logo

        CCleaner Browser

        A free, fast and powerful browser from the makers of CCleaner

        Free Version (Only)

        Enjoy cleaner, faster online browsing. Delete browser files and data automatically, disable trackers, and block malicious websites. Load pages faster by disabling pop-ups with ad-block, and stop your PC slowing down when you browse online by optimizing its performance.

        Includes:

        • Access to CCleaner app with one click
        • Optimization of your PC with ‘Performance Manager’
        • Faster web page load times with ‘Adblock’
        • Built-in privacy and security tools
        • Fast and powerful browsing that works with CCleaner.

        Download

        Back to top
        Kamo - product logo

        Kamo

        Protect your privacy by stopping online tracking

        KAMO

        Kamo can do what private browsing, adblockers, VPNs, and antivirus programs can’t. Not much can block browser fingerprinting technology from pushing up the prices you see online and tracking your online activity with up to 99% accuracy, but Kamo can and does.

        What else does Kamo do?

        • Syncs with most web browsers on your computer
        • Stops companies from tracking what you do on your PC

        Use the full version of Kamo for 14 days for free: no credit card required. Once your trial is over, you’ll need to purchase Kamo to continue blocking online trackers and retain your online privacy.

        Free Trial

        Back to top

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to top
        Recuva - product logo

        Recuva v1.53

        Restore accidentally deleted files quickly and easily

        Professional

        Rescue valuable files fast – even if they were deleted weeks ago. Restore pictures, music, documents, videos, emails or any other file type from PCs, portable or rewritable media.

        Includes:

        • Deep scan file recovery
        • Priority technical support

        So you never have to worry about losing a file again!

        Buy Now

        Free

        Install our standard version of Recuva.

        Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to top
        Speccy - product logo

        Speccy v1.32

        Fast, lightweight, advanced system information at your fingertips

        Professional

        Get detailed information on every piece of hardware in your computer so you can make informed purchasing and upgrade decisions - and even spot problems before they occur.

        Includes:

        • Advanced PC insights dashboard
        • Automatic updates
        • Premium support

        So you will never have to trawl through your computer for stats again!

        Buy Now

        Free

        Install our standard version of Speccy.

        Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to topBack to top

        Requires Windows 10, 8.1, 8 and 7 including both 32-bit and 64-bit versions.

        Back to topBack to topBack to topBack to topBack to top
        Источник: https://www.ccleaner.com/download

        WVD service principal name Powershell

        Windows virtual desktop is GA and already there are tons of blog post on how to install windows virtual desktop, first steps on windows virtual desktop.

        I see a huge demand on WVD, Customers wants to try this and see the difference between the traditional RDS setup.  And yes its all Azure but thanks can be build and tested. and there comes all the different builds and setups. Different places to go, and management is a pain no GUI available from Microsoft there is only PowerShell. Not a bad thing but testing the windows virtual desktop leaves me multiple tenants and host pools dead.

        Well I thought lets do a Step By Step windows virtual desktop, Well not exactly I’ll believe you can follow the wizard in Azure and Do all the prereq’s by your self. In this blog post it could be that not all host pools and tenant names are the same as I had a lot of test WVD configs.

        As we all know the Infrastructure that is needed for windows virtual desktop, we also know that a lot can go wrong and then where to look ?

        image

        So to start with windows virtual desktop I created a little Powershell script that does step 1

        Install-Module -Name Microsoft.RDInfra.RDPowerShell
        Import-Module -Name Microsoft.RDInfra.RDPowerShell

        #Setup Settings, TenantName of WVD tenant, Hostpool name
        $Hostpool       = “WVDpool01”
        $HPFriendlyName  = “Win10 + O356”
        $TenantName     = “ClusterMVP”
        $TenantGroupName = “Default Tenant Group”
        $AppGroupName    = “Desktop Application Group”
        $AadTenantId    = “111111-2222222-33333”
        $subscriptionId = “111111-2222222-33333″
        $UPN=”[email protected]

        #Sign in to Windows Virtual Desktop
        Add-RdsAccount -DeploymentUrl “https://rdbroker.wvd.microsoft.com&#8221;

        #New Tenant Keep in mind that Access rights need to be set before doing the next step.
        New-RdsTenant -Name $tenantName -AadTenantId $AadTenantId -AzureSubscriptionId $subscriptionId
        #
        #Hostpool
        #Create new Hostpool
        New-RdsHostPool -TenantName $tenantName -FriendlyName $HPFriendlyName -name $hostpool -ValidationEnv $true
        Get-RdsHostPool -TenantName $tenantName

         

        When Doing these steps I already got errors not on the script but on the basic steps

        image

        Get-RdsTenant : User is not authorized to query the management service.

        The user is global admin uber god in Azure and in the domain. Well you need to give the account that you are using for the installation access. in the Virtual Desktop APP.

        image

        I like to see what happened so often I use an extra Get- to see the values .

        But these errors I hate them, Why can it be so hare to deploy some machines and use RDS, Well it’s a 3 fase installer.

        • Granting the Domain + subscription
        • Powershell stuff to prep things
        • Install Azure VM’s

        And then the setup needs to embed in your infrastructure. Think I saw a lot of issues, during the first RDMI rollouts I thought this is complicated a created a full rollout script, but things changed during the program and at some points I could not get windows virtual desktop Installed several tries etc not good,

        Tons of failure on all kind of errors samples are below.

        —————————————————————————————–

        VM has reported a failure when processing extension ‘joindomain’

        the error is Deployment error: “VMExtensionProvisioningError”.
        Details error message are:
        {“code”:”DeploymentFailed”,”message”:

        Operation ‘Update VM’ is not allowed on VM ‘FIBWVD-0’ since the VM is marked for deletion.

        “The resource operation completed with terminal provisioning state ‘Failed’.”

        statusCode”: “Conflict”,

        “VM has reported a failure when processing extension ‘joindomain’. Error message:
        \”Exception(s) occured while joining Domain

        Error message: \\\”DSC Configuration

        ——————————————————————————————–

        Well I have multiple Domain names added to my Azure AD and Running a VM as DC with multiple domain names.  Azure Connect syncs them to Azure AD but standard well it depends, That’s why I thought lets create a backwards blog about windows virtual desktop #WVD.

        More about errors can be found here 

        https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-role-service#common-error-scenarios

         

        During all my test I noticed my Tenant Names where in use and different all meshed up. Removing them is easy but also in steps.

        First my sample here

        Get-RdsHostPool -TenantName ACACOMPUTERS

        image

        This shows you the host pools for the login user

        get-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        So removing the hostpool is not

        Remove-RdsHostPool -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        That seems logical, then lets see the application groups

        get-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        There are Two application Groups : the default one and an extra created.

        AppGroupName    : Desktop Application Group

        AppGroupName    : MVP-WVD

        Remove-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool -Name “MVP-WVD” –Verbose

        image

        even with the verbose nothing no warning no error.

        Remove-RdsHostPool -TenantName ACAComputers -HostPoolName ACA-HostPool -Verbose

        image

        Now the Hostpool can be removed and no warning

         

        image

        Setting up a fresh new installation of WVD is easy, but the first setup is a bit painful but if you follow the steps you can’t go wrong.

        GO to the  https://rdweb.wvd.microsoft.com Add the Azure AD ID keep in mind if you are running a CSP subscription or you are not the owner it may that your account is blocked to create enterprise apps then this will fail and you can’t setup WVD.

        image

        Do this for Client and Server

        image

        Then give the users access to the Windows Virtual Desktop App, these are the installation accounts.

        image

        Open the app and add users or groups.

        image

         

        image

        Now you can sign in and start the deployment

        #Sign in to Windows Virtual Desktop
        Add-RdsAccount -DeploymentUrl https://rdbroker.wvd.microsoft.com

        image

         

        image

         

         

        You can also use a service principal name

        #############

        Set users or Create service principal name

        # create the service principal:
        $aadContext = Connect-AzureAD
        $svcPrincipal = New-AzureADApplication -AvailableToOtherTenants $true -DisplayName “Windows Virtual Desktop Svc Principal”
        $svcPrincipalCreds = New-AzureADApplicationPasswordCredential -ObjectId $svcPrincipal.ObjectId

        #Here are the three credentials you should write down and the cmdlets you need to run to get them
        $svcPrincipalCreds.Value
        $aadContext.TenantId.Guid
        $svcPrincipal.AppId

        #Set Rolassignment
        New-RdsRoleAssignment -RoleDefinitionName “RDS Owner” -ApplicationId $svcPrincipal.AppId -TenantName $tenantName

        #Sign in with the service principal
        $creds = New-Object System.Management.Automation.PSCredential($svcPrincipal.AppId, (ConvertTo-SecureString $svcPrincipalCreds.Value -AsPlainText -Force))
        Add-RdsAccount -DeploymentUrl “https://rdbroker.wvd.microsoft.com” -Credential $creds -ServicePrincipal -AadTenantId $aadContext.TenantId.Guid

        image

        This is All perfect But often I noticed that the WVD host where added to the domain but failed in something, the VM was fine and there was a folder with the deployment agent. and this got me thinking what If you install this on what ever OS, You could even use the WVD portal to connect to your own laptop.

         

        The manual add Server to the host pool is also a process when you start with 1 server and add later extra servers to the pool.

        but we will need a token to add the WVD host to the pool, like in RDS add the Role not the Role is an agent that is running on the VM

        image

        There are several ways to export the key I like them to capture this in screen and to the clipboard.

        $WVDToken = New-RdsRegistrationInfo -TenantName $tenantName -HostPoolName $hostpool -ExpirationHours 2
        $WVDToken.Token

        Configure Virtual Desktop Support

        Virtual desktop support is an opt-in feature of Tableau Desktop 10.5 and later and Tableau Prep Builder 2018.2.1 and later that gives you the ability to optimize your installations of Tableau for non-persistent virtual desktops, or for computers that are regularly reimaged.

        Starting with version 2020.1, virtual desktop can be configured for login-based license management (no product keys needed). This is the preferred, and often the required, method to implement a virtual deployment of Tableau Desktop when end users are not issued product keys. For more information, see Activate Tableau using Login-based License Management(Link opens in a new window).

        With virtual desktop support enabled, Tableau licenses or login-based license management license leases are automatically returned after a predetermined amount of time. This means that you do not need to manually refresh or deactivate the product key. The requirement that Tableau communicate with the hosted service means that you must periodically connect to the Internet.

        Without virtual desktop support, an activated Tableau license or login-based license management license lease remains in use until the license is deactivated or the lease term expires. This means that with frequently recycled virtual machines (VMs) and regularly reimaged computers, you may never have the opportunity to deactivate the license before the system is recreated, and the license activation remains in effect resulting in a maximum activation error.

        How virtual desktop support works

        When virtual desktop support is enabled, Tableau Desktop or Tableau Prep Builder periodically contacts a Tableau-hosted authorization-to-run (ATR) service to verify that Tableau is authorized to run, based on its license. When virtual desktop is configured to also use login-based license management, Tableau Online and Tableau Server work as a proxy to the ATR service to verify that Tableau is authorized to run with a valid Tableau Online or Tableau Server Creator user.

        The ATR service verifies the license or whether the user is a valid Creator user, and the length of the authorization window. As long as this communication is successful, Tableau runs without any impact to the user. The diagrams below show the communication process between the client and licensing components.

        Virtual desktop support and the ATR service without login-based license management

        1. Tableau Desktop or Tableau Prep Builder contacts the ATR service to verify that Tableau Desktop or Tableau Prep Builder is authorized to run.

        2. The ATR service contacts the Tableau Licensing Service to verify that the license is valid.

        3. The ATR service determines the length of the authorization to run window.

        4. If valid, the ATR service allows you to use Tableau Desktop or Tableau Prep Builder.

        Login-based license management with Tableau Online

        Login-based license management with Tableau Server

        1. You install Tableau Desktop or Tableau Prep Builder and select Activate with your credentials. You sign into your Tableau Online or Tableau Server site.

        2. Tableau Online or Tableau Server verifies that you are a Creator. If not, you get an error. If yes, Tableau Online or Tableau Server communicates with the ATR service.

        3. The ATR service returns an ATR lease to Tableau Online or Tableau Server.

        4. Tableau Online or Tableau Server provides an ATR lease to Tableau Desktop or Tableau Prep Builder to finalize activation.

        Requested duration

        By default, an instance of Tableau Desktop or Tableau Prep Builder is given a 14 day authorization window during which it is authorized to run. This means that after the initial authorization, you could use Tableau without any network connection for 14 days before the activation expired. The authorization checks are attempted regularly, and each time a check is successful, the authorization window is reset to its full length. This happens without any impact to you, unless there have been no successful checks and the window is nearing its expiration, in which case a warning message lets you know that you need to connect Tableau to the network so the authorization can be confirmed. The 14 day default is typically not a good value for deploying virtual desktop where you receive a new VM with every use. For more information, see Requested duration settings.

        The length of the authorization window is determined by the value of the requested duration. By default, the requested duration is 14 days (1,209,600 seconds), but you can configure this to fit your environment depending on how often a user will be receiving a new VM or if the Tableau Desktop is of a persistent nature.

        Note: If you use both Tableau Desktop and Tableau Prep Builder, setting the requested duration for Tableau Desktop also sets this same duration for Tableau Prep Builder and vice-versa.

        Requested duration settings

        You set the requested duration in seconds. The minimum requested duration you can set is 4 hours (14,400 seconds) and the maximum is six months (15,552,000 seconds). Use the following guidelines to determine how to set the requested duration setting for your users:

        • For most non-shared computers, especially those that are sometimes offline for several weeks at a time, set the requested duration to three to six months (7,776,000 – 15,552,000 seconds). A longer duration will allow the user to continue to use Tableau for an extended time without an internet connection.

        • For computers that are reimaged approximately once per month, set the requested duration to 30 days (2,592,000 seconds).

        • For virtual desktops that are recycled nightly, set the requested duration to the minimum of 4 hours (14,400 seconds). This will allow you to reuse your product keys each morning and eliminate the need to remember to deactivate them each evening before the virtual desktops are recycled.

        Virtual machines and product keys

        The benefit of using virtual desktop support is that for environments that regularly recycle their VMs, you can set a duration short enough to expire the license activation before the desktop is reused. This means that you do not use up all your activations. You will still need to enter the product key to run Tableau after the desktop is recycled. Login-based license management can improve the end-user experience in this scenario by requesting a sign in to Tableau Online or Tableau Server to activate Tableau Desktop or Tableau Prep Builder instead of entering a product key.

        Note: When using virtual desktop with subscription licenses, you cannot refresh your product keys. To renew a subscription or make licensing changes, you must identify the new product key in the Tableau Customer Portal and activate it.

        How to use virtual desktop support

        Virtual desktop support is an opt-in feature if you're not using login-based license management, so you need to enable the feature in order to use it (it is disabled by default). If you're using login-based license management, see Activate Tableau using Login-based License Management(Link opens in a new window). The ways to enable virtual desktop when not using login-based license management depend on whether you are running Tableau on Windows or on the Mac:

        On Windows you can enable and configure virtual desktop support:

        • At installation of Tableau Desktop and Tableau Prep Builder using command line install switches to enable virtual desktop support and specify a requested duration.

        • After installation, by editing the Windows registry to enable virtual desktop support and specify a requested duration.

        On a Mac you can enable and configure virtual desktop support:

        • After installation of Tableau Desktop and Tableau Prep Builder using commands.

        Tableau Desktop and Tableau Prep Builder on Windows

        There are three methods for setting the virtual desktop flags:

        Enable virtual desktop support at install

        Run the installer file from the computer's command line as an administrator, and include the switch if login-based license management is not being used (version 2019.4 and earlier, or manually disabled). The switch is not needed if login-based license management is configured on Tableau Desktop. To use a duration length other than the default of 14 days, include the switch. If you need to extract the .msi files, follow the instructions to Extract and run the Windows (MSI) installer .

        You must run the command from the directory where the file is located or specify a full path to the location of the file on the computer. Do not run the setup program from a shared directory on your network. Instead, download the file to a directory on the computer where you're installing.

        The has a minimum setting of 4 hours (14,400 seconds). The following example shows the Windows installer command that enables automatic license deactivation and set the duration to 12 hours (43,200 seconds):

        or

        When creating a primary image for a large virtual deployment, the above settings are appropriate and no product key activation should be completed. When using a new VM, each end user will enter the product key or sign in to Tableau Desktop or Tableau Prep Builder if login-based license management is enabled.

        Enable virtual desktop support by editing the registry

        If Tableau Desktop or Tableau Prep Builder is already installed, you can still enable virtual desktop support by editing the Windows registry to add an entry for . To change the default duration a license activation is authorized for, you can add an entry for .

        1. As an administrator on the computer running Tableau Desktop or Tableau Prep Builder, make a backup of the registry file before you make any changes to it.

        2. Edit the registry, and in , create a new hive named with these values:

          • Name: Add a DWORD (32-bit) value named .

          • Data: Add .

          • Name: Add a DWORD (32-bit) value named .

          • Data: Add a number of seconds the duration should last. For example, add to set a duration of 12 hours.

          The illustration below shows what the hive looks like in the registry editor.

        3. Restart Tableau so that the changes take effect.

        Enable virtual desktop support by using the atr tool

        If Tableau Desktop or Tableau Prep Builder is already installed, you can still enable virtual desktop support from the Windows command prompt. The atrdiag.exe program resides in the \bin directory for Windows and is a tool specific to the virtual desktop and login-based license management settings. The atrdiag.exe program can report on the values selected, change virtual desktop configuration settings, and initially configure virtual desktop. If Tableau Technical Support is needed, providing the output from the atr tool is often helpful.

        Note: Tableau Prep Builder must be installed on the same computer with Tableau Desktop in order to use atrdiag.exe with Tableau Prep Builder.

        1. Sign in on the computer running Tableau Desktop as an administrator.

        2. At a command prompt, navigate to the directory where Tableau Desktop is installed:

        3. At a command prompt, enable the ATR service:

        4. Set the duration, in seconds, that the license activation is authorized for. (For example, use 43200 to set a duration of 12 hours.)

        5. Restart Tableau so that the changes take effect.

        Disable virtual desktop support by using the atr tool

        If you no longer want to use the virtual desktop support feature, you can disable it.

        1. Shut down Tableau Desktop on the computer where you want to disable virtual desktop support.

        2. Open the Windows Command Prompt as an administrator, and then navigate to the directory where Tableau Desktop is installed:

        3. At a command prompt, run the following command to turn off the ATR service:

        4. At a command prompt, run the following command:

        5. Start Tableau Desktop.

        6. On the License Has Changed dialog, click Exit.

        7. Restart Tableau so that the changes take effect.

        8. On the Help menu, click Manage Product Keys to see if you can deactivate the product key.

        Tableau Desktop and Tableau Prep Builder on Mac

        Enable by updating the preference file

        To enable virtual desktop support on the Mac, run the following commands in a terminal window and then install or restart Tableau Desktop or Tableau Prep Builder:

        Troubleshoot virtual desktop

        If you encounter issues when configuring or using virtual desktop, you can collect diagnostic information about the computer that is running Tableau Prep Builder or Tableau Desktop using the virtual desktop diagnostic tool (atrdiag).

        You can verify that virtual desktop is enabled and view the value set for the requested duration seconds in use for Tableau Desktop activation. The TTL Start and TTL End values reflect the current lease being used on the virtual machine (VM) running Tableau Desktop. The commands provided below will capture the state of your virtual desktop support installation, regardless of whether you have installed Tableau Desktop or Tableau Prep Builder.

        Collect virtual desktop diagnostics on Windows

        1. Open a Command Prompt as an administrator.
        2. Navigate to the Tableau binaries () directory, using the following command:
        3. Run the following command:

          To optionally save the output to a file:

        Collect virtual desktop diagnostics on Mac

        1. Open the Terminal app.
        2. Navigate to the directory that contains the atrdiag tool, using the following command:
        3. Run the following command:

          To optionally save the output to a file:

        To learn more about resolving issues with Tableau Desktop installation, see Troubleshoot Your Tableau Desktop or Tableau Prep Builder Installation.

        Источник: https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_license_deactivate.htm

        In an enterprise environment, users do not need to worry about Windows activation on their work devices. That’s one of the many jobs for the IT department. It’s another story with personal devices. Every user should be prepared: a laptop might be lost, a PC motherboard stop working, and so on. In such cases, actually in any case when you have a valid, transferable digital license, you can reactivate your device after major hardware changes, or activate Windows 10 on a new device. You just need to be prepared.

        Many of you geeks have a Visual Studio subscription (formerly known as MSDN), with lots of product keys to use. Taking care of your digital licenses is equally important whether you have just one device, or a complex home network with multiple devices.

        OEM, Retail, MAK?

        Here’s a good rule of thumb: If a Windows 10 device comes with Windows preinstalled , it is a so-called OEM (Original Equipment Manufacturer) license. If Windows 10 was purchased from Microsoft or some licensed retailer, it is a Retail license. One exception: so-called System Builder versions which are also OEM licenses. All single use Visual Studio subscription keys are also Retail keys. Multiple Activation Keys (MAK) are also shown as Retail in the Windows Software License Manager (slmgr.vbs).

        OEM licenses can’t be transferred to new devices, and they cannot be used to reactivate Windows 10 when major hardware changes such as replacing motherboards occur. One somewhat grey area is Microsoft’s tech support: on various tech sites and forums you can read about users claiming that talking to the activation helpline succeeded, and an OEM license reactivated even after both motherboard and CPU were swapped out and automatic activation failed.

        To check if you have an OEM, non-transferrable license, enter the following command in an elevated PowerShell or Command Prompt:

        slmgr /dli

        Software License Manager opens a prompt telling about your license. If it shows that your license is from OEM channel, you cannot transfer the license:

        What is a Digital License?

        When Windows 10 is activated for the first time, that device gets a valid digital license for the activated edition, for the lifetime of that device. However, its hardware ID (HWID) must remain the same (no major hardware changes). Microsoft has 15 different hardware IDs to be used in various scenarios, the one that determines if a digital license on a device is valid is hardware ID 3. See the full list: Specifying Hardware IDs for a Computer.

        Notice that disk drives are not included in the HWID. This means that a user is free to replace an HDD or SSD without losing his or her Windows 10 license. That said, a digital license is edition specific, but not language, version or bit architecture specific. You can replace your HDD containing a licensed 64-bit Windows 10 Pro version 1809 in English, and install a 32-bit Windows 10 Pro version 1909 in Swedish on a new HDD. Windows 10 will be automatically activated, based on the HWID and the existing digital license.

        Taking care of Digital Licenses

        Even if you use only a local account to sign in to Windows 10, it is important to create a Microsoft account, if you do not have one already. This is the only way to be sure that license can be reused for reactivation after replacing hardware or transferring that license to a new device. As an example, I have just performed a clean install of W10 Pro on a Hyper-V virtual machine, although exactly the same applies to physical devices, too. The first thing to do is to change the device name to something that will later clearly tell me which machine this is. I renamed the machine to VM-W10PRO07, it being the seventh W10 Pro VM I have activated. When transferring the license, it is important that you know the device name for the license you wish to transfer.

        After the restart required by renaming the machine, I activated this VM using one of my MAK keys for the Windows 10 Pro edition. At this point, activation status is shown as Activated with a digital license:

        Click screenshots to open enlarged in a new tab.

        If I now clicked the Add an account under Add a Microsoft Account link, my local account would be switched to a Microsoft Account, and this license would be registered for that MS account. If a Microsoft account is what you want to use, click Add an account and follow the on-screen instructions to sign in. However, if you are like me and want to continue using a local account, do not click that link! See this earlier Win10.guru story, scroll down to title Why not best of both?, and see how to add a Microsoft account to Windows 10 without switching a local account to a Microsoft account: Microsoft Account vs. Local Account – Why not both?

        Whichever method you choose, after switching to a Microsoft account or adding an MS account to a local account, the activation status changes to Activated with a digital license linked to your Microsoft account:

        One last check: I will go to https://account.microsoft.com/devices/ and check that the new machine, and its digital license have been added to my MS account:

        That’s it, the digital license is now ready to be transferred.

        Transferring a Digital License

        Let’s say that my sample machine was a real, physical machine, and that it died. A Retail license registered on my MS account now belongs to a device that does not exist anymore. I can assemble a new PC, clean-install Windows 10 Pro on it selecting I don’t have a product key, and when I get to its desktop for the first time, rename that PC and restart. Then, I can either switch to a Microsoft account or add an MS account to a local account.

        When all that is done, I go to Activation settings, and select the activation troubleshooter:

        At the next prompt, I select I recently changed hardware on this device link:

        A list of devices registered to my MS account is then shown. I select my sample VM, and click Activate:

        The new clean installation on the new device is now activated:

        Easy and fast!

        That’s it, geeks. Take care of your licenses, register them on your MS account using a clear, explanatory device name.

        Kari

         

        Author: Kari Finn

        A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site TenForums.com.

        Twitter

        Related

        Источник: https://win10.guru/windows-10-digital-license-how-to-transfer/

        Best virtual desktop services 2021

        RSS

        TechRadar is supported by its audience. When you purchase through links on our site, we may earn an affiliate commission. Learn more

        By Christian Rigg last updated

        Hosted desktop solutions for your company’s needs

        The best virtual desktop services and Desktop as a Service (DaaS) providers make it simple and easy to ensure secure and cost-effective solutions for remote working.

        Desktop as a Service (DaaS) is not an entirely new phenomenon, but it’s certainly experienced significant growth in the past few years, both in terms of technology and market share, and especially more recently due to the pandemic.

        The reason for their take-up is that virtual desktops are a secure and flexible means for businesses to support a remote work staff and Bring Your Own Device (BYOD) practices. Of course, the pandemic and move to working from home has also accelerated take up of this technology.

        In a DaaS framework, a provider takes care of the technical and logistical aspects of cloud desktop and app environments, and a business rents these services for less than the cost of building and maintaining them itself. We’ve combed through the many DaaS providers on the market and chosen six of the best, based on services, security, scalability, and cost. 

        1. Amazon WorkSpaces

        Highly flexible pricing with payments by the hour

        Reasons to buy

        +Scale CPU, GPU, and storage as needed+Hourly pricing: pay what you use+24/7 phone/chat/email customer support+Includes AWS Security Hub and Application Manager

        Reasons to avoid

        -No text/data transfer from local machine to VM-Additional technical support is paid-Can only add users/assign desktops manually

        Amazon WorkSpaces is an industry leader in DaaS, with great features and pricing options for small businesses. It makes use of a PCoIP protocol for compression and encryption of data transfers, and WorkSpaces also uses Amazon’s SDX protocol. 

        Customers can provision Linux and Windows virtual machines, while AWS runs on Windows, macOS, Chromebook, iPad, Amazon and Android tablets, Chrome and Firefox. Both operating systems come bundled with default software like Internet Explorer, while Microsoft Office and others can be added for a monthly fee.

        One of the biggest advantages with Amazon WorkSpaces is the flexible pricing. Businesses that are interested in trying out the services can take advantage of a free tier with two workspaces, for up to 40 hours per month. There are several payment options based on disk size, number of CPUs, memory, and whether you bring your own licenses (BYOL).

        Bundled services can be charged monthly or even hourly, so you pay for what you use. There are no one-time fees and no commitments: you can cancel your subscription at any time.

        2. Citrix Virtual Apps and Desktops

        A trusted name in DaaS, well suited to a mobile workforce

        Reasons to buy

        +Great BYOD support+Supports remote access to physical machines+Encrypted data, never stored on device+Good centralized management

        Reasons to avoid

        -Minimum of 25 users-No autoscaling 

        Citrix is another big name in DaaS, and the Citrix Virtual Apps and Desktops platform has great hosted desktop services that are particularly well suited to a mobile workforce. Users can connect from Android, Windows, macOS, Chrome OS, and iOS/iPadOS and seamlessly switch between devices while maintaining workflow: the service adapts to different screen sizes, so employees can connect on a computer, tablet, or even mobile phone. 

        Plans vary by number of users, applications, features, and licenses. A Standalone version, deployed as a cloud service, includes Windows and Linux provisions, while the Workspace Premium Plus solution adds open support for any public cloud or hypervisor and is marketed as a comprehensive digital platform for managing Windows, Linux, web, SaaS, and mobile apps.

        Citrix also integrates with and virtualizes collaboration and communication tools like Skype for Business and can manage graphics-intensive jobs, with support for Intel, AMD, and NVIDIA GPUs. 

        3. Azure Virtual Desktop

        Customize plans to meet your needs and budget

        Reasons to buy

        +No minimum users or machines+Excellent backup and data safety+Supports Windows, Apple, and Android devices

        Reasons to avoid

        -Cloud-only, no on-site option-Windows only; no Linux provisions

        Azure Virtual Desktop enables businesses to provision Windows 7 or 10 virtual machines, complete with support for Office 365 and many third-party applications. WVD has excellent device support as well: Windows, iOS/iPadOS, MacOS, Chrome OS, Android, and all major browsers. 

        Pricing depends on region, operating system, virtual machine (CPU, GPU, and memory), and usage (in hours, days, or months) and is thus flexible. There are discounts available for one- and three-year subscriptions, or you can pay as you go. The Windows Virtual Desktop website even has a comprehensive calculator to estimate your costs based on your business’s needs. 

        With Azure, customers benefit from great backup and recovery features, making this one of the best providers for data security. Scheduled backups, snapshots, offline and encrypted backups of virtual machines, and automatic failover all help mitigate the risks of data corruption or loss. 

        4. VMWare Horizon Cloud

        DaaS from the desktop virtualization giant

        Reasons to buy

        +Supports all major devices and browsers+Available on-site, IBM Cloud, or Microsoft Azure+Scale complex custom machines easily

        Reasons to avoid

        -End users cannot up/downgrade computer power-BYOL only

        A name well known in virtualization, VMWare Horizon Cloud is available as a standalone, on-premises service or hosted on IBM Cloud or Microsoft Azure. Unlike previous providers, however, it is strictly BYOL, as VMWare does not plan to sell Windows licenses. 

        Horizon has great features for scalability and maintaining uptime. Instant Clone, for example, enables customers to rapidly deploy customized virtual machines by cloning from a parent or “master image” machine. The resulting machines are fully independent, so they can be further customized as necessary for easy scalability. Clones can also share a virtual disk and thus consume less storage, a practical money-saving feature.

        Pricing depends on user style (named vs. concurrent), payment plan (pay as you go or contractual), and edition (Standard, Advanced, and Enterprise). More advanced editions include features like Linux provisioning, virtualization for Skype for Business, and SSO and MF authentication. 

        5. Nutanix XI Frame

        Easily set up your infrastructure

        Reasons to buy

        +Simplified approach to VM creation and use+Strong integration with clouds, identity providers+Auto-scaling and auto-decommission

        Reasons to avoid

        -No native apps-Windows 10 only

        Nutanix XI Frame is a great choice for anybody who’s wary of the complexity and IT know-how necessary to set up and take advantage of a full-featured DaaS environment. The company aims to provide a more streamline experience to admins, without sacrificing end-user experience and functionality.

        Источник: https://www.techradar.com/best/virtual-desktop-services
        Set-Clipboard
        ##
        $WVDToken.Token

        #When using the Clipboard then use this.
        Export-RdsRegistrationInfo -TenantName $tenantName -HostPoolName 4k youtube to mp3 license key Freegate Free Download service principal name Powershell

        Windows virtual desktop is GA and already there are tons of blog post on how to install windows virtual desktop, first steps on windows virtual desktop.

        I see a huge demand on WVD, Customers wants to try this and see the difference between the traditional RDS setup.  And yes its all Azure but thanks can be build and tested. and there comes all the different builds and setups. Different places to go, and management is a pain no GUI available from Microsoft there is only PowerShell. Not a bad thing but testing the windows virtual desktop leaves me multiple tenants and host pools dead.

        Well I thought lets do a Step By Step windows virtual desktop, Well not exactly I’ll believe you can follow the wizard in Azure and Do all the prereq’s by your self. In this blog post it could be that not all host pools and tenant names are the same as I had a lot of test WVD configs.

        As we all know the Infrastructure that is needed for windows virtual desktop, we also know that a lot can go wrong and then where to look ?

        image

        So to start with windows virtual desktop I created a little Powershell script that does step 1

        Install-Module -Name Microsoft.RDInfra.RDPowerShell
        Import-Module -Name Microsoft.RDInfra.RDPowerShell

        #Setup Settings, TenantName of WVD tenant, Hostpool name
        $Hostpool       = “WVDpool01”
        $HPFriendlyName  = “Win10 + O356”
        $TenantName     = “ClusterMVP”
        $TenantGroupName = “Default Tenant Group”
        $AppGroupName    = “Desktop Application Group”
        $AadTenantId    = “111111-2222222-33333”
        $subscriptionId = “111111-2222222-33333″
        $UPN=”[email protected]

        #Sign in to Windows Virtual Desktop
        Add-RdsAccount -DeploymentUrl “https://rdbroker.wvd.microsoft.com&#8221;

        #New Tenant Keep in mind that Access rights need to be set before doing the next step.
        New-RdsTenant -Name $tenantName -AadTenantId $AadTenantId -AzureSubscriptionId $subscriptionId
        #
        #Hostpool
        #Create new Hostpool
        New-RdsHostPool -TenantName $tenantName -FriendlyName $HPFriendlyName -name $hostpool -ValidationEnv $true
        Get-RdsHostPool -TenantName $tenantName

         

        When Doing these steps I already got errors not on the script but on the basic steps

        image

        Get-RdsTenant : User is not authorized to query the management service.

        The user is global admin uber god in Azure and in the domain. Well you need to give the account that you are using for the installation Iperius Backup 7.5.0 Crack + Serial Key Free Download 2021. in the Virtual Desktop APP.

        image

        I like to see what happened so often I use an extra Get- to see the values .

        But these errors I hate them, Why can it be so hare to deploy some machines and use RDS, Well it’s a 3 fase installer.

        • Granting the Domain + subscription
        • Powershell stuff to prep things
        • Install Azure VM’s

        And then the setup needs to embed in your infrastructure. Think I saw a lot of issues, during the first RDMI rollouts I thought this is complicated a created a full rollout script, but things changed during the program and at some points I could not get windows virtual desktop Installed several tries etc not good,

        Tons of failure on all kind of errors samples are below.

        —————————————————————————————–

        VM has reported a failure when processing extension ‘joindomain’

        the error is Deployment error: “VMExtensionProvisioningError”.
        Details error message are:
        {“code”:”DeploymentFailed”,”message”:

        Operation ‘Update VM’ is not allowed on VM ‘FIBWVD-0’ since the VM is marked for deletion.

        “The resource operation completed with terminal provisioning state ‘Failed’.”

        statusCode”: “Conflict”,

        “VM has reported a failure when processing extension ‘joindomain’. Error message:
        \”Exception(s) occured while joining Domain

        Error message: \\\”DSC Configuration

        ——————————————————————————————–

        Well I have multiple Domain names added to my Azure AD and Running a VM as DC with multiple domain names.  Azure Connect syncs them to Azure AD but standard well it depends, That’s why I thought lets create a backwards blog about windows virtual desktop #WVD.

        More about errors can be found here 

        https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-role-service#common-error-scenarios

         

        During all my test I noticed my Tenant Names where in use and different all meshed up. Removing them is easy but also in steps.

        First my sample here

        Get-RdsHostPool -TenantName ACACOMPUTERS

        image

        This shows you the host pools for the login user

        get-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        So removing the hostpool is not

        Remove-RdsHostPool -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        That seems logical, then lets see the application groups

        get-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool

        image

        There are Two application Groups : the default one and an extra created.

        AppGroupName    : Desktop Application Group

        AppGroupName    : MVP-WVD

        Remove-RdsAppGroup -TenantName ACAComputers -HostPoolName ACA-HostPool -Name “MVP-WVD” –Verbose

        image

        even with the verbose nothing no warning no error.

        Remove-RdsHostPool -TenantName ACAComputers -HostPoolName ACA-HostPool -Verbose

        image

        Now the Hostpool can be removed and no warning

         

        image

        Setting up a fresh new installation of WVD is easy, but the first setup is a bit painful but if you follow the steps you can’t go wrong.

        GO to the  https://rdweb.wvd.microsoft.com Add the Azure AD ID keep in mind if you are running a CSP subscription or you are not the owner it may that your account is blocked to create enterprise apps then this will fail and you can’t setup WVD.

        image

        Do this for Client and Server

        image

        Then give the users access to the Windows Virtual Desktop AVG PC TuneUp 19.1.831.0 Serial key - Crack Key For U, these are the installation accounts.

        image

        Open the app and add users or groups.

        image

         

        image

        Now you can sign in and start the deployment

        #Sign in to Windows Virtual Desktop
        Add-RdsAccount -DeploymentUrl https://rdbroker.wvd.microsoft.com

        image

         

        image

         

         

        You can also use a service principal name

        #############

        Set users or Create service principal name

        # create the service principal:
        $aadContext = Connect-AzureAD
        $svcPrincipal = New-AzureADApplication -AvailableToOtherTenants $true -DisplayName “Windows Virtual Desktop Svc Principal”
        $svcPrincipalCreds = New-AzureADApplicationPasswordCredential -ObjectId $svcPrincipal.ObjectId

        #Here are the three credentials you should write down and the cmdlets you need to run to get them
        $svcPrincipalCreds.Value
        $aadContext.TenantId.Guid
        $svcPrincipal.AppId

        #Set Rolassignment
        New-RdsRoleAssignment -RoleDefinitionName “RDS Owner” -ApplicationId $svcPrincipal.AppId -TenantName $tenantName

        #Sign in with the service principal
        $creds = New-Object System.Management.Automation.PSCredential($svcPrincipal.AppId, (ConvertTo-SecureString $svcPrincipalCreds.Value -AsPlainText -Force))
        Add-RdsAccount -DeploymentUrl “https://rdbroker.wvd.microsoft.com” -Credential $creds -ServicePrincipal -AadTenantId $aadContext.TenantId.Guid

        image

        This is All perfect But often I noticed that the WVD host where added to the domain but failed in something, the VM was fine and there was a folder with the deployment agent. and this got me thinking what If you install this on what ever OS, You could even use the WVD portal to connect to your own laptop.

         

        The manual add Server to the host pool is also a process when you start with 1 server and add later extra servers to the pool.

        but we will need a token to add the WVD host to the pool, like in RDS add the Role not the Role is an agent that is running on the VM

        image

        There are several ways to export the key I like them to capture this in screen and to the clipboard.

        $WVDToken = New-RdsRegistrationInfo -TenantName $tenantName -HostPoolName $hostpool -ExpirationHours 2
        $WVDToken.Token

        Configure Virtual Desktop Support

        Virtual desktop support is an opt-in feature of Tableau Desktop 10.5 and later and Tableau Prep Builder 2018.2.1 and later that gives you the ability to optimize your installations of Tableau for non-persistent virtual desktops, or for computers that are regularly reimaged.

        Starting with version 2020.1, virtual desktop can be configured for login-based license management (no product keys needed). This is the preferred, and often the required, method to implement a virtual deployment of Tableau Desktop when end users are not issued product keys. For more information, see Activate Tableau using Login-based License Management(Link opens in a new window).

        With virtual desktop support enabled, Tableau licenses or login-based license management license leases are automatically returned after a predetermined amount of time. This means that you do not need to manually refresh or deactivate the product key. The requirement that Tableau communicate with the hosted service means that you must periodically connect to the Internet.

        Without virtual desktop support, an activated Tableau license or login-based license management license lease remains in use until the license is deactivated or the lease term expires. This means that with frequently recycled virtual machines (VMs) and regularly reimaged computers, you may never have the opportunity to deactivate the license before the system is recreated, and the license activation remains in effect resulting in a maximum activation error.

        How virtual desktop support works

        When virtual desktop support is enabled, Tableau Desktop or Tableau Prep Builder periodically contacts a Tableau-hosted authorization-to-run (ATR) service to verify that Tableau is authorized to run, based on its license. When virtual desktop is configured to also use login-based license management, Tableau Online and Tableau Server work as a proxy to the ATR service to verify that Tableau is authorized to run with a valid Tableau Online or Tableau Server Creator user.

        The ATR service verifies the license or whether the user is a valid Creator user, and the length of the authorization window. As long as this communication is successful, Tableau runs without any impact to the user. The diagrams below show the communication process between the client and licensing components.

        Virtual desktop support and the ATR service without login-based Actual Virtual Desktops Registration key management

        1. Tableau Desktop or Tableau Prep Builder contacts the ATR service to verify that Tableau Desktop or Tableau Prep Builder is authorized to run.

        2. The ATR service contacts the Tableau Licensing Service to verify that the license is valid.

        3. The ATR service determines the length of the authorization to run window.

        4. If valid, the ATR service allows you to use Tableau Desktop or Tableau Prep Builder.

        Login-based license management with Tableau Online

        Login-based license management with Tableau Server

        1. You install Tableau Desktop or Tableau Prep Builder and select Activate with your credentials. You sign into your Tableau Online or Tableau Server site.

        2. Tableau Online or Tableau Server verifies that you are a Creator. If not, you get an error. If yes, Tableau Online or Tableau Server communicates with the ATR service.

        3. The ATR service returns an ATR lease to Tableau Online or Tableau Server.

        4. Tableau Online or Tableau Server provides an ATR lease to Tableau Desktop or Tableau Prep Builder to finalize activation.

        Requested duration

        By default, an instance of Tableau Desktop or Tableau Prep Builder is given a 14 day authorization window during which it is authorized to run. This means that after the initial authorization, you could use Tableau without any network connection for 14 days before the activation expired. The authorization checks are attempted regularly, and each time a check is successful, the authorization window is reset to its full length. This happens without any impact to you, unless there have been no successful checks and the window is nearing its expiration, in which case a warning message lets you know that you need to connect Tableau to the network so the authorization can be confirmed. The 14 day default is typically not a good value for deploying virtual desktop where you receive a new VM with every use. For more information, see Requested duration settings.

        The length of the authorization window is determined by the value of the requested duration. By default, the requested duration is 14 days (1,209,600 seconds), but you can configure this to fit your environment depending on how often Soundtoys 2021 Crack + Activation Code 2021 - Free Activators user will be receiving a new VM or if the Tableau Desktop is of a persistent nature.

        Note: If you use both Tableau Desktop and Tableau Prep Builder, setting the requested duration for Tableau Desktop also sets this same duration for Tableau Prep Builder and vice-versa.

        Requested duration settings

        You set the requested duration in seconds. The minimum requested duration you can set is 4 hours (14,400 seconds) and the maximum is six months (15,552,000 seconds). Use the following guidelines to determine how to set the requested duration setting for your users:

        • For most non-shared computers, especially those that are sometimes offline for several weeks at a time, set the requested duration to three to six months (7,776,000 – 15,552,000 seconds). A longer duration will allow the user to continue to use Tableau for an extended time without an internet connection.

        • For computers that are reimaged approximately once per month, set the requested duration to 30 days (2,592,000 seconds).

        • For virtual desktops that are recycled nightly, set the requested duration to the minimum of 4 hours (14,400 seconds). This will allow you to reuse your product keys each morning and eliminate the need to remember to deactivate them each evening before the virtual desktops are recycled.

        Virtual machines and product keys

        The benefit of using virtual desktop support is that for environments that regularly recycle their VMs, you can set a duration short enough to expire the license activation before the desktop is reused. This means that you do not use up screenhunter 6.0 free portable your activations. You will still need to enter the product key to run Tableau after the desktop is recycled. Login-based license management can improve the end-user experience in this scenario by requesting a sign in to Tableau Online or Tableau Server to activate Tableau Desktop or Tableau Prep Builder instead of entering a product key.

        Note: When using virtual desktop with subscription licenses, you cannot refresh your product keys. To renew a subscription or make licensing changes, you must identify the new product key in the Tableau Customer Portal and activate it.

        How to use virtual desktop support

        Virtual desktop support is an opt-in feature if you're not using login-based license management, so you need to enable the feature in order to use it (it is disabled by default). If you're using login-based license management, see Activate Tableau using Login-based License Management(Link opens in a new window). The ways to enable virtual desktop when not using login-based license management depend on whether you are running Tableau on Windows or on the Mac:

        On Windows you can enable and configure virtual desktop support:

        • At installation of Tableau Desktop and Tableau Prep Builder using command line install switches to enable virtual desktop support and specify a requested duration.

        • After installation, by editing the Windows registry to enable virtual desktop support and specify a requested duration.

        On a Mac you can enable and configure virtual desktop support:

        • After installation of Tableau Desktop and Tableau Prep Builder using commands.

        Tableau Desktop and Tableau Prep Builder on Windows

        There are three methods for setting the virtual desktop flags:

        Enable virtual desktop support at install

        Run the installer file from the computer's command line as an administrator, and include the switch if login-based license management is not being used (version 2019.4 and earlier, or manually disabled). The switch is not needed if login-based license management is configured on Tableau Desktop. To use a duration length other than the default of 14 days, include the switch. If you need to extract the .msi files, follow the instructions to Extract and run the Windows (MSI) installer .

        You must run the command from the directory where the file is located or specify a full path to the location of the file on the computer. Do not Actual Virtual Desktops Registration key the setup program from a shared directory on your network. Instead, download the file to a directory on the computer where you're installing.

        The has a minimum setting of 4 hours (14,400 seconds). The following example shows the Windows installer command that enables automatic license deactivation and set the duration to 12 hours (43,200 seconds):

        or

        When creating a primary image for a large virtual deployment, the above settings are appropriate and no product key activation should be completed. When using a new VM, each end user will enter the product key or sign in to Tableau Desktop or Tableau Prep Builder if login-based license management is enabled.

        Enable virtual desktop support by editing the registry

        If Tableau Desktop or Tableau Prep Builder is already installed, Actual Virtual Desktops Registration key can still enable virtual desktop support by editing the Windows registry to add an entry for. To change the default duration a license activation is authorized for, you can add an entry for .

        1. As an administrator on the computer running Tableau Desktop or Tableau Prep Builder, make a backup of the registry file before you make any changes to it.

        2. Edit the registry, and in create a new hive named with these values:

          • Name: Add a DWORD (32-bit) value named.

          • Data: Add .

          • Name: Add a DWORD (32-bit) value named.

          • Data: Add a number of seconds the duration should last. For example, add to set a duration of 12 hours.

          The illustration below shows what the hive looks like in the registry editor.

        3. Restart Tableau so that the changes take effect.

        Enable virtual desktop support by using the atr tool

        If Tableau Desktop or Tableau Prep Builder is already installed, you can still enable virtual desktop support from the Windows command prompt. The atrdiag.exe program resides in the \bin directory for Windows and is a tool specific to the virtual desktop and login-based license management settings. The atrdiag.exe program can report on the values selected, change virtual desktop configuration settings, and initially configure virtual desktop. If Tableau Download deep freeze full crack - Crack Key For U Support is needed, providing the output from the atr tool is often helpful.

        Note: Tableau Prep Builder must be installed on the same computer with Tableau Desktop in order to use atrdiag.exe with Tableau Prep Builder.

        1. Sign in on the computer running Tableau Desktop as an administrator.

        2. At a command prompt, navigate to the directory where Tableau Desktop is installed:

        3. At a command prompt, enable the ATR service:

        4. Set the duration, in seconds, that the license activation is authorized for. (For example, use 43200 to set a duration of 12 hours.)

        5. Restart Tableau so that the changes take effect.

        Disable virtual desktop support by using the atr tool

        If you no longer want to use the virtual desktop support feature, you can disable it.

        1. Shut down Tableau Desktop on the computer where you want to disable virtual desktop support.

        2. Open the Windows Command Prompt as an administrator, and then navigate to the directory where Tableau Desktop is installed:

        3. At a command prompt, run the following command to turn off the ATR service:

        4. At a command prompt, run the following command:

        5. Start Tableau Desktop.

        6. On the License Has Changed dialog, click Exit.

        7. Restart Tableau so that the changes take effect.

        8. On the Help menu, click Manage Product Keys to see if you can deactivate the product key.

        Tableau Desktop and Tableau Prep Builder on Mac

        Enable by updating the preference file

        To enable virtual desktop support on the Mac, run the following commands in a terminal window and then install or restart Tableau Desktop or Tableau Prep Builder:

        Troubleshoot virtual desktop

        If you encounter issues when configuring or using virtual desktop, you can collect diagnostic information about the computer that is running Tableau Prep Builder or Tableau Desktop using the virtual desktop diagnostic tool (atrdiag).

        You can verify that virtual desktop is enabled and view the value set for the requested duration seconds in use for Tableau Desktop activation. The TTL Start and TTL End values reflect the current lease being used on the virtual machine (VM) running Tableau Desktop. The commands provided below will capture the state of your virtual desktop support installation, regardless of whether you have installed Tableau Desktop or Tableau Prep Builder.

        Collect virtual desktop diagnostics on Windows

        1. Open a Command Prompt as an administrator.
        2. Navigate to the Tableau binaries () directory, using the following command:
        3. Run the following command:

          To optionally save the output to a file:

        Collect virtual desktop diagnostics on Mac

        1. Open the Terminal app.
        2. Navigate to the directory that contains the atrdiag tool, using the following command:
        3. Run the following command:

          To optionally save the output to a file:

        To learn more about resolving issues with Tableau Desktop installation, see Troubleshoot Your Tableau Desktop or Tableau Prep Builder Installation.

        Источник: https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_license_deactivate.htm
        Select-Object -ExpandProperty Token

        Best virtual desktop services 2021

        RSS

        TechRadar is supported by its audience. When you purchase through links on our site, we may earn an affiliate commission. Learn more

        By Christian Rigg last updated

        Hosted desktop solutions for your company’s needs

        The best virtual desktop services and Desktop as a Service (DaaS) providers make it simple and easy to ensure secure and cost-effective solutions for remote working.

        Desktop as a Service (DaaS) is not an entirely new phenomenon, but it’s certainly experienced significant growth in the past few years, both in terms of technology and market share, and especially more recently due to the pandemic.

        The reason for their take-up is that virtual desktops are a secure and flexible means for businesses to support a remote work staff and Bring Your Own Device (BYOD) practices. Of course, the pandemic and move to working from home has also accelerated take up of this technology.

        In a DaaS framework, a provider takes care of the technical and logistical aspects of cloud desktop and app environments, and a business rents these services for less than the cost of building and maintaining them itself. We’ve combed through the many DaaS providers on the market and chosen six of the best, based on services, security, scalability, and cost. 

        1. Amazon WorkSpaces

        Highly flexible pricing with payments by the hour

        Reasons to buy

        +Scale CPU, GPU, and storage as needed+Hourly pricing: pay what you use+24/7 phone/chat/email helpndoc professional edition download - Free Activators support+Includes AWS Security Hub and Application Manager

        Reasons to avoid

        -No text/data transfer from local machine to VM-Additional technical support is paid-Can only add users/assign desktops manually

        Amazon WorkSpaces is an industry leader in DaaS, with great features and pricing options for small businesses. It makes use of a PCoIP protocol for compression and encryption of data transfers, and WorkSpaces also uses Amazon’s SDX protocol. 

        Customers can provision Linux and Windows virtual machines, while AWS runs on Windows, macOS, Chromebook, iPad, Amazon and Android tablets, Chrome and Firefox. Both operating systems come bundled with default software like Internet Explorer, while Microsoft Office and others can be added for a monthly fee.

        One of the biggest advantages with Amazon WorkSpaces is the flexible pricing. Businesses that are interested in trying out the services can take advantage of a free tier with two workspaces, for up to 40 hours per month. There are several payment options based on disk size, number of CPUs, memory, and whether you bring your own licenses (BYOL).

        Bundled services can be charged monthly or even hourly, so you pay for what you use. There are no one-time fees and no commitments: you can cancel your subscription at any time.

        2. Citrix Virtual Apps and Desktops

        A trusted name in DaaS, well suited to a mobile workforce

        Reasons to buy

        +Great BYOD support+Supports remote access to physical machines+Encrypted data, never stored on device+Good centralized management

        Reasons to avoid

        -Minimum of 25 users-No autoscaling 

        Citrix is another big name in DaaS, and the Citrix Virtual Apps and Desktops platform has great hosted desktop services that are particularly well suited to a mobile workforce. Users can connect from Android, Windows, macOS, Chrome OS, and iOS/iPadOS and seamlessly switch between devices while maintaining workflow: the service adapts to different screen sizes, so employees can connect on a computer, tablet, or even mobile phone. 

        Plans vary by number of users, applications, features, and licenses. A Standalone version, deployed as a cloud service, includes Windows and Linux provisions, while the Workspace Premium Plus solution adds open support for any public cloud or hypervisor and is marketed as a comprehensive digital platform for managing Windows, Linux, web, SaaS, and mobile apps.

        Citrix also integrates with and virtualizes collaboration and communication tools like Skype for Business and can manage graphics-intensive jobs, with support for Intel, AMD, and NVIDIA GPUs. 

        3. Azure Virtual Desktop

        Customize plans to meet your needs and budget

        Reasons to buy

        +No minimum users or machines+Excellent backup and data safety+Supports Windows, Apple, and Android devices

        Reasons to avoid

        -Cloud-only, no on-site option-Windows only; no Linux provisions

        Azure Virtual Desktop enables businesses to provision Windows 7 or 10 virtual machines, complete with support for Office 365 and many third-party applications. WVD has excellent device support as well: Windows, iOS/iPadOS, MacOS, Chrome OS, Android, and Actual Virtual Desktops Registration key major browsers. 

        Pricing depends on region, operating system, virtual machine (CPU, GPU, and memory), and usage (in hours, days, or months) and is thus flexible. There are discounts available for one- and three-year subscriptions, or you can pay as you go. The Windows Virtual Desktop website even has a comprehensive calculator to estimate your costs based on your business’s needs. 

        With Azure, customers benefit from great backup and recovery features, making this one of the best providers for data security. Scheduled backups, snapshots, offline and encrypted backups of virtual machines, and automatic failover all help mitigate the risks of data corruption or loss. 

        4. VMWare Horizon Cloud

        DaaS from the desktop virtualization giant

        Reasons to buy

        +Supports all major devices and browsers+Available on-site, IBM Cloud, or Microsoft Azure+Scale complex custom machines easily

        Reasons to avoid

        -End users cannot up/downgrade computer power-BYOL only

        A name well known in virtualization, VMWare Horizon Cloud is available as a standalone, on-premises service or hosted on IBM Cloud or Microsoft Azure. Unlike previous providers, however, it is strictly BYOL, as VMWare does not plan to sell Windows licenses. 

        Horizon has great features for scalability and maintaining uptime. Instant Clone, for example, enables customers to rapidly deploy customized virtual machines by cloning from a parent or “master image” machine. The resulting machines are fully independent, so they can be further customized as necessary for easy scalability. Clones can also share a virtual disk and thus consume less storage, a practical money-saving feature.

        Pricing depends on user style (named vs. concurrent), payment plan (pay as you go or contractual), and edition (Standard, Advanced, and Enterprise). More advanced editions include features like Linux provisioning, virtualization for Skype for Business, and SSO and MF authentication. 

        5. Nutanix XI Frame

        Easily set up your infrastructure

        Reasons to buy

        +Simplified approach to VM creation and use+Strong integration with clouds, identity providers+Auto-scaling and auto-decommission

        Reasons to avoid

        -No native apps-Windows 10 only

        Nutanix XI Frame is a great choice for anybody who’s wary of the complexity and IT know-how necessary to set up and take advantage of a full-featured DaaS environment. The company aims to provide a more streamline experience to admins, without directx 11 download - Activators Patch end-user experience and functionality.

        Источник: https://www.techradar.com/best/virtual-desktop-services

        In an enterprise environment, users do not need to worry about Windows activation on their work devices. That’s one of the many jobs for the IT department. It’s another story with personal devices. Every user should be prepared: a laptop might be lost, a PC motherboard stop working, and so on. In such cases, actually in any case when you have a valid, transferable digital license, you can reactivate your device after major hardware changes, or activate Windows 10 on a new device. You just need to be prepared.

        Many of you geeks have a Visual Studio subscription (formerly known as MSDN), with lots of product keys to use. Taking care of your digital licenses is equally important whether you have just one device, or a complex home network with multiple devices.

        OEM, Retail, MAK?

        Here’s a good rule of thumb: If a Windows 10 device comes with Windows preinstalledit is a so-called OEM (Original Equipment Manufacturer) license. If Windows 10 was purchased from Microsoft or some licensed retailer, it is a Retail license. One exception: so-called System Builder versions which are also OEM licenses. All single use Visual Studio subscription keys are also Retail keys. Multiple Activation Keys (MAK) are also shown as Retail in the Windows Software License Manager (slmgr.vbs).

        OEM licenses can’t be transferred to new devices, and they cannot be used to reactivate Windows 10 when major hardware changes such as replacing motherboards occur. One somewhat grey Nitro Pro 13.42.3.855 Crack With Latest Activation Key [Latest 2021] is Microsoft’s tech support: on various tech sites and forums you can read about users claiming that talking to the activation helpline succeeded, and an OEM license reactivated even after both motherboard and CPU were swapped out and automatic activation failed.

        To check if you have an OEM, non-transferrable license, enter the following command in an elevated PowerShell or Command Prompt:

        slmgr /dli

        Software License Manager opens a prompt telling about your license. If it shows that your license is from OEM channel, you cannot transfer the license:

        What is a Digital License?

        When Windows 10 is activated for the first time, that device gets a valid digital license for the activated edition, for the lifetime of that device. However, its hardware ID (HWID) must remain the same (no major hardware changes). Microsoft has 15 different hardware IDs to be used in various scenarios, the one that determines if a digital license on a device is valid is hardware ID 3. See the full list: Specifying Hardware IDs for a Computer.

        Notice that disk drives are not included in the HWID. This means that a user is free to replace an HDD or SSD without losing his or her Windows 10 license. That said, a digital license is edition specific, but not language, version or bit architecture specific. You can replace your HDD containing a licensed 64-bit Windows 10 Pro version 1809 in English, and install a 32-bit Windows 10 Pro version 1909 in Swedish on a new HDD. Windows 10 will be automatically activated, based on the HWID and the existing digital license.

        Taking care of Digital Licenses

        Even if you use only a local account to sign in to Windows 10, it is important to create a Microsoft account, if you do not have one already. This is the only way to be sure that license can be reused for reactivation after replacing hardware or transferring that license to a new device. As an example, I have just performed a clean install of W10 Pro on a Hyper-V virtual machine, although exactly the same Actual Virtual Desktops Registration key to physical devices, too. The first thing to do is to change the device name to something that will later clearly tell me which machine this is. I renamed the machine to VM-W10PRO07, it being the seventh W10 Pro VM I have activated. When transferring the license, it is important that you know the device name for the license you wish to transfer.

        After the restart required by renaming the machine, I activated this VM using one of my MAK keys for the Windows 10 Pro edition. At this point, activation status is shown as Activated with a digital license:

        Click screenshots to open enlarged in a new tab.

        If I now clicked the Add an account under Add a Microsoft Account link, my local account would be switched to a Microsoft Account, and this license would be registered for that MS account. If a Microsoft account is what you want to use, click Add an account and follow the on-screen instructions to sign in. However, if you are like me and want to continue using a local Actual Virtual Desktops Registration key, do not click that link! See this earlier Win10.guru story, scroll down to title Why not best of both?, and see how to add a Microsoft account to Windows 10 without switching a local account to a Microsoft account: Microsoft Account vs. Local Account – Why not both?

        Whichever method you choose, after switching to a Microsoft account or adding an MS account to a local account, the activation status changes to Activated with a digital license linked to your Microsoft account:

        One last check: I will go to https://account.microsoft.com/devices/ and check that the new machine, and its digital license have been added to my MS account:

        That’s it, the digital license is now ready to be transferred.

        Transferring a Digital License

        Let’s say that my sample machine was a real, physical machine, and that it died. A Retail license registered on my MS account now belongs to a device that does not exist anymore. I can assemble a new PC, clean-install Windows 10 Pro on it selecting I don’t have a product key, and when I get to its desktop for the first time, rename that PC and restart. Then, I can either switch to a Microsoft account or add an MS account to a local account.

        When all that is done, I go to Activation settings, and select the activation troubleshooter:

        At the next prompt, I select I recently changed hardware on this device link:

        A list of devices registered to my MS account is then shown. I select my sample VM, and click Activate:

        The new clean installation on the new device is now activated:

        Easy and fast!

        That’s it, geeks. Take care of your licenses, register them on your MS account using a clear, explanatory device name.

        Kari

         

        Author: Kari Finn

        A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site TenForums.com.

        Twitter

        Related

        Источник: https://win10.guru/windows-10-digital-license-how-to-transfer/

        Products

        CCleaner logo

        CCleaner v5.87

        Optimize, clean, protect and speed up your PC

        Professional

        Inject instant speed into your machine by removing the unnecessary files taking up room on your hard drive. Clear out errors and broken settings to improve stability. Boost your browser and help protect your privacy by securely erasing tracking cookies and history.

        Includes:

        • Real-time monitoring
        • Scheduled cleaning

        So your PC stays clean without you having to do a thing!

        Buy Now

        Professional Trial

        Use CCleaner Professional for 14 days, for free. Once your trial is over you'll automatically drop down to CCleaner Free, so it won't cost you a thing.

        Actual Virtual Desktops Registration key Download

        Free

        Install our standard version of CCleaner.

        Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution!

        Runs on Microsoft Windows 10, 8.1, and 7. Including both 32-bit and 64-bit versions.

        Back to top
        CCleaner logo

        CCleaner v1.18

        Optimize, clean, protect and speed up your Mac

        Professional

        Inject instant speed into your machine by removing the unnecessary files taking up room on your hard drive. Clear out errors and broken settings to improve stability. Boost your browser and help protect your privacy by securely erasing tracking cookies and history.

        Includes:

        • Real-time monitoring
        • Scheduled cleaning
        • Automatic updates

        So your Mac stays clean without you having to do a thing!

        Buy Now

        Free

        Install our standard version of CCleaner.

        Download

        Requires an Apple Mac running 64-bit macOS 10.10 and above.

        Back to top
        CCleaner Browser - product logo

        CCleaner Browser

        A free, fast and powerful browser from the makers of CCleaner

        Free Version (Only)

        Enjoy cleaner, faster online browsing. Delete browser files and data automatically, disable trackers, and block malicious websites. Load pages faster by disabling pop-ups with ad-block, and stop your PC slowing down when you browse online by optimizing its performance.

        Includes:

        • Access to CCleaner app with one click
        • Optimization of your PC with ‘Performance Manager’
        • Faster web page load times with ‘Adblock’
        • Built-in privacy and security tools
        • Fast and powerful browsing that works with CCleaner.

        Download

        Back to top
        Kamo - product logo

        Kamo

        Protect your privacy by stopping online tracking

        KAMO

        Kamo can do what private browsing, adblockers, VPNs, and antivirus programs can’t. Not much can block browser fingerprinting technology from pushing up the prices you see online and tracking your online activity with up to 99% accuracy, but Kamo can and does.

        What else does Kamo do?

        • Syncs with most web browsers on your computer
        • Stops companies from tracking what you do on your PC

        Use the full version of Kamo for 14 days for free: no credit card required. Once your trial is over, you’ll need to purchase Kamo to continue blocking online trackers and retain your online privacy.

        Free Trial

        Back to top

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to top
        Recuva - product logo

        Recuva v1.53

        Restore accidentally deleted files quickly and easily

        Professional

        Rescue valuable files fast – even if they were deleted weeks ago. Restore pictures, music, documents, videos, emails or any other file type from PCs, portable or rewritable media.

        Includes:

        • Deep scan file recovery
        • Priority technical support

        So you never have to worry about losing a file again!

        Buy Now

        Free

        Install our standard version of Recuva.

        Actual Virtual Desktops Registration key Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to top
        Speccy - product logo

        Speccy v1.32

        Fast, lightweight, advanced system information at your fingertips

        Professional

        Get detailed information on every piece of hardware in your computer so you can make informed purchasing and upgrade decisions - and even spot problems before they occur.

        Includes:

        • Advanced PC insights dashboard
        • Automatic updates
        • Premium support

        So you will never have to trawl through your computer for stats again!

        Buy Now

        Free

        Install our standard version of Speccy.

        Download

        CCleaner Professional Plus - Upgrade to our 4-in-1 complete cleaning & recovery solution

        Windows 10, 8.1, 7, Vista and XP. Including both 32-bit and 64-bit versions, but not RT tablet editions.

        Back to topBack to top

        Requires Windows 10, 8.1, 8 and 7 including both 32-bit and 64-bit versions.

        Back to topBack to topBack to topBack to topBack to top
        Источник: https://www.ccleaner.com/download
        Actual Virtual Desktops Registration key

        1 Replies to “Actual Virtual Desktops Registration key”

        Leave a Reply

        Your email address will not be published. Required fields are marked *