Exchange Server 2013 SP1 Prerequisites (Exchange2013SP1Prerequisites_v1.0)

This script automate execute steps for installing the necessary Windows Server 2012 R2 and Windows Server 2012 operating system prerequisites for the Microsoft Exchange 2013 Mailbox, Client Access, Multirole and Edge Transport server roles. The prerequisites that are needed to install Exchange 2013 on a Windows Server 2012 R2 or Windows Server 2012 computer depends on which Exchange roles you want to install.

What do you need to know before you begin?

o The Edge Transport server role is available starting with Exchange 2013 SP1.

o Make sure that the functional level of your forest is at least Windows Server 2003, and that the schema master is running Windows Server 2003 with Service Pack 2 or later.

o The full installation option of Windows Server 2012 R2 and Windows Server 2012 must be used for all servers running Exchange 2013 server roles or management tools.

o You must first join the computer to the appropriate internal Active Directory forest and domain.

o You must check and be sure your server has access to the internet

o Some prerequisites require you to reboot the server to complete installation.

Let’s have a quick look how to execute the script Exchange2013SP1Prerequisites_v1.0 on Windows PowerShell and what this script do for us.

1. Login to Windows Server 2012 R2 and Windows Server 2012 with Enterprise Administrator credentials

2. Start Windows PowerShell “As Administrator”

3. Next step, copy the script Exchange2013SP1Prerequisites_v1.0 on (C:\) drive

4. Let’s start with running scripts from within Windows PowerShell itself.
In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted

Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.

Windows PowerShell has four different execution policies:

o Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.

o AllSigned – Only scripts signed by a trusted publisher can be run.

o RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.

o Unrestricted – No restrictions; all Windows PowerShell scripts can be run.

5. The most common (default) way to run a script is by calling it:

PS C:\> & “C:\Admin\My first Script.ps1”

If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator

PS C:\> C:\Admin\Myscript.ps1

If the script is in the current directory, you must indicate this using .\ (or ./ will also work)

PS C:\> .\Myscript.ps1

In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter

6. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 3 (E2013 Multirole installation) and click Enter

7. As you can easy check bellow, my Multirole Prerequisites are in progress to be download and install

8.  After the Prerequisites successfully installed, we have to choose the option 10 in order to restart our server

9. After restart your server, login as EA and proceed to install your Microsoft Exchange Server 2013 SP1

You can download the script here

Enjoy…..

This script automate execute steps for connecting to Office 365.
By choosing only a number, you can manage your Office 365 connection or disconnect

What do you need to know before you begin?

• Make sure you have already installed Windows Azure AD PowerShell
• You must check and be sure your server or your computer has access to the internet

Let’s have a quick look how to execute the script Connect_to_EXO_v1.0 on Windows PowerShell and what this script do for us.

1. Login to your computer with Administrator credentials
2. Start Windows Azure AD PowerShell “As Administrator”

3. Next step, copy the script Connect_to_EXO_v1.0 on (C:\) drive

4. Let’s start by running the script from Windows Azure AD PowerShell itself.
In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted

Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.

Windows PowerShell has four different execution policies:

• Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
• AllSigned – Only scripts signed by a trusted publisher can be run.
• RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
• Unrestricted – No restrictions; all Windows PowerShell scripts can be run.

5. The most common (default) way to run a script is by calling it:

PS C:\> & “C:\Admin\My first Script.ps1”

If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator

PS C:\> C:\Admin\Myscript.ps1

If the script is in the current directory, you must indicate this using .\ (or ./ will also work)

PS C:\> .\Myscript.ps1

In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter

6. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 1 (Connect to Exchange Online) and click Enter

7. Type your credentials (Username and Password) and let the script do the rest for you…

You can download the script, from here Microsoft TechNet Gallery

Enjoy…..

This script Set-VirtualDirectory.ps1 automate configure all Exchange 2013 virtual directories:

o OWA

o ECP

o OAB

o ActiveSync

o Web Services

o AutoDiscover

o Outlook Anywhere

You just type the External Url and Internal Url you want to set, and automatically Url’s are set

Let’s have a quick look how to execute the script Set-VirtualDirectory.ps1 on Windows PowerShell and what this script do for us.

1. Login to Windows Server with Enterprise Administrator credentials

2. Start Windows PowerShell “As Administrator”

3. Next step, copy the script Get-ActiveMailboxList.ps1 on (C:\) drive

4. Let’s start with running scripts from within Windows PowerShell itself.
In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Exchange PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
Navigate back to Exchange PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted

Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.

Windows PowerShell has four different execution policies:

o Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.

o AllSigned – Only scripts signed by a trusted publisher can be run.

o RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.

o Unrestricted – No restrictions; all Windows PowerShell scripts can be run.

5. The most common (default) way to run a script is by calling it:

PS C:\> & “C:\Admin\My first Script.ps1”

If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator

PS C:\> C:\Admin\Myscript.ps1

If the script is in the current directory, you must indicate this using .\ (or ./ will also work)

PS C:\> .\Myscript.ps1

In our case scenario we run the script in the current directory “C:\” so, we must indicate this using & ‘.\’ and we click Enter

If you’re running some command and the command path has spaces in it, then you need the command invocation operator ‘&’ (see help about_operators, look for “call operator”).

The call operator (&) allows you to execute a command, script or function.

Many times you can execute a command by just typing its name, but if the command (or the path) contains a space then this will fail.

Putting the command in quotes would make PowerShell treat it as a string, so in addition to quotes, use the call operator to force PowerShell to treat the string as a command to be executed.

Syntax
& “[path] command” [arguments]

6. Our script now it starts running, automatically on C:\ drive

7. You have to “Set” type the External and Internal Url you want to use

As you can see now, the Name Spaces are set with the External and Internal Url you set

You can download it here

Today, I manage to complete the bellow script, in order some basic Office 365 Administrator Task Daily & Weekly to be automate with one click

This script automate execute steps for Office 365 Administrator Daily & Weekly Tasks.
By choosing only a number, you can manage your Office 365 Daily & Weekly Tasks
You can download the Script here.

 

What do you need to know before you begin?

• Make sure you have already installed Windows Azure AD PowerShell
• You must check and be sure your server or your computer has access to the internet

Let’s have a quick look how to execute the script O365_DailyAdminTasks_v1.0 on Windows PowerShell and what this script do for us.

• 1. Login to your computer with Administrator credentials
• 2. Start Windows Azure AD PowerShell “As Administrator”

  

• 3. Next step, copy the script O365_DailyAdminTasks_v1.0 on (C:\) drive

  

• 4. Let’s start by running the script from Windows Azure AD PowerShell itself.
  In case you get weird error messages when you try to run a script, the reason is only one, security settings built into Windows PowerShell include something called the “execution policy” the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted that means that scripts – including those you write yourself – won’t run.
  Navigate back to Windows PowerShell and set the Execution policy to unrestricted in order to be able to run the script, in that case, use this command to set your execution policy to RemoteSigned or Unrestricted

  

  Note: The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer.

  Windows PowerShell has four different execution policies:

  • Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
  • AllSigned – Only scripts signed by a trusted publisher can be run.
  • RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
  • Unrestricted – No restrictions; all Windows PowerShell scripts can be run.
• 5. The most common (default) way to run a script is by calling it:

  PS C:\> & “C:\Admin\My first Script.ps1”

  If the path does not contain any spaces, then you can omit the quotes and the ‘&’ operator

  PS C:\> C:\Admin\Myscript.ps1

  If the script is in the current directory, you must indicate this using .\ (or ./ will also work)

  PS C:\> .\Myscript.ps1

  In our case scenario we run the script in the current directory “C:\” so, we must indicate this using .\ and we click Enter

  

• 6. Type your Global Admin credentials, Username and Password in order to login

  

• 7. Our script now it starts running, select an option from the menu. In my case scenario, I will select option 4 (Change User/s Password) and click Enter

  The 4th choice Change User’s Password, let’s see together how we can change user or users password with one click

  

• 8. When you press Enter, automatically its appear a window with all the users in Office 365.
  Just choose the user or the users by clicking on the user and click OK

  

• 9. Password change and automatically a new pass is generate

  

• 10. Next step, you can choose another option without to need to type again your Office 365 credentials

The Code:
#######################################################################################################

<#
   DESCRIPTION                                                                                                              
   *************                                                                                                                
    This script automate execute steps for Office 365 Administrator daily tasks
                                                                                                                           
   SYNOPSIS                                                                                                                 
   ***********                                                                                                                                                                                                                                           
   Daily:  Mailbox Administrators are constantly responding to any addition, change, and removal requests for their Office365 accounts. 
   According to the data that we analyzed from 365Command, the most common daily tasks are:
  
    Menu
   *******
   1. Create a new User in Office 365                  
   2. Remove a User or User’s from Office 365          
   3. Restore a User or User’s in Office 365            
   4. Change User or User’s Password in Office 365     
   5. Set User/User’s Password never Expires in Office 365
   6. Export License Statistics in Office 365             
   7. Export List for SMTP address & Last connection time 
   8. Export Recipient Statistics in Office 365           
   9. Export Mailbox Usage Report from Office 365         
  10. Export Connection By Client Type Report in Office 365                                                                 

Disclaimer
     Important Note Test it first on Lab environment                                           
     THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE                        
     RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER                     
#########################################################################
#       To run the script                                                                                                             #
#      *******************                                                                                                             #
#                                                                                                                                              #
# .\O365_DailyAdminTasks_v1.0.ps1                                                                                    # 
# Author: Joanna Vathis                                                                                                        #
# Blog1: https://catastrophicerrors.wordpress.com/                                                        #
# Blog2: http://autoexec.gr/blogs_autoexec_gr/b/cf/default.aspx?pi516=2                   #
# Version: 1.0                                                                                                                        #
# Last Modified Date: 31/03/2014                                                                                        #
# Last Modified By:  Joanna Vathis                                                                                        #                                                                                     
#########################################################################
#>

Function LoginOffice365 {
     # Connect to Office 365 and Exchange Online
      Clear;
      Import-Module Msonline
      $GA_UserName = Read-Host “Please enter your GA Username for Office 365 account”;
      $GA_Password = Read-Host “Please enter your GA Password for Office 365 account” -AsSecureString;
      Write-Host “Don’t press any key, wait until connect……” -ForegroundColor Yellow;
      $GA_Credentials = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $GA_UserName, $GA_Password;
      $Connect = Connect-MsolService -Credential $GA_Credentials;
      Start-Sleep -Seconds 10
      $Error = $Connect | ?{$_.gettype().Name -eq “ErrorRecord”}
             If($Error){
                        Write-Host ” $Connect” -ForegroundColor Red;   
                        Read-Host;
                       }
             Else{
      Write-Host ” Succesfully login in Office 365…” -ForegroundColor Green;
  }
  } # End LoginO365  

[string] $menu = @’
    ============================================================
       Office 365 Administrator Daily & Weekly Tasks Tool
    ============================================================
     
      1. Create a new User in Office 365                  
      2. Remove a User or User’s from Office 365          
      3. Restore a User or User’s in Office 365            
      4. Change User or User’s Password in Office 365     
      5. Set User/User’s Password never Expires in Office 365
      6. Export License Statistics in Office 365             
      7. Export List for SMTP address & Last connection time 
      8. Export Recipient Statistics in Office 365           
      9. Export Mailbox Usage Report from Office 365         
     10. Export Connection By Client Type Report in Office 365
 
     21. Exit                                   
    ============================================================
    Select an option from the menu…(1-21)
‘@ # Menu List

Function SmtpReport {
  Clear;
        Write-Host ” ==============================================” -ForegroundColor Cyan;
        Write-Host ”  List for SMTP address & Last connection time ” -ForegroundColor White;
        Write-Host ” ==============================================” -ForegroundColor Cyan;
        Write-Host ” ”   
  # List for SMTP address and Last connection time for all the users
    Get-Mailbox | fl EmailAddresses, identity | Export-Csv -Path ‘C:\Emailaddress.csv’ -NoTypeInformation
    Get-Mailbox -ResultSize unlimited | Get-MailboxStatistics | Select-Object identity,lastlogontime,lastlogofftime,DisplayName | Sort-Object DisplayName -Descending | Export-Csv -Path ‘C:\Lastlogontime.csv’ -NoTypeInformation
} # End SMTP Report

Function CreateUser {
  Clear;
        Write-Host ” =======================================” -ForegroundColor Cyan;
        Write-Host ”    Create a new User in Office 365     ” -ForegroundColor White;
        Write-Host ” =======================================” -ForegroundColor Cyan;
        Write-Host ” ”   
        $DisplayName = Read-Host “Display Name”;
        $FirstName = Read-Host “First Name”;
        $LastName = Read-Host “Last Name”;
        Write-Host “Type the username@yourdomain.onmicrosoft.com” -ForegroundColor Yellow;
        $UserName = Read-Host “User Name”;
        $UserPrincipalName = $UserName;
        #$Role = Read-Host “Assign Role”;
        $Department = Read-Host “Department”;
        $Location = Read-Host “Set user Location”;
        $PassWord = Read-Host “New Password”;
        $Proce = New-MsolUser -FirstName $FirstName -LastName $LastName -UserPrincipalName $UserPrincipalName -DisplayName $DisplayName -UsageLocation $Location -Password $PassWord -ForceChangePassword $false;
        $Error = $Proce | ?{$_.gettype().Name -eq “ErrorRecord”};
       
        If($Error){
             Write-Host $Error -BackgroundColor Black -ForegroundColor Red;
         }
         else{
        Set-MsolUser -UserPrincipalName $UserPrincipalName -UsageLocation $UsageLocation;
        Get-MsolUser | FT DisplayName,UsageLocation,Licenses,IsLicensed -AutoSize | Out-GridView;
        Get-MsolUser | FT DisplayName,UsageLocation,Licenses,IsLicensed -AutoSize | Export-Csv -Path C:\UserStatistics.csv -NoTypeInformation;
        Get-MsolAccountSku |FT AccountSkuId,ActiveUnits,ConsumedUnits;
        Write-Host “User was succesfully created…” -BackgroundColor DarkBlue -ForegroundColor White;
   
      # Proceed to Assign License for the User 
        $SkuPartNumber = Read-Host;
        $LicensesType = Read-Host;
             Write-Host ” ==============================================” -ForegroundColor Cyan;
             Write-Host ”    Office 365 Service Plans AccountSkuID      ” -ForegroundColor White;
             Write-Host ” ==============================================” -ForegroundColor Cyan;
             Write-Host ”                                               “
             Write-Host ”     1. Windows Azure AD Rights                “
             Write-Host ”     2. Office 365 ProPlus                     “
             Write-Host ”     3. Lync Online                            “
             Write-Host ”     4. Office Web Apps                        “
             Write-Host ”     5. SharePoint Online                      “
             Write-Host ”     6. Exchange Online                        “
             Write-Host ”     7. Yammer                                 ”             
             Write-Host “===============================================” -ForegroundColor Cyan;
             Write-Host  “Select a License type to assign…(1-7):”-ForegroundColor White;
            
             # 1. Windows Azure AD Rights
             If($LicensesType -eq “1”){
                  $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “RMS_S_ENTERPRISE”} $s.ServiceStatus;
             }
             # 2. Office 365 ProPlus
             elseif($LicensesType -eq “2”){
                     $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “OFFICESUBSCRIPTION”} $s.ServiceStatus;
             }
             # 3. Lync Online
             elseif($LicensesType -eq “3”){
                      $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “MCOSTANDARD”} $s.ServiceStatus;
             }
             # 4. Office Online
             elseif($LicensesType -eq “4”){
                      $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “SHAREPOINTWAC”} $s.ServiceStatus;
             }
             # 5. SharePoint Online   
             elseif($LicensesType -eq “5”){
                     $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “SHAREPOINTENTERPRISE”} $s.ServiceStatus;
             }
             # 6. Exchange Online
             elseif($LicensesType -eq “6”){
                     $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “EXCHANGE_S_ENTERISE”} $s.ServiceStatus;
             }
             # 7. Yammer
             elseif($LicensesType -eq “7”){
                     $ServicePlans = Get-MsolAccountSku | Where {$_.SkuPartNumber -eq “YAMMER_ENTERPRISE”} $s.ServiceStatus;                     
             }
             ForEach ($LicensesType in $ServicePlans){                       
                Set-MsolUserLicense -UserPrincipalName $UserPrincipalName -AddLicenses $LicenseType.AccountSkuId;
                  }
              
            Write-Host “License was succesfully assigned to the user…” -BackgroundColor DarkBlue -ForegroundColor White;
  }
  }# End CreateUser

Function LicenseStatistics {
    # Export License Statistics   
        Clear;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ”   Office 365 License Statistics    ” -ForegroundColor White;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ” ”   
        $a = Get-MsolAccountSku
        $all = $a.ActiveUnits
        $consumed = $a.ConsumedUnits
        $left = $all – $consumed
       
        # Get Report for All Licensed users in Office 365
          Get-MsolUser -All | Where-Object { $_.isLicensed -eq “True” } | Select-Object UserPrincipalName, DisplayName, Country, Department | Export-Csv C:\LicensedUsers.csv -NoTypeInformation;
          Get-MsolUser -All | Where-Object { $_.isLicensed -eq “True” } | Select-Object UserPrincipalName, DisplayName, Country, Department | Out-GridView;
       
        # Get Report for All UnLicensed users in Office 365
          Get-MsolUser -All | Where-Object { $_.isLicensed -eq “False” } | Select-Object UserPrincipalName, DisplayName, Country, Department | Export-Csv C:\UnLicensedUsers.csv -NoTypeInformation;
          Get-MsolUser -All | Where-Object { $_.isLicensed -eq “False” } | Select-Object UserPrincipalName, DisplayName, Country, Department | Out-GridView;
       
        # Check if we have availiable License in Office 365 Tenant
          If ($all -eq $consumed) { “There are no licences available”}
              Else { “There $left licences available”}
} # End LicenseStatistics

Function RemoveUser {
      # Remove a user from Office 365   
        Clear;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ”   Remove a User from Office 365    ” -ForegroundColor White;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ” ”   
       
        # Proceed to Remove user or users from Office 365
        Get-MsolUser -All | Out-GridView -Title “Choose users from the list you want to delete” -PassThru | ForEach-Object {Remove-MsolUser -UserPrincipalName  $_.UserPrincipalName -force}
        Write-Host “User was succesfully removed….” -ForegroundColor Green;

       # Proceed to Remove user or users from RecycleBin in Office 365
        Get-MsolUser -All | Out-GridView -Title “Choose users from the list you want to Remove from RecycleBin” -PassThru | ForEach-Object {Remove-MsolUser -UserPrincipalName $_.UserPrincipalName -RemoveFromRecycleBin}
        Write-Host “User was succesfully removed from RecycleBin….” -ForegroundColor Green;
} # End RemoveUser

Function RestoreUser{
      # Remove a user from Office 365   
        Clear;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ”   Restore a User from Office 365   ” -ForegroundColor White;
        Write-Host ” ===================================” -ForegroundColor Cyan;
        Write-Host ” ”   
       
        # Proceed to Recover user or users from Office 365
          Get-MsolUser -ReturnDeletedUsers | Out-GridView -Title “Choose users from the list you want to Recover” -PassThru | ForEach-Object {Restore-MsolUser -UserPrincipalName  $_.UserPrincipalName -AutoReconcileProxyConflicts}   
          Write-Host “User was succesfully Recovered…” -ForegroundColor Green;
}# End RestoreUser

Function ChangeUserPass {
        # Change users Password in Office 365   
        Clear;
        Write-Host ” =====================================” -ForegroundColor Cyan;
        Write-Host ”  Change Users Password in Office 365 ” -ForegroundColor White;
        Write-Host ” =====================================” -ForegroundColor Cyan;
        Write-Host ” ”   
       
        # Proceed to change user or users from Office 365
          Get-MsolUser -All | Out-GridView -Title “Choose user from the list you whish to change the Password” -PassThru | ForEach-Object {Set-MsolUserPassword -UserPrincipalName $_.UserPrincipalName -NewPassword $Password}  
          Write-Host “Password was change succesfully. Please type the New Password was automaticaly generate…” -ForegroundColor Green;
     
        # In case you want to set your Password for the User and not the auto-generate pass, disable the previews command, and enable the command bellow
        # $Password = “P@ssword1”
        # Get-MsolUser -All | Out-GridView -Title “Choose user from the list you whish to change the Password” -PassThru | ForEach-Object {Set-MsolUserPassword -UserPrincipalName $_.UserPrincipalName -NewPassword $Password}  
        # Write-Host “Password was change succesfully. Please try to login to the portal with the New Password…” -ForegroundColor Green;
 
} # End ChangeUserPass

Function SetPassNeverExpires {
   # Change users Password NeverExpires in Office 365   
        Clear;
        Write-Host ” ==========================================” -ForegroundColor Cyan;
        Write-Host ”  Users Password NeverExpiresin Office 365 ” -ForegroundColor White;
        Write-Host ” ==========================================” -ForegroundColor Cyan;
        Write-Host ” ”   
       
        # Proceed to change user or users from Office 365
          Get-MsolUser -All | Out-GridView -Title “Choose user from the list you whish to change the Password to Never Expire” -PassThru | ForEach-Object {Set-MsolUser -UserPrincipalName $_.UserPrincipalName -PasswordNeverExpires $true}  
          Write-Host “Password was change succesfully to Never Expires…” -ForegroundColor Green;

       # To view all users and their “Password never expires setting true”
          Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires | Export-Csv C:\PasswordNeverExpiresUsersTrue.csv -NoTypeInformation
          Write-Host “Recipient Statistics Report was exported succesfully as PasswordNeverExpiresUsers.csv..” -ForegroundColor Green;
          Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires | Out-GridView

       # To view all users and their “Password never expires setting false”
          Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires | Export-Csv C:\PasswordNeverExpiresUsersFalse.csv -NoTypeInformation
          Write-Host “Recipient Statistics Report was exported succesfully as PasswordNeverExpiresUsers.csv..” -ForegroundColor Green;
          Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires | Out-GridView
         
} # End SetPassNeverExpires

Function MailboxUsageReport{
     
      # This command retrieves details for mailboxes that were near or over the maximum mailbox size in Office 365   
        Clear;
        Write-Host ” ===========================================” -ForegroundColor Cyan;
        Write-Host ”  Mailbox Usage Detail Report in Office 365 ” -ForegroundColor White;
        Write-Host ” ===========================================” -ForegroundColor Cyan;
        Write-Host ” ”  

       # This command retrieves details for mailboxes that were near or over the maximum mailbox size       
         Get-MailboxUsageDetailReport | Out-GridView -Title “Mailbox Reports…….”;   
       
} # End MailboxUsageReport

Function RecipientStatisticsReport {
     # We use the Get-RecipientStatisticsReport cmdlet to view the recipient statistics report in Office 365   
        Clear;
        Write-Host ” ===========================================” -ForegroundColor Cyan;
        Write-Host ”  Recipient Statistics Report in Office 365 ” -ForegroundColor White;
        Write-Host ” ===========================================” -ForegroundColor Cyan;
        Write-Host ” ”   
      
       Get-RecipientStatisticsReport | Out-GridView -Title “Recipient Statistics Report…….”;
       Get-RecipientStatisticsReport | Export-Csv -Path C:\RecipientStatisticsReport.csv -NoTypeInformation;
       Write-Host “Recipient Statistics Report was exported succesfully as RecipientStatisticsReport.csv..” -ForegroundColor Green;

} # End RecipientStatisticsReport

Function ConnectionByClientTypeDetailReport {
    # This command retrieves details about the different types of clients used to connect to mailboxes Office 365   
        Clear;
        Write-Host ” ============================================” -ForegroundColor Cyan;
        Write-Host ”  Connect Mailboxes Types Stat in Office 365 ” -ForegroundColor White;
        Write-Host ” ============================================” -ForegroundColor Cyan;
        Write-Host ” ”      
    # This command retrieves details about the different types of clients used to connect to mailboxes 
      Get-ConnectionByClientTypeDetailReport | Out-GridView -Title “Statistics Report…….”;
      Get-ConnectionByClientTypeDetailReport | Export-Csv -Path C:\ConnectionByClientTypeDetailReport.csv -NoTypeInformation;
      Write-Host “Statistics Report was exported succesfully as ConnectionByClientTypeDetailReport.csv..” -ForegroundColor Green;

} # End ConnectionByClientTypeDetailReport

Function ConnectionByClientTypeReport {
    # This command retrieves details about the different types of clients used to connect to mailboxes in Office 365   
        Clear;
        Write-Host ” ============================================” -ForegroundColor Cyan;
        Write-Host ”  Connect Mailboxes Types Stat in Office 365 ” -ForegroundColor White;
        Write-Host ” ============================================” -ForegroundColor Cyan;
        Write-Host ” ”   
    # This command retrieves details about the different types of clients used to connect to mailboxes 
      Get-ConnectionByClientTypeReport | Out-GridView -Title “Statistics Report…….”;
      Get-ConnectionByClientTypeReport | Export-Csv -Path C:\ConnectionByClientTypeReport.csv -NoTypeInformation;
      Write-Host “Statistics Report was exported succesfully as ConnectionByClientTypeReport.csv..” -ForegroundColor Green;
} # End ConnectionByClientTypeReport
 
  LoginOffice365;
Do {
    $existingSession = Get-PSSession -Verbose:$false | Where-Object {$_.ConfigurationName -eq “Microsoft.Exchange”}
    If ($existingSession -eq $null) {Write-Host ” “}
    If ($existingSession -eq $true) {Write-Host “Already connect to Office 365..” -ForegroundColor Green}
    $opt = Read-Host $menu

  Switch ($opt)    {
         1  {# Change Users Password
             CreateUser;
            }
         2  {# Change Folder Permissions
             RemoveUser;
            }
         3  {# Mailbox Forwoarding
             RestoreUser;
            }
         4  {# Create a Shared Mailbox
             ChangeUserPass;
            }
         5  {# Check Mailboxs Report
             SetPassNeverExpires;
            }
         6  {# Give Users Send As Permission
             LicenseStatistics;
            }     
         7  {# Export List for SMTP address & Last connection time
             SmtpReport;
            }     
         8  {# Share calendar in Office 365
             RecipientStatisticsReport;
            }
         9  {# Share calendar in Office 365
             MailboxUsageReport;
            }                  
        10  {# Logout from Office 365
            ConnectionByClientTypeDetailReport;
            ConnectionByClientTypeReport;
            }
        21  {# Exit
            If ($choose -ne -21){
            Write-Host “Exiting from Office 365…..” -ForegroundColor Cyan
            }
            {……………………………..}
            }
}
} While ($opt -ne 21) # Execute cmdlets from the script in order

#########################################################################################################################

Enjoy…..

 

Scenario: In this scenario an Office 365 mailbox is not receiving a message sent from outside of the Office 365 organization.

Step 1: See if Office 365 received the message and was able to deliver it

Since you don’t have the item, you will need to enter the delivery report center though Outlook Web App (OWA).  Log in to OWA, go to Options

Find the Delivery Reports under Organize Email:

Highlight the Search for messages that were sent to me from button and then in the box that pops up, type the SMTP address of the user you sent mail to:

Things to consider for inbound messages when looking at the Delivery Report results:

· If the message doesn’t appear in the report results, it may never have made it to Office 365. 

· If the message appears in the report results, check to make sure it was delivered.  If it was delivered, check to see if an inbox rule rerouted or deleted the message.  Check to see if the email was moved to the Junk folder.  For more information on inbox rules, see Learn About Inbox Rules.

· Administrators: If the message was not delivered, did a transport rule act on the message? For more information on Transport Rules, see Create a new Rule.

Step 2: Work with the sender to determine what happened to the message

Assuming that you still have not solved the issue, this is about as far as you can go right now from the receiving side.  If the sender just sent you the message, you may need to give it some time to arrive or timeout.  If the message times out, then the sender will get a notification and be able to skip to the troubleshooting notifications section.  If, however, the sender does not receive a notification, then the sending side should perform message tracking.  In most cases, the remote side should be able to provide you with information to help you make sure that the message was handed off properly.  One data point that will be extremely useful is the IP address of the system to which they handed off the message.  Frequently, the problem is that a DNS configuration problem causes the sending system to hand off the message to the wrong email server.  Having an IP address will help you in this case.

One last thing you can try as a test: have the sender email your onmicrosoft.com email address instead of using your custom domain address.  This test can help prove if the issue is with DNS.

Common problems

Here we’ll add links to helpful Knowledge Base articles or other documentation that pertains to this scenario.   

· Use of more than one MX record with Office 365 is not recommended or supported by Microsoft.  The options are as follows:

o MX record points to Office 365 ONLY

o MX record points to other email server which forwards some/all email to Office 365 (e.g. Hybrid or Simple Shared).  Multiple MX records can be used in this scenario, but only if one of the MX records is NOT pointing to Office 365.

Trying to use multiple records can result in:

· Missing email

· Rejected email

· Inconsistent results with spam

To verify that you only have one MX record, open a Command Prompt and type: nslookup -type=MX contoso.com

Where contoso.com is your domain. You should ONLY get one result, like this:
Server:  test.contoso.com
Address:  10.2.3.7
Non-authoritative answer: contoso.com  MX preference = 5, mail exchanger = contoso_com.mail.eo.outlook.com

If you previously used your domain with BPOS, FOPE, or Exchange Hosted Archive then even after you have verified your domain, you will find that messages sent to your domain may bounce with either a 550 5.4.1 Relay Access Denied or possible mail loop.  If both of these conditions are true, you need to contact FOPE support and have them remove your duplicate domain.

· If you recently moved your domain (Professional) or MX records (Enterprise or Education), there is a DNS caching period where some servers may still deliver your email to your old provider.  If you have recently moved the domain to Office 365 and are missing email, one thing you should try to do is check the old provider and see if they are still getting some of your email.  The problem may be isolated to some senders.

· If you have Office 365 Professional and are having trouble receiving email from your old email provider, the problem may be that the old provider is still hosting stale DNS records for your domain.  If the domain you are using was hosted somewhere other than the domain registrar you were using, then you may also need to contact your old DNS provider and have them remove the stale entries for your domain. For more information see Domains in Office 365.

Outbound mail flow

Why is my message taking so long to arrive at its destination?

Scenario: You sent a message from your Office 365 mailbox.  One or more recipients are complaining either that they haven’t received the message or that the message took a long time to arrive.

Steps:

Open a delivery report for your message

If you have Outlook 2010, go to your Sent Items folder, and find the message you want to track.  Open the message.  In the message window, click the File tab.  Under Message Delivery Report, click Open Delivery Report. 

As an administrator or someone with the ability to track messages (helpdesk), you can also search directly from the Exchange Administrator Control. In the EAC (Exchange Administrator Control) go to Mail flow > Message trace.

Common problems

Here we’ll add links to helpful Knowledge Base articles or other documentation that pertains to this scenario.

· If you are having trouble sending mail to certain domains, you may want to verify that you have the recommended DNS record types for sending mail.  Specifically, you want an A record for the domain (example: @.contoso.com – this record should generally point to the same address as your www record), an MX record, and SPF record that designates Outlook.com as a sender.  For more information see Domains in Office 365.