Dear All, I've just installed Exchange 2010 SP1 CAS into my 2007 environment and am testing things before continuing with the install of the other roles. When I run the Test-OutlookWebServices cmdlet I'm getting errors such as this: RunspaceId : 4a476e8e-dab3-4cf2-9c18-87fe149f82c5 Id : 1019 Type : Information Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://ex2010.mydomain.co.uk/Autodiscover/Autodiscover.xml. RunspaceId : 4a476e8e-dab3-4cf2-9c18-87fe149f82c5 Id : 1013 Type : Error Message : When contacting https://ex2010.mydomain.co.uk/Autodiscover/Autodiscover.xml received the error The remote server returned an error: (407) Proxy Authentication Required. RunspaceId : 4a476e8e-dab3-4cf2-9c18-87fe149f82c5 Id : 1023 Type : Error Message : The Autodiscover service couldn't be contacted. There is a 3rd party certificate installed with IIS allocated as a service so that's not it. I've tried navigating to the URL https://ex2010.mydomain.co.uk/Autodiscover/Autodiscover.xml and, following the normal Exchange prompts for credentials, it returns some XML - which tells me that it's able to get to the URL without proxy authentication. Any ideas what could be wrong? Many thanks. Chris

I beleive that the term "proxy" in the error code is misleading you and that it's saying that the test couldn't authenticate successfully. I'm not sure whether or not it's required for that cmdlet, but did you create the EXTEST account using the New-TestCasConnectivityUser.ps1 script loacated in the Scripts folder under where you installed Exchange?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, No, I haven't run the New-TestCasConnectivityUser.ps1 script - before I do could you tell me what it does please? Many thanks. Chris

It creates a test user named extest_ followed by some GUID that's used by several Test- cmdlets, especially if you use SCOM, but useful even if you don't.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Is the creation of this extest_GUID user a pre-requisite for the Test-OutlookWebServices cmdlet? The reason I ask is that when I ran it initially I told it to use my mailbox (which still resides on the Exchange 2007 server) as the 'Identity'. I also tried running it whilst specifying both my mailbox and the Exchange 2007 server as parameters and the same errors came back - except the URLs in the errors referred to the Exchange 2007 server rather than the 2010 one obviously. What I really need to know is should I continue installing the remaining roles (Hub, Mailbox and UM) and migrate some mailboxes over before worrying about this or is it something that I should try to fix now? Many thanks. Chris

You may not need the mailbox but it won't hurt anything to create it. But if you don't have a mailbox server yet, then it's too early to run it! The other roles will work fine without Autodiscover. Maybe Autodiscover will work better when you have all the roles installed. It would have helped if you had disclosed that you hadn't installed the Mailbox role yet. Autodiscover won't work on mailboxes that are on Exchange 2003, so maybe that's your problem.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Ed, Apologies if my initial post wasn't clear enough: 'I've just installed Exchange 2010 SP1 CAS into my 2007 environment and am testing things before continuing with the install of the other roles. When I run the Test-OutlookWebServices cmdlet I'm getting errors such as this:' I have an existing 2007 environment with CAS, Mailbox, Hub and UM running fine - the 2010 server currently only has the CAS role installed. Am I to understand that I'll need the 2010 Mailbox role before the test cmdlet will work? Many thanks. Chris

Does anyone else know if this is the case? Any suggestions most appreciated. Happy Christmas!

You should not need the mailbox role for the CAS to work. I can't say whether the Test-OutlookWebServices cmdlet will work, though!Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Please try to disable the loopback check and then test to see if the issue persists. To set the DisableLoopbackCheck registry key, follow these steps: Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa Right-click Lsa, point to New, and then click DWORD Value. Type DisableLoopbackCheck, and then press ENTER. Right-click DisableLoopbackCheck, and then click Modify. In the Value data box, type 1, and then click OK. Quit Registry Editor, and then restart your computer. 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. Thanks Gen Lin-MSFT

Hi, I have tried adding the above registry key but I'm afraid it hasn't made any difference. I'm still seeing the 1013 error: "The remote server returned an error: (407) Proxy Authentication Required." The only thing that might be slightly different with my setup is that I've had to add both my internal domain and the domain of my certificate provider to the WinHTTP proxy bypass list (this was to solve a problem with the server accessing the 3rd party's Certificate Revocation List). The certificate itself is a SAN one with several alternative names but the EMC says that it's valid so I don't think that's the problem. I've also been attempting to access OWA and the redirection appears to be working correctly. Am I worrying about nothing or is this something I need to persue before adding the Hub, MBX and UM roles? Many thanks. Chris

I've just tried running the Test-OutlookWebServices from my existing Exchange 2007 server but pointed it at the Exchange 2010 CAS server and it contacted it and redirected back to the Exchange 2007 server correctly. From the Exchange 2007 server I ran: Test-OutlookWebServices -ClientAccessServer EXCHANGE2010CAS -Identity "Chris" Where the mailbox for "Chris" still lives on the Exchange 2007 server. I'm going to press on with the rest of the Exchange 2010 install and see what happens.

Hi Chris, I'm having same problem. How did it go?