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 |
I'm fairly certain this has been discussed previously, yet I was unable to find anything related to it in earlier conferences or STARS... Consider the scenario where an ALL-IN-1 system has been installed, and the VMS account serving as the ALL-IN-1 Manager's account is named ALLIN1V24. The system is to be upgraded to Version 3.0, and the intention is to change the name of the manager's VMS account to ALLIN1V3 (or something different). What steps need to be carried out to accomplish this? Thanks, Steve
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
692.1 | Guessing... | ULYSSE::TORTUE::REDMOND | Tony Redmond (at the ATS) | Sun May 17 1992 18:31 | 26 |
Hi Steve, This is just a set of guesses... 1. Shutdown ALL-IN-1 2. Create the new VMS account 3. Delete the old one. 4. Change profile records for ALL-IN-1 accounts to use the new VMS a/c 5. Change the A1CONFIG records to use the new a/c 6. SET FILE/OWN=new_ac for everything in the [ALLIN1V24...] directory structure. 7. Start up ALL-IN-1 and see what breaks. Check that the sender and fetcher run, that priv'd and unpriv'd users can create and send mail, that the TM scan works, and the background formatter works. It's a start. Others may have more words of wisdom. Tony | |||||
692.2 | Make new UIC = old UIC | IOSG::TALLETT | Making broccoli | Wed May 20 1992 20:47 | 7 |
Well I'd cheat and make the new account identifier have the same value as the old account... That saves all those ownership problems. Regards, Paul |