[gptalk] Re: Perplexing Logon script issue

  • From: "Omar Droubi" <omar@xxxxxxxxxxxxxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Wed, 1 Nov 2006 12:45:34 -0800

Why you figure this out how to remove the legacy entry:
 
Just create a new share on the same folder with the incorrectly type share
name so your users can connect to it by the old name.
 
 A single folder can be shared with multiple names.
 
Also- I have found instanced when a share is mapped and the share no longer
exists- it is difficult to remove- but if you recreate the share- just for
functionality purposes then the user deleting the share works much smoother.
 
Omar
 
 

  _____  

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Gray Troutman
Sent: Wednesday, November 01, 2006 12:22 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Perplexing Logon script issue


We had a similar problem here and found that we had to log in locally as
admin on the box, delete the mapping manually (net use /delete didn't work)
and then it worked fine.  That was for drive mappings that had existed
before the workstations had been moved to the domain, though. 


On 11/1/06, joakim dahl <joakim.dahl@xxxxxxxxx> wrote: 

if you run mapping using batch files , use .cmd instead of .bat
add a line before each new share like this
----
net use o: /d
net use o: \\server\share
----
you should look in to making it a vbs file instead to make it easier to
handle. 
you may also want to add printers this way....
depending on the size of your organization


brgds joakim


for each 


On 10/31/06, Washington, Booker <Booker.Washington@xxxxxxxxxxxxxx> wrote: 

That just might do the trick.

Thanks for the helpful hint.  I will let you know tomorrow when I work
with my users.

And I wonder why it looks like they are not even receiving the batch
file.  I had a pause line setup, but I never see the script run when I 
am at the user's workstation.

I will keep you posted.

Thanks again






-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Tuesday, October 31, 2006 5:33 PM 
To: gptalk@xxxxxxxxxxxxx  <mailto:gptalk@xxxxxxxxxxxxx> 
Subject: [gptalk] Re: Perplexing Logon script issue

Also, you might want to just do a net use o: /d |echo y at the beginning
of
your logon script just to get rid of that mapping. Mappings are not
supposed 
to persist unless you tell them too but I've seen inconsistent results
with
this.

Darren

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx  <mailto:gptalk-bounce@xxxxxxxxxxxxx>
[mailto:gptalk-bounce@xxxxxxxxxxxxx]
On
Behalf Of Nelson, Jamie R Contr OC-ALC/ITMA
Sent: Tuesday, October 31, 2006 2:25 PM 
To: '  <mailto:gptalk@xxxxxxxxxxxxx> gptalk@xxxxxxxxxxxxx'
Subject: [gptalk] Re: Perplexing Logon script issue

What are you using to map your drives? Batch or Windows Script Host
(VBS,
Jscript)?

//signed//
Jamie R Nelson
Systems Engineer / Analyst 
Ingenium Corporation
OC-ALC/ITMA
405.739.2811 (DSN 339)

-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:
<mailto:gptalk-bounce@xxxxxxxxxxxxx> gptalk-bounce@xxxxxxxxxxxxx]
On
Behalf Of Washington, Booker
Sent: Tuesday, October 31, 2006 4:23 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Perplexing Logon script issue 

I have a logon script setup for a group of users.

Initially, I made a mistake and had a mapped drive going to a wrongly
named
share

i.e, it was going to \\servername\hiddenshares$


it was suppose to go to \\servername\hiddenshare$ 


the mapped drive letter was O

I change the script to point to the correct location, but my users still
keep getting O going to the first wrongly named share


It's almost as if the logon is being cached and it keeps holding on to 
the
old mapping.

Any ideas as to why this would occur.


I have the logon policy set to wait for the network before applying
policy,
but they just don't seem to be getting the policy.  But all of the rsop 
and
modeling tests say that it IS getting the policy..

Signed.... so confused

:)



***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR
by
logging into the freelists.org Web interface. Archives for the list are
available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx  <mailto:gptalk-request@xxxxxxxxxxxxx> with
'unsubscribe' in the Subject field OR
by
logging into the freelists.org Web interface. Archives for the list are 
available at http://www.freelists.org/archives/gptalk/
************************

***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx  <mailto:gptalk-request@xxxxxxxxxxxxx> with
'unsubscribe' in the Subject field OR
by logging into the freelists.org Web interface. Archives for the list 
are available at http://www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx  <mailto:gptalk-request@xxxxxxxxxxxxx> with
'unsubscribe' in the Subject field OR by logging into the freelists.org Web
interface. Archives for the list are available at
http://www.freelists.org/archives/gptalk/
************************





-- 

Best regards Joakim Dahl

http://wize.spaces.msn.com  <http://wize.spaces.msn.com> 

msn joakim.dahl@xxxxxxxxx / icq 1596678 


Other related posts: