The next step requires us to define a detection policy, we click on “ Add” and specify the MSI product code option, as this is already prefilled.įor the next steps we don’t define dependencies, supersedence and we can continue to select the Scope Tags and do the assignment if needed. In the next tab, we need to provide the requirements, which is obviously the 64-bit architecture and the minimum operating system (that can be adjusted to your environment), which is Windin my case. The advantage of using an MSI is that the IntuneAppWinUtil automatically detects the installation parameters, additional ones can be added, but that’s not required and we can continue with the next steps. I specified “Microsoft” and click on next. In my case I only had to add the Publisher information to the package. Once everything is fine, we click on OK and specify the parameters for the installer. The process asks us now for the app package file, which is the intunewin file we’ve just created. Now we need to select the App type, which is “Windows app (Win32)” and click on select. #Windows remote desktop client windowsNow we see the collection of all Windows apps available and we click on “ Add” to import our Remote Desktop Client. Now we need to navigate to Apps / Windows To import the package to Intune, we need to login first to our tenant using: Import Remote Desktop Manager via MEM (Intune) We can see the intunewin file besides the MSI file. If that’s correctly done, the output will look like this: We don’t want to specify a catalog folder. The tool asks us to specify the source folder, we select the one where our Remote Desktop Client is stored, give the tool the file name and select the output folder. We start with opening the IntuneWinAppUtil.\IntuneWinAppUtil.exe Now we need to specify the Source file, which is our recently downloaded Remote Desktop Client and the destination location for the IntuneWin file. Next, we navigate to the folder, that has our IntuneWinAppUtil, which is in my example C:\MEM. Now, we need to open a PowerShell window with elevated rights (Administrator) and set the Execution Policy to “RemoteSigned” and approve with “Y(es)”: Set-ExecutionPolicy RemoteSigned #Windows remote desktop client downloadGo to the following GitHub page and download the exe: GitHub – microsoft/Microsoft-Win32-Content-Prep-Tool: A tool to wrap Win32 App and then it can be uploaded to Intuneįor this demonstration I’ve created a folder called “MEM” where I store the file: In the next step, we need to download the Microsoft Win32 Content Prep tool, to package our MSI file into an IntuneWin container. For this reason, I create a new folder called: “ RemoteDesktopClient_122130″ in my favorite location. Now I copy the downloaded file to a location that is easily accessible from my packaging PC. I’ve used the following download link for the 64-bit version: In my case, I take the 64-bit client and download it to my computer. The first thing we need to do now is to select the architecture, we use to distribute the client. Please find the latest version here: What’s new in the Windows Desktop client | Microsoft Doc Packaging of the Remote Desktop Client app and upload to Microsoft Endpoint Manager (Intune) The first thing we need to do is to package our Remote Desktop Client in the current version: We will perform the distribution to your clients via Microsoft Endpoint Manager (Intune). #Windows remote desktop client how toThis way you can drag it around like a regular window.Today I have another blog for you about how to distribute the Remote Desktop Client for Azure Virtual Desktop and the upcoming service release of Windows 365 Cloud PC. #Windows remote desktop client fullYou can tell it to only be a small window in your monitor (do not use full monitor size).You can only allow the RDC to only use one monitor only.You can turn on the settings on the RDC such that it covers all your monitors and thereby taking over your local desktop.How does connecting to the remote server affect what you see on your screen locally? You have a few options when using RDP as it pertains to your local monitor. Screen and Monitor Considerations when using Remote Desktop Connections At this point if you are authorized you will be connected with your remote desktop If the username field is not available to type in, make sure you click on more choices, then “user a different account”. If you are not part of a domain try “.\username”. Enter your username - Your username is usually in the format of “domain\username” if you are part of a domain.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |