Oleg - you will find 2 similar security groups for every "default" security
group. The logic is as follows:
We have default security groups in Project Server 2003 and 2007. But due to
architecture changes, the default group is Project Server 2007 has a few new
permissions. We could have done 2 things:
1) Overwrite the default group in Project Server 2007 with the one in
Project Server 2003. Now you will see only one group, but you won't know
how the default security group (say Administrator) looked like in Project
Server 2007 - you will just have to rely on documentation.
2) Rename and retain the default group in Project Server 2007 - and also
migrate the one from Project Server 2003. After migration, the admin can
compare the migrated group with the "ProjectServer2007_" group, see if he
needs to change anything, then delete the "ProjectServer2007_" group. Now
you are left with just ONE group at the end. This is covered in the "post
migration tasks" section of the migration guide:
http://technet2.microsoft.com/Office/en-us/library/8fa78463-2066-4def-939f-c56eb9e66e1b1033.mspx.
=====Snip start========
Merge and rename similar security groups, categories, and templates and
Project Web Access view definitions: If there is a name clash while
migrating security templates, view definitions, or security groups or
categories, the migration tool attaches a prefix or suffix to the clashing
names. This action is taken to preserve both Project 2007 entities and
Project 2003 entities in one system. Then you can select which one to keep
or elect to merge them, as appropriate. We recommend that you resolve them
so that end users do not become confused.
====Snip end =========
We went with (2).
--
Thanx and regards
Pradeep GanapathyRaj [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm