New 2008 r2 DC

[techie08]

Hi everyone

 

Im about to put in a third 2008 R2 dc to eventually bring the last 2003 R2 DC offline and i was wondering wheather its ok to put SP1 on it?

 

The other 2 2008R2 dc's dont have SP1 on.

 

Not sure if its just me being paranoid again!!

 

Aslo we use exchange 2007. Would this have an impact moving to 2008 R2 dcs only?

 

Thanks

[steve]

Exchange should be ok as long as you don't raise your functional level.

 

The SP1 thing won't be an issue - how would you do it any other way - upgrade all 3 at exactly the same time? :-)

[techie08]

I thought Exchange 2007 was ok in a 2008 R2 domain funtional level???

[sukh]

it is, just means you cant introduce 2003 DC anymore

[steve]

I should have said don't raise it until everything is working OK, then read up on exchange 2007 functional level support.

 

Not sure if SP1 makes any changes to functional levels.

[Firefox]

nope no schema changes with regards to SP1, upgraded our via wsus easy enough, no errors reported.

 

You could argue the case if you need to go to SP1, it seems the update is based around virtualisation more then anything, we needed this to help further make use of Hyper-V, but I can see a lot of people not bothering with the update.

[PiqueABoo]

I can see a lot of people not bothering with the update.

 

I'll skip the war stories but don't underestimate the potential value of all those other fixes in SPs because one of them might jut save you lots of pain in future. OTOH it might create some new hurt, but this one was a long time coming and I haven't seen any significant screaming about it.

 

PS: SP1 fixed a bug that very nearly stopped me upgrading a 2008 "off-the-shelf" system to R2. [several PSS web-request KBs for that area had done nothing for it].

Edited May 19, 2011 by PiqueABoo

[Arthur]

I can see a lot of people not bothering with the update.

Apart from the 970 hotfixes and updates included with SP1, the service pack is mandatory if you have a server with an Intel Sandy Bridge processor in it and are using Hyper-V R2. Without it, you will receive VM could not initialize error messages.

Edited May 19, 2011 by Arthur

[3s-gtech]

All my new machines, both Server 2008 R2 and Windows 7, have SP1 on, but not rolled out via WSUS yet as I like to give the SPs a bit of time in the wild first. Any problems noticed?

[Firefox]

I'll skip the war stories but don't underestimate the potential value of all those other fixes in SPs because one of them might jut save you lots of pain in future. OTOH it might create some new hurt, but this one was a long time coming and I haven't seen any significant screaming about it.

 

PS: SP1 fixed a bug that very nearly stopped me upgrading a 2008 "off-the-shelf" system to R2. [several PSS web-request KBs for that area had done nothing for it].

 

I didn't say you couldn't run other updates without going fully to SP1

 

@ Arthur, we had the "VM could not initialise" errors too, but we did manage to resolve these before our SP1 update - although this did take a call to microsoft.

 

As with anything, it's going to depend on what your business it happy with risk wise. I have run the SP1 update on 52 DC's so far, and 3 have failed, and corrupted the OS...now for me 3/52 I can work around, if you have 1 and that fails.

 

Also seem to get a problem with some updates, whereby the roles section under server manager simply says "Error"

Edited May 20, 2011 by Firefox