I am currently installing Exchange 2003 on my first upgraded server in my
domain. I have progressed through the installation with no errors, but after
installing the Active Directory Connector, and run the ADC tool, a script
window displays and Reads:

Access is denied

Facility: Win32
ID No: c0070005
Microsoft Active Directory Connector Management

Does anyone have an idea as to what is causing this, or if there is a work
around?

Re: Exchange Active Directory Connector Management - Access Denied by Jeremy

Jeremy
Fri Mar 11 18:17:18 CST 2005

I believe the ADC is only for connecting Exchange 5.5 to Active Directory
and is geared towards enabling Exchange 5.5 to Exchange 2000/2003 migration.
Exchange 2003 does not need the ADC.


"Mike" <Mike@discussions.microsoft.com> wrote in message
news:8CA4CA2F-8494-4C53-AB0D-6F876452FA28@microsoft.com...
> I am currently installing Exchange 2003 on my first upgraded server in my
> domain. I have progressed through the installation with no errors, but
after
> installing the Active Directory Connector, and run the ADC tool, a script
> window displays and Reads:
>
> Access is denied
>
> Facility: Win32
> ID No: c0070005
> Microsoft Active Directory Connector Management
>
> Does anyone have an idea as to what is causing this, or if there is a work
> around?



Re: Exchange Active Directory Connector Management - Access Denied by Santhosh

Santhosh
Fri Mar 25 12:39:42 CST 2005

What are you trying to do? Creating a new connection agreement between Ex
5.5 and AD?

--
Santhosh Sivarajan
MCSE(W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),CCNA,Network+
Houston, TX



"Mike" <Mike@discussions.microsoft.com> wrote in message
news:8CA4CA2F-8494-4C53-AB0D-6F876452FA28@microsoft.com...
>I am currently installing Exchange 2003 on my first upgraded server in my
> domain. I have progressed through the installation with no errors, but
> after
> installing the Active Directory Connector, and run the ADC tool, a script
> window displays and Reads:
>
> Access is denied
>
> Facility: Win32
> ID No: c0070005
> Microsoft Active Directory Connector Management
>
> Does anyone have an idea as to what is causing this, or if there is a work
> around?