|
Motorola’s Exchange Server 2003 ActiveSync Implementation
|
bet | 3/3 | Sana | 03.10.2020 | Hajmi | 0,61 Mb. | | #11958 |
Motorola’s Exchange Server 2003 ActiveSync Implementation
To properly validate the Exchange Server 2003 ActiveSync architecture, a test configuration is needed. Motorola’s relatively complex lab configuration represents the variations in the production environment in enough detail to allow for testing of all of the functionality intended for production deployment. All changes, new features, and implementation methods are rigorously tested and certified before implementing them in production.
One of the most important benefits of a successful pilot is that it proves the environment. This allows the project team to demonstrate the production feasibility of Exchange Server 2003 and ActiveSync. As a result, the issues encountered during the pilot are likely to have already been addressed or determined to have a minor impact on a wider deployment.
Exchange
Motorola’s Exchange Server configuration is shown in the table below.
-
Exchange configuration
|
Test
|
Production
|
Exchange 5.5 sites or Exchange 2000 or 2003 administration groups
|
8
|
93
|
Mailbox servers running Exchange 5.5 SP4 on Windows NT 4.0 SP6A
|
9
|
177
|
Mailbox servers running Exchange 2000 SP4 on Windows 2000 SP3
|
7
|
9
|
Mailbox servers running Exchange Server 2003 on Windows Server 2003 SP0
|
2
|
2
|
Dedicated hub or bridgehead servers running Exchange 5.5 SP4 on Windows NT 4.0 SP6A
|
2
|
22
|
Dedicated conferencing and Instant Messaging servers running Exchange 2000 SP3 on Windows 2000 SP3
|
2
|
8
|
Active Directory
Motorola’s Active Directory configuration is shown in the table below.
-
Active Directory configuration
|
Test
|
Production
|
Native mode root domain controllers running Windows 2000 SP3
|
1
|
5
|
Child domains
|
2
|
9
|
Domain controllers running Windows Server 2003 SP0
|
1
|
17
|
Domain controllers running Windows 2000 Server SP3
|
4
|
139
|
Domain controllers that are global catalog servers
|
4
|
113
|
Domain controllers running the Active Directory Connector
|
2
|
15
|
Active Directory Connector connection agreements
|
36
|
502
|
Trusting Windows NT 4.0 resource domains
|
1
|
8
|
Domain controllers running Windows NT 4.0 SP6A
|
2
|
63
|
Total objects
|
40,000+
|
480,000+
|
Users and mailboxes
|
14,000+
|
280,000+
|
Computers
|
70+
|
45,000+
|
Groups and distribution lists
|
900+
|
43,000+
|
Public folders
|
2,000+
|
33,000+
|
Organizational units
|
100+
|
13,000+
|
Subnets
|
20+
|
7,000+
|
Active Directory sites
|
9
|
187
|
Wireless Mobile devices
-
Motorola used new prototype and production Motorola MPx200 phones running Smartphone 2002 as devices in the test and production environments.
Motorola also used a Pocket PC Phone edition device running Smartphone 2002 as a reference device with a commercial history of about a year.
|
|
Internet connectivity and security
Motorola used separate external DNS names for wireless mail connectivity in the test and production environments to allow independent testing without affecting production users.
Motorola opened port 443 to the IP addresses corresponding to these names.
Motorola has a proprietary cache system for Internet–facing Web servers, which includes SSL termination and acceleration.
Motorola initially installed a free-of-charge test certificate from Thawte on the lab system for SSL termination. The corresponding test root certificate was installed on the wireless devices. Following a successful test, a production Thawte certificate was installed for SSL termination. This matches one of the preinstalled certificates on the Smartphone 2002 operating system.
Motorola used ISA Server 2000 SP1 running on Windows 2000 Server SP3 as a proxy to direct incoming Web requests to Exchange. Motorola installed the ISA feature pack, which includes URLScan 2.5.
Infrastructure Changes to Support Exchange Server 2003 ActiveSync
Current Exchange Server version
|
Recommendation
|
Exchange 2003
|
No additional change is necessary. ActiveSync is enabled by default on each Exchange 2003 mailbox.
|
Exchange 2000
|
You can introduce an Exchange Server 2003 server into your existing environment without difficulties. Your existing hardware should be able to run Exchange Server 2003.
|
Exchange 5.5
|
You may need to review your existing hardware, especially if you plan to run Exchange Server 2003 on Windows Server 2003. You need to work carefully with your Active Directory team to plan your Exchange Server 2003 deployment.
|
Current Windows domain implementation
|
Recommendation
|
Active Directory using Windows Server 2003 or Windows 2000 Server
|
Implement the following preparation steps:
Be sure that any domain controllers running Windows 2000 have at least SP3 installed.
Run Exchange Server 2003 ForestPrep to install the required schema and configuration context changes in Active Directory. Windows 2000 based global catalog servers will undergo a global catalog rebuild.
Run Exchange Server 2003 DomainPrep on each domain that will contain Exchange Server 2003 instances or users and mailboxes on an Exchange Server 2003 mailbox server.
Upgrade all Active Directory Connector instances to Exchange Server 2003.
|
All Windows NT 4.0 domains
|
Introduce Active Directory into your environment. Active Directory requires very careful planning:
A single Exchange Server organization means a single Active Directory forest.
Plan the domain structure, including possible use of an empty root domain. Decide whether you will migrate into new domains or upgrade existing domains.
Determine the DNS strategy to support Active Directory, bearing in mind your current DNS architecture and products together with the technical requirements of Active Directory to support service (SRV) records (mandatory) and the dynamic DNS (highly desirable).
Plan your domain and forest operations master roles.
Estimate the size of your global catalog.
Plan your replication topology.
Plan your organization unit structure bearing in mind your likely use of delegated administration and Group Policy.
Plan your deployment of the Active Directory connector, which is required if you have Exchange 5.5 in your Exchange organization in addition to Exchange 2000 and/or Exchange Server 2003.
|
Wireless Mobile Devices
The new Motorola MPx200 phone uses the Windows Mobile 2002 software for Smartphones and is fully Exchange Server 2003 ActiveSync capable. You can use any device capable of running the Windows Mobile 2002 or 2003 software for Smartphones that has wireless connectivity. Or you can use any other phone that is Exchange Server 2003 ActiveSync compatible. Devices are available in the Smartphone form factor, which primarily functions as a phone and has a standard phone style numeric keypad. Or you can use a PDA format device that has a stylus and on-screen keyboard. The devices must be capable of an Internet connection—for example through GPRS. You will need to activate this with your telephone service provider. You should be able to use your Exchange Server 2003 infrastructure to enable browse access to e-mail, calendar, contacts, and tasks from Wireless Application Protocol (WAP) enabled phones and mobile devices that support HTML and cHTML Browsers.
If a wireless mobile device is stolen, the thief has immediate access to the true owner’s e-mail because the Windows password is cached. So always implement a PIN on the phone or PDA.
Internet Connectivity and Security
You will need a new externally addressable DNS name, such as wireless-mail.myco.com.
You need to open port 443 SSL HTTPS in your firewall to the IP address corresponding to this name.
You will need a certificate for SSL termination. Although you can turn off SSL on a device running Smartphone 2003, avoid doing so. An SSL–encrypted connection is always preferable.
You may have rules regarding incoming connections from the Internet into your intranet. If you use a proxy server such as ISA Server 2000 with the feature pack installed, you can use the URLScan feature to check for valid commands and filter out buffer overflow attacks. You can also implement custom content inspection and filtering.
Additional Benefits of an Exchange Server 2003 ActiveSync–Enabled Infrastructure
Your current infrastructure may require significant work to implement Exchange Server 2003 ActiveSync; however, you will find numerous significant advantages for both users and administrators in deploying the required products.
Exchange Server 2003
User benefits:
Mail traffic compression (with Outlook 2003)
Access from Outlook 2003 to Exchange 2003 without a virtual private network (VPN)
Full featured Outlook Web Access with comparable features to Outlook 2003
Administrator benefits:
Recovery Storage Groups allow rapid restore of a subset of the Exchange Server 2003 database.
Many-to-one clustering (7 active, 1 passive).
Easier to move users between servers.
Control public folder search order.
Admin tools work with Exchange Server 2003, 2000, and 5.5.
Improved queue management.
Kerberos support.
More secure Internet Information Services (IIS) 6.0 (when Exchange Server 2003 is installed on Windows Server 2003).
Active Directory
User benefits:
Changed passwords are immediately globally accessible.
Administrator benefits:
Delegated administration allows administrators to manage a subset of users, groups, and computers.
Use Group Policy to allow settings made in one place to propagate to thousands of users or computers.
Overcome Windows NT 4.0 domain SAM size limitations, and support millions of users and computers in each domain.
Multimaster replication allows changes to be written to any domain controller (not just the primary domain controller (PDC)).
An opportunity to collapse legacy domains.
Supports secure dynamic DNS.
Lightweight Directory Access Protocol (LDAP) directory compliant with version 3 enables many business applications.
Manage a set of domains as a single directory.
Motorola MPx200 Smartphone
Browse the Web and your Exchange 2003 e-mail, calendar, and contact information using Pocket Internet Explorer.
Wirelessly synchronize your Exchange 2003 e-mail, calendar, and contact information.
Listen to music and view video clips using Microsoft Windows Media® Player.
Expanded storage using Secure Digital (SD) card.
Internet connectivity
Allow mobile users to have full corporate e-mail access while on the move.
Conclusion
Motorola has leveraged Microsoft Windows Mobile software and has integrated the power of ActiveSync technology with its mobile phones, delivering the benefits of ActiveSync technology. The Motorola–Microsoft alliance provides mobile users full access to mail, calendar, and contacts, including offline availability.
References
Active Directory
|
http://www.microsoft.com/windowsserver2003/technologies/directory/activedirectory/default.mspx
|
Motorola’s Active Directory migration strategy
|
“Motorola Reduces TCO and Improves Productivity with Domain Consolidation and Upgrade to Windows Server 2003”
http://www.microsoft.com/windowsserver2003/evaluation/casestudies/CaseStudy.aspx?CaseStudyID=13931
|
Exchange Server 2003
|
http://www.microsoft.com/exchange
|
Exchange 2000 Server
|
http://www.microsoft.com/exchange
|
Internet Security and Acceleration (ISA) Server
|
http://www.microsoft.com/isaserver/
|
Motorola MPx200
|
http://commerce.motorola.com/consumer/QWhtml/mpx200.html
|
Windows Mobile software for Smartphones
|
http://www.microsoft.com/windowsmobile/products/smartphone/default.mspx
|
Windows 2000 Server
|
http://www.microsoft.com/windows2000/default.asp
|
Windows Server 2003
|
http://www.microsoft.com/windowsserver2003/default.mspx
|
Microsoft consulting Services Page October 3, 2020
Exchange 2003 ActiveSync® architecture
|
| |