Solved

EX2013 problem with AD

Posted on 2016-10-31
13
61 Views
Last Modified: 2016-11-02
Hi Experts,

my EX2013 server cannot connect to AD properly.
I always get the Error:

Unable to find a default server with Active Directory Web Service running

Ex2013 is installed on WIN2012R2
The DCs are WIN2008

Do you have any idea ?
0
Comment
Question by:Eprs_Admin
[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
13 Comments
 
LVL 30

Expert Comment

by:Scott C
ID: 41867075
Take a look at this article.

It looks like you may not have Active Directory Web Service (ADWS) installed.
0
 

Author Comment

by:Eprs_Admin
ID: 41867081
it is an DC with WIN2008
0
 
LVL 15

Expert Comment

by:Jason Crawford
ID: 41867152
Is the ADWS service running on your DC?
0
Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

 
LVL 2

Expert Comment

by:Mikhail Sartaev
ID: 41867595
You must install adws to 2008 DC for powershell cmdlets.
https://www.microsoft.com/en-us/download/details.aspx?id=2852
0
 

Author Comment

by:Eprs_Admin
ID: 41869679
I think not, which service is it exactly ?
It must be installed on my DC or on all DCs ?
0
 
LVL 2

Expert Comment

by:Mikhail Sartaev
ID: 41869718
On all DC which exchange connects
0
 

Author Comment

by:Eprs_Admin
ID: 41869723
I have got the advice to just install a server win2012r2 and promote em to AD.
0
 
LVL 2

Accepted Solution

by:
Mikhail Sartaev earned 500 total points
ID: 41869732
Good, but you exchange must connect only to this DC then run ad cmdlets.
1
 

Author Comment

by:Eprs_Admin
ID: 41869734
ok I see.
I will give it a try, because in the future we have to use the new DC
0
 

Author Comment

by:Eprs_Admin
ID: 41869956
The new DC is installed.
From the GUI I have the same issue, cannot find all AD users.

From the the SHELL it works when I check a user with GET-ADUSER user01

Why not from the GUI ?
0
 
LVL 2

Expert Comment

by:Mikhail Sartaev
ID: 41869960
Because from GUI you can't choose DC.
0
 

Author Comment

by:Eprs_Admin
ID: 41869970
in SHELL I also not choose any AD, I just type the command.

How can I solve it ?
Because like this, the GUI has no sense yet.
0
 

Author Closing Comment

by:Eprs_Admin
ID: 41870110
With the new DC it works.
0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

739 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