How to setup Exchange email on PocketPC PPC-6700

Hi, first let me say that my knowledge of PocketPC’s is very limited and so is my knowledge of remote exchange access.  This makes for a dangerous combination when I try to make the two work together.

From what I have read, there is wireless access to an Exchange server from a PPC.  I’m not sure of the difference in OWA and OMA or any other method of obtaining email remotely.  I do know that our server, SBS 2003, is running exchange.  From home, I can login my email my entering http://companyname.net/exchange.  After entering my user account and password, my email shows in OWA.  For this problem, the server name is Server01, external domain is Companyname.com, internal domain is Companyname.net.  (Would OMA be a better solution? Why/Why not?)

From the PocketPC, if I’m connected to the cradle and synced with my office computer, I can also get to my email via OWA.  If I remove the PPC from the cradle, I cannot get email.  I do have cellular access to the internet.

Can someone please help me understand how to connect to my Exchange server using my PPC, and get email.  I would like to use the cellular wireless connection for email and if possible, have notification when new email arrives.  Thanks!
RepicheepAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
You have three options.

1. OWA - that is accessed via /exchange on the end of the URL that you use to access the server. Full graphics which means it can be a little slow and will use up a lot of data.
2. OMA - that is accessed via /oma on the end of the URL. Basic, text only. You can load this from a standard web browser and see what it looks like.
3. Exchange Active Sync. This lets you synchronise Inbox, Contacts, Tasks and Calendar. EAS will be the backbone of the push technology - when it eventually appears.

All three really require an SSL certificate to deploy securely.

To access it from outside, you will need to have a valid host, this is what you get the certificate on and is entered in to the software.
I would not advise using domain.com - but instead a host in the domain - so host.domain.com - that will let you get a valid certificate and access everything over the Internet.

Get it working with OWA first, then move to OMA and finally EAS.

Simon.
RepicheepAuthor Commented:
Hi Simon,

Thanks for the information.  I have added a certificate to the server and I can get email via http://company.net/exchange.  It askes you to accept the certificate and then I get the OWA web page to login.

When I type https://company.net/owa, I get a certificate request, then after proceeding, I get a page not found.

With I type https://company.net/oma, I get a certificate request, then after proceeding am immediately asked to login.  After login, I get the error "A System error has occurred while processing your request".

Any thoughts on what I am doing when I use /exchange?  Somehow it's appears to be using OWA, but I'm not sure why /owa doesn't work.

Thanks for any help.

On a different note, one thing that did change unexpectedly is that now our email access through the SBS Shared Portal has changed to OWA.  I'm not sure how that works and do you have any idea how to change that back?

P.S.  Do you know of any good books or papers that explaing all of this to people like me that are mobile/exchange challenged?
SembeeCommented:
OWA is Outlook Web Access - which is /exchange
The URL /owa doesn't actually exist in this version of Exchange.

The asking for acceptance of the certificate will cause a problem with the handheld devices. You should use a purchased certificate to ensure compatibility.

The System Error is quite common.
In IIS Manager, make sure that integrated authentication is enabled on the /oma virtual directory.

No idea on the SBS portal I am afraid, I don't get involved with SBS very much.

Simon.
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

RepicheepAuthor Commented:
That explains the /owa issue...  :)

Can you explain how the certificates will cause a problem with the handhelds?  It appears to work, but I would like to get that fixed before it creates more problems.

I have enabled integrated authentication on the /oma directory.  I unchecked basic authenication (correct?).  After my first login, I recieve another login box and then the same error.  Not sure why?

I'm finding what SBS is very unique in some ways.  This is not really an issue, everyone can still get email, just through a different interface.  :)

Thanks for all the help!
SembeeCommented:
Looking at my production system I have both integrated and basic authentication enabled on the OMA virtual directory.

Certificates can cause a problem because they work on a process of trust. Inside your web browser there is the root certificates for a number of certificate providers. There is a smaller number of root certificates in the handhelds.
When you try to access a site using a certificate that hasn't been issued off one of these trusted roots - you get the prompt.

It is possible to install the root certificates on to the Pocket PC devices, but it isn't always that easy, especially if you are installing your own root certificate.

Similarly with the deployment of RPC over HTTPS you would have to install the certificate on every machine that is using the facility. That would still not stop the certificate prompts when anyone accesses OWA from a machine that doesn't have the certificate installed, and certificate prompts are one of my pet hates - they look unprofessional and don't actually increase the security of your network in the way that they should.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RepicheepAuthor Commented:
Simon,

Well, the email on the PPC device is now working.  I am assuming that it was the authentication issue.  Thanks for the help in getting this to work!

I gather from your note that in this instance, certificates are more of a problem than a necessity.  It sounds like I need to install our certificate on the PPC device (that's going to be more research).

From my desktop, it gives you an option to install the certificate.  After the install, I still receive the certificate pop up.  Any thoughts on why?

Thanks again!
SembeeCommented:
Certificates can certainly make the deployment more complex, but I wouldn't consider deploying this type of solution without a certificate. I don't want my credentials going across the internet in the clear.

If you are using home grown certificates then the management of the certificate becomes more complex. What you need to weigh up is how much it is costing to manage a solution using home grown certificates, versus using a solution that uses a purchased solution. A certificate from RapidSSL costs US$70 ish a year and their root certificate can be easily imported in to a Pocket PC. Or you could purchase a certificate from one of the bigger vendors who have their root certificate already in the Pocket PC, then there is nothing to deploy.

As for the certificate prompt on your desktop - check what it is prompting over. It might be the URL is different from the one on the certificate. If that is the case then you will always get a prompt.

Simon.
RepicheepAuthor Commented:
I will look into RapidSSL and see what deployment issues there may be.  Otherwise, maybe go with a bigger vendor just to make things easy.

Yes, the certificate prompt on my desktop is because the site name is different.

Thanks for all the help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.