If you have been using Remote Desktop Connection Client for Mac public beta2, you will be greeted by a message when you launch the beta today.
This simply means that the beta2 testing period has ended. We do this because the RDC public beta2 was released last October and has been out there for 5 months. As indicated on the dialog, you can continue using beta by dismissing the message dialog. Otherwise, the beta2 build you have stays fully functional. My team is moving full throttle to make the final release available for download from Mactopia by the end of May … if not earlier. Stay tuned, and thank you for your patience!
Update on RDC behavior after clicking "Continue Using Beta" - Some of you reported that RDC beta2 did not load the connection file you were launching RDC from, after selecting "Continue Using Beta". RDC beta2 will load your last used connection settings instead of the file you were trying to open. This is a known issue. Our current plan is not to do another beta because we are focusing all RDC resources on the final release. But I'd like to offer this workaround:
After dismissing the beta expiration dialog, use RDC menu command File->Open command to open your connection file.
This will launch a second RDC session that comes with its own beta expiration dialog, but you will be able to use your saved settings from the connection file after dismissing the second beta dialog.
I realize that this is inconvenient, especially for those of you who use RDC to run multiple connection sessions. My team understands this, and has been putting in extra effort to get the final release out to you as soon as possible. Again, thanks for staying with us!
...why not have the dialog pop up when the new version is actually released? Is it really necessary that I be nagged by this for the next 2+ months?
RomaineMan
Mar 31, 2008
9:30pm
Agree with Kurt
Why not simply notify us when v.2.0 is released? The current procedure (clicking "Continue Using Beta") is an unnecessary use of time. In addition, couldn't you just post on your downloads page something like this -- "Ooops, we were just kidding -- there really is no new version that you can download at this time." If there were such a message, it would wave folks a lot of wasted time that they will spend looking for the new version when they do click on "Download Latest Version," which you know 90% of the people will do.
Darren Davies
Apr 01, 2008
2:33pm
Serious problem with RDC beta and Mac Mini
I've been happily using RDC beta 2 for months now, excellent product by the way. I use a mac mini with a Dell keyboard. Ever since RDC has expired I can no longer type a backslash! As you know this is quite a useful character, I am now completely stuffed and may have to stop using my Mac altogether. I am extremely annoyed. Being able to use a Mac at work keeps me sane, and I can no longer work with it for at least a month!
On the Mac side the hash key produces a \ char, and it used to do the same in RDC. Nothing has changed and I am mystified that simply RDC expiring has caused this, I have spent hours trying to fix this problem and I am not impressed.
This does not mean that I am not grateful for the work the MacBU do, but I expected more! I did not expect a product to expire before the final release was available, that is just madness.
I expect to be able to download a new RDC beta with the time limit altered to expire AFTER the final release has been made available.
Laurie
Apr 01, 2008
3:03pm
Thanks, but...
I agree with many of the people above - we appreciate your work on this, but.... we need it to work! I have a whole lab that logs in to our server; the way this issue sits right now, I have to manually go to each machine and fix the setting. Not just once, but every single day for the next two months. While this version is faster with the Intels, it doesn't have the access to the remote devices that the old version did (with this version, you have to log off, put in the device, then log back in - why'd ya take that away??), so given this dialog box issue, we will probably revert for the next two months. It's not that the dialog box pops up - I could easily live with that - it's that it's not taking the last connection setting as it should, rather digging up something else.
Hope we get that patch we're all dreaming about.
taximan
Apr 02, 2008
12:03pm
JUST an expiration fix?
Sure, I'm in software development too - I also put an expiration date on my demo versions. Then each month, I go into my code and push the month value of the expiration date forward by 1.
And I am VERY aware that making a change somewhere causes the dreaded spaghetti effect - something unravels somewhere else.
But RDC obviously checks on a date (as it did to tell us the beta had expired) - could you guys not release another beta with the ONLY change being that the expiry moves to May 31?
Yes I know its not a deal-breaker going to Open each time we want to open an RDC file, but it gets pretty annoying when you open and close sessions the whole day long.
rogerbond
Apr 09, 2008
8:07pm
Snatching defeat for the jaws of victory
Beta2 was a nice improvement over the earlier versions. What's incredible is the way MS has managed to convert the goodwill of users into exasperation by hopelessly bungling the rollout. Why does a beta need a time bomb in it, anyway? If it has no teeth, and is designed only to annoy, it's probably a good idea to ensure you HAVE something for users to download when the bomb goes off. It's not rocket science to plan these things, is it? If you think you'll ship in April, have the bomb go off in August.
So now Microsoft looks like the jerk again, for 2 reasons: 1) not updating the product (even beta) in ages, and 2) refusing to issue a quick fix moving back the time bomb activation date. Refresh my memory - how was the MBU supposed to be unique again? This sounds just like the dopes who coordinated Vista.
The scaling windows, the quick shortcuts to fullscreen, all are forgotten in the face of planning so OBVIOUSLY bad, along with a patent disregard for the users. We're right back to the same old Microsoft.
John Boxter
Mar 31, 2008
10:25am
It's
...and there is no updated version or final release after all this time?
Ridiculous!
RDC User
Mar 31, 2008
10:25am
But...
It has to be clicked every single time I launch RDC. Notagood.
Jeremy Kemp
Mar 31, 2008
10:25am
No replacement
So, does this mean those of use who use this tool daily will have to continue clicking "Continue Using Beta" every day for the next two months, or is there an interim beta on the way to fix this? Thanks!
Mike Sax
Mar 31, 2008
10:25am
Will there be a beta 3?
Hi David, thanks for the update. Two quick questions:
1) Will there be a beta 3 or RC posted?
2) Will Font Aliasing make it in the final release?
Jeff
Mar 31, 2008
10:25am
Thanks
Keep up the good work and I look forward to the next release. I use RDC all day long everyday so it is an invaluable tool to me.
dab
Mar 31, 2008
10:25am
Thanks for the update...
Thanks...I'm glad you can still use the beta after the expiration date. Looking forward to the final release.
Nick
Mar 31, 2008
10:25am
Hello
The sooner the better. Keep up the good work!
Justin
Mar 31, 2008
10:25am
can you release a patch?
Can you release a patch so that users are not impacted with the Beta reminder every time they log in? To have to deal with the message for the next 2 months will be a huge pain, and reverting to the 1.03 option would be a travesty.
cookdorf
Mar 31, 2008
10:25am
Great news!
Been trying to find information on this all morning. Glad to know you're working on it. Keep up the good work and thanks for the heads up!
Update on RDC behavior after clicking “Continue Using Beta”
Update on RDC behavior after clicking "Continue Using Beta" - Some of you reported that RDC beta2 did not load the connection file you were launching RDC from, after selecting "Continue Using Beta". RDC beta2 will load your last used connection settings instead of the file you were trying to open. This is a known issue, but I'd like to offer this workaround:
- After dismissing the beta expiration dialog, use RDC menu command File->Open command to open your connection file.
- This will launch a second RDC session that comes with its own beta expiration dialog, but you will be able to use your saved settings from the connection file after dismissing the second beta dialog.
And there will be no beta3. I'd like to get the final release out to you guys at the earliest possible date, and that is where we are putting all our RDC team resources
David
zibeb
Mar 31, 2008
9:30pm
It's a shame that RDC files are ignored when after clicking
I understand the "need" for an expiring Beta. However, I don't understand why popping up the Beta Reminder message should break the functionality of Beta 2. Clicking "Continue Using Beta" results in loading the Default connnection instead of the file that was actually opened in Finder.
Alan Houtzer
Mar 31, 2008
9:30pm
END OF MAY????!!!!!
You are mistaken. RDC 2 Beta 2.0 does NOT continue to work. We start RDC from connection documents. After dismissing the dialog with the "Continue Using Beta" button, RDC ignores the settings in the connection document and will connect using the most recent connection settings. So it works only in the crudest and simplest situation -- when a person only ever connects to one server with one set of settings. In any other circumstance, RDC 2 NO LONGER WORKS.
All you have to do is re-release the same software with the expiration date moved forward. DO IT. You are killing us!
Bryan
Mar 31, 2008
9:30pm
Disable Upgrade Popup
I am going to continue to use the beta until the full release. I dont want to keep getting this popup until May or whenever the final release is out. How do i disable it for good?
Lars
Mar 31, 2008
9:30pm
Seconding the request for a 'no-nag' patch
I agree with everything Justin says above - you need to provide a way for your customers to disable the nag screen for the next two months.
Jon
Mar 31, 2008
9:30pm
Not an issue
To me, this issue couldn't be smaller in scope, so I regret that the above commenters are giving you guys so much grief.
Keep working hard; I look forward to the next release.
TC
Mar 31, 2008
9:37pm
Beta 2
Typically these expiration settings are designed to prevent or discourage use of a beta product after a new beta build, release candidate or final build has been made available.
If you're committing to deliver the RTM by May, couldn't you simply rerelease this beta, or "refresh" it with a built in kill switch for June 1? This way you can provide the early adopter community with a quick fix to let them continue to use and test the beta and you still can make sure people don't use it after the RTM.
I know a new release of anything is a non-trivial task but even simply re-releasing the current beta with a later kill switch would be greatly appreciated.
I look forward to the final version, as it is night and day above the 1.0 version.
DHA
Mar 31, 2008
9:37pm
Remote for MAC in Office 2008
Is Remote for MAC final 2.? part of the Office 2008 Suite?
pastafazool
Mar 31, 2008
9:37pm
What you mean is....
The latest version is not ready. Despite the inconvenient and inaccurate dialog, your only option is to continue using the beta version until the next version is, in fact, available - which is at least 2 months away.
It would be nice to not have to deal with this dialog for the next 2+ months...
Thanks
Rodney
Mar 31, 2008
9:37pm
Re: RDC Beta Users: Beta2 is Expiring, But Don’t Panic
As Justin said in an earlier post, can you just release a patch so we are not nagged to death?
Why do I feel that someone is asleep at the wheel at MBU?
-Rodney
RAVEN1185
Mar 31, 2008
9:37pm
Disable Upgrade Popup
It is very annoying and I use this all day every day. There has to be a way to get rid of it.
Kevin Del Castillo
Mar 31, 2008
9:37pm
so many issues
We have to use this software in our entire School district. We have to use the beta because we are using Intel Macs. Even after you click Continue with Beta, it does not grab the preferences from the RDC settings, so Screen Settings are messed up. Can we get at least get a new version of the beta with the time pushed?
Danny
Mar 31, 2008
9:37pm
Glad to see
Glad to see I am not the only one with this product. Here's hoping it is released soon. Keep up the good work.
Rick(UK)
Mar 31, 2008
9:37pm
I've only had it for 2 days but it's grat
I used the old version for ages and only twigged there was a new release a couple of days ago.
Big improvement over V1
But that nag message will be annoying. And I guess it's built in and there's no way to turn it off without releasing another version. Still, end of May is not too bad(you did mean May 2008 right? ( )
But ti's nice to see MS developing a really useful cross platform tool
rdc
Mar 31, 2008
9:37pm
So...
A new version, nice! I go looking for the new RDC-client, search through the whole site, download the current version, update etc. etc. Then I find this blog post... Its not the first of April today, is it?
NIshan
Mar 31, 2008
9:37pm
Must have workable RDP 2.0
Falling back to using the 1.x version for RDP is not feasible, for performance and feature reasons. We have over 50 servers we have to connect to with RDP, and the crippled 2.0 version (it doesn't have ability to use configuration files) isn't feasible either.
Is there a chance of releasing the same Beta 2.0 software, with the expiration date extended?
Hope to hear from someone at Microsoft.
Robbie Foust
Mar 31, 2008
9:37pm
nightly build?
I'd settle for a recent nightly build if it would get rid of the nag.
Sam
Mar 31, 2008
9:37pm
Disconnecting when being remote controlled from the host.
Were you aware that, for whatever reason, when an administrator on the windows server tries to remote control (or shadow) the client that is using RDC, it boot the RDC client out.
When it boots them out, the admin doesn't see anything either (he gets booted too).
This is a major problem when the admin is trying to do tech support with uneducated clients who are on the other side of the country.
Brett Randall
Mar 31, 2008
9:55pm
Kidding...
I run three or four remote desktops at a time, continually opening new ones. Every time I hit Apple-N to open a new one, in the background appears the question asking if I want to continue opening a beta. Except I can't Apple-Tab or Option-Tab to it, I have to click the bouncing icon in the Dock. Then I hit spacebar or Continue, and the field for the server name isn't even selected, nor is the window, so I have to click the text box before I can type. I better not have to do this for the next 2 months! Please, Microsoft, at least get rid of that dialog until the end of May.
Steve
Mar 31, 2008
9:55pm
Beta expire breaks opening of .rdp files
I have a stack on my dock containing all my .rdp files. Now that beta has expired, clicking on any of them causes the last successful connection to open, not the one in the file. For example, earlier in the day, I connected to my work PC, saved as work.rdp in the stack. Later I try to connect to my home PC, saved as home.rdp in the stack. After I dismiss the expiration dialog, RDC loads work.rdp, not home.rdp. I then have to go to the file menu to manually open home.rdp, which brings up the expiration dialog yet again, but opens the correct configuation file this time.
Someone needs to spend a little more time on the expiration UI.
First David, thanks for your team's hard work. Sounds like there are a lot of ungrateful people from the comments so far.
That being said, I really don't think it would take too many resources to simply remove the date-check code (or nag) and allow people to use the program seamlessly. It's not a big deal to someone like me who keeps the RDC connection open for long periods of time, but I can see it being quite annoying for those who login / logoff and no longer get an automatic login.
eisnerguy1
Mar 31, 2008
10:02pm
Wow, displeased with MacBU
Wow, the fact that MacBU can't release a very small patch to move the killswitch date to May is a bit surprising. I've tried using it after clicking "continue using beta" and it only loads the most recent settings. I NEED a functional Remote Desktop Client for school that connects to Windows. It seems that the MacBU is a sleeping a bit at the wheel. To wait AFTER it becomes an issue on MANY Mac sites, to release a statement is bad show MacBU, bad show indeed
former msft
Apr 01, 2008
2:33pm
Gotta love this
This so exemplifies why I no longer use use any Microsoft software, and I've been a Microsoft certified developer for 15 years.
Suyog
Apr 01, 2008
2:33pm
Annoying popup message
Can this be patched?
ralembik
Apr 01, 2008
2:33pm
Re: RDC Beta Users: Beta2 is Expiring, But Don’t Panic
Now I remember why I went to Mac at home. I just wasted almost an hour trying to upgrade my "Beta 2.0" only to find out that there is no upgrade.
Intel Mac User
Apr 01, 2008
2:33pm
We're not bashing but asking for an expiration fix!
Please do offer an expiration fix. As you might see from the comments, this is a very urgent and important thing we need.
Some here say we're ungrateful, but I can't see many bashings here. The reaction here should show you how many people are using your product. If it wasn't good, they wouldn't use it.
As already said, using the 1.x version is no option for us Intel Mac users.
So please, pretty please with sugar on top, give us back the opportunity to click on .rdp files again. That is so important, I can't stress this enough.
Please, guys. Come on. Don't just sit there and let us stand in the rain.
Please. Just an expiration patch or a fixed version. No new functions, only a Beta 2 as we got used to it. I wouldn't even care if you'd continue to keep Beta stage for another year, as long as we'd be able to use the app at all. At least it works so good that it can be used for everyday WORK.
Heads up, guys. Don't forget us.
zebrum
Apr 01, 2008
2:33pm
Wtf?
A mistake nag screen until May??? Are you having us on??? Release a fixed version NOW.
John
Apr 01, 2008
3:00pm
What a misleading post!
I binned my current beta as this message says a new version is available. But it's not! Oh!
How foolish of me!
Silly me, I should have realised - it's simply an alert msg telling me a non-beta version will be available sometime!
And it pops up every time I use the program!
Bless!
Isn't it wonderful how similar microsoft-speak is to politician-speak - say one thing and mean something completely different?
Josh
Apr 01, 2008
3:00pm
Not a good move, folks
I understand that the priority is (and should be) to produce a final release version of RDC, but given the expected timeframe until that point there absolutely should be either a Beta 3 or a refreshed Beta 2 that eliminates the expiration error. RDC is a niche product that doesn't generate any direct revenue, but still - if you're going to release it at all you should do it the right way. When RDC got put on back burner with the Office 2008 shipment slipping we knew this day would be coming. Something should have been done about it beforehand.
I will say this: Microsoft can (and has) produced some great Mac products over the years. But the trend of late hasn't been great. Between removing VBA support from Office 2008 (couldn't you have cut a deal with RealBasic or something? You used to provide their product in the box), and the issues it shipped with, and this RDC problem I see a lack of customer focus. Not good.
Jonathan White
Apr 01, 2008
3:00pm
Workaround for opening RDC connections
Not sure if this will work for everyone, but I've found that if I leave a RDC connection open to one of my servers, I can open another RDC connection file, and after accepting the nag screen, it opens that connection without incident. I've found that this is much quicker for me than manually opening a connection file from the File menu each time.
Ulf Dahlen
Apr 01, 2008
3:00pm
Problem with window size
If you just click the "continue using beta" button and connect, it doesn't respect the window size (this bug was in beta 1 as well). The workaround is to start one instance, click the "continue" button, then start another instance and click "continue" there as well, then it works... This is very irritating, to put it mildly! Couldn't you please give out a new beta without this date check?!
Tim F.
Apr 01, 2008
3:00pm
Extend the beta
David,
I appreciate the workaround you gave for using connection files by opening one first, which helps. But what's the deal with not extending the Beta? MS does it with other programs (PEP comes to mind).
Power users and sys admins are really crippled by this. It was a big surprise to me yesterday during our quarterly software release. I was not happy that it defaulted to my last connection (entering in 50 different addresses was not fun) and disabled dynamic window sizing.
zebrum
Apr 01, 2008
3:03pm
Cord - open source RDC
I've found a replacement, and it is awesome!! You can have multiple servers in a drawer, its fast, and has clipboard sharing. http://cord.sourceforge.net/
Comments | Who's Blogging This
Kurt
Mar 31, 2008
10:25am
Here's an idea...
RomaineMan
Mar 31, 2008
9:30pm
Agree with Kurt
Darren Davies
Apr 01, 2008
2:33pm
Serious problem with RDC beta and Mac Mini
On the Mac side the hash key produces a \ char, and it used to do the same in RDC. Nothing has changed and I am mystified that simply RDC expiring has caused this, I have spent hours trying to fix this problem and I am not impressed.
This does not mean that I am not grateful for the work the MacBU do, but I expected more! I did not expect a product to expire before the final release was available, that is just madness.
I expect to be able to download a new RDC beta with the time limit altered to expire AFTER the final release has been made available.
Laurie
Apr 01, 2008
3:03pm
Thanks, but...
Hope we get that patch we're all dreaming about.
taximan
Apr 02, 2008
12:03pm
JUST an expiration fix?
And I am VERY aware that making a change somewhere causes the dreaded spaghetti effect - something unravels somewhere else.
But RDC obviously checks on a date (as it did to tell us the beta had expired) - could you guys not release another beta with the ONLY change being that the expiry moves to May 31?
Yes I know its not a deal-breaker going to Open each time we want to open an RDC file, but it gets pretty annoying when you open and close sessions the whole day long.
rogerbond
Apr 09, 2008
8:07pm
Snatching defeat for the jaws of victory
So now Microsoft looks like the jerk again, for 2 reasons: 1) not updating the product (even beta) in ages, and 2) refusing to issue a quick fix moving back the time bomb activation date. Refresh my memory - how was the MBU supposed to be unique again? This sounds just like the dopes who coordinated Vista.
The scaling windows, the quick shortcuts to fullscreen, all are forgotten in the face of planning so OBVIOUSLY bad, along with a patent disregard for the users. We're right back to the same old Microsoft.
John Boxter
Mar 31, 2008
10:25am
It's
Ridiculous!
RDC User
Mar 31, 2008
10:25am
But...
Jeremy Kemp
Mar 31, 2008
10:25am
No replacement
Mike Sax
Mar 31, 2008
10:25am
Will there be a beta 3?
1) Will there be a beta 3 or RC posted?
2) Will Font Aliasing make it in the final release?
Jeff
Mar 31, 2008
10:25am
Thanks
dab
Mar 31, 2008
10:25am
Thanks for the update...
Nick
Mar 31, 2008
10:25am
Hello
Justin
Mar 31, 2008
10:25am
can you release a patch?
cookdorf
Mar 31, 2008
10:25am
Great news!
David Liu
Mar 31, 2008
5:07pm
Update on RDC behavior after clicking “Continue Using Beta”
- After dismissing the beta expiration dialog, use RDC menu command File->Open command to open your connection file.
- This will launch a second RDC session that comes with its own beta expiration dialog, but you will be able to use your saved settings from the connection file after dismissing the second beta dialog.
David
David Liu
Mar 31, 2008
5:13pm
And...
David
zibeb
Mar 31, 2008
9:30pm
It's a shame that RDC files are ignored when after clicking
Alan Houtzer
Mar 31, 2008
9:30pm
END OF MAY????!!!!!
All you have to do is re-release the same software with the expiration date moved forward. DO IT. You are killing us!
Bryan
Mar 31, 2008
9:30pm
Disable Upgrade Popup
Lars
Mar 31, 2008
9:30pm
Seconding the request for a 'no-nag' patch
Jon
Mar 31, 2008
9:30pm
Not an issue
Keep working hard; I look forward to the next release.
TC
Mar 31, 2008
9:37pm
Beta 2
If you're committing to deliver the RTM by May, couldn't you simply rerelease this beta, or "refresh" it with a built in kill switch for June 1? This way you can provide the early adopter community with a quick fix to let them continue to use and test the beta and you still can make sure people don't use it after the RTM.
I know a new release of anything is a non-trivial task but even simply re-releasing the current beta with a later kill switch would be greatly appreciated.
I look forward to the final version, as it is night and day above the 1.0 version.
DHA
Mar 31, 2008
9:37pm
Remote for MAC in Office 2008
pastafazool
Mar 31, 2008
9:37pm
What you mean is....
It would be nice to not have to deal with this dialog for the next 2+ months...
Thanks
Rodney
Mar 31, 2008
9:37pm
Re: RDC Beta Users: Beta2 is Expiring, But Don’t Panic
Why do I feel that someone is asleep at the wheel at MBU?
-Rodney
RAVEN1185
Mar 31, 2008
9:37pm
Disable Upgrade Popup
Kevin Del Castillo
Mar 31, 2008
9:37pm
so many issues
Danny
Mar 31, 2008
9:37pm
Glad to see
Rick(UK)
Mar 31, 2008
9:37pm
I've only had it for 2 days but it's grat
Big improvement over V1
But that nag message will be annoying. And I guess it's built in and there's no way to turn it off without releasing another version. Still, end of May is not too bad(you did mean May 2008 right? (
But ti's nice to see MS developing a really useful cross platform tool
rdc
Mar 31, 2008
9:37pm
So...
NIshan
Mar 31, 2008
9:37pm
Must have workable RDP 2.0
Is there a chance of releasing the same Beta 2.0 software, with the expiration date extended?
Hope to hear from someone at Microsoft.
Robbie Foust
Mar 31, 2008
9:37pm
nightly build?
Sam
Mar 31, 2008
9:37pm
Disconnecting when being remote controlled from the host.
When it boots them out, the admin doesn't see anything either (he gets booted too).
This is a major problem when the admin is trying to do tech support with uneducated clients who are on the other side of the country.
Brett Randall
Mar 31, 2008
9:55pm
Kidding...
Steve
Mar 31, 2008
9:55pm
Beta expire breaks opening of .rdp files
Someone needs to spend a little more time on the expiration UI.
Steve
Mar 31, 2008
9:55pm
Beta 2 feedback link broken?
Scott
Mar 31, 2008
10:02pm
Thanks, but...
That being said, I really don't think it would take too many resources to simply remove the date-check code (or nag) and allow people to use the program seamlessly. It's not a big deal to someone like me who keeps the RDC connection open for long periods of time, but I can see it being quite annoying for those who login / logoff and no longer get an automatic login.
eisnerguy1
Mar 31, 2008
10:02pm
Wow, displeased with MacBU
former msft
Apr 01, 2008
2:33pm
Gotta love this
Suyog
Apr 01, 2008
2:33pm
Annoying popup message
ralembik
Apr 01, 2008
2:33pm
Re: RDC Beta Users: Beta2 is Expiring, But Don’t Panic
Intel Mac User
Apr 01, 2008
2:33pm
We're not bashing but asking for an expiration fix!
Some here say we're ungrateful, but I can't see many bashings here. The reaction here should show you how many people are using your product. If it wasn't good, they wouldn't use it.
As already said, using the 1.x version is no option for us Intel Mac users.
So please, pretty please with sugar on top, give us back the opportunity to click on .rdp files again. That is so important, I can't stress this enough.
Please, guys. Come on. Don't just sit there and let us stand in the rain.
Please. Just an expiration patch or a fixed version. No new functions, only a Beta 2 as we got used to it. I wouldn't even care if you'd continue to keep Beta stage for another year, as long as we'd be able to use the app at all. At least it works so good that it can be used for everyday WORK.
Heads up, guys. Don't forget us.
zebrum
Apr 01, 2008
2:33pm
Wtf?
John
Apr 01, 2008
3:00pm
What a misleading post!
How foolish of me!
Silly me, I should have realised - it's simply an alert msg telling me a non-beta version will be available sometime!
And it pops up every time I use the program!
Bless!
Isn't it wonderful how similar microsoft-speak is to politician-speak - say one thing and mean something completely different?
Josh
Apr 01, 2008
3:00pm
Not a good move, folks
I will say this: Microsoft can (and has) produced some great Mac products over the years. But the trend of late hasn't been great. Between removing VBA support from Office 2008 (couldn't you have cut a deal with RealBasic or something? You used to provide their product in the box), and the issues it shipped with, and this RDC problem I see a lack of customer focus. Not good.
Jonathan White
Apr 01, 2008
3:00pm
Workaround for opening RDC connections
Ulf Dahlen
Apr 01, 2008
3:00pm
Problem with window size
Tim F.
Apr 01, 2008
3:00pm
Extend the beta
I appreciate the workaround you gave for using connection files by opening one first, which helps. But what's the deal with not extending the Beta? MS does it with other programs (PEP comes to mind).
Power users and sys admins are really crippled by this. It was a big surprise to me yesterday during our quarterly software release. I was not happy that it defaulted to my last connection (entering in 50 different addresses was not fun) and disabled dynamic window sizing.
zebrum
Apr 01, 2008
3:03pm
Cord - open source RDC
http://cord.sourceforge.net/