Enabling the UM server is easy. All that is required is the name of the UM server. The cmdlet is
Enable-UMServer . Once the server is enabled it will begin processing any available calls that it has in
the associated UM dial plan. The UM IP gateway that was disabled to have some patches applied can
now start taking calls again. The Enable-UMIPGateway is similar to its disable counterpart. All that is
required is the identity of UM IP gateway. To enable our test gateway the cmdlet would look like this:
Enable-UMIPGateway -Identity test
When devices are no longer used or functionality no longer needed, they can be removed via the
Remove-* set of cmdlets. These cmdlets will remove the associated data from Active Directory. At this
time there is no undo function for a remove cmdlet. As a result, care should be taken when removing any
UM object. With enable and disable the UM administrator had the ability to set the status of the UM
server. It would seem logical that the UM server, then, would be able to be disabled using a similar
cmdlet. This is not the case. Using step.com /m:uninstall /r:u is the only supported way to
remove the UM server from the Exchange topology.
There are six Remove cmdlets. All require the Identity value as the only required value. Though this
may seem simplistic in nature, there is a certain amount of preprocessing that must occur.
Pages:
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426