Remote desktop client file name

Remote desktop allows you to configure and connect to another computer running Windows XP Pro. Here's what you need to know about the remote desktop connection dialog box, including a few parameters you're most likely to encounter. The Windows XP remote desktop connection dialog box provides you with everything that you need to configure and connect to another computer running Windows XP Pro. Then, you can launch and connect to a remote computer simply by double-clicking the RDP file.

You can also script a remote desktop connection, as Windows XP's remote desktop connection has an executable file that can accept command line parameters and be run from a batch file.

EXE, and the following are some of the most common parameters:. Microsoft Remote Desktop clients let you use and control a remote PC.

With a Remote Desktop client, you can do all the things with a remote PC that you can do with a physical PC, such as:. You can also use a Remote Desktop client to access your remote PC from almost any device. There are even clients for mobile smartphones! Here's a list of the latest versions of the client apps and where you can download them:. Before you start using the client of your choice, there are a few things you'll need to do first. Just as you would with a local computer, you'll need to configure your remote computer before you start accessing it with the client.

If you have any other questions that this article didn't answer, check out the Remote Desktop client FAQ. These are all local users. Does an RD Gateway need to be used for local users? We are using trusted certificates. Thanks for your help! I have a test group of about 20 users that are all using RemoteApps on a single single server.

RemoteApps all work great for all the users. All the users are in one building, on one subnet, and the RemoteApp server is in a different subnet. All users have the problem. Thanks a lot! Sorry for the delay in responding. The first of the year is super busy for us. I found no events listed either in Server Manger or going into Event Viewer.

There were, of course, some events, but they all were verbose or information. That caused a few problems initially, but they were, I thought, all worked out. I noticed in the RDP file that the gatewayhostname was using. I tried setting gatewayhostname to domain. Do you know from where it gets the gatewayhostname? For consistency, I'd prefer that it also used the domain. Our file type associations also have a problem when they try to open the file.

When we double-click on a file from the client, the application opens, but then we receive an error that the file can't be opened. If that is the case, it makes sense that the file type associations don't work either.

I checked the gateway configuration.