[THIN] Re: Published Explorer as an app, not a shell ... And how to restrict it?

  • From: "Landin, Mark" <Mark.Landin@xxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 21 Jul 2006 10:03:46 -0500

Well they DO have rights to access other parts of our enterprise file
servers and such, but I don't want them doing that from HERE this time.
I want them in one tree and one tree only.


________________________________

        From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Chris White
        Sent: Friday, July 21, 2006 10:00 AM
        To: thin@xxxxxxxxxxxxx
        Subject: RE: [THIN] RE: [THIN] Published Explorer as an app, not
a shell ... And how to restrict it?
        
        
        You could setup a group policy and only give them access to what
drives you want them to see. You could also setup file/share permissions
so they dont have access to other areas.
         
        Cheers,
        Chris.

________________________________

        From: thin-bounce@xxxxxxxxxxxxx on behalf of Evan Mann
        Sent: Fri 21/07/2006 15:51
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] RE: [THIN] Published Explorer as an app, not a
shell ... And how to restrict it?
        
        

        I did the following:
        
        1) Copy explorer.exe to an alternate location, rename to
        ctx_explorer.exe (for ease of finding in process view)
        
        2) Publish app as follows: ctx_explorer.exe /root,"c:\" (place
the root
        path in the quotes, can be any location.
        
        If you set the root path at say, H:\Jane, then it wont let them
go
        back/up beyond H:\Jane, but they can just go into the address
bar and
        type H:\ or C:\ or anything else and browse around.  I found no
way
        around this.  Hidding the address bar is one way to prevent it I
        suppose, but they can just show it again.
        
        -----Original Message-----
        From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On
        Behalf Of Landin, Mark
        Sent: Friday, July 21, 2006 10:38 AM
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Published Explorer as an app, not a shell ...
And how to
        restrict it?
        
        I need to give my users an Explorer file management window
published
        from a Citrix server, but when I publish it and they launch it,
they get
        a full desktop instead. I guess it's launching Explorer as a
shell, not
        as an app. So, how do I give my users an Explorer window, as an
app?
        
        I'd also like to restrict their browsing to a particular
directory tree
        and not let them get anywhere else, but am not usre how hard
that would
        be with Explorer. If others have alternative suggestions, I'd
like to
        hear them. Thanks!
        ************************************************
        For Archives, RSS, to Unsubscribe, Subscribe or set Digest or
Vacation
        mode use the below link:
        //www.freelists.org/list/thin
        ************************************************
        ************************************************
        For Archives, RSS, to Unsubscribe, Subscribe or
        set Digest or Vacation mode use the below link:
        //www.freelists.org/list/thin
        ************************************************
        

        Visit our web site http://www.basilica.co.uk
        
**********************************************************************
        This email and any files transmitted with it are confidential.
If you
        are not the intended recipient please contact Basilica Computing
on
        01462 708090 or by return email.It is Basilica Computing Limited
policy
        that the Company only enter into obligations, warranties and
representations
        which are signed in hard copy form by an authorised individual.
Personal
        messages sent from this email address are not authorised by
Basilica.
        This footnote also confirms that this email message has been
swept by
        MIMEsweeper for the presence of computer viruses.
        postmaster@xxxxxxxxxxxxxx
        
***********************************************************************

Other related posts: