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...
Volker Weber on Lenovo Yoga Tablet 10 HD+ at 17:34
Bernd Schuster on Lenovo Yoga Tablet 10 HD+ at 14:52
Mark Ehmann on Probably not at 12:28
Martin Cygan on Probably not at 10:59
Stephan H. Wissel on Probably not at 09:16
Tom Weeghmans on Probably not at 08:41
Scott Hanson on Probably not at 07:31
Erik Ferrari on Probably not at 01:30
Daniel Naumann on Probably not at 00:40
Uwe Papenfuss on Probably not at 23:50
Thomas Lang on Probably not at 23:44
Volker Weber on Lenovo Yoga Tablet 10 HD+ at 23:25
Sascha Westphal on Lenovo Yoga Tablet 10 HD+ at 23:18
Roland Dressler on The first million is always the hardest at 13:33
Thomas Lang on The first million is always the hardest at 14:14
Martina Kautz on The first million is always the hardest at 22:24
Pedro Quaresma on SensorCore :: Fitness tracking with an affordable smartphone at 19:56
Roman Weber on The first million is always the hardest at 11:54
Philipp Sury on The first million is always the hardest at 20:52
Karl-Henry Martinsson on The first million is always the hardest at 19:53
Bill Buchan on The first million is always the hardest at 19:20
Ben Poole on The first million is always the hardest at 16:42
Richard Kaufmann on The first million is always the hardest at 14:29
Richard Schwartz on The first million is always the hardest at 14:20
Volker Weber on The first million is always the hardest at 13:47