KSBTech
asked on
Exchange 2007 SP3 Update Rollup 3-v2 doesn't reflect v8.03.0159.002 on server configuration screen
I just successfully upgraded from Exchange 2007 v8.2.176.2 to SP3 8.3.83.6. Rebooted the server verified v8.3.83.6 was listed on the server configuration screen and successfully tested functionallity.
I then upgraded to Exchange 2007 SP3 Update Rollup 3-v2 and received a successfull upgrade compleation message. Rebooted the server, but the version listed on the server configuration screen is still v8.3.83.6, when it should be v8.03.0159.002. I tried reinstalling Rollup 3-v2, but it didn't help. I have tested and Exchange seems to be working just fine.
We are using ForeFront Protection and I did disable ForeFront before installing the updates.
I haven't opened the server up to internal users or external mail yet and have a SAN snapshot of the Exchange programs, database and logs (D & L drives), but the OS (C drive) is on direct attached storage and I don't have an image of it.
I figured I would check to see if anyone else has run into this before trying to revert the SAN components back to SP2.
I then upgraded to Exchange 2007 SP3 Update Rollup 3-v2 and received a successfull upgrade compleation message. Rebooted the server, but the version listed on the server configuration screen is still v8.3.83.6, when it should be v8.03.0159.002. I tried reinstalling Rollup 3-v2, but it didn't help. I have tested and Exchange seems to be working just fine.
We are using ForeFront Protection and I did disable ForeFront before installing the updates.
I haven't opened the server up to internal users or external mail yet and have a SAN snapshot of the Exchange programs, database and logs (D & L drives), but the OS (C drive) is on direct attached storage and I don't have an image of it.
I figured I would check to see if anyone else has run into this before trying to revert the SAN components back to SP2.
ASKER
All three list 8.3.83.6; however, Program & Features Installed Updates says Update Rollup 3-v2... was installed on 5/15/2011.
ASKER
I wasn't sure if Rollup 3-v2 has a bug and simply fails to update the version information.
that might be, but the SP3 (v1) is definitlly buggy
have tried to deinstall v2 and v1 and reinstall v2 without v1
there is a ms kb article for those having trouble with the v1 rollup
regards
have tried to deinstall v2 and v1 and reinstall v2 without v1
there is a ms kb article for those having trouble with the v1 rollup
regards
So you do not have to worry. The roll up update have been sucessfully intslled on your exchange.
ASKER
numero_uno, how do I know that if the version information is telling me otherwise?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I opened a ticket with Microsoft and they were able to recreate the version reporting issue in their test lab. We confirmed that Update Rollup 3-v2 was successfully installed by validating the version of key binaries. It looks like this is a Rollup 3-v2 bug and simply fails to update the version information.
Looking at the version information from the exsetup.exe was also helpful.
Looking at the version information from the exsetup.exe was also helpful.
ASKER
I opened a ticket with Microsoft and they were able to recreate the version reporting issue in their test lab. We confirmed that Update Rollup 3-v2 was successfully installed by validating the version of key binaries. It looks like this is a Rollup 3-v2 bug and simply fails to update the version information.
Looking at the version information from the exsetup.exe was also helpful.
Looking at the version information from the exsetup.exe was also helpful.
HKLM\Software\Microsoft\Ex
Check the roles :
Mailbox/HUB/CAS
and check for the entry
Configured version
Now check the value there if Roll up update has been installed.
You can also verify the same from the EXBPA from the informational items