With Exchange Server 2003 about to hit the street and Windows Server 2003 just two months out the door, now is the time to learn how to optimize these new technologies. In a recent webcast, Integrating Exchange 2003 with Windows Server 2003 & Outlook 2003, Microsoft Senior Technology Advisor Matthew Hester and Exchange Server product manager Edward Wu discussed the key issues to consider before integrating new Exchange technologies into your existing Windows infrastructure. In this Q&A, they respond to audience questions.
Q: Will Web access support sync to palm pilots?
A: There is no synch support to announce; however, browse access is supported via HTML compatible browsers.
Q: What is RLS 1 and RTM 1? (in reference to Exchange 2003)?
A: If you are referring to RC1, then Release Candidate 1 is usually one of the last milestones before the final, "release to manufacturing (RTM)" milestone.
Q: Is there a "Corporate Disclaimer" capability built-in Exchange 2003?
A: No, this is only a partner add-on right now.
Q: Are there any auto accept features for resources?
A: Not yet, but there are ways to write custom code to support this -- stay tuned.
Q: How does the /3GB & /VA switch improve memory management?
A: With the /Userva switch, you can customize how the memory is allocated when you use the /3GB switch. The number following /Userva= is the amount of memory in megabytes (MB) that will be allocated to each process. If you set /3gb /Userva=3030, this reserves 3,030 MB of memory to the process space, as compared to 3,072 MB when you use the /3GB switch alone. The 42 MB that is saved when you set /Userva=3030 is used to increase the kernel memory space, free system page table entries (PTEs). The PTE memory pool is increased by the difference between 3GB (specified by the /3GB switch) and the value that is assigned to the /Userva switch. For more details, click here.
Q: When are classes going to be available?
A: Many classes will be available in August. Please take a look at the training schedule.
Q: Will Exchange 2003 allow full Outlook e-mail access to an account without allowing that account to see itself in the global address book?
A: There may be a way to hide accounts (e.g. Resource Accts).
Q: You mentioned improved clustering for Exchange 2003; do you mean Windows clustering or is there one in particular for Exchange 2000?
A: Windows clustering specifically, but there are things Exchange 2003 improves upon.
Q: Should/could you use separate servers for Web access and SMTP?
A: This depends upon your security and performance needs. Larger organizations do this, but some smaller ones use one box.
Q: Microsoft Outlook Web Access (OWA) for Exchange 2000 was not able to use logged in user authentication for security. Can OWA 2003 do so?
A: You can set this differently in Exchange 2003. If you used OWA on the Intranet, then yes, you can cache credentials, but not from the Intranet.
Q: If I want to use one or more Exchange Server 2003, do I have to migrate all my domain controllers (DC) and global catalogs (GC) to Windows Server 2003?
A: No, Exchange 2003 is fully compatible with Windows 2000 servers, DCs and GCs. Some features will not be available, such as RPC/HTTPS access from Outlook 2003 (VPN'less access using OL2003 from the Internet).
Q: Will Exchange 2003 provide SMIME functions on the server?
A: Not directly (as in store/manage certs). It is still a function of Windows Server; however for SMIME in OWA, the OWA Front End (FE) "proxies" all PKI infrastructure for the end user -- that is, it manages the PKI infrastructure from the FE server.
>> Continue to part two
FOR MORE INFORMATION