Connection broken between ISA FW and ISA Storage conf.

The only case that I see this issue is when the cert on ADAM instance was expire, but I have the same issue with a intermediate Verising cert for an application.

Verising has two new cert for SLL apps, so take care with those because there is one that has problem with ISA server:

1.

2.

Those certs has a different serial number version, on one of those there is something wrong because when we paste it on the server, isa server stop to work:

‎ VeriSign Class 3 Public Primary Certification Authority - G5 (serial number)

1b 09 3b 78 60 96 da 37 bb a4 51 94 46 c8 96 78 --- wrong cert

18 da d1 9e 26 7d e8 bb 4a 21 58 cd cc 6b 3b 4a--- wrong cert

‎25 0c e8 e0 30 61 2e 9f 2b 89 f7 05 4d 7c f8 fd --- correct cert

Solution:

Just replace the cert for the correct one and the problem will be solved.

3.

4.

On this document there is information about How to Securely Publish a Configuration Storage Server in ISA Server 2006 and also how to change an expiate certificate:

http://technet.microsoft.com/en-us/library/bb794830.aspx

How to Back Up and Restore an ISA Server Enterprise Configuration (Enterprise Edition)

http://technet.microsoft.com/en-us/library/bb794757.aspx

In ISA Server 2006 EE the configuration is stored in ADAM (Active Directory Application Mode)
Connect to you ADAM ADSI Edit
Server Name: localhost and port: 2171
Connect to the following node:
Distinguished name (DN) or namingContext: CN=FPC2
Navigate to CN=Array-Root
CN=Arrays
CN={ID of your Array}
CN=ArrayPolicy
CN=PolicyRules
CN={ID of the bad rule}

5.

How to delete Logs in a Exchange 2007 CCR

Here is the process to manually remove log files. As a reminder once this is done you will NOT be able to perform an incremental backup until a FULL backup is completed.


1. Suspend replication on the server
a. Get-StorageGroup -Server | Suspend-StorageGroupCopy
2. On the passive node check the database header to find out the logs required.
a. Eseuil /mh (the ‘State’ will be Dirty Shutdown, this is expected and not an issue).
b. Look for ‘Log Required’. This will tell you which logs CANNOT be removed. Anything before those logs are safe to remove.
i. Looking at the sample below, Logs Exx00004A42-Exx00004A45 cannot be removed. Logs Exx00004A41 and earlier can be removed. (Exx will depend on the SG…can be E00, E01, E02, etc.)
3. Resume replication on the server
a. Get-StorageGroup -Server | Resume-StorageGroupCopy
4. Run Get-StorageGroupCopyStatus and check that CopyQueueLength and ReplayQueueLength are 0
5. Perform a switchover using Move-ClusteredMailboxServer and repeast the process on the former active (now newly passive) node.
6. Perform a FULL Backup. All previous backups are now invalid.

[PS] C:\>eseutil /mh F:\CCRMBX1\CCR-SG4.edb
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.02
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
DB Signature: Create time:11/25/2008 16:50:25 Rand:102284345 Computer:
cbDbPage: 8192
dbtime: 165542 (0x286a6)
State: Dirty Shutdown
Log Required: 19010-19013 (0x4a42-0x4a45)

Also here there is a procedure to run a backup with windows 2008:

http://technet.microsoft.com/en-us/library/ee221177(EXCHG.80).aspx

Siii robocopy en w2008

Esta fue una tool muy utilizada por los administradores de file server, muy poderosa y de mucha auyuda, la buena noticia es q viene incluida en esta version de windows.

Para los administradores de Echnage, con los nuevos logs de 1mb en 2007, es muy util para mover logs por falta de espacio en disco:

robocopy x:\LG09 z:\temp e09002b*.log /R:1 /W:1 /mov /LOG:c:\ROBOLOGexch5.txt
comando--origen----destino--criterio-------reintentos-espera--move--log

http://technet.microsoft.com/en-us/library/cc733145%28WS.10%29.aspx

OCS y grupos en la GAL

Managing the Address Book Server from the Command Line

You can manage the Address Book Server by running ABServer.exe from a command prompt. You can modify the environment path system variable to include the location of ABServer.exe (%programfiles%\Microsoft Office Communications Server 2007\Server\Core), or you can run the tool directly from the Office Communications Server Address Book directory.

Table 6 shows valid command switches and arguments.

http://technet.microsoft.com/en-us/library/bb936631%28office.12%29.aspx

Este blog es muy interesante, esta todo el deploy de ocs:

Office Communications Server 2007 Enterprise Deployment

http://www.shudnow.net/2008/06/08/office-communications-server-2007-enterprise-deployment-part-1/

Routing en modo misxto

Como funciona:

When only one routing group connector is established between Exchange 2003 and Exchange 2007, you do not have to make any changes to link state, and routing loops will not occur. However, if more than one routing group connector is configured between Exchange 2003 and Exchange 2007, the minor link state updates that are transmitted between Exchange 2003 servers can introduce problems. When Exchange 2003 detects that a connector is unavailable, link state updates are communicated throughout the Exchange organization to notify them of the connector down state. The Exchange 2003 bridgehead server also tries to determine an alternative route for message transfer to the destination server. However, Exchange 2007 does not use link state to determine a routing path. The Exchange 2007 Hub Transport server will be unaware of the down connector state and may decide to route a message back through a routing path that Exchange 2003 is trying to route around.


Q es liknk state?? Disabel en 2003 para evitar problemas de looping:

To avoid routing loops, you must suppress minor link state updates before introducing additional routing group connectors. Minor link state updates are sent between Exchange 2003 servers to update the link state routing table to indicate that a connector is down. When the SuppressStateChanges registry key is set, you are turning off the ability for a connector to be marked as down. Link state messages are also used to notify Exchange 2003 servers of configuration changes to the Exchange organization, such as the addition or removal of a connector or a server. When you suppress minor link state updates, it does not prevent these major link state update messages from being communicated.

When minor link state updates are suppressed, Exchange 2003 also only uses least cost routing. This eliminates the chance for routing loops to occur. We recommend that you suppress link state updates on every Exchange 2003 server in the organization to maintain a consistent configuration.

Lo mas importante q me llamo mucho la atención:

mportant: If configuration changes are made in Exchange Routing Group (DWBGZMFD01QNBJR) some latency may occur before those changes are received by Exchange Server 2003 servers and propagated by the Exchange 2003 routing group masters. The delay will depend on how frequently the routing group masters poll for configuration changes in other routing groups. By default, the polling interval is set to one hour. To immediately register all changes in Exchange Routing Group (DWBGZMFD01QNBJR) on Exchange 2003 servers, you must restart the routing group masters.



Articulo:

http://technet.microsoft.com/en-us/library/bb125223%28EXCHG.80%29.aspx

Message Tracking

Exchange 2007 tiene una solucion de track, una salvedad es q cuado se ejecuta desde una consola solo buscara el track con los logs locales de ese particular hub server.
La consola muestra por debajo la opcion de Pshell para ejecutarla, con lo q la solucio n seria:

Get-ExchangeServer | where {$_.isHubTransportServer -eq $true -or $_.isMailboxServer -eq $true} | parametros de consola

http://technet.microsoft.com/en-us/library/bb124926%28EXCHG.80%29.aspx

Working With the Search Results

Once you have a search which returns the results you need, you may want to convert those results into other formats, perhaps to use for reports or to provide information to others. PowerShell includes built-in cmdlets for re-formatting output data, and those can be used in conjunction with the Get-MessageTrackingLog cmdlet. For the ‘Recipients’, ‘RecipentStatus’ and ‘Reference’ properties it’s necessary to convert the data so that it appears in the output files.

To convert the results to CSV format you can pipe the search command to the Export-CSV cmdlet. This command will create a CSV file called C:\Temp\SearchResults.csv, exporting all the available fields:

[PS] C:\>Get-MessageTrackingLog -Server EXCHANGE01 -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | Select Timestamp, ClientIp, ClientHostname, ServerIp, ServerHostname, SourceContext, ConnectorId, Source, EventId, InternalMessageId, MessageId, {$_.Recipients}, {$_.RecipientStatus}, TotalBytes, RecipientCount, RelatedRecipientAddress, {$_.Reference}, MessageSubject, Sender, ReturnPath, MessageInfo | Export-CSV C:\Temp\SearchResults.csv

This command will create a CSV file including only the timestamp, event ID, sender, recipients, and subject line:

[PS] C:\>Get-MessageTrackingLog -Server EXCHANGE01 -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | Select Timestamp, EventID, Sender, {$_.Recipients}, MessageSubject | Export-CSV C:\Temp\SearchResults.csv

Alternatively, to convert the results to HTML you can pipe the search command to the ConvertTo-HTML cmdlet. Use this command to export the results to an HTML file showing the timestamp, event ID, sender, recipients, and subject line:

[PS] C:\>Get-MessageTrackingLog -Server EXHUB-00-UK -EventID SEND -Sender john@example.com -Recipients bill@example.net -Start 12/3/2009 -End 13/3/2009 | ConvertTo-Html Timestamp, EventID, Sender, {$_.Recipients}, MessageSubject | Set-Content C:\Temp\logs.html

El siguiente ling tiene un script muy bueno de como sacar una metrica del dia anterior:

http://www.simple-talk.com/content/print.aspx?article=681

Reporting on e-mail messages sent and received yesterday

Circular loging

Switching CCR Storage Groups into Circular Logging during Migration - and why you might want to do this…

De la pagina Telnetport25, (jajaj muy bueno el nombre), estos muchachos subieron un script muy bueno q habilita CL en forma automatica, claro q esto implica montar y desmontar las bases de datos, este script lo hace en forma automatica.

La mala noticia es q para exchange2007 CCR cluster esto no es suficiente, tenemos q reinicia el servicio de MSExchangeIS o hacer un Fail Over.

http://www.telnetport25.com/component/content/article/16-exchange-2007-ccr/318-switching-ccr-storage-groups-into-circular-logging-during-migration-and-why-you-might-want-to-do-this.html

Esto es lo q dice MS con respecto a CL, ya es voz populi:

n the release to manufacturing (RTM) version of Exchange 2007, combining circular logging with cluster continuous replication (CCR) or local continuous replication (LCR) is supported. However, we do not recommend this because it does not allow a roll-forward recovery after a backup has been restored. Exchange 2007 Service Pack 1 (SP1) also allows storage groups in a CCR, LCR or standby continuous replication (SCR) environment to have circular logging enabled. However, this practice is also not recommended for the reason indicated previously. When enabled in either of these environments, the functionality is CRCL and not ESE circular logging (also known as Joint Engine Technology (JET) circular logging). In a CCR, LCR, or SCR environment, you should always use the following process to enable or disable circular logging:

1. Suspend continuous replication by using the Suspend-StorageGroupCopy cmdlet.
   
2. Enable or disable circular logging. For detailed steps about how to enable or disable circular logging, see How to Enable or Disable Circular Logging for a Storage Group.
   
3. Dismount and then mount the database in the storage group that is being enabled or disabled for circular logging.
   
4. Resume continuous replication by using the Resume-StorageGroupCopy cmdlet.

http://technet.microsoft.com/en-us/library/bb331951%28EXCHG.80%29.aspx

Esto ultimo no es tan asi por mi comentario anterior.