Re: Migration 4.2 to 5.3

2004-08-15 Thread Gordon Woodward
[EMAIL PROTECTED] ERLING.COM To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Migration 4.2 to 5.3 EDU 13/08/2004 09:23

Re: Migration 4.2 to 5.3

2004-08-13 Thread Coats, Jack
harles [SMTP:[EMAIL PROTECTED] > Sent: Friday, August 13, 2004 6:28 AM > To: [EMAIL PROTECTED] > Subject: Re: Migration 4.2 to 5.3 > > RUn "cleanup backupgroups" prior to upgrade as it cleans out a bug where > win2k sysobj do not expire to the policies. > >

Re: Migration 4.2 to 5.3

2004-08-13 Thread Coats, Jack
to latest supported release! > -Original Message- > From: Loon, E.J. van - SPLXM [SMTP:[EMAIL PROTECTED] > Sent: Friday, August 13, 2004 6:59 AM > To: [EMAIL PROTECTED] > Subject: Re: Migration 4.2 to 5.3 > > Hi Jack! > I wouldn't use 5.3. It

Re: Migration 4.2 to 5.3

2004-08-13 Thread Loon, E.J. van - SPLXM
-Original Message- From: Coats, Jack [mailto:[EMAIL PROTECTED] Sent: Friday, August 13, 2004 13:23 To: [EMAIL PROTECTED] Subject: Migration 4.2 to 5.3 It is time upgrade :-) I currently have 4.2.1.3 on a windows 2K server. Going to upgrade to a Win 2003 server with the latest serv

Re: Migration 4.2 to 5.3

2004-08-13 Thread Hart, Charles
D] Subject: Migration 4.2 to 5.3 It is time upgrade :-) I currently have 4.2.1.3 on a windows 2K server. Going to upgrade to a Win 2003 server with the latest server (5.3 I think) Does anyone know of any upgrade problems with making that big of a jump? Even 'it would have been smoother/

Migration 4.2 to 5.3

2004-08-13 Thread Coats, Jack
It is time upgrade :-) I currently have 4.2.1.3 on a windows 2K server. Going to upgrade to a Win 2003 server with the latest server (5.3 I think) Does anyone know of any upgrade problems with making that big of a jump? Even 'it would have been smoother/easier if I had ...' stories? ... Jac