So we worked upon a PowerShell script which can help you help you migrate FTP websites and virtual directories with very basic settings. You can modify this script to do more while migrating like username and others..

In order to run the script you need Metabase.xml file from Windows 2003 box. You can find this file in %SystemRoot%\system32\inetsrv folder. Please open Metabase.xml file in notepad and remove <configuration> tab from the top and bottom of document. Once done, run below script :

# Remove the following lines from the XML source file before running this 
# <configuration xmlns="urn:microsoft-catalog:XML_Metabase_V64_0"> 
# </configuration> 

# Developed under Powershell V2 on 2008 R2 
# invoke "importsystemmodules" to get the webAdministration libraries loaded 

#importsystemmodules 

select-xml -path d:\temp\MetaBase.xml -xpath "//IIsFtpVirtualDir" | % { 
    $location= split-path $_.node.getattribute("Location") -leaf 
    $path = $_.node.getattribute("Path") 

     
        # Use this to test, this will give you stack of commands to execute which you can validate, add or modify and create another script file.
     "New-WebVirtualDirectory -site 'Default FTP Site' -name '$location' -physicalpath `"$path`" -Force"  # | out-file -append c:\temp\junk.txt.xml 

    # Use this to really create on IIS if you are sure (backup first)
    # "New-WebVirtualDirectory -site 'Default FTP Site' -name $location -physicalpath `"$path`"" 

createFTP.ren2ps1.txt

In IIS7, we could register the IP address as hostname. If we do this in IIS8, I get the failure message:

---------------------------
Edit Site Binding
---------------------------
The specified host name is incorrect. The host name must use a valid host name format and cannot contain the following characters: "/\[]:|<>+=;,?*$%#@{}^`. Example: www.contoso.com.
---------------------------
OK  
---------------------------

This is by design in IIS 8 UI. Hence we wont be able to skip this from UI. Though as a workaround you can directly edit applicationhost.config from  %SystemRoot%\system32\inetsrv\config folder. Please do take a back up of this file before directly editing. Once backed up, open applicationhost.config file in notepad. Try finding the bindings something like and add it manually:

 <site name="mstest" id="4" serverAutoStart="true">
                <application path="/" applicationPool="mstest">
                    <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                </application>
                <bindings>

                    <binding protocol="http" bindingInformation="*:80:mydomainnamedotcom" />
                    <binding protocol="http" bindingInformation="*:80:192.168.172.1" />
                </bindings>
            </site> 

 This seems to work in my black box testing. Let me know if any comments or suggestions.

~ Devendra Asane

We can customize our batch file which has been mentioned in KB828222 and use the same batch file for taking the dump. I have customized my batch file like below:

@if "%_echo%"=="" echo off

setlocal
    set TIMESTAMP=%DATE:~-9%_%TIME%
set TIMESTAMP=%TIMESTAMP:/=_%
set TIMESTAMP=%TIMESTAMP::=_%
set TIMESTAMP=%TIMESTAMP:.=_%
set TIMESTAMP=%TIMESTAMP: =_%
set FILENAME=c:\debuggers\deadlocked_PID_%1_%TIMESTAMP%.dmp
set LOG=c:\debuggers\procdumplog.txt
set COMMAND=c:\debuggers\procdump.exe -ma %1 %FILENAME%
echo %COMMAND% > %LOG%
%COMMAND%
endlocal

For IIS6, store this batch file to the path you wish and use the same path to configure adsutil.vbs like mentioned in KB828222.

&

For IIS 7+, IIS manager can be used to configure application pool. IIS Manager >> Application Pools >> Advanced Setting (on particular application pool ) >> Process Orphaning >> Executable --> Batch file which we created & Executable Parameters --> %1

ProcDump

https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

How to generate a dump file when ASP.NET deadlocks in IIS 6.0

https://support.microsoft.com/kb/828222

Cheers!

Devendra Asane

The reason for above error lies in new Code access security (CAS) model. So just switching to 4.0 framework may not help. You need to configure ASP.Net 4.0 application to Use the ASP.Net 2.0 CAS Model as a workaround which brings you back to legacy CAS model from .Net 2.0. 

Add the following line to our web.config file :

<trust level="Full" originUrl="" legacyCasModel="true"/>

Please refer following article for more information on:

Code Access Security in ASP.NET 4 Applications

https://msdn.microsoft.com/en-us/library/dd984947.aspx

In Server Manager >> TOOLS >> Computer Management.

To export the All Website from IIS 6 in a package:

msdeploy -verb:sync -source:metakey=lm/w3svc -dest:package=c:\temp\AllSites.zip,encryptPassword=test -enableLink:appPool

To import All Websites from the package on IIS 7:

msdeploy -verb:sync -source:package=C:\temp\AllSites.zip,encryptPassword=test -dest:metakey=lm/w3svc,rootwebconfig32.netfxversion=2.0.50727,encryptPassword=test -enableLink:appPool

1) Create a Regular Expression :

2) Create a Pattern :

We can use Debug Diagnostics 1.2 on windows 2008 and Windows 7.  Please visit KB https://support.microsoft.com/kb/2580960 for more information.

Also Windows 2008 and Windows 7 has got WER services which can take the User-Mode crash dump. This works very well for x64 versions too.

To configure WER services please visit the below link :

Collecting User-Mode Dumps

https://msdn.microsoft.com/en-us/library/bb787181(VS.85).aspx

Starting with Windows Server 2008 and Windows Vista with Service Pack 1 (SP1), Windows Error Reporting (WER) can be configured so that full user-mode dumps are collected and stored locally after a user-mode application crashes.

For example if my IIS 7 worker process i.e. w3wp.exe is crashing then I need to configure below.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\w3wp.exe]

"DumpFolder"= REG_EXPAND_SZ: c:\temp

"DumpCount"=dword:00000005

"DumpType"=dword:00000002

And above registry settings will give you 5 dumps for w3wp.exe if it crashes.

Collecting User-Mode Hang Dumps

For taking hand dumps in Windows 7 and Windows 2008 server, we need to figure the hung process. Open task manager >> figure out the hung process >> right click on the hung process >> click “Create Dump File”.   And dump will be taken on the temp path. The path will be shown in the dialogue box. Press Ctrl + C on the dialogue box and message(path) will be copied to the clipboard.

This applies to x64 versions as well. For advanced users there is always "Debugging tools for Windows"

https://www.microsoft.com/whdc/DevTools/Debugging/default.mspx

	Install Debugging Tools for Windows 32-bit Version Download page for the latest 32-bit packages.
	Install Debugging Tools for Windows 64-bit Versions Download page for the latest 64-bit packages.

Your capability to configure application pools enables you to limit the kernel request queue size, limit CPU utilization, and apply other restrictions to help ensure that an attack, when it comes, will have its impact minimized on the server overall. To help combat buffer overflow attacks, IIS 6.0 monitors incoming requests to identify unusually large transaction requests that are indicative of an attack. You can also configure IIS 6.0 to recycle worker processes if they consume too much physical or virtual memory based on limits that you specify on a per-application-pool basis, reducing the impact of memory overflow exploits. Your capability to isolate sites and applications using multiple application pools and to configure recycling parameters for those pools helps reduce the effect of denial-of-service attacks.

Also as we see in below IIS6 architecture image the http.sys takes the credit for securing the IIS from Denial of Service attack by restricting the connection limit. But Http.sys is kernel component and hence if its affected by flood of million connections means your whole box is affected. In case of Attack, the http.sys will accept only configured connection and rest of these connections will be rejected by IIS 503 error. Only configured connections will be send to the application pool to serve the requests.

Denial of Service (DOS) attack symptoms:

==========================================

A Denial of Service (DOS) attack is made up of excessive successful or unsuccessful attempts to access the Web server or site with HTTP, File Transfer Protocol (FTP), or another protocol from a single IP address with the possible intention of increasing network traffic and denying access to other users.

Possible Actions to prevent the attacks

==========================================

·         Install URLScan and configure DenyUrlSequences to deny /. This will typically be implemented by the security team at your end. The following URL describes in detail about what URLSCAN is and how to configure it

UrlScan Security Tool

https://msdn.microsoft.com/en-us/library/aa302368.aspx

·         Prevent Denial of Service (DOS) attacks in your web application

https://weblogs.asp.net/omarzabir/archive/2007/10/16/prevent-denial-of-service-dos-attacks-in-your-web-application.aspx

·         For this type of attempt, set the firewall policy or TCP/IP filtering to block the IP. If the IP is internal, take the computer off the network to determine why it is trying to access the HTTP or FTP services of the Web server excessively.

https://msdn.microsoft.com/en-us/library/aa302363.aspx

·         ISA Server Network Protection: Protecting Against Floods and Attacks

https://technet.microsoft.com/en-us/library/bb794735.aspx

·         Restrict the connection to a particular number of connections. The number of connection is something which you need to decide on the basis of your infrastructure and threat model.

·         Building Secure Web Services

https://msdn.microsoft.com/en-us/library/aa302428.aspx

Your capability to configure application pools enables you to limit the kernel request queue size, limit CPU utilization, and apply other restrictions to help ensure that an attack, when it comes, will have its impact minimized on the server overall. To help combat buffer overflow attacks, IIS 6.0 monitors incoming requests to identify unusually large transaction requests that are indicative of an attack. You can also configure IIS 6.0 to recycle worker processes if they consume too much physical or virtual memory based on limits that you specify on a per-application-pool basis, reducing the impact of memory overflow exploits. Your capability to isolate sites and applications using multiple application pools and to configure recycling parameters for those pools helps reduce the effect of denial-of-service attacks.

Denial of Service (DOS) attack symptoms:

==========================================

A Denial of Service (DOS) attack is made up of excessive successful or unsuccessful attempts to access the Web server or site with HTTP, File Transfer Protocol (FTP), or another protocol from a single IP address with the possible intention of increasing network traffic and denying access to other users.

Possible Actions to prevent the attacks

==========================================

·         Install URLScan and configure DenyUrlSequences to deny /. This will typically be implemented by the security team at your end. The following URL describes in detail about what URLSCAN is and how to configure it

https://www.urlscan.net/

https://msdn.microsoft.com/en-us/library/aa302368.aspx

·         Prevent Denial of Service (DOS) attacks in your web application

https://weblogs.asp.net/omarzabir/archive/2007/10/16/prevent-denial-of-service-dos-attacks-in-your-web-application.aspx

·         For this type of attempt, set the firewall policy or TCP/IP filtering to block the IP. If the IP is internal, take the computer off the network to determine why it is trying to access the HTTP or FTP services of the Web server excessively.

https://msdn.microsoft.com/en-us/library/aa302363.aspx

https://support.microsoft.com/default.aspx?scid=kb;en-us;324270

·         ISA Server Network Protection: Protecting Against Floods and Attacks

https://technet.microsoft.com/en-us/library/bb794735.aspx

·         Restrict the connection to a particular number of connections. The number of connection is something which you need to decide on the basis of your infrastructure and threat model.

·         Building Secure Web Services

https://msdn.microsoft.com/en-us/library/aa302428.aspx

For IIS 7.0 there is a tool called Dynamic IP Restrictions Extension for IIS which is still beta but has got below benefits

1. Reduce the chances of a Denial of Service attack by dynamically blocking requests from malicious IP addresses.
2. Minimize the possibilities of Brute-force-cracking of the passwords of your Web Server.
3. Maintain static lists containing IPs or domains that are begin denied to access the Web Server