Migrating Users

Hi all,

I have a new machine installed and content migrated with TS 6.7.1. At present we are on TS 6.1 and we need to migrate all the users along with the designated role to new server.

Could anyone be kind enough to provide the path to be followed to do the same without / minimal downtime to the existing server?

All suggestions are welcome.

Find more posts tagged with

Comments

nipper

What OS ? You sig says Solaris.

Are you using LDAP or local accounts.

Are you keeping the normal roles ?

kaalraa

What OS ? You sig says Solaris.
Are you using LDAP or local accounts.
Are you keeping the normal roles ?

Hi Andy,
You have got the right OS...and we are using local users and need to migrate as normal users (Author, Editor, Admin and Master).

It was to be done in that way... as we dont want any user to face any difficulty in login once new server would be up for Production. Also.. there are some applications which are running in combination with IW role and our own customised role... and we are comparing them as well.

nipper

You will need to copy/integrate /etc/password, /etc/groups and /etc/shadow on the new server.

You will need to edit iw-home/conf/roles/tsusers.xml to add a master. I am not certain if you can automatically get the users into the new roles so you may need to do that via the GUI.

HTH

Andy

kaalraa

Has anyone used [font=Arial]iwusermigrate or

[/font]

[font=Verdana]iwaccessmigrate CLTs to upgrade the users from pre6.7 release to 6.7.1? Do they get all users migrated and thats too with the earlier role?

[/font]

Adam Stoller

Has anyone used [font=Arial]iwusermigrate or
[/font]
[font=Verdana]iwaccessmigrate CLTs to upgrade the users from pre6.7 release to 6.7.1? Do they get all users migrated and thats too with the earlier role?
[/font]

I believe that the one time I had (so far) to do this (also in a Solaris environment) we ran iwusermigrate and iwaccessmigrate -m and checked what it was planning to do - and then ran iwaccessmigrate -n so that it didn't try to create custom groups on a per branch / workarea level on the fly (if you need to run it a second time, you first need to touch /iw-store/TSManageAccess)

I also ended up writing a script using iwaccess add-permission-entry that looped through branches and users and such and assigned the specific roles we wanted for the users for the branches.

kaalraa

I believe that the one time I had (so far) to do this (also in a Solaris environment) we ran iwusermigrate and iwaccessmigrate -m and checked what it was planning to do - and then ran iwaccessmigrate -n so that it didn't try to create custom groups on a per branch / workarea level on the fly (if you need to run it a second time, you first need to touch /iw-store/TSManageAccess)

I also ended up writing a script using iwaccess add-permission-entry that looped through branches and users and such and assigned the specific roles we wanted for the users for the branches.

Hi Adam,

Thanks for a nice explanation, however i do not intend to change the access permissions and roles of the users working as of now... for any branch.

What i need all... is to pull all the users from the existing version (TS 6.1) along with their roles and migrate them to new version (TS 6.7.1) ... the only business requirement beneath that is ... no user should come back saying "i am not able to login".

nipper

How many users are you talking about ?

kaalraa

How many users are you talking about ?

Around 500.

nipper

OK so brute forcing it for 500 users may be a bit much. I guess you will have to try iwusermigrate

bcvbbbjnn

Dear Fish,

Could you please share the script using iwaccess add-permission-entry that looped through branches and users that assigns the specific roles we wanted for the users for the branches

It would be a great help Fish.

Warm Regards
Nirmal

Quote:
Originally Posted by kaalraa
Has anyone used iwusermigrate or iwaccessmigrate CLTs to upgrade the users from pre6.7 release to 6.7.1? Do they get all users migrated and thats too with the earlier role?

I believe that the one time I had (so far) to do this (also in a Solaris environment) we ran iwusermigrate and iwaccessmigrate -m and checked what it was planning to do - and then ran iwaccessmigrate -n so that it didn't try to create custom groups on a per branch / workarea level on the fly (if you need to run it a second time, you first need to touch /iw-store/TSManageAccess)

I also ended up writing a script using iwaccess add-permission-entry that looped through branches and users and such and assigned the specific roles we wanted for the users for the branches.
__________________
--fish
eFish-ent Consulting, LLC

Adam Stoller

Dear Fish,

Could you please share the script using iwaccess add-permission-entry that looped through branches and users that assigns the specific roles we wanted for the users for the branches

It would be a great help Fish.

This was something I threw together quickly - so I wouldn't claim it to be without issues - but ... (note it's hard-coded for the 'admin' role)[html]#!/apps/interwoven/iw-home/iw-perl/bin/iwperl
#======================================================================
use strict;
use warnings;
use TeamSite::Config;
#======================================================================
my $iwhome = TeamSite::Config::iwgethome();

my %NO_SUCH_USER;
my @branches = ;
#----------------------------------------------------------------------
# See note at bottom regarding DATA
#----------------------------------------------------------------------
my @users = ;
chomp(@users);
#----------------------------------------------------------------------
BRANCH_LOOP:
foreach my $b (@branches){
next BRANCH_LOOP if ($b =~ /(?:EDITION|STAGING|WORKAREA)$/);
print "$b ...\n";
USER_LOOP:
foreach my $u (@users){
next if ($u =~ /^\s*$/);
my $cmd = qq($iwhome/bin/iwaccess add-permission-entry $b -user $u -role admin);
my $result = qx($cmd 2>&1);
if ($?){
next USER_LOOP if ($result =~ /ERROR:00017:/); # entry already exists
if ($result =~ /ERROR:00925/) {
$NO_SUCH_USER{$u} = 1;
}
else {
die ("$cmd\n=> $result\n=> $?\n");
}
}
}
}

if (keys(%NO_SUCH_USER)){
print "The following users were listed in the UID files but no longer appear to be valid\n";
print "\t", join("\n\t", sort(keys(%NO_SUCH_USER))), "\n";
}
#======================================================================
# The original script had a list of userids entered, one per line, no
# white-space, below the DATA line ... You can either do that, or
# read the information from some other file (like conf/roles/*.uid)
#======================================================================
__DATA__[/html] Hope that helps.

bcvbbbjnn

Dear Fish,

Thanks a lot.

Warm Regards
Nirmal

bcvbbbjnn

Dear Fish / Devnet users,

This is wrto upgrade to TS 671 from TS 61.

In our environment we are making use of a single unix OS group for a branch which has a set of editors,authors and Administrators.

When we executed iwaccessmigrate -bg then that single os group speicific for a branch was getting both editor and admin roles. So by default the editor user is getting admin role for that branch

On the basis of kb article 57148 we had again rerun the iwaccessmigrate -m
steps in our environment as suggested by IW support.

But still we are facing the same issue.
Any idea.

Warm Regards
Nirmal