Recently MS released Rollup 5 for Exchange 2010 SP2, I downloaded this version and ran an update on my test servers, the update was then pulled from MS site due to DAG issues and topology errors. I have seen these errors in my own environment.
Hopefully MS will release v2 soon to fix the problem that RU 5 caused.
So i decided to installed another Hyper-V server using Windows Server 2012 and i created another Exchange server to add to my DAG. I thought using .VHDX VM’s is great because of all the new features.
Upon connecting the newly created Exchange 2010 server to the existing DAG i noticed that it would not sync. So i dismounted the store, moved all log files to another folder, cleared out the “Passive Copy” folders and let the sync run again.
After 3 hours i had a “healthy” copy, but the CopyQueueLength and ReplayQueueLength would just not clear. I went and checked the log files and Exchange was complaining about a mismatch of the sectors.
I then realized that the newly created .vhdx works differently and has these features:
- Support for virtual hard disk storage capacity of up to 64 TB.
- Protection against data corruption during power failures by logging updates to the VHDX metadata structures.
- Improved alignment of the virtual hard disk format to work well on large sector disks.
The VHDX format also provides the following features:
- Larger block sizes for dynamic and differencing disks, which allows these disks to attune to the needs of the workload.
- A 4-KB logical sector virtual disk that allows for increased performance when used by applications and workloads that are designed for 4-KB sectors.
- The ability to store custom metadata about the file that the user might want to record, such as operating system version or patches applied.
- Efficiency in representing data (also known as “trim”), which results in smaller file size and allows the underlying physical storage device to reclaim unused space. (Trim requires physical disks directly attached to a virtual machine or SCSI disks, and trim-compatible hardware.)
So i decided on windows server 2012 to convert the newly created VM back to.VHD, after doing this all the queues cleared in a matter of minutes and Exchange was as happy as it could be.
Today trying to install an OS on a newly created VM i could not open the console for the guest. It kept giving an error “Cannot connect to virtual machine” and after a few seconds a screen pops up and asks if you want to try again.
Thought it was AV so i uninstalled it. That did not fix anything.
Disabled windows firewall, rebooted, still could not access the VM. I then checked and i could not access any of the other VM’s i had running.
Tried running vmconnect from a command prompt, still did not work.
Dug a bit deeper and opened up IPSEC manager and added in a rule as follows:
I gave it 5-10 min and after that i was able to open up the console of the VM.
Today while busy with SCCM and SCOM 2012 installations the feature Dotnetframework 3.5 needs to be installed.
Initially by selecting the feature and choosing install it fails at 50%.
Quick fix is the point to an alternative location and choose the DVD where the files are located and add the following: D:\sources\sxs or your drive letter and then start the installation.
Installation went through with no issues on both SCCM and SCOM servers.
Today i am removing the last of my Exchange 2003 servers and encountered this error while running the uninstall: setup failed while installing sub-component exchange activesync with error code 0x80072030
Quick check and the following services were stopped, so i started them and the uninstall ran until a point and gave me the same error:
World Wide Web
So what i ended up doing was running the uninstall directly from the CD and it worked. (make sure you run the uninstall with the administrator account)
Recently I installed Exchange 2013 Preview, very interesting that you don’t have a console which I think a lot of people are going to miss.
The install is pretty straight forward with 16 steps to complete of which step 14-16 take the longest.
Last night I received an email from MS that the release-to-manufacturing version is now available for evaluation. I’m going to download this and see what changes they have made.
More to come…