Improve your Windows server's performance: 10 tips

There are a number of simple things you can do to help increase your server's performance. None of these things -- with the possible exception of moving the pagefile to a dedicated disk -- will do much by itself, but collectively these techniques can improve server performance noticeably.

1. Use a dedicated drive for the pagefile This is probably the tip that will give you the largest performance gain. By default, Windows creates a pagefile that it treats as virtual memory. Because Windows uses this file frequently, it's best to place it on a dedicated drive (not a dedicated volume). Doing so ensures that Windows will not have to wait on another application to finish using the hard disk before it can read data from the pagefile.

2. Keep your hard disks defragmented Modern hard drives are extremely fast when performing sequential reads. However, performance goes out the window when the disk is asked to read data stored in random locations. By keeping your hard disk defragmented, you ensure that blocks of files are placed in sequence rather than scattered randomly across the surface of the drive, thus allowing your computer to read files more efficiently.

3. Use the NTFS file system Although NTFS is the default file system for Windows servers, Windows does support the use of FAT and FAT-32 file systems. Every MCSE training book I've ever read recommends using the NTFS file system is because it is more secure than alternative file systems. What these books fail to mention is that NTFS is a transaction-based file system. This means that NTFS is slightly faster, and much less prone to corruption than the FAT or FAT-32 file systems.

4. Avoid running 16-bit applications 64-bit Windows operating systems can't run 16-bit applications at all, so this one isn't even an issue for those with 64-bit operating systems. 32-bit Windows operating systems will run 16-bit applications, but at a price. Windows uses a separate multitasking model for 16-bit applications than for 32-bit applications. The specifics of how Windows multitasks 16-bit applications would require a separate article, but suffice to say that running 16-bit applications negatively effects performance.

5. Look for memory leaks
Memory leaks are caused by poorly written applications. It's normal for an application to request memory from the operating system on an as-needed basis. Typically, an application will return memory to the operating system when it is no longer needed. An application that contains a memory leak will ask for memory when it needs it, but will fail to release the memory when it is finished using it. The next time the application needs memory, it will ask Windows for more, rather than using the memory it has already reserved. Over time, Windows has less and less memory to assign to other applications.

Memory leaks have a negligible effect on system performance at first, but over time their effects become more and more noticeable as the application continues to run. Although I said I wasn't going to talk about performance monitoring, Performance Monitor really is the best tool for finding memory leaks.

6. Remove seldom-used utilities Every server has come with all sorts of monitoring or logging utilities. If you use these utilities on a regular basis, there's nothing wrong with having them installed on the server. But it never fails to amaze me how many administrators install (or never remove) utilities that come with the server, and then never use them. Running an application you're not actually using is a waste of server resources.
7. Disable unused services On a similar note, I also recommend looking through the Service Control Manager and disabling any services that are not required for the role the server is performing. Not only will disabling unused services increase the server's performance, it will also increase the server's security. A law of computing states that the larger the executing code base, the greater chance that the code contains an exploitable vulnerability. By disabling unnecessary services, you are shrinking the size of the executing code base, thereby reducing the chances of the server containing an exploitable security hole.
8. Log off This is another example of a situation in which you can increase security and performance at the same time. You should always log off of a server when you're not actively using the console, for security reasons. At the same time, when you are logged on, Windows loads your user profile. This consumes memory and CPU cycles.
9. Compress the hard disk
When Microsoft released MS-DOS 5.0, they introduced the disk compression feature. At the time, the idea was that a hard or floppy disk could be compressed so that more data would fit on the drive. Back then I tried using disk compression, and my computer slowed down so much that I went back to using an uncompressed disk, and never looked at compression again until recently.

Today, under the right circumstances, compression can actually increase performance. Hard drives are typically the slowest component in a computer. However, if you can compress a file, you reduce its physical size, which also reduces the amount of time that it takes to read the file from the disk. At the same time, a compressed file must be decompressed after it has been read from the disk. The decompression happens on-the-fly in memory, and the process uses some CPU time in addition to memory. If your server is running a disk-intensive application that deals with a lot of individual files (not a database), compression may improve performance. Otherwise, you're probably better off not compressing a hard disk.

10. Adjust the server response
A server is different from a desktop computer in that applications are not usually run from the server's console. That being the case, it's best to optimize the server so that applications running in the background take priority. You can do this by opening the Server's Control Panel and double-clicking the System icon. When Windows opens the System Properties sheet, go to the Advanced tab and click the Settings button found in the Performance section. Windows will now open the Performance Options properties sheet. Go to the properties sheet's Advanced tab and make sure that Windows is set to provide the best performance to background services

GUIDELINES FOR COMPUTER USERS
GUIDELINES FOR COMPUTER USERS

(TO ALL SUPERVISORS AND ALL POSTAL ASSISTANTS)
DO’s

1.                All PAs and Supervisors should use their own password and periodically changed (at least once in a fortnight) and should not be shared with any one to prevent access to unauthorized persons.
2.                Take necessary precautions against natural hazards like fire, rain, dust, etc. Users should clean the printer, keyboard and monitor externally once in a week.  Cleaning brush will be provided in the lab.
3.                Printer should be switched off whenever it is not in use.
4.                Take enough precautions against computer viruses by not allowing any outside floppy, pen driver or Compact Disk or any e-mail attachments for use without scanning for the viruses.
5.                Periodical change of Ribbons in the Printer should be carried out. Please ensure that impressions are bright and clear.
6.                Rectification of faults and maintenance should be carried out under proper and close supervision and service report from the service engineer should be obtained.
7.                In case the shift system is in vogue, there should be proper handing and taking over of charge between shift in-charges.
8.                Concerned supervisor should allocate Job to the Postal Assistants whenever Postal Assistant in the Counter and also in other branches is changed.  Whenever delivery staff is changes proper name of the delivery personnel to be used.  Concerned Supervisor may ensure that Postal Assistants enters into the system with their name and password only.
9.                At close of work in a day, System should be shut down systematically and switch off the power plug too.
10.           Wherever Day begin and Day End is prescribed, Supervisors may ensure that this is done by them.
11.           In the case of sub offices the Postmaster should ensure that Backup of sanchaya post is sent to Supervisor SBCO in the first week of every month without fail.
12.            Telephone connection and power supply to modem should be removed in the evening (during rainy seasons) to avoid damage to modem and computer. 
13.              Systems identified for the backup purpose should be switched off only after the backup is over. 

DON’Ts

1.    Don’t let any unauthorized person use your computer system.
2.    Don’t share your password with any one, not even with your colleagues.
3.    Don’t reveal the password to any person.
4.    Don’t connect the computer directly to the mains.
5.    No heavy electric load drawing machines like plain paper copier, shredding machines, coolers, etc. should be connected to the source of constant voltage power supply to the computer.
6.    Don’t connect your computer system storing classified data to INTERNET.
7.    Don’t allow staff members to bring their own pendrives/floppies/re-writable CDs to run on the computer system of the department.
8.    Don’t use pirates or gifted copies of software as these may contain virus and even facilitate intrusion into the system.
9.    Don’t play computer games. These could be the main carriers of computer viruses and an unsuspecting easy medium for an intruder to break into your computer system.
10.Don’t allow eatable and water near the computer as these attract rats/pests and raise the dust and moisture level to the detriment of the computer system.
11.Don’t switch off the computer suddenly.  Sudden power fluctuation/failure may leads to corruption/deletion of data.
12.Don’t rotate the printer cylinder while the printer is in ON position. Switch off the printer when not in use.
13.Don’t work on Server system without Postmaster’s permission.
14.Don't plug or unplug any devices like keyboard, mouse etc.,  to the system while it is on.
15.Don't keep ledgers/books etc on systems, keyboards, mouse, weighing scales etc.
16.Don't connect UPS to lights, fans etc. Use exclusively for computers.
*************
NOTE

            To the maximum extent possible all the above guidelines may be followed strictly to avoid embarrassing situation later.  Your doubts/difficulties, if any to implement the guidelines may be raised for taking assistance of the SA.  These guidelines are intended to upgrade our working method and to safeguard the systems as well as Data.                          

Advanced Repair Options for Windows Boxes (தனஞ்செழியன் அவர்கட்கு நன்றிகள் )

For example, if a blue screen appears in windows XP or any Win OS, we cannot enter into the system. Restoration to a old date is also not possible as we could not able log in to the system.. In this situation, we are left with only one solution. Just the "Brain Operation"

Put the XP Live CD in the CD Drive and reboot the machine.

select miniXP

Go to C:\System Volume Information\RP1\snapshot
(RP1 may be replace with any of the latest restoration point. RP1 or RP2 or RP3 etc)

copy the following files
_REGISTRY_MACHINE_SAM
_REGISTRY_MACHINE_SECURITY
_REGISTRY_MACHINE_SOFTWARE
_REGISTRY_MACHINE_SYSTEM
_REGISTRY_MACHINE_DEFAULT

paste these files in the following folder
C:\windows\system32\config
rename the existing SAM, SECURITY, SOFTWARE,SYSTEM,DEFAULT files to SAM1,SECURITY1,SOFTWARE1,SYSTEM1,DEFAULT1 etc.

rename above files to

_REGISTRY_MACHINE_SAM ----> SAM
_REGISTRY_MACHINE_SECURITY ---> SECURITY
_REGISTRY_MACHINE_SOFTWARE---> SOFTWARE
_REGISTRY_MACHINE_SYSTEM-------> SYSTEM
_REGISTRY_MACHINE_DEFAULT------> DEFAULT

now remove the CD and start with windows you prefer.
Thats all folks. The Brain Operation is over.