Anonymous_User Absent Member.
Absent Member.
224 views

AD driver upgrade from Exchange 2003 to 2010


Hello,

A customer is upgrading their Exchange from 2003 to 2010. Their AD is
still running on a Windows Server 2003, but the Exchange 2010 is now
running on a Windows Server 2008 R2.

The remote loader is running on the domain controller(AD), but needs the
Exchange 2010 System Management Tools to be able to integrate with
Exchange 2010. It is not possible to install Exchange 2010 System
Management Tools on the Windows Server 2003. It's just not supported.

So the questions is. How do i fix this? Is the only possibility to
install a new Windows Server 2008 R2, install the remote loader and
Exchange 2010 System Management Tools on that, or is there so sort of
fix, that enables me to get it to work with the current Windows Server
2003?

Jacob


--
jacmarpet
------------------------------------------------------------------------
jacmarpet's Profile: https://forums.netiq.com/member.php?userid=415
View this thread: https://forums.netiq.com/showthread.php?t=46357

Labels (1)
0 Likes
7 Replies
Knowledge Partner
Knowledge Partner

Re: AD driver upgrade from Exchange 2003 to 2010

On 12/11/2012 4:24 AM, jacmarpet wrote:
>
> Hello,
>
> A customer is upgrading their Exchange from 2003 to 2010. Their AD is
> still running on a Windows Server 2003, but the Exchange 2010 is now
> running on a Windows Server 2008 R2.
>
> The remote loader is running on the domain controller(AD), but needs the
> Exchange 2010 System Management Tools to be able to integrate with
> Exchange 2010. It is not possible to install Exchange 2010 System
> Management Tools on the Windows Server 2003. It's just not supported.


Move the remote loader to a Win 2008 server, since that is a Microsoft
requirement. Not much you can do about it except complain to Microsoft.


> So the questions is. How do i fix this? Is the only possibility to
> install a new Windows Server 2008 R2, install the remote loader and
> Exchange 2010 System Management Tools on that, or is there so sort of
> fix, that enables me to get it to work with the current Windows Server
> 2003?
>
> Jacob
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD driver upgrade from Exchange 2003 to 2010

On 11.12.2012 10:24, jacmarpet wrote:
>
> Hello,
>
> A customer is upgrading their Exchange from 2003 to 2010. Their AD is
> still running on a Windows Server 2003, but the Exchange 2010 is now
> running on a Windows Server 2008 R2.
>
> The remote loader is running on the domain controller(AD), but needs the
> Exchange 2010 System Management Tools to be able to integrate with
> Exchange 2010. It is not possible to install Exchange 2010 System
> Management Tools on the Windows Server 2003. It's just not supported.
>
> So the questions is. How do i fix this? Is the only possibility to
> install a new Windows Server 2008 R2, install the remote loader and
> Exchange 2010 System Management Tools on that, or is there so sort of
> fix, that enables me to get it to work with the current Windows Server
> 2003?


There is no fix to get Exchange management tools working on server 2003.
Exchange 2010 is 64 bit only and although they existed, it it very rare
to find a 64 bit windows 2003 server, plus there are other software
dependencies that likely can't be met on a 2003 server

You have two options:

1. you can move the AD RL on a member server (running Windows 2008 R2)
with Exchange 2010 System Management Tools installed on same box.

2. convince the customer to introduce a 2008 R2 domain controller and
add Exchange 2010 System Management Tools. Then move the AD RL to that box.

Note that NetIQ has a TID which details how to move the AD RL to another
sever.

http://www.novell.com/support/kb/doc.php?id=7000882


I'd suggest option 2, it's likely worth the fight to get the customer to
start moving off 2003 servers hosting AD.

In addition, if the 2003 Exchange logic does more than just provision
mailboxes, you may find yourself limited by the functionality offered by
the built-in Exchange 2010 support.
0 Likes
Knowledge Partner
Knowledge Partner

Re: AD driver upgrade from Exchange 2003 to 2010

> In addition, if the 2003 Exchange logic does more than just provision
> mailboxes, you may find yourself limited by the functionality offered by
> the built-in Exchange 2010 support.


WHat specifically where you thinking of here Alex?

Does the 4.02 support for Exchange related powershell help make up for
these issues?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD driver upgrade from Exchange 2003 to 2010

On 11.12.2012 15:15, Geoffrey Carman wrote:
>> In addition, if the 2003 Exchange logic does more than just provision
>> mailboxes, you may find yourself limited by the functionality offered by
>> the built-in Exchange 2010 support.

>
> WHat specifically where you thinking of here Alex?


Just that with Exchange 2003, one could set all sorts of exchange
related attributes directly in AD and have this trigger actions in
Exchange. Some of these attributes are now stripped or ignored when
using the Exchange 2007/2010 driver option in the AD driver.

Even if not stripped/ignored, some of these attribute changes are
ignored by Exchange 2010 or are now insufficient (and should be done via
powershell instead).

So if they are doing anything more than just provisioning mailboxes,
it's likely they will encounter some other roadbumps along the way.

> Does the 4.02 support for Exchange related powershell help make up for
> these issues?


Yes it does, but there was no mention that the version of IDM in use
here had been upgraded, the IDM 4.02 AD driver requires 4.02 licensing.

Doesn't that mean that it's not possible to use the new Exchange related
powershell features with an older engine?
0 Likes
Knowledge Partner
Knowledge Partner

Re: AD driver upgrade from Exchange 2003 to 2010

On 12/11/2012 9:32 AM, Alex McHugh wrote:
> On 11.12.2012 15:15, Geoffrey Carman wrote:
>>> In addition, if the 2003 Exchange logic does more than just provision
>>> mailboxes, you may find yourself limited by the functionality offered by
>>> the built-in Exchange 2010 support.

>>
>> WHat specifically where you thinking of here Alex?

>
> Just that with Exchange 2003, one could set all sorts of exchange
> related attributes directly in AD and have this trigger actions in
> Exchange. Some of these attributes are now stripped or ignored when
> using the Exchange 2007/2010 driver option in the AD driver.


Thanks! That is a great example. I had not thought of that aspect.

> Even if not stripped/ignored, some of these attribute changes are
> ignored by Exchange 2010 or are now insufficient (and should be done via
> powershell instead).


>> Does the 4.02 support for Exchange related powershell help make up for
>> these issues?

>
> Yes it does, but there was no mention that the version of IDM in use
> here had been upgraded, the IDM 4.02 AD driver requires 4.02 licensing.
>
> Doesn't that mean that it's not possible to use the new Exchange related
> powershell features with an older engine?


I wonder. I recall that the driver init message talks about min
licensing, not necessarily min engine version. I have not tried, but do
wonder...

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD driver upgrade from Exchange 2003 to 2010

On 12/11/12 6:01 AM, Alex McHugh wrote:
> There is no fix to get Exchange management tools working on server 2003.
> Exchange 2010 is 64 bit only and although they existed, it it very rare
> to find a 64 bit windows 2003 server, plus there are other software
> dependencies that likely can't be met on a 2003 server


My 2 cents - Unlike Exchange 2007, Exchange 2010 is managed through
remote powershell and doesn't require exchange management tools to be
installed anywhere other than the exchange server. Any machine running
powershell 2.0 (which is available for W2K3) and configured for remoting
should be able to manage Exchange 2010.

That said, I have no idea if the AD driver is smart enough to make the
remote connection.

--
Shon
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD driver upgrade from Exchange 2003 to 2010


Thanks for the answers everyone!

We will use alexmchugh's proposal and attempt to convice the customer to
introduce a new 2008 R2 server. If they will agree to make it a DC we
don't know, but hopefully they will.

Again, thanks alot for the help!


--
jacmarpet
------------------------------------------------------------------------
jacmarpet's Profile: https://forums.netiq.com/member.php?userid=415
View this thread: https://forums.netiq.com/showthread.php?t=46357

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.