thanks carl. it's not really the software cost that's of concern as that's
already paid for. (in this case) it's more just ensuring the integration
approach (change mgmt) so that any transition is smooth and downtime, if
any, is minimized. also, the 2000 DC hardware is dated so upgrading their
OS presents a level of risk, that, if not required, may be simpler, if only
in the short run.
That said, It seems clear (at this point) like an upgrade of (at least one)
DC is required. I had received conflicting info prior. This is helpful
info.
thanks again for your comments.
byron
http://www.MSExchange.org/
You only have to upgrade one DC to 2003, but you will also have to buy new Windows 2003 CALs for all client computers.
It's pretty simple really. If you want the new features, you have to pay
for them. If the benefit doesn't justify the expense, then you do without.
Carl
-----Original Message----- From: Byron (Yahoo) [mailto:snail945@xxxxxxxxx] Sent: Tuesday, November 08, 2005 12:15 PM To: [ExchangeList] Subject: [exchangelist] Re: RPC over http
so in my case i'm in a tough spot because:
1. i have only 1 exch 2003 server (and client is too small to justify another) 2. both DCs are win2k sp4
So, it looks like the net/net is that we can't run rpc over http unless we upgrade the DCs to 2003 - provide for a 2003 global catalog.
do you see a simpler alternative than planning to upgrade the 2 DCs to Windows 2003? given the info provided.
thanks much-byron
----- Original Message ----- From: "Carl Houseman" <c.houseman@xxxxxxxxx>
To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
Sent: Monday, November 07, 2005 5:26 PM
Subject: [exchangelist] Re: RPC over http
One does not "make this E2K3 server a DC." without consequences.
http://support.microsoft.com/kb/822179 "Changing the role of a server after you install Exchange Server 2003 may result in loss of some Exchange functionality and is not supported. "
And preferably, one does not run Exchange on a DC at all, unless there's only one server or it's SBS.
-----Original Message----- From: Richard Kasslack [mailto:rkasslack@xxxxxxx] Sent: Monday, November 07, 2005 8:15 PM To: [ExchangeList] Subject: [exchangelist] Re: RPC over http
The only problem you'll have is authenticating the users. There is a change you have to make in the registry on the E2K3 server to tell it to authenticate itself and not pass on to other DCs.
There is an excellent paper at microsoft on how to do this, search RPC over HTTPS at microsoft.com.
You'll have to make this E2K3 server a DC.
You'll also have to make sure IIS is setup and configured on the E2K3 server with an SSL certificate.
Other than that, it works like a charm.
-----Original Message----- From: "Byron \(Yahoo\)" <snail945@xxxxxxxxx> Date: Mon, 7 Nov 2005 16:57:11 To:"[ExchangeList]" <exchangelist@xxxxxxxxxxxxx> Subject: [exchangelist] RPC over http
hello, question on rpc over http.
Current setup is as follows:
- 2 Windows 2000 DCs sp4 (also GC/DNS) Active Directory servers - 1 separate Exchange 2003 server (sp1) running on Windows 2003 sp1
Would like to enable rpc over http/s for outlook 2003 clients to access from
remote. is this possible in this setup, given 1 exchange server?
many thanks! byron
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as: snail945@xxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx
