By filling up all free space, impurities are effectively prevented from entering and damaging bearings and lubricating intervals can be extended.

For most other greases, general rule applies.

Bearings can be divided into two categories - non-separable and separable bearings. No matter which bearing type it is, general practice is to fill up space between inner race, outer race, and rolling components (ball or roller) on both sides of bearing. Because of its consistency, grease should be able to remain in place without dropping off. In this way, we can ensure that rubbing contact surface actually has grease on it.

For relubrication, how much is enough? The following formula gives a good indication:

G = 0.005 DB

where, G = grease quantity in grams D = bearing outside diameter in mm B = total bearing width in mm

By practicing proper lubrication, bearings should be able to last for a long time. However, bearings can still fail if it has not been installed properly or for other reasons.

Until next time...

Check Out What Happens at Home! Amazing Spy Camera lets You check your maid, children, family while you are away. Excellent Monitoring Tool for Industry and Home.

But, what happens if you have multiple application pools running as same user? For example, if you keep to default NETWORK SERVICE user but create multiple Application Pools, you may want to know which process belongs to which App Pool. Component Services doesn't work for this anymore.

Enough already, tell me how to do it!

Have no worries, Microsoft has given us exact tool for situation. IISApp.vbs lists all applications, their PID and their App Pool name.

The script is already placed in systemrootsystem32 on Windows Server 2003 so simply go to your Command Prompt and type in iisapp.vbs (the .vbs is optional) and you'll have an instant list of all App Pool information you've always wanted to know. You may need to type cscript iisapp.vbs if CScript isn't your default WSH script host.

Let's see an example of output:

W3WP.exe PID: 1468 AppPoolId: AppPoolForSite1.com W3WP.exe PID: 3056 AppPoolId: AppPoolForSite2.com W3WP.exe PID: 1316 AppPoolId: AppPoolForSite3.com

Direct from horse's mouth, Microsoft documents this:

http://www.microsoft.com/resources/documentation/WindowsServ/2003

Summary

We've seen here that using iisapp.vbs, you can painlessly match up PID to friendly name of Application Pool.

Scott Forsyth is Director of IT with ORCS Web, Inc. - a company that provides managed hosting services for clients who develop and deploy their applications on Microsoft Windows platforms.