?
Solved

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

Posted on 2013-11-28
5
Medium Priority
?
407 Views
Last Modified: 2014-06-06
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
0
Comment
Question by:wizel
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 39683997
This has nothing to do with the RGC or co-existence, something is stopping the tools from accessing Exchange. Do you have a proxy in place on the network? If so that is the most likely cause, as both EMS and EMC make calls to the web server, and a proxy can get in the way.

Simon.
0
 

Author Comment

by:wizel
ID: 39684029
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
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39684061
You either need to disable the proxy for the server or put exclusions in place. Depends how the proxy is configured.

Simon.
0
 

Author Comment

by:wizel
ID: 39684212
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?
0
 

Author Comment

by:wizel
ID: 39684260
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.
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question