Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Enable-UMService

 

Applies to: Exchange Server 2013

Topic Last Modified: 2012-11-05

Use the Enable-UMService cmdlet to set the status of a Microsoft Exchange Server 2007 or Exchange Server 2010 Unified Messaging server to enabled. This setting enables the Unified Messaging server to process UM calls.

For information about the parameter sets in the Syntax section below, see Syntax.

Enable-UMService -Identity <UMServerIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

This example enables Unified Messaging on the UM server MyUMServer.

Enable-UMService -Identity MyUMServer

The Enable-UMService cmdlet sets the status of an Exchange server running the Unified Messaging server role. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.

After this task is completed, the UM server is available to answer incoming calls.

WarningWarning:
This cmdlet only is available for Exchange 2007 and Exchange 2010 servers running the Unified Messaging server role, and it’s not available on Exchange 2013 Client Access and Mailbox servers.

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. To see what permissions you need, see the "Mailbox Server (UM service)" entry in the Unified Messaging Permissions topic.

 

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.UMServerIdParameter

The Identity parameter specifies the identifier for the UM server being enabled. This is the directory object ID for the Mailbox server.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.