Get More Content
What was the one thing we heard over and over again at last November's Microsoft Exchange Connections conference? "We need more SharePoint coverage!" Messaging administrators everywhere are being asked to implement and manage Microsoft Share-Point Portal Server and Windows SharePoint Services, without receiving much guidance about how to do so. If you're one of these people, you'll be happy to know that we'll be offering more SharePoint coverage in our publications and conferences. In this issue's "SharePoint Solutions," Ethan Wilansky and Jeff Sandler give you some real-world advice about working with SharePoint security. You can get more SharePoint workarounds in the authors' February 2006 Windows IT Pro article, "Get Past the Gaps in Share-Point," which gives you solutions for branding your portal, supporting multiple languages in SharePoint Portal Server, and searching across Windows SharePoint Services sites.
Also in the February issue of Windows IT Pro: Tony Redmond takes on "Exchange 12: The 64-Bit Question." Why has Microsoft decided to restrict the next version of Exchange Server to the 64-bit platform, and how will that move affect you? As Tony points out, "Microsoft has based this decision on the belief that the world is moving rapidly to a point at which 64-bit hardware is the norm for customer deployments. On top of that, moving Exchange to a 64-bit platform solves several of the product's technical challenges. Will this decision cause customers to slow their plans for Exchange 12 deployment, or will it make the next Exchange version more attractive than ever?"
For those who might be thinking of alternatives to Exchange, Michael Otey reviews Kerio MailServer 6.1, which can run on Windows Server 2003, Windows XP, Windows 2000 Server, Win2K Professional, Red Hat Linux, Novell SUSE Linux, and even Macintosh OS X. This product is a perpetual favorite in Windows IT Pro's annual Readers' Choice awards.
Learn to Share
Who says sharing can't be rewarding? Exchange & Outlook Administrator wants your tips, solutions, and advice—we'll even give you $100 for them! Send us a short (less than 500 words) submission that tells us how you solved a problem or gives us your take on a messaging-related product.
If we publish the piece in the newsletter's Reader to Reader column, you'll get $100 (and the undying gratitude of your peers). Send submissions to [email protected]
Exchange Tips: Prevent Accidental Outlook Shutdown; RPC over HTTP on One Server
This month's first tip comes from Sue Mosher (courtesy of Windows IT Pro's Ask the Experts column); the second tip comes from our sister site, MSD2D. See "Get More Online" for directions to the tips.
Displaying a Prompt Before Outlook Closes
Q: I often close Microsoft Outlook by accident. Is there a way to have Outlook present a prompt that lets me cancel or confirm the closing operation?
A: Here's a little trick to help with that. Create a message to yourself. Before sending it, click the Options button and select the Do not deliver before check box. Enter a delivery date and time that's some time in the future, but the exact date doesn't really matter. Send that message. Now go to the Outbox and open the message, then close it without resending it. The message-should appear in the Outbox in normal type, not italics.
As long as that message remains in the Outbox, closing Outlook displays a prompt that items are still in the Outbox. You can click No on the prompt if you closed Outlook unintentionally and don't really want it to quit.
Configuring RPC over HTTP on a Single Exchange Server
If you're running a single Exchange Server 2003 server with Service Pack 1 (SP1) and want to configure Remote Procedure Call (RPC) over HTTP on the server, open Exchange System Manager (ESM). Right-click the server and select Properties, then go to the RPC-HTTP tab and configure the server as a back-end server. You'll get a warning about not having front-end servers; just click OK. You'll get another warning about the server not having the correct ports configured. Click OK to configure the ports automatically.
Next, you'll need to configure the RPC virtual directory in Microsoft IIS. You can find the RPC virtual directory under the Default Web Site. You'll need to disable Anonymous access and enable Basic Authentication and Integrated Windows authentication for the RPC virtual directory.
Configuring the RPC proxy server will require some registry editing. Modify the HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\ValidPorts subkey as follows: NET BIOS:6001-6002; FQDN:6001-6002; NETBIOS:6004; FQDN:6004. NET BIOS is the NetBIOS name of your Exchange server, and FQDN is the server's Fully Qualified Domain Name (FQDN). Create a new multistring entry, called NSPI interface protocol sequences, under the HKEY_LOCAL_ MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters subkey. To that entry, add the following data: ncacn_http:6004. Reboot your server and test.