Harish Kaushal Blog https://docs.microsoft.com/archive/blogs/harishck/feed.xml Office 365 Exchange Online and Identity Online Blog Wed, 17 Apr 2019 03:21:46 GMT en-US hourly 1 PowerShell script to run MIM Delta or Full Sync https://docs.microsoft.com/archive/blogs/harishck/powershell-script-to-run-mim-delta-or-full-sync Tue, 30 Jan 2018 10:36:10 GMT https://blogs.msdn.microsoft.com/harishck/?p=155 Hello Guys, Struggling with finding out easy way to run MIM Delta or Full Sync, here is the script which can help.
  • Run below command to create a directory to keep module.

          New-Item -Path "$home\MimSync" -ItemType Directory

  • Run below command to update PsModulePath

 $p = [Environment]::GetEnvironmentVariable('PSModulePath','User')

$p += ";$home\"

        [Environment]::SetEnvironmentVariable('PSModulePath',$p,'User')

  • Extract the attached file to $home\MimSync folder.

Link to Module : - MimSync

  • Run below commands to start sync.

         Import-Module MimSync

         Start-MimSync

  • You will get two options whether to run delta sync or Full sync.
  • Output will look like below.

              Please do share feedback.]]> Unable to remove domain from Office 365? Here is the script which can help!! https://docs.microsoft.com/archive/blogs/harishck/unable-to-remove-domain-from-office-365-here-is-the-script-which-can-help Mon, 08 May 2017 12:32:09 GMT https://blogs.msdn.microsoft.com/harishck/?p=65 When we should use this script? When you are trying to remove a domain from one Office 365 tenant and want to verify domain on another tenant but you are unable to remove and getting errors like below. Remove-MsolDomain : Unable to remove this domain. Use Get-MsolUser -DomainName<domain name> to retrieve a list of objects that are blocking removal. At line:1 char:18 + Remove-MsolDomain <<<< -DomainName <DomainName> + CategoryInfo : OperationStopped: (:) [Remove-MsolDomain], MicrosoftOnlineException + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.DomainNotEmptyException,Microsoft.Online.Administration.Automation.RemoveDomain Remove-MsolDomain : Unable to complete this action. Try again later. At line:1 char:1 + Remove-MsolDomain -DomainName peppromotions.com –Force + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : OperationStopped: (:) [Remove-MsolDomain], MicrosoftOnlineException     + FullyQualifiedErrorId : Microsoft.Online.Administration.Automation.InternalServiceException,Microsoft.Online.Adm    inistration.Automation.RemoveDomain

What is the reason for these errors?

We get this error when domain we are trying to remove is getting consumed in any of the Office 365 User or Exchange Recipient or Azure AD. So in order to release the domain first we need to remove all the references for that domain from Office 365, Exchange online and Azure. So this script will help you in finding out where all domain is getting used.

What do you need to know before you begin?

Need an admin account who is Global admin for Office 365, Exchange Online and Azure AD. Windows PowerShell. Azure AD and MSOnline modules installed.(Note: If not installed script will guide you in installing them)

How to download?

Download Link :- version-2

What all this script will do?

Checks for all the modules required to perform steps in the steps and if they are missing it will guide to install. Checks for domain references under users in Office 365 and extract CSV file. Checks for domain references under recipients in Exchange Online and extract CSV file. Checks for domain references in Azure AD and extract CSV file. Helps in removing Azure Apps consuming the domain we want to remove. If no references found then helps in removing domain.

How you can use it?

1. Save attached and extract attached script. It should contain below files. scripts 2. Open windows PowerShell as administrator and run below command to set execution policy. Set-ExecutionPolicy Unrestricted -Force 3. Run below command to set directory where script is extracted and import module. cd "Directory where scripts extracted" Import-Module .\DomainScriptModule.psm1 Once you run above command it will give you below warning four time as this script is not signed so you need to type "R" to allow this script. Security warning Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run D:\Scripts\DomainScript\DomainScript\DomainScriptModule.psm1? [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): R 4. Once you allow script it will start checking if AzureADPreview module is installed or not, if not it will give you an option to install as in my case its not installed so i selected Y in below option. It will perform same steps for MsOnline module and give you link if not installed. modulecheck 5. In my case MsOnline module is also not installed so it will check and provide me an link to download module. Download module from listed link and re-import module. msonlinemodule 6. Once all module check passes it will import module and ask for Global admin credentials which is global admin for Office 365, Exchange online as well as Azure AD. creds 7. After entering credentials it will connect to Office 365, Exchange online and Azure AD. 8. Once connected run below command. Domain-RemovalScript 9. After executing above command it will ask for domain name which you want to remove. In my case i am typing abc123.com Type domain you want to remove: abc123.com nouserdomain 10. Once you type above command it will do below checks. If domain exists on the tenant or not?If Yes, then continue otherwise Stop. How many Msol users consuming domain? How many Exchange Online users consuming domain? How many Azure objects consuming domain? If no reference found in any of the service then ask if you want to remove the domain or not. 11. In step 9, domain i used doesn't have any object reference so we get Green output and its asking if we want to remove the domain or not. 12. If i try domain which has object references in Office 365, Exchange and Azure output should look like below. It will show you MSOL users which are consuming this domain. It will ask for CSV file where you want to export the data of MsolUsers. It will show you Exchange recipient and there type which all are consuming this domain and extract CSV. It will show you Azure Apps which are consuming this domain and extract them to a CSV. It will also give you option of you want to remove shown apps or not, if you select Yes, it will remove the apps. userdomain 13. Once you remove all the references run below command again to check and if all green, remove the domain. Domain-RemovalScript I hope it helps. Please do share your feedback in comments and it you run into any issues please feel free to share it in comments. Thanks, Harish]]> Script to Update msExchArchiveGuid and msExchArchiveName in bulk from Exchange Online to On-premise AD https://docs.microsoft.com/archive/blogs/harishck/update-msexcharchiveguid-in-bulk-from-exchange-online-to-on-premise-ad Sun, 26 Feb 2017 04:21:39 GMT https://blogs.msdn.microsoft.com/harishck/?p=35 Summary – Use this script for errors like below on office 365 portal. Failed to sync the ArchiveGuid 00000000-0000-0000-0000-000000000000 of mailbox 28b656595f-924b-4c5b-a4be-ea255450f  because one cloud archive 45e245ba67-a5ed-4408-8ced-a4d124521 exists Note: Recommended way to resolve this issue is using On-premise Exchange PowerShell. But these steps are for those scenarios wherein we don’t have on-premise exchange to fix this but exchange attributes are there in AD schema. Managing the Exchange Attributes for cloud users from AD PowerShell or from ADSIedit is not supported and we strongly recommend keeping an active Exchange Server in your Active directory with minimum roles, just for being able to manage the Exchange attributes that shall be synced to the cloud. For more information about these recommendations, you might find interesting below public article: https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx “The question of whether a third-party management tool or ADSIEDIT can be used is often asked. The answer is you can use them, but they are not supported. The Exchange Management Console, the Exchange Administration Center (EAC), and the Exchange Management Shell are the only supported tools that are available to manage Exchange recipients and objects. If you decide to use third-party management tools, it would be at your own risk. Third-party management tools often work fine, but Microsoft does not validate these tools. “ Who should use this? It can be used for users for whom you are getting error like below. Failed to sync the ArchiveGuid 00000000-0000-0000-0000-000000000000 of mailbox 28b656595f-924b-4c5b-a4be-ea255450f  because one cloud archive 45e245ba67-a5ed-4408-8ced-a4d124521 exists What do you need to know before you begin?
  • Should have installed MsOnline module for Office 365.
  • Should have Global admin credentials for Office 365.
  • Should have logged in to domain controller with Enterprise Admin credentials.
  • Should have rights to execute scripts.
How you do this?
  1. Login to a domain controller which meets above per-requites.
  2. Download and extract attached zip file in any location on the server. For example, I extracted it under “C:\O365”. There should be below 4 files.
  ArchiveGuid_Version1.0.ps1 ArchiveGuid_Version1.0_Menifest.psd1 ArchiveGuid_Version1.0_Module.psm1 ConnectingToResources.ps1  
  1. Open Windows PowerShell as administrator on the machine and set the directory of script files. For example, below.
  Set-Location “C:\O365”  
  1. Run below command and you should be able to see script files. If they are not there then you have set wrong location on step 3.
  Get-ChildItem
  1. Run below command to import module.
  Import-Module .\ArchiveGuid_Version1.0_Menifest.psd1  
  1. Run below command to connect to office 365 and when prompted enter Office 365 global admin credentials.
ConnectTo-office365
  1. Run below command to collect effected users data from Office 365.
Get-EffectedMsolUser -CSVPath “location for csv file” For example: Get-EffectedMsolUser -CSVPath "C:\O365\EffectedMsolUser.csv"   **CSVPath – Path where you want to extract CSV file of effected MSOL users. Suggested to use same path where you have script files.  
  1. Run below command to collect effected mailboxes data from Office 365.
Get-EffectedMailboxes -MsolUserCSVPath "location of CSV file collected in step 7" -MailboxCSVPath "location to create effected mailbox csv file" For example: Get-EffectedMailboxes -MsolUserCSVPath "C:\O365\EffectedMsolUser.csv" -MailboxCSVPath "C:\O365\EffectedMailboxes.csv"   **MsolUserCSVPath – Path of CSV file collected in step 7. **MailboxCSVPath – Location to create effected mailboxes csv. Suggested to use same path where you have script files.  
  1. Run below command to see effected AD accounts in your on-premise active directory. Output of this will show samAccountName of users where Archive Guid and name needs to be set.
  Get-EffectedAdUser -EffectedMailboxCsvPath "location of CSV file generated in step 8" -EffectedPartition 'Domain partition where you want to search'   For example: Get-EffectedAdUser -EffectedMailboxCsvPath "C:\O365\EffectedMailboxes.csv" -EffectedPartition 'DC=hckoffice365,DC=in'   **EffectedMailboxCsvPath – Location of CSV file generated in step 8. In my case its “C:\O365\EffectedMailboxes.csv” **EffectedPartition (Not Mandatory) – Domain partition where you want to search and set the attributes. If you don’t mention this attribute, then script will take root partition by default.  
  1. Run below command to set Archive Guid and Archive Name values on effected user accounts.
  Set-msExchArchiveInfo -EffectedMailboxCsvPath "location of CSV file generated in step 8" -EffectedPartition "domain partition where you want to set the values"   For example:   Set-msExchArchiveInfo -EffectedMailboxCsvPath "C:\O365\EffectedMailboxes.csv" -EffectedPartition "DC=hckoffice365,DC=in"   **EffectedMailboxCsvPath – Location of CSV file generated in step 8. In my case its “C:\O365\EffectedMailboxes.csv”   **EffectedPartition (Not Mandatory) – Domain partition where you want to search and set the attributes. If you don’t mention this attribute, then script will take root partition by default.  
  1. Once above steps completed force directory sync from AAD connect server PowerShell using below command.
  Start-AdSyncSyncCycle -PolicyType Initial  
  1. Once sync completed check office 365 portal after 10-15 mins and there should not be any error for effected mailboxes. You can also confirm by performing step 7 again and this time output CSV file should be blank.
  Script File Zip file - Archive Guid Script   Please do share feedback in comments if you face any issues. Thanks, Harish Kaushal]]>