Enabling Disk Cleanup Utility in Windows Server 2012

"Disk Cleanup Utility"

Step No. #1 Open The Roles and Features Wizard

To open the roes and feauture wizard. Lauch the "server manager" by pressing the Windows key


and clicking on the server manage please see Screenshot as shown. 

Step No. #2 Click on Add role and Feature

Click on add role and feture to launch the add role and feature wizard.

Step No. #3  Choose  installation Type

Choose rolebase or feature based installation  to install to local machine.

Step No. #4  Click Next all the way to features

Click "next" all the way to features.  Locate "User Interface and Infrastructure".  Click on "Desktop Experience"


and install additional required feature.

Step No. #5  Proceed with the installation and Reboot

Make it sure that you reboot the system

Step No. #6  Verify that the Utility is indeed installed

Ready to run diskcleanup. See screen shot below.

Disk Cleanup in Action

Below is a sample snapshot of disk cleanup in action.

Changing a Username and Email Address

Problem

This was asked on Experts Exchange this morning, and so I thought I'd get it documented. There are loads of reasons why you might want to change a username, display name, and email address. It can be spelt wrong, a user has got married/divorced and changed their surname, or they have simply changed their name.

There are also some clients who don't create a new user when a member of staff leaves. They just want to rename the old user and change the email address. The advantage of this approach is that all the group membership, and permissions will be correct for the replacement member of staff.

Solution

Step 1 Change the Username, Logon Name and Display Name.

1. On the Exchange server > Start > Run > dsa.msc {enter} > Locate the user in question > Right click and rename.

Note: You can do this on any Domain Controller but for Step 2 we will need to be on an Exchange server, or a machine with the Exchange Management tools installed.

2. As soon as you press {enter} > The rename user dialog will open, and you can change the display name, and the user logon name > OK.

Step 2 - Exchange 2000 / 2003 (Including SBS 2000 / 2003) Change the Email address.

Note: For newer versions of Exchange see below.

1. Whilst still in active Directory Users and Computers > Right click the affected user > Properties.

2. E-mail Addresses tab > Add > SMTP Address.

3. Type in the new email address > OK.

4. Untick the "Automatically update email..." option > Select the NEW email address >Set As Primary > Apply > OK.

Note: It can take a while for your global address list to update, then your Outlook clients need to get the updated list, sometimes this can take a couple of days! Be patient, the changes have been made.

Step 2 - Exchange 2007 / 2010 (Including SBS 2008 / 2011) Change the Email address.

1. On your Exchange 2007/2010 Server Launch the Exchange Management Console > Recipient Configuration > Mailbox > Locate the user > Properties. 

2. E-mail Addresses tab > Add > Type in the new address > OK.

3. Untick the "Automatically update email..." option > Select the NEW email address > Set As Primary > Apply > OK.

Note: It can take a while for your global address list to update, then your Outlook clients need to get the updated list, sometimes this can take a couple of days! Be patient, the changes have been made.

.lnk File association issues/ all programs open in Notepad/Word

The other day I got a call from a  user who had somehow managed to make all his desktop shortcuts open in Word. I suspected he had used the “open With” option in the context menu; thus, telling Windows to “Always use this program to open these files”. The problem was clear. Even though each shortcut had the correct settings, Windows would still open them in Word. The problem is, you can’t just tell Windows to open the shortcut files in an other program than Word. You have to somehow Reset the shortcut behavior to factory settings.

So how did we fix it ?

Doing some initial Googling (that’s a word now I believe) I came up with two solutions, where the first was to delete all .lnk references in the registry HKEY_CLASSES_ROOT and then import these from a different computer. Luckily I then found a much safer (and quicker) method, that actually works.

1. Open Regedit
2. Open Key folder:
   HKEY_CURRENT_USER | SOFTWARE | MICROSOFT | WINDOWS | CURRENT VERSION |EXPLORER | FILEXTS |.LNK
3. Locate a sub folder named: User Choice
4. Delete it
5. Close RegEdit
6. Reboot

Now all your shortcuts should be back to normal

How do I use Previous Versions /Shadow Copies?

How do I use Previous Versions?

This topic includes the following information:

What is the Previous Versions feature?

You can use Previous Versions to enable your users to access previous versions of their files and folders on your network. To enable access to previous versions of files, you must enable Shadow Copies of Shared Folders on the file server. Shadow copies are copies of files that are located on the server and appear as previous versions.

Once you enable Previous Versions, your users access this feature using the folder Properties dialog box. Available versions appear on the Previous Versions tab under Folder versions.

This feature is useful because users can:

• Recover files that were accidentally deleted. If you accidentally delete a file, you can open a previous version and copy it to a safe location.
• Recover from accidentally overwriting a file. If you accidentally overwrite a file, you can recover a previous version of the file. (The number of versions depends on how many snapshots you have created.)
• Compare versions of a file while working. You can use previous versions when you want to check what has changed between two versions of a file.

Important

This feature is not a replacement for creating regular backups. Use a backup utility, such as Windows Server Backup in Windows Server 2008 or Windows Server 2008 R2, in coordination with Shadow Copies of Shared Folders and Previous Versions as your strategy for data protection.

Previous versions are read-only. You cannot make changes to a previous version of the file as it exists on the server. In addition, previous versions are periodically deleted and can disappear at any time. If you think you might want a previous version of a file, you should copy it to another folder so that it is not deleted.

How do I enable and configure Shadow Copies of Shared Folders to make Previous Versions available?

Shadow Copies of Shared Folders is a feature included in the Shared Folders Microsoft Management Console (MMC) snap-in. If you enable Shadow Copies of Shared Folders on a volume using the default values, a task will be scheduled to create shadow copies at 7:00 A.M.. The default storage area will be on the same volume, and its size will be 10 percent of the available space.

You can only enable Shadow Copies of Shared Folders on a per-volume basis—that is, you cannot select specific shared folders and files on a volume to be copied or not copied. Also, you should not use this feature to create shadow copies of files needed for the operating system to run properly.

To enable and configure Shadow Copies of Shared Folders

1. Click Start, click Administrative Tools, and then click Computer Management.
2. In the console tree, right-click Shared Folders, click All Tasks, and click Configure Shadow Copies.
3. In Select a volume, click the volume that you want to enable Shadow Copies of Shared Folders for, and then click Enable.
4. You will see an alert that Windows will create a shadow copy now with the current settings and that the settings might not be appropriate for servers with high I/O loads. Click Yes if you want to continue or No if you want to select a different volume or settings.
5. To make changes to the default schedule and storage area, click Settings.

How do I restore a previous version of a file or folder?

Once you enable Shadow Copies of Shared Folders and start creating shadow copies, you can use the Previous Version feature to recover previous versions of files and folders, or files and folders that have been renamed or were deleted.

To restore a previous version of a file or folder

1. Locate the file or folder that you want to restore, right-click the file or older, and click Properties. The Properties dialog box will appear.
2. Click the Previous Versions tab, click the version of the file that you want to restore, and then click Restore. A warning message about restoring a previous version will appear. Click Restore to complete the procedure.
3. Restoring a previous version will delete the current version. If you choose to restore a previous version of a folder, the folder will be restored to its state at the date and time of the version you selected. You will lose any changes that you have made to files in the folder since that time. Instead, if you do not want to delete the current version of a file or folder, click Copy to copy the previous version to a different location.

Additional considerations

• If the Previous Versions tab does not appear in the Properties dialog box, Shadow Copies of Shared Folders might not be enabled on the shared resource. Shadow copies are copies of files that are located on the server and appear as previous versions.
• If there are no previous versions listed, the file has not changed since the oldest copy was created—Previous Versions shows only the unique versions of the file.
• When you restore a previous version of a folder, files in the current folder that were not contained in the previous version of the folder will not be deleted.
• When you restore a file, the file permissions will not be changed—permissions will remain the same as they were before the restore operation. When you copy a previous version of a file, the permissions will be set to the default permissions for the directory (or folder) where the copy of the file is placed.
• Restoring a large directory (or folder) puts a heavy load on the file server and can result in previous versions being deleted. Try to restore individual files instead of entire directories whenever possible.
• Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings.

Analyzing a server 2008 R2 dwp crash dump file

Yesterday the four node file cluster resource crashed and blue screened and was moved to another node. I wanted to analyze the crash dump file (C:\Windows\Minidump\070711-36473-01.dmp) so I copied it to my W7 workstation and tried to open it but Visual Studio could not help me out here.
Reading a crash dump file is far from intuitive and I spent a great deal of the morning learning about debugging. So here is what I did to read the dump file.
First, you need to install the debugging tools from here. Choose the version that corresponds to your architecture. This install will take a long time depending on your network speed. Important is that you include the WinDbg.exe because that is the tool we will be using.
Next, you need to download the symbol files. Note that you can also use the symbol server from Microsoft but it is faster to have a copy of the symbol files on your hard drive. Download them here. Just download them all. And this will also take a long time because the Symbol files are huge.
Next! Open C:\Program Files\Debugging Tools for Windows (x86)\WinDb.exe.
Choose File -> Open -> Symbol File Path
Type: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols like this:

Now press CTRL+D to open the DWP file! Very exciting.

Now, if you enter !analyze -v like this:
And you’ll get more information about the crash. In my case:

8: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* USER_MODE_HEALTH_MONITOR (9e) One or more critical user mode components failed to satisfy a health check. Hardware mechanisms such as watchdog timers can detect that basic kernel services are not executing. However, resource starvation issues, including memory leaks, lock contention, and scheduling priority misconfiguration, may block critical user mode components without blocking DPCs or draining the nonpaged pool. Kernel components can extend watchdog timer functionality to user mode by periodically monitoring critical applications. This bugcheck indicates that a user mode health check failed in a manner such that graceful shutdown is unlikely to succeed. It restores critical services by rebooting and/or allowing application failover to other servers. Arguments: Arg1: fffffa8038f3ab30, Process that failed to satisfy a health check within the  configured timeout Arg2: 00000000000004b0, Health monitoring timeout (seconds) Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ PROCESS_OBJECT: fffffa8038f3ab30 CUSTOMER_CRASH_COUNT:  1 DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR:  0x9E PROCESS_NAME:  System CURRENT_IRQL:  2 LAST_CONTROL_TRANSFER:  from fffff880030b76a5 to fffff80001a98d00 STACK_TEXT: fffff880`0253d518 fffff880`030b76a5 : 00000000`0000009e fffffa80`38f3ab30 00000000`000004b0 00000000`00000000 : nt!KeBugCheckEx fffff880`0253d520 fffff800`01aa4652 : fffff880`0253d600 00000000`00000000 00000000`40800088 00000000`00000001 : netft!NetftWatchdogTimerDpc+0xb9 fffff880`0253d570 fffff800`01aa44f6 : fffff880`030c4100 00000000`03023940 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff880`0253d5e0 fffff800`01aa43de : 00000729`6e09a2ce fffff880`0253dc58 00000000`03023940 fffff880`02517d88 : nt!KiProcessExpiredTimerList+0xc6 fffff880`0253dc30 fffff800`01aa41c7 : 000001c5`99d9f3c1 000001c5`03023940 000001c5`99d9f3fd 00000000`00000040 : nt!KiTimerExpiration+0x1be fffff880`0253dcd0 fffff800`01a90a2a : fffff880`02515180 fffff880`025202c0 00000000`00000000 fffff880`01368420 : nt!KiRetireDpcList+0x277 fffff880`0253dd80 00000000`00000000 : fffff880`0253e000 fffff880`02538000 fffff880`0253dd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND:  kb FOLLOWUP_IP: netft!NetftWatchdogTimerDpc+b9 fffff880`030b76a5 cc              int     3 SYMBOL_STACK_INDEX:  1 SYMBOL_NAME:  netft!NetftWatchdogTimerDpc+b9 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: netft IMAGE_NAME:  netft.sys DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc48a FAILURE_BUCKET_ID:  X64_0x9E_netft!NetftWatchdogTimerDpc+b9 BUCKET_ID:  X64_0x9E_netft!NetftWatchdogTimerDpc+b9 Followup: MachineOwner ---------

Explanation: USER_MODE_HEALTH_MONITOR (9e) is the bug check code I need to investigate. For a complete list of bugcheck codes look here: http://msdn.microsoft.com/en-us/library/ff542347%28v=VS.85%29.aspx
And now all that is left for me to say is: ‘happy debugging’.
Oh here are some helpful links: http://blogs.technet.com/b/askcore/archive/2009/06/12/why-is-my-2008-failover-clustering-node-blue-screening-with-a-stop-0x0000009e.aspx

http://blogs.msdn.com/b/ntdebugging/archive/tags/hangs/

Windows Server 2012 features

Opinion Microsoft's Windows Server 2012 is out. For many systems administrators, the question about this latest iteration of Microsoft's server family is not "What's new?" but "Why care?"
Server 2008 R2 is a great operating system, while Server 2012 bears the stigma of Metro and the Windows 8 controversy. But the answer to "why care" is simple: Server 2012 is as big a leap over 2008 R2 as 2008 R2 was over 2003.


Server 2012 comes with some great new features. It also refines previous versions of Server to bring it past the "never use version 1.0" stage and up to parity, in features and stability, with competing offerings.
In short Windows Server 2012 kicks ass. Here are the top 10 reasons why.

10. IIS 8

IIS 8 brings Internet Information Services up to feature parity with the rest of the world, and surpasses it in places. More than a decade's worth of "you use Windows as your web server" jokes officially end here.
IIS 8 sports script precompilation, granular process throttling, SNI support and centralised certificate management. Add in a FTP server that finally, mercifully, doesn't suck (it even has functional login restrictions) and IIS 8 becomes worth the cost of the operating system on its own.

9. PowerShell

PowerShell 3.0 is an evolution rather than a revolution. Having more PowerShell scriptlets is not normally something I would care about. That said, the 2012 line of products marks a revolution in Microsoft's approach to server management.
Every element of the operating system and virtually every other companion server, such as SQL, Exchange or Lync, are completely manageable through PowerShell. This is so ingrained that the GUIs are just buttons that call PowerShell scripts underneath.
PowerShell should be tops on this list but to make proper use of it, your Google-fu has to be strong. The official documentation is incomplete, Bing is still worthless for searching Microsoft's web estate and the golden examples for making use of PowerShell lie in the blogs maintained by Microsoft's staff.
Once you have assembled the list of scriptlets you need – printed, laminated and guarded by a fire elemental as in days of old – you can make the 2012 stack of Microsoft software sing. Thanks to PowerShell, Microsoft is ready to take on all comers at any scale.

8. DirectAccess

DirectAccess was a neat idea but it was poorly implemented in previous versions of Windows. Server 2012 makes it easier to use, with SSL as the default configuration and IPSec as an option. The rigid dependence on IPv6 has also been removed.
DirectAccess has evolved into a reasonable, reliable and easy-to-use replacement for virtual private networks.

7. Cluster Shared Volumes

With Server 2012 Cluster Shared Volumes are officially supported for use beyond hosting virtual hard disks for Hyper-V. You may now roll your own highly available multi-node replicated storage cluster and do so with a proper fistful of best-practice documentation.

6. Deduplication

For years now, storage demand has been growing faster than hard drive density. Meeting our voracious appetite for data storage has meant more and more spindles, and more controllers, chassis, power supplies, electricity and cooling to keep those spindles spinning.
Deduplication has moved from nice to have to absolute must in recent years and Microsoft has taken notice. Server 2012 supports deduplication on NTFS volumes – though tragically it does not work with CSV – and deeply integrates it with BranchCache to save on WAN bandwidth.

5. Hyper-V 3.0

Server 2012 sees Hyper-V catch up with VMware's mainstream. While objectively I would have to say that VMware retains the feature lead at the top end, when combined with System Center 2012, Hyper-V 3.0 will cheerfully handle two-sigma worth of use cases.
Microsoft is no longer an also-ran in the virtualisation space; it is a capable and voracious predator stalking the wilds of the data centre for new prey.
Microsoft's Hyper-V Server – a free Windows Core version of Hyper-V – is feature complete. If you have a yen to dive into PowerShell then you can run a complete 64-node, 8,000 virtual machine Hyper-V cluster without paying Microsoft a dime.
It takes a very special kind of masochist to do so – Microsoft is betting you will spend the money on System Center 2012 and it is probably right. System Center 2012 is amazing, even more so with the newly launched Service Pack 1.
Microsoft's focus on PowerShell and its decision to put price pressure on VMware with Hyper-V server has opened up a market for third-party management tools such as 5Nine. These are not nearly as capable as System Center, but offer a great mid-point between free and impossible to manage and awesome but too expensive. This emerging ecosystem should see Hyper-V's market share explode.

4. Hyper-V Replica

Hyper-V Replica is a storage technology designed to continuously replicate your virtual machines across to a backup cluster. It ensures that snapshots no more than 15 minutes old of your critical virtual machines are available over any network link, including the internet.
It replicates the initial snapshot in full – after that it sends only change blocks – and it fully supports versioning of your virtual machines.

3. iSCSI

With Windows Storage Server 2008, Microsoft first made an iSCSI target available. It eventually became an optional download from Microsoft's website for Server 2008 R2 and is now finally integrated into Server 2012 as a core component.

2. NFS 4.1

Microsoft's NFS 4.1 server is good code. Designed from the ground up it is is fast, stable and reliable. It makes a great storage system for heterogenous environments and a wonderful network storage point for VMware servers.

1. SMB 3.0

SMB 3.0 is the crown jewel of Server 2012. It is far removed from its laughingstock predecessor CIFS. It supports multiple simultaneous network interfaces – including the ability to hot-plug new interfaces on the fly to increase bandwidth for large or complex transfers – and supports MPIO, thin provisioning of volumes and deduplication (assuming the underlying storage is NTFS).
SMB 3.0 also supports SMB Direct and remote direct memory access, the ability for appropriately kitted systems to move SMB data directly from one system's memory to the other, bypassing the SMB stack. This has enabled Microsoft to hit 16GBps transfer rates for SMB 3.0, a weighty gauntlet for any potential challenger to raise.
I have found Server 2012 to be worth the cost of the upgrade, even where I have the excellent Server 2008 R2 deployed. Given that I work with very limited IT budgets, that is a strong endorsement.
If you have also taken the plunge, please share your take in the comments below

IIS -Internet Information Service Server Restart in 2008 Server

You might need to restart Internet Information Services (IIS) before certain configuration changes take effect or when applications become unavailable. Restarting IIS is the same as first stopping IIS, and then starting it again, except it is accomplished with a single command. There are two ways to restart IIS:

• Using IIS Manager.
• Using the IISReset command-line utility.

Both methods allow you to stop, start, and restart IIS Internet services. The Restart IIS command in IIS Manager and the IISReset command-line utility do not restart the HTTP protocol stack (HTTP.sys) or Internet services outside of IIS. In previous versions of IIS, restarting IIS using the IISReset command-line utility was a common practice for recovering from an unresponsive application.

Restarting or stopping IIS, or rebooting your Web server, is a severe action. When you restart the Internet service, all sessions connected to your Web server (including Internet, FTP, SMTP, and NNTP) are dropped. Any data held in Web applications is lost. All Internet sites are unavailable until Internet services are restarted. For this reason, you should avoid restarting, stopping, or rebooting your server if at all possible. IIS 6.0 includes application pool recycling and several other features that provide alternatives to restarting IIS. For a list of features designed to improve IIS reliability and remedy the need to restart IIS, see "Alternatives to Restarting IIS" in this topic.

Note

Changes to the metabase can be lost when restarting IIS. To avoid losing metabase changes and to trigger history files that back up the metabase, use the SaveData method. For more information about the SaveData method, see "SaveData" in the Platform SDK on MSDN.

With IIS 6.0, the World Wide Web Publishing Service (WWW service) lives in the service host, Svchost.exe. The FTP, NNTP, and SMTP services and the IIS metabase, known as the IIS Admin service, lives in Inetinfo.exe. If the IIS Admin service terminates abnormally, IIS restarts automatically. This feature is known as Automatic Restart. Previously, in IIS 5.0, if the IIS Admin service terminated abnormally, both the WWW service and IIS Admin service had to be restarted because they shared the same application space. In IIS 6.0, if the IIS Admin service terminates abnormally, the WWW service does not go down because the IIS Admin service and the WWW service run in separate process spaces. In this case, the WWW service acknowledges that the metabase has terminated abnormally and checks to see if the IISReset command-line utility is configured on the IIS Admin service. If IISReset is configured on the IIS Admin service, IIS waits for the IIS Admin service to start again and reconnects the WWW service.

All of the Internet services listed below, if installed, are affected when you restart IIS. Not all of the services listed below are installed by default.

Service	Description
IIS Admin service	This service manages all the services of IIS other than the WWW service (FTP, NMTP, and SMTP).
WWW service	This service provides Web connectivity between clients and Web sites.
HTTP SSL service	This service provides secure Web connectivity between clients and Web sites.
FTP service	This service provides FTP connectivity and administration through IIS Manager.
SMTP service	This service transports electronic mail across the network.
NNTP service	This service transports network news across the network.

Important

You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log on to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type runas /User:Administrative_AccountName "mmc %systemroot%\system32\inetsrv\iis.msc".

Procedures

To restart IIS using IIS Manager

1. In IIS Manager, right click the local computer, point to All Tasks, then click Restart IIS.
2. In the What do you want IIS to do list, click Restart Internet Services on computername.
3. IIS attempts to stop all services before restarting. IIS waits up to five minutes for all services to stop. If the services cannot be stopped within five minutes, all IIS services are terminated, and IIS restarts. In addition, clicking End now forces all IIS services to stop immediately, and IIS is restarted.

Caution

If IIS is terminated before its services have stopped normally, data loss can result. If possible, back up your IIS configuration before restarting IIS. See Backing Up and Restoring the Metabase for information about backing up your IIS configuration.

Important

You must be a member of the Administrators group on the local computer to run scripts and executables. As a security best practice, log on to your computer by using an account that is not in the Administrators group, and then use the runas command to run your script or executable as an administrator. At a command prompt, type runas /profile /User:MyComputer\Administrator cmd to open a command window with administrator rights and then type cscript.exe ScriptName (include the script's full path and any parameters).

To restart IIS using the IISReset command-line utility

1. From the Start menu, click Run.
2. In the Open box, type cmd, and click OK.
3. At the command prompt, type iisreset /noforce computername, and press ENTER.

Note

The /noforce parameter is recommended as a safeguard against data loss in case the IIS services cannot all be stopped within the one minute timeout period. If you are certain that it is safe to force IIS to restart, you can omit the /noforce parameter. In addition, if you are logged on locally, the computername parameter is not required. If you are administering an IIS server remotely, the computername parameter is the NetBIOS name of the computer on which you wish to restart IIS.

4. IIS attempts to stop all services before restarting. The IISReset command-line utility waits up to one minute for all services to stop. If the services cannot be stopped within one minute, all IIS services are terminated, and IIS restarts.

Note

You can adjust the timeout value using the iisreset /timeout command.

The IISReset command-line utility has several options available. For more information about the options available with the IISReset command-line utility, open a command-prompt window, and type iisreset /? You can also search for "iisreset" in Windows Help.

Automatic Restart

Automatic Restart is enabled by default for the IIS Admin service and WWW service. If a process within either service terminates abnormally, the service restarts automatically. The WWW service restarts using the net start command. The IIS Admin service restarts using the iisreset command. These commands are issued internally without user intervention. You can disable Automatic Restart using the following procedures.

To disable restart of IIS Admin service

1. From the Start menu, right-click My Computer, and click Manage.
2. In the console tree, expand the Services and Applications node, and click Services.
3. Right-click IIS Admin Service, and click Properties.
4. Click the Recovery tab, and in the First failure, Second failure, and Subsequent failures list boxes, click Take No Action.
5. Click OK.

The following command can only be issued on the local machine.

To disable restart of IIS Admin service from the command line

1. From the Start menu, click Run.
2. In the Open box, type cmd, and click OK.
3. At a command prompt, type iisreset /disable, and press ENTER. This command disables IIS and prevents all iisreset calls from executing.

Note

To re-enable the IIS Admin service, at the command prompt, type iisreset /enable, and press ENTER.

To disable restart of the WWW service

1. From the Start menu, right-click My Computer, and click Manage.
2. In the console tree, expand the Services and Applications node, and click Services.
3. Right-click World Wide Web Publishing Service, and click Properties.
4. Click the Recovery tab, and in the First failure, Second failure, and Subsequent failures list boxes, click Take No Action.
5. Click OK.