Nonpaged Pool Memory

what distinguishes Paged Pool and NonPaged Pool memory? The first difference is that Paged Pool is exactly what its name implies - it can be paged out. The NonPaged Pool cannot be paged out. Drivers use the NonPaged Pool for many of their requirements because they can be accessed at any Interrupt Request Level (IRQL). The IRQL defines the hardware priority at which a processor operates at any given time (there's a link to a document covering Scheduling, Thread Context and IRQL's in the Additional Resources section at the end of this post).

Getting back to our Pool Resources, it is important to remember that these resources are finite. The table below outlines some sample maximum values for Paged / NonPaged Pool on x86 systems that are not configured with the /3GB switch in the system's boot.ini file. We'll cover /3GB and its effects on memory in a future post. We'll also cover Kernel Changes to Windows Vista separately. It's important to note that x64 systems don't suffer from the same Virtual Address Space limitations!

Windows 2000

System RAM	NonPaged Max	Paged Max	Paged Max (TS)
512 MB	131 MB	264 MB	160 MB *
1024 MB	212 MB	268 MB	160 MB *
1536 MB	256 MB	340 MB	160 MB *
2048 MB	256 MB	340 MB	160 MB *

* If Terminal Services is installed on Windows 2000, Paged Pool is lowered down to 160 MB unless a registry change is made to the server to set the Paged Pool Size to its maximum value (see below).

Windows 2003 SP1

System RAM	NonPaged Max	Paged Max
512 MB	125 MB	184 MB
1024 MB	202 MB	168 MB
1536 MB	254 MB	352 MB
2048 MB	252 MB	352 MB

On Windows 2003 systems, Terminal Services are enabled by default.

On both Windows 2000 and Windows 2003, the HKLM\System\CurrentControlSet\Control\Session Management\Memory Management\PagedPoolSize value can be set to 0xFFFFFFFF (or resetting the value to 0) to ensure that the Virtual Address Space used for Paged Pool is maximized.

Also - here's the theoretical maximums for pre-Vista Operating Systems:

Region	IA-64	x64	x86
Process Address Space	7152 GB	8192 GB	2 to 3 GB*
Paged Pool	128 GB	128 GB	470 to 650 MB
NonPaged Pool	128 GB	128 GB	256 MB

http://blogs.technet.com/b/askperf/archive/2007/03/07/memory-management-understanding-pool-resources.aspx


For server runing Exchange 2003

The following table displays the matrix of evaluations used by the Exchange Server Analyzer to determine whether this value is out-of-bounds for a specified Exchange server. If the conditions in the following table are matched, a warning is displayed.

Operating System	Boot.ini Setting	Current Non-Paged Pool is
Microsoft Windows 2000 Advanced Server	/3GB	100 MB or more
Microsoft Windows 2000 Server or Advanced Server	None	200 MB or more
Microsoft Windows Server™ 2003	/3GB	100 MB or more
Microsoft Windows Server 2003	None	200 MB or more

The PoolNonpagedBytes key value is the size, in bytes, of the kernel memory non-paged pool. This is an area of physical system memory for objects that cannot be written to disk even when they are not being used. This value for this key is the last observed value. On a healthy Exchange server, unless a backup or restore is occurring, there should be no more than 85 MB of non-paged pool memory being used.

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

Schedule free bussy

Outlook 2003 and 2007

Outlook 2007 will look for a Client Access Server to view free/busy info. Exchange 2003 uses public folders to publish free/busy info.

To force Outlook 2007 to look for Public Folder based Free/Busy information you need to hack the registry:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Calendar
Value Type: DWORD
Value Name: UseLegacyFB
Values:0 or not set (default behavior which is to use the Availability Service) or 1 (use Public Folder based Free/Busy information)

Special Considerations for Working with Client Permissions

For outlook 2003

MS recomendation:

By default:

For outlook 2007:

· Si ambos usuarios no están, usen PFadmin para reparar los permisos, al agregar o modificar permisos, también corrige problemas.

------------------------------------------------------------------------------------------------------------------------------------------------------

Algunos testeos q están buenos:

Test configuration on outlook 2007

# While Outlook 2007 is running, hold down the CTRL key, right-click the Outlook icon in the notification area, and then select Test E-mail AutoConfiguration.

# Verify that the correct e-mail address is in the box next to E-mail Address.

# Clear the check boxes next to Use Guessmart and Secure Guessmart Authentication.

# On the Test E-mail AutoConfiguration page, verify that the check box next to Use AutoDiscover is selected, and then click the Test button.

Enable TST

# In Outlook 2007, on the Tools menu, click Options, click the Other tab, and then click Advanced Options.

# On the Advanced Options page, select Enable logging (troubleshooting), and then click OK.

# Restart Outlook 2007, and then try to view free/busy information for another user.

# In Microsoft Windows, click Start, click Run, and then type %temp%.

# In Windows Explorer, open the olkdisc.log file and locate the files in the olkas directory.

SSL services in exchange 2007

On exchange 2007 there are many client protocols as 2003 as well, when import a cert on the CAS or HUB server, we are able to co consolidate or associate those with all services (pop3, imap4,smtp,owa).

For a clients outlook express and SMTP we must take care with the configuration, by default there is a receive connector for a clients:





On the client:

We are using an internal PKI and in order to request a new SMTP certificate using the Exchange Management Shell use the following cmdlet:

New-ExchangeCertificate –GenerateRequest –Path c:\cert.req –SubjectName “cn=relay.apatricio.local” –FriendlyName “Internal Relay Certificate” –PrivateKeyExportable:$True

Now, let’s request the certificate created using the Certification Authority webpage:

1. Logged on Exchange Server open the http:///certsrv, where is your server which hosts the Certification Authority.
2. Click on Request a Certificate link.
3. Click on advanced certificate request.
4. Click on the second link which is Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
5. Open the file C:\cert.req which was created by New-ExchangeCertificate cmdlet and copy the content.
6. Paste the content of that file into the Base-64-encoded certificate request field in the webpage.
7. On the same page, select Web Server in the Certificate Template field and then click the Submit button.
8. On the new page, click on the Download Certificate link and save it in the C:\ root of the Exchange Server.

Let’s import the new certificate, to do that use this cmdlet:

Import-ExchangeCertificate –Path:C:\certnew.cer

Note:
The file name and path is just an example, you have to use the file name and path that you have used in the previous step.

Time to enable the new imported certificate to be used by the SMTP service using the Exchange Management Shell. To enable it we just need to copy the Thumbprint that was shown when we imported the request in the previous step and use this cmdlet:

Enable-ExchangeCertificate –Thumbprint -Services SMTP

You will be prompted to change the default SMTP certificate, just type in N and hit enter.

Use get-excgangecertificates | fl PS to see the current services attached on the cert:

More information:

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

For enable logging:

Information Store and Log sequence numbers

Event 514 on our exchange server means that the logs sequence is consume and when is completed, all Exchange databases will dismounted.

Information Store (6768) XXX: Log sequence numbers for this instance have almost been completely consumed. The current log generation is 933000 (0x000E3C88) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 115559 (0x0001C367) log generations.

So the maximum log generation is 1048559 (0x000FFFEF) and remains 115559 logs to consume, so ig we find on the APP eventvwr the event number 214, we can estimate how many logs our Exchange use by day and we can estimate how many days we have until to have this problem.

Exchange 2007 supports 2 billion log files (2147483628) which is 7fffffec in hexadecimal.

Notice that if you miss the ESE 514 warning your databases will dismount and generate the following events:

Event ID: 1159
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Description: Database error 0xfffffdf9 occurred in function JTAB_BASE::EcEscrowUpdate while accessing the database "First Storage Group\Mailbox Store (SERVER)".

Event ID: 9518
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Description: Error 0xfffffddc starting Storage Group Path_of_Storage_Group on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed.

More info.
http://support.microsoft.com/kb/830408

Solution:

One of the common solution is dismount all database that are part of storage group, move out all logs and CHK file, mount all databases, CHK file and transaction logs will create starting in 0.

1--


2--


3--


4--


After that, all incremental backup are unusable, so run a full backup after this procedure.

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