Archive for the Category »Windows 2003 «
INSTALL AND CONFIGURE STATISTICS FOR LOAD BALANCED IIS SITES-
Ingredients-
* In this scenario I’m going to use the following things-
# 3 NLB nodes – 2K31 (IP- 192.168.1.129), 2K32 (IP- 192.168.1.130), 2K33 (IP- 192.168.1.131)
# A server for stats installation – 2K34 (IP- 192.168.1.132)
# Statistics – AWStats (download from http://awstats.sourceforge.net). I used AWStats 6.8 version.
# Website for testing – www.a-r-u-n.com (must be setup in all the above 3 NLB nodes)
# Stats website in 2K34. I’m going to use server’s IP itself for testing.
Preparation-
1. Install AWStats 6.8 in the server 2K34 in the following location – C:\AWStats.
2. During installation it prompts you to specify the location of apache installation. Specify ‘none’ since this one is for IIS-
—–> Running OS detected: Windows
—–> Check for web server install
awstats_configure did not find your Apache web main runtime.
Please, enter full directory path of your Apache web server or ‘none’ to skip this step if you don’t have local web server or don’t have permission to change its setup.
Example: c:\Program files\apache group\apache
Apache Web server path (‘none’ to skip):
> none
3. Next step is it will ask to create a new config file for website, specify ‘y’-
—–> Need to create a new config file ?
Do you want me to build a new AWStats config/profile
file (required if first install) [y/N] ? y
4. It then asks you to specify the name of the website for config file. Specify the website name-
—–> Define config file name to create
What is the name of your web site or profile analysis ?
Example: www.mysite.com
Example: demo
Your web site, virtual server or profile name:
> a-r-u-n.com
5. Press Enter to complete the installation of AWStats.
6. Create the data directory called ‘Data’ under the following location C:\AWStats\ and assign modify permission to the following objects – Network Service, web user(IUSR).
7. Now open the config file ‘awstats.a-r-u-n.com.conf’ located under ‘cgi-bin’ folder (in my case – C:\AWStats\wwwroot\cgi-bin).
8. Search for ‘LogFile’ section. You need to specify the path where log files are created for the website.
Note – Since this configuration is for websites hosted in Load Balanced servers the format for ‘LogFile’ differs from the usual log format. There are two options available to generate logs for websites-
a. Copy all the log files from log folders of a-r-u-n.com from all the 3 nodes to the location in local server. In this case, I copied from \\2K31\C$\Domains\a-r-u-n.com\logs\W3SVC100\*.log to C:\Logs\a-r-u-n.com\2K31\*.log for 1st node. \\2K32\C$\Domains\a-r-u-n.com\logs\W3SVC190\*.log to C:\Logs\a-r-u-n.com\2K32\*.log for 2nd node. And \\2K33\C$\Domains\a-r-u-n.com\logs\W3SVC150\*.log to C:\Logs\a-r-u-n.com\2K33\*.log for 3rd node. Now all the 3 nodes’ log files for a-r-u-n.com have been copied to the location in local server – C:\Logs\a-r-u-n.com\ in 2K34. Now we need to merge all the above 3 nodes’ log files into one file using a perl tool called logresolvemerge.pl which ships with AWStats installation. This can be found in C:\AWStats\tools\logresolvemerge.pl. To merge all the log files to a single file, perform these steps-
1. Goto command prompt and to C:\AWStats\tools\ and type the following command –
perl logresolvemerge.pl C:\Logs\a-r-u-n.com\2K31\ex*.log C:\Logs\a-r-u-n.com\2K32\ex*.log C:\Logs\a-r-u-n.com\2K33\ex*.log > C:\Logs\a-r-u-n.com\all.log
2. Now you will see all the nodes’ log files have been merged to a single log file at C:\Logs\a-r-u-n.com\all.log
3. Now specify this log file path ‘C:\Logs\a-r-u-n.com\all.log’ under the ‘LogFile’ section in ‘awstats.a-r-u-n.com.conf’. This will looks like-
LogFile=”C:/Logs/a-r-u-n.com/all.log”
b. Second option is to specify UNC share path in config file. Note down the UNC share path of all the nodes for a-r-u-n.com (\\2k31\C$\Domains, \\2k32\C$\Domains and \\2k33\C$\Domains). Create a map networked drive for the above UNC shares. Say ‘G’ drive mapped to \\2k31\C$\Domains and ‘H’ drive mapped to \\2k32\C$\Domains and ‘I’ drive mapped to \\2k33\C$\Domains respectively. Now you can access those log files directly by G:\a-r-u-n.com\logs\W3SVC100\*.log for 2K31 server and H:\a-r-u-n.com\.. for 2K32 server and so on. Now open the config file ‘awstats.a-r-u-n.com.conf’ and look for ‘LogFile’ section. Specify the following-
LogFile=”perl C:/AWStats/tools/logresolvemerge.pl G:/a-r-u-n.com/logs/W3SVC100/ex*.log H:/a-r-u-n.com/logs/W3SVC190/ex*.log I:/arun1.com/log/W3SVC150/ex*.log |”
By specifying the above format in config file of a-r-u-n.com AWStats generates stats automatically during update the process. This is most suited in the environment where the log files are too large and you need to save space. Also this is time saver.
o Note – First option is time consuming and requires human intervention for exporting each and every logs. Where as second option is easier and can be specified only in config file and stats generation is automated during rebuild process.
9. Now you need to specify the log format for your website. Simply copy the format to config file from the top of the web log file(exmmddyy.log) if you not sure about the exact LogFormat of your web sites. (Note – Websites in each nodes must have same ‘Logging options’ enabled in IIS, this can be confirmed by right clicking web site properties > Logging Properties > in General and Advanced tab make sure that particular website in all the nodes have same settings)-
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2010-08-31 14:39:06
#Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken
Copy the fields so that it looks like this-
LogFormat= “date time s-sitename s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken”
10. Please specify DirData path in ‘DirData’ section as C:\AWStats\Data which you created in step 6 so that AWStats will store the result of stats analysis in AWStats files.
11. Now you need to update the stats in order to view it as GUI from web browser. To do this goto command prompt to the location – C:\AWStats\wwwroot\cgi-bin and key in the following command-
perl awstats.pl -config=www.a-r-u-n.com –update
You will see the result like this-
C:\AWStats\wwwroot\cgi-bin>perl awstats.pl -config=www.a-r-u-n.com -update
Create/Update database for config “./awstats.www.a-r-u-n.com.conf” by AWStats version 6.8 (build 1.910)
From data in log file “perl C:/AWStats/tools/logresolvemerge.pl G:/a-r-u-n.com/logs/W3SVC100/ex*.log H:/a-r-u-n.com/logs/W3SVC190/ex*.log I:/arun1.com/log/W3SVC150/ex*.log |”…
Phase 1 : First bypass old records, searching new record…
Searching new records from beginning of log file…
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)…
Jumped lines in file: 0
Parsed lines in file: 1560
Found 43 dropped records,
Found 0 corrupted records,
Found 197 old records,
Found 1320 new qualified records.
Make sure you see new qualified records at the end. If there’s any problem or error please verify you have followed previous steps correctly.
12. Stats have been generated for your website. Now we need URL to view the generated stats. Please create a website in IIS mapped to AWStats ‘cgi-bin’ directory (ie, C:\AWStats\wwwroot\cgi-bin).
13. Call the website from browser – http://192.168.1.132/awstats.pl?config=a-r-u-n.com
14. You are almost done. To generate stats automatically on daily or hourly basis you need to automate it by using Windows Scheduled Tasks. Create a batch file under cgi-bin folder of AWStats and specify the following command – perl awstats.pl -config=www.a-r-u-n.com –update
And finally create a scheduled task to schedule the batch file every 6 hrs or 12 hours.
15. Add sugar to taste… sorry add websites. 
…Configuring NLB for websites with dedicated ip addresses
# Assuming NLB is already setup and the nodes are converged fine.
Ingredients-
Following are the things I planned for my NLB (Network Load Balancing) setup in Windows Server 2003-
# 3 machines for web server(IIS installed) – Windows Server 2003
Machine names and its IP addresses-
2K31 - 192.168.1.129
2K32 - 192.168.1.130
2K33 - 192.168.1.131
# 1 machine for DNS server – Windows Server 2003
2K34 – 192.168.1.132
# Cluster IP addresses (for dedicated IP) – 192.168.1.150(for arun1.com), 192.168.1.151(for arun2.com)
# Website name that is going to use in dedicated IP configuration – arun1.com, arun2.com
# On each web servers create the folder structures as below-
C:\Domains
C:\Domains\arun1.com
C:\Domains\arun1.com\wwwroot
C:\Domains
C:\Domains\arun2.com
C:\Domains\arun2.com\wwwroot
Create a test page “index.html” under wwwroot and copy paste the below code-
<html>
<h1><center>WELCOME TO ARUN WORLD</center></h1>
<b/>
2K31 – arun1.com – dedicated
</html>
Change the domain name arun1.com and server name ‘Hosted in 2K31’ to appropriate domain name and server’s name on each sever as this will help a bit in the later stage during testing of each nodes as which node is servicing the request.
Note – It is not intention to have separate physical machines to configure NLB. You can either configure it in Virtual servers like – Microsoft Virtual PC, VMWare Workstation or VMWare Server. This saves cost. In this scenario I’ve setup servers in my friend’s laptop with this configs-
VMWare Workstation ACE Edition 6.02
1.73 Ghz Intel Dual Core
1 GB RAM
120 GB HD
Preparation-
In Network Load Balancing Manager-
1. Open ‘Cluster Properties’ of the cluster nlb.arun.com.
2. In ‘Cluster IP Address’ click ‘Add’ to add new dedicated IP. In this case I’ve added 192.168.1.150 and 192.168.1.151
3. You will be presented with a dialog box “Confirm Change of Cluster-wide
Properties”. Click ‘Yes’ to proceed further.
In IIS Manager-
Setup 2 sites arun1.com host header pointing to the ip 192.168.1.150 and arun2.com host header pointing to the ip 192.168.1.151.
In DNS Management console-
Create forward lookup zone for 2 domains – arun1.com(192.168.1.150) and arun2.com(192.168.1.151)-
Testing-
Now open the browser and type http://arun1.com and you will see something like this-
In the above pic, it is serviced by node 1 – 2K31.
To test whether this site is servicing through other nodes please suspend or stop the 2K31 node in Cluster Manager(Please refer this URL Setup Network Load Balancing in Windows Server 2003 see under ‘Testing’ section)
Happy Load Balancing! 
“`*“`arun …
Setup Network Load Balancing in Windows Server 2003
Generally you will need atleast 2 machines installed with Windows Server 2003 and each machine should have atleast 1 NIC and 1 static IP address. Additionally, you will need one more machine (either Windows Server 2003 or Windows XP) needed in order to test the setup. Assuming DNS server is included to add DNS records for websites.
Ingredients-
Following are the things I planned for my NLB (Network Load Balancing) setup in Windows Server 2003-
# 3 machines for web server(IIS installed) – Windows Server 2003
Machine names and its IP addresses-
2K31 - 192.168.1.129
2K32 - 192.168.1.130
2K33 - 192.168.1.131
# 1 machine for DNS server – Windows Server 2003
2K34 – 192.168.1.132
# Cluster IP address – 192.168.1.100
# Cluster Name – nlb.arun.com
# On each web servers create the folder structures as below-¦lt;br /> C:\Domains
C:\Domains\nlb.arun.com
C:\Domains\nlb.arun.com\wwwroot
¦lt;br /> Create a test page “index.html” under wwwroot and copy paste the below code-
<html>
<h1><center>WELCOME TO ARUN WORLD</center></h1>
<b/>
Hosted in 2K31
</html>
Change the server name ‘Hosted in 2K31’ to appropriate server’s name on each sever as this will help a bit in the later stage during testing of each nodes as which node is servicing the request.
Note – It is not intention to have separate physical machines to configure NLB. You can either configure it in Virtual servers like – Microsoft Virtual PC, VMWare Workstation or VMWare Server. This saves cost. In this scenario I’ve setup servers in my friend’s laptop with this configs-
VMWare Workstation ACE Edition 6.02
1.73 Ghz Intel Dual Core
1 GB RAM
120 GB HD
Preparation-
Setting up Network Load Balancer-
1. Open Network Load balancing Manager-
Start > Administrative Tools > Network Load balancing Manager
(or)
Start > Run > type ‘nlbmgr’
2. Right click Network Load Balancing Manager > New Cluster
3. In ‘Cluster Parameters’ wizard, in ‘Cluster IP Configuration’ specify the cluster IP address – 192.168.1.100, subnet mask and Full Internet Name as ‘nlb.arun.com’. Ensure ‘Multicast’ option is selected along with ‘IGMP Multicast’.
Leave the ‘Allow Remote Control’ unchecked.
Note – IP address is the virtual IP address for the cluster that will be used to address the cluster. If you have single adapter then you should select ‘Multicast’ in ‘Cluster Operation Mode’. By selecting ‘Unicast’ allows NLB to take over the network card it is bound to and doesn’t allow any additional network traffic through it. You can configure single adapter in ‘Unicast’ mode but after configuration the cluster manager will not be able to communicate with the server. Generally, ‘Multicast’ is slower than ‘Unicast’ mode.
4. On the next wizard ‘Cluster IP addresses’, leave the settings as it is and click next. (We will visit this in next topic).
5. In ‘Port Rules’ wizard, ensure the necessary ports are added. By default NLB configures to handle all ports. In this scenario I’m going to add these ports – 80 (http traffic) and 443 (https traffic). Add the ports by hitting ‘Add’ button and input 80 as From and To in Port range. Ensure ‘Both’ (ie, both TCP and UDP) protocol is selected.
One of the important thing here is ‘Filtering Mode’ which determines affinity of requests. Affinity describes how requests are routed to a specific server. ‘None’ refers any servers can service the incoming requests. ‘Single’ refers to a specific server has to handle each and every requests from a given IP. ‘None’ is recommended as it is better in stateless applications and this results in less overhead in NLB. ‘Single’ mode should be used when there’s a state server connection, for example – SSL.
Do the same thing for adding port 443.
6. Next step is to add nodes to the cluster. In the ‘Connect’ wizard specify the host name which needs to be included in NLB. In this case I specified 2K31 in ‘Host’ (or you can specify IP address of the host, for this server – 192.168.1.129) and click ‘Connect’ button and ensure interface name and IP info of that node are listed. If there’s more than one NIC card select the one that is going to be configured for NLB.
7. In ‘Host Parameters’ wizard specify the Priority. This should be unique number and it identifies each node in the cluster. Lower the number the higher the priority. Priority 1 is the master node which receives requests and routes the traffic to other nodes only when the load in this node is high. Hit ‘Finish’.
8. This will take 25 – 35 secs for a node to get converged. Following is the status of NLB cluster-
9. Follow the above steps (6th and 7th) to add remaining nodes-
2K32 - 192.168.1.130
2K33 - 192.168.1.131 Review the error log in the bottom pane if there is rror during additional node setup. Wait for few seconds and hit refresh until you see all the nodes becomes ‘Converged’ state.
One of the other ways to determine the status of each node in the cluster is – Goto command prompt in one of the nodes > type wlbs query
You will see something like this if all nodes are converged-
In this picture I tried in 2K33 (3rd node).
Setting up website to test NLB-
Setup website in node 1 – 2K31 – Setting up a website is easy process – Open IIS Manager from Administrative Tools and create a new website called nlb.arun.com as host header mapped to the ip address 192.168.1.100 (Cluster IP). Please setup the same site with same settings in all other nodes (2K32, 2K33).
Setting up DNS records-
This should be carried out in DNS server 2K34 which is not a part of cluster and just acts as DNS server. In order to get a website working you need DNS record configured for that website. To do this you need to create DNS record for arun.com as shown in this picture. Create host record (A) for nlb.arun.com pointing to the cluster IP – 192.168.1.100-
Testing-
Now open the browser and type http://nlb.arun.com and you will see something like this-
In the above pic, it is serviced by node 1 – 2K31To test whether this site is servicing through other nodes please suspend or stop the 2K31 node in Cluster Manager.
Access the site http://nlb.arun.com again after suspending node 1.
Now you will see the request is serviced by 2K32 (node 2). This confirms request is routed to another node when the first node is unreachable. Now resume/start the node which you stopped in previous stage.
Happy Load Balancing!
“`*“`arun …
If you receive this error when accessing Kayako SupportSuite-
Parse error: syntax error, unexpected ‘{‘ in support\includes\SmartyLight\class.template.php on line 351
Please make sure ‘short_open_tag‘ is set to ‘On‘ in php.ini this will fix the problem.
…Advantages of Windows 2003
1. Domains can be renamed or moved to a different level in an AD tree.
2. Schema attributes can be deleted as well as added.
3. Any Domain Controller can cache the Global Catalog thus preventing user logon problems if no Global Catalog server is available.
4. AD Replication can be set not to use compression.
5. Cross-Forest Transitive Trusts can be created.
6. Many administrative tools allow drag-and-drop and there are more configuration and management wizards.
7. Most services are disabled by default in 2003 instead of enabled as in Windows 2000.2003
allows partial synchronizations of the Global Catalog 2000 had always to have full synchronizations.
8. Support for IPv6. Ping and Tracert have extra IPv6 options.
9. Supports XML web services.
10. A new service called Volume Shadow Copy takes periodic snapshots of a hard drive making it easier to take backups and recover deleted files. Users can even be allowed to recover previous versions of files by themselves by using the Previous Versions client.
11. A Global Catalog server can be built from backup media instead of by replication.
12. IPSec Nat Traversal – NAT-T – allows IPSec VPN clients and servers to pass through NAT firewalls. This is likely to lead to the wider adoption of L2TP VPNs.
13. Distributed File System DFS has had significant improvements made to it. For example DFS replicas can now be prestaged to avoid excessive initial file replication.
14. Multiple DFS Roots per server can be created (Enterprise and Datacenter editions only).
15. Print queue redundancy can be achieved by storing them on multiple servers.
16. Active Directory Migration Tool v.2.0 can now migrate users, computers, groups and passwords from an NT domain and can also perform the cross-forest migration of objects.
17. Terminal Server allows clients to map their local drives and printers
18. The FTP server allows different default directories to be assigned to different users.
19. There’s a Security Configuration and Analysis tool to check a server’s security settingsDNS AD-integrated zones are stored in the Application Partition of a forest so aren’t replicated to domain controllers which aren’t DNS servers.
20. Regedit.exe and Regedt32.exe have been amalgamated into a single utility which takes the best features of each. Both files still exist but run the same utility.
21. The DNS server has added flexibility with the new options of stub zones and conditional forwarding.
22. Internet Information Server 6 (IIS 6) has the ability to keep worker processes from different websites and web applications separate so that if one application crashes then other websites running on the same server remain unaffected.
…IIS SMTP not available in IIS Snap-in-
Please make sure IIS SMTP is installed in the server. If you find it’s installed but not visible in IIS Snap-in can be fixed by registering the dll using this code-
regsvr32 C:\Windows\System32\inetsrv\smtpsnap.dll
or
regsrv32 %systemroot%\system32\inetsrv\smtpsnap.dll
Once done IIS SMTP virtual server node will be listed in IIS Snap-in.
…To enable Full trust mode for ASP.NET sites please follow these steps-
Locate web.config file at C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG
or
%systemroot%\Microsoft.NET\Framework\v2.0.50727\CONFIG
Add the following entries at the top of the page before the entry ‘<location allowOverride=”false”>’ (Without quotes)-
<location path=”your website name here” allowOverride=”true”>
<system.web>
<trust level=”Full” originUrl=”.*”/>
</system.web>
</location>
Finally restart IIS.
***Note: Please take a copy of web.config before making the above changes***
Problem description-
Server Error in ‘/virtual directory name’ Application.
Error in File UNKNOWN.RPT:
The request could not be submitted for background processing.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Error in File UNKNOWN.RPT: The request could not be submitted for background processing.
Solution-
This is most likely a permission error in C drive. To fix this please follow these steps-
Open My Computer > Right click ‘C’ drive then properties > Security tab > Click Advanced > in ‘Permissions tab’ click ‘Add’ > Add ‘Network Service’ > in the ‘Apply onto’ drop down list make sure ‘This folder only’ is selected and no other should be selected > Make ‘Read Attributes’ and ‘Read Permissions’ are checked > Click Ok > Also make sure ‘Replace permission entries on all child objects’ is NOT checked.
***Note: If you incorrectly set to anything other than ‘This folder only’ in ‘Apply onto’ dropdown list will result in severe permission issues and all of your sites will prompt for authentication so handle withe extra care.***
To change Terminal Service/RDP port please follow these steps-
*****You are about to make changes in server’s registry so any incorrect changes will result in severe problem*****
1. Open registry editor by running this command in run – regedit
2. Locate for HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
3. Locate the ‘PortNumber’ subkey and find the value of d3d (in hexadecimal), change the ‘Base’ radio button to ‘Decimal’ and modify the port no. from 3389 to new one.
Note: If your server is behind hardware/software firewall please make sure to add this port in allow list so that you can establish connection from outside.
To prevent synattack in Windows server 2003 please follow this-
Save the following in synattackprotect.reg and double click it to merge-
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
“EnableTCPChimney”=dword:00000000
“SynAttackProtect”=dword:00000002
“TcpMaxHalfOpen”=dword:00000064
“TcpMaxHalfOpenRetried”=dword:00000050
“TcpMaxPortsExhausted”=dword:00000005
“TcpMaxConnectResponseRetransmissions”=dword:00000003
To fix the application popup-
Warning : Unknown(): Unable to load dynamic library ‘C:\Program Files\SWsoft\Plesk\Additional\Php\extensions\php_curl.dll’ – The specified module could not be found
Make sure libeay32.dll and ssleay32.dll exist in the Windows system32 folder. These 2 files can be found in a folder called dll in the PHP folder.
To enable HTTP compression and Conditional GET please follow these steps-
1. You need to open Metabase.xml from the location – C:\Windows\System32\inetsrv
******Please take much care in handling this since you are doing this in Metabase file. Any incorrect actions can lead to severe problems. Do it at your own risk******
**Before doing this please make sure your IIS Metabase is directly editable without stopping IIS. If this option is not enabled you can enable it in IIS > properties of server name > under ‘Internet Information Services’ tab > check ‘Enable Direct Metabase Edit’ check box > hit Ok. Otherwise you will have to stop IIS then open Metabase.xml to proceed further. Either things will work according to your convenience**
And look for the following parameters-
<IIsCompressionScheme Location =”/LM/W3SVC/Filters/Compression/deflate”
HcCompressionDll=”%windir%\system32\inetsrv\gzip.dll”
HcCreateFlags=”0″
HcDoDynamicCompression=”TRUE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”FALSE”
HcDynamicCompressionLevel=”0″
HcFileExtensions=”htm
html
txt”
HcOnDemandCompLevel=”10″
HcPriority=”1″
HcScriptFileExtensions=”asp
dll
exe”
>
</IIsCompressionScheme>
<IIsCompressionScheme Location =”/LM/W3SVC/Filters/Compression/gzip”
HcCompressionDll=”%windir%\system32\inetsrv\gzip.dll”
HcCreateFlags=”1″
HcDoDynamicCompression=”TRUE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”TRUE”
HcDynamicCompressionLevel=”0″
HcFileExtensions=”htm
html
txt”
HcOnDemandCompLevel=”10″
HcPriority=”1″
HcScriptFileExtensions=”asp
dll
exe”
>
</IIsCompressionScheme>
<IIsCompressionSchemes Location =”/LM/W3SVC/Filters/Compression/Parameters”
HcCacheControlHeader=”max-age=86400″
HcCompressionBufferSize=”8192″
HcCompressionDirectory=”%windir%\IIS Temporary Compressed Files”
HcDoDiskSpaceLimiting=”FALSE”
HcDoDynamicCompression=”FALSE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”FALSE”
HcExpiresHeader=”Wed, 01 Jan 1997 12:00:00 GMT”
HcFilesDeletedPerDiskFree=”256″
HcIoBufferSize=”8192″
HcMaxDiskSpaceUsage=”100000000″
HcMaxQueueLength=”1000″
HcMinFileSizeForComp=”1″
HcNoCompressionForHttp10=”TRUE”
HcNoCompressionForProxies=”TRUE”
HcNoCompressionForRange=”FALSE”
HcSendCacheHeaders=”FALSE”
>
</IIsCompressionSchemes>
Change the above to the following-
<IIsCompressionScheme Location =”/LM/W3SVC/Filters/Compression/deflate”
HcCompressionDll=”%windir%\system32\inetsrv\gzip.dll”
HcCreateFlags=”0″
HcDoDynamicCompression=”TRUE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”TRUE”
HcDynamicCompressionLevel=”10″
HcFileExtensions=”htm
xml
css
rdf
js
html
txt”
HcOnDemandCompLevel=”10″
HcPriority=”1″
HcScriptFileExtensions=”asp
php
cgi
dll
aspx
asmx
exe”
>
</IIsCompressionScheme>
<IIsCompressionScheme Location =”/LM/W3SVC/Filters/Compression/gzip”
HcCompressionDll=”%windir%\system32\inetsrv\gzip.dll”
HcCreateFlags=”1″
HcDoDynamicCompression=”TRUE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”TRUE”
HcDynamicCompressionLevel=”10″
HcFileExtensions=”htm
html
xml
css
rdf
js
txt”
HcOnDemandCompLevel=”10″
HcPriority=”1″
HcScriptFileExtensions=”asp
php
cgi
aspx
asmx
dll
exe”
>
</IIsCompressionScheme>
<IIsCompressionSchemes Location =”/LM/W3SVC/Filters/Compression/Parameters”
HcCacheControlHeader=”max-age=86400″
HcCompressionBufferSize=”8192″
HcCompressionDirectory=”%windir%\IIS Temporary Compressed Files”
HcDoDiskSpaceLimiting=”TRUE”
HcDoDynamicCompression=”FALSE”
HcDoOnDemandCompression=”TRUE”
HcDoStaticCompression=”FALSE”
HcExpiresHeader=”Wed, 01 Jan 1997 12:00:00 GMT”
HcFilesDeletedPerDiskFree=”256″
HcIoBufferSize=”8192″
HcMaxDiskSpaceUsage=”100000000″
HcMaxQueueLength=”1000″
HcMinFileSizeForComp=”1″
HcNoCompressionForHttp10=”FALSE”
HcNoCompressionForProxies=”FALSE”
HcNoCompressionForRange=”FALSE”
HcSendCacheHeaders=”FALSE”
>
</IIsCompressionSchemes>
Once the changes are done please save the metabase file.
2. Now goto command prompt and to the following location and type-
C:\Inetpub\AdminScripts>
adsutil set w3svc/filters/compression/parameters/HcDoSta
ticCompression false
HcDoStaticCompression : (BOOLEAN) False
C:\Inetpub\AdminScripts>adsutil set w3svc/filters/compression/parameters/HcDoDyn
amicCompression false
HcDoDynamicCompression : (BOOLEAN) False
C:\Inetpub\AdminScripts>adsutil set w3svc/1234/root/DoStaticCompression true
DoStaticCompression : (BOOLEAN) True
C:\Inetpub\AdminScripts>adsutil set w3svc/1234/root/DoDynamicCompression true
DoDynamicCompression : (BOOLEAN) True
Note: The value ’1234′ is website’s identifier. You can note this in IIS Manager > locate the website > note the identifier or you can find it in site’s logfile folder name for ex- w3svc1234
3. Finally restart IIS.
Microsoft has released the Windows Server 2003 ‘Server Performance Advisor’ tool designed to help troubleshoot Windows 2003 performance problems. Neither Windows XP nor Windows 2000 platforms support this tool. The tool is available here: http://www.microsoft.com/downloads/details.aspx?familyid=61a41d78-e4aa-47b9-901b-cf85da075a73&displaylang=en
Once downloaded please run the msi file and follow the instructions and these steps-
1. Click Next to go to the “Welcome to the Server Performance Advisor Setup Wizard” introduction screen.
2. Click “I accept” on the license page, then click Next.
3. Accept the default installation location and select whether the tool will be used by just the person installing the tool or by all administrators, as the figure shows. Click Next.
4. The wizard prompts you for a location for the temporary storage of performance log files. Accept the default C:\perflogs\data location and click Next.
5. The wizard prompts you for a reports folder location. Again, accept the default location (C:\perfLogs) and click Next. Click Next to begin the installation. When the installation is finished, click Finish.
7. You’ll now have a new Start menu item, Server Performance Advisor, which you can use to start the advisor process.
Recent Comments