AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Users are directed to resources based on the credentials they supply when logging in. WVD is a PaaS offering with a shared URL for client access that requires Azure AD authentication. Unfortunately, that client will not work with WVD. This client has been used with RDS environments for quite some time. Windows comes with a Remote Desktop Connection client (MSTSC). The following client configuration information includes instructions for both options. Once the DNS entry is added and replicated, end users can access published resources by entering their email address instead of a URL. In most cases, it takes just a few minutes, but some systems could take hours. Keep in mind that it can take some time for DNS to update. Log in to the DNS service with an account that has rights to modify DNS.Īdd the following host and associated values as a new text record in the domain: Host:_msradcĪll DNS services are different, but the end result should look similar to the image below. Below is an overview of the steps for adding email feed discovery to DNS. For example, if the user's email address ends with a DNS entry for the WVD is added to the domain. The host record is added to the user's email domain, and the corresponding DNS entry for the domain directs the client to the WVD feed URL. This is an easier method for end users that uses a host record added to DNS to facilitate WVD feed discovery. The second option is to enable email feed discovery. URLs are complicated to type, and some devices don't allow copying and pasting between applications. Locating WVD resources by the feed URL is a viable option, but users may find it cumbersome. The first is by entering the feed URL into the client. There are two options available for the clients to locate the WVD service. Credentials can be cached in the web browser to minimize user sign-in. The first sign-in is to Azure AD and the second is to the Active Directory domain. Please contact our sales team to try Liquit Release & Patch Management free of charge for 30 days.The double sign-in is necessary, as the user signs into two systems. Receive e-mail notifications about updated managed packages. The Three Components of Liquit Release & Patch Management. ![]() You can do this automatically, using a scheduled task, or semi-automatically using the ‘Updates’ feature of the Setup Store connector. ![]() ‘Managed’ means that every time Microsoft releases a new version of Microsoft Remote Desktop, the Setup Store connector updates all ‘managed’ packages with the latest version of that particular application. The Setup Connector now grabs the latest version of ‘Microsoft Remote Desktop’ and creates a ‘Managed Package’. In the Summary screen leave the ‘Modify package after creation’ checkbox checked.In the Entitlements screen add the users you want to assign this package to.Set AllUsers to 1 for deploying the client ‘per machine’, click ‘Save’. ![]() In the Customize screen, click the ‘Configure’ option.In the Details screen opt for ‘Package Type = Managed’.Select either one of the available ‘Microsoft Remote Desktop’ setups, depending on the platform you want to deploy it on.Click Resources and search for ‘Microsoft Remote Desktop’.Click Manage, Connector, then select the Setup Store connector.
0 Comments
Read More
Leave a Reply. |