Hi.
Does anyone know about a good time sync Software for Windows Mobile?
it is a pluss if it supports both PPC and Smartphone.
I use SynchroTime with my hermes, with no problem, but I don't know how the application will behave in a smartphone.
It's made by Dennis Grachov, and its homepage is http://gsoft.fromru.com
It's a quite good NTP client, it takes time zones and daylight savins into account, and it's also quite simple, so there's not much more to ask for in an NTP client.
Cheers
Related
Hello
I'm hoping someone might be able to help with a problem we have encountered. We would like to allow some of our XDA users to access their Exchange email accounts via the webmail interface using Pocket Internet Explorer. This all works OK but there is a slight security issue with Pocket IE on the XDA caching network credentials.
The first time the user accesses the webmail site they are asked for the username, password and domain details as we would expect. Once authenticated they get to the mailbox login and from here can access their account. No problem here.
All subsequent logins however go straight to the mailbox so the XDA seems to be caching the network credentials. The only way we have found so far to clear the "cache" is to reset the XDA. I was wondering if anyone could suggest any other way.
O2 say this is a known "feature / issue" and the solution is to upgrade our Exchange server from 5.5 to 2000.
Thanks in advance for any help.
Microsoft
The problem you are experiencing here is an issue with Pocket IE. This part of the PocketPC 2002 operating system, and it pretty much unmodified by O2 / T-Mobile etc. You will find the same problem if you use an iPAQ, Casiopea etc, so it's not something that can be specifically fixed by O" - that's really up to microsoft.
I initially contacted Microsoft Tech Support and was told that they didn't support Pocket PC and I should contact the supplier of the PDA (ie O2).
I'll try Microsoft again but in the meantime I'd be grateful for any other suggestions.
Reading other posts on the site it looks as if it might not be possible to update the version of Pocket PC on the XDA anyway.
Thanks very much for your help.
Looks like this is common problem: I am heavy user of Siemens SX56 PPC2002 (a.k.a XDA, a.k.a T-Mobile MDA). In Outlook 2002, Contacts folder in Outlook contains subfolders - to structure big (more than 3000 items) number of contacts. The same story with Inbox and Notes. ActiveSync v.3.7.1 synchronizes only top level of all folders – thus I miss biggest part of the needed data. Ok, I could manage Inbox – manually select every subfolder in ActiveSync settings, but nothing can be done with Contacts and Notes. I do not want to have mess in Contacts by copying all of it in one flat folder.
If somebody aware of the solution – please let me know.
Thats a hard one to do, but take a look at the below programs.
Outlook 2002 Add-in: Pocket Contact Synchronizer 1.2
http://www.microsoft.com/downloads/...F0-B871-49CE-9F96-712A1695E372&displaylang=EN
MightySync
http://www.mydocsunlimited.com/html/mightysync.html
For Notes you might want to take a look at HPC Notes its what I use:
HPC Notes
http://www.phatware.com/hpcnotes/hpcnotes3std.html
HTH
Hi Qman,
BIG thanks for your help. Somehow or other your recommendations help to resolve all my questions.
=Outlook 2002 Add-in: Pocket Contact Synchronizer 1.2
Good but stupid – do not syncs in both ways, simply dumps all your contact folders to one place for sync. What it means is that when you change the contact details in you device (and you’d definitely do it) it would be synced with that ‘dump place’ and would be lost after next dumping... I still look for the soft like HPC Notes but for Contacts...
HPC Notes
Superb, cannot say anything bad – it add to the notes functionality I need!!!
Amazingly, why neither M$ not 3rd party developers do not create real pocket outlook which, at least, would follow the same BD structure, to have all vital info in sync and handy????
I do believe that hundreds of heavy users would buy it...
best regards, Andrey
Great!
You also might want to check out the Big Daddy of all Pocket PC PIM's:
Pocket-On-Schedule 5
http://www.odysseyinc.com/
http://www.odysseyinc.com/site_Software/on-schedule/frameset.htm
A demo is also available and check out the review at:
http://www.pocketpcmag.com/Jan01/onschedule.asp
Later,
Hello !
Please try mNotes from CommonTime if you use Lotus Notes, it's an excellent program which never failes, with this you can add all your subfolders and have them syncronized as you like with different settings.
Patrik
Patrik,
I’m Outlook user, thus Lotus Notes is not a solution now. Thanks anyway.
Qman,
Big Daddy (Pocket-On-Schedule 5) looks rather ancient This is the most complete pocket replica of Outlook DB and seems that sync is bi-directional, but, again, several cons.:
- Hierarchical folders structure in Outlook translated to flat structure in Device. I.e. does not mater what level of depth folder was – it becomes level-1 folder. At least there is no need for Outlook Pocket Contact Synchronizer.
- Program interface is awful: I wish I had functionality and interface friendliness of Pocket Informant and DB structure of Pocket-On-Schedule. In addition, DB is different from standard pocket outlook, thus, cannot be used by any other application (e.g. Pocket Informant).
- Moreover, pity that software not developing further.
Now, best solution I see is combination of:
- Outlook Pocket Contact Synchronizer 1.2 - to grab all contacts
- Pocket Informant – to manage contacts
- HPC Notes – for notes
and last, tell me one thing does M$ in PPC2003 changed this situation? I see that sooner or later somebody would develop software I dream about.
I've the same problem !!! it's incredible that there is NOT an easy solution... Palm OS as at least two... and very simple...
however, I found that intellisync http://www.intellisync.com/palmce_trial_dldml.html is very easy and usefull, but it does not manage notes...
I've found Companion Syncronize http://www.companionlink.com/products.htm which could be a solution, but I'm not able to run it...
Other suggestion?
Stefano
from Italy
Guys,
My company's security group recently pushed out an "upgrade" to the GoodLink client on my personal Mogul Power PC that allows them to arbitrarily (in practice, during working hours) disable access to my Pocket Outlook apps, including POP3, IMAP and even text messaging clients. The GoodLink Messaging client apparently accomplishes this by replacing all shortcuts and making changes to the registry. I suspect that that is the extent of the problem because Pocket Outlook apps running during the morning lockdown period continue to function normally, but become inaccessible if shut down.
I would greatly appreciate some assistance in installing or implementing a workaround.
Thanks,
Goodbane
P.s. I am using a corporate-installed Good Mobile Messaging client (v5.0.3.23_EN) with WM6 Pro CE OS 5.2.1238 (Build 17745.0.2.3) on an HTC Mogul.
Hey Everyone -
I hate the sprint stock ROM but it is the only one that will work with Exchange 2007.
Is there any cool cooked ROM/Build that works with Exchange 2007?
Thank you
DCD 3.2.6 syncs with my exchange 2007
All of DCD's
I have used all of DCD's roms and Scott Rosler Reloaded roms with exchange 07 no issues with any of them...
owa works fine for me
I am an Exchange Administrator and I have never had a problem with new WinMo builds syncing with my Exchange 2k7 clusters. Going forward, I anticipate WinMo to drop support for Exchange 2k3 syncing. It's just not as neat, tidy, secure, fast, etc as Exchange 2k7. But that thought is very far fetched, just my thoughts.
Anyway, I have run every Titan ROM put out through XDA and never had an issue with Exchange 2k7. Of course, I use nothing by secure activesync and have full "Autodiscovery" setup with the proper exchange certificates on all the domains, matching the domain names properly, etc. So that could be part of everyone's issue with with Autodiscovery not working or the certificates not matching the domains they were issued for, etc.
djbeames said:
I am an Exchange Administrator and I have never had a problem with new WinMo builds syncing with my Exchange 2k7 clusters. Going forward, I anticipate WinMo to drop support for Exchange 2k3 syncing. It's just not as neat, tidy, secure, fast, etc as Exchange 2k7. But that thought is very far fetched, just my thoughts.
Anyway, I have run every Titan ROM put out through XDA and never had an issue with Exchange 2k7. Of course, I use nothing by secure activesync and have full "Autodiscovery" setup with the proper exchange certificates on all the domains, matching the domain names properly, etc. So that could be part of everyone's issue with with Autodiscovery not working or the certificates not matching the domains they were issued for, etc.
Click to expand...
Click to collapse
I can second everything djbeames said.
Precisely accurate. I too administer 2k7, and agree that the autodiscovery component is key.
djbeames said:
I am an Exchange Administrator and I have never had a problem with new WinMo builds syncing with my Exchange 2k7 clusters. Going forward, I anticipate WinMo to drop support for Exchange 2k3 syncing. It's just not as neat, tidy, secure, fast, etc as Exchange 2k7. But that thought is very far fetched, just my thoughts.
Anyway, I have run every Titan ROM put out through XDA and never had an issue with Exchange 2k7. Of course, I use nothing by secure activesync and have full "Autodiscovery" setup with the proper exchange certificates on all the domains, matching the domain names properly, etc. So that could be part of everyone's issue with with Autodiscovery not working or the certificates not matching the domains they were issued for, etc.
Click to expand...
Click to collapse
Two questions:
1. Do you have the setting "Allow Non-provisionable" devices checked?
2. Do you have the "remote wipe" capability enabled?
It works when they allow non-provisionable devices. Our Exchange admin tested it with me. But when he unchecks then it stops working.
Something to do with the newer ROMs not setup to allow provisioning.
And I have tried full automatic, manual and any other way you think of to test.
Thanks guys!
arifiano said:
Two questions:
1. Do you have the setting "Allow Non-provisionable" devices checked?
2. Do you have the "remote wipe" capability enabled?
It works when they allow non-provisionable devices. Our Exchange admin tested it with me. But when he unchecks then it stops working.
Something to do with the newer ROMs not setup to allow provisioning.
And I have tried full automatic, manual and any other way you think of to test.
Thanks guys!
Click to expand...
Click to collapse
I don't think it has anything to do with that. What "non-provisionable devices" refers to is: A device is considered "non-provisionable" if it cannot apply ALL security policies set by Exchange 2k7. In Exchange 2k7 SP1 Enterprise, there are a TON of settings that are NOT supported by WM 6.1, or even 6.5 (at this time). So if you are wanting to use Exchange 2k7 with ANY device at this time and provision over half the settings, you will HAVE to enable non-provisionable devices.
Here is a link to a matrix of what versions of WM support what:
http://blogs.msdn.com/jasonlan/archive/2007/12/04/exchange-activesync-policies-summary.aspx
And a technet article directly referring to what "is compatible" and what "isn't":
http://technet.microsoft.com/en-us/library/bb232162.aspx
Now. To answer your questions:
1) Yes, I have non-provisionable enabled. You have to.
2) Remote wipe is enabled on all devices. It's an integral part of Exchange 2007. I, on my personal OWN activesync profile, do not require a password. This makes it much easier for me to unlock my phone.. however, I can still do a Remote Wipe. Everyone can.
So to sum it up, you, or your exchange admin (I forgot who you said it was), have created an ActiveSync Profile with some of the settings enabled that current windows mobile (including latest 6.5 builds) do not support yet. You will have to uncheck those options, OR, simply allow non-provisionable devices. ActiveSync will still apply the policies it can, but will just skip the ones it can't apply.
Understand?
djbeames said:
I don't think it has anything to do with that. What "non-provisionable devices" refers to is: A device is considered "non-provisionable" if it cannot apply ALL security policies set by Exchange 2k7. In Exchange 2k7 SP1 Enterprise, there are a TON of settings that are NOT supported by WM 6.1, or even 6.5 (at this time). So if you are wanting to use Exchange 2k7 with ANY device at this time and provision over half the settings, you will HAVE to enable non-provisionable devices.
Here is a link to a matrix of what versions of WM support what:
http://blogs.msdn.com/jasonlan/archive/2007/12/04/exchange-activesync-policies-summary.aspx
And a technet article directly referring to what "is compatible" and what "isn't":
http://technet.microsoft.com/en-us/library/bb232162.aspx
Now. To answer your questions:
1) Yes, I have non-provisionable enabled. You have to.
2) Remote wipe is enabled on all devices. It's an integral part of Exchange 2007. I, on my personal OWN activesync profile, do not require a password. This makes it much easier for me to unlock my phone.. however, I can still do a Remote Wipe. Everyone can.
So to sum it up, you, or your exchange admin (I forgot who you said it was), have created an ActiveSync Profile with some of the settings enabled that current windows mobile (including latest 6.5 builds) do not support yet. You will have to uncheck those options, OR, simply allow non-provisionable devices. ActiveSync will still apply the policies it can, but will just skip the ones it can't apply.
Understand?
Click to expand...
Click to collapse
Yes I completely understand now. It makes complete sense. I talked to our Exchange Admin via email and he said it was corporate policy to not allow non-provisionable devices. We are a 80,000 employee company and according to him, I was the only one having the problem. So they wont change the policy just for me.
But it still makes no sense as to why my stock Sprint ROM works fine with exchange 2007. And the cooked ROMs dont. I think it has to be some sort of a registry fix on the Windows Mobile side that allows it to become provisionable. So even though Exchange 2007 has tighter security settings, it does work fine with the sprint stock WIM 6.1 ROM.
I've moved over from the Windows Mobile camp very recently (2 days now!) and thought i'd say hi
I've found plenty of info in the Hero section very helpful to get me going, and so far I'm remarkably impressed, I was expecting a much less robust solution as Android is so young. I've found it slick, fast, easy to use and very reliable - it's taken away all the pains that WM can cause!
To anyone who has yet to take the leap, I'd STRONGLY recommend it, if you're considering Android in place of your WM handset, you won't be disappointed.
Within an hour of having the device, I've updated the rom, connected it to my exchange server and gmail accounts, setup a forward from my sms to my email (for this sms problem that i've heard mention of), looked at the sky on google sky etc. and it's been a great experience so far.
Anyway, I'll see you around in various threads - no actual questions as such...but this felt the correct area!
Does Android itself provide MS Exchange support for corporate emails without any add on third party software?
I am in double minds to switch to Android but am held back only for the excellent MS Office support on Windows Mobile.
Please advice. I need to decide on this in a day.
The Hero supports exchange natively, but the software provided by Touchdown apparently provides a better corporate "experience", in terms of PIN enforcement etc.
For MS Office support, use DocumentsToGo, which is great, though the device is supplied with QuickOffice which can read many MS Office documents.
Both Touchdown and DocumentsToGo are paid apps.
Regards,
Dave
I find the exchange support sufficient with the hero (Hero version of android supports it natively, Android itself doesnt).
I'm running exchange 2007 and connected it with SSL without any issue at all. calendar, contacts, email all work perfectly fine