So what can you do to begin mastering the Exchange 2007 cmdlets? Well this is where PowerGUI comes into the picture.
In addition to the above, the frustrated Exchange administrators have to use the EMS to manage public folders, POP3/IMAP4 access and many other Exchange 2007 features until Exchange Server 2007 Service Pack 1 RTWs. Because a lot of work went into creating consistent verb-noun pairs (aka cmdlet’s), most Exchange administrators don’t have a problem issuing single cmdlet’s such as Move-Mailbox or Get-MailboxDatabase, but as soon as it comes to using piping (meaning one cmdlet makes use of the output of another cmdlet) or simply modifying objects in bulk, most Exchange administrators get stuck. Although the Exchange Product group did everything in their power to make managing tasks via the EMS as easy, simple, and painless as possible, Exchange administrators with no scripting experience at all can find it extremely difficult to manage objects using this new command shell. In Exchange Server 2007, management of single recipients, databases, servers and other objects can typically be performed from within the Exchange Management Console, but when you are required to perform bulk changes of one or more of these objects, you need to turn to the new Exchange Management Shell (EMS). If you would like to read the next part in this article series please go to Managing Exchange 2007 using PowerGUI (Part 2)
0 kommentar(er)
