The other Exchange 2013 tips of the day posts can be found here:
Exchange 2013 Tip Of The Day – 1 To 25
Exchange 2013 Tip Of The Day – 26 To 50
Exchange 2013 Tip Of The Day – 51 To 75
To obtain the listing below, the following command was used:
$Int = 76;While ($Int -le 100){Get-Tip $Int; Write-Host; $Int+=1}
To get a list of all parameters available for a cmdlet, type:
(Get-… Read the rest “Exchange 2013 Tip Of The Day – 76 To 93”
Now that the Windows XP, Office 2003 and Exchange 2010 SP2 support expiration date has come and gone, the world is still turning, and we are not in a state of Armageddon! *
That said, focus now needs to be on Office 2010 as it is 6 months until support ends for Office 2010 SP1 on the 14th of October 2014. At that point all Office 2010 installations need to be on SP2. This is detailed in the note… Read the rest “Office 2010 SP2– Do You Need To Upgrade?”
DirSync in one of my O365 test labs started to complain that there were some issues with objects synching to Windows Azure Active Directory (WAAD). EventID 0 was logging into the application event log, and stated: “The Management Agent 'Active Directory Connector' reported errors on execution”.
This is a an Exchange 2010 SP3 RU 7 based hybrid solution. Exchange 2013 is not present. DirSync is … Read the rest “DirSync Error 87 – The parameter Is Incorrect”
The other Exchange 2013 tips of the day posts can be found here:
Exchange 2013 Tip Of The Day – 1 To 25
Exchange 2013 Tip Of The Day – 26 To 50
Exchange 2013 Tip of The Day – 76 To 93
To obtain the listing below, the following command was used:
$Int = 51;While ($Int -le 75){Get-Tip $Int; Write-Host; $Int+=1}
Want to know what permissions an Active D… Read the rest “Exchange 2013 Tip Of The Day – 51 To 75”
Time files and we are now at the end of the Exchange 2010 SP2 support lifecycle. And as previously discussed Windows XP and Office 2003 left extended support yesterday. It seems like only yesterday when Exchange 2010 SP2 was released in November 2011.
The support lifecycle marker is the Exchange 2010 Service Pack. Exchange 2010 Rollup Updates (RU), are not milestones in the support lifecycle. So… Read the rest “End Of Exchange 2010 SP2 Support”
MEC 2014 has now come and gone, and it's been both an exciting and tiring week! There was always so much going on that it was a constant battle to decide what to go and see next. But that is a great dilemma to face. I will be spending a lot of time in the coming weeks looking at the recordings on the IamMEC.com site. Jon Orton just commented that the content will be release in the coming weeks… Read the rest “MEC 2014 – The Aftermath”
The other Exchange 2013 tips of the day posts can be found here:
Exchange 2013 Tip Of The Day – 1 To 25
Exchange 2013 Tip Of The Day – 51 To 75
Exchange 2013 Tip of The Day – 76 To 93
To obtain the listing below, the following command was used:
$Int = 26;While ($Int -le 50){Get-Tip $Int; Write-Host; $Int+=1}
Forget a property name? Not a problem because you can use wildcard charact… Read the rest “Exchange 2013 Tip Of The Day – 26 To 50”
The Exchange Management Shell helps us discover the amazing capabilities of PowerShell. One way it does this is by displaying a tip of the day so that we are introduced to concepts and topics that inevitably will come in handy one day!
The other Exchange 2013 tips of the day posts can be found here:
Exchange 2013 Tip Of The Day – 26 To 50
Exchange 2013 Tip Of The Day – 51 To 75
Exchange 2013 Tip of T… Read the rest “Exchange 2013 Tip Of The Day – 1 To 25”
When doing some recent customer work for Exchange 2013, I ran into an annoying issue in one of my labs. Outlook 2013 refused to connect to Exchange 2013. A witch hunt then ensued to ensure that all of my Outlook Anywhere, Autodiscover and authentication settings were correct. Well it turns out that they were, and this was just a client side issue. Legacy IIS permissions when coexisting with E… Read the rest “Outlook Unable To Connect To Exchange –Default Gateway Not Found”
When writing Exchange PowerShell scripts it is very useful to target specific machines to either query or set their properties. Thus the ability to generate a query that effectively targets the correct machines is a very good thing to have!
The reason I'm posting this is that I see a lot of people manually specify a list of servers, and then iterate through the list which typically looks like this:… Read the rest “Exchange PowerShell Filtering Examples”