Terminal Server on Win 2k Advanced Server Scripting

[brodie1227]

Currently I have win2k server running. What I would like to do is have users be able to connect through rdc client(which they can) but only show the database which they will all be sharing. I would also like to know how to map their local c drive upon login so they can copy files to and from their workstation to server. I am no longer running active directory. Can you guys help me out. Thanks in advance for all who respond. Henry

 

[markdmac]

You would need to publish the application via TS and have the users log in to that. If you want your users to be able to connect drives, then they will need to be using the RDP 5 client which is provided in Windows XP or as a download from Microsoft.com. The users simply need to configure their client to allow access to the local disk.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[brodie1227]

Mark this is what I read under help in publish programs on the w2k server. I may not understand exactly how to do what you reccomend. Let me clarify what I want to do: Have users connect to TS. When they log into TS their c$ drive is mapped as well as the location of the application on the TS. It is an access database. No passwords are assigned by application, all users have access. What I want is for them to only be able to access the application. So when they log into TS only the application will be visible, no access to the desktop apps(IE etc.) or be able to see the other apps through start programs. I think the first thing I need to know how to do is have the TS be able to map a drive for only the application and deny the users access to browse the network through TS. I have not created log in scripts before, and appreciate your tips. I hope I am on the right track. Right now researhing Log in scripts. Thanks Mark.



'Assigned and published programs
Windows 2000 provides Windows Installer for deploying programs within your organization. You can assign a program to either computers or users, or publish programs to users. For more information, see Understanding Software Installation.

Because Terminal Services is able to provide multisession access to programs, additional consideration is needed before deploying applications in environments that contain Terminal servers.

Applications are installed on a per-computer basis for Terminal Services, meaning they are available to any user with access to the Terminal server. Terminal Services cannot accept published programs because they are published on a per-user basis. Additionally, assigned programs must be assigned on a per-computer basis, rather than on a per-user basis.

When installing assigned programs, anyone with administrative privileges on the Terminal server can install the program from either the console or from a remote session.'

 

[brodie1227]

The TS is configured in Application server mode also.

 

[markdmac]

You won't as far as I know be able to map a drive back tot he local user's hard drive. This is done dynamically by the RDP5 client. You would find it as "C on Client" in the drive listing ONLY IF the user has enabled that.

Also, if you take a look at the RDP5 Client, you will find there is a Program tab. This allows you to specify that Access is to be run. The user would not get a desktop at all, they would just see Access.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[brodie1227]

Mark, I think I am on to something. When I go to Terminal Services Configuration, to connections, and go to properties of the rdc5.0 protocal, and go to the client settings tab, under disable the following 'map client drives' this is grayed out wit no option to turn this service on. I need to have which ever client logs into TS, have their local C$ drive mapped so that file transfers to and from the TS can take place. Any suggestions? Your last post got me where I am at and can automatically launch the app upon login, and now just need to deal with file and data transfer preferably through mapped drives(local) as opposed to ftp or using citrix. Thanks Mark.

 

[markdmac]

I believe that using the Program settings of the connection disables the local drive option, though I don't have a server to test that on to verify if it is the case.

Can anybody else in the group help with this?

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[brodie1227]

Mark, I found out that you cannot use the feature in rdp5.0 properties,client settings, 'map client local drives' for windows server, and advanced server 2000. This can be done in server 03 but does me no good at this point. Trying to find the resolution any other suggestions are appreciated, thanks again.

 

[ShackDaddy]

You know what would be a better way to configure the applications? To not specify the "Program" on the client side, but to specify it on the server (Terminal Server Configuration Tool) under the RDP connection settings (Environment tab). That way the user can't tweak the local RDP connector settings to bypass this security. When specifying the startup environment in that manner, I believe that the options for drive mappings are still available.

Anyway, this might open up a better solution for you, but know that anything you change in that configuration area will affect every user who logs on. I have a server set up that way and I only use VNC to manage it, since every RDP connection to it automatically kicks off my custom shell.

ShackDaddy