Monday, 23 August 2010
Thursday, 12 August 2010
How to find memory leak Using Performance Monitor
Access Performance Monitor by entering the PERFMON command at the server's Run prompt. When Performance Monitor opens, several counters (mechanisms that Performance Monitor uses to measure some individual aspect of the server's performance) will already have been loaded. Click the X icon repeatedly until all default counters have been removed. You can now load new counters by clicking the + icon.
Individual counters are organized into performance objects, which are simply categories under which Performance Monitor counters are stored. From hereon, I will refer to individual counters in performance object/counter format. For example, Processor/% Processor Time refers to the % Processor Time counter found in the Processor performance object.
To detect a memory leak using Performance Monitor, monitor these counters:
1.The Memory/Available Bytes counter lets you view the total number of bytes of available memory. This value normally fluctuates, but if you have an application with the memory leak, it will decrease over time.
2.TheMemory/Committed Bytes counter will steadily rise if a memory leak is occurring, because as the number of available bytes of memory decreases, the number of committed bytes increases.
3.The Process/Private Bytes counter displays the number of bytes reserved exclusively for a specific process. If a memory leak is occurring, this value will tend to steadily rise.
4.The Process/Page File Bytes counter displays the size of the pagefile. Windows uses virtual memory (the pagefile) to supplement a machine's physical memory. As a machine's physical memory begins to fill up, pages of memory are moved to the pagefile. It is normal for the pagefile to be used even on machines with plenty of memory. But if the size of the pagefile steadily increases, that's a good sign a memory leak is occurring.
5.I also want to mention the Process/Handle Count counter. Applications use handles to identify resources that they must access. If a memory leak is occurring, an application will often create additional handles to identify memory resources. So a rise in the handle count might indicate a memory leak. However, not all memory leaks will result in a rise in the handle count.
Individual counters are organized into performance objects, which are simply categories under which Performance Monitor counters are stored. From hereon, I will refer to individual counters in performance object/counter format. For example, Processor/% Processor Time refers to the % Processor Time counter found in the Processor performance object.
To detect a memory leak using Performance Monitor, monitor these counters:
1.The Memory/Available Bytes counter lets you view the total number of bytes of available memory. This value normally fluctuates, but if you have an application with the memory leak, it will decrease over time.
2.TheMemory/Committed Bytes counter will steadily rise if a memory leak is occurring, because as the number of available bytes of memory decreases, the number of committed bytes increases.
3.The Process/Private Bytes counter displays the number of bytes reserved exclusively for a specific process. If a memory leak is occurring, this value will tend to steadily rise.
4.The Process/Page File Bytes counter displays the size of the pagefile. Windows uses virtual memory (the pagefile) to supplement a machine's physical memory. As a machine's physical memory begins to fill up, pages of memory are moved to the pagefile. It is normal for the pagefile to be used even on machines with plenty of memory. But if the size of the pagefile steadily increases, that's a good sign a memory leak is occurring.
5.I also want to mention the Process/Handle Count counter. Applications use handles to identify resources that they must access. If a memory leak is occurring, an application will often create additional handles to identify memory resources. So a rise in the handle count might indicate a memory leak. However, not all memory leaks will result in a rise in the handle count.
Tuesday, 10 August 2010
Monday, 9 August 2010
How to disable/enable remote login in windows server?
c:>change logon /disable
c:>change logon /enable
Note c:>change logon /disable, after putting this you are not able to login remotely but you can login locally or use psexec \\ server namecmd
c:>change logon /enable
Note c:>change logon /disable, after putting this you are not able to login remotely but you can login locally or use psexec \\ server name
How to change RDP port?
Go to registry & change the PortNumber(default : 3389)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp]
After changeing the registry reboot is required.
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp]
After changeing the registry reboot is required.
Friday, 6 August 2010
Diffrerce between Windows 2003 and 2008 Quorum Model
Windows 2008
1.Node Majority
2.Node and Disk Majority
3.Node and File Share Majority
4.No Majority: Disk Only
Windows 2003
1.Local quorum
2.Single quorum device
3.Majority node set
1.Node Majority
2.Node and Disk Majority
3.Node and File Share Majority
4.No Majority: Disk Only
Windows 2003
1.Local quorum
2.Single quorum device
3.Majority node set
For deep dive please see the below links.
http://blogs.msdn.com/b/clustering/archive/2010/05/14/10012930.aspx
http://blogs.msdn.com/b/clustering/archive/2010/06/15/10024985.aspx
Thursday, 5 August 2010
move cluster resource using the command line cluster.exe
cluster group "GROUPNAME" /move
Use it for two node cluster
cluster group "R1 Print" /moveto:test01
Use it for more than two node cluster.
Use it for two node cluster
cluster group "R1 Print" /moveto:test01
Use it for more than two node cluster.
Sunday, 1 August 2010
How to extend windows 2008 License?
Go to cmd and type
slmgr
slmgr /rearm
Reboot the server.
slmgr
slmgr /rearm
Reboot the server.
You can extend the license upto 1 year but it will not extend the Terminal server license.
Subscribe to:
Posts (Atom)