Exchange server 2007 still on version 8.1 even after applying sp3

hello,
I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.
I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.
any idea about this issue?
thank you

Hi
As is well known, you
must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.
According to your description, I suggest you should check the rangeUpper value by using ADSI Edit . If the value was 14625. This indicates
your schema is at Exchange 2007 SP3.
Here is the article for your reference: https://supertekboy.com/2014/05/01/check-exchange-schema-objects-adsi-edit/
Also you could re-install the patches in the following links .
Please download and install these patches from here:
Exchange Server 2007 Service Pack 3: https://www.microsoft.com/en-gb/download/details.aspx?id=24111
Exchange Server 2007 SP3 Update Rollup 10 : https://www.microsoft.com/en-us/download/details.aspx?id=36708
Hope it’s helpful to you .
Best Regards,
David

Similar Messages

Hi, in our Enterprise environment, we have a single mac with Mavericks version 10.9.2 and Office for Mac 14.4.1. When setting up outlook, we are trying to connect to a mailbox on exchange server 2007.

Hi, in our Enterprise environment, we have a single mac with Mavericks version 10.9.2 and Office for Mac 14.4.1. When setting up outlook, we are trying to connect to a mailbox on exchange server 2007. We put in the EWS details in the server field since our autodiscover function is not functioning. But still it doesn't work. There are no errors, no popups. We turned on the logging and in the logs, it says a error of -3259. We are stuck and any help will be really appreciated.

I have a customer experiencing exactly the same issue. Their computer is running Windows 7 Pro with Office 2007 SP3. After seemingly exhausting all troubleshooting options, I backed up their data, formatted the hard drive and performed a clean install of
Windows and all their applications. It didn't solve the problem!
What's strange is the customer also has a laptop computer, running the same version of Outlook, and that doesn't experience any problems connecting to Office 365 on the same network.
My next step is to send the customer a new ADSL modem/router to try.
I have another customer on Office 365, also running Outlook 2007, and they also experience issues with emails sitting in the outbox while Outlook displays the status message “Outlook is trying to retrieve data from the Microsoft exchange server outlook.office365.com.”
In this case Outlook doesn't freeze/stop responding, like it does for the first customer I mentioned.

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

Need Documentation on how to intehrate Exchange server 2007 with SAP portal

hi,
i need some documentation on how to integrate microsoft Exchange server 2007 with SAP portal.
can anybody help?

Hi Payel,
Pls check the links below..
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/7a/ec015c8446d447a83776d40f31c84f/content.htm">Link</a>
Note : As specified in the document, only the following versions of Microsoft Exchange server are supported:
● Exchange Server 2000
● Exchange Server 2003
Regards,
Venkat.

M4E with N73 - MS Exchange server 2007

Hi Guys,
maybe I am stupid, but I can't seem to get this thing to work,
I have installed mail for exchange 2.3, finally the security setting is showing, I have approved the certificate but still I am getting the very general :
"Error in Exchange server. try again later."
to explain my steps:
1. configure the connection to use the HSDPA/Cellular link.
2. hostname: owa.domain.com , username and password.
server is Exchange server 2007 and configured behind an ISA server. OWA 2007 from a browser works fine.
please any assistance would be great, I don't even know how to approach it anymore.
thanks in advance,
Badsyntax (Simon)

Hi Imran,
As per my information Webcenter Suite 10.1.3.2 does not have any direct integration capability with MS Exchange Server due to DEEP LINK LIMITATION. Only possible work around is go for External Application SSO registration and then render that URL in IFRAME.
As far as WEBCENTER INTERACTION is concerned i think its seprately licensed and eventhough it's free you need extra Hardware to Install and Configure.
Regards,
Vindhyachal Sharma

HELP - Exchange Server 2007 Transport Rule Issue

Hi all,
sorry if here is not the place to put my question but I did not find another forum, so if anyone can help me I appreciate.
- I have an Exchange Server 2007 SP3 environment with 1 MBX Server and 3 CAS/HUB Servers.
- I have created a Transport Rule that said:
"all emails that have @test.com in BCC field are dropped off except one group can send" .
The issue is the rule doesn´t work.
Anyone can help me, please?
Thanks in advance.
Luiz

The Exchange previous versions forums are here:
http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hidden Contact Subfolders are visible on iPhone after sync with Exchange Server 2007

Hello,
We have encountered an issue where synchronizing the iPhone with Contacts from an Exchange Server 2007 mailbox, causes hidden contact subfolders (from Outlook) to be visible and appear in the Groups list in the Contacts App on the iPhone. This does not occur with Exchange Server 2010 mailboxes.
We have a 3rd party application that creates hidden subfolders in the default Contacts folder on Exchange Server 2007 mailboxes. The hidden folders do not display in the Outlook client, Blackberry or on an Android phone. We did see that they were showing up in Outlook Web Access until we applied this Microsoft Exchange Server 2007 Service Pack 3 Rollup 2 patch unto the Exchange server:
http://support.microsoft.com/kb/2210042 - A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment.
After the patch was applied, the hidden contacts do not show up anywhere else. However, when we synced the mailbox to an iPhone and synced existing contacts, all of the hidden folders appear in the Contact Groups list. Is there a way to hide the hidden sub contact folders on the iPhone and prevent them from appearing in the Contact Group lists?
Any help provided would be most appreciated.
Thanks and Best Regards

Hi SBuchan,
I have an open case with Microsoft about it. It is an issue with ActiveSync in Exchange 2007 that sends the hidden objects. Microsoft tried to resolve this in Exchange 2010 by sending a delete message after sending the hidden objects to remove them from the device. Am awaiting to see if they will approve a design change to Exchange 2007 ActiveSync to prevent the synching of hidden objects.

Exchange Server 2007 shows email as "Receive" but not "Deliver"

Hi Guys
We have Exchange Server 2007 inside of a SBS 2008 set up.
One specific email from a regular sender wasn't received by the recipient. The recipient is used to receiving messages from this sender and the email is not hiding within Outlook.
Exchange 2007 mail tracker shows the email was received, but that's it. Nothing has happened to the email after that. Normally we'd see a "Deliver" report, or possibly a "Fail", but always something to show the email has been actioned
in some way.
The queues are all empty.
So, this one email has disappeared into the ether of Exchange! So far as I can see, this is the only email with only a "Receive" notification. All others have something else immediately following the Receive.
The Server has GFI anti-spam installed, but that hasn't seen the email either, because emails are collected by Exchange before being passed to GFI. In this instance it hasn't been passed, or returned to the sender as undeliverable. It just seems
to have been eaten.
Would anyone have any sensible suggestions on where to start kicking this email back into life?

Hi Simon
Apologies for the late response, but I only get to this client once a month.
1. Did the sender get NDR? ~ No
2. Let the receiver check the email via OWA and see
whether the email is available. ~ Still not available
3. Use MFCMAPI to check the user mailbox, can you
find the missing email? ~ I haven't yet worked out what is MFCMAPI or how to use it to check, but I suspect that as the Exchange email tracker doesn't have any actions after "Receive" that it cannot have sent the email on to the user's mailbox or rejected
the email as non-deliverable.
The client isn't too willing to expend too much effort
/ cost on this issue which does appear to be a one-off glitch, but I am interested in resolving it for myself as I haven't heard of this problem before.
Thanks for the interest,
Michael D

Exchange Server 2007 OWA users can receive email but can't send

Hi,
I have an Exchange server 2007 in an SBS 2008 environment with POP3 connector configured and working fine , smtp send mail connector configured.
Now users can connect to OWA, receive email but cant not send.
smtp connector works fine from Outlook client. Tried to track the emails from exchange server management console and I get the
SEND DELIVER SUBMIT TRANSFER.
The emails go to the sent items folder, but it never reach the recipients.
Have been troubleshooting for a while without succes. Any help will be most appreciated.
Regards
Faisal

POP3 is a single mailbox client mail retrieval protocol, not a mail transport protocol.
Any attempt to use it as a mail transport protocol is a great big kludge.
Exchange is designed to connect to the Internet using SMTP.
No version of Exchange has a POP3 connector.
I recommend that you post this in the SBS Forum: http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

MS. Exchange Server 2007 Integration

I want to integrate MS. Exchange Server 2007 with my WebCenter portal application. I read that I can do this with WebCenter Interaction. I have following questions:-
1. Is the license of WebCenter Interaction is convered under the license of WebCenter Suite?
2. Does WebCenter Interaction support Exchange Server 2007 version?
Or will you guys suggest me any other solution for same purpose. Waiting for your reply.
Regards,
Imran

Hi Imran,
As per my information Webcenter Suite 10.1.3.2 does not have any direct integration capability with MS Exchange Server due to DEEP LINK LIMITATION. Only possible work around is go for External Application SSO registration and then render that URL in IFRAME.
As far as WEBCENTER INTERACTION is concerned i think its seprately licensed and eventhough it's free you need extra Hardware to Install and Configure.
Regards,
Vindhyachal Sharma

Exchange server 2007 Service Pack problems SBS 2008

I am Running Exchange server 2007 on Small Business server 2008 (SBS 2008). I tried to install SP2 but it fails both windows update and manually. Can anyone first advise me what version I'm currently running?
Help / about form Exchange Management Console displays:
Version 08.01.0436.000
And running repair on Exchange server from programs and features displays 2007 SP1 setup. So I believe SP2 to be next I have also ran SP3 but this fails.
Here is the end lines from a log:
[03/05/2014 08:54:13] [0] Setup will run the task 'uninstall-msipackage'
[03/05/2014 08:54:13] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '24b2c164-de66-44fe-b468-a46d9d5e6b31' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''
[03/05/2014 08:54:13] [1] Beginning processing.
[03/05/2014 08:54:13] [1] Property 'PackageName' is 'EXCHANGESERVER.msi'.
[03/05/2014 08:54:13] [1] Removing MSI package with code '24b2c164-de66-44fe-b468-a46d9d5e6b31'.
[03/05/2014 09:09:01] [1] [ERROR] Unexpected Error
[03/05/2014 09:09:01] [1] [ERROR] Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not open key: UNKNOWN\Components\7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613.
Verify that you have sufficient access to that key, or contact your support personnel. '.
[03/05/2014 09:09:01] [1] [ERROR] Fatal error during installation
[03/05/2014 09:09:01] [1] Ending processing.
[07/05/2014 19:45:17] [0] End of Setup
There is a registry key to match this and The administrator account used for setup has access to it i believe??? What does this log mean?

Hi,
This error indicated that your account missed registry permissions on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\ 7ABFE44842C12B390AF18C3B9B1A1EE8\461C2B4266EDEF444B864AD6D9E5B613
Please check whether you have permission. You can also check whether the key have permissions inherited from the Parent Key or not.
After changing the permission, please run the setup again.
Best Regards.

Mail / Calendar with Exchange Server 2007

Hi all,
We have a problem with Apple Mail and Calendar (Mountain Lion) connected to an Exchange Server 2007.
Apple Mail for no reason doesn't show the available data on the server. At first all goes right but after a few hours the data get corrupt. Folders disappear, mails aren't shown, ... The folders and mails are there in the server. I can check that with Outlook for Mac or on a collegues machine on Windows.
I tried:
- deleting the mail cache and mail data and restart
- removing the accounts and setting them up again
- creating a new user and trying mail in that user
None of those solved my problem.
Apple Calendar doesn't sync its data correctly. Example:
I create an event in calendar A. From that event I onvite calendar B to join the event. So far, so good. Everything just syncs fine. Then for some reason I delete the event from calendar A. In the server the event is still there. I checked in Outlook. This error is reproducable.
I tried:
- naming the user to <WORKGROUP>\<user>
- deleting the calendar cache and calendar data
None of those solved my problem.
Can anybody help me with this?

Hi and Welcome to the Forums!
The configuration I think you have is MS Exchange on the back end fronted (to the Internet) by Outlook Web Access (OWA). As such, Blackberry Internet Service is the interface between OWA and the BB...there is no direct interaction between the BB and the Exchange server. As such, only email will reconcile wirelessly in this configuration. Calendar, contacts, and other items must be reconciled via USB/BT tether.
Now, that said, there is a free solution to do what you desire -- it's called BES Express. BES is BlackBerry Enterprise Solution and provides OTA sync of email, calendar, contacts, etc. Full BES is not free. But BES-X is. If you truly require full reconciliation of all things from Exchange, I recommend you research BES-X.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

After upgrading Exchange Server 2007 to SP3 with update rollup 13, OWA not working

Hi,
We have just installed Service Pack 3 and update rollup 13 on our Exchange Server 2007, but unfortunately our OWA has gone inaccessible.
PROBLEM- The following error comes up when we try to access OWA :
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance
of an object.
Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
ACTION TAKEN SO FAR :
1. Removed OWA virtual directories and recreated them again.
2. IIS has been reset.
3. Restarted the HUB/CAS server.
4. Created public folder database.
Even after doing all these activities, owa is still inaccessible. Please help.
Regards,
Ankur

Hi Ankur,
From your description, you can't access to OWA after upgrading Exchange server 2007 to SP3 rollup 13. Firstly, please locate to C:\ExchangeSetupLogs and make sure that it is a successful installation. If not, this issue often occurs.
If it is a successful upgrading, please follow the steps below for troubleshooting.
1. Open IIS Manager, click Default Web Site -> Authentication, make sure that Anonymous Authentication and Windows Authentication are enabled.
2. Click Default Web Site -> SSL Settings, check "Require SSL" and click Ignore.
3. Click Default Web Site -> HTTP Redirect, check Redirect (enter your
https://URL), check "Only redirect" box and Status code Found 302.
4. Expand Server Configuration -> Client Access ->double click owa ->Authentication tab. Check the Basic Authentication and check the Use forms-based authentication button Logon Format: Domain\user name.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Spam Protection for Email showing Critical for Exchange Server 2007 after installing Symantec Mail Security for Microsoft Exchange

Hi there,
I have SBS 2008, and I have recently installed Symantec Mail Security for Microsoft Exchange version 7.5 but when I take a look on Windows SBS Console under Security, it shows "Spam Protection for Email Critical Exchange Server 2007" However,
when I open the SMSME it shows running well with no problem..
Any Suggestions???
Thanks

Hi,
Would you please let me confirm whether all functions (which are related to Exchange Server) run as normal? Just
a confirmation, thanks for your understanding.
Please run
SBS BPA and check if find relevant issues. In addition, please refer to GaryD9’s suggestion in following thread and check if can help you.
SBS
2008 & Forefront Protection 2010 for Exchange - SBS Console Error
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Using Exchange Server 2007 with 755p ???

After three phone calls to Palm customer service, I still cannot get my 755p to connection to Microsoft Exchange Server 2007 via Versamail. I have tried enumerous combinations without success. One customer service person told me I had to have a "certificate" with Server 2007 (unlike) but she could never tell me how to use it. (I have a line in my regular Outlook account set-up that reads "Only connect to proxy servers that have this principal name in their certificate:" I have that name in Outlook , but see no way of using it in Versamail. Without that certificate, it seems to reject my username and password.)
Any help here from someone who has actually been able to connect using the basic Versamail wizard and Exchange 2007? (I'm using Windows XP, but setting this up in the 755p -- not the computer. My service is Sprint.)
Post relates to: Treo 755p (Sprint)

Click on the following link for the support page for your device on the kb.palm.com webpage.
http://www.palm.com/us/support/treo/treo755psprint/
There are links on the page to the user guide, troubleshooting, how to's, downloads, etc.
Click on the link for "email setup (Versamail)"
There are instructions there for setting up an exchange account.
If you need to install a certificate on the device, click on the following link for instructions on installing a certificate on a Palm OS device.
http://www.palm.com/us/support/downloads/versamail/certmodtool.html
Post relates to: Palm i705

Exchange server 2007 still on version 8.1 even after applying sp3

Similar Messages

Maybe you are looking for