There are many ways:
- Use ssh. This requires you to install an SSH server on the target machines.
- Use WMI. This requires you to have the appropriate permissions in your domain to launch processes remotely.
- Have a periodic job on the target machines fetch and run a Perl program that sits at a well-known location. To run a program on a machine, you put the appropriate script into the well-known location.
- If it's just to access files remotely, just have the machines export the relevant directories via SMB.
- Use Win32::GUI to automate the Windows Terminal Server Client and send mouse clicks to it.
I don't know Windows Server 2003, but I'm told that you can operate it through the text console, so I assume that the Microsoft documentation about Windows Server 2003 has information on how to do that. I would read the documentation to learn more about the environment.
| [reply]
[d/l] |
Thank You Corion for your precious reply. Its quite shocking to know there is no module in perl to connect to a remote computer directly as Remote Desktop does without any dependencies. Anyway, will try all the ways you suggested. Thank You once again.
| [reply] |
Its quite shocking to know there is no module in perl to connect to a remote computer directly as Remote Desktop does without any dependencies
Why? It would be quite a useless thing to do. If someone wanted to do connections programmatically, it's because he wanted to issue commands or transfer files, neither of which Remote Desktop can do.
Besides, it's quite easy to do anyway: system("start my.rdp");
| [reply]
[d/l] |
If you know of any other programming languages who have a facility to connect to a remote computer directly as Remote Desktop does without any dependencies, I'm interested of hearing about them. But it sounded to me as if Remote Desktop was not essential to your needs anyway, because you tried to avoid the transfer overhead that the RDC protocol incurs.
| [reply] |