Check that it is listed in the "Certificates". This is control panel application (!). In order to install the certificate you need to save it somewhere and open from the file browser.
P.S. I can send you the screenshot of "Certificates" application if it is not clear what am I talking about.
No, I understand what you're taking about. The certificate is installed in the Cert Manager. Just doesn't work, and the error message is useless in my opinion.
Thanks anyway.
Edit: Ok, I don't know what happened, but I actually saved the .pem file to the device first this time before opening the certificate manager (instead of opening the certificate manager directly from the browser) and it seems to have imported it and it works to connect to Exchange. Apparently if you open the cert manager from the browser (by navigating to a .pem file) it doesn't import it correct (even though the cert is listed in certificate manager). So now things are cool.
Maybe I missed the information, but when the update fixing Exchange 2003 could be available? Thank you.
Yes, I also would like an idea of when the Exchange 2003 fix will be available, I also couldn't see anything posted here. Some idea would be really really appreciated. Thanks for your time.
I am not sure that having 2 different packages can help much here. The simpler way to implement and maintain it is to have an option somewhere in the UI "support provisioning". If it is turned on, device is provisionable. Otherwise it is not.
Yes, this sounds more logical. Just didn't think it would be possible to do this way.
Originally Posted by
Even if company has installed the package with provisioning support to the user, he or she can easily remove it and install the version without this support.
As long as the device doesn't have provisioning support enabled (not depending on how it's implemented), server shouldn't allow the sync is it requires this feature?
But my point isn't that how it should be implemented etc. Just that this feature would be important to have somehow to many users.
Edit..
But anyway, guess I'll need to file in a bug report on this. I'll just wait untill I'll have the device in my hands.
Edit: Ok, I don't know what happened, but I actually saved the .pem file to the device first this time before opening the certificate manager (instead of opening the certificate manager directly from the browser) and it seems to have imported it and it works to connect to Exchange. Apparently if you open the cert manager from the browser (by navigating to a .pem file) it doesn't import it correct (even though the cert is listed in certificate manager). So now things are cool.
Thanks!
Hi Hypnotik,
where did you get the .pem file from? i went to Cert Manager under settings in the N900 but cannot seem to locate the file.
where did you get the .pem file from? i went to Cert Manager under settings in the N900 but cannot seem to locate the file.
you can get the certificate from your Exchange Administrators.
if your company provides outlook web access, you could also try getting the certificate from there. browse to your outlook web access page, click the certificate icon in the status bar, click "show certificates", "details", "Export". this provides you with said .pem file, which you then copy to the N900 and open in the file (!) browser.
after looking at the cert's in my E90 and noticing a cert for my mail, i realised this could be the problem.
that being said the files (downloaded version (ure post) and the file on my E90 are very different).
i tried to follow the steps you mentioned i opened the file from File manager, however it didn't give me the option of doing anything with it i.e. saving it to the correct location etc.
after opening and closing the file i looked in the cert manager but still no file.
I am sure many are in the same boat, but having migrated from N97 to N900, the lack of ES2003 support is really disappointing. I now have my N900 back in its box and I am using the N97 as I really, really need email access.
I was using RoadSync on my N97 but have used MfE on my old E71 and really thought this would be possible. Any idea when the new firmware will be ready so I can avoid selling the N900 on ebay?
i tried to follow the steps you mentioned i opened the file from File manager, however it didn't give me the option of doing anything with it i.e. saving it to the correct location etc.
i don't have a N900 yet, so i'm not sure how exactly it's supposed to work, but vitaly - one of the MfE developers - said in this thread that the maemo file manager is used to import certificates.
see here and here.
edit: those posts were actually answers to posts from you, so i guess you have already read them
if your company requires provisionable devices, then it's not possible to sync the N900.
it's not an issue of the MfE client, it has to do with Maemo/Linux being too open to be able to enforce the needed settings to fullfill the requirements.
this will probably change with Maemo 6 and it's DRM-Mode, but until then, you're out of luck.
