command-Line Parameters for Defrag.exe in Windows 2008

Switch	Description
/A	Perform analysis on the specified volumes.
/C	Perform the operation on all volumes.
/E	Perform the operation on all volumes except those specified.
/H	Run the operation at normal priority (default is low).
/M	Run the operation on each volume in parallel in the background.
/T	Track an operation already in progress on the specified volume.
/U	Print the progress of the operation on the screen.
/V	Print verbose output containing the fragmentation statistics.
/X	Perform free space consolidation on the specified volumes.

/R	Performs partial defragmentation (default). Attempts to consolidate only fragments smaller than 64 megabytes (MB).
/W	Performs full defragmentation. Attempts to consolidate all file fragments, regardless of their size.
/F	Forces defragmentation of the volume when free space is low.

Defrag Files Large Than 64 MB

/W	Performs full defragmentation. Attempts to consolidate all file fragments, regardless of their size. in 2008 this switch has been deprecated Undocumented switch : B Use B instead of /W

Defragment all your drives at once

Would you like to just defragment all of your drives without getting extra info or doing a more complicated defrag?  If so, just enter defrag /C and let defrag take over.  Or, hey, you could just do this from the main defrag window since it works the exact same.

Other Nice Options

Get more info about the defrag:	/V
Consolidate free space on a drive:	/X
Defrag at normal process priority:	/H
Track a defrag already in progress:	/T
Defrag all drives except the one listed:	/E
Defrag all drives at the same time:	/M – note, this is only advisable if you have multiple drives, and will not work good on a computer with multiple partitions

You can put the options you need together, too.  Say you want to defrag all of your devices in verbose mode to see more info, and you also want the defrag to run at top priority.  To do this, we’ll enter:

defrag /C /H /V

The RDP Protocol Component X.224 Detected an Error in the Protocol Stream and has Disconnected the Client

I encountered this error one day when trying to login to a terminal server and got nothing but a black screen with a cursor. Rebooting the server would fix the problem for a short while. When investigating the event logs I found the following errors:

Event ID 56: The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: xxx.xxx.xxx.xxx.
Event ID 50: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.

Disabling TCP Offload on the server fixed the issue:

1. Open an administrative command prompt and run the following commands:
   netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
2. Next, open regedit and navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableTCPA and set the value to 0. If the key does not exist, right-click on Parameters, select new DWORD Value, and enter EnableTCPA in the text box.

Time server Configuration - windows 2008 server

>>>>>>>>>>> Take a full backup of registry before modifying the values  <<<<<<<<<<<<<<<<


Steps to be followed to execute the CR :

1.Point the Primary domain controller to internal time server by executing the below commands

     1.w32tm /config /update /manualpeerlist: "hostname1, hostname2" /syncfromflags:MANUAL

     2.w32tm /config /reliable:yes

2. Resync the time source

     w32tm /resync /rediscover

3. Restart the time services on the server HOSTNAME

      1.Net Stop w32time
      2. Net Start w32time

4. Modify registry configuration

     1.Click Start, click Run, type regedit, and then click OK. 

     2.Locate and then click the following registry sub key  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters


     



In the right pane, right-click Ntpserver, and then click Modify  Edit string and paste the text    >>>>>    hostname1  hostname2




Space should be there between hostname1 and hostname2

Processor Affinity on Servers with Multiple CPUs

Given that multi-core / multi-processor systems are the way of the future, this might seem like an odd post for us to be writing.  However, we have run into a few instances where 32-bit applications run with no issues on single processor systems, but fail to run, or perform poorly on multiprocessor systems.  I know that seems counterintuitive, but if an application is not multi-processor aware you may experience issues.  In cases such as these, there are a couple of different approaches you might try:
Method 1:  Setting processor affinity via Task Manager
If the application is already running, then you can use the “Set Affinity” feature within Task Manager on Windows XP and later operating systems.  To use this feature, highlight the process within Task Manager, right-click and select the “Set Affinity” option as shown below:

You are then presented with the option to select your processor affinity:

Remember that this option is only available on Windows XP and later operating systems.
Method 2: Use IMAGECFG.EXE to permanently set the processor affinity for the executable (Windows 2000 Systems)
Using this method you can permanently bind an executable to a processor.  IMAGECFG.EXE was available on the Windows 2000 Server Resource Kit (Supplement One).  To set the processor affinity, use the following syntax from a Command Prompt:  imagecfg –a 0xn <full path to the executable>.  In our sample syntax, 0xn is the processor affinity mask.  This mask is what restricts the application to a specific CPU.  To determine the correct mask, use the table below:

CPU Number	Mask
0	0x1
1	0x2
2	0x3
3	0x4

You can use this syntax to set the affinity all the way up from processors 0 through 31.  Remember that this would be the preferred method on a Windows 2000 system, where you cannot dynamically change the processor affinity via Task Manager.
Method 3: Use PsExec to set the Processor Affinity for an executable on Windows XP and later OS versions
In Method 1 we used Task Manager to set the processor affinity for an application that had already been launched.  But, what happens if you need to launch the application with a specific processor affinity?  You could certainly use Method 2, but you might have to hunt around for a copy of IMAGECFG.EXE.  Instead you can use PsExec to pre-set your processor affinity.  We normally use PsExec to execute programs on remote systems, but we can also use it to set processor affinity.  The syntax is as follows:  PsExec.exe –a 0 <path to executable>.  The –a switch sets the affinity of the process – in this case to Processor 0.  This isn't a permanent method of setting the affinity, although you could create a .cmd or .bat file that launched the executable using these parameters.
Method 4: Use the /AFFINITY switch (Windows Server 2003 and later)
You can also use the START command with the /AFFINITY switch to start the program with whichever processor affinity you wish to set.  This is not a persistent method (unlike Method 2) – you would need to use the command each time, or launch the program via a batch file or a similar mechanism.  The syntax for this command is as follows: START /AFFINITY <processor number> <program>.  The processor number is defined by the same mask we used above in Method 2.
To verify that your process is started with the proper processor affinity, launch Task Manager once the process has launched.  Right click on the process name and click on “Set Affinity” – the processor number that you set should be the one that is checked.  Here’s an example from my Windows Server 2008 system – using Notepad as my test application I want to constrain Notepad to CPU 0.

Notepad launches successfully – now let’s check Task Manager:

And as we can see, Notepad was launched and is constrained to CPU 0.


Source : http://blogs.technet.com/b/askperf/archive/2009/02/03/help-my-application-only-runs-on-a-single-processor-system.aspx