No it’s not a new application. It’s the new name for TSCManager. At the time that name made sense to me 
Release notes:
The release can be downloaded at: Sourceforge.
26 Responses to “RemoteDesktopManager 1.0 release”
Comments are currently closed.
Stuff and more
No it’s not a new application. It’s the new name for TSCManager. At the time that name made sense to me
Release notes:
The release can be downloaded at: Sourceforge.
First of al, great tool!!!!!
thanks for that.
I have two questions,
Is it possible to integrate this tool with ICA. So that we have the possibility to choose with connection we want to use (RDP or ICA)
Second,
On this moment, it is possible to export the connections or place the connections to an other place. But if you forgot to copy/backup the RemoteDesktopManager_config.xml file than you can’t copy it back on a new/other system.
can you find a solution for this issue?
Regards,
Dirk
Dirk,
I would consider adding the option to connect to ICA, however I am not familiar with the ICA client (downloaded one from citrix, but don’t know how it works). If the ICA client can be started with a connection file as command line parameter, the parameter file is some sort of properties/xml file and the connection options are similar to RDP I don’t see why adding ICA support wouldn’t be possible.
About the second question. You don’t necessarily need the RemoteDesktopManager_config.xml to restore the connection files. The RDP files written by RemoteDesktopManager contain all the information to rebuild the connection tree except for the order of groups and connections. The option to set the RDP location is not yet how I want it. The (vague) plan is allow a shared location on a central place to share connections but allow local differences.
Daniel
have you considered adding possible VNC & putty options?
Brian, no I have not considered adding VNC and putty support to RemoteDesktopManager. Adding support for these and other protocols requires more of a universal connection tool. It’s not a bad idea but simply does not suit the RDM. Maybe in the future I will start developing such an universal tool. But at the moment I don’t really need it and don’t I have the time to develop it.
There is already a remote desktop manager
http://www.devolutions.net/products/RemoteDesktopManager.aspx
DAvid, I know there already is a Remote Desktop Manager tool. Problem is it’s not free for commercial use and does not look the way I like it.
It’s just for the name, your program is very nice, it’s just confusing when we do a search…
Awesome tool. I’ve been looking around for something just like this. Thank you. Would you by chance be able to add a sorting functionality to it?
Thanks.
Brian, I added sorting to the TO-DO list. I have not yet decided if I will add a right-mouse menu or add some buttons above/beneith the tree.
Hi
thank you a lot for this release but I have a question :
when I’ve tried to rebuild te source code one error appears :Assemblyinfo.cs and Increment.exe is exited with code 9009
hi there,
i’ve downloaded the remoteDesktopManager but i haven’t figured out how it can be launched, do i need a database? or a terminal server? if it is a database where is it?????
best regards
hi,,
iv just noticed that didou has the same problem i do:
Assemblyinfo.cs and Increment.exe is exited with code 9009
Da’3las, make sure you have .NET framework 2.0 installed. Other than that there is only a remote desktop dependency (which is by default installed on Windows XP).
I have it, ( .NET framework 2.0 ) ver. x86 , and I have Visual Studio Dot Net 2005 … , I can’t do any thing because this message, what it mean
( ” Error 1 The command “E:\New Folder\tscm_src_1.0\\IncrementBuildNr.exe E:\New Folder\tscm_src_1.0\RemoteDesktopManager\\Properties\AssemblyInfo.cs” exited with code 9009. RemoteDesktopManager
” )… plz help me ………………….
with my best wishes for you…
Da’3las
Ah, you are trying to build the app yourself (missed the clue in your post about increment.exe). I use express edition and that version lacks support for auto incrementing build numbers. That’s why I created the IncrementBuildNr.exe. It is called as a pre-build step. You can leave it out by editing the projects settings.
Thanks for you its build correctly
and i hope best wishes for you
Da’3las
Hi
thank you for your answer, But I’vnt understood how to leave it out form the project.
may be it is trivial task but I’m beginner in uing VS 2005,
TANK YOU FOR YOUR HELP
Ahh
it is ok I’ve left it out but I have a new warnning :
Warning 1 ‘System.AppDomain.GetCurrentThreadId()’ is obsolete: ‘AppDomain.GetCurrentThreadId has been deprecated because it does not provide a stable Id when managed threads are running on fibers (aka lightweight threads). To get a stable identifier for a managed thread, use the ManagedThreadId property on Thread. http://go.microsoft.com/fwlink/?linkid=14202‘ D:\mon PFE\interessant\tscm_src_1.0\RemoteDesktopManager\Utility.cs 86 83 RemoteDesktopManager
what to do in this casa? thank you for your help
Regards
didou, in reaction to both of your questions:
1) Why not use Visual Studio Express, it’s free even for commercial use. I guess the pre-build step is at the same location as VS Express:
Menu Project > RemoteDesktopManager Properties… > Build Events, then empty the text-field for Pre-build event command line
2) As you can read in the source-code, you can ignore the AppDomain.GetCurrentThreadId() warning.
Hi
Daniel really I would like to thank you very much for your interest and your help.
1)Concerning ignoring the warnning message, in fact when I build a solution i don’t get the ain form, I view only a consol for 1 second and no form is running.
2)what is the role of the project ” setuphelper” in your solution?
Really thank your very much for your responses.
Dear Sir,
Thanks you alot for this application, and I hope you best wishes in your life.
Please, I need some help from you in executing this application on a small network I had done it in my home and executed the application on it but I faced some problems.
In this link I had uploaded the pictures, there are commpressed, please extract it to show it.
http://rapidshare.com/files/26789847/RDP.rar.html
it’s 116KB.
In Picture 1, when I adding the informations and press the connection button the error in picture 2 has shown, and I don’t know what it means.
Please, Help me.
with my best wishes for you.
Da’3las
Well Da’3las the error means something expected was not provided. You can try to change the highlighted exception block in picture two to:
catch( Exception pe )
{
throw pe;
}
Hi,
Thank you alot for your help and instant response but I would like to know if there is any documentation for the code source of tscm?
In fact I haven’tknown why should I include Setup helpper, and how the connection to the remore host is done.
Thank you a lot for your help
Dear sir,
thanks faithfully for your help which you are presented for me . There is an important notice on your project that it makes the client locked when the server connected. I hope from you to answer me about my questioneer. Ineed to remote the client with out make it lock.
i.e any action the server do on the client’s desktop can be seen by the client itself.
with my all respects.
Looks like a useful tool, though it would be nice if we could set the password from within the application directly.
At present, there doesn’t seem like there’s an option to do this, so getting the password saved is a case of creating the connection in RDM, then creating it from the standard RD tool with the password and save password option checked, and then saving the rdp connection file over the one created by RDM in the connections folder.
Another useful feature would be to import existing connections from RDP files, or perhaps even go as far as to build the tree from the RDP files in the connections folder. That way we could just copy existing RDP files into the folder and name them using the Group-Name format.
Overall though, looks like a useful tool and will help to avoid the clutter of having lots of icons for different remote desktops
Mun, you can actually import existing RDP files. Just select and drop them somewhere (except the tree) on RDM. It does not however look at the directory structure so you have to set the group manually.
Saving the password would require some reverse engineering of the MSTSC tool from microsoft. If I can make a suggestion: upgrade the RDP client: http://support.microsoft.com/kb/925876 . The new MSTSC has a lot of new features and the security model in completely rewritten. It is still not possible to save from within RDM, but the process of storing the passwords in MSTSC works more logically (to my opinion).
You only have to install the new MSTSC once after that you can copy mstsc.exe and mstscax.dll from system32 to the RDM folder.
So hopefully this info is of any help to you.
Update: The new MSTSC is portable, but you need some more files to make it work. In System32 there is a map en-us with the files mstsc.exe.mui and mstscax.dll.mui. Copy those files (including the en-us directory) to the same location a you put mstsc.exe en mstscax.dll.