The Security certificate has Expired or is not yet valid

your users are receiving fallowing message when they open their outlook “The Security certificate has Expired or is not yet valid”

You also are receiving fallowing errors on your mail server

• Event Type: Error
• Event Source: MSExchangeTransport
• Event Category: TransportService
• Event ID: 12014
• Date: Date
• Time: Time
• User: N/A
• Computer: Server_Name
• Description:

Microsoft Exchange couldn't find a certificate that contains the domain name Domain_Name in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default Server with a FQDN parameter of FQDN. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

• Event Type: Warning
• Event Source: MSExchangeTransport
• Event Category: TransportService
• Event ID: 12015
• Date: Date
• Time: Time
• User: N/A
• Computer: Server_Name
• Description:
• An internal transport certificate expired.
• Thumbprint:Thumb_Print_Value

Cause:  the internal certificate used by Exchange is expired due to limitation, check out bb851554

Limitations of the Self-Signed Certificate

The following list describes some limitations of the self-signed certificate.

• Expiration Date: The self-signed certificate expires 12 months after Exchange 2007 is installed. When the certificate expires, a new self-signed certificate must be manually generated by using the New-ExchangeCertificate cmdlet.
• Outlook Anywhere: The self-signed certificate cannot be used with Outlook Anywhere. We recommend that you obtain a certificate from a Windows PKI or a trusted commercial third party if you will be using Outlook Anywhere.
• Exchange ActiveSync: The self-signed certificate cannot be used to encrypt communications between Microsoft Exchange ActiveSync devices and the Exchange server. We recommend that you obtain a certificate from a Windows PKI or a trusted commercial third party for use with Exchange ActiveSync.
• Outlook Web Access: Microsoft Outlook Web Access users will receive a prompt informing them that the certificate being used to help secure Outlook Web Access is not trusted. This error occurs because the certificate is not signed by an authority that the client trusts. Users will be able to ignore the prompt and use the self-signed certificate for Outlook Web Access. However, we recommend that you obtain a certificate from a Windows PKI or a trusted commercial third party.

Solution:

Logon to Exchange server issue fallowing command from EMS

Get-ExchangeCertificate | FL

Now pay attention to Status and  the dates and also you will need to copy and paste “Thumbprint”

Now copy paste or type below into EMS

Get-ExchangeCertificate -Thumbprint 56BB128980C53883BBF09AA0281FBC6471FB04FE | New- ExchangeCertificate

Do not forget to copy and paste the Thumbprint corresponds to your own exchange server

Type letter “Y” when it is prompted

Issue once more 

Get-ExchangeCertificate | FL

Now get rid of from the old one simply use below PS and corresponding thumbprint

Remove-ExchangeCertificate –thumbprint 56BB128980C53883BBF09AA0281FBC6471FB04FE

oz Casey Dedeal,

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http://smtp25.blogspot.com (Blog)

Http://telnet25.spaces.live.com (Blog)

Http://telnet25.wordpress.com (Blog

Outlook is retrieving data from the Microsoft Exchange Server

Outlook is retrieving data from the Microsoft Exchange Server mail1.smtp235.org; Christmas Balloon is not welcome for many exchange administrators.

In the past I blogged about the reasons and how to troubleshoot the issue in details here is the link to that post

Recently , we found out the same issue was raising on one of our customers network. The Exchange servers on this environment had 32 Gig memory with 16 CPU, so it was pretty easy not to start looking for server side problems, rather some other issue was causing the problem. Short story we found out  the problem was related to DC/GC , decommissioning problem DC/GC did the trick, the famous balloon  was gone.

I wanted to post some little very useful information , help me to what to look for right off the bat (-:

Note:

Server name	Outlook retrieving    data	Who is causing problem?
NetBIOS name	---------->	Exchange Server
(FQDN)	---------->	DC/GC

If the server name appears as a NetBIOS name, the data is being retrieved from an Exchange Server computer. If the server name appears as a fully qualified domain name (FQDN), the data is being retrieved from a global catalog server

Cheers,

oz Casey Dedeal,

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http://smtp25.blogspot.com (Blog)

Http://telnet25.spaces.live.com (Blog)

Http://telnet25.wordpress.com (Blog

Installing EXC SP2 Failed to initialize the log file: Access to the path 'C:ExchangeSetupLogs\ExchangeSetup.log' is denied.

Are you installing Exchange Sp2 on windows 2008 SBS server and getting below error?

Failed to initialize the log file: Access to the path 'C:ExchangeSetupLogs\ExchangeSetup.log' is denied.

Turn off UAC , by going control panel , user accounts, turn user account control off.

Also you will need to fallow the step mentioned on kb 973862 if you are receiving below erros.

You must update your Windows Small Business Server 2008 settings both before and after you install Exchange Server 2007 Service Pack 2 (SP2). Before installing SP2 for Exchange Server 2007, read the detailed information at http://go.microsoft.com/fwlink/?LinkId=155135.

Open Regedit on the SBS server

• HKEY_LOCAL_MACHINE
• Software
• Microsoft
• SmallBusinessServer
• Exchange  ( create this if does not exisit)
• E12SP2READY  (create this also and Value is = 1)

 

 

oz Casey Dedeal,

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http://smtp25.blogspot.com (Blog)

Http://telnet25.spaces.live.com (Blog)

Http://telnet25.wordpress.com (Blog

Exchange 2010 and RIM support

There are no updates or any news as far as I know yet  from RIM  in regards to Exchange 2010. RIM has  not announced any type of support for Exchange 2010.

Exchange 2010 has changed a lot compared to Exchange 2007 and hence current version of BES in not compatible with beta version of Exchange 2010.

To be honest I would love to see some testing going forward and hopefully RIM will catch up the official release day of Exchange 2010 which will be Soon (-: ( Shisss don't ask, it will be ready when it is read)

The bottom line is,  there is no support as of yet and we are hoping RIM is working on it to catch up the official Exchange 2010 release day….

oz Casey Dedeal,

MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +

Http://smtp25.blogspot.com (Blog)

Http://telnet25.spaces.live.com (Blog)

Http://telnet25.wordpress.com (Blog