Hi Everyone this is Prem, I have worked as Microsoft 365 support ambassador. In this blog I will share How to Fix The term ‘Start-ManagedFolderAssistant’ is not recognized as the name of a cmdlet, function, script file, or operable program error.
This command is available in On-premise Exchange and Exchange online environment.
Depending on the environment you can have different fix for this error.
If your mailbox on which you are trying to run this command is on on-premise, then you will have to make sure that you are on the Windows Server which has Exchange running on it and you are running this command in Exchange Management Shell and not Windows PowerShell.
With the above checked, you should be able to run it without the error.
If your mailbox is on Exchange Online, then this error can occur when we run the command in the Windows PowerShell which is not connected to Exchange online.
Steps to Fix The term ‘Start-ManagedFolderAssistant’ is not recognized error for Exchange Online mailboxes:
Open Windows PowerShell as Administrator on your computer and then connect it to Exchange online using this detailed article.
Once it is connected, you should be able to run the Start-ManagedFolderAssistant command.
Below is the syntax of the Start-ManagedFolderAssistant command:
Start-ManagedFolderAssistant
[-Identity]
[-StopHoldCleanup]
[-AggMailboxCleanup]
[-Confirm]
[-FullCrawl]
[-InactiveMailbox]
[-WhatIf]
Example for the above command:
Start-ManagedFolderAssistant -Identity "Prem@theadmin365.com"
Above “Prem@theadmin365.com” is the email address of the user mailbox on which I want to initiate MRM processing.
To know more in detail about the command Start-ManagedFolderAssistant, refer Microsoft Official article.
If you are looking to setup retention policies, troubleshoot Archive issues and even backup the Archive, refer this ARTICLE.
Do let me know if you have any question in the comment box below.
Date:31/05/2023
Author: Prem
Tag: The term ‘Start-ManagedFolderAssistant’ is not recognized