I decided to host my own site and moved this blog to my new website
This means I will not be updating any new content here. A huge thanks for following my blog and please continue following it at the above mentioned address.
Hope to hear from you soon 🙂
Tiens van Zyl
Had an interesting one today with a bit of a lesson at the end of the article.
Users are able to connect to Exchange with Outlook, send and receive mails etc. Users are however unable to set up their Out of Office using Outlook but they are able to set it using Outlook WebApp. We have a hybrid Exchange environment with 2010 and 2007 CAS servers. In the back-end we are running an Exchange 2007 CCR Cluster.
Past troubleshooting with regards to Out of Office not working has taught me to check and test autodiscover. I bet that the OAB is also not downloading?
I ran the normal checks such as checking the certificates and running nslookup to see if autodiscover.domain.com redirects to autodiscoverredirect.domain.com asn it did.
My next step was to check IIS as I’ve had a previous issue there. Low and behold I noticed that an ex-admin used his credentials for authentication. This caused issues as the admin’s account has been deleted a few days ago as he left our company. I then created a service account and added the credentials in IIS to ensure that this does not happen again. Users reported that Out of Office is working again.
Below are some screenshots for where I changed the credentials. Note that when I tried opening any settings under the Autodiscoverredirect Webpage in IIS that the error explicitly told me that the account for admin-abc had problems authenticating. The challenge was that I was not too sure where this is supposed to be changed. But here you go:
1. Open IIS on your CAS server and browse to Sites => AutodiscoverRedirect (Or whatever you named it)
2. On the right click on “Advanced Settings”
3. Click on “Physical Path Credentials” and then set. Add your service account credentials and save.
This solved my issue with redirection.
Lesson: No matter how many years of experience admins have, the still seem to take the quick route of using their personal credentials where a service account should be used causing issues for your users and customers. Don’t be a lazy engineer and use the service accounts and remember to document EVERYTHING!
We received a call today where a meeting request sent to a Room mailbox shows the meeting organiser’s name in the subject line.
This can be rectified by running the following:
Set-CalendarProcessing -identity “meeting room name” -DeleteComments $true -AddOrganizerToSubject $true -DeleteAttachments $true -DeleteSubject $true
set-mailboxcalendarsettings -identity “meeting room name” -deletesubject $false -addorganizertosubject $false
Hope this makes your life a bit easier.
We had a backup fail this week with an error stating something to the lines of Exchange Writer is in a failed state.
After some digging around I found that the Microsoft Exchange Replica Writer was in a failed state. To check the writers do the following:
- Open the command prompt on the Exchange server where the backup is failing. (In my case the server with the passive copies)
- In the command prompt type: vssadmin list writers and hit enter.
- You will now see a list of all the writers with their current state.
The picture below shows the writer in the failed state.
To resolve this issue I had to restart the Exchange Replication Service
I then re-ran vssadmin list writers in the command prompt and it showed its state as stable and the backups went through.
During my lab testing and installing Exchange Server 2010 on Windows Server 2008 R2 I keep receiving this pre-requisite that fails.
The start mode for the Net. TCP Port Sharing service must be set to Automatic before Setup can continue.
As far as I know (I might be wrong) this pre-requisite only fails the readiness check on Windows Server 2008 R2. In order to set the Net.TCP Port Sharing Service to Automatic at start-up do the following:
- Open Power Shell on the Windows 2008 R2 Server that you are trying to install Exchange 2010.
- Type: Set-Service NetTcpPortSharing -StartupType Automatic
- Hit enter.
- Run the Exchange installation wizard again and you should be good to go.
A good idea is to run the cmdlts on each of the Exchange server roles before you start installing Exchange 2010 as per this Microsoft article.