Released: Update Rollup 5 for Exchange Server 2007 SP3

From our MSExchange Team's friends:

Earlier today the Exchange CXP team released Update Rollup 5 for Exchange Server 2007 SP3 to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of RU4. See 'KB 2602324: Description of Update Rollup 5 for Exchange Server 2007 Service Pack 3' for more details.

We would like to specifically call out the following fixes which are included in this release:

• DST: New updates for August DST - Exchange 2007
• 2536695 "Some items cannot be deleted" error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment
• 2292150 A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment (article not yet live)

General Notes:

• For DST Changes: http://www.microsoft.com/time
• Update Rollup 6 for Exchange Server 2007 Service Pack 3 is currently scheduled to release in April 2012. This will be in rhythm with next DST changes.

Complete article here :http://blogs.technet.com/b/exchange/archive/2011/09/22/released-update-rollup-5-for-exchange-server-2007-sp3.aspx

-Dario

Amig@s..Released: Update Rollup 4 for Exchange Server 2007 SP3 (KB2509911)

Recien salidito del horno
Lo pueden bajar de acá http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26692
Estas son las cosas que resuelve (http://support.microsoft.com/?kbid=2509911)

• 2531208  (http://support.microsoft.com/kb/2531208/ ) You cannot synchronize a folder hierarchy by using Outlook for Mac 2011 in an Exchange Server 2007 SP3 environment
• 2528437  (http://support.microsoft.com/kb/2528437/ ) EWS applications cannot connect to Exchange Server 2007 servers after you make changes on accepted domains
• 2521063  (http://support.microsoft.com/kb/2521063/ ) You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment
• 2517337  (http://support.microsoft.com/kb/2517337/ ) You cannot open a mailbox that has a "#" character in the primary SMTP email address by using OWA in an Exchange Server 2007 environment
• 2515428  (http://support.microsoft.com/kb/2515428/ ) The MSExchangeMailboxAssistants.exe process crashes when the managed folder assistant tries to journal a message in an Exchange Server 2007 environment
• 2508872  (http://support.microsoft.com/kb/2508872/ ) The W3WP.exe process in the Autodiscover application pool on the Exchange Server 2007 Client Access servers consumes excessive CPU resources
• 2507374  (http://support.microsoft.com/kb/2507374/ ) "Cannot open this item" error message in Outlook online mode in an Exchange Server 2007 environment
• 2506827  (http://support.microsoft.com/kb/2506827/ ) An UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2007 environment
• 2502276  (http://support.microsoft.com/kb/2502276/ ) A meeting request series are deleted unexpectedly from the calendar in an Exchange Server 2007 environment
• 2498924  (http://support.microsoft.com/kb/2498924/ ) "Could not connect to a directory server" error message when you click the last page button in the search results in Exchange Server 2007 OWA
• 2498156  (http://support.microsoft.com/kb/2498156/ ) OLM/OLD incorrectly runs against databases in a RSG in an Exchange Server 2007 environment
• 2496806  (http://support.microsoft.com/kb/2496806/ ) A mobile phone times out when you use ActiveSync to synchronize the calendar on the mobile phone with an Exchange Server 2007 mailbox
• 2543879  (http://support.microsoft.com/kb/2543879/ ) A PDF attachment sent from a Mac Mail client does not display when you open the email message by using Outlook 2010 in an Exchange Server 2007 SP3 environment
• 2491751  (http://support.microsoft.com/kb/2491751/ ) Spell checking does not function correctly in OWA when an S/MIME control is used and SSL Offloading is enabled in Exchange Server 2007
• 2484147  (http://support.microsoft.com/kb/2484147/ ) "HTTP Error 400 Bad Request" error message when you use OWA to log on to a newly created Exchange Server 2007 mailbox
• 2466220  (http://support.microsoft.com/kb/2466220/ ) Question mark (?) characters appear in the subject of a reply email message in an Exchange Server 2007 environment
• 2223294  (http://support.microsoft.com/kb/2223294/ ) A new feature is available to disable the "No end date" check box in OWA when you create a recurring meeting item in an Exchange Server 2007 environment
• 977906  (http://support.microsoft.com/kb/977906/ ) You receive an error message when you run certain commands in the EMS on an Exchange Server 2007 server
• 2495010  (http://support.microsoft.com/kb/2495010/ ) The EdgeTransport.exe process consumes 100% CPU usage on an Exchange Server 2010 Edge Transport server or an Exchange Server 2007 Edge Transport server
• 2484817  (http://support.microsoft.com/kb/2484817/ ) A mailbox does not show in certain address lists after you run commands on an Exchange Server 2007 mailbox

-Dario

¿Cómo obtener estadísticas de Exchange Active Sync para Exchange 2007?

English Version

Amig@s,
les dejo un scritp que saca estadísticas de Exchange Active Sync y las guarda en una planilla excel

El código:

NEWS!! !---- Announcing the Re-release of Exchange 2007 Service Pack 3 Update Rollup 3 (V2)

Finally !!!! for Exchange 2007 so far

The Exchange Servicing team has fixed the reported issue with RU3 and is making available a new version of RU3 for our customers, version 08.03.159.002, (KB2530488). We strongly advise all customers install this newly released version of Microsoft Exchange Server 2007 SP3 Update Rollup 3 and to discard any prior version of RU3 (KB2492691) which you may have.
RU3 Installation Guidance:

• Customers with RU3 already installed within your Exchange environment It is not necessary for you to uninstall the existing RU3 within your environment. The new RU3 package can be installed over the top of the existing package installed on your servers.
• Customers with previous SP3 RU’s installed within your Exchange environment You can simply install the new version of the RU3 package.

General RU Installation Guidance

• Note for deployments that leverage Forefront Security for Exchange: For those of you running Forefront Security for Exchange perform these important steps from the command line in the Forefront directory before and after this rollup's installation. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable Forefront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.

see the full article : http://blogs.technet.com/b/exchange/archive/2011/03/31/announcing-the-re-release-of-exchange-2007-service-pack-3-update-rollup-3-v2.aspx?utm_source=twitterfeed&utm_medium=twitter
-Dario

Exchange 2007 SP3 RU3 and Exchange 2010 SP1 RU3 Status UPDATE!!!!!

And..finally an update from ours friends of Exchange Team....just in case do not install those roll ups

 

Exchange 2007 SP3 RU3 Status

The Exchange Servicing team expects to re-release the Exchange 2007 SP3 RU3 rollup in the next day or so. We are going through the final sign-off processes. As reported yesterday, a bug was introduced which had the potential to create database corruption. We consider any situation which could lead to data loss a significant risk, which is why we posted the unusual guidance to rollback to the previously installed version versus waiting for an update.
Still, we have been able to identify the issue, remove the fix which introduced the problem, complete our testing, and expect to re-release the Update Rollup shortly. We also understand what happened to allow this situation to occur and are taking corrective measures. Finally, for customers who have not uninstalled E2007 SP3 RU3, this will install seamlessly on top of the existing E2007 SP3 RU3 installations.

Exchange 2010 SP1 RU3 Status

For E2010 SP1 RU3 we are still one to two weeks away from re-release. While the previous post specifically mentioned only one issue related to duplicate messages in the Sent Items folder on Blackberry devices, we unfortunately uncovered one additional issue after my original post. There is no risk of to customer data as a result of this second problem.  However, the underlying problem is complex and we are taking the necessary time to get a high quality solution.
Specific to this second issue we uncovered a problem which manifested as an email delivery delay for users of Microsoft Outlook 2007 or 2010.  Our investigation of the problem exposed a rare situation in Exchange 2010 where notifications were not sent to these clients.  What changed in E2010 SP1 RU3 is that this situation is more likely to occur because of code added to support coexistence in cross-premises environments, i.e., users within an enterprise both on-premises and in the cloud.
While I know many of you are waiting to deploy E2010 SP1 RU3, and we could have removed the code to more quickly turn around the re-release, in our analysis we felt this issue was significant enough that it needed to be addressed immediately.  Additionally our testing uncovered the need to refine the notification experience with Microsoft Outlook 2003 clients.  So we have taken the additional time to ensure resolution of the issues uncovered with notifications.  The delay in re-releasing E2010 SP1 RU3 is a result of ensuring these issues are resolved satisfactorily
For those of you that currently have E2010 SP1 RU3 installed, you can either uninstall E2010 SP1 RU3 (which is recommended if you are experiencing any of the above issues), or wait for the re-release. The re-release build will install seamlessly on top of the existing E2010 SP1 RU3 installation.

see the full article http://blogs.technet.com/b/exchange/archive/2011/03/30/exchange-2007-2010-rollup-3-status-update.aspx

-Dario

NEWS!!!!! ---Serious Risk of Database Corruption with Exchange 2007 SP3 Update Rollup 3

Over the weekend, the Exchange Product Group was made aware of an issue which may lead to database corruption if you are running Exchange 2007 Service Pack 3 with Update Rollup 3 (Exchange 2007 SP3 RU3). Specifically, the issue was introduced in Exchange 2007 SP3 RU3 by a change in how the database is grown during transaction log replay when new data is written to the database file and there are no available free pages to be consumed.
This issue is of specific concern in two scenarios: 1) when transaction log replay is performed by the Replication Service as part of ensuring the passive database copy is up-to-date and/or 2) when a database is not cleanly shut down and recovery occurs.

While only a small number of customers have been affected to date, we believe the risk is significant enough that we are recommending all customers to uninstall Exchange 2007 SP3 RU3 on all Mailbox Servers and Transport servers. Uninstalling the rollup will revert the system back to the previously installed version. We have also removed the Exchange 2007 SP3 RU3 download from the Microsoft Download Center and from Microsoft Update until we are able to produce a new version of the rollup.

When this issue occurs, the following similar events are logged in the Application Event log of the Mailbox server. Regardless of whether you see these types of events, you should review the recovery instructions and begin that process. If you are uncomfortable performing any of these steps please contact Microsoft Support for assistance.

• Event ID: 454
  Event Type: Error
  Event Source: ESE
  Event Category: Logging/Recovery
  Description: Microsoft.Exchange.Cluster.ReplayService (12716) Recovery E20 SG1\DB1: Database recovery/restore failed with unexpected error -4001.
• Event ID: 2095
  Event Type: Error
  Event Source: MSExchangeRepl
  Event Category: Service
  Description: Log file D:\logs\SG1\E200006AFAE.log in SG1\DB1 could not be replayed. Re-seeding the passive node is now required. Use the Update-StorageGroupCopy cmdlet in the Exchange Management Shell to perform a re-seed operation
• Event ID: 2097
  Event Type: Error
  Event Source: MSExchangeRepl
  Event Category: Service
  Description: The Microsoft Exchange Replication Service encountered an unexpected Extensible Storage Engine (ESE) exception in storage group 'SG1\DB1'. The ESE exception is a read was issued to a location beyond EOF (writes will expand the file) (-4001) ().

See the full article: http://blogs.technet.com/b/exchange/archive/2011/03/29/potential-for-database-corruption-as-a-result-of-installing-exchange-2007-sp3-ru3.aspx

-Dario

Exchange Architecture Poster

Hi everyone,
I know...this is not new, but just in case...
Exchange 2010 Architecture Poster http://go.microsoft.com/?linkid=9729251 and Exchange 2007 Architecture Poster http://www.microsoft.com/downloads/en/confirmation.aspx?displaylang=en&FamilyID=fdcdf6e5-de47-4b58-8086-282101bcdde9

Enjoy!

-Dario

Error message when an Exchange Server 2007 user or an Exchange Server 2010 user tries to log on to OWA

In the mixed mode between Exchange 2003/Exchange 2010 or Exchange 2007, after move an user to the new server or when create a new one from the ADUC, the below error could show up when the user try to access by OWA

A problem occurred while trying to use your mailbox. Please contact technical support for your organization.
or

An unexpected error occurred and your request couldn't be handled.

In Show datails:

Request

Url: https://<user's<user's owa link>:443/owa/lang.owa

User host address: <user’s ip address>

Exception

Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException

Exception message: There was a problem accessing Active Directory.

Call stack

Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save() 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(O

waContext owaContext, UserContextCookie userContextCookie) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) 

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) 

System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Inner Exception

Exception type: 

Microsoft.Exchange.Data.Directory.InvalidADObjectOperationException

Exception message: Property Languages cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0). 

Call stack

Microsoft.Exchange.Data.Directory.PropertyBag.set_Item(PropertyDefinition key, Object value) 

Microsoft.Exchange.Data.Directory.ADObject.set_Item(PropertyDefinition propertyDefinition, Object value) 

Microsoft.Exchange.Data.Directory.ADObject.StampCachedCaculatedProperties(Boolean retireCachedValue) 

Microsoft.Exchange.Data.Directory.ADObject.ValidateWrite(List`1 errors) 

Microsoft.Exchange.Data.Directory.Recipient.ADRecipient.ValidateWrite(List`1 errors) 

Microsoft.Exchange.Data.Directory.Recipient.ADUser.ValidateWrite(List`1 errors) 

Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties) 

Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

This problem can occur when the msExchVersion attribute is not configured correctly on the user object in Active Directory.
Note The msExchVersion attribute may not be configured correctly if you create the user's mailbox by using Active Directory Users and Computers Microsoft Management Console (MMC) snap-in instead of using the Exchange Management Console.

In order to verify this problem, you can check the msExchVersion attribute by using the Exchange Management Shell. Run the following command in the Exchange Management Shell prompt:

Get-Mailbox <User_Name>| format-list ExchangeVersion

Note Exchange Server 2007 and Exchange Server 2010 both use the msExchVersion attribute to determine the version of Exchange Server that user objects are associated with. If the version value is less than 0.1, Exchange Server 2007 or Exchange Server 2010 considers the user object as Read-only.

To resolve this problem, an Exchange administrator should run the following command in the Exchange Management Shell prompt:

 Set-Mailbox <User_Name> -ApplyMandatoryProperties

Notes

• To fix the problem on an Exchange Server 2007 mailbox, an Exchange administrator should run the Set-Mailbox command in the Exchange Management Shell 2007.
• To fix the problem on an Exchange Server 2010 mailbox, an Exchange administrator should run the command in the Exchange Management Shell 2010.

-Dario

Released: Update Rollup 3 for Exchange 2010 SP1 and Exchange 2007 SP3

Good moooorning!!!
from :Exchange Team blog http://msexchangeteam.com/archive/2011/03/08/458566.aspx

Earlier today the Exchange CXP team released the following Update Rollups for Exchange Server 2010 and 2007 to the Download Center. Release via Microsoft Update will occur on March 22nd 2011.

• Update Rollup 3 for Exchange Server 2010 Service Pack 1
• Update Rollup 3 for Exchange Server 2007 Service Pack 3

Update Rollup 3 for Exchange Server 2010 SP1

This update contains a number of customer reported and internally found issues since the release of RU2. In particular we would like to specifically call out the following fixes which are included in this release:

• 2432494 'Database Copies' list is being populated incorrectly (case sensitive) in EMC with DAG in place after upgrade to E14 SP1
• 2489822 Users without mailbox can't delete items in shared mailbox via OWA premium
• 2511471 Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode

Update Rollup 4 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in May 2011.

Update Rollup 3 for Exchange Server 2007 SP3

This update contains a number of customer reported and internally found issues since the release of RU2. In particular we would like to specifically call out the following fixes which are included in this release:

• 2267661 Exchange should support promotion of multipart/mixed messages into a single aggregate body
• 2479939 Resource Booking using ScheduleOnlyDuringWorkHours does not consider mailbox's time zone

Update Rollup 4 for Exchange Server 2007 Service Pack 3 is currently scheduled to release in May 2011.

General Notes

Note for Exchange 2010 Customers using the Arabic and Hebrew language version: We introduced two new languages with the release of Service Pack 1, Arabic and Hebrew. At present we are working through the process of modifying our installers to incorporate these two languages. Customers running either of the two language versions affected are advised to download and install the English language version of the rollup which contains all of the same fixes.
Note for Forefront users: For those of you running Forefront, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable ForeFront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.

Enjoy

-Dario

After apply RU1 for Exchange 2007 SP3 we cannot create a Receive Connector

When we try to create a new receive connector in Exchange 2007, we received the error:

New-ReceiveConnector : Active Directory operation failed on testgdc1.company.com. This error is not retriab

le. Additional information: The parameter is incorrect.

Active directory response: 00000057: LdapErr: DSID-0C090B38, comment: Error in attribute conversion operation, dat

a 0, vece

At line:1 char:21

+ new-ReceiveConnector <<<< -Name 'TEST' -Usage 'Custom' -Bindings '10.1.2.30' -RemoteIpRanges '192.168.0.2' -Server 'TESTHCEX1'

The accepted solution is
From Exchange 2007 SP3 source and with Schema admin permissions

C:\Source\Ex2007-SP3>setup /ps
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
    Organization Checks              ......................... COMPLETED
Configuring Microsoft Exchange Server
    Extending Active Directory schema
    Progress                         ......................... COMPLETED
The Microsoft Exchange Server setup operation completed successfully.

After that, simply try to create the Receive connector again


new-ReceiveConnector -Name 'TESTHCEX1-Inbound Mail' -Usage 'Custom' -Bindings '10.1.2.30:25' -RemoteIPRanges '192.168.0.2' -Server 'TESTHCEX1' -PermissionGroups AnonymousUsers

Identity                                                               Bindings              Enabled

TESTHCEX1\TESTHCEX1-Inbound Mail      {135.9.6.94:25}    True

And

Get-ReceiveConnector "TESTHCEX1-Inbound Mail" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

Identity                                      User                                   Deny   Inherited    Rights
TESTHCEX1\TESTCHEX1... NT AUTHORITY\ANON... False  False           ms-Exch-SMTP-Accept-Any-Recipient

-Dario

Users are getting “Security certificate on server is not valid” error message when trying to access emails from their mobile devices ...And you just recently has renewed the CAS & ISA 's Verisign certifcates

UPDATED 02/15/2011

I know I know...is not new, ours Verisign friends have published new Intermediate certificates, so all new or renewed certificates requested at (10/30/2010)  with all possible path set, will need to update or install this Intermediate certificate in the servers, in mobile devices and clients machines as well..

SSL/TLS certificates issued by VeriSign after Oct 10th 2010 will use a trust chain that includes the new intermediate certificates. You may need to import these certificates into CAS and ISA Server to support TLS with partners.
If you use VeriSign for your TLS certificates, I believe you need to import these new intermediate certificates before importing any newly requested VeriSign TLS certificate
See the link http://www.verisign.com/support/verisign-intermediate-ca/secure-site-intermediate/index.html

If you enrolled for your certificate between May 17, 2009 and October 10th, 2010 Click here for your Intermediate CA

If you enrolled for your certificate before May 17, 2009 Click here for your Intermediate CA

Download the root CA for Windows XP SP3 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=25249786-2b8e-4c51-8f4b-727ce25cc2c5


Please follow this link for how to install this certificate in Windows Server environments https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=SO8227

Enjoy

-Dario

"The name of the security certificate is invalid or does not match the name of the site" when check Free/Busy calendar availability or OOF message

Folks
OOF and Free/Busy calendar availability depends on Autodiscovery Service.

First of all to get this availability for Outlook anywhere the /Autodiscover folder should be published form ISA server , and configuring the External URL in CAS servers.

Enable-OutlookAnywhere -Server CAS01 -ExternalHostname "mail.domain.com" -ExternalAuthenticationMethod "Basic" -SSLOffloading:$False

Set-OABVirtualDirectory -identity "CAS01\OAB (Default Web Site)" -externalurl https://mail.domain.com/OAB -RequireSSL:$true

Set-WebServicesVirtualDirectory -identity "CAS01\EWS (Default Web Site)" -externalurl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$True

How to request a new certificate manually with certreq.exe tool ussing a INF file and a SAN

Once a time I was really lost regarding how to get a new cert request from command line and I've found  this command ....this is useful for Windows 2003 Server and Windows 2008 Server.

1.Open a notepad and save as policy.inf and copy the below lines:

Policy.INF file

[Version]
Signature= "$Windows NT$"
[NewRequest]
Subject= "CN =server1.mycompany.com;OU=MyCompany IT;O=My Company Inc;L=Saavedra;S=CABA;C=AR"
KeySpec = 1 
KeyLength = 1024  
Exportable = TRUE
MachineKeySet = TRUE
SMIME = FALSE
PrivateKeyArchive = FALSE
UserProtected = FALSE   
UseExistingKeySet = FALSE
ProviderName = "Microsoft RSA Schannel Cryptographic Provider"
ProviderType = 12
RequestType = PKCS10 
KeyUsage = 0xa0   
[EnhancedKeyUsageExtension]
OID=1.3.6.1.5.5.7.3.1   
[RequestAttributes]
SAN:DNS=name1.mycompany.com&DNS=name2.mycompany.com&DNS=name3.mycompany.com&DNS=name4.mycompany.com&DNS=name4.mycompany.com&DNS=name5.mycompany.com


2. From command line and with Local Administrator permissions, type:

certreq -new Policy.inf c:\certs\server1New.txt

3. Submit the request file to the Certificate Authority (CA) and have the CA generate the certificate

4.After receiving the certificate , accept it

certreq -accept c:\certs\cert.cer

 This will install the certificate in your certificate personal folder..

Further information be free to contact me at dario.may@gmail.com

-Dario

How to install a Certificate in Exchange 2007 CAS Server

Gooood night for all...

A commercial certificate is only needed if the Client Access server will service client requests from the Internet or to facilitate un-trusted cross-forest communication between Client Access servers.

1.Connect to the server via Remote Desktop and log on with an account that has local administrative access and has been delegated the Exchange Server Administrator role (or higher).

Note:

For more information about using the certificate tasks, see the Exchange 2007 Online Help topic Creating a Certificate or Certificate Request for TLS .

 

 Note:

If generating a certificate that will use Subject Alternative Names, be sure that the certificate’s principal name will be the one that the clients (for example, Outlook) will use to connect (for example, mail.contoso.com). In other words, do not list the Autodiscover namespace as the principal name in the certificate.

2. Generate the certificate request by using the following Exchange Management Shell command. The DomainName parameter includes the principal URL, Autodiscover FQDN, and the server FQDN. The FriendlyName parameter matches the principal URL that is used by Outlook Web Access and Outlook Anywhere.

New-ExchangeCertificate -GenerateRequest -SubjectName “c=US,o=MyCompany,cn=<Primary Namespace>.mycompany.com” -DomainName =<Primary Namespace>, <Secondary Namespace(s)>, <ServerName>, <ServerName>.domain.mycompany.com, <Location Code>NLB.mycompany.com -FriendlyName <Primary Regional Namespace>.webmail.mycompany.com -privatekeyexportable:$true -path c:\cert.txt

 Note:
An example of [Full Subject Path] is "c=US, o=Company, cn=CAS01.contoso.com".

Note: In Windows Vista, the Windows RPC/HTTP client-side component required that the Subject Name (Common Name) on the certificate match the “Certificate Principal Name” configured for the Outlook Anywhere connection in the Outlook profile. This behavior was changed in Windows Vista Service Pack 1 (SP1). Therefore, as a best practice, make sure that the Subject Name (Common Name) on the certificate match the “Certificate Principal Name” configured for the Outlook Anywhere connection. 

3. Submit the request file to the Certificate Authority (CA) and have the CA generate the certificate.
4. After receiving the certificate, import and enable the certificate by running the following Exchange Management Shell command where [services] can be POP, IMAP, IIS, or a combination:

Import-ExchangeCertificate -path c:\newcert.cer | Enable-ExchangeCertificate -services "IIS,IMAP,SMTP"
5. You will prompted to “Confirm; Overwrite existing default SMTP certificate”. Respond “L” for “No to all”

6. Require SSL on the default Web site, do the following:

1.  Open Internet Information Services (IIS) Manager.
2. Expand the Server Node object and the Sites node.
3. Click the Default Web Site.
4. In the middle pane, double-click SSL Settings.
5. Verify Require secure channel (SSL) is enabled.

 Note:

If you require 128-bit encryption, also verify that Require 128-bit encryption is enabled.

DataBase's OnLine Defrag is silent as bad cholesterol - Exchange 2007

And is true...Before you know it, you have clogged arteries..and your databases ..broken .So the code below will check the events 700-701-702-703-704 see the table below.

As Microsoft states as best practices :
"Monitoring online defragmentation enables you to verify that defragmentation of every Exchange database is completing often enough (at least every two weeks, as a best practice). Monitoring online defragmentation may also enable you to decrease the online maintenance window, which has the following advantages:

• Allows more time for database backup.
• Validates that online checksumming and page zeroing can be introduced within the current online maintenance window.

Microsoft Exchange Server 2007 Service Pack 1 (SP1) introduces the following improvements to help you monitor online defragmentation:

• Extended information for Event 703 allows you to more easily monitor online defragmentation pass completions.
• Two extended Extensible Storage Engine (ESE) performance counters for monitoring the effectiveness and efficiency of online defragmentation have been added for use with Performance Monitor (which is called Reliability and Performance Monitor in Windows Server 2008)."

This code will generate two types fo outputs:

With errors (not completed)
Name                    : DATABASE1-SG04
Identity                : SERVER\STORAGEGROUP\DATABASE1-SG04
EdbFilePath             : N:\STORAGEGROUP\DATABASE1-SG04
.edb
DefragStart             :
DefragEnd               :
DefragDuration          :
DefragInvocations       :
DefragDays              :
DefragInterrupts        :
DefragError             : unexpected error :-327.--> this is a critical error, you shold repair the DB (http://technet.microsoft.com/en-us/library/bb218265(EXCHG.80).aspx)DefragStillRunningSince : 20/01/2011
DefragStillRunningDays  : 13  ----> 13 days running

Without errors (completed)
Name                    : DATABASE-SG05
Identity                : SERVER\STORAGEGROUP\DATABASE-SG05
EdbFilePath             : P:\DATABASE\DATABASE-SG05.edb
DefragStart             : 03/02/2011 04:54 
DefragEnd               : 03/02/2011 04:54
DefragDuration          : 28976 seconds.
DefragInvocations       : 2 time[s].
DefragDays              : 1
DefragInterrupts        : 03/02/2011 09:59  ---> Backup interruptions
DefragError             :
DefragStillRunningSince :
DefragStillRunningDays  :

The event 705 is preceded for the event 447 , this issue indicates that a corrupt page link was detected in a B-Tree.

Explanation:
Online defragmentation has failed because of some issues in this tree. Event 447 suggests that a B-tree consists a corrupt page link. The most common reasons for this problem to occur are:

• Hardware failure
• Antivirus software scanning of Exchange database directory (Antivirus's Exclisions for Exchange 2007)

Note: It is not safe to continue using such corrupted database as a bad page link indicates logical database corruption at ESE level. Also, you should ensure that no antivirus software is scanning the Exchange database files.

Solution:

• Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step
• If the Exchange store database is running, use ExMerge to merge your data to .pst files, delete the database, create a blank database, and then run ExMerge t databases to a blank database.
• If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.
• If the Exchange store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the Application log.
• If the Exchange store database will not mount and there is no backup, the last resort is to repair the database by running eseutil /p and then repeatedly running isinteg -fix until there are no fixes reported. Finally, run ExMerge, create a blank store, and use ExMerge to move the data back in.

-----------------------begin code
$srv = Get-ExchangeServer |where {$_.IsMailboxServer -eq 'True'}


$output = @()
$dmtf = [System.Management.ManagementDateTimeconverter]
$Startdate = $dmtf::ToDmtfDateTime( (Get-Date).AddDays(-1).Date )
$free = @{Name="WhiteSpace(MB)";Expression={[int]$_.InsertionStrings[0]}}


foreach ($dbserver in $srv){


# Get the mailbox databases from the server
$mbdatabases = Get-MailboxDatabase -Server $dbserver.name | Sort-Object -Property Name


# Get the public folder databases from the server
$pfdatabases = Get-PublicFolderDatabase -Server $dbserver.name | Sort-Object -Property Name


# Create an array for the databases
$databases = @()


# Check if mailbox databases were found on the server
If ($mbdatabases) {
      # Loop through the databases
      ForEach ($mdb in $mbdatabases) {
            # Create an object to store information about the database
            $db = "" | Select-Object Name,Identity,EdbFilePath,DefragStart,DefragEnd,DefragDuration,DefragInvocations,DefragDays,DefragInterrupts,DefragError,DefragStillRunningSince,DefragStillRunningDays
           
            # Populate the object
            $db.Name = $mdb.Name.ToString()
            $db.Identity = $mdb.Identity.ToString()
            $db.EdbFilePath = $mdb.EdbFilePath.ToString()
           
            # Add this database to the array
            $databases = $databases + $db
      }
}


# Check if public folder databases were found on the server
If ($pfdatabases) {
      # Loop through the databases
      ForEach ($pfdb in $pfdatabases) {
            # Create an object to store information about the database
            $db = "" | Select-Object Name,Identity,EdbFilePath,DefragStart,DefragEnd, DefragDuration,DefragInvocations,DefragDays,DefragInterrupts,DefragError,DefragStillRunningSince,DefragStillRunningDays
           
            # Populate the object
            $db.Name = $pfdb.Name.ToString()
            $db.Identity = $pfdb.Identity.ToString()
            $db.EdbFilePath = $pfdb.EdbFilePath.ToString()
           
            # Add this database to the array
            $databases = $databases + $db
      }
}


# Retrieve the events from the local Application log, filter them for ESE messages
$logs = Get-WMIObject Win32_NTLogEvent -ComputerName $dbserver.name  -Filter "LogFile='Application' AND Timewritten>='$startdate' AND sourceName='ESE' AND CategoryString='Online Defragmentation'  "
 


# Loop through each of the databases and search the event logs for relevant messages
ForEach ($db in $databases) {


      # Create the search string to look for in the Message property of each log entry
      $s = "*" + $db.EdbFilePath + "*"


      # Search for an event 701 or 703, meaning that online defragmentation finished
      $end = $logs | where {
            $_.Message -like "$s" -and ($_.eventcode -eq 701 -or $_.eventcode -eq 703)
      } | select-object -First 1


      # Search for the first event 700 which preceeds the finished event
      $start = $logs | where {
            $_.Message -like "$s" -and $_.eventcode -eq 700 -and $_.Index -le $end.Index
      } | select-object -First 1
  $interr = $logs | where {
            $_.Message -like "$s" -and $_.eventcode -eq 704
      } | select-object -First 1
 $defError = $logs | where {
            $_.Message -like "$s" -and $_.eventcode -eq 705
      } | select-object -First 1

 $defStillRun = $logs | where {
            $_.Message -like "$s" -and $_.eventcode -eq 702
      } | select-object -First 1


      # Make sure we found both a start and an end message
      if ($start -and $end  ) {


            # Get the start and end times
  $st= $start.TimeGenerated
  $stY=$st.substring(0,4)
  $stM=$st.substring(4,2)
  $stD=$st.substring(6,2)
  $stH=$st.substring(8,2)
  $stMs=$st.substring(10,2)
  $et= $end.TimeGenerated
  $etY=$et.substring(0,4)
  $etM=$et.substring(4,2)
  $etD=$et.substring(6,2)
  $etH=$et.substring(8,2)
  $etMs=$et.substring(10,2)
  


           $db.DefragStart = $stD + "/" + $stM + "/" +  $stY + " " + $stH + ":"  + $stMs
            $db.DefragEnd = $etD  + "/" + $etM + "/" + $etY  + " " + $etH + ":" + $etMs


            # Parse the end event message for the number of seconds defragmentation ran for
            $end.Message -match "This pass started on .* and ran for a total of .* seconds" >$null
     #$db.DefragStart = $Matches[0].Split(" ")[4] + " restarted."
            $db.DefragDuration = $Matches[0].Split(" ")[11] + " seconds."
        
            # Parse the end event message for the number of invocations and days
            $end.Message -match "requiring .* invocations over .* days" > $null
            $db.DefragInvocations = $Matches[0].Split(" ")[1] + " time[s]."
            $db.DefragDays = $Matches[0].Split(" ")[4]


  
  #$interr.Message -match "was interrupted and terminated." >$null
  if ($interr) {
  $it= [string]$interr.TimeGenerated
  $itY=$it.substring(0,4)
  $itM=$it.substring(4,2)
  $itD=$it.substring(6,2)
  $itH=$it.substring(8,2)
  $itMs=$it.substring(10,2)
       $db.DefragInterrupts=$itD  + "/" + $itM + "/" + $itY  + " " + $itH + ":" + $itMs
     
  }
          } else {
            if ($defError -and $defStillRun) {


            $defError.Message -match "after encountering unexpected error .*" >$null
    
            $db.DefragError = "unexpected error :" + $Matches[0].Split(" ")[4]


     $defStillRun.Message -match "pass started on .* and has been running for .* days" >$null 
     $db.DefragStillRunningSince = $Matches[0].Split(" ")[3]
     $db.DefragStillRunningDays = $Matches[0].Split(" ")[9]


            }
           
      }
      # Add the data for this database to the output
      $output = $output + $db
}
 }
# Print the output
$output

------end code

Don't worry...be happy.

-Dario

How to get Exchange 2007 database's White Space in PowerShell

Hi everyone,
the sun is shining in Buenos Aires and with the summer breeze my mood is better than yesterday :)..I would to share with you this simple script that search the Event 1221 in all mailbox servers  and get the DB's white space in MB...the result will be exported to a csv file, see the code below:

$ComputerName =Get-ExchangeServer |where {$_.IsMailboxServer -eq 'True'}
$dmtf = [System.Management.ManagementDateTimeconverter]
$Start = $dmtf::ToDmtfDateTime( (Get-Date).AddDays(-1).Date )
$db = @{Name="DB";Expression={$_.InsertionStrings[1]}}
$free = @{Name="WhiteSpace(MB)";Expression={[int]$_.InsertionStrings[0]}}
$filter = "LogFile='Application' AND EventCode=1221 AND TimeWritten>='$Start'"
Get-WMIObject Win32_NTLogEvent -ComputerName $ComputerName -Filter $filter | select ComputerName,$db,$free | export-csv salida.csv -Force -NoTypeInformation

Enjoy!

-Dario

How to get mailbox size from Exchange 2010 and Exchange 2007

Another cool script that always is requested for ours managers. Get the MBX size from one Exchange mailbox server (CMS) whit a sorted output, you could switch the -server for -database .Form more info regard Get-MailboxStatistics 2007  & Get-MailboxStatistics 2010. Thanks God this  powershell query is useful for both Exchange version.

Enjoy!!

-Dario
diseño pagina web
desarrollo web
desarrollo web
cannaweed
comprar bisuteria
desarrollo web
diseño pagina web
empresas de trabajo
cannaweed
comprar bisuteria
desarrollo web
diseño pagina web
empresas de trabajo
psicologo on line
cannaweed
comprar bisuteria
desarrollo web
empresas de trabajo
link text
mejor seguro medico
psicologo on line
seguro familiar cannaweed comprar bisuteria desarrollo web empresas de trabajo link text mejor seguro medico proteinas masa muscular psicologo on line seguro familiar cannaweed comprar bisuteria cuidados en el embarazo desarrollo web empresas de trabajo link text mejor seguro medico proteinas masa muscular psicologo on line seguro familiar
booking system
cannaweed
cuidados en el embarazo
empresas de trabajo
link text
mejor seguro medico
proteinas masa muscular
psicologo on line
seguro familiar
Seguros vida

booking system
cannaweed
coches de segunda mano
cuidados en el embarazo
empresas de trabajo
link text
mejor seguro medico
psicologo on line
seguro familiar
Seguros vida
booking system
cannaweed
cestas y lotes navideños
coches de segunda mano
cuidados en el embarazo
empresas de trabajo
link text
mejor seguro medico
seguro familiar
Seguros vida

Where is my rollup build number in Exchange 2010 and 2007?

Hey all!!!
this morning I've found a crazy thing about the Exchange built version, as you know simply with a Get-ExchangeServer | fl name,*version*, we can get

AdminDisplayVersion : Version 14.0 (Build 639.21)
ExchangeVersion     : 0.1 (8.0.535.0)

So if you see the table below you can see that this version matches with the RTM version.

Como zafar del infierno de un tracking en Exchange 2007- Updated

Estimad@s,

les paso un script  útil para hacer un track en 2007 en todos los hub transport servers de una, sin tener que hacer varios tracks por server, pegen el codogo de abajo en un txt con extension ps1 y corranlo desde una consola de EMS, espero que les sea útil

　

$servers = Get-Exchangeserver|where {$_.isHubTransportServer -eq $true}

$servicios = Get-Service -computername $servers | where {$_.displayname -like "*transport log*"}

foreach ($server in $servers){

foreach ($servicio in $servicios){

write-host $server.name

write-host $servicio.displayname

if ($servicio.status -eq "Running"){

Get-MessageTrackingLog -server $server.name -Recipients:user@domain.com -EventId "RECEIVE" -Start "01/18/2011 0:00:00" |fl Sender,Recipients,ServerHostname,Timestamp,MessageSubject

}else{

write-host $server.name + "has the service " + $servicio.displayname $servicio.status

}

}

}

Note: This script run on Windows Powershell 2.0
(thank you JuanMa)