Hier is ie dan, de mini-Howto om RPC over HTTP in te stellen op een Exchange 2003 omgeving
Ik ben begonnen met deze Guide te downloaden :
http://www.microsoft.com/...B01958F6B7&displaylang=en
Ik ga eerst ff lezen en laat straks wel wat van me horen.
Ahh, in dit document wordt verwezen naar :
http://www.microsoft.com/...003/library/ex2k3rpc.mspx
Ga ik ook even lezen.
Quote van deze site :
Microsoft® Exchange Server 2003 and Microsoft Office Outlook® 2003, combined with Windows Server™ 2003, support the use of RPC over HTTP to access Exchange servers. Using the Microsoft Windows RPC over HTTP feature to enable your users to connect to their Exchange mailbox eliminates the need for remote office users to use a virtual private network (VPN) to connect to their Exchange servers. Users running Outlook 2003 on client computers can connect directly to an Exchange server within a corporate environment from the Internet.
Kijk dat is wat we willen
Ah, een ander document downloaden, met daarin een aantal scenarios.
Exchange Server 2003 RPC over HTTP Deployment Scenarios
http://www.microsoft.com/...8e2bef39e8&displaylang=en
Het scenario wat voor mij van toepassing is, is de single server scenario (3)

To use RPC over HTTP, you must run Windows Server 2003 on the following computers:
• All Exchange Server 2003 servers that will be accessed with RPC over HTTP.
• All Exchange Server 2003 front-end servers acting as RPC proxy servers.
• All global catalog servers used by Outlook 2003 clients and Exchange Server 2003 servers configured to use RPC over HTTP.
Exchange Server 2003 must be installed on all Exchange servers that are used by the RPC proxy server.
All client computers that are running Outlook 2003 must be running either Windows Server 2003 or Microsoft Windows XP Service Pack 1 (SP1) or later with the following update:
331320, "Windows XP Patch: RPC Updates Needed for Exchange Server 2003" (
http://go.microsoft.com/fwlink/?LinkId=16687).
Also, the following is recommended when you use RPC over HTTP communication:
• Use Secure Sockets Layer (SSL) encryption. SSL is required by the RPC proxy server for all client-to-server communication and the servers SSL certificate must be valid and trusted by the client. Outlook will not connect if the certificate is invalid or not trusted.
• Choose the correct client authentication method. Basic authentication over SSL is firewall-independent and can be used regardless of firewall configuration. NTLM authentication can be used but is dependent on how the firewall handles SSL traffic.
Note If the firewall does not add a via: header to the HTTP header information, NTLM can be used. If the firewall does add a via: header (as many reverse proxies do), IIS will not allow NTLM authentication.
• Use an advanced firewall server in front of your Exchange front-end server in the perimeter network. It is recommended that you use a dedicated firewall server such as ISA Server 2000 with Service Pack 1 and Feature Pack 1 or later to secure your messaging environment. For information about using ISA Server 2000 SP1 with Exchange, see the Exchange online book, Using ISA Server 2000 with Exchange Server 2003 (
http://go.microsoft.com/fwlink/?linkid=23232).
Ok, genoeg info over wat we nodig hebben. Nu aan de slag.
Stap 1.
Aanloggen op de Exchange server.
Service Manager opstarten
Expand het server mapje
Rechter Muisknop op de servernaam
Tabblad RPC-Http aanklikken.

Klik op Ok
Klik op Ok bij de waarschuwing.

Klik ook op Ok bij deze melding.
Reboot
Stap 2
Start nu de Internet Information Service
Expand de Default Website
Klik met je rechtermuisknop op RPC
Klik op Properties
Ga naar het tabblad : Directory Security
Klik bij Authentication and access control op Edit en neem de volgende instellingen over. (Je moet wel al een Server Certificaat op je IIS hebben staan, maar dit heb je waarschijnlijk al bij je webmail gedaan)
Klik op Ok en sluit IIS af.
Nu is je Exchange server geconfigureerd voor RPC over HTTP
Stap 3.
Nu moet exchange nog verteld worden dat ie een aantal vaste poorten moet gebruiken voor RPC over HTTP.
1. On the Exchange proxy server, start Registry Editor (regedit).
2. In the console tree, locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3. In the details pane, right-click the ValidPorts subkey, and then click Modify.
4. In Edit String, in the Value data box, type the following information:
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004;
• ExchangeServer is the NetBIOS name of your Exchange server.
• ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server.
Your Exchange server is now set up to act as both a back-end mailbox and an RPC over HTTP proxy server.
To configure the global catalog server acting as an Exchange back-end server to use a specified port for RPC over HTTP
1. On the RPC proxy server, start Registry Editor (regedit).
2. In the console tree, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\
Parameters
3. Click Edit, click New, and then select Multi String value.
4. Create a multi-string value with the name NSPI interface protocol sequences.
5. Right-click the NSPI interface protocol sequences multi-string value and then select Modify.
6. In the Value data field, enter ncacn_http:6004.
7. In Registry Editor, click File, and then select Exit to save your settings.
8. You must now restart your server for the settings to be applied.
Stap 4
Vervolgens moet Outlook ingesteld worden voor het gebruik van RPC over HTTP
Neem de volgende instellingen over in de accounteigenschappen (Vul wel je eigen web-adres in)
---------*** THE END ***---------
[
Voor 2% gewijzigd door
F_J_K op 04-10-2004 21:28
]
Heb je iets aan mijn antwoord ? Een thumbs-up wordt zeker op prijs gesteld.