Mount Point Icon shown as Folder instead of Mount drive – Windows server 2012r2

Hi, today I want to shed some light on mount point icon when mounting a new volume on Windows server 2012 , perhaps you have had an issue whereby your mount point icon appeared as a normal folder icon instead of a mount drive icon.

A problem mount point Icon shown as a normal yellow folder with an arrow:-

partitionicon4

A normal mount drive Icon :-

partitionicon

Cause:-

You created the mount point folder from windows explorer first before using windows new volume wizard to bring online, enable and point your new volume to the mount point folder you manually created. Do not create the folder manually , rather use the new volume wizard to create it.

Solution:-

Make sure when you are creating a mount point, you need to create the mount point folder from the ‘New Simple Volume Wizard’ in disk management of your windows server.

partitionicon7

Create a new mount point folder and follow the prompts to complete

partitionicon9

Once it is done, your new mount point will appear with the correct mount drive icon :-

partitionicon

I hope this helps anyone who have encountered this issue.

Add domains to Internal Relay on Exchange 2010

Here is a quick step to add new domains to your internal relay on Exchange.

If you are not familiar with what internal relay means and what are its impact, you can head over to Microsoft technet and read more:- https://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx#Anchor_2

internaldomains

 

  1.  open up the EMC console and under Organization Configuration >> Hub Transport >> Accepted domains, in the actions menu, select New Accepted domain
  2.  Enter the display name, you can use a different name than the actual accepted domain or for me I prefer to keep it the same.
  3.  Select internal relay domain and save.

Via powershell command:-

new-AcceptedDomain -Name ‘contoso.com’ -DomainName ‘testdomain.com’ -DomainType ‘InternalRelay’

4. To verify that the new accepted domain is working, I usually like to test by sending a test message and then see the results, you can do this via powershell as follows:-

Send-MailMessage -From noreply@newcontoso.com -To “administrator@contoso.com” -Subject “Test internal relay ” -Body “Test only. Do not reply” -SmtpServer “name of your hub server”

View the result from message tracking log:-

Get-MessageTrackingLog -ResultSize unlimited -Start “08/06/2018 9:00AM” -Recipients “administrator@contoso.com” -sender noreply@newcontoso.com -Server”name of your hub server”

This will help you to know immediately if something was wrong with your configuration and you can go back and follow the steps again.