|
|
Cannot administer exchange from 2003 domain controller
-
04-13-2007, 7:35 |
-
chard-fi
-
-
-
Joined on 04-13-2007
-
-
Posts 2
-
-
|
Cannot administer exchange from 2003 domain controller
Hi,
I'm trying to install exchange server 2003 within my organisation. I have two servers, one domain controller and another to be the exchange server. both machines run server 2k3 r2 and are fresh installs. The domain controller is all set up ready to go and netdiag and dcdiag report no problems from either machine. Howerver, dispite running forest prep and domain prep on the DC after i instelled exchange on the other member server i still cannot change any of the exchange atributes on the DC. I can on the exchange server and all looks great from here but i was sure that i should be able to make changes like mail enable accounts from the DC's as well?
Any thoughts?
|
|
-
04-13-2007, 8:26 |
-
NHobson
-
-

-
Joined on 07-20-2006
-
Dorset
-
Posts 17
-
-
|
Re: Cannot administer exchange from 2003 domain controller
You'll need to install the Exchange management tools on the DC in order to be able to do this. Run Exchange setup on the DC and install only the management tools. Don't forget to service pack the installation too. You could also just use terminal services to the Exchange server, etc.
Neil Hobson Exchange MVP http://www.msexchange.org/Neil_Hobson/
|
|
-
04-13-2007, 9:02 |
-
chard-fi
-
-
-
Joined on 04-13-2007
-
-
Posts 2
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Right.
Why is it thst i was able to administer the exchange atributes from any of the servers be it a DC or exchange server the last time i did this with a win 2k dc and a win 2k3 exchange server?
This whole situation is worrying me slightly.
|
|
-
04-13-2007, 11:47 |
-
nathanwinters
-
-

-
Joined on 07-09-2006
-
Croydon, UK
-
Posts 732
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hmm,
Most likely the Exchange System tools were installed.
This is perfectly normal behaviour, without ESM installed you don't get the update to ADUC so you can see the Exchange attributes.
Cheers
Nathan
Nathan Winters - MVP Exchange Server MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3. Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk
|
|
-
04-17-2007, 5:04 |
-
eddyvh
-
-
-
Joined on 04-17-2007
-
-
Posts 5
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hello,
I have the same problem, furthermore this little problems occurs also Our situation,
DC running windows 2000 (before exchange 2000 also) Exchange server 2003 running on windows 2003 standard edition Now just installed a second DC running 2003 R2 Domain replication works fine, Cannot administer exchange from win2k3R2 And the real problem : When the old DC (win2k) goes down, users can no longer login to the exchange server,
Anybody any idea of what is going on..? I checked AD for all dns records (OK) AD Services and sites (new DC ntds settings are fine) ADSIE on new DC are showing fine Created an extra RUS on the exchange to point to the new DC (was not created automaticly) Nothing helps
tnx in advanse for any suggestion.
Eddy
|
|
-
-
04-17-2007, 15:29 |
-
Greg T [MSFT]
-
-
-
Joined on 08-09-2006
-
-
Posts 86
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Is the new DC enabled as a Global Catalog....?
Greg
|
|
-
04-18-2007, 2:39 |
-
eddyvh
-
-
-
Joined on 04-17-2007
-
-
Posts 5
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Greg,
No, the new DC is not configured as Global Catalog Server I have found in exchange documentation that the most of the services from exchange use the global catalog server.
but then this sticky question pops up, may you have more than one Global Catalog server within one domain .? Eddy
|
|
-
04-18-2007, 2:47 |
-
eddyvh
-
-
-
Joined on 04-17-2007
-
-
Posts 5
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Nathan,
Directory access tab shows the following: oldserver config(auto) newserver DC(auto) oldserver DC(auto) oldserver GC(auto)
Offline adress list (only the old server shown here) Should i create a new offline adres list for the new DC also..??
The Rus are configured like this: RUS(domain) oldserver RUS(domain) newserver (have i placed manually, was not created automaticly) RUS(enterprise) oldserver
For the enterprise the only server configured is the old one but i dont have the possibility to create a second enterprise RUS, exchange is telling me there can only be one
Eddy
|
|
-
04-18-2007, 2:53 |
-
nathanwinters
-
-

-
Joined on 07-09-2006
-
Croydon, UK
-
Posts 732
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hi,
Regards the GC issue, yes you can have more than one GC per domain.
In fact, for most setups where bandwidth is not an issue then all DCs should be GCs.
How many domains and how many sites have you got? If it is just one then make all your boxes GCs.
Cheers
Nathan
Regards the other question, sounds like that is OK. Greg will probably add something when he take a look. I will have a check online and get back to you tonight (with luck)
Cheers
Nathan
Nathan Winters - MVP Exchange Server MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3. Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk
|
|
-
04-18-2007, 4:53 |
-
Greg T [MSFT]
-
-
-
Joined on 08-09-2006
-
-
Posts 86
-
-
|
Re: Cannot administer exchange from 2003 domain controller
As Nathan says, in a simple environment like this, make all the domain contollers GC's - as you have seen, Exchange doesn't work when it can't find a GC.....GC's are very very important to Exchange.
An interesting aside and often mis-understood point in the co-existence of GC and Infrastructure Master FSMOP role placement - if you only have one domain the IM role is irrelevant. In a multi domain model, where ALL DC's are GC's then it also is irrelvant.... It's only in a multi domain environment where only some of the DC's are GC's do you need to seperate them.
OAB - don't need to change the default, you just add a replica of the OAB Public Folder to each server. Only one server needs to generate the OAB. You can add extra Domain RUS's but for just a couple of servers I wouldn't bother. AD replication will be under 5 mins if they are in the same site anyway, so the extra RUS isn't really necessary. And yes, only one Enterprise RUS.
HTH
Greg
|
|
-
04-18-2007, 5:17 |
-
nathanwinters
-
-

-
Joined on 07-09-2006
-
Croydon, UK
-
Posts 732
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Thanks Greg
Nathan Winters - MVP Exchange Server MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3. Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk
|
|
-
04-18-2007, 9:59 |
-
eddyvh
-
-
-
Joined on 04-17-2007
-
-
Posts 5
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hey All,
I have configured the new DC as Global Catalog also. Under exchange i can see now 2 GC(auto) so this looks good, Will test this new settings this week-end, unaible to shut down the server during working days, so i will inform you guys on monday to see whether al works fine now,
and for now , Thank you both verry much for helping me out here..,
Eddy
|
|
-
04-19-2007, 6:48 |
-
nathanwinters
-
-

-
Joined on 07-09-2006
-
Croydon, UK
-
Posts 732
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hi,
No problem, let us know how it goes.
Cheers
Nathan
Nathan Winters - MVP Exchange Server MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3. Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk
|
|
-
05-02-2007, 1:57 |
-
eddyvh
-
-
-
Joined on 04-17-2007
-
-
Posts 5
-
-
|
Re: Cannot administer exchange from 2003 domain controller
Hi Guys,
Sorry for the delay, something else was come up in the past weekend, so i have made the tests yesterday (yeach i know, on labour day ..)
Concerning the tests, i put down the DC1, and after 3-4 minutes the exchange as working like it should again, why he needed this little time out..? Noticed also something else that i found weird.. Both of the DC's are also DNS Servers (AD Integrated) The exchange ip config is set to both servers with the old DC als favourite, @ the moment i changed the priority of dns to the new DC the exchange was running faster in responses, so i make further tests in command modus, Did a nslookup : everthing looks fine, changed priority to first DC as dns server, redid the same nslookup : Failed, 2times, did not see any respons from the second dns server, like he was not requested or something like that..
Is there some reason that exchange cannot handle 2 dns servers..??? or do i have to look to the OS for this matter None of my other servers/computers seem to have a problem with this
I have seen however that while the DC1 was down the exchange server still wanted to LDAP bind to this server, LDAP Bind was unsuccessful on directory ddymsesrv01.dedijcker.be for distinguished name ''. Directory returned error:[0x51] Server Down.
I restarted the exchange also and when he came up he did an LDAP bind to the DC2 Opening LDAP session to directory ddysrvdc02.dedijcker.be on port 389. Microsoft Exchange System Attendant is binding to domain controller 'ddysrvdc02.dedijcker.be'.
Could this time-out he got coming from the fact that the exchaneg was not yet restarted after the change of making the DC2 also a GC .?
Also noticed that exchange information staore is limited to 18GB, is there some way to overide this (licence, software..) now already using 13GB
Tnx for the advice and again sorry for the late reaction Eddy
|
|
Page 1 of 2 (16 items)
1
|
|