You should not be able to install a 2003 backend in an administrative group where you have 2000 front ends. You should be able to install a 2003 front-end in an administrative group where there are other 2000 front-ends.
' function returns true if an error occurred
' isFrontEnd, a byref variable, contains the answer to the question
Function isFrontEndServer (ByVal strAdministrativeGroupName, _
ByVal strServerName, _
ByVal strOrganizationDN, _
ByRef isFrontEnd)
Dim objContainer
Dim strConnString
On Error Resume Next
isFrontEndServer = False
strConnString = "LDAP://CN=" & strServerName & _
",CN=Servers,CN=" & strAdministrativeGroupName & _
",CN=Administrative Groups," & strOrganizationDN
Set objContainer = GetObject (strConnString)
If Err.Number Then
isFrontEndServer = True
Exit Function
End if
isFrontEnd = CBool (objContainer.Get ("serverRole"))
Set objContainer = Nothing
End Function
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Tom Kern
Sent: Tuesday, December 20, 2005 8:53 AM
To: activedirectory
Subject: [ActiveDir] exchange 2k3 install(OT)
If i run setup for exchange 2k3 in a domain with a exchange 2k FE server will that be enough to stop the setup on exchange 2k3?
I can see that it checks for the existance of a FE server and i know exchange 2k can't be a front end for a exchange 2k3 backend but i didn't know that was a deal breaker for set up to stop.
Also, does anyone know of the name of attrib in AD that setup checks to determine if a server is a FE?
Thanks
thanks.
I assume a FE server can be a front end to any exchange server in the entire ORG regardless of domain or admin group but Exchange setup only checks for FE's in its Admin group to see what verison of exchange the FE is running?
Thanks again
On12/20/05, Michael B. Smith <[EMAIL PROTECTED]> wrote:
