Avatar of wizel
wizel
Flag for Germany asked on

can't open EMC and EMS - Exhange2010 installed on Server 2012 STD, swing server Migration from Exchange 2003

Hi,

I installed the Exchange 2010 from SP3 setup on a Server 2012 STD. Server is Memberserver of the domain. During setup I chose the existing Exchange 2003 so there is a routing connector.

The problem is since installation.

When i try to connect the EMC i get an error (see screen, in german)
....'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.3 (Build 123.4)

The only way to contact the Exchange is with windows power shell:
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010

I tried some solutions but nothing helps.
screen.JPG
ExchangeWindows Server 2012Microsoft IIS Web Server

Avatar of undefined
Last Comment
wizel

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Simon Butler (Sembee)

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
wizel

ASKER
Hello simon,
yes there is a proxy in the local network for internet access. The proxy is also the gateway ip for all devices. What should i do now?

Thanks
Simon Butler (Sembee)

You either need to disable the proxy for the server or put exclusions in place. Depends how the proxy is configured.

Simon.
wizel

ASKER
Before installing exchange I set the proxy adress in netsh to get windows updates:
Netsh winhttp import proxy source=ie

When i run 'Netsh winhttp show proxy' now the settings are:
Proxyserver: x.x.x.x:8080
<local>

Do you mean this caused the problem?
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
wizel

ASKER
Simon,

'Netsh winhttp reset proxy' solved my problem, now I have access to both EMC and EMS.

Oh man, the proxy - I did not remember at this setting.

Thank you for the tip.