Server: Exchange 2007 on Windows 2008 – 64 Bit, in a VMWare environment. The server has 4 GB of RAM.
Symptom: I run performance counters (scripts) every 15 minutes to collect statistics on usage, resources and local CPU percentages. Recently I have began seeing errors where the WMI service tanks and my counters cease to dump data. There errors is:
This problem may occur if the computer experiences a low-memory condition. When the computer experiences a low-memory condition, memory corruption may occur in the private heap of a dynamic link library (.dll) file. These random heap corruptions may cause programs to crash.
Memory corruption may occur when you run memory-intensive programs on a computer that has the Intel Physical Addressing Extensions (PAE) specification enabled. PAE enables a computer to support more than 4 gigabytes (GB) of installed memory.
We doubled the RAM from 4 GB to 8 GB. I noticed by digging into the perfmon counters, we were paging at higher level than anticipated, which indicated the RAM was insufficient at its current amount.
To set the server with a static IP address:
Find which Network Adapter to set:
At a command prompt, type the following:netsh interface ipv4 show interfaces
Bind Network Settings to a specific Network Adapter:
Look at the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address.
At a command prompt, type the following:
netsh interface ipv4 set address name="<ID>" source=static address=<StaticIP> mask=<SubnetMask> gateway=<DefaultGateway>
- ID is the number from step 2 above
- StaticIP is the static IP address that you are setting
- SubnetMask is the subnet mask for the IP address
- DefaultGateway is the default gateway
To specify DNS
At a command prompt, type the following: netsh interface ipv4 add dnsserver name="<ID>" address=<DNSIP> index=1
Repeat step 4 for each DNS server that you want to set, incrementing the index= number each time.
Verify by typing ipconfig /all and checking that all the addresses are correct.
So far, my experiences with Windows Server 2008 has been less than stellar, from a application server perspective. One bad caveat, the Windows 2008 Server RTM code does not allow you to perform a RunAs on any account other than the “administrator”. This is especially bothersome when you are trying to run or install an application using a different credential. (i.e., Exchange 2007)
Microsoft’s newly acquired Sysinternals has a new utility that restores this functionality.
From the command-line perform a "shellrunas /reg"
So far it has worked great, however, one thing to note, is you must run this command on every user needing the functionality. It appears to install on a per-user basis.