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:-
A normal mount drive Icon :-
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.
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.
Create a new mount point folder and follow the prompts to complete
Once it is done, your new mount point will appear with the correct mount drive icon :-
I hope this helps anyone who have encountered this issue.
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
- open up the EMC console and under Organization Configuration >> Hub Transport >> Accepted domains, in the actions menu, select New Accepted domain
- 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.
- 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 email@example.com -To “firstname.lastname@example.org” -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 “email@example.com” -sender firstname.lastname@example.org -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.
You may come across this error especially if you have not fully migrated all user mailboxes to the new exchange 2016, or co-existence with 2010, and you still have to resolve requests and help desk calls from both users, those not yet migrated and those already migrated, sometimes it could be even while migration is on-going.
“Cannot set the security descriptor of mailbox…….. in exchange mailbox database ……..”
Below command was executed to grant full access permission:-
Add-MailboxPermission -Identity “userA” -User “userB” -AccessRights FullAccess -InheritanceType All
And then it threw the error described above.
Powershell is throwing this error because the mailbox that you are trying to add permissions is hosted in a more higher version of exchange than the server you are running the command from. That means you should be running the command in Exchange 2016 where the mailbox of userA is now hosted after it was migrated, rather than in Exchange 2010 powershell in this case.
Simply to say:- You can’t change the properties of a user mailbox in Exchange Server 2013 or 2016 when you connect to a server that is running Exchange Server 2010. 🙂
- Check which database the mailbox is currently hosted on and which version of Exchange server. Use this command to check:-
Get-Mailbox -Identity UserA | fl database,exchangeversion
2. Use exchange 2016 powershell, or 2013 powershell depending on your result from step 1.
You can always refer here to know your versions of Exchange 🙂 :-
Another good tip would be to always first check which database and exchange version the user mailbox is on whenever you have a co-existence!
Today one of my client encountered this error while trying to add a new SMTP address to an existing mailbox account and it failed. He mentioned that the new SMTP address has never been assigned to any other mailbox in the organization.
Error:- The proxy address “smtp:email@example.com” is already being used by “contoso.com/Microsoft Exchange System Objects/BI176-Folder”. Please choose another proxy address.
The user mailbox is hosted on an Exchange 2007 mailbox database.
I suspect one of the public folder child item could be using this SMTP address, either it’s still in use or it’s orphaned.
To troubleshoot, I used ADSIEdit.msc tool to find the Exchange object causing the error, and under the attribute “class” it is marked “Public Folder”, on the properties dialog, I could see under “proxyAddresses” , the email address in the error was listed there.
Next is to use the tool PFDAVAdmin for exchange 2007,
Using PFDAVAdmin I was able to connect to the public folders in the organization and find one of the subfolders that was using the SMTP address shown in the error.
I requested user to choose another SMTP address, just as the error prompt suggested, and that solved it.
If the Exchange object is already orphaned and no longer in use in your organization you can delete it or rename the proxy-addresses attribute.
Today I will share with you my powershell command I use to quickly know what licenses are provisioned for a user in office365. It’s faster and saves the time to do it via the admin panel.
First you will need to have Microsoft Azure Active Directory Module installed for your windows powershell. You only need to do this once if you don’t already have this module installed.
To download this Module for your powershell, here is the OS requirements:-
- Windows 10, Windows 8.1, Windows 8 or Windows 7 Service Pack 1 (SP1)
- Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 SP1
Follow the steps here to install it:- https://docs.microsoft.com/en-us/office365/enterprise/powershell/connect-to-office-365-powershell
Connect to Azure AD for your office365 subscription:-
- In your powershell screen enter the below commands:-
$UserCredential = Get-Credential
Connect-MsolService -Credential $UserCredential
Type your Office 365 Administrator account user name and password, and then click OK. Now you are ready to check user license.
2. Enter the following command:-
(Get-MsolUser -UserPrincipalName firstname.lastname@example.org).Licenses.ServiceStatus
You can now see the service plans and licenses assigned to the user.
Today I was asked to create a new send connector. Its always good to have your information ready, or ask if not provided before getting started.
- Name of send connector to be created
- SMTP address space – e.g *.mail.contoso.com
- Smart hosts IP address
- Source servers that will route your emails.
Once ready you run the command in your Exchange powershell:-
new-SendConnector -Name ‘MYSENDCONNECTORNAME’ -Usage ‘Custom’ -AddressSpaces ‘SMTP:*.mail.contoso.com;1’ -IsScopedConnector $true -DNSRoutingEnabled $false -SmartHosts ‘[192.168.11.12]’,'[192.168.11.13]’ -SmartHostAuthMechanism ‘None’ -UseExternalDNSServersEnabled $false -SourceTransportServers ‘LAB-HCP01′,’LAB-HCP02′,’LAB2-HCP01′,’LAB2-HCP02’
You can refer to MSDN library link below for a full detail information about each important item to be configured on your send connector such as:-
Usage type:- For Send connectors, the usage type is basically a descriptive label that identifies what the Send connector is used for. All usage type values receive the same permissions.
Network settings:– Configure how the Send connector routes mail: by using DNS or by automatically forward all mail to a smart host.
Address spaces :- Configure the destination domains that the Send connector is responsible for.
Scope :- Configures the visibility of the Send connector to other Exchange servers in the organization.
Source servers:– Configure the Exchange servers where the Send connector is hosted. Mail that needs to be delivered by using the Send connector is routed to one of the source servers.
NOTE:- You can specify SMTP address spaces or non-SMTP address spaces on Send connectors that are configured on Hub Transport servers. You can only specify SMTP address spaces on Send connectors that are configured on Edge Transport servers.
I decided to earn my long overdue ITIL foundation certification. So I am now preparing and I’ve started studying for it. For those of you who already have your ITIL foundation, feel free to give me some exam preparation tips.