Question forcing clients to access new server shares

[Guest AllenK]

Hello all,

 

I am going to be adding a new Win2k3 server to a domain. No problem there.

 

My question is if I give this new server a new name, how do I force the

clients to access the network shares on this server.

 

The server is basically just a file server and the users login with a batch

file in theNetlogon share that creates their drive mappings.

 

When I did this before, I had a hard time getting the clients to access the

new server shares. I had to manually remove the existing mapped drives from

the PC's then re-run the logon.bat file in the Netlogon share.

 

I know I can add the /d switch to remove the previous drive mappings. Maybe

I need to also add the /y switch so the users do not get a prompted.

 

I am looking at trying to do this w/o any user intervention on the client

side.

 

Hopefully this post makes sense....

 

Thanks,

Allen K.

[Guest Pegasus \(MVP\)]

Re: Question forcing clients to access new server shares

 

 

"AllenK" <AllenK@discussions.microsoft.com> wrote in message

news:68AF9E52-FBB6-4934-9AA1-5360482F3A83@microsoft.com...

> Hello all,

>

> I am going to be adding a new Win2k3 server to a domain. No problem

> there.

>

> My question is if I give this new server a new name, how do I force the

> clients to access the network shares on this server.

>

> The server is basically just a file server and the users login with a

> batch

> file in theNetlogon share that creates their drive mappings.

>

> When I did this before, I had a hard time getting the clients to access

> the

> new server shares. I had to manually remove the existing mapped drives

> from

> the PC's then re-run the logon.bat file in the Netlogon share.

>

> I know I can add the /d switch to remove the previous drive mappings.

> Maybe

> I need to also add the /y switch so the users do not get a prompted.

>

> I am looking at trying to do this w/o any user intervention on the client

> side.

>

> Hopefully this post makes sense....

>

> Thanks,

> Allen K.

 

You should have these instructions at the start of your logon script.

They will put an end to users mapping their shares manually and

getting Windows to remember them:

 

net use * /del /y > nul

net use /persistent:no

[Guest AllenK]

Re: Question forcing clients to access new server shares

 

And the other issue I have is the clients printers are \\servername\printer .

Any easy way to change this to point to the new server?

 

"Pegasus (MVP)" wrote:

>

> "AllenK" <AllenK@discussions.microsoft.com> wrote in message

> news:68AF9E52-FBB6-4934-9AA1-5360482F3A83@microsoft.com...

> > Hello all,

> >

> > I am going to be adding a new Win2k3 server to a domain. No problem

> > there.

> >

> > My question is if I give this new server a new name, how do I force the

> > clients to access the network shares on this server.

> >

> > The server is basically just a file server and the users login with a

> > batch

> > file in theNetlogon share that creates their drive mappings.

> >

> > When I did this before, I had a hard time getting the clients to access

> > the

> > new server shares. I had to manually remove the existing mapped drives

> > from

> > the PC's then re-run the logon.bat file in the Netlogon share.

> >

> > I know I can add the /d switch to remove the previous drive mappings.

> > Maybe

> > I need to also add the /y switch so the users do not get a prompted.

> >

> > I am looking at trying to do this w/o any user intervention on the client

> > side.

> >

> > Hopefully this post makes sense....

> >

> > Thanks,

> > Allen K.

>

> You should have these instructions at the start of your logon script.

> They will put an end to users mapping their shares manually and

> getting Windows to remember them:

>

> net use * /del /y > nul

> net use /persistent:no

>

>

>