michaelcamden46158
asked on
How to map a drive for terminal services.
I have a app that is installed on the local machine but then ran off a network drive. I am using terminal services in server 2008 beta to serve out just this one application. The application fails when TS is started due to not having this drive mapped. How do I map a drive for Terminal services to run an app.
ASKER
When I terminal serve just the app it does not run my logon script.
The application runs a logon script? Bit bizzare.
I'd just run it at actual logon as described above really, then the mapping exists when the application tries to run first time.
I'd just run it at actual logon as described above really, then the mapping exists when the application tries to run first time.
ASKER
Im only serving up the one app (new with server 2008). This app requires "start in network drive".
Ok, so if you've mapped a persistant network drive on the terminal server it will be able to start in the network drive as it does on your local PC.
Am I getting the wrong end of the stick here? Are you trying to run this application with no interactive session running on the terminal server?
Am I getting the wrong end of the stick here? Are you trying to run this application with no interactive session running on the terminal server?
ASKER
Its the same thing as a publishing an app with citrix. U copy the app.rdp to a user's desktop then when the user runs the app it starts the rdp session. Only problem is mine will not keep the drive mappings that it needs (already mapped on the terminal server).
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I have a terminal server that will map the drive but will not let me execute apps from that drive? Any ideas?
Just do a net use from the terminal server session to the relevant network share (the same that you have mapped on your local PC for the application).
E.G. net use I: \\<Server>\<Share> /persistent:y
If you want this to be mapped everytime a user logs on, create a quick batch to do this in the netlogon share (or even just stick it in the all users startup folder if you don't have a domain). HTH.