[Exch. 2k3] Template voor Ipaq*

[QuikSoft]

Heeft iemand een idee of een shema hoe je je webmail van exchange 2003 kunt aanpassen voor een ipaq ( ivm de groote van het scherm en dergelijke van je Ipaq).
Of zijn hier al standaarden en/of voorbeelden bij exchange 2003 tooe gevoegd.
Bijv planet heeft een speciale wemail site voor ipaq gebuikers.

Gevonden Info bij MS.

Configuring Mobile Device Support
Configuring mobile device support for Exchange 2003 involves the following activities:
• Configure synchronization.
• Configure Exchange ActiveSync to use RSA SecurID.
• Enable Outlook Mobile Access.
Configuring Synchronization
When you install Exchange, synchronization access to Exchange is enabled by default for all users in your organization. You can also use the Active Directory Users and Computers snap-in to enable individual users for synchronization access.
Configuring Exchange ActiveSync
The following procedure shows you how to configure Exchange ActiveSync in your organization.
To configure Exchange 2003 to use Exchange ActiveSync
1. Start Exchange System Manager.
2. Expand Global Settings, right-click Mobile Services, and then click Properties.
3. Under Exchange ActiveSync, select from the following check boxes:
• Select the Enable user initiated synchronization check box to allow users to use Pocket PC 2002 devices to synchronize their Exchange data.
• Select the Enable up-to-date notifications check box to allow users to receive notifications that are sent from the Exchange server to devices that are designed to allow notifications.

• Select the Enable notifications to user specified SMTP addresses check box to allow users to use their own SMTP carrier for notifications.
Note
With this feature enabled, when a new message arrives in a user's mailbox, up-to-date notifications allows synchronization to occur on a user's device. Enable this feature if you have users who are using mobile devices to synchronize, and you do not want to specify the carrier

4. Click Apply, and then click OK.
The following procedure shows you how to configure a mobile device such as a Pocket PC Phone Edition device to use Exchange ActiveSync. Perform this procedure on each mobile device in your organization. As an alternative, you can instruct your users how to configure their own devices.
To configure Pocket PC Phone Edition devices to use Exchange ActiveSync
1. On the mobile device, from the Today screen, tap Start, and then tap ActiveSync.
2. Tap Tools, tap Options, and then tap the Server tab.
3. Select the check box next to each type of information that you want to synchronize with the server.
4. To configure synchronization options for each type of information, select the type of information, and then tap Settings.
5. In the Server Name field, enter the address or name of the server to connect to when synchronizing Exchange data.
6. Tap Advanced.
7. On the Connection tab, enter the user name, password, and domain name.
8. On the Rules tab, select the rule that best applies to you, for how you want synchronization to work whenever information on your device and your Exchange server have both been changed.
9. Tap OK to accept the changes you made to ActiveSync.
10. Repeat this procedure for each of your users' Pocket PC Phone Edition devices. As an alternative, instruct your users about how to configure their devices for use with Exchange ActiveSync.
Up-to-Date Notifications
Windows Mobile™ 2003 devices are able to receive notifications generated by Exchange 2003 that initiate Exchange ActiveSync synchronization between a user's device and his or her Exchange mailbox. This synchronization allows the users mobile device to be up-to-date with the latest Exchange information.
Configuring Exchange ActiveSync to Use RSA SecurID
As an added level of security, you can use Microsoft Windows Mobile devices with Exchange ActiveSync in conjunction with RSA SecurID two-factor authentication.
Note
No additional device configuration is required to support RSA SecurID. The device presents the appropriate authentication automatically when synchronizing with an Exchange ActiveSync server protected by RSA SecurID.

Using RSA SecurID with Exchange ActiveSync involves the following steps.
1. Set up the RSA SecurID server components.
2. Configure Internet Information Server (IIS) to use RSA SecurID.
3. Set up user accounts.
4. Configure ISA Server 2000.
Setting Up the RSA SecurID Server Components
To configure the RSA SecurID server components, you need to:
• Set up the RSA ACE/Server The RSA ACE/Server is the RSA server that stores and manages authentication tickets and credentials for your users. To set up the RSA ACE/Server, follow the procedures as outlined in the RSA SecurID documentation provided by RSA Security Inc.
• Set up the RSA ACE/Agent on the front-end server The RSA ACE/Agent is the Internet Server Application Programming Interface (ISAPI) filter that performs authentication and communicates to the ACE/Server to retrieve SecurID credentials. To set up the RSA ACE/Agent, follow the procedures as outlined in the RSA documentation.
Configuring IIS to Use RSA SecurID
Configuring IIS for RSA and Exchange ActiveSync involves the following procedures.
1. Protect the Exchange ActiveSync virtual directories.
2. Customize the custom HTTP response headers.
3. Install SecurID screens (optional). For information about installing these screens, see the RSA SecurID documentation.
Complete these steps to properly configure IIS for SecurID and Exchange ActiveSync operations.
Protecting the Exchange ActiveSync Virtual Directories
The first step to configuring IIS is to protect the virtual directories that your users access when they use Exchange ActiveSync. Exchange Server 2003 uses the Microsoft-Server-ActiveSync virtual directory.
You can protect this virtual directory in one of the following two ways:
• Protect the entire Web server (recommended) In this option, you protect all virtual roots on the IIS server with RSA ACE/Agent, including any other services implemented by the front-end server. For example, you may have configured your front-end Exchange server as an access point for Outlook Mobile Access or for Outlook Web Access.
• Protect only the Exchange ActiveSync virtual directories In this option, you configure the RSA ACE/Agent so that only Exchange ActiveSync is protected by SecurID. Use this option if you intend to enable additional services, such as Outlook Web Access and Outlook Mobile Access, on the same server without protecting those services with SecurID.
By default, the ACE/Agent is configured to protect the entire Web server. You can use the following procedure to verify this configuration.
To verify ACE/Agent is configured to protect the entire Web server
1. In the Internet Information Services snap-in for MMC, right-click the default Web server and select Properties.
2. Click the RSA SecurID tab, and verify that the Protect This Resource check box is selected.
Use the following procedure to configure the front-end server so that RSA SecurID authentication is limited to Exchange ActiveSync.
To limit SecurID Authentication to the Microsoft-Exchange-ActiveSync virtual directory
1. To disable server-wide protection, in the IIS snap-in, right-click the default Web server, and then click Properties.
2. Click the RSA SecurID tab, and then clear the Protect This Resource check box. (This step ensures that RSA SecurID is not enabled for the entire server, but rather only for the virtual roots that you specify.)
3. To enable protection for the virtual directories, in the IIS snap-in, right-click the Microsoft-Server-ActiveSync virtual directory, and then click Properties.
4. Select the RSA SecurID tab, and then select the Protect This Resource check box.
Note
If the check box is selected and shaded, this means that the virtual directory is inheriting its setting from the parent directory. Inspect the properties for the parent directory, and clear the Protect This Resource check box if you do not want the parent directory to be protected. Then, return to the child directory and make sure the check box is selected.

Customizing the HTTP Response Header for Devices
The ActiveSync client on the Microsoft Windows Mobile device must be able to distinguish between RSA SecurID authentication and Exchange ActiveSync responses. To enable this capability, you need to configure custom HTTP response headers on the WebID virtual root that contains the HTML forms configured by RSA ACE/Agent.
To configure custom HTTP responses for devices
1. In the IIS snap-in for MMC, locate the WebID virtual directory on the front-end server. This virtual directory is created by SecurID and contains the SecurID authentication forms and responses.
2. Right-click the WebID virtual directory, and then click Properties to open the properties for this virtual directory.
3. Click the HTTP Headers tab, click the Add button, and then enter the following header information.
Note
The following value is case-sensitive and must be entered on one line.

Custom Header Name: MSAS-TwoFactorAuth Custom Header Value: True Custom Header Name: MS-ASProtocolVersions Custom Header Value: 1.0,2.0 Custom Header Name: MS-ASProtocolCommands Custom Header Value: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse
Setting Up User Accounts
User accounts for SecurID should be set up by the Administrator as recommended by the RSA SecurID product documentation, with the following restriction:
• For all users, SecurID user IDs must be selected to match the Windows account name. Exchange ActiveSync with SecurID does not function for users who have a distinct RSA user ID that does not match their Windows account name.
Configuring ISA Server 2000
ISA Server 2000 Feature Pack 1 and RSA SecurID technology are integrated on the ISA Server. Currently, using RSA SecurID with ISA Server 2000 with Feature Pack 1 is unsupported. You can, however, deploy RSA SecurID with ISA Server 2000 Feature Pack 1, but you must configure the ISA Server to enable pass-through authentication. In this scenario, RSA authentication still occurs at the front-end server, not at the ISA Server. For information about how to enable pass-through authentication, see the ISA Server 2000 documentation.
Enabling Outlook Mobile Access
By default, all users are enabled for Exchange ActiveSync and Outlook Mobile Access. However, only Exchange ActiveSync is enabled on the Exchange server; by default, Outlook Mobile Access is disabled. This section describes how to enable Outlook Mobile Access on your Exchange server.
Perform the following steps to enable your Exchange 2003 users to use Outlook Mobile Access.
1. Configure your Exchange 2003 front-end server for Outlook Mobile Access.
2. Enable Outlook Mobile Access on the Exchange server.
3. Configure user devices to use a mobile connection.
4. Instruct your users in using Outlook Mobile Access.
Step 1: Configuring Your Exchange 2003 Front-End Server for Outlook Mobile Access
By default, the Outlook Mobile Access virtual directory (which allows your users to access Exchange from a mobile device) is installed with Exchange 2003. This virtual directory has the same capabilities and configuration settings as the Outlook Web Access virtual directory. When you configure a server to use Outlook Mobile Access, you should configure the server in the same way you configure a server for Outlook Web Access. For information about how to configure your Exchange 2003 servers to use Outlook Web Access, see the book Using Microsoft Exchange 2000 Front-End Servers (http://go.microsoft.com/fwlink/?linkid=14575).
Step 2: Enabling Outlook Mobile Access on the Exchange Server
After you configure your front-end server to use Outlook Mobile Access, you need to enable Outlook Mobile Access on your Exchange servers.
To enable Outlook Mobile Access
1. Log on as an Exchange Administrator to the Exchange server where the user's mailbox is located, and start Exchange System Manager.
2. Expand Global Settings, right-click Mobile Services, and then click Properties.
3. On the Mobile Services properties page, in Outlook Mobile Access, select Enable Outlook Mobile Access.
4. To enable users to use unsupported devices, click the Enable unsupported devices check box.
Note
For information about supported devices for Exchange and planning for mobile device support with Exchange, see the book Planning an Exchange Server 2003 Messaging System (http://www.microsoft.com/exchange/library/).


5. Click OK.
After you enable Outlook Mobile Access, you can modify the Outlook Mobile Access settings for users or groups of users using the Active Directory Users and Computers snap-in.
Step 3: Configuring Users' Devices to Use a Mobile Connection
To access Exchange 2003 using Outlook Mobile Access, users must have a mobile device from a mobile operator who has an established data network for mobile data. Before your users connect to Exchange 2003 and use Outlook Mobile Access or Exchange ActiveSync over a mobile connection, instruct them about how to configure their devices to use a mobile network, or provide them with resources that explain how to do so. For more information about configuring mobile devices and Exchange ActiveSync, see "To configure Pocket PC Phone Edition devices to use Exchange ActiveSync" earlier in this chapter.
Step 4: Instructing Your Users in Using Outlook Mobile Access
After you configure Exchange 2003 for Outlook Mobile Access, and your users have mobile devices that can use a mobile network to access Exchange 2003 servers, they need to know how to access their Exchange server and use Outlook Mobile Access. The following procedure describes how to use Outlook Mobile Access on a Pocket PC Phone Edition device.
To configure a Pocket PC Phone Edition device to use Outlook Mobile Access
1. On the device, from the Today screen, tap Start, and then tap Internet Explorer.
2. On the Internet Explorer screen, tap View, and then tap Address Bar to open the address bar in your browser window.
3. Tap anywhere inside the address bar, enter the following URL, and then tap the Go button: https://ExchangeServerName/oma, where ExchangeServerName is the name of your Exchange server running Outlook Mobile Access.
Note
If a connection bubble does not appear, you may have to connect to your network manually.

4. At the Network Log On screen, enter the user name, password, and domain in the spaces provided, and then tap OK.
5. Repeat this procedure for each of your users' Pocket PC Phone Edition devices. As an alternative, instruct your users about how to configure their devices for use with Exchange ActiveSync.

Configuring Outlook Web Access
By default, Outlook Web Access is enabled for all of your users after you install Exchange 2003. However, you can enable the following features for Outlook Web Access:
• Forms-based authentication
• Outlook Web Access compression
Forms-Based Authentication
You can enable a new logon page for Outlook Web Access that stores the user's name and password in a cookie instead of in the browser. When a user closes his or her browser, the cookie is cleared. Additionally, after a period of inactivity, the cookie is cleared automatically. The new logon page requires users to enter either their domain, user name (in the format domainusername), and password, or their full user principal name (UPN) e-mail address and password to access their e-mail.
To enable the Outlook Web Access logon page, you must enable forms-based authentication on the server. The following procedure describes how to enable forms-based authentication.
To enable forms-based authentication
1. Start Exchange System Manager.
2. In the console tree, expand Servers.
3. Expand the server for which you want to enable forms-based authentication, and then expand Protocols.
4. Expand HTTP, right-click Exchange Virtual Server, and then click Properties.
5. In Exchange Virtual Server Properties, on the Settings tab, select the Enable Forms Based Authentication for Outlook Web Access check box.
6. Click Apply, and then click OK.
Outlook Web Access Compression
Outlook Web Access supports data compression, which is optimal for slow network connections. Depending on the compression setting you use, Outlook Web Access compresses static and/or dynamic Web pages. Table 8.3 lists the compression settings that are available in Exchange Server 2003 for Outlook Web Access.


Table 8.3 Available compression settings for Outlook Web Access
Compression setting Description
High Compresses both static and dynamic pages.
Low Compresses only static pages.
None No compression is used.

When you use data compression, your users can see performance increases of as much as 50 percent on slower network connections, such as traditional dial-up access.
Requirements for Outlook Web Access Compression
To use data compression for Outlook Web Access in Exchange Server 2003, you must verify that you have the following prerequisites:
• The Exchange server that users authenticate against for Outlook Web Access must be running Windows Server 2003.
• Your users' mailboxes must be on Exchange 2003 servers. (If you have a mixed deployment of Exchange mailboxes, you can create a separate virtual server on your Exchange server just for Exchange 2003 users and enable compression on it.)
• Client computers must be running Internet Explorer version 6 or later. The computers must also be running Windows XP or Windows 2000 and have installed on them the security update that is discussed in Microsoft Security Bulletin MS02-066, "Cumulative Patch for Internet Explorer (Q328970)" (http://go.microsoft.com/fwlink/?LinkId=16694).
Note
If a user does not have a supported browser for compression, the client still behaves normally.

• You may need to enable HTTP 1.1 support through proxy servers for some dial-up connections. (HTTP 1.1 support is required for compression to function properly.)
To enable data compression
1. Start Exchange System Manager.
2. In the details pane, expand Servers, expand the server you want, and then expand Protocols.
3. Expand HTTP, right-click Exchange Virtual Server, and then click Properties.
4. In Exchange Virtual Server Properties, on the Settings tab, under Outlook Web Access, use the Compression list to select the compression level you want (None, Low, or High).
5. Click Apply, and then click OK.
Enabling POP3 and IMAP4 Virtual Servers
By default, the POP3 and IMAP4 virtual servers are disabled on a new installation of Exchange Server 2003. To enable the POP3 and IMAP4 virtual servers, you must first use the Services snap-in to MMC and set the services to start automatically. If you set the services to start automatically and then need to start, pause, or stop the services, use Exchange System Manager.
To start, pause, or stop the virtual server
1. In Exchange System Manager, right-click the IMAP4 or POP3 virtual server.
2. Select one of the following options:
• Start Starts the virtual server.
• Pause Changes the server status to paused, and an icon appears next to the server name in the console tree. To restart the server, select Pause again.
• Stop Changes the server status to stopped, and an icon appears next to the server name in the console tree.

Thanks,

[ Voor 101% gewijzigd door momania op 15-01-2004 10:05 ]

[Verwijderd]

Niet echt PNS, gaat dus naar Software Algemeen met een titelverduidelijking

[QuikSoft]

Nou volgens mij is het toch een behoorlijk impact van exchange 2003 op je server als je de default webmail wilt aanpassen naar een andere standaard en of format.
Denk aanpassingen die waarschijnlijk in je exchange administrator of dergelijk gedaan dienen te worden.
Dan valt het volgens mij toch echt onder PNS

[Verwijderd]

En, wat had je daar aan? Heb je van de dingen die daar genoemd worden wat geprobeerd, etc.?

[mutsje]

Heb je uberhaupt al mobile user geprobeerd?

[QuikSoft]

Ik heb 2 test omgevingen .
1 wy2k met exchange 2003.
* hier heb ik deze opties zoals in bovenstaand document helemaal niet.
* Waarschijnlijk zal dit liggen aan de iis versie die op wy2k staat. En deze zal dan geupgrade dienen te worden naar iis ( maar dit moet ik nog uitzoeken tenzij iemand van jullie dit al weet)

en vervolgens heb ik een wy2k3 machine waar ik exchange 2003 heb geinstalleerd en volgens het bovenstaande document heb getuned.

En natuurlijk de IIS versie 6 geunllocked.

[Verwijderd]

Voor de iPaq is Exchange/IIS ActiveSync ontwikkeld toch?
En als je daar geen gebruik van wil maken dan is oma er ook nog.

[mutsje]

bij mijn weten moet ie ook OMA gebruiker ipv OWA.

En aan iemand gevraagd die een ipaq werkend op exhc2003 heeft. Deze persoon heeft er verder niets voor hoeven doen.. geen extra templates ofzo dus.

[ Voor 61% gewijzigd door mutsje op 16-01-2004 08:49 ]

[midget]

Hier ook al enige tijd werkend.
http://exchange/oma dan in loggen met Domain\user en wachtwoord werkt goed.

[QuikSoft]

Ja klopt ,
Als je de instellingen doet zoals boven staan beschreven in het ms whitepaper , dan werkt het.
Alleen krijg ik nog steeds op mijn ipaq een foutmelding dat het geen ondersteunend apperaat is ( ipaq 5550).
Zodra ik dan voor de optie ok kies kom ik wel in mijn mail box.
Maar jah met zoun foutmelding kan ik het natuurlijk nooit in productie nemen.
haha zullen de gebruikers en mijn baas niet zo leuk vinden...

[Verwijderd]

En volgens mij was daar een update voor de .NET spulletjes voor, ergens van Microsoft.com te halen