nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

swapping IP's and names TS 6.5

ProfessorX

OK, Heres one for ya.

Say on BOX1 whcih has win2k an TS 5.5.2 (OD 5.6) ...we will call that CMS
and on BOX2 whcih has win2k3 an TS 6.5, SP1 (OD 6.0.1) ...we will call that CMSX

No ADS on either ...and each is not part of a domain...and users have been created equally on each

If copy the store from CMS to CMSX
Then swap IP's and Computer names would I have to run iwidmap?
Hmmm...I think I just answered my own question...YES.
Even though the Names would be the same CMS\jdoe then sids would be different.

So here is my check list:
1. Run iwidmap -u -x on CMS
1a. Stop TS and all services on CMS
2. Make a copy of the store on CMS and copy it to CMSX
3. Pull the plug on CMS
4. Stop the services on CMSX
5. Swap out the CMSX store with the CMS store
6. Swap IP's and Computer names (KB 48503)
7. Restart the Server
8. run iwidmap on the store (KB 49980)
9. Pray
10. Test

Plese let me know if you see anything wrong with the above list

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Find more posts tagged with

Comments

lhdavis

I think if you are on TS 5.5.2 SP5 you need to upgrade to SP6 before moving to TS 6.5

Page 48 of the TS 6.5 Install Guide:
"For example, if you are upgrading from TeamSite 5.5.2, you must ensure that Service Pack 6 is installed before starting the TeamSite 6.5 installation program."

Just wanted to double-check. Thanks.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

ProfessorX

Luke-

I don't think this applies becasue I am doing a new install of 6.5 on the X box as apposed to an upgrade. Most SP's apply to iw-home rather than to iw-store. Anyone please correct me if I am wrong

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

lhdavis

I would just double-check with IWOV Support that no backing store changes are done with TS 5.5.2 SP6. Cause even though there aren't SUPPOSED to be any backing store mods with a service pack, you never know Smiley Happy

. Plus the compatibility matrix could be a "get out of jail free" card for them if you did not upgrade to SP6 first on your 5.5.2 box and then try to copy your backing store to a 6.5 box. You know how it goes.

Course you seem to planning on doing a test of your procedure to see if a 5.5.2 SP5 backing store comes up correctly on a TS 6.5 box (after you iwidmap) so my suggestion could be moot. IWOV Support should be able to tell you rather quickly if there are any changes to the backing store in SP6 though.

Not trying to make you do more work, just offering a suggestion on what to verify for your backing store migration path.

Other than that, everything looks good to me with your steps (especially the "Pray" one). Good luck!

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Adam Stoller

If you're moving the backing store to a freshly installed 6.5 server you do NOT need the SPs.
The SPs are for allowing the iwconvert / iwmigrate tools to interact with both source and target backing stores - by copying the backing store in its entirety you avoid this issue.

We did this from 5.5.2 SP2b on Solairs 8 to 6.5 on Solaris 9 -- (note you'll want to also install SP1 since its out now) -- and we verified this with IWOV Support prior to doing so.

Also note - when you run iwidmap to apply the changes for the mapping - follow it with the deactivation / reactivation of the store(s) - e.g.:

iwstoreadm -d default
iwstoreadm -a default

The above will make the change in mappings take effect.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ProfessorX

Going to do the cutover this weekend.

I know about
iwstoreadm -d default
iwstoreadm -a default

but I had problems with user groups not getting mapped right last go around for testing purposes

From KB 49980

Scenario 3

Administrator wishes to move the backing store from systemA to systemB.

Run the following command:
iwidmap -u -x c:\store.idmap c:\iw-store\default

Edit the file and change the ID and Name elements where needed.
Then run:
iwidmap -u -a -I c:\store.idmap c:\iw-store\default

Then two iwstoreadm commands need to be ran in the following sequence to activate the new backing store.
iwstoreadm -d default
iwstoreadm -a

Some of my groups for sharing didn't take...anyone expierence any similiar problems with grops and iwidmap?

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Adam Stoller

Hard to tell from your post is you realize this, but ...
If you're mapping groups you need to use the '-g' flag. The '-u' flag is for the userid maps.

We had issues with regard to mapping old OS-groups to new TS-groups (there's a thread on this somewhere - you should be able to find it) - once we got the specifics figured out it has worked just fine (and we've brought over new copies of the 5.5.2 production backing store to our 6.5 server several times now)

Mind you, I'm working on Solaris - haven't dealt with this on Windows for at least 2 years...thankfully ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jonwood

I'm in the same boat Ghoti, we're going from 552 to 6.5 on a new box. Also going from Solaris 7 to 9 and thus plan to implement Teamsite groups.

You mentioned: "once we got the specifics figured out it has worked just fine" ... care to elaborate? Smiley Happy

Here's my plan (please shoot it down if its lacking)

Server Setup:
old_box: current production box, TS 5.5.2, Solaris 7
- 8 backingstores, with ~300GB between them
- ~800 OS groups manage the permissions across the backingstores

new_box: upgraded production box, TS6.5SP1, Solaris 9
- 8 backingstores, data is same as old_box
- Plan to migrate the OS groups from old_box to tsgroups on this box

Action Plan:
1) Create a script to covert old_box’s /etc/group into xml file readable by iwgroup.
a. XML format is available on page 50 of ts.650a.clt.unix.pdf
b. MUST assign group “id” equal to the group’s GID from old_box

2) Ensure no groups in the xml file already exist in /etc/group on new_box
a. If a group is in both files, remove the group from /etc/group on new_box

3) Add snwspr01’s groups to tsgroups.xml
a. sudo iwgroup addmember -if xml_file.xml

4) Cleanup permissions
a. Run iwidmap for each backingstore and modify the resulting file
i. iwidmap -g -x ~/storename_map.txt /iwmnt/store_name
ii. for records in all storename_map.txt files, set “ID” to the GID of iwglobal on new_box??
iii. iwidmap -g -i ~/updated_map.txt /iwmnt/store_name
b. De-activate & re-activate all backingstores
c. Set the group of every file/folder in all content stores to iwglobal???

5) Verify permissions through GUI and shell access.

Adam Stoller

I believe the specifics are covered in this thread
As for:
4) Cleanup permissions
a. Run iwidmap for each backingstore and modify the resulting file
i. iwidmap -g -x ~/storename_map.txt /iwmnt/store_name
ii. for records in all storename_map.txt files, set ID to the GID of iwglobal on new_box??
iii. iwidmap -g -i ~/updated_map.txt /iwmnt/store_name
b. De-activate & re-activate all backingstores
c. Set the group of every file/folder in all content stores to iwglobal???

4.a.ii is correct [remove the '??']
4.c is incorrect - if you reused the old OS-group GIDs for the TS-group IWGID - it should "just work".

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com