RE: SP3

2013-02-25 Thread Michael B. Smith
I've been running it for months. SP3 is basically SP2 UR6 plus the necessary changes to support 2013 co-existence. Otherwise, there is very little new code. From: Steve Ens [mailto:stevey...@gmail.com] Sent: Monday, February 25, 2013 10:38 AM To: MS-Exchange Admin Issues Subject: SP3 Installed

Re: SP3

2013-02-25 Thread Steve Ens
During the pre-requisite checks, it also reminded me to turn off my AV and my backup exec services (beremote). Kind of nice of them to do that. On Mon, Feb 25, 2013 at 9:41 AM, Michael B. Smith wrote: > I’ve been running it for months. > > ** ** > > SP3 is basically SP2 UR6 plus the necess

Re: SP3

2013-02-25 Thread Candee
Thanks! I've been waiting to see how everyone else makes out. :) On Mon, Feb 25, 2013 at 10:41 AM, Michael B. Smith wrote: > I’ve been running it for months. > > ** ** > > SP3 is basically SP2 UR6 plus the necessary changes to support 2013 > co-existence. Otherwise, there is very little new

RE: SP3

2013-02-25 Thread Rupprecht, James R.
AM To: MS-Exchange Admin Issues Subject: RE: SP3 I've been running it for months. SP3 is basically SP2 UR6 plus the necessary changes to support 2013 co-existence. Otherwise, there is very little new code. From: Steve Ens [mailto:stevey...@gmail.com] Sent: Monday, February 25, 2013 10:38

Re: SP3

2013-02-25 Thread Steve Ens
I don't kiss and tell Candee, but I will patch and tell! Don't wait for me to make out... On Mon, Feb 25, 2013 at 9:51 AM, Candee wrote: > Thanks! > I've been waiting to see how everyone else makes out. > :) > > > On Mon, Feb 25, 2013 at 10:41 AM, Michael B. Smith > wrote: > >> I’ve been run

Re: SP3

2013-02-25 Thread Steve Ens
rs unfounded here. > > Jim Rupprecht > The University of Kansas > > - Original Message - > From: Michael B. Smith [mailto:mich...@smithcons.com] > Sent: Monday, February 25, 2013 9:42 AM > To: MS-Exchange Admin Issues > Subject: RE: SP3 > > I've been running

RE: SP3

2013-02-25 Thread Michael B. Smith
ase is to do rolling upgrades... and then when all upgrades are complete, use the RedistributeDatabases scripts. -Original Message- From: Rupprecht, James R. [mailto:jimruppre...@ku.edu] Sent: Monday, February 25, 2013 10:56 AM To: MS-Exchange Admin Issues Subject: RE: SP3 There is a database

RE: SP3 Install

2010-07-13 Thread Peter Johnson
Hi James I've always done recoveries/reinstalls by reinstalling the OS and Exchange to the same version as my backup. This reduces the number of possible variable that could bite you in the ass :) My recommendation, albeit not having done an Exchange 2007 SP1 re-install like this, would be to

RE: SP3 Install

2010-07-13 Thread Sobey, Richard A
Hi James, You MUST* reinstall/recover to the version currently in use i.e. SP1. Rollups are irrelevant. You can then do an in-place upgrade to SP3. However, after that, you will be able to perform future recoveries directly to SP3. Cheers Richard *You'll just get blocked/Powershell error if y

Re: SP3 Install

2010-07-13 Thread James Bensley
Hi Peter, Yes I also thought that restoring the server as-was would be the safest bet also but just thought I'd check :) Hi Richard, Thanks for the heads up, I shall restore to SP1 and then upgrade. I had wondered with the changes to the location of configuration settings etc moving stuff into a

RE: SP3 Install

2010-07-13 Thread Peter Johnson
] Sent: 13 July 2010 12:27 To: MS-Exchange Admin Issues Subject: Re: SP3 Install Hi Peter, Yes I also thought that restoring the server as-was would be the safest bet also but just thought I'd check :) Hi Richard, Thanks for the heads up, I shall restore to SP1 and then upgrade. I had won