Output looks as ,

The Script :

 $memGrpCnt=0 

$grplst=get-distributiongroup -ResultSize unlimited   

$grplst | foreach-object {     

$curgrpmplt++  

$curgrp=$_    

$grplstls=$curgrp.alias 

$dn= $curgrp.displayname 

write-progress -activity "Checking the DL to calculate " -status "Currently processing the DL(alias) :     $grplstls" -percentcomplete (($curgrpmplt/$grplst.count)*100)   $memGrpCnt=@(get-distributiongroupmember $curgrp.alias | where{$_.recipienttype -eq "MailUniversalDistributionGroup"}).count   

if ($memGrpCnt -gt 0)  { 

write-host $dn,$memGrpCnt  "$dn,$memGrpCnt" | out-file -filepath C:\test\DLwithGrp.txt -append  $memGrpCnt=0 

} 

else  {  $memGrpCnt=0  } 

} 

Take Away:

- There are many ways to send welcome emails in Exchange 2010/2013.

- Using Cmdlet Extension is one of the ways to send welcome email.

- The blog explains how to setup Welcome email thru Cmdlet Extension.

Let’s understand how to configure Exchange Server to send welcome email:

What is Cmdlet Extension Agents?

Cmdlet extension agents are components in Microsoft Exchange Server 2013/Exchange Server 2010 invoked by Exchange 2013/2010 cmdlets when the cmdlets run. Every time an Exchange cmdlet is run, the cmdlet calls the Scripting Agent cmdlet extension agent. When this agent is called, the cmdlet checks whether any scripts are configured to be called by the cmdlet. If a script should be run for a cmdlet, the cmdlet tries to call any APIs defined in the script. Cmdlet extension agents are available on any server role.

For more information on this please refer the link : https://technet.microsoft.com/en-us/library/dd335054.aspx

Implementation:

As you got an idea on the Cmdlet Extension Agent, I will go ahead and explain how we can use the feature to generate welcome email for the new mailboxes that we create.

When we create new mailbox in Exchange 2010/2013,  new-mailbox command is used (whether it is Exchange Management Shell or Exchange Management Console). You can enhance the behavior of the command by using Cmdlet Extension. It is like triggering a script whenever new-mailbox command is used.

In order to use the feature, we need to,

-          Deploy XML file on all the exchange servers.

-          Enable “Scripting Agent”.

How to deploy XML files?

On all the exchange servers, the exchange setup copies the file "ScriptingAgentConfig.xml.sample" to <installation path>\Bin\CmdletExtensionAgents\.  The file is a kind of sample/template. We can modify the file to meet our requirement or we can make our own XML file. I have detailed the steps to modify the sample file to send welcome email.

Note: The sample XML contains other feature blocks. If you are appending the below steps as it is without making changes to other feature blocks, you may receive unexpected warning while create new mailbox. If you are not using cmdlet-extension sample file for any other purpose/tasks, I would suggest you keep only the Welcome Email Feature block as it is in XML file provided in the attached zip file.
 

Step #1:

Create a welcome email template in html format that will be sent as welcome email or use the exiting template attached to the blog to suit your requirement. Easiest way to create welcome email template would be, open new message in Outlook, compose the email and save it as HTML.

Step #2:

Make a copy of the existing XML file and rename it to ScriptingAgentConfig.xml. Keep the file in <installation path>\Bin\CmdletExtensionAgents\.

Step #3:

Copy and paste the below script into appropriate location inside the XML file and Save it. It can be inserted between </feature> ….  <Feature Name ….> or at the beginning of the XML file (after <Configuration Version=”1.0”>).

# Script to send new email starts here

<Feature Name="Welcome Email" Cmdlets="New-Mailbox,Enable-Mailbox">

  <ApiCall Name="OnComplete">

   if($succeeded)    {

                if ($provisioningHandler.TaskName -eq "New-Mailbox") {

# Replace place holder.

                $USRdname=$provisioningHandler.UserSpecifiedParameters["Name"]

                $tempmsg= [string] (get-content ("c:\welcome\WelcomeMSG.htm"))

                $tempmsg = $tempmsg -replace "NewUser00",$USRdname

                # Picking Primary SMTP address,saving to $pSMTP to send email.

                $Ualias=$provisioningHandler.UserSpecifiedParameters["Alias"]

                $pSMTP = (get-mailbox $Ualias | select-object PrimarySMTPAddress | Format-Wide | Out-String ).trim()

}              

elseif ($provisioningHandler.TaskName -eq "Enable-Mailbox") {               

# Picking Primary SMTP address,saving to $pSMTP to send email.

                $eUalias=$provisioningHandler.UserSpecifiedParameters["Alias"]

                $dName = (get-mailbox $eUalias | select-object Name | Format-Wide | Out-String ).trim()        

                $pSMTP = (get-mailbox $eUalias | select-object PrimarySMTPAddress | Format-Wide | Out-String ).trim()

                # Replace place holder.

                $tempmsg= [string] (get-content ("c:\welcome\WelcomeMSG.htm"))

                $tempmsg = $tempmsg -replace "NewUser00",$dName

}

                # Please give the correct HUB serve IP address in the following line.

                $HUBServer="20.1.1.2"

                $EMail =new-object net.mail.mailmessage

                $HUBTask = new-object net.mail.smtpclient($HUBServer)

                # Email with attachment will be sent from the address given in the following line.

                $EMail.From="administrator@exchange2010.com"

                # Email with attachment will be sent TO the address given in the following line.

                $EMail.To.add($pSMTP)

                # Email Subject and Body details are specified in following lines

                $EMail.Subject="Welcome to Contoso IT !!!"

                $EMail.Body= $tempmsg

                $Email.IsBodyHtml = $true

                $HUBTask.send($EMail)

   }

  </ApiCall>

</Feature>

# Script to send new email ends here

Step #4:

Make the necessary changes in the script to suite your environment.

**** Give the path of the template file you created in Step #1. ****

$tempmsg= [string] (get-content ("c:\welcome\WelcomeMSG.htm"))

**** Give your HUB server IP address and Make sure that the HUB server accept connection ****

$HUBServer="10.1.1.2"

**** Give email address from which you want to send welcome message ****

$WelcomeEMail.From=administrator@e2k10.com

**** Change the subject of the welcome message, if you wish ****

$WelcomeEMail.Subject="Welcome to Contoso IT !!!"

What the script does?

When a new mailbox is created either with new-mailbox or enable-mailbox, on its successful completion, the script will be called. The script works along with email template available in "c:\welcome\WelcomeMSG.htm". It can be modified to meet your requirement.

To start with,

It checks whether new-mailbox or enable-mailbox command is used. If new-mailbox is used, Name parameter value will be stored in variable $USRDname.In addition, we also store the primaySMTPAddress to the variable $pSMTP. When enable-mailbox is used, Alias value will be stored in $eUalias instead of Name. As we need to send email, we use get-mailbox command to retrieve name,primarySMTPAddress and store those in $dName,$pSMTP variables.

Then it reads the content of template "c:\welcome\WelcomeMSG.htm" and stores in the variable $tempmsg. As the template is set with place holder "NewUser00", the script uses “-replace” to update the place holder “NewUser00” with the display name.

Later we create new message object and SMTP client object to send out email. Before we send the email, we compose the email with From address, To address, Subject and Body.

Welcome Email Template with Place Holder:

I have created template as shown in the Picture #1. The template is with place holder “NewUser00”. This will be replaced with display name when the email is sent (as shown in Picture #2).

Picture 1

Welcome Email after place holder replacement:

Picture 2

How to manage/enable Cmdlet Extension Agent?

After the XML file updated with script, you need to enable the agent to call the XML file and the script whenever new-mailbox used. You can view the agent status by running the command: Get-CmdletExtensionAgent | FT Name,Enabled

By default,“Scripting Agent” is disabled. You can enable it using the command,

Enable-CmdletExtensionAgent "Scripting Agent"

When you wanted to disable the “Scripting Agent” , run the command ,

Disable-CmdletExtensionAgent "Scripting Agent"

Enabling or disabling CmdletExtension does not require restart of the server or exchange services in a normal scenario. It is a global command and applicable to all the exchange servers in the organization. So you have to update the XML file on all the exchange servers. If the XML files is not updated on any of the exchange server and you run any non-Get cmdlets, the cmdlet will fail.

 For More Information on managing Cmdlet Extension, please refer the link : https://technet.microsoft.com/en-us/library/dd298143.aspx

Test:

As both script and agent are in place, you can create new mailbox using EMC or EMS and check how it works. You may notice that the mailbox creation is taking little bit longer than it used to. That’s because the additional activities are done along with new-mailbox.

Related articles :

https://technet.microsoft.com/en-in/library/dd297951(v=exchg.141).aspx

https://technet.microsoft.com/en-in/library/dd335067(v=exchg.141).aspx

https://technet.microsoft.com/en-us/library/dd298143(v=exchg.141).aspx

WelcomeMSG.zip

               This version of flow-chart is additional resource to the DAG Datacenter Switchover GWT (https://support.microsoft.com/common/survey.aspx?scid=sw;en;3510&showpage=1). This was done intentionally. So the flow-chart will enhance the DAG Datacenter Switchover knowledge with less effort.

Features:

>> It is a detailed Secondary/DR Site DAG switchover flow-chart.

>> The flow-chart helps to get better logical understanding of the switch-over process.

>> Knowledge gained from DAG Datacenter Switchover GWT enhanced thru flow-chart as you can visualize whole activity in a sequential flow.

>> Easy navigation between pages.

The Flow-Chart Availability:

You can download the Exchange 2010 DAG Datacenter Switchover Flow-Chart from https://gallery.technet.microsoft.com/Exchange-2010-DAG-b95d1e48

Feedback/Suggestion:

We welcome your suggestion and feedback.

Disclaimer:

The EASAdmin Tool facilitates to manage Exchange ActiveSync Device on Office365 and Exchange On-Premises. This tool is provided "as is" without warranty of any kind. Microsoft and Tool Developer, Tool Supplier further disclaim all implied warranties including but not limited to any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the samples remains with you. In no event shall Microsoft or the Tool Developer, Suppliers be liable for any damages whatsoever (including but not limited to damages for loss of business profits,business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the tool, even if Microsoft, the Tool Developer, Suppliers have advised of the possibility of such damages.

** EASAdmin Version 1.0.0.2 is updated with multi-domain feature. The feature will fetch the users, devices from across domains in a forest. 

Introduction:

The Exchange ActiveSync Admin (EASAdmin) tool enables administrators to manage the process of remotely erasing lost, stolen, or otherwise compromised mobile devices. The EASAdmin Tool is designed for use with Exchange Server 2010, Exchange 2013, Office 365 (Wave14 and 15).

By using the EASAdmin tool, administrators can perform the following actions on Office 365 and Exchange On-Premise:

• View a list of all devices that are being used by any enterprise user.
• Find Inactive Devices.
• Get No. of devices per user.
• Block/Allow devices.
• Select/De-select devices to be remotely erased.
• View the status of pending remote erase requests for each device.
• Remove Mobile Devices.
• Enable,Disable ActiveSync/MAPI/EWS/OWA Exchange features during troubleshooting.
• Clear Blocked/Allowed Devices.
• Execute Get-CASMailbox, Get-Mailbox,Get-ActiveSyncDeviceStatistics,Get-MailboxFolderStatistics,Get-ActiveSyncDeviceClass,Get-ActiveSyncDeviceAccessRule,Get-ActiveSyncOrganizationSettings,Get-ActiveSyncMailboxPolicy.
• Parse IIS log and get reports to troubleshoot ActiveSync related Issue and manage the device/user from report output.

Pre-Requisite:

The tool is written using C# Visual Studio 2012, PowerShell 3.0, Log Parser 2.2, .Net Framework 4.0. It is tested with Exchange 2010,Exchange 2013 and Office 365 (Wave 14 & 15) and run from Windows 7, Windows 8, Windows 2008 R2 and Windows 2012.

System Requirement:

• .Net Framework 4. (https://www.microsoft.com/en-in/download/details.aspx?id=17718 )
• PowerShell 2.0 or Later. (https://support.microsoft.com/kb/968929 )
• Log Parser 2.2 (https://www.microsoft.com/en-in/download/details.aspx?id=24659 )
• The tool screen layout works best with resolution 1920 x 1080.
• Verify that Windows PowerShell can run scripts:

1. Click      Start > All Programs > Accessories > Windows PowerShell.
2. Do one of the following to open Windows PowerShell:
• If you're running Windows Vista,Windows 7, or Windows Server 2008 R2, right-click Windows PowerShell and select Run as administrator. If you get a user account control prompt that asks if you would like to continue, respond Continue.
• If you're running Windows XP or Windows Server 2003, click Windows PowerShell.
3. Run the following command:Get-ExecutionPolicy
4. If the value returned is anything other than RemoteSigned, you need to change the value to RemoteSigned.
   
        Note   When you set the script execution policy to RemoteSigned, you can  only run scripts that you create on your computer or scripts that are signed by a trusted source.

Enable scripts to run in Windows PowerShell

In Windows PowerShell session you just opened as an administrator, run the following command:

Set-ExecutionPolicy RemoteSigned

• As the tool does not store any user data on the disk, physical RAM requirement various based on the data retrieval from server. The tool minimum requires 500 MB of RAM.

How Tool Works:

As an Office 365/Exchange Administrator, if you want to perform any activity on ActiveSync that are in the cloud, you will use Remote PowerShell or Online Portal. Both connect to the remote server over the Internet.

Similarly, the EASAdmin tool requires Internet connection to connect to Office 365 servers.The tool has to connect to Remote Powershell to perform the tasks. The tool performs various SET & GET tasks. It is expected that the machine that runs the tool installed with pre-requisites for the commands to function. So please refer the pre-requisite section in the documentation before using the tool.

If you are using On-Prem option in the tool, the authentication method will be Kerberos and it will be HTTP communication. If there is any Kerberos unsupported device between tool and server, authentication may fail.

Note: I have titled the fields/options as per Microsoft Exchange Terminology used with Exchange Shell for the easier understanding.

Important: There are options in the tool that can wipe entire data on devices. Please know the options before you execute it.

How to Use the Tool:

It is a stand-alone tool and is multi-instance capable. The tool cannot be run in DOS/Command Prompt as it is GUI based.When you double-click the tool short-cut or the application file, the tool presents you
with log on screen. If you wish to work with Office 365, give sign-in address and password to connect to Office 365 server. Instead you prefer to work with Exchange On-Premise server, you have to provide FQDN of
Exchange 2010/2013 CAS server.

After successful logon, Disclaimer/About page displayed. By Default, All the option are disabled until you click “I Agree” button.

ActiveSync Device List:

The tab lists all the device details. You can retrieve the data from the server, then work with it. More the data you ask, more the time it takes.

The data retrieval from the server can be restricted with,

Important: Clear/Wipe Mobile Device option will clear all the data on the device. Please use it with caution. The tool restricts to send remote wipe request to only three devices at a time to reduce the damage, if the option executed accidently.

IIS Log Parser for ActiveSync:

The option can be used only if IIS log is available.So it will be used primarily with Exchange On-Premise. The result can be further used to disable ActiveSync or view the properties of users.

Exchange Feature:

Exchange Feature executes Get-CASMailbox and retrieve the data from server based the condition you choose.You can enable/disable Exchange Feature and execute Get-CASMailbox,Get-Mailbox,Get-ActiveSyncDeviceStatistics, Get-MailboxFolderStatistics.

Device Block Clear, Device Allow Clear: When you run Get-CASMailbox command for any user, it will list the devices blocked and allowed for users. At times, you want to set this value to $Null. The command
will do the same.

The data retrieval from the server can be restricted with,

General ActiveSync Output:

As name suggests, you can generate multiple ActiveSync related reports. The command output is displayed in the text box. It does not append the current output to the previous command output. It is done intentionally.

Known Issues:

If you leave the Remote PowerShell session running for a long time (may be over 6 hours) without using the tool, then you try to use the PS related option, if you may get unexpected behavior due to session time out.

Troubleshooting:

Issue #1:

PowerShell Session to the server will expire if the tool is not actively used. If you create the session and do not use the tool for a long time, then try to use it after session expiry, you will see the below error. You have to reopen the tool and create new PowerShell Session thru Authentication Tab.

Troubleshooting: Restart the tool to create new session and check.

Issue #2:

If you are not able to create Remote PowerShell Session to the server. Please check whether you are able to connect to Remote PowerShell manually following the method detail in the article : https://help.outlook.com/en-us/140/cc952755.aspx

If you receive error like,

Please set the proper proxy server.

Troubleshooting: Run the command: netsh winhttp show proxy and check what the proxy server is set. If you are using proxy, but the output of the command shown as below, set the correct proxy server.

To set the proxy server, run the command : netsh winhttp set proxy <Proxy Server Name:Port>

If you are not able to connect to PowerShell by following the method in the link : https://help.outlook.com/en-us/140/cc952755.aspx, the PS related options in the tool will not work.

Issue #3:

At times, all looks good but the session may not be established due to server connection rejection or intermittent issues or transient failure.

Troubleshooting: Close the tool and try to create the session after a couple of minutes.

Issue #4:

No Error reported when you Fetch Data and also it completes the task in no time. The issue could be due to PowerShell Script Execution restriction.Run Get-ExecutionPolicy from Windows PowerShell and check the policy. The tool requires execution policy set to RemoteSigned or Unrestricted,else the behavior is expected.

Support/Feedback:

If you have any questions or feedback, you can contact me at: sukum@microsoft.com / raghuv@microsoft.com

Download :

***

The sample script to send birthday greetings. A separate email will be sent to individual users who will be celebrating birthday on the day the script runs. The script can be used with windows Task Scheduler to automate the process with a minimum modification. 

Features:

-     The script includes the function to help the users to run the friendly command: Send-DOBGreetings.

-     It can be used with Server,Database,FrmEmailID,HUBServer parameters.

-     FrmEmailID,HUBServer are mandatory.

-     Database and Server parameters are optional.

-     If the Server/Database is not used, it will run against all the mailboxes.

-     You cannot use Server and Database parameters together.

-     FrmEmailID will be used to send BirthDay Greeting Email to the users.

-     You cannot use administrator email ID or credential to send email. When you use  other user's email id to send message, You should have at least "Send As" permission.

-    You will be prompted with credential once to send emails. Only after successful authentication, the email will be sent.

-    Script does not make any modification, apart from running Get-Mailbox  commands.

-    Script can be used with Exchange 2007/2010/2013 and Office 365.

 Sample Screen-Shot:

- You may download the script from TechNet Gallery

The script to get list of inactive mailboxes. Inactive is very relative term. For Example, some organizations mark the mailbox as inactive, if it is not accessed for a long time. Other organizations mark the mailbox as inactive, if the user did not sent email for a long period. If you ask me, why they should go by sent item. Some of the reasons could be, the mailboxes are scanned by AV/management tool that changes logon date. So they cannot go by access date. The script identify the inactive mailboxes based on Sent Items.

Features:

-       The script includes the function to help the users to run the friendly command: Get-InActiveMailbox.

-       It can be used with Server,IdleDays,FilePath,Database,EmailID,HUBServer parameters.

-       IdleDays Parameter is mandatory and with the range 1 – 5000.

-       FilePath,Database,EmailID,HUBServer and Server parameters are optional.

-       If the FilePath is not given, the output will be stored in current folder. If the Server is not used, it will run against all the mailboxes.

-       You cannot use Server and Database parameters together.

-       If you wish to have the output file sent thru email. You can use EmailID parameter. The EmailID should be used with HUBServer parameter.

-       You cannot use administrator email ID or credential to send email. When you use other user's email id to send message, You should have at least "Send As" permission.

-       If the email option used, you will be prompted with credential. Only after successful authentication, the email will be sent.

-       Script does not make any modification, apart from running Get-Mailbox and Get-MailboxFolderStatistics commands.

-       The output will be stored to the file with the name < IdleDays > DayInactiveMailbox.csv.

You can download the script from ,

https://gallery.technet.microsoft.com/scriptcenter/List-Inactive-Mailboxes-on-1ac82ddf

Sample Screen-Shots:

Note : The output may include system mailboxes. If you wish to process further with output, make sure you do not distrub/disable/delete system mailboxes.Refer https://technet.microsoft.com/en-us/library/gg588318(v=exchg.141).aspx for more details.

I will start by listing how DS Access/AD Access identifies the topology by using the following steps for the benefit of Exchange administrators:

1. The system attendant process, mad.exe, instantiates and initializes DSAccess.dll during startup.
2. From the local domain, DSAccess opens an LDAP connection to a randomly chosen Domain Controller (DC). This DC is referred to as the bootstrap server.
3. DSAccess reads the local registry to determine if the topology is hard coded. If the topology is hard coded, the discovery process stops. If no hard coding is detected, DSAccess continues the discovery process.
4. DSAccess queries the bootstrap server to identify local DCs and Global Catalog servers (GCs). DSAccess then determines server suitability and assigns server roles.
5. DSAccess queries the bootstrap server to determine if one or more secondary sites are connected to the local site. If secondary sites exist, DSAccess sorts the siteLink objects for each site from lowest cost to highest cost. DSAccess places the lowest cost sites in a secondary topology list.
6. DSAccess queries the bootstrap server to identify the DCs and GCs that are located in the secondary topology sites.
7. DSAccess identifies the full topology and compiles a list of working domain controllers and a list of working GCs.

There are situations when Exchange DS Access/AD Access does not show the GCs from other AD Sites in Event ID 2080. As an Exchange administrator, you may be wondering why the event 2080 does not list all GCs in the domain even though the GCs are healthy. To save you a lot of production downtime and effort, I will discuss the following aspects.

Exchange DS Access/AD Access uses AD Site Link details while listing GCs in Out-Of-Site in Event ID 2080. If there is no direct site link between AD site where Exchange exists and other AD sites, the AD sites' GCs will not be considered to be listed in Event ID 2080.

I thought that giving an explanation on AD site link criteria used by DS Access/AD Access will help you to manage the GC resource efficiently for better Exchange functionality.

Since a picture is worth a thousand words, I will explain the topic in question using examples and diagrams.

Let’s say we have the following lab setup:

• Four AD sites named Site A, Site B, Site C, and Site D
• All sites belong to a domain – CONTOSO.COM
• Each site has two GCs
• The Site A is installed with Exchange server
• There are direct AD Site links between Site A and Site B, Site A and Site C, Site A and Site D

Picture 1

Scenario 1:

The Site A, the Exchange site, has direct AD site link with other AD sites. All site links have the same site Link Cost i.e. 100. So, the Event ID 2080 on Exchange will appear like in the following snapshot, Picture 1A:

Picture 1A

Scenario 2:

If I change my AD site Link Cost as shown in Picture 2, then Exchange will pick the GCs from the Site with lowest cost to list under Out-Of-Site in Event ID 2080 and will ignore other AD Site GCs.

Picture 2:

Exchange will consider only the Site Link with lowest cost for the Out-Of-Site GCs. So, the Event ID 2080 will look like Picture 2A.

Picture 2A

Other GCs in Site B and Site C will not be listed in Event ID 2080. Therefore, Exchange will not use the other GCs i.e. GC5, GC6, GC7 and GC8 in sites B and C.

Scenario 3:

If I change my AD site Link as shown in Picture 3 then Exchange will pick the GCs from the Site C to list under Out-Of-Site in Event ID 2080, and it will ignore other AD Site GCs i.e. GC3, GC4, GC7 and GC8.

Picture 3

Picture 3A

Scenario 4:

This scenario may be a little odd and may not usually happen as there is no AD with multiple AD sites but no site link. Still, I wanted to talk about this scenario so that the logic can be clearly understood. If there are no site links for any site as in Picture 4, sites are not considered. It will only use local site DC/GC.

Picture 4

Picture 4A

Now that you’ve gone over various scenarios, you may ask, what if I hardcode the GCs that are:

• In-Site but do not have a direct site link with Site A, the Exchange Site, or
• there is no site link with Site A, the Exchange site,

Will exchange use the GCs?

The answer is yes. It will use GCs, because if you hard code the directory servers, DSAccess bypasses the discovery process and checks only for server suitability. Similarly when you set StaticExcludedDomainControllers, the excluded DC will be listed in 2080 event, but  scores for the DC in the event will be set to 0 for all except GC Capable.

Let‘s say, I run the following command, the exchange will get updated and will log the Event ID 2080 as in Picture 5:

Get-ExchangeServer MSX | Set-Exchangeserver –identity MSX – StaticDomainControllers GC3.CONTOSO.COM, GC5.CONTOSO.COM, GC7.CONTOSO.COM – StaticGlobalCatalogs GC3.CONTOSO.COM, GC5.CONTOSO.COM, GC7.CONTOSO.COM – StaticConfigDomainController GC3.CONTOSO.COM

Picture 5

In conclusion, you can ensure service continuity and minimize service downtime by setting a proper AD site link.

Applies to

Microsoft Exchange Server 2010

Microsoft Exchange Server 2007

Microsoft Exchange Server 2003

• During the course of Office 365 Exchange related troubleshooting, You need to generate various PowerShell command to collect various data.
• At times, You may feel using Powershell is not very comfortable to collect the data.
• I had heard from friends that if they have a tool to perform their day to day activities in managing the mailboxes rather using remote PowerShell, it will be very useful.
• Also when I was checking various Microsoft Developers forums, I could see a huge demand for a sample tool to help the Office 365 tool developers.
• In Order to help, Office 365 Exchange Administrators, Office 365 Tool Developers,   The O365 Delegates tool developed.

The tool can be used to:

• Allow others to manage your mailbox and calendar by giving delegate permission.
• Find existing distribution list members.
• List delegate permission.
• Remove delegate permission.
• Modify delegate permission level.
• Grant & Revoke “Full Mailbox” and “Send As” Permission.
• Run various Office 365 PowerShell commands to retrieve user/mailbox details.
• It is provisioned to get LDP dump of the on-premise user through PowerShell.

• Customizable PowerShell commands to generate various advance reports .
• Run the command for multiple users.
• Perform various Set commands to manage O365 mailboxes and the list goes on.