Fonte: http://www.gizmodo.com.br/conteudo/sincronizacao-completa-com-exchange-chega-ao-android-desenvolvedor-particular

Falando em Android, você que é fã do G1 talvez se lembre que o telefone foi lançado com zero-vírgula-zero funcionalidade com o Exchange, irritando mais de um executivo (pelo menos uns dois ou três). Os mestres do Android disseram que a plataforma suportaria de bom grado a integração com o Exchange feita por desenvolvedores particulares e veja só, ei-lo! semana passada a NitroDesk lançou o TouchDown, “a primeira solução para acessar o seu e-mail no Exchange Server, seus contatos e o calendário em aparelhos móveis com Android”.
Talvez você se lembre que há um mês eu falei sobre um aplicativo gratuito de sincronização de contatos para o Android. O TouchDown, que custa 30 dólares, é um pouco mais extenso:
•    Funciona com Microsoft Exchange Server 2007 SP1 e a “maior parte” dos hosts online do Exchange
•    Você pode compor, enviar, responder, responder a todos, encaminhar e deletar e-mails
•    Você pode acrescentar, deletar ou editar contatos do telefone, atualizando nas duas vias para a sua conta Exchange
•    Ele não requer um aplicativo rodando no seu computador para transmitir as coisas para o telefone.
Eis algumas telas:

Nós provavelmente não testaremos o aplicativo logo de cara, mas se você chegar a rodá-lo, favor comentar aqui embaixo para o benefícios dos demais.

Fonte: http://msmvps.com/blogs/nunoluz/archive/2008/04/07/securing-mobile-devices.aspx

Por nunoluz

Exchange Server 2007 as added some cool new features for Windows Mobile Devices, like managing your Out Of Office and Fetch E-mail.

But also it also helps IT Administrators to secure company information on the devices and control potential security risks by enabling the new Exchange Activesync Mailbox Policies.

Now with Service Pack 1 you can do even more: not only the existing policies have been enhanced, but also new security policies have been introduced.

These new policies are divided into three major categories: Device Control, Application Control and Network Control. In order to implement these policies, not only you will need an Enterprise CAL, as well as a Windows Mobile 6.1 device.

Some of these policies include camera lock, application disallowance or even Wifi deactivation. 

Applying them couldn´t be easier: all you need to do is create a new EAS policy and apply all your company's IT policies, and apply it to a user's mailbox. Of course that the user must have a Windows Mobile 6.1 device, or the device will cease to synchronize with the Exchange Server.

After the device synchronizes it will ask to reset in order to apply the new policies.

As soon as it reboots, the device is now secure and IT policies will have been applied.

If you are interested in learning more about the great new features for Windows Mobile devices that Exchange 2007 has to offer, visit this Blog frequently

Fonte: http://msmvps.com/blogs/nunoluz/archive/2008/04/09/step-by-step-adding-ssl-certificate-to-exchange-server-and-windows-mobile-devices.aspx

Por nunoluz

In this article I will show how you can get and install an SSL certificate on your Exchange Server and on Windows Mobile devices.

SSL certificates provide e-mail connection encryption beetwen the Exchange Server and Windows Mobile devices, protecting important and confidencial corporate data from unwanted access.

Some of my clients have been facing difficulties in choosing the correct certificate authority and in choosing whether they should use self signed certificates or certificates from third party CA's.

While self signed certificates are free, you should consider these only in two possible circumstances: either for testing, or for providing internal services.

Third party certificates can be used in most cases, but especialLy if you or your company are providing for instance e-mail services to external clients.

STEP 1: Preparing the certificate request

Note: All of the following steps and operations must be performed using the administrator account.

Your first task is preparing the certificate request using Internet Information Services.

1- Open IIS and expand the tree until you find the "Default Site" or the site where you installed the Exchange Server services;

2- Right click on the "Default Site" and choose "Properties";

3- Next you must go to the "Directory Security" tab and click on "Server Certificate";

4- Now the request wizard should come up and you will choose the option "Create a new Certificate" and press "Next";

5- On this screen choose "Prepare de request now, but send it later";

6- Click "Next" again and write the name of the certificate (this name should be easy to identify);

7- Click "Next" again and enter your company name and department wich will help further on identifying  the certificate and its rightful owner and click "Next";
8- This step is critical: here you must enter the valid DNS of your server. Remember you must have the DNS entries that go with the DNS name you are entering here otherwise your device will not sync.

9- Click "Next" and in this screen you must choose your location and country;
10- Finally you name your certificate request and save it in your hard drive and click, review the request information and click "Finish"

STEP TWO: Submit the certificate request to a Certification Authority
There are several CA's availiable on the market nowadays, so you are free to try your own choices. I mainly use one or two companies which I learned to trust. One of them is Rapissl, that has a great certificate 30 day free trial you can test-drive for yourself.

Note: The following examples are based on their certificates, so if you use another CA some steps might be different.

1- Go to www.rapidssl.com and choose "Free SSL" / "Try before you buy" and afterwards click "Free Trial".

2- Confirm the the selected FreeSSL product and click "Next".
3- On this next window you should see a screen where you are asked to insert the certificate signature request. In the "Insert CSR"  you should paste the code generated by IIS when you first submitted the certificate request. Therefore you must browse to the location where you saved certificate request, which by default is named "certreq.txt".

4- You must open the txt file and copy all of its contents to the RapidSSL form:

5- Once you submit this form, a confirmation e-mail is sent to the domain administrator, so its important that you have access to one of the e-mail accounts suggested. Tipically the administrator@domainname.domain.
6- One of the most interesting steps of this CA for verification of ownership and for security reasons is the fact that you must recieve an automated call in which you must provide a code that is generated on the rapissl site.
7- After this step a security e-mail is sent to verify the ownership of the domain, in which you or the domain admin must confirm to agree to the certificate creation.
8- If all validation and security steps are perfomed correctly you should recieve an e-mail containing the certificate. Some CA's might send you a link to download the certificate or attach the certificate to the e-mail. Rapidssl in this service as opted to include the certificate on the body of the message, so you should simply copy the text and paste it onto a new text document using for example notepad. When you save the document you must specify the type of the document as  *.cer file type.

THIRD STEP: Importing and activating the certificate

Now that our certificate is in our hands we must apply it to the Exchange server. In order to do so, we must first import the certificate and then activate it in our system. There are two ways of doing this: one is using IIS, the other one implies the usage of cmdlets and Exchange Management Shell. I will show how to do this using the latter.
1- Fisrt you must open EMS: "Start, All Programs, Microsoft Exchange Server 2007", choose "Exchange Management Shell".

2- Once the command line is visible type the following:

Import-ExchangeCertificate -Path "c:\certnew.cer"

and:
Enable -ExchangeCertificate -Thumbprint [thumbprint] -Services:"SMTP,IIS"

In order to know the Thumbprint, you should double click on the certificate file and go to "Details" and then "Thumbnail". Then you just copy thumbprint with a simple  CTRL+C and paste it on the command line.

If all goes well you should see something like this:

3- In order to check if all went well in the previous steps you can go to IIS and see if the certificate as been correctly installed and is now active fot the selected website.

Another way t check is by opening Internet Explorer and navigate to your domain. If all is well it will not open. So you must add an "s" to the url so that it reads "https:\\" this indicates you are accessing a website using a secure connection.

FOURTH STEP: Exporting the certificate
Now all we have to do is obtain and apply the certificate on the Windows Mobile device. So we must get a certificate that will work on Windows Mobile device:

1- Go to "Start", "Run", and write "mmc".
2- On the new management console go to "File", "Add/Remove Snap In...".
3- On the Add Standalone Snap-in Windows choose "Add" and select "Certificates".

4- Choose "Computer account" and click "Next"

5- Choose "Local Computer", click "Finish" and then "Close" and "OK".

6- On the certificate window browse to "Trusted Root Certification Authorities" and locate the certificate you installed.

7- Right-click on the certificate and choose "All tasks" and "Export..."
8- The Certificate Export Wizard should open. Now you must slect the type of certificate to create. Choose PKCS #7" with the extension .P7B.
9- Do not forget to select the option: "include all certificates in ther certification path if possible"

10- Click next and save the certificate.

FIFTH STEP: Installing the certificate on the Windows Mobile device and configure EAS
We should now copy the exported certificate to the device, either by including it on a CAB installation file, sending it via e-mail or copying it to a storage card.

1- Once the certificate is on the device you must tap on it in order to install the certificate onto the device's certificate library.

For Windows Mobile 6 and 6.1 certificate installation is quite simple and after taping the certificate you should see the confirmation box that it has beem installed successfully.

Our last task is configuring Activesync on the device to synchronize with our Exchange server:

You should have no problem sycing information with your server using a secure connection.

The process is very much the same for self signed certificates, with the exception that the CA should be in you organization and you must install Certification Authorities on one of your domain servers.

Fonte: http://blogspot-page.blogspot.com/2008/04/how-to-connect-your-windows-mobile.html

Microsoft Exchange servers offer a lot of a features that regular POP3 and IMAP email servers do not. It was even a consideration when I was deciding which company I wanted to work for.

Exchange servers have a number of features such as Outlook Web Access and Push Email, that help us have greater access to our email. Push Email helps us get email to our devices as soon as it hits the server.

If you have access to both an Exchange server and a recent Windows Mobile device (post WM5), you can get email to and from your device better than what is possible with any other method.

This article will show you how to connect your Windows Mobile 5 device to an Exchange server. It is not very hard to get up and running, but there are a few terms which are a little confusing.

This article is written for Windows Mobile 5, but I hope it will assist people with Windows Mobile 6 devices also.

Test Setup:

• I will be using an Ipaq rw6828 running Windows Mobile 5.
• I will be connecting to an Exchange Server 2003.
• No additional software is required to make this work.

While Exchange servers can probably be set up in various ways, I can only go from the experience I have had. A few years back, when our new Exchange administrator said that he couldn’t figure out how to connect his Windows Mobile device to the server, I had already been on it for a week. I passed on my documentation then and it has been used around the company ever since.

Find out your server information:

The amount of times friends have asked me to setup their email connections without them knowing server names, usernames and passwords is numerous, making my job just about impossible. Before you start attempting this, collect the following information.

1. Your username
2. Your password
3. Your domain (often your company name)
4. Outlook Web Access address (not the Exchange Server)

If you are unsure, I am sorry to say… you will need to contact your help desk or server administrator.

Setting it up:

Exchange and Windows Mobile devices were designed to work together and there are 3 ways that I know of to get the two to talk to each other.

• Setting up the connection using ActiveSync
• Setting up the connection using WMDC
• Setting up the connection using your device

No matter which of the options you use, the settings will filter across to the other two during a sync. All you need to do is find the setup you feel most comfortable with. Each option is fairly straightforward and the results are identical.

If you are on an expensive data plan, you are probably best to take a WMDC or ActiveSync option as the initial data costs will be much lower than syncing directly through a GPRS link.

All the images below can be enlarged by clicking on them.

Setting up the connection using your device:

Ensure you have a wireless Internet connection of some type on your device, and make sure it is active.

Open up ActiveSync on your device

Tap “Menu”

Tap “Add Server Source…”

Enter in your Outlook Web Access address as your server name. There is no need to put the http:// or https://

Leave the SSL box ticked – you may want to toggle this if you have problems.

Tap “Next”

Enter your username, password and domain.

Tick “Save Password”

Tap “Next”

In this window, you get to choose what you want to sync. By default, all the boxes are ticked. If you want to play with these settings, press settings. You can’t do any damage here so have a play.

The only thing I would be careful about is syncing all your email. There probably won’t be enough space on your device and you are unlikely to ever look at it. Take a minimalistic stance.

Tap “Finish”

Now all the settings are done.

Open up ActiveSync and select “Sync”. You should not be connected to WMDC or ActiveSync for this step.

When the sync is completed successfully, disconnect your device.

Scroll down to the testing area.

Setting up the connection using ActiveSync:

Start off by connecting your device to ActiveSync. If you have not done this yet, read this Inspect My Gadget article which shows you how to connect your device to ActiveSync via Bluetooth. If you are using USB, install ActiveSync and plug in your device.

Go into tools and select “Add Server Source…”

Enter in your Outlook Web Access address as your server name. There is no need to put the http:// or https://

Leave the SSL box ticked – you may want to toggle this if you have problems.

Enter your username, password and domain.

Tick “Save Password”

Click “OK”

In this window, you get to choose what you want to sync. By default, all the boxes are ticked. If you want to play with these settings, press settings. You can’t do any damage here so have a play.

The only thing I would be careful about is syncing all your email. There probably won’t be enough space on your device and you are unlikely to ever look at it. Take a minimalistic stance.

Click ”OK”

Now all the settings are done.

Get the sync rolling while you are still connected. This will be quicker (and probably cheaper) than using a GPRS connection.

Open ActiveSync on your device and tap “Sync”. You should see that all the data is being transferred to your device. When the sync is completed successfully, disconnect your device.

Scroll down to the testing area.

Setting up the connection using WMDC:

Start off by connecting your device to WMDC. If you have not done this yet, read this Inspect My Gadget article which shows you how to connect your device to WMDC via Bluetooth. If you are using USB, install WMDC and plug in your device.

Under Mobile Device Settings, Select “Sync wirelessly with Exchange Server”

Enter in your Outlook Web Access address as your server name. There is no need to put the http:// or https://

Leave the SSL box ticked – you may want to toggle this if you have problems.

Enter your username, password and domain.

Tick “Save Password”

Click “Set Up”

The final step is to configure what we want to sync. In the main window of WMDC, under Mobile Device Settings, select “more>>”

Select “Change content sync settings”

In here tick what you want to sync. Most importantly your contacts and email.

Click “Save”

Now all the settings are done.

Get the sync rolling while you are still connected. This will be quicker (and probably cheaper) than using a GPRS connection.

Open ActiveSync on your device and tap “Sync”. You should see that all the data is being transferred to your device. When the sync is completed successfully, disconnect your device.

Testing:

To test that everything is working correctly, try deleting a few emails and/or sending yourself an email from your desktop computer.

Enable your Wifi, GPRS or similar connection on your device.

Open up ActiveSync on your device and select sync.

You should see that the messages have been deleted and that you have received a new email. It may take a minute or two for the email to come in, but as I tested this out, the message arrived on my device around 10 seconds before it reached my desktop.

Conclusion:

I hope that you have had success in connecting to your Exchange server from your Windows Mobile device. You are now experiencing some of the latest technology available, and making the most out of your device.

I would love to hear what any Windows Mobile 6 users have to say about this article.