I installed a Windows 2003 Service Pack 1 server with ISA 2004 Standard edition Service Pack 1. After a few days logging on to the ISA server I got the error “Out of memory”. After checking the Task Manager to find out what process was the problem I noticed it was SQLServr.exe. It was using about 1,7 Gb of memory. As there is only 2 Gb of memory and some other processes also require some memory, I wanted to know how I could lower the usage of the SQL Server (MSDE).
On an ISA 2004 (including Service Pack 1) I have configured the cache size.After a reboot I noticed the following error :
Disk cache D:\urlcache\Dir1 failed to initialize.
I noticed on my servers that everytime I had a restart, the following events were placed in the eventviewer.
EventID : 1015
Source : EvntAgnt
TraceLevel parameter not located in registry; Default trace level used is 32.
EventID : 1003
Source : EvntAgnt
TraceFileName parameter not located in registry; Default trace file used is.
Ever had the need to script the installation or removal of Windows Components? As some of you might not know, there is a tool present on your Windows 2003 system which can perform this task.The tool is called : sysocmgr.exe (System stand-alone Optional Component Manager)
RIPREP images created on (for example hp/compaq dx6100mt/d530s) which have Broadcom NetXtreme Gigabit Ethernet controllers (bcm47x) are not listed as an available choice to other machines on the RIS OS Choices screen – including even a hp/compaq d330m computer which has the same Broadcom NetXtreme Gigabit Ethernet controller.
To verify that your Exchange servers can resolve internal DNS names, you can use the DNS Resolver Tool (DNSDiag.exe) from Microsoft. Dnsdiag.exe is available for use on Exchange servers running Microsoft Windows Server™ 2003. This tool simulates the internal code path of the SMTP service and generates diagnostic messages that indicate how DNS resolution is proceeding.
The Windows 2003 support tools are a collection of resources with the aim of assisting administrators to simplify management tasks. These include: troubleshooting operating systems, configuring networking and security features, managing Active Directory, and automating application deployment. With the use of these tools, the user is able to pin-point problematic issues with the system and will therefore be able to find a solution more easily.
By default, the Security tab is missing in the Exchange System Manager. To display the permissions tab, you have to make a change to the registry.
Here is the correct path to navigate:
HKEY_Current_User\Software\Exchange\ExAdmin.
When you reach the above section of the registry you need to create a DWORD called ShowSecurityPage.
A value of 1 (Numeric one) means on, whilst 0 (Zero) means off.
Close the Exchange System Manger, then reopen (no need for a reboot).
For more info: http://support.microsoft.com/default.aspx?scid=kb;en-us;264733
Exchange admins will check the queue’s in Exchange System Manager (ESM) on a regular basis. But what if one of these queue’s is filling, do you know where to begin to check? Here are a few tips which will maybey help you find the problem a little bit faster.
With the help of ESEUTIL you can defragment your Exchange information store offline, check the integrity of the store and repair the information store in case of emergency. ISINTEG is used to perform some tests on the information stores and to fix some errors.