Go Down
-
I.T. Nerds... I'm installing Exchange SP2 on a cluster by PowerOfCheese on 23 Jan, 2009 13:10
-
Any personal experiences you'd like to pass my way?
-
#1 by StumpyDave on 31 Jan, 2009 08:20
-
Only just seen this one.
Did it go OK?
I always spec mission critical servers to have mirrored OS disks.
Ensure you have a decent backup of the mailstore and then dis-associate the mirror. It makes it much quicker to put it back when things go hideously wrong. I'm not aware of anything nasty to watch out for on this one. -
#2 by PowerOfCheese on 02 Feb, 2009 09:28
-
Hey Dave. Of course it didn't go okay. lol
Just started a ticket with Microsuck
*****************
I'm running a 2 node cluster of Exchange 2003 Enterprise. I was following the steps supplied by Microsoft http://support.microsoft.com/kb/328839
I stopped the cluster service on Node 2, installed SP2 which appeared to install fine. The next step is taking all resources offline except IP address, Physical Disk and network name. Start the cluster service, move virtual server to node 2 (node 2 now has SP2) then right click the group that contains "exchange virtual server 1" and select "Upgrade Exchange Virtual Server".
Much to my surprise and disappointment "Upgrade Exchange Virtual Server" did not appear in the context menu. At the top there is only REMOVE Exchange Virtual Server.
I've researched this and have only found one vague solution. Reinstall Exchange on that node. Are there any other solutions to this that don't require a reinstall?
******************************** -
#3 by StumpyDave on 03 Feb, 2009 06:34
-
I'll check my records to see if we've applied an SP since we moved to a clustered environment. Were you doing this live or in a test lab?
I try to build a small test rig for all the dodgy stuff so that we can break that at out leisure until we get the right solution. It never seems to work like the book says the first time.
Fingers crossed for you. -
#4 by PowerOfCheese on 03 Feb, 2009 08:23
-
There's no test lab. Just 1 live 2 node cluster. Workin without a net here.
I did get a fix from Microsoft that hopefully works. I'll try it a little later
These servers are 5 years old and the only issues I've ever had with them have been post windows updates. Every time I see new updates available I get sick to my stomach. lol
I hope this works.
*******
To correct this issue, we need to run the following command in the command line:
CLUSTER RES "<System Attendant Resource Name>" /priv ResourceBuild=455081984
Note:
1, Please replace <System Attendant Resource Name> with the name per your server.
2, A reboot is reported to correct the issue.
After the reboot, we should then have the option in Cluster administrator to upgrade the virtual server. Please also check the option by right-clicking the System Attendant resource.
******** -
#5 by The Scottish Ambassador on 03 Feb, 2009 08:44
-
After reading this thread, I now know why I work in food retail and NOT IT! By now I would have blown up every computer in the world
-
#6 by PowerOfCheese on 03 Feb, 2009 09:53
-
After reading this thread, I now know why I work in food retail and NOT IT! By now I would have blown up every computer in the world
Believe me my friend. The second I figure out how to make real money in the golf business, my I.T. days are over!
-
#7 by The Scottish Ambassador on 03 Feb, 2009 10:25
-
After reading this thread, I now know why I work in food retail and NOT IT! By now I would have blown up every computer in the world
Believe me my friend. The second I figure out how to make real money in the golf business, my I.T. days are over!
I am making £5500 from letting my house out to the BBC for the Open. That any good to you?
-
#8 by PowerOfCheese on 03 Feb, 2009 11:23
-
That's cool for you. I was thinkin more long term though.
-
#9 by The Scottish Ambassador on 03 Feb, 2009 11:42
-
That's cool for you. I was thinkin more long term though.
I know m8. I was kidding. Sorry. Its the crazy in me comin out