10.4.6 update broke my Exchange certificate?????

Everything was working fine on my PowerMac G4 dual processor until I installed the 10.4.6 updater that was posted yesterday. Now, when I try to run Entourage 11.2.3, I get an error message that the root certificate does not exist.
However, when I go into keychain access, I find that the root certificate is, in fact, there. In both instances, keychain access says the certificate is valid, but no matter what I try, Entourage doesn't recognize its validity.
And this problem is not limited to Entourage. When I try collecting my exchange mail using the web client, Safari says the certificate is not valid. What's worse, I cannot tell it to always allow. No matter whether I check the box to always allow at the top of the certificate display or even go into the individual certificate security settings and set to always allow, every time I run Safari, it notifies me that the certificate is not valid.
I have already tried repairing permissions (which has gotten very, very quiet since the update to 10.4.6 - no more "we are using special permissions for xxx.widget" over and over again) and repairing through keychain first aid many times. Multiple re-starts has not resolved the issue.
What did 10.4.6 do to my certificate, and how can I fix it???

Hello Brad.
I've not had the courage for 10.4.6 yet, but am on 10.4.5 with Entourage/Exchange. I therefore have no specific result for you other than to say I had a challenge that Entourage constantly telling me that the root certificate wasn't installed... I followed the MS help proceedure of installing the root certificate to no avail. I wasn't until I changed the name of the exchange certifcate in the path of the exchange it was looking for did it no longer complain (in Account prefs of Entourage).
Specifically:
if your Exchange is called mailserver.domain.com, but your certificate has a name of exchange.domain.com, then change the path in Entourage to the latter... also remember to change the Public Folder lookup path to exchange.domain.com/Public.
It occured to me then, that the installation of the root certificate was an irrelevance??
HTH
Let me know how you get on, I'll also check some MS sites.
Cheers
iMac 1.9GHz 1.5Gb RAM 17"   Mac OS X (10.4.4)  
iMac 1.9GHz 1.5Gb RAM 17"   Mac OS X (10.4.4)  
iMac 1.9GHz 1.5Gb RAM 17"   Mac OS X (10.4.4)  

Similar Messages

  • Froyo OTA Update broke my Exchange Account!

    I received the "official" OTA update last night for my Droid and installed it this morning.  My corporate exchange account worked wonderfully before the installation and has been since I got the phone on it's release date.  After the installation, it's broken.  I've tried deleting the account and re-entering it and just get a message that advises that it's unable to connect to the server. 
    I've found that this has happened to many who have used the FRG01B update that VZW rolled out.  Anyone hear of a solution to this problem?  VZW, is there any plan to fix this bug?  I need my email and calendar back!!!  It's part of the reason I got this phone in the first place!

    first, let me tell you about my "registering on these forums" experience.  I tried over and over and it would not let me register.  silly little errors like, "your registration cannot be completed, try again later."
    Nonetheless, I have seen a few postings about how Froyo hoses Exchange(Corporate)e mail and I wanted to talk about why it is happening.   I was finally able to register from within my myverizon account, I could not do it any other way.  Also, got a page cannot be displayed error when I tried to click the support  site for the community/blog.
    Anyway, the solution:
    It looks like Froyo is forcing the use of a certificate on your Exchange portal.  It really is that simple.  Your Exchange Admin just needs to put a cert on the portal and then enable SSL.  That is all it takes, then on your phone, select to use SSL and Accept all Certs in the Inbound Accounts settings.  For some reason, corporate mail does not work without SSL, even if you uncheck the box.
    Most people won't have this problem since they probably already have a cert on the mailserver portal.

  • Airport utility 5.3.2 update broke configuration functionality

    After upgrading to the newest apple airport utility I can no longer read the configuration of any of my airports. Using an extreme and airport express.
    I open the application, it shows my 2 airport networks but when I try to run any kind of configuration on them then it stalls at the 'reading configuration' screen.
    This is quite a serious problem for me as this effects a work network that I need to be able to update. This is like the 3rd or 4th time something that was supposed to be an update broke functionality. Very disappointing. If someone is still on the old version, perhaps they could eMail it to me ?
    Specs of the effected computer and what it is effecting :
    Intel 2.4gz iMac
    Airport Extreme
    Airport Express
    Message was edited by: hellotyler
    Message was edited by: hellotyler

    Bump~

  • Checklist for Exchange Certificate issues

    Checklist for Exchange Certificate issues
    1. 
    Why certificate is important for Exchange and What are Certificates used for
    Exchange is now using certificates for more than just web, POP3, or IMAP. In addition to
    securing web services, it has also incorporated Transport Layer Security (TLS) for session based authentication and encryption.
    Certificates are used for several things on Exchange Server. Most customers also use certificates
    on more than one Exchange server. In general, the fewer certificates you have, the easier certificate management becomes.
    IIS (OWA, ECP, EWS, EAS, OA, Autodiscover, OAB, UM)
    POP/IMAP
    SMTP
     2. 
    Common symptoms for
    certificate issue
    Here we can see three different types of the certificate warning, mainly from the Outlook
    side.
    a.
    Certificate mismatch issue
    b.
    Certificate trust issue
    c.
    Certificate expiration issue
    3. 
    Checklists
    In this section, checklists will be provided according to the three different scenarios:
    Certificate Mismatch Issue
    [Analysis]:
    This issue mainly occurs because the URL of the web services Outlook tries
    to connect does not match the host name in the certificate.
    [Checklist]:
    Firstly make sure how many host name in your certificate the certificate. Run “Get-ExchangeCertificate | select certificatedomain”.
    Secondly, check the web services URLs which Outlook are trying to connect to. Run “Test Email AutoConfiguration”
    In this scenario, you need to check the host name for the following services:
    Autodiscover
    EWS
    OAB
    ECP
    UM
    If any of the urls above does not match the one in the certificate, refer to the following article to change
    it via EMS:
    http://support.microsoft.com/kb/940726
     1.
    Do not forget to restart the IIS service after applying the changes above.
     2. Make sure a valid certificate is enabled on the IIS service.
    Certificate Trust Issue
    [Analysis]:
    For the self-signed and PKI-based (Enterprise)
    certificates, they are not automatically trusted by the client computer or mobile device, you must make sure that you import the certificate into the trusted root certificate store on client computers and devices. On the other hand, Third-party or commercial
    certificates do not have this problem. Most commercial CA certificates are already trusted because the certificate already resides in the trusted root certificate store. Because the issuer is trusted, the certificate is also trusted. Using third-party certificates
    greatly simplifies deployment.
    [Checklist]:
    If it’s an Enterprise CA certificate, manually install the root certificate to the “Trusted Root Certification Authorities” folder:
    If it is a 3<sup>rd</sup>-party certificate, first remove and reinstall the certificate. Check whether the Windows Certificate Store on the local
    client is corrupted. If it still does not work, please contact the third-party CA support to verify the certificate.
    Certificate Expiration Issue
    [Checklist]:
    When a certificate is about to expired, we just need to renew it by referring the following article:
    Renew an Exchange Certificate
    http://technet.microsoft.com/en-us/library/ee332322(v=exchg.141).aspx
    To avoid any conflictions, it’s recommended to remove the expired certificate from the certificate store.
    [How to set a reminder to alert the administrator when a certificate is about to expired]:
    It’s easy to fix the certificate expire issue. But it should be more important to set a reminder before the
    certificate expiration. Or there can be a large user impacts.
    Generally, the Event ID “^(24|25)$” will appear in Application log when a certificate is about to expire.
    If it’s not quite visible, we can refer to the following solution:
    http://blogs.technet.com/b/nexthop/archive/2011/11/18/certificate-expiration-alerting.aspx
    OWA certificate revoked issue
    [Analysis]:
    IE
    includes support for server certificate revocation which verifies that an issuing
    CA has not revoked a server certificate. This feature checks for CryptoAPI revocation when certificate extensions
    are present. If the URL for the revocation information is unresponsive, IE cancels the connection.
    [Solution or workaround]:
    1. Contact CA provider and check whether the questioned certificate is in the Revoked List.
    2. If not, check whether the certificate has a private key.
    3. Remove the old certificate and import the new one.
    Workaround:
    IE Internet Options -> Advanced tab -> Clear the "Check for server certificate revocation"
    checkbox.
    4. 
    More References
    Digital Certificates and SSL
    http://technet.microsoft.com/en-us/library/dd351044(v=exchg.150).aspx
    More on Exchange 2007 and certificates - with real world scenario
    http://blogs.technet.com/b/exchange/archive/2007/07/02/3403301.aspx

    (Reported previous post with link to SIS package to moderator)
    This is not the correct SIS package for the N73. The package shown is for S60 3.2 devices, but the N73 is not S60 3.2, I believe it is S60 3.0.
    Most features may work with this SIS, but if you experience strange problems, try using the S60 3.0 version.
    But there are no significant difference between 2.5.3 and 2.5.5 with regard to attachments. The only changes were with localization (languages).
    At this point, try 2.7.0 which is out now:
    http://businesssoftware.nokia.com/mail_for_exchange_downloads.php
    Make sure to pick the right phone on the drop down list. It does matter! There are 4 different packages. This list makes sure you get the right one.
    I have seen some issues with attachments not completing that seem to be carrier dependent. You can test this my using Wifi (if possible).
    Message Edited by m4e_team_k on 28-Sep-2008 12:25 AM

  • RESOLVED On Premises (intranet use only) Exchange Certificate Help (Please)!

    I apologize in advance for what may end up being a very silly issue.
    I have racked my brain and read and searched and I still can't seem to find the answer to my question.
    I have an in house Exchange server that is only accessible internally. We do not have external clients (laptops/tablets/etc) and all computers stay on premises. Most of our clients use OWA to access email. Everything has been working fine up until about
    2 weeks ago when everybody started getting a certificate error. I have tried every thing I can find to fix this issue to no avail. It seems the thumbprint of the certificate is different each time I visit the exchange server (https://exchange/owa). So I can
    install the certificate which works for a few minutes and then it prompts me again. When looking at the thumb print of each instance, everything seems to be exactly the same with the exception of the thumbprint.
    My first question, is do I still need to go through a CA even though this server is not accessible via external IP?
    Where are my clients getting the certificate they are trying to install because they do not match the certificate that is installed on the Exchange Server.
    Thank you in advance for anybody that can steer me in the right direction to getting this resolved.
    I support this site remotely so any additional info can be provided but there might be a small delay.

    First, thank you for taking the time to respond.
    "I'm going to assume that you have some sort of PKI infrastructure with in your environment."
    I'm not sure I do. This project landed in my lap a few years ago. This particular client is my only client
    with exchange. I have limped my way though to this point but I'm afraid I'm just not clear on what it is I actually need.
    We are running Exchange 2013 on a Server 2008 box. Everything worked fine up until about 2 weeks ago. I have no idea what changed.
    I think my biggest problem is my lack of understanding of where the client is pulling the certificate when I access the intranet site. I don't understand why the certificate (whether valid or not) isn't matching the certificate within IIS/Exchange admin.
    Hi,
    I think you can check your certificate information and provide the information here for more help. Please run the following command in Exchange Management Shell:
    Get-ExchangeCertificate | fl
    Additionally, since the certificate issue occurs when accessing Exchange server from OWA, please check the OWA configuration in your Exchange:
    Get-OwaVirtualDirectory | FL Identity,*Authentication*,*url*
    Generally, the namespace used in the OWA URL should be included in the Exchange certificate which is assigned with IIS service.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Update Broke Dual Monitors...among other things

    Well Good Evening everyone....I got home to an updated, broke windows build.  I am guessing my PC stayed on and automatically updated over night. I came home to no signal on either of my monitors, all of my software that was installed is now missing,
    and i could not get into my PC. I restarted several times but still no success. I finally removed my secondary monitor, and I then had my screen back which is when I discovered all of my settings and software had been removed, kindalike a Refresh PC you can
    do on Windows 8. All of my files and documents are still in tact though. Also if I plug my secondary monitor back into the video card, still no signal. I've tried using the Windows+P to extend, as well as going to Screen Resolution but my settings will
    not save when i hit apply. This is a bit annoying but I do understand its a technical preview. Just wish my secondary monitor worked, Windows 10 is no good without it. Any ideas?

    Have you tried deleting the drivers manually from Device Manager? Remove any and all components that might be conflicting and unplug any unrelated peripherals. Then reinstall the latest Windows 8.1 drivers. Also make sure your
    monitor connections are setup properly.
    Hessam
    Windows Outreach Team- IT Pro
    Windows for IT Pros on TechNet

  • Exchange certificate error

    Hi Guys,
    I am in the process of upgrading my exchange 2007 to 2013. i now have setup a 2013 server successfully. However, i seem to be having problems with my exchange certificate. Everytime i open my outlook it comes up with the dialogue gox below
    The old server is still in the envirnoment so i was thinking its certificate is the one being picked up. could this be that the CAS is still on the old server? if yes, how to i transfer it. if otherwise, please assist.
    Regards,
    BJ

    Hi,
    I suggest try to re-create profile to refresh the caches for testing.
    If doesn't work, please try to check following checkpoints:
    1. Open IE and browse RPC URL, https://mail.domain.com/rpc, to examine the certificate.
    2. Install the trusted root certificate.
    3. Disable the 3rd party add-in or the 3rd party browser add-in.
    More details to refer following KB:
    Error message when Outlook tries to connect to a server by using an RPC connection or an HTTPS connection: "There is a problem with the proxy server's security certificate"
    https://support.microsoft.com/kb/923575?wa=wsignin1.0 
    Also provide an FAQ for your reference:
    Checklist for Exchange Certificate issues
    https://social.technet.microsoft.com/Forums/en-US/fa78799b-5c55-4c71-973b-0e186612ff6f/checklist-for-exchange-certificate-issues?forum=exchangesvrgeneral
    Thanks
    Mavis Huang
    TechNet Community Support

  • Update Rollup in Exchange 2007 SCR environment.

    Dear Experts. 
    I am going to install Rollup 12 for Exchange 2007 SP3, so could you please confirm if any issue with Rollup 12 Exchange 2007 SP3?
    Could you please advise to update Rollup in Exchange 2007 SCR environment with CCR.? I would appreciate. If you provide step by step
    process, Thanks
    Regards Vijaya Babu S | MCITP | MCTS | MCP| MCSA

    Hi Vijaya,
    Based on my known, Exchange 2007 SP3 Rollup 12 doesn't have a known issue so far.
    About the steps of update Exchange 2007 SCR with CCR, please follow the above article Mike provided.
    What's more, I recommend you make a complete backup of the clustered mailbox server prior to applying the update rollup and again after successfully applying the update rollup.
    Here is an article for your reference.
    How to Install Update Rollups in a CCR Environment
    http://technet.microsoft.com/en-us/library/bb885047(v=exchg.80).aspx
    Hope it helps.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • OIF-do I need to exchange certificate,keys if using selfsigned certificate?

    I have setup OIF federated authentication and it works between SP and IdP. I think I'm using self-signed certificates.
    With my setup, I did not have to exchange certificate between SP and IdP, however, my customer (IdP side) told me that I need to exchange with them the self-signed certificates and public key/private key.
    Do I need to exchange self-signed certificates and public key/private key between SP and IdP or only third party CA signed certs need to be exchanged?
    Also, to exchange certificate, I thought I just need to add it through "Trusted CAs and CRLs" in EM, but I'm not sure how to exchange public key/private key?
    Thanks

    I got "exchange certificate" working by enable certificate validation and adding IdP's certificate to SP or vice versa. the configuration was done through "Trusted CAs and CRLs" in OIF EM.
    However, I'm not sure what "public key needs to be exchanged" means. Could you please tell me what to do? or, are you saying public key is part of certificate and it exchanged by exchangeing certificate?
    Thanks

  • Error Install Update Rollup 3 Exchange Server 2010 SP2

    Hy Guys,
    I have the follow troubble when i try install the Update Rollup 3 Exchange 2010 SP2 on CAS Server. The error is "The user who's currently logged on doesn't have sufficient permissions to install this package. You need at least Exchange Server Administrator
    permissions on the current computer to complete the task."
    I've checked the permissions of the user which run the installer and those permissiones are OK. The user belong to Domain Admin, Enterprise Admin, Exchange Organization Management groups.
    I don't know what else to do. Thanks for your great help.

    Hi Wilmar
    Do you have PowerShell execution policy via Group Policy that could be blocking the install? If you right click the file and select "Run as Administrator"?
    Can you try running the setup from an elevated command prompt?
    Or you can enable logging by executing the patch like this below:
    Rollup3.msp /lxv* c:\Rollup3.log
    You can also look here:
    http://technet.microsoft.com/en-us/library/ff772434(EXCHG.80).aspx
    http://exchangeshare.wordpress.com/2009/05/30/exchange-update-rollup-installation-it-is-not-nightmare/

  • Cumulative Update 5 for Exchange Server 2013 (KB2936880)

    Hi,
    i have installed exchange server 2013 on separate servers, I deployed the Mailbox role on the first server, and the CAS role on the second server.
    I checked the edition using the exchange management shell on the mailbox server and on the CAS server:
    >>>
    [PS] C:\Windows\system32>Get-ExchangeServer | fl name,edition,admindisplayversion
    Name                : EXMBX
    Edition             : Standard
    AdminDisplayVersion : Version 15.0 (Build 516.32)
    Name                : EXCAS
    Edition             : Standard
    AdminDisplayVersion : Version 15.0 (Build 516.32)
    <<<
    My question is, is it possible to update this current edition to the "Cumulative update 5 for Exchange Server 2013 (KB293688) ?
    if it is, in my case, on which servers should i install this update ? on the Mailbox server ? or on the CAS server ?
    i appreciate you fast response,
    Thanks.

    Hello,
    It doesn't matter which build you choose: you should first update the mailbox role and then CAS. The best option is to have same version of all your Exchange servers (e.g. CU5).
    It is not necessary to install Exchange binaries on DC.
    Hope it helps,
    Adam
    www.codetwo.com
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
    find the answer faster.

  • Lync + Exchange certificate

    Hello guys,
    I want to go through the PIC provisioning process so that my lync users can communicate with Skype users. I am aware that i need a public certificate for my edge server in order to do this. Right now i have certificates for my Exchange 2013 and Lync 2013
    from my internal CA and i want to replace the Lync Edge certificate and the Exchange Certificate with a public one(SAN, i want all the FQDNs on one certificate). I have read other articles on this but i want to be sure so please hear me out.
    1) My Lync Edge server has only one external intereface with the FQDN sip.contoso.com. From what i've read i cant use wildcard certificates with this interface, so i must use SANs.
    2) My Exchange uses one namespace: mail.contoso.com. Also i need autodiscover.contoso.com for autodiscovery.
    So the certificate will look something like:
    CN: sip.contoso.com
    SAN: mail.contoso.com, autodiscover.contoso.com
    Do i need to put sip.contoso.com or anything else in SAN also?
    I'm going to test this with an internal certificate before i buy a public one, but i want a second opinion before testing on a production environment.
    Thank you

    Hi,
    I would say , we should include sip.domain.com in certificate SAN entry. Few validation checks will skip subject name and verify SAN in the certificate. Following article may help you ;
    http://technet.microsoft.com/en-us/library/gg398519.aspx
    Thanks
    Saleesh
    If answer is helpful, please hit the green arrow on the left, or mark as answer. Blog : http://blogs.technet.com/b/saleesh_nv/

  • Netbios names on exchange certificates

    Hi, 
    Is it not best practice to include the server netbios name in the SAN on the Exch 2013 SSL cert? Also is it even supported as I see some suggestions that netbios names on exchange certs is not often supported by online certificate authorities.
    Thanks 

    Hello,
    Since the certificate SAN name can be seen by public. If any security issues are not cared, it’s fine to add it to the SAN name.
    More information and best practices for Exchange Certificate in:
    Digital Certificates and SSL
    http://technet.microsoft.com/en-us/library/dd351044(v=exchg.150).aspx
    Thanks,
    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 Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • The new updater broke my ipod

    I've just installed the new updater for my 5G iPod. Now, when I've got the backlight set to off, I can no longer turn it on again by holding the menu key for a few seconds - it just goes to the previous menu no matter how long I hold it down. However, the backlight does work normally when on a timeout setting
    Anyone else having this problem? Think I'll get hold of the bug-fix updater (the previous version!).

    the reason is that its doin it is because for the
    hold menu thing is that you have to be at the main
    menu to turn it off.. its really only for when you
    have it switched to "always on" when you have it on
    like that. then it works
    No, it doesn't work at the main menu either. And no, it did work from anywhere with version 1.0.
    Basically, the updater broke it like I said, and there was another person who posted the same problem at the same time i did.
    This is a bug caused by the updater.

  • Ios8 update broke messaging in iphone 5

    The i0s8 update broke imessaging in my iphone 5s. Asks if I want to send as SMS instead. Nice QA, Apple.

    I had the same problem with iOS8 and the iPhone5.  I was not getting any messages being sent to me via iMessage.
    I only noticed this because the iMessage app on the Mac had new messages that the iPhone did not.
    When I went to the iPhone Messages settings and tried to log in to iMessage via my apple ID and PW the phone kept saying the PW is not correct which was not true since I am using that same ID and PW to post this message.
    I turned the iPhone off and then back on, went back into the Messages settings and iMessage indicated I was logged and and now is working however the earlier messages only delivered to the mac app don't show up on the phone.

Maybe you are looking for