
|
Originally Posted by whtrbt7
Regarding heartbeat intervals and battery life, the less often you ping, the longer the battery life. This is just common sense. The battery life you save is however nominal so if you wanted to have a faster heartbeat, you're not going to be penalized heavily for it in terms of battery life. The Exchange server is also responsible for the heartbeat signature, not the device.
|
A Blackberry on my mailbox shows a virtually full battery at the end of the day.|
Originally Posted by gblinckmann
I was thinking that I was going to be saving battery life with AUTD2 (push email) over the 10-minute scheduled syncs. Given that I have a 30 minute ping time, this seemed reasonable. I'm only getting about 6 hours of battery life during weekdays if I don't make any phone calls.
A Blackberry on my mailbox shows a virtually full battery at the end of the day.Is AUTD2 really this bad for batteries, or am I missing something? I can't see anything being a "Blackberry killer" that doesn't even last one day on a charge, or is only usable by people who don't get a lot of email.... I'm using a Treo 700W on Verizon. |
|
Originally Posted by whtrbt7
@TEXMudder
On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to “Ignore client certificates.” |
|
Originally Posted by telus_guy
Me and a colleague at work both have WM2003 SE devices and our exchange server is 2003 SP2.
1. What will we miss out on by not having WM 5? 2. Will we not be able to take advantage of the 'push' capability in SP2? 3. If we cannot take advantage of the 'push' feature, will our emails have to be pulled down on a schedule rather then receiving them immediately? 4. Will we still benefit from the compression in SP 2 even though we aren't using the 'push' feature? TG |
|
Originally Posted by Eagle117
You will be able to use a type of "push" capability, but it will have to send an SMS message to your phone to tell it to sync. So if you get a lot of new messages, calendar entries, or contacts, then you will use a lot of text messaging. You could incur some pretty amazing charges like this. You can still sync directly to the Exchange server, I recommend syncing on a schedule though, like every 15 minutes or so.
|
|
Originally Posted by tmosda
Guys, I'm going crazy over setting my ActiveSync with my corporate exchange server.
I'm getting the most famous 0x80072f0d Here's what I did Went to OWA website and exported the certificate from IE. Copied the certificate to my SDA and installed it. Cleared the server connection. Rebooted and setup the connection again. Still the same error. The certificate installed on my PC says windows does not have enough information to verify this certificate Does it mean the certificate is not acceptable by AS? What am I doing wrong ![]() |
|
Originally Posted by whtrbt7
So far there is no 3rd party developed WM5 inbox subfolder notification system. I've been on the lookout for the application for about 2 years now. This issue will most likely be fixed in Photon however since MS knows about the issue.
|
here is the error:
|
Originally Posted by ronag
Thanks!! I've got things working better...but still not 100%
Direct Push is now working Activesync is working (via USB) ....but I cannot send email!! here is the error:Your message xxxxx has not been sent, and has been moved to the drafts folder. Certificates are not available for the following recipients or for one or more members of the following distribution lists xxxx. I get this error regardless of who I try to send to!! Please help.....I'm almost there....so close I can taste it... ![]() |
|
Originally Posted by that_kid
Open activesync on the device goto the e-mail options and choose Advanced, then uncheck "encrypt all outgoing e-mail messages" that'll take care of the certificate issue.
|
|
Originally Posted by ronag
Wow....that worked!!! THANKS....
now, by "unchecking" that box...what is the bad news, I'm assuming this was only a "work around" and not necessarily the ideal setup!? |
|
Originally Posted by yak86
from what I know, aol blocks the smtp server. I tried setting up an aol account once (earlier this year) using a desktop email client and was able to send mail. anyone know if its changed? (of if I'm wrong?)
|
|
Originally Posted by whtrbt7
This thread is reserved for Microsoft Exchange use, not general e-mail. Exchange I feel is a superior e-mail and PIM system. For AOL IMAP e-mail SMTP, you need to set the port number as 587 when you first create the IMAP account. AOL is a pretty crummy way to go however so I suggest that people open up Exchange accounts to replace their existing e-mail systems.
|
|
Originally Posted by Wallace Lau
You will need to add your CA's root cert into the device. If I understand it correctly, the device is still not trusting your home-brew cert (since you have your own CA, and your CA obviously is not trusted by the device by default). The same problem will also occur even if you let Exchange generate its own cert (instead of using your in-house CA), because Exchange's cert won't be from a trusted root CA either.
I have to run through the same process because I am using a GoDaddy cert on my Exchange server, and although its a public cert it is a intermediate cert backed by ValiCert, which of cause was NOT part of the default trusted Certificate Authority (ala Verisign or Thawts) in the device. Anyway, to install the cert in your device you simply need to export it from your server and run the cert in your PPC. My 9100 recognize the .cer file format and automatically imported the root cert without having to install any additional software. Anyway, assuming you know enough about Exchange and CA, here are the simplified steps. 1. Open IE and go to your OWA interface. Double click on the "lock" icon on the bottom to see the detail of your current cert, and go to "Certification Path". If more then one cert is listed on the path, write down the top item which is the root CA your server is using. It might be something like www.YourCompany.com or server.YourCompany.com depends on how you set Exchange and your CA up. 2. Go to either your exchange or GC box, open MMC (Start -> Run -> "MMC" -> Ok) and add the Certificates Snap-in (not Certificate Authority snap-in) for your "computer account" / "local computer". Alternatively you can run the MMC from your desktop and remotely open your Exchange box's computer account... but to be safe I'd terminal-service to the Exchange box and do it from there. 3. Open up the "Trusted Root Certificate Authorities" tree, and under "Certificates" look for one that is named exactly like the one you found on #1. Right click, All Task, Export and export it as a DER Encoded X.509 cert. 4. Copy the exported cert onto your iMate. 5. Open up File Explorer in your iMate, find that file, and double click to execute. It should automatically imported the cert. 6. Now try sync'ing again. Good luck. Wallace |
Thank you for your help!
|
Originally Posted by jedmb
Question: What is the best way to archive all of my folders, mail, contacts, and calendar items to import into an account with 4smartphone?
|
|
Originally Posted by jedmb
In that case, I'll probably migrate over to 4smartphone.
Question: What is the best way to archive all of my folders, mail, contacts, and calendar items to import into an account with 4smartphone? Thank you! |
|
Originally Posted by whtrbt7
I'm back after much consulting work.
Thanks to all that participate in this thread. AKU2.3 updates are getting released and all is well with the Windows Mobile world until the next major hickup. I'll take some time to answer some questions. @ronag Your exchange server may have expiring certs which expire every few days. Many companies do this for security reasons. You should be able to re-acquire the cert by accessing your account via WiFi instead of by USB. What matters most is that you have a fast internet connection to the server through an open port. Some companies issue an encryption key that you carry in your wallet that will give you an access code for the server depending on the time and date. These are normally randomly generated 128-256 bit codes. Once you connect to the server using the access key, you should be able to resynchronize data. It's also to make sure that you don't run off with company secrets or national defense secrets ![]() |
Is there somewhere I can find a guide for them? Do they need an SSL Cert? We don't use one.
|
Originally Posted by telus_guy
It certainly sounds like something changed on your server, since you are getting the same message on each of your other devices. It sounds like your company has implemented an SSL certificate in which case you will have to find out from which Certificate Authority they purchased it from, some have certs you can actually download from their site right onto your device, its that simple, unfortunately in other cases its not so simple, but there is plenty of info out there on how to do it, google is your friend.
TG |
So thank you all!!!
|
Originally Posted by ld555
While installing the Certificate an get the error "ALERT: Security permission was insufficient to update your device." Is there a fix?
I am using a decert i930 on Nextel. 2nd question: SERVER is server.companyname.com ** what is domain ... is it the same. Without the CA installed ... whenever I Activesync ... it returns me back to the password field. It is like I put in the wrong Password, but I know I did not put in the wrong password. Thank you in advance ... |
|
Originally Posted by blackdoc
Has anyone managed to get the email certificate to work on the Treo 750 running WM5?
I have an exchange server synching OTA and had a TyTn working without a lot of problems, I am able to install the Personal, Intermediate and Root Certificates but when I create an email, if I try to sign or encrypt, I get error msg "The Message Cannot Be Signed/ or Encrypted" What am I doing wrong? I can see all the certificates that I have installed in the respective stores on the Treo, just like on the TyTn, but the email client does not want to use them to sign, encrypt or decrypt |
|
Originally Posted by MobileGonzo
The Microsoft Marketing Hype is misleading. Secure e-mail is supported, but only with a hardware based card reader. Soft certs are not supported. At TechEd last year, they showed a picture of the device. Basically a PDA with a Smart-card reader rubber-banded to the unit and interfaced through the SD slot.
![]() |
|
Originally Posted by Islanti
Has anyone actually used S/MIME signing for email on their Windows Mobile 5 device and Exchange 2K3 SP2? I recently upgraded to a WM5 AKU3 Smartphone and one of the features I was looking forward to using was the S/MIME signatures and encryption. When I try to send a signed email the device says "The message cannot be signed because you do not have a certificate for sending signed email. Insert a smart card with the certificate."
I have selected the appropriate certificate via Activesync -> Configure Server -> Next -> Next -> (highlight E-mail) -> Settings (from menu) -> Advanced (from menu) -> Choose Certificate (from menu). I have seen the Jacco de Leeuw page, which offers tools for importing a pfx certificate into Windows Mobile. This seems to work although WM5 doesn't provide much detail on the status of a particular certificate (such as thumbprint data or whether the private key is assocated with the certificate). I also tried the PFX -> OpenSSL PEM method suggested on Jacco's page (under the crtimprt section). This also seems to work fine but no change. I have a Thawte freemail certificate, which requires an intermediate certificate to be installed. I created the necessary cab file to import this. There's no way I know of to verify this, but importing the root CA the same way seemed to work fine. I have my Thawte certificate working fine from the desktop. I have published it to the Exchange GAL via Outlook. I'm stumped as to what else I could possibly do to enable this feature! |
|
Originally Posted by Islanti
Has anyone actually used S/MIME signing for email on their Windows Mobile 5 device and Exchange 2K3 SP2? I recently upgraded to a WM5 AKU3 Smartphone and one of the features I was looking forward to using was the S/MIME signatures and encryption. When I try to send a signed email the device says "The message cannot be signed because you do not have a certificate for sending signed email. Insert a smart card with the certificate."
I have selected the appropriate certificate via Activesync -> Configure Server -> Next -> Next -> (highlight E-mail) -> Settings (from menu) -> Advanced (from menu) -> Choose Certificate (from menu). I have seen the Jacco de Leeuw page, which offers tools for importing a pfx certificate into Windows Mobile. This seems to work although WM5 doesn't provide much detail on the status of a particular certificate (such as thumbprint data or whether the private key is assocated with the certificate). I also tried the PFX -> OpenSSL PEM method suggested on Jacco's page (under the crtimprt section). This also seems to work fine but no change. I have a Thawte freemail certificate, which requires an intermediate certificate to be installed. I created the necessary cab file to import this. There's no way I know of to verify this, but importing the root CA the same way seemed to work fine. I have my Thawte certificate working fine from the desktop. I have published it to the Exchange GAL via Outlook. I'm stumped as to what else I could possibly do to enable this feature! |
|
Originally Posted by whtrbt7
Try turning off advanced network functionality in Start --> settings --> connections --> usb to pc.
If you are getting the error when you are connecting via EVDO, you need to perform a hard reset to the Q. |
|
Originally Posted by blackdoc
got it to work w the help of Jacco, use PFXimport, NOT p12 for WM5 it works!!!
![]() |
|
Originally Posted by kxgard3
Can someone point me in the direction of a good guide to setting up a Exchange Server, and then configuring it for Direct Push?
|
|
Originally Posted by signs
There is a lot of reading, but here ya go:
http://www.microsoft.com/technet/it...le/default.mspx |
|
Originally Posted by kxgard3
Thanks
Right now I just have Server 2003 installed, so I guess I need to get exchange on the machine. |
|
Originally Posted by seaneraz
I previously had activesync setup correctly without Push Email, using activesync over GPRS and WiFi.
I recently upgraded the ROM and Exchange SP2 and I am attempting to get them to activesync, but no dice. I have created and installed the nself signed cert with out issue. Whenever I attempt to activesync i get an error about obtaining the network certificate w/ the support code 0x85030027. I have verified the FQDN on the cert, I have verified the access to the OWA and OMA websites, I have verified that those site are using the specified cert. Can anyone bring clarity to this error? Thanks a ton! ![]() |
vBulletin Copyright ©2000 - 2009,
Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2009
- Created by Stefan "Xenon" Kaeser