At his point I’m going to assume you know that there are Standard Exchange CALs/SALs, and Enterprise Exchange CALs/SALs. And you know the difference! If you’re unsuresee my comments here.
With older versions of Exchange 2010/2007 etc. You could get this information from the GUI. Now you need to use some PowerShell.
Solution
The two commands you want to use are;
Find Out How Many Exchange Standard CALs / SALs Are Required
There are times when a problem with your Outlook profile can manifest itself in many ‘annoying’ ways. Sometimes the simplest thing to do is to put your Outlook profile to one side, and create a fresh new one.
Solution
Ensure Outlook is closed, open Control Panel > Set the view to ‘Small icons’ > Mail > Show Profiles.
Add > Give the new profile a sensible name > OK.
Configure you mail account, (if using Exchange, it should auto-configure for you) > Finish
Change the settings to ‘Prompt for a profile to be used’ > Apply > OK.
Open Outlook and select the new profile.
Make sure everything loads up and syncs correctly > Close Outlook again.
Once you’re happy, go back to the ‘Mail’ Settings, and change it to always use the new profile. You can delete the old profile if you wish > Apply > OK.
Related Articles, References, Credits, or External Links
I had to do this today and realised, it’s been so long since I did it last, I’d forgotten how to do it. Before we go forward, please be clear, I’m talking about MAIL CONTACTS, these are Active Directory Objects that have an Email address, but DO NOT have a mailbox in your Exchange Organisation, and DO NOT have an Active Directory User. I point this out because you can have MAIL USERS that have an Active Directory User Object and have an External Email address (i.e. a Gmail or Hotmail address) associated with the MAIL USER object.
Traditionally mail contacts are used for listing outside mail addresses in your global address list, (like mail users do) but are also used to forward mail to as well.
Solution
I was exporting from Exchange 2010, from the EMC run the following command;
You can see my exported CSV list in, DisplayName, Name, PrimarySmtpAddress format. You will need to do some work with it in Excel to get it in > Name, Firstname, Lastname, ExternalEmailAddress format.
Once you have you CSV file ready, import it into the Target Exchange Server with the following command;
I was doing a Domain/Exchange/RDS migration for a client this week. He had some Macros that he used for printing. Now Macros are something I know very little about. So I had made it clear, if he had problems with them, I would not be the best person to ask.
So when the call came in, that they were having problems with Macros I cringed! As it turned out, the problem wasn’t the Macros at all, it was the ‘Trust Center’ Settings in Word.
Error: Microsoft Office Trusted Location
The remote or network path you have entered is not allowed by your current security settings
Solution
I’m controlling all the office settings via group policy, this is easy to setup, and rather than reinvent the wheel read the following article if you don’t have GPO’s for office setup.
Now, that’s complete, you can solve this problem in one of two ways, (or both if you’re a belt and braces kind of a tech!)
Option 1
As you can see, (above), the location that the user was trying to add, was on a mapped drive (in this case S:), you can allow that from the following policy;
[box]
User configuration > Administrative Templates > Microsoft Word 2013 > Word Options > Security > Trust Center > Trusted Locations
[/box]
Pick one of the locations and configure as follows;
Option 2
Or simply allow the user to add network locations, to the trusted locations, from the following policy;
[box]
User configuration > Administrative Templates > Microsoft Word 2013 > Word Options > Security > Trust Center > Allow Trusted Locations on the network
[/box]
Enable the policy.
Related Articles, References, Credits, or External Links
A client asked this morning if there was a way he could see each users mailbox size, this is pretty simple to do see here. But he wanted to see each individual folder, and see a breakdown on the sizes of these folders.
Solution
Display Folder Sizes For an Individual User
From the Exchange Management Shell, execute the following command;
[box] Get-MailboxFolderStatistics pete | Select Identity,Name,FolderSize,ItemsinFolder | Export-Csv C:Petes_Folder_Size.csv[/box]
This will export to a CSV file in the location specified above.
Display Folder Sizes For All Users
From the Exchange Management Shell, execute the following command;
When attempting to set my Out of Office automatic replies within Outlook, I was greeted with this.
Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.
If I logged into Outlook Web Access, (Options > Set Automatic Replies) I could set it up and it worked fine.
It’s never really bothered me, but my colleagues were complaining about it, and when they used Outlook on our Terminal Server they also got this.
MailTips could not be retrieved.
Solution
Before proceeding you need to make sure of TWO things.
1. You are logged in, or authenticated against your domain.
2. If you are accessing web pages via a proxy server, the name of the Exchange server should be added to the Proxy Exceptions list. (Note: If you have multiple entries, you separate them with a semi colon).
Assuming you have met the two requirements above, then do the following.
1. Open Outlook > In the task bar (in the system tray) > Hold down CTRL and Right Click the Outlook Icon > Select Test E-mail AutoConfiguration.
2. Enter your details > Use AutoDiscover > Test.
Note: Here I got the following error message;
Autoconfiguration was unable to determine your settings
This was because the client I was on, could not resolve autodiscover.my-domain-name.co.uk, once that was rectified I could get further.
3. In the first section Locate the URL that is being used for OOF, and make a note of it.
4. Open your web browser and make sure you can open that URL. (Note: It will redirect to Services.wsdl that is normal).
Note: If you are asked for logon credentials, you are NOT authenticated against the domain.
5. Repeat the same with the URL that is listed in the HTTP section of the test.
6. At this point mine started working. My problem was the lack of DNS resolution, if you find another fix drop me a line and Ill update this article (link at the bottom of the page).
Incorrect Permissions on the EWS Virtual Folder.
Just after I wrote this site follower Peter Dorner Emailed me to say,
Another common problem, is that the EWS virtual directory has misconfigured permissions in IIS.
So I checked permissions on some working systems, to see what they should be.
EWS Permissions Exchange 2007 on IIS 5
EWS Permissions Exchange 2007 on IIS 6 onwards
EWS Permissions Exchange 2010 on IIS 6 onwards
Note: As shown anonymous is enabled for the IUSR account.
EWS Permissions Exchange 2007 on IIS 6 onwards
EWS Permissions Exchange 2013 on IIS 7 onwards
Note: As shown anonymous is enabled for the IUSR account.
Related Articles, References, Credits, or External Links
After building a new Exchange 2013 Server on my test network and changing the Certificate over, I ran a few updates and rebooted. Post reboot I was greeted with this,
VERBOSE: Connecting to PNL-EX2013.petenetlive.net.
New-PSSession : [pnl-ex2013.petenetlive.net] Processing data from remote server pnl-ex2013.petenetlive.net failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully.
Change the request including a valid shell handle and try again. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
Solution
Everything was working fine before I changed the certificates, and all the management runs out of IIS so I headed there first. I found when I checked the ‘bindings’ for the ‘Exchange Back End’ site that HTTPS did not have a certificate selected.
After I selected the correct certificate, the Command Shell opened fine.
Related Articles, References, Credits, or External Links
Seen (usually on a server) when trying to connect to either Outlook Web App, or The Exchange Admin Center.
To use Microsoft Outlook Web App, browser settings must allow scripts to run. For information about how to allow scripts, consult the Help for your browser. If your browser doesn’t support scripts, you can download Microsoft Internet Explorer for access to Outlook Web App.
Solution
You have two options, the first is more sensible (and more secure) so that would be my preference.
Option 1
1. From Internet Explorer Options > Security > Trusted Sites > Add the URL of OWA or ECP > Close > Apply > OK.
Option 2
1. From Internet Explorer Options > Security > Internet > Custom Level > Allow Scriptlets > Enable > OK > Apply > OK.
Related Articles, References, Credits, or External Links
Got in the office to find a colleague was going to be on long term sick this morning, the boss asked, “Can we turn on his out of office?”. I could have simply changed the users password and logged into OWA and done it, but executing some PowerShell would be more elegant.
Note: You must be in one of the following groups to carry out this procedure, Organizational Management, Recipient Management, or Help Desk.
Note: Remember the dates need to be in ‘American date format’ or the command will fail.
Example
[box]
Set-MailboxAutoReplyConfiguration -Identity 'PeteL' -StartTime '08/12/2013 08:00' -AutoReplyState Enabled -EndTime '12/31/2013 23:59' -InternalMessage 'Pete is currently out of the office' -ExternalMessage 'Pete is currently out of the office, please contact the helpdesk for technical assistance' -ExternalAudience 'All'
[/box]
Related Articles, References, Credits, or External Links
