Greeting from my side friends,

Method-:1

1. Use the Registry Editor (Regedit.exe) and navigate to the following branch: HKEY_LOCAL_MACHINE \ Software \ Policies \ Microsoft \ Internet Explorer \ Main

Note: The above branch does not exist by default, and have to be created manually or by running the REG file available at the end of this article.

2. Create a REG_DWORD value named DisableFirstRunCustomize

3. Double-click DisableFirstRunCustomize and set its value data to 1.

4. Exit the Registry Editor.

Note-: To automate the steps, copy the given line and copy them into a txt file. And change its extenton to .reg and run this. You have done all the steps given by a single click.

Windows Registry Editor Version 5.00 ;

Disable IE8 Tour for all users

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Main] “DisableFirstRunCustomize”=dword:00000001

To Undo all changes-:  copy the given line and copy them into a txt file. And change its extenton to .reg and run this

Windows Registry Editor Version 5.00

;Enable IE8 Tour for all users

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]

“IE8RunOnceLastShown”=-

“IE8RunOncePerInstallCompleted”=-

“IE8RunOnceCompletionTime”=-

“IE8TourShown”=-

“IE8TourShownTime”=-

“IE8RunOnceLastShown_TIMESTAMP”=-

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main]

“DisableFirstRunCustomize”=-

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Main]

“DisableFirstRunCustomize”=-

Method-:2

 1. Launch the Group Policy Editor (gpedit.msc).

2. Expand the following branch: Computer Configuration | Administrative Templates | Windows Components | Internet Explorer

3. Computer Configuration | Administrative Templates | Windows Components | Internet Explorer

 4. Double-click Prevent performance of First Run Customize Settings.

5. Enable this.

6. Choose the option to go to the home page directly.

Thanks,

Manish Mishra

Create a batch file to execute when a worker process is orphaned

1. Start Notepad
2. Paste the following code into Notepad.

3.  @if “%_echo%”==”" echo off

4.  setlocal

5.      set TIMESTAMP=%DATE:~-9%_%TIME%

6.  set TIMESTAMP=%TIMESTAMP:/=_%

7.  set TIMESTAMP=%TIMESTAMP::=_%

8.  set TIMESTAMP=%TIMESTAMP:.=_%

9.  set TIMESTAMP=%TIMESTAMP: =_%

10.set FILENAME=c:\crash_PID_%1_%TIMESTAMP%.dmp

11.set LOG=c:\log.txt

12.set COMMAND=c:\debuggers\cdb.exe -c “.dump /o /ma %FILENAME%;q” -p %1

13.

14.echo %COMMAND% > %LOG%

15.%COMMAND%

16.

endlocal

17. Save the file as FileName.cmd. For this example, we will name the file Action.cmd. However, you may name the file as you want.

Note You may have to modify the location of the debuggers and the location where you want the resulting dump file to be generated.

Back to the top

Configure the Orphan Worker Process settings

1. At the command prompt, type the following command, and then press ENTER:

cd \Inetpub\adminscripts

2. To enable the Orphan Worker Process feature, type the following command at the command prompt:

3.  adsutil.vbs SET W3SVC/AppPools/DefaultAppPool/OrphanWorkerProcess TRUE

4. At the command prompt, set the executable to run when a process is scheduled to be recycled. For example, in this case use the batch file that was created in the “Create a Batch File to Execute When a Worker Process Is Orphaned” section:

adsutil.vbs SET W3SVC/AppPools/DefaultAppPool/OrphanActionExe “c:\action.cmd”

adsutil.vbs SET W3SVC/AppPools/DefaultAppPool/OrphanActionParams “%1%”

Note Make sure that the OrphanActionExe option points to the location of the batch file that was created in the “Create a Batch File to Execute When a Worker Process Is Orphaned” section. Also make sure that the identity of the W3wp.exe process has Read and Execute permissions to this file.

Note If you enable IIS to debug worker processes that are reported as unhealthy, make sure that you monitor these released worker processes. IIS does not automatically remove these worker processes from memory. If you do not correctly handle these worker processes, many failed worker processes may be running on your computer. These worker processes can tie up resources that are needed by other processes. You must end these worker processes quickly to free those resources. In some conditions, these worker processes may block metabase access. This causes problems with other worker processes or with the World Wide Web service itself.

Thanks

MK

Here are the steps for AD isolation mode. It is not meant for local users account and only for Active directory users. Please follow the steps carefully since AD isolation mode issues can be a bit tricky to resolve

Here below add the domain admin account and make sure you click on Browse to select the user account and not just manually type it.. I have a reason for asking that.

Create Virtual directories for each of the domain accounts that will be used for accessing the FTP site. Be sure to name the virtual directory identical to the
username of the user who will be logging in. For instance, the user account of User1 will need a virtual directory named User1. Please remember that it is not a must to have a separate virtual directory for all the users under the root FTP site. Based on the commands mentioned below, users will be automatically taken to their respective folders and they need not have a Virtual directory created under the FTP site.

Then, Run the IISFTP.vbs script as below:

In a command prompt, navigate to C:\windows\system32 and run the VBScript iisftp.vbs twice (with different arguments shown below) for each user that will need access to the FTP site. This will do the necessary changes to the user account in AD’s LDAP database.

[Words underlined are your variables]

For user1:

C:\windows\system32> Cscript iisftp.vbs /setadprop domainuser1 ftproot C:\ftproot\adroot

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

The value of ftproot for user domainuser1 has been set to C:\ftproot\adroot

C:\windows\system32> Cscript iisftp.vbs /setadprop domainuser1 ftpdir  folder1

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

The value of ftpdir for user domainuser1 has been set to folder1

[Remember in the above command for ftpdir you need to set the folder name for the user account and not the complete path i.e. although the user's directory is set to C:\ftproot\adroot\folder1, you should mention "folder1" in the command as mentioned above and not the complete path].

ftproot specifies the complete path for the parent folder (root) and ftpdir specifies the name of the user’s folder. Here if you had a remote UNC share for the FTP contents you can change the command to, Cscript iisftp.vbs /setadprop domainuser1 ftproot \\ftpserver\ftproot\adroot

Similarly for user2:

C:\windows\system32> Cscript iisftp.vbs /setadprop domainuser2 ftproot C:\ftproot\adroot    <— [It can be a different location other than the ftproot for user1]

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

The value of ftproot for user domainuser2 has been set to C:\ftproot\adroot

C:\windows\system32> Cscript iisftp.vbs /setadprop domainuser2 ftpdir folder2

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

The value of ftpdir for user domainuser2 has been set to folder2

Now before you try accessing the site using account domain\username ensure that you have the necessary folder hierarchy in place as set up in the above commands, i.e. if you do not have an existing path C:\ftproot\adroot\folder1 you will get the following error message:

User Saurabh1\domainuser1 cannot log in, home directory inaccessible.

Login failed.

Also in an AD isolation mode you won’t see the option to allow anonymous connections. Check the difference between an AD isolated site and a non-AD isolated site. Notice the number of tabs in each.

If you already have an FTP site and you don’t know the isolation mode for it you can open the metabase.xml file from C:\windows\system32\inetsrv and search for the tag UserIsolationMode and check its value.

FTP site having mode as:

• Do not isolate users (this is same as the only mode available in IIS 5.0) ———> will have UserIsolationMode set to 0
• Isolate users (this is applicable for local as well as domain users)   ———–> will have UserIsolationMode set to 1
• Isolate users using Active Directory (also called Active directory user isolation mode, applicable only for Active directory users)  —–> will have UserIsolationMode set to 2.

Checklist:

When you try to visit an AD isolated FTP site from a command prompt, you may receive the following error message:

530 User <Domain>\<UserName> cannot log in, home directory inaccessible.
Login failed.

This problem can occur because of any one of the following reasons:

• The msIIS-FTPDir or msIIS-FTPRoot properties for the User Account that is trying to access the FTP site are not configured in the Active Directory.
  Make sure that msIIS-FTPDir and msIIS-FTPRoot properties for the user account are configured properly. To do this, open up a command prompt on the IIS server and browse to C:\Windows\system32 folder. Run the following commands:

C:\WINDOWS\system32>cscript iisftp.vbs /GetADProp username FTPRoot
C:\WINDOWS\system32>cscript iisftp.vbs /GetADProp username FTPDir

If you get a valid FTPDir and FTPRoot returned as a result of this command, which means these properties are set correctly. The actual path of the user’s folder will be\. If the result of either of the commands is something like

The value of FTPDir for user is:
null

This means that the FTPDir and FTPRoot are not set correctly. You can set them as mentioned some way above.

• The account that is set in the IIS Metabase as the ADConnectionsUserName key for the FTP site is having some issues.

It may have been locked out or is not having enough permissions to query the Active Directory. The password for account connecting to AD in ADConnectionsPassword may be incorrect.

Make sure that the password is correct and that the account is not locked out. Also ensure that the account that is configured here has enough permissions to query the Active Directory.

To check the username and password set in the metabase, run the following commands:

C:\Inetpub\AdminScripts> Cscript adsutil.vbs get msftpsvc//ADConnectionsUserName

C:\Inetpub\AdminScripts> Cscript adsutil.vbs get msftpsvc//ADConnectionsPassword

[You may find the password in encrypted format like ************. In such a case you need to modify the adsutil.vbs file to get the exact password. Open Adsutil.vbs in notepad from the above location and search for the function "IsSecureProperty(ObjectParameter,MachineName)".

In this function IsSecureProperty(ObjectParameter,MachineName), you will find the following code:

Function IsSecureProperty(ObjectParameter,MachineName)

On Error Resume Next
Dim PropObj,Attribute
Set PropObj = GetObject(“IIS://” & MachineName & “/schema/” & ObjectParameter)
If (Err.Number <> 0) Then
ReportError ()
WScript.Echo “Error trying to get the property: ” & err.number
WScript.Quit (Err.Number)
End If
Attribute = PropObj.Secure
If (Attribute = True) Then
IsSecureProperty = True              <——–
Else
IsSecureProperty = False
End If
End Function

In the highlighted line above, change the value to False, save and now rerun the adsutil.vbs command and you should see the actual passwo}

Please refere link given below.

http://technet.microsoft.com/en-us/library/cc782944%28WS.10%29.aspx

FTP AD Isolation Setting in in  IIS7 server-:

On w2003 IIS6 server you can use the iisftp.vbs script to set and get ftp AD properties FTPRoot (DS_msIIS_FTPRoot) and FTPDir (DS_msIIS_FTPDir) from a command line.

On w2008 IIS7 I can’t find this script.

There is a utility made by rakkimk: FTPADPropSetting, you can find it at http://blogs.msdn.com/rakkimk/archive/2008/06/04/iis7-command-line-tool-managed-to-set-ftp-properties-in-active-directory.aspx

Rakkimk has also a GUI for this (at http://blogs.msdn.com/rakkimk/archive/2007/11/28/iis7-ui-module-for-setting-ftp-active-directory-user-isolation-properties.aspx ) but I did not succeed in getting this work.

I could install the iisftp.vbs script:

copy from a w2003 IIS6 server from c:\windows\system32\dllcache

the files iisftp.vbs, iisschlp.wsc and cmdlib.wsc

to your w2008 iis7 ftp7 server

you need to register both *.wsc files

do this by this command:

regsvr32 /i:”cmdlib.wsc ” %SystemRoot%\system32\scrobj.dll        (if commands not runs then pls copy cmdlib.wsc to c:\windows\system32)

and

regsvr32 /i:”IIsScHlp.wsc ” %SystemRoot%\system32\scrobj.dll     ( if this command does not run due to regsrc32 error pls user this command “C:\Windows\SysWOW64\regsvr32.exe cmdlib.wsc”)

Thanks

Manish Kumar

In order for me to get more details on the actual issue, the site needs to be set in development mode. To do this you need to find the file ss_environment.php in the parent directory of the web root. change the first line of this config to say ‘dev’ rather than ‘live’.

After you have done this, you should try re-building the site’s database. Do this by appending /dev/build/?flush=all to the end of the beta site’s URL.

You should get a page similar to screenshot-1.png (attached).

Once this has happened, then try re-visiting the homepage. If you still get an error please screen shot it and then send that over. I will have a look.

Once you have done all this, please ensure that you set ss_environment.php config back to ‘live’, this is VERY important.

HKLM\Software\Policies\Microsoft\Windows\Installer\disableMSI

The value on the workstations is set to 2.

 This value is not present on my servers. When I change the value on the workstations from 2 to 0 I am then able to install whatever I like.

 I have added the desableMSI key to a server and made the value 0 but I am still unable to install anything.

Regards,

MK

when you finish the ‘Clone Virtual Machine’ wizard and try to power on the new VM.

It might not start! I received this error: “Thin/TBZ disks cannot be opened in multiwriter mode”, and the new VM would not start.

After a bit of searching and fiddling around.

Right-click the VM and click ‘Edit Settings’ to bring up the Virtual Machine Properties dialog. Now change the SCSI Controller’s ‘SCSI Bus Sharing’ policy from ‘Virtual’ to ‘None’.

Now try to power on your virtual machine.  It will work fine.

OR

IF you want to enable Multiwriter mode, Please follow the given steps.

Example-:

login as: root
root@192.168.10.93′s password:
Access denied
root@192.168.10.93′s password:
Last login: Fri Jun 24 12:40:03 2011 from abilochi.nivians.net
[root@ESX06 ~]# ls
ks.cfg  old_cores
[root@ESX06 ~]# cd /v
var/      vmfs/     vmimages/ vmware/
[root@ESX06 ~]# cd /vm
vmfs/     vmimages/ vmware/
[root@ESX06 ~]# cd /vmfs/
[root@ESX06 vmfs]# ls
devices  volumes
[root@ESX06 vmfs]# cd volumes/
[root@ESX06 volumes]# ls
4e007bf3-4d7df0f4-f367-00145e57edb0  datastore1
4e034ee1-44fe69e3-3678-0015172e90ec  Datastore2
[root@ESX06 volumes]# cd datastore1/
[root@ESX06 datastore1]# ls
CLUSNODE1-STAGING                                   iso
clusnode1-staging-176                               labman
clusnode2-staging-144                               VLabMan
clusstorage                                         vmlab.iso
EN_WINDOWS_SERVER_2003_R2_ENTERPRISE_DISC1_VLP.iso  W2k8clone
EN_WINDOWS_SERVER_2003_R2_ENTERPRISE_DISC2_VLP.iso  Windows 2008
esxconsole-4e007a5a-9e42-df6d-a2cc-00145e57edb0
[root@ESX06 datastore1]# cd clusnode2-staging-144/
[root@ESX06 clusnode2-staging-144]# ls
clusnode2-staging-144-flat.vmdk  clusnode2-staging-144.vmxf  vmware-6.log
clusnode2-staging-144.nvram      vmware-2.log                vmware-7.log
clusnode2-staging-144.vmdk       vmware-3.log                vmware.log
clusnode2-staging-144.vmsd       vmware-4.log
clusnode2-staging-144.vmx        vmware-5.log
[root@ESX06 clusnode2-staging-144]# ls -a
.                                clusnode2-staging-144.vmsd  vmware-4.log
..                               clusnode2-staging-144.vmx   vmware-5.log
clusnode2-staging-144-flat.vmdk  clusnode2-staging-144.vmxf  vmware-6.log
clusnode2-staging-144.nvram      vmware-2.log                vmware-7.log
clusnode2-staging-144.vmdk       vmware-3.log                vmware.log
[root@ESX06 clusnode2-staging-144]#
[root@ESX06 clusnode2-staging-144]# vmkfstools –eagerzero clusnode2-staging-144.vm
clusnode2-staging-144.vmdk  clusnode2-staging-144.vmx
clusnode2-staging-144.vmsd  clusnode2-staging-144.vmxf
[root@ESX06 clusnode2-staging-144]# vmkfstools –eagerzero clusnode2-staging-144.vmdk
Eagerly zeroing: 100% done.

Regards

MK

When I was trying to import the the privet key it was un-exportable at the time of its configuration.

The tab to export is also blured and I was not able to go ahead with that as indicated on “TechNET” of  Microsoft.

If the Privet key is exportable then you can export it from here-:

Run—mmc—ad remove snap ins—select CERTIFICATE—computer account—local computer—-OK—OK—Certificate (local computer)—-personal—-Certificate—-right click to the desired certificate and export it.

NOTE-: If the privet key will be exportable then the option to export privet key will be highlighted.

Suppose the privet key is not exportable then there is a utility Name or we can say a tool which will give you to export the privet from the local system even if the key is not exportable.

you must have to follow this link  to to get the utility downloaded (jailbreak.exe).

http://www.passion4it.nl/index.php?option=com_fireboard&Itemid=2&func=view&catid=10&id=15

This will provided the your exactly the same Management console to export the Privet but the only difference will be this,

You will be enabled to to export the privet key.

Some time the utility might be consider as a virus on your system by your esteemed anti virus program because it tries to fetch the information from the place where, no any external service is allowed.

For this remedy we only requir to disable our anti virus for the time being to do the activity and after that we can re-enable that anti virus.

That`s it all around,

Thanking you friends,

Regards,

Manish Kumar

Step 1

connect your laptop to the WIFI provider.

Step 2

Run the internet connection wizard

Step 3

At the internet connections options, choose the third option that says “make a home network or connect to a small office network.

Step 4

click next next next bla bla bla until you reach a window that shows your current WIFI connection do not forget to click or check the box that says “ignore the disabled network equipment”

Step 5

From the next window, choose the first option. This option configures your Laptop as a server thereby allowing internet connection sharing. click next next next bla bla bla until you are prompted to restart your computer. When your computer is restarting, you will receive a message that a gateway will be created for this connection, answer “YES” and that is all.

Step 6

As for the second computer, connect it to the Laptop by a twisted pair cable (RJ-45+CAT5 cable). Step 7 Switch on the computer and repeat Step 1 to Step 4. In Step 5, choose the second option.

this configures the second computer as a client to the Laptop.

Step 8

click next next next bla bla bla until you are prompted to restart your computer. As soon as the restart is done, you second computer should browse the internet without any clicking. Enjoy !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Note: This is a generic WIMP server that’s capable of running WordPress, PHPbb, and other popular PHP and MySQL powered web sites. You might have to change a few things to get your WIMP server running just right depending on your usage.

The Limitations
Before you go too far you need to know that IIS7 running on Windows Vista is full featured with a few limitations.

Before you right this type of server off because it’s limited you need to realize if you ever reach one of the limitations you’ll have so much traffic you could probably buy an actual server with one day’s pay from the web site.

The Limitations

Request Execution Limit: IIS7 running on Windows Vista Basic, Starter, Home, and Home Premium have a Request Execution Limit of 3. Vista Ultimate is limited to 10. Request Execution Limit is how many simultaneous pages the web server can give out at one time. That means Vista Basic, Starter, and Home editions can serve up to 259,200 pages per day and Ultimate can serve up to 864,000 pages per day!
FTP: FTP is very limited. You can only download files as anonymous. No uploading via FTP to your web server. If this is a problem, check out the FileZilla FTP Server.
Install IIS7
First thing first, we need to install a web server.

Open the Control Panel in classic view.
Double-click Programs and Features.
Click Turn Windows features on or off on the left.
Check off Internet Information Services.
Expand Internet Information Services, World Wide Web Services, Application Development Features, and then check off ISAPI Extensions. ISAPI will be needed later when we install PHP.

Click OK to install IIS7.
When the Windows Features box disappears IIS7 is installed and should be running. Test IIS7 by going to http://localhost in your web browser. You should see an IIS7 test page like the screenshot below.

The root of the default web site is located at C:\inetpub\wwwroot. Your web site goes there.

Install PHP
Now that we have a web server we need support for PHP. In this example I’m installing PHP 5.2.4.

Create a folder called php in the root of the C: drive.
Download the Windows Binaries Zip package from http://www.php.net/downloads.php.
Extract the files and save them in the php folder you just created.
Copy C:\php\php.ini-dist and save it on your desktop so we can work with it.
Rename php.ini-dist you just copied on your desktop to php.ini.
Right-click php.ini and select Edit.
Search for extension=php_mysql.dll and uncomment it by deleting the ; in front of it. This allows php to login a MySQL database.
Now move up in the php.ini code and look for extension_dir = “./”. Change “./” to “C:\php\ext”. This shows php where to load the extension=php_mysql.dll extension you just uncommented.
Save php.ini.
Copy php.ini and save it in C:\Windows.
Open the IIS Manager by typing IIS Manager in the Start Menu’s search box and click Internet Information Services (IIS) Manager in the search results.
Double-click Handler Mappings.
Click Add Script Map located on the right.
Fill out the Add Script Map window like the screen shot below.

Click OK to save the changes.
Click Yes in the window that asks you if you want to enable this ISAPI extension.
Click the back button in the IIS Manager and then double-click Default Document.
Type index.php, with a space behind , in the File names list.
Click Apply on the top right of IIS Manager.
Now you need to copy libmysql.dll from C:\php and save it in C:\WINDOWS\System32. Thanks for the fix Oruba.
Lets test to make sure php is installed and running correctly.

Open notepad.
Type in the blank document.
Note: Remove the space between < ? in . I had to add the space so the command doesn’t execute on this page.

Save it as test.php on your desktop and then move it to C:\inetpub\wwwroot.

Note: A common mistake when saving test.php is to save it as test.php.txt. Don’t forget to select All files under Save as type and then name the file test.php in notepad.

Go to http://localhost/test.php. You should get a php information page similar to the screen shot below.

Install MySQL
Before we can install MySQL we need to disable UAC in Windows Vista.

Open the Control Panel in classic view.
Click User Accounts.
Click Turn User Account Control on or off.
Uncheck Use User Account Control and then click OK.
Restart your computer.
Note: You can turn UAC back on after everything has been installed and working.

Now we can install MySQL. In this example I’m going to install MySQL Community Edition 5.0.45.

Download the Windows ZIP/setup.exe version http://dev.mysql.com/downloads/mysql/5.0.html#win32.
Unzip it and save setup.exe on your desktop.
Run Setup.exe.
The welcome window will popup. Click Next.

Since this is a general guide on creating a WIMP server leave Typical selected and click Next.

Let MySQL install in its default directory by simply clicking Install in this window.

Click Next to move through a few advertisements.
Leave Configure the MySQL Server now checked and click Finished.

Note: It seems some versions other than 5.0.45 of MySQL silently errors out during installation. I’m not sure if this is a bug or not but Dustin has provided a great fix in the comments.

Click Next at the welcome window.

I’m assuming that you don’t need to configure any advanced MySQL settings. If you did you probably wouldn’t need this guide or you should leave this job to an expert. Select Standard Configuration and then click Next.

Leave Install As Windows Service, the service name MySQL, and Launch MySQL Automatically checked and click Next.

Type the MySQL administrator (root) password twice and then click Next.

This part is VERY important. Hold your mouth just right, cross your fingers and click Execute to configure MySQL. If you did it just right you should get 4 check marks when it’s done.

Note: If you get a Connection Error, click Retry and it should work. This is caused by a slower computer not starting the MySQL service fast enough.

Click Finished.
Now that you have MySQL installed and running lets install the GUI Tools to make managing databases easy.

Download the GUI Tools (Windows x86) at http://dev.mysql.com/downloads/gui-tools/5.0.html.
Install it just like any other software.
Click Start, All Programs, MySQL, MySQL Administrator.
Fill in the fields just like the screen shot below.

Remember: Root’s password is the one you set when you installed MySQL.

Once MySQL Administrator is open, you can create a new database by clicking Catalogs and then right-clicking under test and select Create Schema.

Give it a name and there you go!
Open Port 80
Now that you have a working WIMP lets open it up to the world. All internet (HTTP) traffic passes through port 80. Let’s open port 80 to the world.

Search for firewall in the search box in the Start Menu and click Windows Firewall in the search results.
Click the Exceptions tab in the Windows Firewall Settings window.

Click the Add port button.
Type HTTP as the name and 80 as the port number.

Adjust Vista for Web Server Performance
Because Windows Vista is not meant to be a server out of the box its priorities are backwards when it’s being used as a web server. Windows Vista prioritizes programs like Word before background services like IIS7 to give the end user the best experience possible. Since we’re configuring Windows Vista as a web server background services need to be Vistas priority instead of programs.

Let’s set Windows Vista’s services as a higher priority than programs to squeeze the most speed out of it as we can.

Right-click Computer in the Start Menu and then select Properties.
Click Advanced system settings.
Click Settings under Performance in the Advanced tab of the System Properties window.
Click the Advanced tab in the Performance Options window.
Select Background services.
Click OK and then restart your computer.
Hardware

Troubleshoot..if you are configuring PHP using silver strip(flush and rebuild database cashe).

This error is a generic IIS error produced so that potential users don’t get detailed information on the sites architecture.

In order for me to get more details on the actual issue, the site needs to be set in development mode. To do this you need to find the file ss_environment.php in the parent directory of the web root. change the first line of this config to say ‘dev’ rather than ‘live’.

After you have done this, you should try re-building the site’s database. Do this by appending /dev/build/?flush=all to the end of the beta site’s URL.

You should get a page similar to screenshot-1.png (attached).

Once this has happened, then try re-visiting the homepage. If you still get an error please screen shot it and then send that over. I will have a look.

Once you have done all this, please ensure that you set ss_environment.php config back to ‘live’, this is VERY important.

I personaly faced this issue in one of my domain controller. This is highily in satiable for all techies.

I searched a lot on internet for the ramedy bu all was in vain. No one came with me to help me out to overcome this really critical issue.

After strugling a lot, I decided my self to take it as a challange to me and solve the problem without formating the server.

The approach to find out the excat problem started from basic concept of networking OSI model.

In my research it was confirmed that the problem was due to virus attack on the server. NIC driver uninstall and installetion does not solve the issues.

Here are the steps to solve the problem simply….

1. Scan your system with all available updated anti virus and please insure there is no any virus remaining in the system at all.

2. Uninstall all softwars, that is not required for long.

3. Uninstall all antivirus programs from the computer along with unnecessary tools and patches provided by internt FREE.

4. Download “CCleaner” (A software availabel on net for free) to clean your systems temp files crom all locations and registry as well.

5. Restart the system and uninstall CCleaner as well.

6. Again shutdown the system and repair the Operating syste.

Problem will definetly be resolve. If you need some more clarification, please revert on this post.

Thansk

Manish Kumar