Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hello, I have a customer who has been running ALL-IN-1 2.2 on VMS 5.1 for some time. They have now purchased a new system and want to move to VMS 5.5-1 and ALL-IN-1 3.0. The effort involved in upgrading seems huge. I have read various notes about transferring accounts between versions but none seemed to have as simple a configuration as in this case. The customer currently only uses the WP part of ALL-IN-1 (no EM, TM etc) and has only about 20 users. My question is Is it possible to build V3.0 on the new system, apply any customisations, create user accounts, add user profiles and then just bring back each users A1 directory? The only thing I had considered was that oafc$part_seed would need to be run for each user to put the old documents into the main drawer. Thanks for any input Regards Heather
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1597.1 | Should be OK | SIOG::T_REDMOND | Thoughts of an Idle Mind | Mon Oct 12 1992 18:56 | 9 |
Yes, it's possible. And with only 20 users it will probably take a lot less work than applying all the upgrades... Just thinking... will the internal SDAF changes (V2.3?) affect things.. or will ALL-IN-1's internal processing handle it? I think the latter is correct, but await confirmation from someone who knows more about it. Tony | |||||
1597.2 | Non-problem? | SCOTTC::MARSHALL | Do you feel lucky? | Tue Oct 13 1992 11:26 | 7 |
Hi, SDAF changes shouldn't matter, as if all documents are WP, there will be nothing in the shared areas. So the "empty" SDAF created by the V3.0 installation can be used. Scott |