[THIN] Re: C: drive access through WI 4.2

  • From: "Hutchinson, Alan" <Alan.Hutchinson@xxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 5 Jul 2006 18:14:36 +0100

You're absolutely right - getting my synch and asynch back to front
.....

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Joe Shonk
Sent: 05 July 2006 18:01
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: C: drive access through WI 4.2


If anything,  you may need it to run synchronously.  W2k3 will run
scripts asyncronously by default.

Joe


On 7/5/06, Hutchinson, Alan < Alan.Hutchinson@xxxxxxxxxxxxxxxxxx
<mailto:Alan.Hutchinson@xxxxxxxxxxxxxxxxxx> > wrote: 

        Synchronously - used to do asynch years ago but don't seem to
have the same issues these days. Will try asynch tho'. No, nothing in
event logs I'm afraid.

  _____  

        From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
        
        Sent: 05 July 2006 16:04
        
        To: thin@xxxxxxxxxxxxx 
        Subject: [THIN] Re: C: drive access through WI 4.2
        

        Are you running you login scripts synchronously or
asynchronously?

         

        Is it possible that wfshell.exe is abending?  What do the event
logs show?

         

        Joe

         

        
  _____  


        From: thin-bounce@xxxxxxxxxxxxx [mailto:
thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf
Of Hutchinson, Alan

        
        Sent: Wednesday, July 05, 2006 6:42 AM
        
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: C: drive access through WI 4.2

        

         

        Rick,

        Not a dumb question at all.

        Only the two servers for this pilot at the moment - and only one
actually live (using the other one as test at the moment - so no, but I
expect other issues when we expand).

         

        No desktop I'm afraid. All published apps - my main farm is all
desktops, but for this environment I decided to go with published apps
due to the way that the CAG/AAC has hooks into PS4 (not that we're using
them at the moment). O.K. so I didn't give the full picture in my note
below but I have set up a second WI site also for testing purposes. When
I can get consistency through this I'll work back to AAC and then CAG.

         

        Despite 'manually' mapping as part of the logon script, when I
get my C: drive I also get my U: drive (I have a U on my PC). This U: is
not mapped as part of the logon script so I suspect this is not having
any effect.

         

        So what's the best way of wrapping that up as a published app (I
know I'm going to regret having asked that one).

         

        Regards,

         

        Alan.

         

        
  _____  


        From: Rick Mack [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Rick Mack
        Sent: 05 July 2006 12:40
        To: thin@xxxxxxxxxxxxx
        Subject: RE: [THIN] Re: C: drive access through WI 4.2

        Hi Alan,

         

        Dumb question, but how many Citrix servers do you have?

         

        Could the inconsistency be due to different ts connection
settings on different servers?

         

        Mapping aside, a fairly slick way to access client drives
without the mapping overhead is by using a shortcut to \\client\c$ on
the desktop to acces local files.

         

        regards,

         

        Rick

         

        regards,

         

        Rick

         

        Ulrich Mack 
        Volante Systems 

        
  _____  


        From: thin-bounce@xxxxxxxxxxxxx on behalf of Hutchinson, Alan
        Sent: Wed 5/07/2006 19:11
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: C: drive access through WI 4.2

        Andrew,

        If you mean 'trusted' or 'untrusted' in the sense of the
accomapanying article by Jeff - then it's untrusted. It's just that
its's not consistent e.g. I logged in this morning through our WI and
got my C: drive. Experience tells me that if I now log out and back in
again there is a high probability that I won't get this drive.

         

        It's really frustrating - I can sort of understand the rationale
to say that WI connection may be 'untrusted' - but surely that's down to
us to decide (and enable). Our homeworkers are currently using 'known'
PC's through an SSL VPN tunnel, all sorts of end-point scans etc. The
business has eventually decided that these would come into the category
of 'trusted'.

         

        Regards,

         

        Alan.

         

        
  _____  


        From: thin-bounce@xxxxxxxxxxxxx [mailto:
thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf
Of Andrew Wood
        Sent: 05 July 2006 09:58
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: C: drive access through WI 4.2

        when it fails is your connection trusted or untrusted? 

        
  _____  


        From: thin-bounce@xxxxxxxxxxxxx [mailto:
thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf
Of Hutchinson, Alan
        Sent: 04 July 2006 14:19
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] C: drive access through WI 4.2

        Have been requested to provide access to the C: for our
homeworkers (after much of a battle). Have enabled the appropriate
policies including Citrix ones and whilst I can see my C: through PN
connection to the desktop I'm having what I can only call inconsistent
c: drive mapping through WI. See the note from Jeff Pitsch
(http://www.brianmadden.com/content/content.asp?ID=504 ) to confirm.
Anyone with any ideas - I've tried doing a 'manual' mapping at logon but
this is also inconsistent.

         

        W2K3SP1, MPS4, WI4.2

         

        Regards,

         

        Alan.

        
########################################################################
#############

        This e-mail, including all attachments, may be confidential or
privileged. Confidentiality or privilege is not waived or lost because
this e-mail has been sent to you in error. If you are not the intended
recipient any use, disclosure or copying of this e-mail is prohibited.
If you have received it in error please notify the sender immediately by
reply e-mail and destroy all copies of this e-mail and any attachments.
All liability for direct and indirect loss arising from this e-mail and
any attachments is hereby disclaimed to the extent permitted by law.

        
########################################################################
#############


Other related posts: