Group rename problem

[Guest Einari]

Hello,

 

We have Win2003 AD with about 2000 users.

A few days ago I had to rename a few security groups in our AD.

After the rename I made tests with my test accounts and all seemed to

function okay (network shares are mapped in logon script).

Later I got messages from users complaining that network shares no longer

work.

We discovered that manual mapping still works but login mapping doesn't.

Yesterday I made a new group with the original group name and added all the

original users there. I also added this new group condition to login script

(if ingroup group or ingroup original group then map network share).

Now login mapping works too.

 

Could someone explain this and how should this (group rename) have been done ?

 

Greetings

Einari

[Guest Meinolf Weber]

Re: Group rename problem

 

Hello Einari,

 

I have renamed very often groups and never had any problems, except if I

forget some changes in the scripts. So make sure that the scripts are ok

and also replicated to all DC's in your domain.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> Hello,

>

> We have Win2003 AD with about 2000 users.

> A few days ago I had to rename a few security groups in our AD.

> After the rename I made tests with my test accounts and all seemed to

> function okay (network shares are mapped in logon script).

> Later I got messages from users complaining that network shares no

> longer

> work.

> We discovered that manual mapping still works but login mapping

> doesn't.

> Yesterday I made a new group with the original group name and added

> all the

> original users there. I also added this new group condition to login

> script

> (if ingroup group or ingroup original group then map network share).

> Now login mapping works too.

> Could someone explain this and how should this (group rename) have

> been done ?

>

> Greetings

> Einari

[Guest Einari]

Re: Group rename problem

 

Hello Meinolf,

 

Thanks for the reply.

Yes, scripts are replicated okay.

I guess I should have noticed it if they weren't in my numerous tests with

my test account.

Well, today I'm going to check one of our clients status to see what's

happening there.

 

Regards

Einari

 

"Meinolf Weber" wrote:

> Hello Einari,

>

> I have renamed very often groups and never had any problems, except if I

> forget some changes in the scripts. So make sure that the scripts are ok

> and also replicated to all DC's in your domain.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

>

> > Hello,

> >

> > We have Win2003 AD with about 2000 users.

> > A few days ago I had to rename a few security groups in our AD.

> > After the rename I made tests with my test accounts and all seemed to

> > function okay (network shares are mapped in logon script).

> > Later I got messages from users complaining that network shares no

> > longer

> > work.

> > We discovered that manual mapping still works but login mapping

> > doesn't.

> > Yesterday I made a new group with the original group name and added

> > all the

> > original users there. I also added this new group condition to login

> > script

> > (if ingroup group or ingroup original group then map network share).

> > Now login mapping works too.

> > Could someone explain this and how should this (group rename) have

> > been done ?

> >

> > Greetings

> > Einari

>

>

>

[Guest Harry Bates]

Re: Group rename problem

 

After logging in with one of the offending accounts, open a cmd prompt and

type the following:

 

Echo %logonserver%

 

Then hit enter. Connect to the logonserver listed with ADUC and confirm that

replication of these groups has taken place and they are the correct name.

 

 

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

news:B334C3AC-3CF7-41CE-A29D-638203EB7273@microsoft.com...

> Hello Meinolf,

>

> Thanks for the reply.

> Yes, scripts are replicated okay.

> I guess I should have noticed it if they weren't in my numerous tests with

> my test account.

> Well, today I'm going to check one of our clients status to see what's

> happening there.

>

> Regards

> Einari

>

> "Meinolf Weber" wrote:

>

>> Hello Einari,

>>

>> I have renamed very often groups and never had any problems, except if I

>> forget some changes in the scripts. So make sure that the scripts are ok

>> and also replicated to all DC's in your domain.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

>>

>> > Hello,

>> >

>> > We have Win2003 AD with about 2000 users.

>> > A few days ago I had to rename a few security groups in our AD.

>> > After the rename I made tests with my test accounts and all seemed to

>> > function okay (network shares are mapped in logon script).

>> > Later I got messages from users complaining that network shares no

>> > longer

>> > work.

>> > We discovered that manual mapping still works but login mapping

>> > doesn't.

>> > Yesterday I made a new group with the original group name and added

>> > all the

>> > original users there. I also added this new group condition to login

>> > script

>> > (if ingroup group or ingroup original group then map network share).

>> > Now login mapping works too.

>> > Could someone explain this and how should this (group rename) have

>> > been done ?

>> >

>> > Greetings

>> > Einari

>>

>>

>>