We have Windows 2008 Server with Terminal Server RemoteAPP services
installed.
The application I want to publish requires a mapped drive.
If I use a Remote Desktop session, I can launch the app fine. The "desktop"
environment gets the mapped drive either from Group Policy based on the user
logon or because the drive is mapped locally on the server.
If I use RemoteAPP, I am getting errors and the app is not working. It
appears (but I am not 100% sure) that the mapping might not be working.
Since there is no desktop environment, I can't verify mapping or even run
CMD to see what environment variables are set. I have a VB Script that runs
at logon which does mapping via group policy. The script is running but it
is erroring out. It does not error with a Remote Desktop session.
The goal is to get this working so home users can run the app when connected
to the internet.
What do I need to do to get this to work using RemoteAPP?
Try (for testing purposes) publishing cmd.exe as a RemoteApp. You can then
check to see what's happening.
Rob
"Saucer Man" <saucerman@nospam.com> wrote in message
news:488a06fd$0$19676$cc2e38e6@news.uslec.net...
> We have Windows 2008 Server with Terminal Server RemoteAPP services
> installed.
>
> The application I want to publish requires a mapped drive.
>
> If I use a Remote Desktop session, I can launch the app fine. The
> "desktop" environment gets the mapped drive either from Group Policy based
> on the user logon or because the drive is mapped locally on the server.
>
> If I use RemoteAPP, I am getting errors and the app is not working. It
> appears (but I am not 100% sure) that the mapping might not be working.
> Since there is no desktop environment, I can't verify mapping or even run
> CMD to see what environment variables are set. I have a VB Script that
> runs at logon which does mapping via group policy. The script is running
> but it is erroring out. It does not error with a Remote Desktop session.
>
> The goal is to get this working so home users can run the app when
> connected to the internet.
>
> What do I need to do to get this to work using RemoteAPP?
>
> --
> Thanks!
>
We tested Calculator and that works. The problem arises when the app
requires a mapped drive.
Thanks.
"Rob Leitman [MSFT]" <robleit@microsoft.com> wrote in message
news:u2m6Bmq7IHA.2416@TK2MSFTNGP02.phx.gbl...
> Try (for testing purposes) publishing cmd.exe as a RemoteApp. You can
> then check to see what's happening.
>
> Rob
>
> "Saucer Man" <saucerman@nospam.com> wrote in message
> news:488a06fd$0$19676$cc2e38e6@news.uslec.net...
>> We have Windows 2008 Server with Terminal Server RemoteAPP services
>> installed.
>>
>> The application I want to publish requires a mapped drive.
>>
>> If I use a Remote Desktop session, I can launch the app fine. The
>> "desktop" environment gets the mapped drive either from Group Policy
>> based on the user logon or because the drive is mapped locally on the
>> server.
>>
>> If I use RemoteAPP, I am getting errors and the app is not working. It
>> appears (but I am not 100% sure) that the mapping might not be working.
>> Since there is no desktop environment, I can't verify mapping or even run
>> CMD to see what environment variables are set. I have a VB Script that
>> runs at logon which does mapping via group policy. The script is running
>> but it is erroring out. It does not error with a Remote Desktop session.
>>
>> The goal is to get this working so home users can run the app when
>> connected to the internet.
>>
>> What do I need to do to get this to work using RemoteAPP?
>>
>> --
>> Thanks!
>>
>
>
I think that Rob meant: publish cmd.exe, then you can check if the
mapping is there and which environment variables are set.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
"Saucer Man" <saucerman@nospam.com> wrote on 28 jul 2008:
> We tested Calculator and that works. The problem arises when
> the app requires a mapped drive.
>
> Thanks.
>
>
> "Rob Leitman [MSFT]" <robleit@microsoft.com> wrote in message
> news:u2m6Bmq7IHA.2416@TK2MSFTNGP02.phx.gbl...
>> Try (for testing purposes) publishing cmd.exe as a RemoteApp.
>> You can then check to see what's happening.
>>
>> Rob
>>
>> "Saucer Man" <saucerman@nospam.com> wrote in message
>> news:488a06fd$0$19676$cc2e38e6@news.uslec.net...
>>> We have Windows 2008 Server with Terminal Server RemoteAPP
>>> services installed.
>>>
>>> The application I want to publish requires a mapped drive.
>>>
>>> If I use a Remote Desktop session, I can launch the app fine.
>>> The "desktop" environment gets the mapped drive either from
>>> Group Policy based on the user logon or because the drive is
>>> mapped locally on the server.
>>>
>>> If I use RemoteAPP, I am getting errors and the app is not
>>> working. It appears (but I am not 100% sure) that the mapping
>>> might not be working. Since there is no desktop environment, I
>>> can't verify mapping or even run CMD to see what environment
>>> variables are set. I have a VB Script that runs at logon
>>> which does mapping via group policy. The script is running
>>> but it is erroring out. It does not error with a Remote
>>> Desktop session.
>>>
>>> The goal is to get this working so home users can run the app
>>> when connected to the internet.
>>>
>>> What do I need to do to get this to work using RemoteAPP?
>>>
>>> --
>>> Thanks!
OH. I see. OK, Well yesterday I got it working but I haven't tested the
app fully yet. I created a .bat file which firsts maps the drive and then
changes the default drive and directory to this mapped drive. Then I start
the app. I like the cmd idea. I think I will publish it also just to see
what is going on. Thanks.
"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AE9A2AD3926Averanoesthemutforsse@207.46.248.16...
>I think that Rob meant: publish cmd.exe, then you can check if the
> mapping is there and which environment variables are set.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> "Saucer Man" <saucerman@nospam.com> wrote on 28 jul 2008:
>
>> We tested Calculator and that works. The problem arises when
>> the app requires a mapped drive.
>>
>> Thanks.
>>
>>
>> "Rob Leitman [MSFT]" <robleit@microsoft.com> wrote in message
>> news:u2m6Bmq7IHA.2416@TK2MSFTNGP02.phx.gbl...
>>> Try (for testing purposes) publishing cmd.exe as a RemoteApp.
>>> You can then check to see what's happening.
>>>
>>> Rob
>>>
>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>> news:488a06fd$0$19676$cc2e38e6@news.uslec.net...
>>>> We have Windows 2008 Server with Terminal Server RemoteAPP
>>>> services installed.
>>>>
>>>> The application I want to publish requires a mapped drive.
>>>>
>>>> If I use a Remote Desktop session, I can launch the app fine.
>>>> The "desktop" environment gets the mapped drive either from
>>>> Group Policy based on the user logon or because the drive is
>>>> mapped locally on the server.
>>>>
>>>> If I use RemoteAPP, I am getting errors and the app is not
>>>> working. It appears (but I am not 100% sure) that the mapping
>>>> might not be working. Since there is no desktop environment, I
>>>> can't verify mapping or even run CMD to see what environment
>>>> variables are set. I have a VB Script that runs at logon
>>>> which does mapping via group policy. The script is running
>>>> but it is erroring out. It does not error with a Remote
>>>> Desktop session.
>>>>
>>>> The goal is to get this working so home users can run the app
>>>> when connected to the internet.
>>>>
>>>> What do I need to do to get this to work using RemoteAPP?
>>>>
>>>> --
>>>> Thanks!
>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.