1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Limited Acces to local desktop

Discussion in 'Windows Home Server' started by Paul Taylor, Sep 4, 2009.

  1. Paul Taylor

    Paul Taylor Guest

    Hi there

    the normal route to access the remote desktop client is to boot the client
    pc into windows then run the RDP client from there.
    i know how to make it run at startup so it appears automatically once the
    client has booted but is there any way to make it the only thing that appears
    on the client screen so that the client has no acces to the client pc's local
    opperating system. the only thing they should be able to do is log on to the
    remote desktop without being presented with the local desktop and all its
    icons etc

    thanks for any assistance

    paul
    --
    Paul - South Africa
     
  2. Paul Taylor <PaulTaylor@discussions.microsoft.com> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hi there
    >
    > the normal route to access the remote desktop client is to boot the
    > client pc into windows then run the RDP client from there.
    > i know how to make it run at startup so it appears automatically once
    > the client has booted but is there any way to make it the only thing
    > that appears on the client screen so that the client has no acces to
    > the client pc's local opperating system. the only thing they should
    > be able to do is log on to the remote desktop without being presented
    > with the local desktop and all its icons etc
    >
    > thanks for any assistance
    >
    > paul<!--colorc--><!--/colorc-->

    Hi - this isn't a Terminal Services issue at all (in that your question
    could just as easily have to do with "how do I set the PC to run Solitaire
    only, and automatically?").

    You can do a lot with Group Policy to lock down your workstations, and you
    will find a lot of help for that in microsoft.public.windows.group_policy.
    Or, don't use windows workstations - use thin clients. Then it's a
    non-issue, and you've saved some cash [​IMG]
     
  3. "Lanwench [MVP - Exchange]"
    <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote
    on 06 sep 2009:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Paul Taylor <PaulTaylor@discussions.microsoft.com> wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Hi there
    >>
    >> the normal route to access the remote desktop client is to boot
    >> the client pc into windows then run the RDP client from there.
    >> i know how to make it run at startup so it appears
    >> automatically once the client has booted but is there any way
    >> to make it the only thing that appears on the client screen so
    >> that the client has no acces to the client pc's local
    >> opperating system. the only thing they should be able to do is
    >> log on to the remote desktop without being presented with the
    >> local desktop and all its icons etc
    >>
    >> thanks for any assistance
    >>
    >> paul<!--colorc--><!--/colorc-->
    >
    > Hi - this isn't a Terminal Services issue at all (in that your
    > question could just as easily have to do with "how do I set the
    > PC to run Solitaire only, and automatically?").
    >
    > You can do a lot with Group Policy to lock down your
    > workstations, and you will find a lot of help for that in
    > microsoft.public.windows.group_policy. Or, don't use windows
    > workstations - use thin clients. Then it's a non-issue, and
    > you've saved some cash [​IMG] <!--colorc--><!--/colorc-->

    As Lanwench writes, you can accomplish this with policies and
    registry hacks, but there are also a number of freeware utilies
    which do this for you. One that comes to mind is shelly:
    ?
    articleid=1722
    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Server
    TS troubleshooting:

    *----------- Please reply in newsgroup -------------*
     

Share This Page