Re: Exchange 2000 containers (Fields) not showing up in active directory!!

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 08/22/04 

Date: Sun, 22 Aug 2004 16:23:57 -0400

Don't need to log on with a domain admin ID. Could use runas or cpau to fire up
esm or ADUC or run scripts in alternate security context. Far more secure than
logging interactively into servers. Also, I would say that delegation of
exchange should be done, there is a chapter in the up and coming Windows Server
2003 Cookbook that has a recipe and recommendations on it.

   joe 

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Oli Restorick [MVP] wrote:
> Hi Joe
> 
> While I agree with you, I think it's also important to mention that it's not 
> a security best practice to log in as a domain admin on a workstation.  I'd 
> prefer to see people doing all user management from a domain controller than 
> using a domain admin account outside of a secure server room/datacentre.
> 
> Of course, the proper balance is to use the delegation of control wizard to 
> allow creation of regular accounts and/or using the runas feature to elevate 
> as required.
> 
> Regards
> 
> Oli
> 
> 
> "Joe Richards [MVP]" <humorexpress@hotmail.com> wrote in message 
> news:%230uy5A5hEHA.244@TK2MSFTNGP10.phx.gbl...
> 
>>My recommendation though is to NOT install the exchange tools on your 
>>domain controllers. Install it on your workstations, you shouldn't really 
>>be managing users directly from domain controllers, it is a security best 
>>practice to log directly into servers as little as possible.
>>
>>--
>>Joe Richards Microsoft MVP Windows Server Directory Services
>>www.joeware.net
>>
>>
>>
>>Cary Shultz [A.D. MVP] wrote:
>>
>>>Waz up, James?
>>>
>>>Sorry!  Feeling a little old tonight so I thought....
>>>
>>>Anyway, as the others have suggested you are seeing everything correctly. 
>>>I
>>>am sure that this is a bit limiting.  Here is how to resolve this problem 
>>>in
>>>a bit more detail:
>>>
>>>On all of your Domain Controllers you need to drop in the Exchange 2000
>>>Server CD.  You are going to do a custom installation and you are going 
>>>to
>>>install the Exchange Server Manager ( or whatever it is actually 
>>>called ).
>>>
>>>Let that install.  It should take but a few moments to do this.  Next, 
>>>and
>>>this is important, install the Exchange 2000 Service Pack level that your
>>>Exchange Server have ( so, if your Exchange Server is at SP3 then install
>>>SP3 on your Domain Controllers ).
>>>
>>>Repeat this on all of your Domain Controllers.
>>>
>>>You are now done.
>>>
>>>When you install SP4 on your Exchange Server ( once it comes out ) then
>>>install it on your Domain Controllers.  It is important to keep this at 
>>>the
>>>same SP level.
>>>
>>>Now, to see the Exchange related fields you will need to make sure that 
>>>you
>>>enable the Advanced View ( which you will need to do each and every time 
>>>you
>>>open this up ).  Also, if you have any shortcuts on your desktop then you
>>>might want to replace the one from the Admin Tools with the one from the
>>>Exchange Server.
>>>
>>>Actually, I would ask you why you are doing this on your Domain 
>>>Controllers
>>>as you really should be doing all of your Admin work from a workstation (
>>>similar to the way you do things in Novell ).  However, I will say that I 
>>>do
>>>this as well.  If you also have Terminal Services in Remote Admin Mode 
>>>then
>>>I would suggest that you log on remotely after you do this and update any
>>>shortcuts that you might have so that you are using the correct ADUC.....
>>>
>>>HTH,
>>>
>>>Cary
>>>
>>>
>>>"James Mullins" <texasviper@cox.net> wrote in message
>>>news:73b001c483bd$65a1d9e0$a601280a@phx.gbl...
>>>
>>>
>>>>When I open active directory on any of the Windows 2000
>>>>domain controllers except the exchange 2000 server I do
>>>>not see the exchange fields. Also the exchange 2000 e-mail
>>>>addresses are not in the LDAP database. Is there a way to
>>>>fix this? I think it might have something to do with the
>>>>forest prep on the AD.
>>>>
>>>
>>>
>

Relevant Pages

  • Re: Exchange 2000 System Attendant not starting
    ... You say you promoted Windows 2003 Domain Controllers but you did not mention whether your AD is 2003? ... If you run ADPREP while Exchange 2000 is present you could have issues, ... > "Brian Hammer" wrote in> message ... The server that is running exchange has also>> always ...
    (microsoft.public.exchange.admin)
  • Re: Exchange breaks connetion with Domain Controller
    ... that you are running Exchange 2003 with Active Directory 2003. ... that you can ping the DCs from the Exchange server. ... those on the Exchange server and domain controllers. ...
    (microsoft.public.exchange.admin)
  • RE: LSASS 100% Randomly
    ... You can try to move the global catalog role to your other domain controller ... > We're experiencing hangs on one of our Domain Controllers on a regular basis ... > The Server is a Windows2000 Active Directory, ... > We also have an Exchange 2000 Server in this site. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Problem
    ... server are pointed to the same DNS server for primary DNS ... On the domain controllers from sites and services delete all connection ... On exchange server run ipconfig /flushdns & ipconfig /registerdns. ...
    (microsoft.public.win2000.active_directory)
  • Re: New Exchange 2000 server wont join existing Ex 5.5 Organization
    ... account as the exchange administrator. ... When we specified the local domain admin account, ... > It sounds like there are still remnant of a previous install in the AD- ... >> to initially install an Exchange server on a regular member server to ...
    (microsoft.public.exchange2000.setup.installation)