We use MCMS 2002 sp 1 on Windows 2003. Currently we are starting a user
migration. All user ID's will be changed. E.g. "contoso\parkerj" will become
"newcompany\james.parker". We are migrating from Windows 2000/ NT4.0 to a ne
w
Windows 2003 domain with SID history.

We use over 200 CMS Right groups, because of the large amount of editors.

Is there a way to automate this process regarding the permissions set in CMS
?
What do you recommend us to do?

Thanks for the help and suggestions.

- Paul

[ Post a follow-up to this message ]

Hi Paul,

no there is no supported way to achieve this.
It is recommended to assign an AD or NT group to the rights groups and do
the updates by adding users to the AD / NT groups.
Adding users directly to the MCMS rights groups is not very good from a site
management perspective as this cannot be automated.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------


"Paul Slijkhuis" <PaulSlijkhuis@discussions.microsoft.com> wrote in message
news:80034A6C-1E38-48CF-BA23-44D725402E92@microsoft.com...
> We use MCMS 2002 sp 1 on Windows 2003. Currently we are starting a user
> migration. All user ID's will be changed. E.g. "contoso\parkerj" will
> become
> "newcompany\james.parker". We are migrating from Windows 2000/ NT4.0 to a
> new
> Windows 2003 domain with SID history.
>
> We use over 200 CMS Right groups, because of the large amount of editors.
>
> Is there a way to automate this process regarding the permissions set in
> CMS?
> What do you recommend us to do?
>
> Thanks for the help and suggestions.
>
> - Paul

[ Post a follow-up to this message ]

Stephn,

I agree with your statement. Still a lot of improvements to be achieved.

To make my question more explicit:
Is the AEAuser table in a CMS db the only place to update a user's login nam
e?

If so, a smart SQL script will do the job...?

Cheers, Paul

"Stefan [MSFT]" wrote:

> Hi Paul,
>
> no there is no supported way to achieve this.
> It is recommended to assign an AD or NT group to the rights groups and do
> the updates by adding users to the AD / NT groups.
> Adding users directly to the MCMS rights groups is not very good from a si
te
> management perspective as this cannot be automated.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: [url]http://tinyurl.com/6zj44[/url
]
> ----------------------
>
>
> "Paul Slijkhuis" <PaulSlijkhuis@discussions.microsoft.com> wrote in messag
e
> news:80034A6C-1E38-48CF-BA23-44D725402E92@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hi Paul,

I'm not allowed to comment on the database schema as this is MS internal
information.
Touching the database would break the Microsoft Support Boundaries for MCMS
which would mean you could no longer request support for your solution if
any problems occur in the future.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------


"Paul Slijkhuis" <PaulSlijkhuis@discussions.microsoft.com> wrote in message
news:3BAF4E8D-F93C-4BB6-BA68-CA809DF0AA31@microsoft.com...[vbcol=seagreen]
> Stephn,
>
> I agree with your statement. Still a lot of improvements to be achieved.
>
> To make my question more explicit:
> Is the AEAuser table in a CMS db the only place to update a user's login
> name?
>
> If so, a smart SQL script will do the job...?
>
> Cheers, Paul
>
> "Stefan [MSFT]" wrote:
> 

[ Post a follow-up to this message ]

Hi Paul,

Doing something directly with MCMS database may cause many problems, mainly
database inconsistency. Other than the Microsoft support problem, it's
always a good idea not to do anything with your MCMS database to keep your
system away from many issues!

Cheers,
Chester.

"Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
news:ey6UGiSbFHA.1660@tk2msftngp13.phx.gbl...
> Hi Paul,
>
> I'm not allowed to comment on the database schema as this is MS internal
> information.
> Touching the database would break the Microsoft Support Boundaries for
MCMS
> which would mean you could no longer request support for your solution if
> any problems occur in the future.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS:
http://tinyurl.com/6zj44
> ----------------------
>
>
> "Paul Slijkhuis" <PaulSlijkhuis@discussions.microsoft.com> wrote in
message
> news:3BAF4E8D-F93C-4BB6-BA68-CA809DF0AA31@microsoft.com... 
do[vbcol=seagreen] 
user[vbcol=seagreen] 
to[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

In the end it appeared that CMS 2002 recognised SID history from the user in
Active Directory. Actually I did not have to do anything !

Thanks for the tips and advises. This community is alive indeed.

Regards, Paul

"Chester Ragel" wrote:

> Hi Paul,
>
> Doing something directly with MCMS database may cause many problems, mainl
y
> database inconsistency. Other than the Microsoft support problem, it's
> always a good idea not to do anything with your MCMS database to keep your
> system away from many issues!
>
> Cheers,
> Chester.
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:ey6UGiSbFHA.1660@tk2msftngp13.phx.gbl... 
> MCMS 
> http://tinyurl.com/6zj44 
> message 
> do 
> user 
> to 
>
>
>

[ Post a follow-up to this message ]