Remote Desktop 8.0.12 for Mac Typo

Remote Desktop 8.0.12 for Mac has a typo in the "What's New" box that appears at startup. It reads "Fixed full screen issues in Yosemity," but should read "Fixed full screen issues in Yosemite." This should be fixed as
soon as possible to preserve Microsoft's professionalism.

Hi Jolly,
Thanks for shading your light, I will share with product group for further updation.
Regards.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Remote Desktop 8.0.6 for Mac does not map keyboard key properly

Remote Desktop for Mac 8.0.6 is incorrectly mapping the grave / tilde key on the keyboard to the backslash / pipe key.

Hi,
Please check if the system language on your Mac and the keyboard language on the remote PC are match.
Thanks.
Jeremy Wu
TechNet Community Support

HT5306 I do not want to give remote access to anyone but myself as privacy is my friend. Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only? What if I do not update? compatibility issues with wh

Hello:
Thank you for the update for remote access for desktops.
Personally, I do not want to give remote access to anyone but myself as privacy is my friend. Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only? What if I do not update? I do use this lap top in other countries. compatibility issues with what?

Apple Remote Desktop is off be default. It has to be enabled for some one to be able to remotely connect to the computer. And then, you still have to have a user name and password on the computer to remotely connect with.
If you want to see if remote access has is enabled for Apple Remote Desktop; you can find the setting in, Apple Menu, System Prefrences, Sharing. If it's enabled, Remote Management or Screen Sharing will be checked.
Beucase Apple Remote Desktop Agent is part of the Mac Operating System; even if your not using it, Apple Software Updates will from time to time offer updates for ARD Agent. Software Updates can some times be stacked ontop of each other; so chosing not to install an update, can mean other updates you may want may not be offered. At least until you install the updates those updates require. Also software updates can improve the security of your computer.

Problems with Remote Desktop and Back to My Mac

It's impressive how quickly Apple removed my post because of its tone. I hope they respond with equal speed and verve to my concerns.
I need to get Remote Desktop operational. Can someone walk me through the process of getting Remote Desktop to "see" my home computer? The current online video tutorial for Remote Desktop is outdated and no longer resembles the current UI for setting up Remote Desktop.
What about Back to My Mac? Can I get help with that, too? I figure if I can get at least RD or BTMM running properly I'll be able to do what I want to do.

The subject of connecting ARD via the Internet has been covered here many times already (search the forum for "Internet"), but take a look at this web page:
http://www.starkpr.com/ard.htm
It should help, though you may have to refer to your router's documentation for specifics on opening and forward ports in that particular unit.
"Back to my Mac" is a different feature of Mac OS X and has it's own forum:
http://discussions.apple.com/forum.jspa?forumID=1247

Apple Remote Desktop to wake up a Mac

Hello,
Do you know how to use Apple Remote Desktop (ARD) to wake up a Mac which is not on my local network?
Imagine I am in the USA and I need to wake up my Mac in France to see my files, play some music... Is it possible? ARD can do it?
Or should I prefer another program like WakeOnLan by ReadPixel, or the Depicus page...?
Do I need an IP address, a MAC address and to configure my router to accept the correct "wake" packet?
I know the Mac needs to be connected with Ethernet, and "Wake for network access" has to be checked in the Energy Saver panel.
In case it works, can I shutdown my Mac with ARD too?
Maybe you would suggest to use ARD to wake up the Mac then use FTP to see my files, read some music...
The thing would be to use the Mac as a server I could connect with from anywhere in the world to see my files, play music and more...then shutdown it when I finished. Am I dreaming?
Thank you for your help.

Thank you for your information.
I found another topic here : Wake-On-Lan support?
The member el_migu_el wrote something interesting I think.
Basically, it seems Apple Remote Desktop is designed for local network only. When we need to wake up a Mac through the Internet, ARD shows its limits and we have to find another tip to make this thing possible.
Maybe I am wrong but it seems easier to wake up a PC (with Linux OS) through the Internet than a Mac.
I was thinking to another solution :
Would it be possible to configure the Mac with the Energy Saver panel to make it wake up on a specific day at a specific hour (then shut down it in the same way), and use a FTP connection to access our shared datas? It would mean applies like Pure FTPd Manager should run after the Mac woke up, and it would be necessary to configure a static IP address with the DynDNS service for example to avoid any IP changes to still get the conection with the Mac.
And obviously we would use some applications like Cyberduck or FileZilla to access our shared datas. The problem is that we couldn't use our Mac as a server, I mean use it to launch some music for example from anywhere in the world.
I had a friend who had used is old PC (with a Linux OS) as a server to share some music we could hear on our computer. With an address he gave we could see the music he shared. It was cool. The thing was his PC had to be switched on all the time. But I am sure we could have woke up his computer from anywhere to get access to his music if he had configured his PC in that way.

Problems with BBC iPlayer Desktop and Adobe Air for Mac

I would be grateful for anyone who can help me with a problem I have on my Laptop running Mac OS X Lion 10.7.3.I am having difficulty running BBC iPlayer Desktop and I suspect it is caused by Adobe Air.
Recently I was prompted to update Adobe Air to the latest version (as of February 2012) and after I successfully updated the program, this began to cause problems when I used BBC iPlayer desktop.
The first problem I noticed was that I was unable to play any downloaded programmes in full screen - only the sound played, not the video.
Secondly, a few weeks after this problem began, all my TV programmes mysteriously disappeared.
My final problem is that everytime I launch BBC iPlayer it is unable to download new programmes - when I am connected to the internet, the application still says it is "offline".
I have tried to resolve the problem by restarting my computer, uninstalling and reinstalling BBC iPlayer, disabling and re-enabling my firewall, connecting to the internet in different locations but this has not resolved the problem.
I tried to uninstall Adobe Air, but the installation package tells me it is 'corrupt'. So I tried to download and reinstall the application from the adobe website, but the computer already recognises that the app is installed. i.e. - I can't uninstall or reinstall Adobe Air.
I contacted BBC iPlayer support and they were unable to help - directing me to your website. I have read several other discussion topics posted on this website but not found the solution I am looking for.
Please can some help me to solve this problem, by helping me uninstall and reinstall Adobe Air for Mac?
I am not very technical minded - for example - I don't know what log files are or how to find them - so please explain it as simply as possible.
Thank you in advance for your help!
Ryan

Just had the same thing happen AGAIN. Suddenly - a blank iPlayer Desktop which failed to download new programmes. All previous programmes were still in the repository folder. This time the sequence I outlined previously didn't work.
What eventually got things working this time was to reinstall Adobe Air as part of the BBC iPlayer Desktop installation process - and not separately.
So:
a) Move iPlayer to trash.
b) Find and delete the following folder: Users/Yourname/Library/Preferences/BBCiPlayerDesktop.61DB7A798358575D6A969CCD73DDBBD 723A6DA9D.1
c) Find and delete the following folder:
Users/Yourname/Library/Application Support/Adobe/AIR/ELS/BBCiPlayerDesktop.61DB7A798358575D6A969CCD73DDB BD723A6DA9D.1
d) Find and delete the following folder:
Users/Yourname/Movies/BBC iPlayer/repository/cache
e) Find and run: Applications/Utilities/Adobe AIR Uninstaller
f) Empty the Trash. I found that bits and pieces of BBC iPlayer were still running despite having been quit and dumped in the trash - and so it wouldn't allow me to complete this part. Restarted the computer, then empty the trash.
g) Find the folder: Users/Yourname/Movies/BBC iPlayer/repository and rename it repository2
h) Reinstall iPlayer. It will tell you that you have no programmes to view. Quit the programme.
i) Find and delete the folder: Users/Yourname/Movies/BBC iPlayer/repository
j) Find the folder: Users/Yourname/Movies/BBC iPlayer/repository2 and rename it to repository.
k) Relaunch iPlayer
It would be terribly nice if the BBC or Adobe stopped buggering about with this . . .

(Resolved - My own stupidity) Remote Desktop 8.1.3 for iOS (iOS 8.0) - Connects to Black Screen

New version, new problems!
After finally solving my problems with connecting introduced in 8.1.0 for iOS, I have updated to 8.1.3 and have a new problem!
I am able to log in, but upon login, I am presented with a black screen instead of my desktop. If I turn on the mouse pointer, the pointer shows up, but it does not control the remote computer.
Additionally, the iOS Remote Desktop Client is not "taking over" the remote computer... I am typing on the computer to write this, while my iPad's Remote Desktop app is supposedly "connected" to it.
Anyone else having this new issue?

Resolved - My own stupidity! :-P
Garbage in, garbage out! I have two computers connected to the same monitor...My 2nd computer was active on the monitor, hiding the fact that my primary computer (and remote desktop host computer) needed a restart! I restarted, and the issue
was resolved!

Allow log on through Remote Desktop Services Group Policy for Domain Controllers

Hello,
We want to allow our Helpdesk Operators to be able to connect to Domain Controllers with the Remote Desktop Services. This is by default not allowed but according to many sites, it should be able to configure by using a Group Policy.
We made a new Group Policy with the setting 'Allow log on through Remote Desktop Services' and 'Allow log on locally' (as an extra for testing) and applied Security Filtering to only use it for a specific Security Group. Our test user is a member of this
security group and should be able to access the Domain Controllers now. However this isn't working.
The error message we receive upon trying to connect:
The connection was denied because the user account is not authorized for remote login.
For troubleshooting, we also applied the Security Group for that setting in the Default Domain Controllers Policy but that doesn't seem to work either. We want to avoid customization on our Default Domain Controllers Policy but this was just a test case
for solving our problem.
What should we do to solve our problem?
I hope to hear from you soon.
Thanks in advance.

Hi, I just found out what the problem was. This site helped me alot:
http://blogs.technet.com/b/askperf/archive/2011/09/09/allow-logon-through-terminal-services-group-policy-and-remote-desktop-users-group.aspx
In my case, I had the group added to the Allow Logon Through Remote Desktop Services but was not added to the Builtin\Remote Desktop Users group. After knowing this I made some changes to our situation and are now using the builtin\Remote Desktop Users group
rather than a new self made Security Group. I also added the Remote Desktop Users to the Allow Logon Through Remote Desktop Service in the Default Domain Controllers Policy as this is not done by default. By default only the Domain Administrators are able
to logon through remote desktop services.
You do not need the 'Log on Locally' permission within the Group Policies.
In short:
Add the desired users/groups to the 'Builtin\Remote Desktop Users' security group.
Add the 'Builtin\Remote Desktop Users' security group to the 'Allow Logon Through Remote Desktop Services' within the 'Default Domain Controllers Policy'.
Thank you anyway for the fast reply.
Have a nice day!

Remote Desktop Manager 50% off for SysAdmin week!

It has not been posted here yet, but Devolutions are again offering 50% off a one-year licence of their excellent Remote Desktop Manager software. The offer is available at
https://store.devolutions.net/promo/sysadminThis program is something I use on a daily basis in my job, and to be honest I would be completely lost without it now. Manage just about any server or environment you have from a single program - RDP, VNC, SSH/Telnet, Citix, Teamviewer, LogMeIn, Radmin, XWindow. It will even give you status pages for VMware, HyperV & XenServer environments - and even AWS! The best part, it also integrates with Spiceworks.
Strong credential management and integration with popular services like KeePass and LastPass make it easy, and there is also automated VPN management (start connection, VPN opens & connects then the software opens the...
This topic first appeared in the Spiceworks Community

Thanks Jakub for "corflags" info.
Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
Error message when making RDP connection:
Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
http://www.filedropper.com/axinteropmstsclib-mremoteng
Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
so final .dll wasn't working.
Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
Hope it helps
P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

Logitech Cordless Desktop S 530 Laser for Mac

Is anyone using this keyboard? http://www.logitech.com/index.cfm/keyboards/keyboardmicecombos/devices/158&cl=us,en
I have had it with the BT Apple keyboard...
I have no intention of using the logitech drivers, and I am wondering how it behaves without them?
Any input would be appreciated

My Mac tech guy has one and loves it. There is a driver download on the Apple site that has the fully customizable control panel for it. Apparently it's a 50/50 shot of getting the correct driver disk in the box!
Here's the Apple download link
http://www.apple.com/downloads/macosx/drivers/logitechcontrolcenter.html
Deb.

Two critical regressions - Microsoft Remote Desktop 8.0.5 for OS X in Japanese environment

When connecting from an OS X host to a Windows 7 box remotely via RDC, there are two critical regressions I've noticed.
Prerequisites:
OS X host with RDC 8.0.5 and JIS keyboard
Windows 7 SP1, Japanese
First issue: yen sign vs. backslash
Upon connecting to the Windows 7 machine remotely, open a command prompt.
On a Japanese machine with ShiftJIS (MS932) encoding, the backslash character is represented by a yen sign.
RDC 8.0.5 is incorrectly sending U+00A5 (yen sign) whey typing the backslash key from the OS X JIS keyboard. RDC should be sending ShiftJIS character 5C (backslash) instead.
Typing a directory path in the command prompt appears to work as the backslash is represented correctly, however the underlying character is incorrect and commands cannot be processed.
Second issue: OS X keyboard IME on/off
The OS X keyboard has two keys to activate/deactivate the Japanese input mode editor, to the left and right of the space bar. These are both dead with RDC 8 and both keys send simple spaces (U+0020) to the remote host, which is useless and makes
Japanese input impossible.

Hi,
Please make sure that the keyboard language and system language are set to Japanese both on Mac and Windows 7.
However, if issue persists, you may have to use the On-screen Keyboard of Windows 7 as a workaround.
Type without using the keyboard (On-Screen Keyboard)
http://windows.microsoft.com/en-us/windows/type-without-keyboard#type-without-keyboard=windows-vista
Thanks.
Jeremy Wu
TechNet Community Support

Remote Desktop Access with Mac and Asus Transformer Prime

I have an E2000 router with the most current firmware. I have a Sony VAio laptop with Windows 7 Home Premium 64bit,a Macbook with 10.6.8, and a new Asus Transformer Prime with ICS.My work desktop is a Dell Optiplex 380 with Windows 7 Pro 32bit. I frequently work from home and have no issues remoting into to my work PC from by Sony laptop via VPN and RDP.However I have never been able to connect successfully to my work PC with my Macbook(using Remote Desktop Connection 2.1 for Mac OS) or Asus tablet(using WYSE Pocket Cloud RDP app for Android). I can however connect to the VPN itself on the Macbook and tablet without issue same as my Windows laptop. The other interesting part is I can connect via RDP when I am connected to a Mi-Fi 3g hotspot. So it is definitely something in the my Linksys E2000 blocking the connection for some reason. I have even set Port forwarding of 3389 with the ip's of both the Macbook and Asus tablet.I have also tried connecting via ethernet to the router with the same outcome. I cannot ping my work pc from either device as well.In addition the firewall on my work PC is completely disabled and all services related to Remote desktop access are enabled and running.Does anyone have any ideas?

For my tablet its own ip assigned by the router. Same with the macbook.the Pocketcloud RDP app also uses 3389.I have port 3389 set for both internal and external port and protocol "both" under the Single Port Forwarding tab in the router config.

Remote Desktop Connection stop working after upgrade from 10.5.8 to 10.6.1

I too could not connect to a W2K3 server with RDC 2.0.1 after upgrading from Mac OS X, 10.5.8 to 10.6/10.6.1. I have another Mac which is on 10.5.8 and connect fine with the same version of RDC 2.0.1 as well as other PC with Terminal Service Clients.
There is no change on the server side. I have uninstalled and reinstalled RDC 2.0.1 several time and it did not resolve the issue. To rule out firewall/network, I tested with another remote desktop application called CoRD (for Mac) on the same laptop running SL 10.6.1 and it connected to the same W2K3 server fine.
One thing that is worth mentioning (in my case), when it does not connect, RDC totally quit (not running anymore. Not minimize, no cannot connect error message, no little dot on the Dock for RDC, nothing) right after I put in the credential in. When looking at the log entries that are related to RDC in the Console application, I see the following
machine 10.6.1. with RDC 2.0.1 (non-working)
9/22/09 1:17:16 PM [0x0-0x3a03a].com.microsoft.rdc[468] objc[468]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . One of the two will be used. Which one is undefined.
On the 10.5.8 machine with RDC 2.0.1 (working), I see the following entries
9/22/09 1:13:23 PM [0x0-0x24f24f].com.microsoft.rdc[5502] objc[5502]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . Using implementation from /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL .
9/22/09 1:13:39 PM Remote Desktop Connection[5502] * _NSAutoreleaseNoPool(): Object 0x16a25c20 of class NSCFArray autoreleased with no pool in place - just leaking
Stack: (0x9277af4f 0x92687432 0x93062bf5 0x926ce0fb 0x9723dff5 0x9268d52c 0x92fd447a 0x92fd4753 0x92fd4a48 0x930375da 0x530bac 0x4831a2 0x483750 0x483c0b 0x47a811 0x4796ac 0x485dad 0x47d475 0x5099dc 0x574c70 0x4ade03 0x4ae65d 0x4ae6f7 0x4ac8dd 0x53260c 0x534187 0x4ae76a 0x4ae7d0 0x4ae88e 0x493925 0x4ae13d 0x533b1a 0x53da6c 0x94a48057 0x934b3155 0x934b3012)
Any help would be appreciated

Doing some more troubleshooting after my post above as I saw a couple of entries referencing Stop Light keep popping up in the log of the Console. I removed Stoplight and Cocoa Gesture (for good meausre) and RDC 2.0.1 started working. I think it is Stop Light which causes RDC stop working, but I don't have to time right now to put Cocoa Gesture back to confirm that. I might if I have the time or post here if you have Stop Light installed as well and removing it resolved the RDC issue for you.

Remote Desktop Client For Mac?

Hi! I wanted to get the remote desktop client by MS onto my iBook g4. I am running leopard, and the webpage says it is a universal application, but when I download the .DMG the Installer application comes up and tells me I need an Intel Processor. Anybody know what's going on here? And does anyone know if the 1.0.3 version will run under Leopard? If it does, would I need to download stuffit expander and Apple Disc Copy like it says, or is that built into Disk utility at this point? And would I need to download the .bin or the .hqx files? Thanks, any help will be appreciated!
Remote Desktop site:
http://www.microsoft.com/mac/remote-desktop-client
Download details for version 2:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=68346e0d-44d3-4065-9 9bb-b664b27ee1f0&displayLang=en
Download details for 1.0.3:
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=6573F9F1-8AE1-4DA9-A B5C-F8457ECDAF2D&displaylang=en

Ok. Found the program on the apple website and downloaded and it worked. I solved my own question.

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop 8.0.12 for Mac Typo

Similar Messages

Maybe you are looking for