The release of Exchange 2003 bought us some very good features, like Intelligent Filtering (IMF) and my favorite RPC over HTTP message. This allows a user to access their e-mail client Outlook, without the use of VPN or dial-up network. To me, this was a way to send a god, I like to spend much time on client sites and need constant access to important documents to my e-mail stored. The RPC over HTTP I can just connect my laptop to the network, open my Outlook> Client and remove my e-mail as if I were in office.
The initial configuration of RPC over HTTP together is not easy and requires you to follow a rigorous process. I have a lot of clients call me the expectation that they do not get, that I devoted an article, decided to write this feature work.
RPC over HTTP System Requirements
To use RPC over HTTP, you must have Windows Server 2003 is running on your computer as follows:
or All Exchange 2003 servers that are accessed with Outlook 2003The client RPC over HTTP.
or Exchange Server 2003 front-end servers as RPC proxy.
o The global catalog server used by Outlook 2003 client and Exchange Server 2003 are configured to use RPC over HTTP.
Exchange 2003 proxy server must be installed on all Exchange RPC Server, which are used as indicated by the computer. In addition, the client computer running Outlook 2003, all with Microsoft Windows XP Service Pack 1 (SP1) orlater.
-------------------------------------------------- ----------
Deploying RPC over HTTP
This section contains detailed instructions for deploying RPC over HTTP in Exchange 2003. Follow the steps in the following order.
1. Configure your Exchange front-end servers as RPC proxy server.
2. Configure the RPC virtual directory in Internet Information Services (IIS) server on the Exchange front-end.
3. Configure the registry to the exchange2003 that communicates with the RPC proxy server to communicate with specific ports for RPC over HTTP.
4. Open specific ports on the internal firewall for RPC over HTTP, and the standard ports for the exchange of communications front-end.
5. Create a profile for each user to use RPC over HTTP.
Each of these steps is described in the following sections. After completing these steps, users with RPC over HTTP accessthe front-end Exchange server.
-------------------------------------------------- ----------
Step 1: Configure the Exchange front-end server for RPC over HTTP
The RPC proxy server processes the Outlook 2003 RPC requests that arrive on the Internet. In order for the RPC proxy server processes the requests successfully RPC over HTTP, you must have Windows Server 2003 RPC over HTTP Proxy networking component on the Exchange front-end server.
To configure theExchange front-end server for RPC over HTTP
1. On the server front-end server running Windows Server 2003, click Start, Control Panel, then click Add / Remove Programs.
2. In Add / Remove Programs, click Add / Remove Windows Components in the left pane.
3. In the Windows Components Wizard, click the Windows Components page, select Networking Services and click Details.
4. In Networking Services, select the Enable RPC over HTTP proxy, and thenClick OK.
5. In the Windows Components page, click Next to install the RPC over HTTP proxy Windows.
-------------------------------------------------- ----------
Step 2: Configure the RPC virtual directory in Internet Information Services
Now you have your Exchange front-end server is configured for RPC over HTTP, you need the RPC virtual directory in IIS.
To configure the RPC virtual directory
1. Click Start, point to All Programs,Administrative Tools, then click Internet Information Services (IIS).
2. In Internet Information Services (IIS) in the console tree, expand the server you want, expand Web Sites, expand Default Web Site, right-click the RPC virtual directory, and then click Properties.
3. In RPC Properties, on the Directory Security tab in the Authentication and access control panel, click Edit.
Note: RPC over HTTP does not allow anonymous access.
4. InAuthenticated access, select the check boxes next to Basic authentication (password is sent in clear) and then click OK.
5. To save the settings, click Apply, then click OK.
Your RPC virtual directory is now to use Basic authentication.
If you use SSL, skip the following steps to plan the configuration are not forwarded to SSL, however, the RPC proxy server is configured for non-SSL sessions. The non-SSL sessions can be transmitted by adding aRegister of particular value to the server.
Caution: Incorrectly editing the registry problems are serious problems that may require you to reinstall your operating system can do can bring. The problems resulting from editing the registry may not be correct defective. Before you edit the registry, back up all important data.
For non-SSL encrypted traffic using RPC over HTTP
1. The RPC proxy server, start Registry Editor (regedit).
2. In the console tree, navigate to the followingRegistration Key:
HKEY_LOCAL_MACHINESoftwareMicrosoftRpcRpcProxy
3. In the details pane, right-click and add a new DWORD value named AllowAnonymous and then right click and select Modify.
4. In the Edit DWORD Value, enter the value 1.
The RPC proxy server is now configured for applications without a requirement to produce a first encrypted SSL session to be transmitted. The adjustment to enforce authenticated access is still controlled in the authentication andAccess Control Settings.
-------------------------------------------------- ----------
Step 3: Configure the RPC proxy server to use specific ports
After the RPC over HTTP networking component for IIS, you must use the RPC proxy server to use specific port numbers to communicate with the server on the corporate network. In this scenario, the RPC proxy server is configured to use specific ports and individual computers that the RPC proxy servercommunicates with are also configured to use specific ports when required by the RPC proxy server. If you run Exchange 2003 Setup, Exchange is automatically configured to be ncacn_http the ports listed in Table 2.1.
Phase 3 includes the following two methods.
1. Configure the RPC proxy server on specific ports for RPC over HTTP requests to servers that can communicate across a network.
2. Configure to use specific global catalog server portscommunicate to the RPC over HTTP requests to the RPC proxy server in the perimeter network.
Warning:
Incorrectly editing the registry can cause serious problems that may require you to perform a new installation of the operating system. The problems resulting from editing the registry may not be correct defective. Before you edit the registry, back up all important data.
To configure the RPC proxy server to the specified default ports for RPC over HTTP
The following portsIf the required ports for RPC over HTTP.
Table 2.1 ports required for RPC over HTTP
Server ports (services)
Exchange back-end server 593 (endpoint mapper)
6001 (Store)
6002 (DS referral)
6004 (DS proxy)
Global Catalog Server 593 and 6004
1. The RPC proxy server, start Registry Editor (regedit).
2. In the console tree to the following registry key:
HKEY_LOCAL_MACHINESoftwareMicrosoftRpcRpcProxy
3. In detailPane, right-click the subkey ValidPorts, and then click Edit.
Figure 2.4 The registry settings RPCProxy
4. Edit the string in the Value data box, type the following information:
ExchangeBEServer: 593; ExchangeBEServerFQDN: 593; ExchangeBEServer :6001-6002; ExchangeBEServerFQDN :6001-6002; ExchangeBEServer: 6004; ExchangeBEServerFQDN: 6004;
global catalog server: 593; GlobalCatalogServerFQDN: 593; global catalog server: 6004; GlobalCatalogServerFQDN: 6004
O and ExchangeBEServer global catalog server, the NetBIOS name of Exchange back-end server and global catalog servers.
O ExchangeBEFQDN GlobalCatalogServerFQDN and the domain name (FQDN) of the Exchange back-end server and global catalog servers.
Communicate in the registry key that remains on all servers in the network society in which the RPC proxy server list.
Important:
access to communicate with the RPC proxy server, any server from Outlook> Doors client must have set. If a server as Exchange public folder was not configured to use RPC over HTTP as communication ports, the client will not be able to access the server.
To configure the global catalog server to specific ports for RPC over HTTP
1. For the global catalog server, start Registry Editor (regedit).
2. Navigate to the following registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSet
ServicesNTDSParameters
3. From the Edit menu, choose New, then Multi-String Value.
4. In the details pane, a multi-value string with NSPI interface protocol name.
5. Right-click the NSPI interface protocol sequences multi-string value and click Modify.
6. Edit the string in the Value data box, type ncacn_http: 6004
7. Start the Global CatalogServer.
-------------------------------------------------- ----------
Step 4: Create an Outlook profile with RPC over HTTP
To allow users to use RPC over HTTP client from their computer, they have an Outlook profile that uses the required RPC over HTTP settings. These settings enable Secure Sockets Layer (SSL) communications with basic authentication, which is necessary when RPC over HTTP.
Although voluntary, it is veryrecommends that the "cached mode" option for all profiles, which is used to connect to Exchange using RPC over HTTP in conjunction.
To create an Outlook profile to use RPC over HTTP
1. Click Start, click Control Panel.
2. In Control Panel, one of the following tasks:
o If the Category View, in the left pane, under See other options in Control Panel, and then click Mail.
o If you are using Classic View, double-clickE-mail.
3. In the Mail Setup in Vista's profiles.
4. In Mail, click Add.
5. In New Profile, the profile field, type a name for this profile, and then click OK.
6. In E-mail Accounts Wizard, click Add a new e-mail account and then click Next.
7. On the Server Type page, click Microsoft Exchange Server, and then click Next.
8. Exchange Server Settings page, do the following:
a. In Microsoft Exchange Server,Enter the name of the server back-end server that hosts the mailbox.
b. Check the box next to Use Cached Exchange Mode.
c. In the Username field.
d. Click More Settings.
9. On the Connection tab in the exchange on the Internet pane, select Connect to my Exchange mailbox using HTTP check box.
10. Click Exchange Proxy Settings.
11. Exchange Proxy Settings page, under Connection Settings, the followingSteps:
a. connect the domain name (FQDN) of the RPC proxy server Use this URL to the proxy server for Exchange box.
b. Select the connection using SSL only check box.
c. Select the session mutual authentication when connecting with SSL checkbox.
d. Enter the FQDN of the RPC proxy server on behalf of principle for the proxy server. Use the format: msstd: FQDN of RPC Proxy Server.
e. As an optional step you can configure Outlook2003 default on the Exchange server with RPC over HTTP, connecting the box next to On fast networks, connect to Exchange using HTTP first, then connect using TCP / IP.
12. In the Exchange Proxy Settings in the Proxy authentication settings window, under Use this authentication when connecting to the proxy server for Exchange, select the Basic authentication.
13. Click OK
14. Enabling RPC over HTTP, allowing the user profiles for RPCHTTP communication with Outlook 2003. Alternatively, you can instruct the user how to manually enable RPC over HTTP for Outlook 2003 to their profiles.
Note:
If you have configured the client to communicate using SSL, you must use the machine to add SSL certificate chain, the Trusted Root Certification Authorities store on the client.
Users are now configured to use RPC over HTTP.
My Links : MP3 Player logitech webcam
Continuar leyendo 
Ocultar articulo 