Christmas is over – and the New Year is approaching.
What will the next 12 months, or the next decade bring us? Flying Cars? Horses that poo gold?
Seriously, what it will bring is more updates. As I promise you, faithful readers, that I will post more in the NY in the hope that you guys come back and read regularly!
So have a good NYE, and a happy 2010 morning – hope the hangovers dont hit you too bad!!!
If you are not reading the step-by-step installation guide (any of them) and relying on Exchange 2010’s “pre-requisites” check, you may have an issue with OWA when done.
Basically when the setup program is checking the Pre-requisites for CAS, it doesn’t check to ensure you have the correct authentication protocols installed.
This can be remedied by adding them as follows;
I also enabled the Windows Authentication, just for good measure.
Post-install no need to force an IIS restart (I think it does it as part of the install TBH), just refresh your OWA logon page and login as you want 🙂
Typically when clustering the Exchange 2007 mailbox role, you would use one of the HT servers as a witness.
However with 2010 you are no longer required to move the HT/CAS roles onto separate servers – so where to place it?
Obviously the “official” MS answer would probably be to install an additional HT server into your organisation, but why when you have perfectly fine other servers in place?
I placed mine on the customers vSphere vCentre server. It’s always up, and is key to their environment, so I have no worries about it being neglected.
However when creating a DAG, I got an error message telling me that it could not enable the Share as it didn’t have permissions.
*** Ok – so this is where it gets confusing. Pre-SP1 (as pointed out in the comments by Devin) only required the following step;
1) Add the “Exchange Trusted Subsystems” group to the local administrative group on the server (if you are using a DC you will have to add it to the BUILTIN\administrators group, which I would prefer not to personally)
However, in an SP1 environment it looks like you also have to add the server you are attempting to use as a FSW to the “Exchange Servers” group. I have posted on Devin’s blog (http://www.thecabal.org/2009/12/busting-the-exchange-trusted-subsystem-myth/#comment-3282) to see if there can be any clarity on this matter – but it does seem like something changed in SP1.
Re-create the DAG (delete the one you got an error with) and voila, your selected server is now a witness to your DAG 😉
EDIT:My apologies to Simon from Techhead – I mean to cause no offence by copying and pasting his blog (nor did I mean to pass it off as my own work)
I have removed said post, and just left the link through to his site 🙂
I belive Update 1 resolves this “properly” – however for archaic reasons here is how to run vSphere client under Windows 7 / 2008 R2
Simon @ Techhead has posted a rather spliffing guide on how to enable the vSphere client under Windows 7 (and presumably 2008 R2)’;
Typically you would install the sysprep files to “c:\documents and settings\all users\application data…” on a 2003 vCentre server.
However, under 2008 this location is not accessible and has changed to;
“C:\Users\All Users\VMware\VMware VirtualCenter\sysprep”
Needs to be run on both the Client and Server;
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes