Microsoft Remote Desktop 4+
Microsoft Corporation
-
- 4,7 • Оценок: 8,8 тыс.
-
- Бесплатно
Снимки экрана
Описание
Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are.
Configure your PC for remote access using the information at https://aka.ms/rdsetup.
Learn about our other Remote Desktop clients at https://aka.ms/rdclients.
• Access remote PCs running Windows Professional or Enterprise and Windows Server.
• Access managed resources published by your admin.
• Connect through a Remote Desktop Gateway.
• Secure connection to your data and applications.
• Simple management of your connections and user account from the Connection Center.
• Audio and video streaming.
• Redirect folders, your clipboard, and local devices such as microphones and cameras.
Submit feedback at https://aka.ms/rdmacfbk.
Что нового
In this release we’ve worked through some bugs that were hanging around in our backlog. Some items we addressed include:
• Added background refresh for subscribed workspaces.
• Fixed an issue where the session window may jump to another monitor when auto-reconnect kicks in.
• Fixed an issue where the session window would sometimes be enlarged after connecting.
• Addressed an issue where the name of a redirected folder would be incorrect in the remote session.
• Fixed a bug that made it difficult to resize remote app windows.
• Improved the error messages that are displayed when user accounts fail to update.
• Fixed an issue where window titles in the list of connected remote apps were blank.
• Addressed a multimon issue where the mouse cursor shape would not update correctly when dragging between monitors.
• Added a checkbox to General Preferences to enable/disable Microsoft Teams optimizations.
• Added UI to report if a remote app could not be launched on the server due to not being on the system allow list.
• Fixed an issue where the session window could not be made wider when placed at the top or bottom of the screen.
• Addressed scenarios where the mouse cursor would disappear while connected to a remote PC.
• Deletion of an Azure Virtual Desktop workspace now correctly removes all associated workspaces.
• Fixed an issue where adding a folder to redirect to a bookmark would enable the «Add» button with an empty PC name.
• Addressed an issue where double-clicking the title bar incorrectly stretched the session window.
• Updated the mouse to change to a hand glyph when hovering over a red input error indicator.
• Fixed an issue where the session window would flash rapidly in the «Mission Control» or «Application windows» view.
In addition, we have continued to make updates to improve connectivity and performance metrics when connecting to Azure Virtual Desktop.
Note that by default subscribed workspaces are refreshed every six hours. This interval can be changed using the ClientSettings.WorkspaceAutoRefreshInterval user default (minimum is 30 minutes and maximum is 24 hours).
Thanks to everyone who reported bugs and worked with us to diagnose and fix issues. If you encounter any errors, you can contact us via Help > Report an Issue.
Источник
Mac os rdp принтер
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Answers
It depends where your printers are being delivered from. There are two ways that you can print in a Terminal Services/Remote Desktop connection.
The first way is a Server printer. In this method — the printers are set up on the server for each user connection via a script that runs on the server or via group policy preferences. This should work regardless of your platform and should be set up by the Administrator on the server.
The second method is a Redirected Printer. Redirected Printers are «redirected» from your Remote Desktop Client. Your remote desktop client needs to be configured to pass through its printers in this method, and the server must support redirected printers. This option will be available in your Remote Desktop Client options.
If your Remote Desktop Client is set up correctly to redirect its printers, and the server has been configured to support redirected printers, but your printers are still not appearing, I suggest that you ask your the Server Administrator to take a look at the Event Viewer on the Server.
All replies
It depends where your printers are being delivered from. There are two ways that you can print in a Terminal Services/Remote Desktop connection.
The first way is a Server printer. In this method — the printers are set up on the server for each user connection via a script that runs on the server or via group policy preferences. This should work regardless of your platform and should be set up by the Administrator on the server.
The second method is a Redirected Printer. Redirected Printers are «redirected» from your Remote Desktop Client. Your remote desktop client needs to be configured to pass through its printers in this method, and the server must support redirected printers. This option will be available in your Remote Desktop Client options.
If your Remote Desktop Client is set up correctly to redirect its printers, and the server has been configured to support redirected printers, but your printers are still not appearing, I suggest that you ask your the Server Administrator to take a look at the Event Viewer on the Server.
I am just writing to say Hi, and to ensure the problem has been completely resolved. If there is anything I can do to help on this issue, please feel free to let me know. I am happy to be of assistance.
Lionel Chen
If you have any feedback on our support, please contact tngfd@microsoft.com
This posting is provided «AS IS» with no warranties, and confers no rights. | Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
Made sure I followed suggestions above. After doing all that we still can’t print. The event viewer had nothing in there concerning rdp printer issues. Where can we go from here?
1. What operating system are you running on your server? 2008 R2 -or- 2008 RTM/SP2
2. Does the problem occur with only one Mac or all Macs that connect to the server?
3. Have you tried connecting from the Mac using different user accounts, specifically a user account that is able to print when logging on from a windows PC?
Normally if there is a problem auto-creating printers for Macs there will be one or more errors in the System log each time someone logs on to the server from a Mac. Source: TerminalServices-Printers Event ID: 1111
The correct HP LaserJet 4350 PS driver must be present on the server.
For best results, please respond back with detailed answers to the above as soon as possible.
1. It’s a Windows 2008 Server R2.
2.The problem occurs with all MACs.
3. Yes I have tried to connect from different MACs using different logon names and I get the same result.
I have a bunch of Event ID: 1111’s present. They reflect each printing connection using different MACs.
How can I setup a script or better still where do I have to go in Group Policy to allow the MAC to print from the Server?
This Server is not a Domain Controller. AD is not setup.
Thank you for responding so quickly.
In order to print from the Macs you need to install the HP LaserJet 4350 PS driver that shipped with Windows Server 2008. You can copy the driver package over from a Server 2008 or create a «dummy» 4350 printer on a Server 2008, share it out, install it on your Server 2008 R2, then delete the printer off of your R2. This will effectively install the driver on your R2.
If you want to copy the driver package over to your 2008 R2 server and then install the driver, the files are by default located in a folder on the 2008 server that starts with prnhp or similar within this folder:
Once you have the folder copied over to your R2 server you can add the driver using the Have Disk option in the Add Printer Driver Wizard from Print Server Properties window, Drivers tab. I have not tried it, but my guess is that you could use the HP LaserJet 4350 PS driver that shipped with Vista if you do not have access to a Server 2008.
NOTE: The 4350 PS driver from HP’s download site will not work correctly, that is why I am instructing you to use the one that shipped with Server 2008.
Please verify that the above solves your printing issue and then come back here and mark this post as the answer so that people will be able to find it in the future.
- Proposed as answer by TP [] MVP Monday, July 12, 2010 4:29 AM
I want to mention that this problem does not exist when I RDP into a Windows 2003 Server. In that enviornment it works the way it is supposed to.
Did you install the HP LaserJet 4350 PS driver from Server 2008 or Vista like I mentioned?
Under 2003 it will typically use the Apple LaserWriter 8500 driver, which is available by default. I am not sure if the 2.0.1 client use the 8500 driver under 2003 or not. If this is the case it would explain why it works when connecting to 2003 and not when connecting to 2008 R2.
If you examine the text of the 1111 errors I think you will see it is looking for the HP LaserJet 4350 PS driver. If not please report back with the exact driver name mentioned in the error text.
Please install the HP LaserJet 4350 PS driver from Server 2008 or Vista onto your Server 2008 R2 and then test.
The above did not solve my problem. Server 2008 is very different from its predecessors. The MACs are able to print using RDP with all flavors of Windows 2003 Servers. The printers redirect correctly. Where are the settings that will allow this to happen in Windows 2008 Server?
Please post the precise text of the 1111 errors that occur when a Mac logs on to your Server 2008 R2.
After that I will assist you further.
This solution finally worked for me with the exception of one user who runs Leopard and has some older printers, his dot matrix one doesn’t print at all and his laserjet one just a two page error report, haha.
I’m dealing with this same issue now and h ere is my problem:
I do not have a previous installation of Windows Server 2008 to get the correct HP LaserJet 4350 PS driver — t his is a brand new installation of Windows Server 2008 R2. It is not an upgrade from Server 2008.
I do not have Vista, which was another suggestion.
I also tried getting it from a Windows 7 install, but this failed.
If the driver provided by HP has font issues, where am I supposed to get the correct driver?
Thank you for any assistance.
For Printing from MAC OSX i recomend TSPrint tool with universal driver.Works great for me.
For Printing from MAC OSX i recomend TSPrint tool with universal driver.Works great for me.
Hi everyone, and Hi TP 🙂
it seems like you know a lot about that kind of issue. Thing is, it’s been several weeks i have the same issue on 2008 R2 with MACS.
I finally found the 1111 ID (a loooot) in the event viewer. It was saying exactly the thing you talked about, installing the famous HP LaserJet 4350 PS.
I still don’t understand why it does need this one because no one of the printers concerned is a LaserJet 4350PS (but there is a Hp LaserJet P2055dn..)
Anyway, i installed that famous hp driver (the one from the hp official website first, i saw that was not installed ‘properly’ in regedit because it created a new HP LaserJet 4350 PS folder over the ‘good’ drivers folder. but since that moment i can see the MACS printers on the 2008R2. Anyway it still don’t work correctly. I read your post, uninstalled the 4350PS from hp and installed the 4350PS from microsoft. Now there is no more hp folder over the good one, and i can also see the mac printers on the 2008 R2 server, but it still don’t work correctly. So, what can i do now please ? And by the way, just FMI, please please please could you explain me why it does need this particular hp 4350ps driver anyway ? I’m okay with if it’s the way it works, i just like to understand, and you seem to know a lot about. am i wrong ? Thank you anyway for reading me 🙂
Oh and, guess you already noticed that, i’m not american, i’m french, and i’m sorry about my primary langage, hope that’s not too hard for you to understand me.
Источник
