It's not the server. This works from a Windows client. There is a leaked 2.1.2 RDC. Can any of my Microsoft buddies verify if there is an internal build?
2.1.1 is from March 2011
2.1.2 (leaked) is from September 2012
I really wonder why Microsoft is not issuing a fix.
Guess they'll have a new one /w the next Office which is due some time in March or so. Haven't seen any private or public beta so far, though...
We just shipped Office 2013 (RTM was 10/11/12). I don't know what group is responsible for RDC but I'll check with some friends in Windows and see what I can dig up for you V.
Oh, 11/10/12 in European. :-p
I have two Windows 7 PCs at work. I get that exact same message, on one of those PCs, when trying to remote to one particular server [Wndows Server 2008]. On the other PC RDC to that server works fine.
Remoting to other servers [Server 2008 and 2003] from the PC with the problem also works fine. Its just the one server I can't remote to.
So the problem is not restricted to the Mac version. But it does appear to be related to a combination of RDC and server.
We had this problem several times and it could be solved most of the time cleaning the terminal server license cache on the client. The cache is located in a folder named "RDC Crucial Server Information" which is anywhere under /users/shared/.
I just verified this folder is still used in 2.1.1 and 2.1.2 in the TSClient framework.
My mistake - I was referring to the Windows version of Office. Looking into what's going on with the Mac version of Office & an update to this.
nice to hear that - in my opinion - very political question in your blog ;-) We had lots of problems with customers using OS X 10.7 and 10.8 in combination with RDC 2.1.1. When I last downloaded the software, I realized for the first time that MS does not support those systems. This of course is ridicular, because 10.7 is now nearly 2 years old. The said version 2.1.2 which I found during searches works well. So for me too: Why does MS not offer that version or - even better - a newer one which also supports smartcards for logging in like the windows version does?
Christian, Amy cannot speak for Microsoft. I have since learned that you need to call Microsoft Support for the fix. And they track how often they ship it. Of course they are lying to themselves since we pass the code on in lieu of a more recent Microsoft download.
same problem here...where can I get the 2.1.2 Client ? On Microsoft Web is still 2.1.1...
Sven Bühler on Ich liebe diese Reaktionen at 21:14
Thomas Holzapfel on Olloclip 4-in-1 photo lens for the iPhone 6 and 6 Plus at 21:01
Christian Henseler on Statt Photoshop at 20:40
Volker Weber on Statt Photoshop at 18:54
Robert Jeschonnek on Glückwunsch @herr_lampe at 17:59
Christian Hensler on Statt Photoshop at 15:43
Ingo Seifert on Sonos Controller on BlackBerry at 15:38
Andrew Magerman on Withings Blood Pressure Monitor at 14:20
Frank Koehler on Sonos Controller on BlackBerry at 13:47
Hubert Stettner on Sonos Controller on BlackBerry at 12:43
John Keys on Statt Photoshop at 12:43
Hubert Stettner on Threema arrives on Windows Phone at 12:41
Hans Giesers on Ich liebe diese Reaktionen at 12:00
Hans Giesers on Ich liebe diese Reaktionen at 11:50
Ingo Seifert on Threema arrives on Windows Phone at 11:42
Marc Patermann on Ich liebe diese Reaktionen at 09:21
Maikel Maes on Ich liebe diese Reaktionen at 08:46
Thomas Lang on Ich liebe diese Reaktionen at 07:45
Hans Giesers on Ich liebe diese Reaktionen at 23:11
Alexander Siemes on Spotify :: voweXXL est mort, vive vowe! at 17:39
Marc Beckersjuergen on Ich liebe diese Reaktionen at 15:57
Volker Weber on Spotify :: voweXXL est mort, vive vowe! at 15:45
Benjamin Bock on Spotify :: voweXXL est mort, vive vowe! at 15:22
Volker Weber on Spotify :: voweXXL est mort, vive vowe! at 14:44
Benjamin Bock on Spotify :: voweXXL est mort, vive vowe! at 14:40