I just installed Exchange 2010 in a brand new Domain on a Windows 2008 Enterprise Server with SP2. Now when I open the exchange management shell or try to access the Queue Viewer via the Exchange Managment Console I get the following error and I can't run any commands in the Exchange Management Shell or in the PowerShell. The term 'D:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.ps 1' is not recognized as the name of a cmdlet, function, script file, or operabl e program. Check the spelling of the name, or if a path was included, verify th at the path is correct and try again. At line:1 char:2 + . <<<< 'D:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.p s1'; Connect-ExchangeServer -auto + CategoryInfo : ObjectNotFound: (D:\Program File...oteExchange.p s1:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException The term 'Connect-ExchangeServer' is not recognized as the name of a cmdlet, fu nction, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:99 + . 'D:\Program Files\Microsoft\Exchange Server\V14\\bin\RemoteExchange.ps1'; C onnect-ExchangeServer <<<< -auto + CategoryInfo : ObjectNotFound: (Connect-ExchangeServer:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException PS C:\Users\administrator.DAL\Desktop>

I'm assuming this is SP1...Check to see if you have all these scripts in your bin folder and if not copy them there from the install media under \setup\serverroles\common: CommonConnectFunctions.ps1 CommonConnectFunctions.strings.psd1 Connect-ExchangeServer-help.xml ConnectFunctions.ps1 ConnectFunctions.strings.psd1 RemoteExchange.ps1 RemoteExchange.strings.psd1 Mike Pfeiffer | blog: mikepfeiffer.net | twitter: @mike_pfeiffer

Thanks that worked to get rid of the error messags, but when I try to run a command I still get this error: Welcome to the Exchange Management Shell! Full list of cmdlets: Get-Command Only Exchange cmdlets: Get-ExCommand Cmdlets that match a specific string: Help *<string>* Get general help: Help Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -? Show quick reference guide: QuickRef Exchange team blog: Get-ExBlog Show full output for a command: <command> | Format-List Tip of the day #25: One benefit of the Exchange Management Shell is that cmdlets can output objects to the console. You can then manipulate this output and organize it in interesting ways. For example, to get a quick view in tabular format, use Format-Table: Get-Mailbox | Format-Table Name,Database,RulesQuota VERBOSE: Connecting to VERBOSE: Connected to . [PS] C:\Users\administrator.DAL\Desktop>Get-OABVirtualDirectory -Identity "48688B16ESV1\OAB (Default Web Site)" -Exte rnalURL A positional parameter cannot be found that accepts argument '-ExternalURL'. + CategoryInfo : InvalidArgument: (:) [Get-OabVirtualDirectory], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Get-OabVirtualDirectory [PS] C:\Users\administrator.DAL\Desktop>

Thanks that worked to get rid of the error messags, but when I try to run a command I still get this error: [PS] C:\Users\administrator.DAL\Desktop>Get-OABVirtualDirectory -Identity "48688B16ESV1\OAB (Default Web Site)" -Exte rnalURL A positional parameter cannot be found that accepts argument '-ExternalURL'. + CategoryInfo : InvalidArgument: (:) [Get-OabVirtualDirectory], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Get-OabVirtualDirectory [PS] C:\Users\administrator.DAL\Desktop> Hi ABMondrey, You enter the cmdlet Get-OABVirtualDirectory -Identity "48688B16ESV1\OAB (Default Web Site)" -ExternalURL in the EMS manually? Can you just run the Get-OABVirtualDirectory? From the Technet, there is no parameter ExternalURL when you run the cmdlet: Get-OABVirtualDirectory http://technet.microsoft.com/en-us/library/aa997926.aspxPlease 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.