Is it too much to ask that there be a single Word file (or PDF if you have to) that contains all of the PowerShell commands pertaining to Exchange 2010 and their syntax? No need for examples, just the command and the syntax. Why a single document? So that we can search for words that we think are likely to be in a command to figure out which command does what we want to do. I created a Word document from the output of the get-help command in Exchange 2007, that is pretty much worthless in Exchange 2010 since the syntax for some commands changed radically and in some cases the old command is gone and replaced by something completely different. Trying to search the TechNet library with Bing is a pretty futile effort since you can't scope BIng to look at just Exchange 2010 - you get lots of hits for Exchange 2007 and a bunch of other products that have nothing to do with what you are researching. The structuing of the documentation in the TechNet Library also makes it hard to figure out what command you need for a given task. The only way to do the searches efficiently is to copy all of the documentation to a file, going through layers and layers of articles and copy and pasting them to a Word file, a very time consuming task. Even posting this question leads to "Related Topics" that aren't related to Exchange 2010! I see references to Configuration Manager, SharePoint, App-V - why would I get those hits while posting in the Exchange forums?? Please give us a break - with literally thousands of EMS commands, this is desperately needed! SnoBoy

Please use Exchange Server 2010 SP1 Help file, which contains the cmdlets and associated parameters. I also use it to search the related commandsPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Again, the search tool with the help file is horrible. It is about as unuseful as Bing is on the TechNet library. After playing around with the Shell commands, I came up with this command line that created a text file I could then copy and paste into Word: get-command -syntax |fl > C:\temp\EX2010.txt I find this far more useful for narrowing down the command I am looking for than the"help" file that gives so many hits that aren't relevant as to be counter-productive, IMHO.SnoBoy