windows server 2008, ex2010 level : rollup 3v3 roles : no edge, no UM exchangepath : C:\Program Files\Microsoft\Exchange Server\V14\ WinRM II Extension installed, WinRM Quickconfig done anonymous auth op iis/powershell : disabled Windows firewall : off VERBOSE: Connecting to EX2010T.holding.local [ex2010t.holding.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service d id not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to EX2010T.holding.local [ex2010t.holding.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service d id not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to EX2010T.holding.local [ex2010t.holding.local] Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service d id not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionOpenFailed Failed to connect to an Exchange server in the current site. Enter the server FQDN where you want to connect.: VERBOSE: Connecting to New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value "http:///powershell?serializationLevel=Full;ExchClientVer=14.1.218.15" to type "System.Uri". Error: "In valid URI: The hostname could not be parsed." At line:1 char:29 + New-PSSession -ConnectionURI <<<< "$connectionUri" -ConfigurationName Microsoft.Exchange -SessionOption $so + CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand

Error message when you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "HTTP server error status (500)" http://support.microsoft.com/kb/2027063 Besides, please go through the following steps: 1. Please verify if all GCs in the network work as well. You can use DCdiag. 2. Please check network Binding order. 3. Please verify if IPV6 is enabled. Regards, Xiu Please 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.

i checked, the installpath is correct. don't understand 1 and 2. Can you put a little bit more flesh to the steps, please? i've read http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx regards, wim

Hi Wim, Is this test lab? did you reinstall exchange 2010 and after that you are facing this issue? what the event generating when opening EMC or EMS?

Hi Wim, Is this test lab? did you reinstall exchange 2010 and after that you are facing this issue? what the event generating when opening EMC or EMS? exchangepath : C:\Program Files\Microsoft\Exchange Server\V14\ WinRM II Extension (re)installed, WinRM Quickconfig done anonymous auth op iis/powershell : disabled kerbauth : local / native Windows firewall : off get-user : the term is not recognized as a command i've read http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx ssl disabled on powershell vir dir it is not a test lab. the error comes when i start the exchange management shell but the console doesn't start either. regards, wim.

Hi, Please try to run DCdiag from DC side and to see if all the DC work as normal. We may need to install Windows Support Tools first. Then please try to run DCdiag from a command prompt and wait for the output. Please check the binding order of network adapt. 1.Click Start, click Run, type ncpa.cpl , and then click OK. 2. Press Alt+N to display the Advanced menu. 3. Navigate to Proider Order to check the network adapt binding order. Regards, Xiu Please 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.

hi Xiu, ok. I can do those commands but I don't know what settings are correct. So still in the fog. I log onto the exchange 2010 machine through RDP en try work there 'locally' in the EMS. i'v got still a ex2007 working. I think i'm gonna remove the ex2010 server from my domain. Although this procedure is undocumented and prob also a pain in the butt. Please one of you all, send me the magic :-) kind regards, wim.

Hi, Could you have a try to use EMC on Exchange Server, not via RDP? XiuPlease 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.

I logged on locally onto the machine. no difference.

Hi, Then please try to run DCdiag to see if all the test will be passed. Domain Controller Diagnostics Tool (dcdiag.exe) http://technet.microsoft.com/en-us/library/cc776854(WS.10).aspx Regards, Xiu

i did the dcdiag from the ex2010 machine. c:\Users\holdingadmin>dcdiag /s:ad1-holding irectory Server Diagnosis erforming initial setup: * Identified AD Forest. Done gathering initial info. oing initial required tests Testing server: Default-First-Site-Name\AD1-HOLDING Starting test: Connectivity ......................... AD1-HOLDING passed test Connectivity oing primary tests Testing server: Default-First-Site-Name\AD1-HOLDING Starting test: Advertising ......................... AD1-HOLDING passed test Advertising Starting test: FrsEvent ......................... AD1-HOLDING passed test FrsEvent Starting test: DFSREvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... AD1-HOLDING failed test DFSREvent Starting test: SysVolCheck ......................... AD1-HOLDING passed test SysVolCheck Starting test: KccEvent ......................... AD1-HOLDING passed test KccEvent Starting test: KnowsOfRoleHolders ......................... AD1-HOLDING passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... AD1-HOLDING passed test MachineAccount Starting test: NCSecDesc Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=ForestDnsZones,DC=holding,DC=local Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=DomainDnsZones,DC=holding,DC=local ......................... AD1-HOLDING failed test NCSecDesc Starting test: NetLogons ......................... AD1-HOLDING passed test NetLogons Starting test: ObjectsReplicated ......................... AD1-HOLDING passed test ObjectsReplicated Starting test: Replications ......................... AD1-HOLDING passed test Replications Starting test: RidManager ......................... AD1-HOLDING passed test RidManager Starting test: Services Invalid service type: RpcSs on AD1-HOLDING, current value WIN32_OWN_PROCESS, expected value WIN32_SHARE_PROCESS ......................... AD1-HOLDING failed test Services Starting test: SystemLog An Error Event occurred. EventID: 0xC000001B Time Generated: 07/12/2011 09:01:09 (Event String (event log = System) could not be retrieved, error 0x7e) An Warning Event occurred. EventID: 0x000003FC Time Generated: 07/12/2011 09:04:12 (Event String (event log = System) could not be retrieved, error 0x7e) ......................... AD1-HOLDING failed test SystemLog Starting test: VerifyReferences ......................... AD1-HOLDING passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : holding Starting test: CheckSDRefDom ......................... holding passed test CheckSDRefDom Starting test: CrossRefValidation ......................... holding passed test CrossRefValidation Running enterprise tests on : holding.local Starting test: LocatorCheck ......................... holding.local passed test LocatorCheck Starting test: Intersite ......................... holding.local passed test Intersite

Hi, Make sure that you can ping between the DCs with IP address, computer name and FQDN. Also make sure that no firewall is blocking AD replication traffic. Please check if the sysvol and netlogon folder exist and if you can access them. Check in AD sites and services, that all DCs are listed and that the sites are using the correct subnet and that the replication topology is created either automatically or done manual for your needs. Please correct NCSecDesc error via the article below: Dcdiag fails for NCSecDesc test on Windows 2008 Domain Controllers http://support.microsoft.com/kb/967482 If we still have failed in DCdiag report, then I recommend you to post the DC issue in Windows Server forum to correct the DC issue first. Windows Server- Directory Service http://social.technet.microsoft.com/Forums/en-US/winserverDS/threads Regards, Xiu