I’ve been installing Exchange 2013 in my lab environment recently. For Exchange I use a System- and Bootdisk and a Mailbox database disk in my lab. Sometimes I add a small disk to the server where the SMTP transport files are located, but this is always added after Exchange is installed.
Recentely I created a template where the C:\ (System- and Boot), D:\ (SMTP files) and F:\ (mailbox database) are already present BEFORE Exchange 2013 is installed.
Now what happens is that two additional directories are created on this D:\ drive during installation of Exchange 2013:
- D:\TransportRoles\Logs\SyncHealth. A small file is located in here called MSExchangeHMHost20140127-1 (that last part is the data the file is created)
It turns out that this is hardcoded in the setup application of Exchange 2013. I’ve received one email from somebody who saw this in Exchange 2010 CU3 as well, so most likely it happened earlier as well.
Since it is hardcoded, it happens only on drive D:\. If drive D:\ is your DVD player and the additional disk is E:\ the directories are not created.
This bug is filed at the Exchange team, now we have to wait what happens.
6 thoughts on “Strange directories in Exchange 2013 on D-drive”
Deployed CU6 today, and still have an error related to the MSExchangeHMHost regarding the D-drive, which is CD-ROM. Did you have received feedback regarding this message actually? Can’t seem to find any update about that… Thanks
It should be fixed, but I seen it still happen, even in CU7. It is annoying to see those show up, but it should not be a big deal. Is it causing issues in your case?
It’s not causing issues in operations at my side. Only generates that alert which looks simple to fix from my point of view… Let’s hope they adjust it, don’t like excluding events from monitoring and so on…
I have a situation where i should remove D: drive from the system. This folder exists on D: drive and the text files are generated to a subfolder.
It might not be a best idea just remove the disk without taking care of this folder first.
Have there been any news how this can be fixed?
I’ve installed CU1 as new server. The problem is still existing. 😦
Is there a light on the horizon?
I’m afraid this is one of the issues that will continue to be there as long as Exchange lives 😦