Category Archives: Microsoft Exchange

This blog has been moved to a new location

Hi everyone

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



Configuring Hyper-v Host Network Adapters for ISCSI Storage Connectivity with Powershell .

Chinny Chukwudozie, Cloud Solutions.

Windows Server 2012 R2 with PowerShell 4.0 has hugely expanded support for configuring multiple NICs on a Cluster/ISCSI Initiator node via command line. After deploying multiple Network Interface Cards on my Hyper-v host, it took me a while to figure out how to properly configure the NICS with PowerShell .

Prior to Windows Server 2012, NIC configurations could be accomplished with the GUI, Netsh command line utility or mainly WmiObject classes. The following cmdlets enabled me complete the configuration of multiple NICs on a cluster node:

List Available NICs on Host Server.

Get-NetAdapter -Physical


Rename Network Adapter for Storage/ISCSI Connection.

Get-NetAdapter -InterfaceIndex 15 | Rename-NetAdapter -NewName StorageNIC1


Set Private IP Address on Selected NIC.

Get-NetAdapter -InterfaceIndex 14 | New-NetIPAddress -IPAddress -PrefixLength 24 -AddressFamily ipv4


Disable Network Adapter Bindings.

Usually the Storage Network Adapter needs just the IPv4 TcpIp binding enabled:

PS C:\ Get-NetAdapterBinding -Name StorageNIC1

Name DisplayName ComponentID Enabled

View original post 345 more words

Converting a User Mailbox to Resource Room Mailbox using PowerShell.

Chinny Chukwudozie, Cloud Solutions.

In past versions of Exchange Server, specifically Exchange 2003, managing Resource Room mailboxes was not exactly a straight forward process. In my organization at the time, to manage room Calendars and bookings for Conference rooms (they were not referred to as Resource Rooms at the time), we had to create mailboxes to represent the conference rooms.

It was not possible within Exchange 2003 Server to automatically process conference room bookings and scheduling on the server side . One had to create a client side outlook profile representing the room mailbox and keep that outlook profile constantly running on some box to ensure room bookings were auto processed.

Exchange 2010 SP1 changed all that with the ability to process all calendar processes Server side. After I completed the migration from Exchange 2003 to Exchange 2010 SP1, I started the task of converting the conference room user mailboxes to type Room mailbox…

View original post 541 more words

Out of Office not working – Using Exchange Autodiscover Redirect

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 redirects to 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!

Meeting requests sent to a room mailbox, replaces the Subject, with the Senders name

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:

Exchange 2010/2013:

Set-CalendarProcessing -identity “meeting room name” -DeleteComments $true -AddOrganizerToSubject $true -DeleteAttachments $true -DeleteSubject $true

Exchange 2007:

set-mailboxcalendarsettings -identity “meeting room name” -deletesubject $false -addorganizertosubject $false

Hope this makes your life a bit easier.

Exchange 2010 Backups fail with Replica Writer Error

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:

  1. Open the command prompt on the Exchange server where the backup is failing. (In my case the server with the passive copies)
  2. In the command prompt type: vssadmin list writers and hit enter.
  3. 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.

When installing Exchange 2010 you receive “The start mode for the Net. TCP Port Sharing service must be set to Automatic before Setup can continue”

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:

  1. Open Power Shell on the Windows 2008 R2 Server that you are trying to install Exchange 2010.
  2. Type: Set-Service NetTcpPortSharing -StartupType Automatic
  3. Hit enter.
  4. 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.

%d bloggers like this: