IIS 5 & IIS 6
Setup & Migration
Multiple server migrations to IIS6
Last post Jun 04, 2010 05:53 PM by Rovastar
Jun 04, 2010 02:54 PM|Dustynet|LINK
Ive just had a project land in my lap which is to migrate hundreds of IIS sites from various versions of IIS (4,5,6) to IIS6.0. Im comfortable managing IIS from a GUI which is probably why (in a misguided way) this has landed with me. My hands are tied
with regards to the use of IISMT. None of the destination environments will be running IIS7, Only IIS6.0
I have just downloaded and tested IISMT 1.1 on the simplest of simple migrations and was horrified to find that this doesnt even configure web service extensions on the destination environment.
My question which will probably end up being a complicated on after a couple of responses is this:
Is there a clean and simple way of moving each website with IISMT, with all relevant IIS specific settings from the source system to a destination?
Im guessing the answer is no. So my second question is :
using WMI, or ADSI, can anyone provide some sample scripts which I may be able to run on the source server which can clearly identify the following information?
Site: access perms such as read, write, index, App name, starting point (Location), exec perms (scripts only etc), App pool defaults.
Virtual Directory: same details as for Site
Summary details of required web service extensions (where they are enabled)
If certs are used, and where they are stored / what type they are (if relevant)
Any GAC files which have been added
Anything else which is probably obvious to you, but not yet apparent to me.
Any help on this would be enormously appreciated. I havent just brain dumped this. Ive spent the last 2 days looking at WMI and ADSI trying to work out exactly how to pull these details, but sadly none of it is making much sense.
Thanks in anticipation
Jun 04, 2010 03:25 PM|Rovastar|LINK
For migrations it is unwise to blindly have faith in any tool. Without know more details about each site and all the dependancies you are on to a tough time.
To be brutally honest I would look at migrating them by hand one by one. Moving from IIS4 to IIS6 will be a right nightmare.......
You might be able to get away with good tools (and you don't even have the right tools for the job - http://www.techgalaxy.net/Docs/IIS/IISMT.htm)
Sorry that that is not the answer you want to here however it is the correct answer.
For compiling a list of things have a look at these scripting sites.
Sadly you will likely have to make you own based on teh commands available.
I don't think you have any hope of scripting what has been added to the GAC or not. Also look at other thing like ISAPI filters (urlscan, rewrite filters, etc), Dependant technologies, Index Services, any software proxies, etc firewall rules, routing for
existing sites, ODBC connections, detailed anaylsis of the web.configs (or relevant technologies), etc
Look through all the log files for existing errors you you have a baseline. Run through a link checker on the existsing sites so you have a baseline for after migration.
Really you need detailed information (from the devs, etc) about what each site does and the depenacies, etc. Some sites can be hideously complex depending on the technologies involved.
Other than that I would go through each site by hand look at all the GUI settings and screenshot/document them work out what is need to convert them for teh different version of IIS. Physically copy the files.
It all depends how complex each site is. I recently spent 3 months doing 2 sites running on 1 machine migrating IIS5 to 6........Good luck.
Jun 04, 2010 04:13 PM|Dustynet|LINK
Er, Thanks :'-(
Ill take a look at the links over the weekend, but as you say I may end up doing these by hand.
Jun 04, 2010 05:53 PM|Rovastar|LINK
Sorry there is not better news. Mayeb someoen else will have some.....
Have a look here at this reporting tool.
Even if you are forced into using the migration tool you might have more luck getting an audit of all the info.