After a good response to my New Cmdlets in Lync 2013 Post I thought I’d post the new PowerShell cmdlets
in Exchange 2013 Preview. Quite a few don’t have descriptions yet but you can guess the functionality
from the naming
Also, we’ve lost 13 cmdlets, mainly due to the changes in Public Folders:
So what are the new Exchange 2013 Preview cmdlets?
|Get-ActiveSyncDeviceAutoblockThreshold||Microsoft Exchange and Exchange ActiveSync have the capability to block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that have the capability to cause issues with the server. The Get-ActiveSyncDeviceAutoblockThreshold cmdlet returns the settings for the requested threshold rule.|
|Disable-App||The Set-App cmdlet can only be used when configuring the availability of an organization app. This task requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it’s a default app for Microsoft Outlook).Default apps in Microsoft Office Outlook Web App and apps that you’ve installed for use by users in your organization are known as organization apps. Organization apps can’t be removed by end users, but can be enabled or disabled. If an app is an organization app (scope default or organization), the delete control on the toolbar is disabled for end users. Administrators are able to remove organization apps. Administrators can’t remove default apps, but they can disable them for the entire organization.|
|Get-AuthConfig||No Description Yet|
|Get-AuthServer||The Set-AuthConfig parameter define Microsoft Exchange as a partner application for server-to-server authentication with other partner applications such as SharePoint 2013 Preview and Lync 2013 Preview, including the certificate used for signing tokens. It’s generally not required for this configuration to be modified except in some cases where you must use a different certificate instead of the self-signed certificate created by Exchange Setup or to use a new certificate after the old one has expired.|
|Get-CalendarDiagnosticAnalysis||You run the Get-CalendarDiagnosticAnalysis cmdlet to analyze calendar data you’ve retrieved using the Get-CalendarDiagnosticLog cmdlet. For more information, see Get-CalendarDiagnosticLog.|
|Get-ClassificationRuleCollection||No Description Yet|
|Get-DataClassification||No Description Yet|
|Get-DlpPolicy||No Description Yet|
|Export-DlpPolicyCollection||The Export-DlpPolicyCollection cmdlet exports the settings of the DLP policies and the associated transport rules. You use the Import-DlpPolicyCollection to import the DLP policy collection into your organization.|
|Get-DlpPolicyTemplate||No Description Yet|
|Get-ExchangeServerAccessLicense||The Get-ExchangeServerAccessLicense cmdlet returns a list of licenses in use in your Exchange 2013 Preview organization. The cmdlet returns a collection of these license names:Exchange 15 Standard CAL
Exchange 15 Enterprise CAL
Exchange 15 Server Standard Edition
Exchange 15 Enterprise Edition
|Get-ExchangeServerAccessLicenseUser||The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it’s associated.|
|Get-FrontendTransportServer||The Front End Transport service runs on all Client Access servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. The Front End Transport service only communicates with the Hub Transport service on a Mailbox server, and doesn’t queue any messages locally.|
|Add-GlobalMonitoringOverride||No Description Yet|
|Get-HealthReport||The following list contains the health values that are returned:Online
|Remove-HybridConfiguration||Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren’t disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard won’t have a hybrid configuration reference point for your existing feature settings. As a result, it will automatically create a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that’s removed, aren’t removed or modified until the Hybrid Configuration wizard is run again.|
|Get-InterceptorRule||No Description Yet|
|Disable-MailboxQuarantine||No Description Yet|
|Get-MailboxSearch||No Description Yet|
|Get-MailboxTransportService||The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using remote procedure calls (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Hub Transport service that runs on all Mailbox servers for routing their ultimate destinations.|
|Get-MalwareFilteringServer||No Description Yet|
|Get-MalwareFilterPolicy||No Description Yet|
|Remove-MalwareFilterRecoveryItem||No Description Yet|
|Send-MapiSubmitSystemProbe||No Description Yet|
|Redirect-Message||When a message queue is drained, the active messages in the queues on the source Mailbox server are routed to the target Mailbox server. After the messages are received and queued by the target Mailbox server, the messages are made redundant. Other considerations include the following:Only active messages are drained. Shadow queues aren’t drained.
Messages in the poison message queue aren’t drained.
The source server won’t accept new messages while the queues are drained.
|Complete-MigrationBatch||After a migration batch for a local or cross-forest move has successfully run and has a status state of Synced, use the Complete-MigrationBatch cmdlet to finalize the migration batch. Finalization is the last phase performed during a local or cross-forest move. When you finalize a migration batch, the cmdlet does the following for each mailbox in the migration batch:Runs a final incremental synchronization.
Configures the user’s Microsoft Outlook profile to point to the new target domain.
Converts the source mailbox to a mail-enabled user in the source domain.
When the finalization process is complete, you can remove the batch by using the Remove-MigrationBatch cmdlet.
If a migration batch has a status of Completed with Errors, you can rerun the Complete-MigrationBatch cmdlet. The cmdlet will attempt to finalize the failed users.
|Get-MigrationConfig||No Description Yet|
|Get-MigrationEndpoint||Use the New-MigrationEndpoint cmdlet to retrieve settings for different types of migration.Cross-forest move Move mailboxes between two different on-premises Exchange forests. Cross-Forest Moves require the use of a “RemoteMove” endpoint.
Remote move In a hybrid deployment, this involves “onboarding” or “offboarding” migrations. Remote moves require the use of a “RemoteMove” endpoint. Onboarding moves mailboxes from an on-premises Exchange organization to Exchange Online in Office 365, and uses a RemoteMove endpoint as the source endpoint of the migration batch. Offboarding moves mailboxes from Exchange Online in Office 365 to an on-premises Exchange organization and uses a RemoteMove endpoint as the target endpoint of the migration batch.
Cutover Exchange migration Migrate all mailboxes in an on-premises Exchange organization to Exchange Online in Office 365. Cutover Exchange Migration requires the use of an “Exchange” endpoint.
Staged Exchange migration Migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online in Office 365. Staged Exchange Migration requires the use of an “Exchange” endpoint.
IMAP migration Migrate mailbox data from an on-premises Exchange organization or other email systems to Exchange Online in Office 365. For an IMAP migration, you must first create the cloud-based mailboxes before you migrate mailbox data. IMAP Migrations require the use of an “IMAP” endpoint.
Local Move mailboxes between different servers or databases within a single on-premises Exchange forest. Local moves do not require the use of an endpoint.
|Export-MigrationReport||The Export-MigrationReport is used by the Microsoft Exchange migration process to enable an administrator to download a CSV file that contains migration errors for a selected migration batch. This cmdlet is not run by an administrator in Windows PowerShell.|
|Test-MigrationServerAvailability||The Test-MigrationServerAvailability cmdlet verifies that you can communicate with the on-premises mail server that houses the mailbox data that you want to migrate to cloud-based mailboxes. When you run this cmdlet, you must specify the migration type. You can specify whether to communicate with an IMAP server or with an Exchange server.For an IMAP migration, this cmdlet uses the server’s FQDN and a port number to verify the connection. If the verification is successful, use the same connection settings when you create a new migration request with the New-MigrationBatch cmdlet.
For an Exchange migration, this cmdlet uses one of these set of settings to communicate with the on-premises server:
For Exchange 2003, it uses the server’s FQDN and credentials for an administrator account that can access the server.
|Get-MigrationStatistics||No Description Yet|
|Get-MigrationUser||No Description Yet|
|Get-MigrationUserStatistics||No Description Yet|
|Clear-MobileDevice||The Get-MobileDevice cmdlet returns identification, configuration, and status information for each mobile device.|
|Get-MobileDeviceMailboxPolicy||With the Set-MobileDeviceMailboxPolicy cmdlet, you can set each parameter in a mailbox policy.|
|Get-MobileDeviceStatistics||The Get-MobileDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes.|
|Get-MonitoringItemHelp||No Description Yet|
|Get-MonitoringItemIdentity||No Description Yet|
|Invoke-MonitoringProbe||No Description Yet|
|Get-Notification||No Description Yet|
|Test-OAuthConnectivity||No Description Yet|
|Get-PartnerApplication||In Exchange Server 2013 Preview, you can configure partner applications such as SharePoint to access Exchange Server resources. Use the New-PartnerApplication cmdlet to create a new partner application configuration for an application that needs to access Exchange 2013 Preview resources. For details, see Integration with SharePoint and Lync.We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the \Exchange Server\V15\Scripts folder to configure partner applications.|
|Get-PendingFederatedDomain||The Get-PendingFederatedDomain cmdlet is used as part of the Exchange Administration Center (EAC) functionality and shouldn’t be used by administrators manually configuring a federation trust.|
|Get-PolicyTipConfig||No Description Yet|
|New-PowerShellVirtualDirectory||Although it’s possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support.|
|Dump-ProvisioningCache||The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators need to run this cmdlet only if incorrect links or properties are stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache. This is a rare occurrence because the provisioning cache has invalidation notification logic.The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don’t change for months or years after they’re created, they’re stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance.|
|Update-PublicFolderMailbox||No Description Yet|
|Get-PublicFolderMailboxDiagnostics||No Description Yet|
|Get-PublicFolderMigrationRequest||The search criteria for the Get-PublicFolderMigrationRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search results and reduce your search criteria. For now there can be only one migration request at any given time.|
|Get-PublicFolderMigrationRequestStatistics||The RequestQueue and MRSInstance parameters are for debugging purposes only.|
|Get-PublicFolderMoveRequest||No Description Yet|
|Get-PublicFolderMoveRequestStatistics||No Description Yet|
|Get-QueueDigest||No Description Yet|
|Get-ResourcePolicy||By default, there is one resource policy for each resource that is managed by Exchange workload management. You can use the New-ResourcePolicy cmdlet to create custom resource policy objects to change the way that Exchange controls the resources that are consumed by Exchange workloads. When you create a new resource policy, you must specify a name of the resource policy, the type of resource, and the name of the workload management policy to which you want it associated. You must use the Set-ResourcePolicy cmdlet to set the thresholds for the new custom resource policy.|
|Add-ResubmitRequest||No Description Yet|
|Get-ServerComponentState||No Description Yet|
|Get-ServerHealth||Use the Get-ServerHealth cmdlet to return health information related to the server you specify. The cmdlet returns health values that you can use to determine the state of the server.The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned:
|Add-ServerMonitoringOverride||Use the Get-ServerMonitoringOverride cmdlet to return all overrides created on the specified server.|
|Get-SiteMailbox||The Set-SiteMailbox cmdlet allows you to change a site mailbox’s settings, such as the SharePoint URL. This cmdlet is primarily used by SharePoint and Exchange user interface such as the SharePoint URL. This cmdlet should only be used for diagnostic and troubleshooting purposes.|
|Get-SiteMailboxDiagnostics||Use the Get-SiteMailboxDiagnostics cmdlet to view important event-related data for each site mailbox. This information can be used to troubleshoot site mailbox issues.|
|Get-SiteMailboxProvisioningPolicy||Use the Get-SiteMailboxProvisioningPolicy cmdlet to view information about site mailbox provisioning policies.|
|Get-TeamMailbox||No Description Yet|
|Get-TeamMailboxDiagnostics||No Description Yet|
|Get-TeamMailboxProvisioningPolicy||No Description Yet|
|Get-TransportService||No Description Yet|
|Disable-UMCallAnsweringRule||The Enable-UMCallAnsweringRule cmdlet enables the call answering rule by modifying its status variable. When the call answering rule is created, it’s enabled. This cmdlet allows you to enable a previously disabled call answering rule. Enabling a call answering rule enables the cmdlet to retrieve the call answering rule including the conditions and actions for a specified call answering rule.|
|Get-UMCallRouterSettings||The Get-UMCallRouterSettings cmdlet retrieves the properties for a Client Access server that runs the Microsoft Exchange Unified Messaging Call Router service and returns a list of available Client Access servers from Active Directory. When the cmdlet is used for a single Client Access server, it returns the UM call router properties including MaxCalls, MaxFaxCalls, and UMDialPlans. The properties and their values for the Client Access server are stored in the Unified Messaging section of the Exchange Server configuration object in Active Directory.|
|Get-UMMailboxConfiguration||The Get-UMMailboxConfiguration cmdlet displays the voice mail options and other personal voice mail configuration setti ngs for a UM-enabled mailbox. When you run the cmdlet, it shows you if a voice mail greeting is enabled, if the user ha s a custom voice mail or away greeting, and whether this is a valid configuration. After you run the Get-UMMailboxConfiguration cmdlet, you see the voice mail options and their settings on a UM-enabled mailbox. You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they’re not included in the permissions assigned to you. T o see what permissions you need, see the “UM mailbox” entry in the Unified Messaging Permissions topic.|
|Get-UMPhoneSession||No Description Yet|
|Get-UserPhoto||The user photos feature allows users to associate a picture with their account. User photos are stored in the user’s Active Directory account and in the root directory of the user’s Exchange mailbox. The user photo feature must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user’s photo. Otherwise, you get an error message saying the user photo doesn’t exist for the specified users. Administrators use the Set-UserPhoto cmdlet or the Exchange Administration Center to configure user photos. Users can upload, preview, and save a user photo to their account by using the Outlook Web App Options page.|
|Get-WorkloadManagementPolicy||Use the Get-WorkloadManagementPolicy cmdlet to retrieve and view properties of the associated workload management policy object.|
|Get-WorkloadPolicy||By default, Exchange controls the resources that are consumed by Exchange workloads using a default workload policy for each workload. You can use the New-WorkloadPolicy to create a custom workload policy to change the way that Exchange controls the resources that are consumed by Exchange workloads. When you create a new workload policy, you must specify a name for the workload policy, the type of workload, the priority of the workload (that is designated by its classification), and the workload management policy to which you want it associated.|