IIS4.0 to IIS6.0 Migration Source Server Website

We are currently running a production website on a WinNT 4.0 server. My
question is, if I migrate from IIS4.0 on WinNT to IIS6.0 on Win2003 using the
IIS6.0 Migration Tool will the current website running on the source WinNT4.0
server be affected in any way?

--
Thanks,
Evan

David
Mon Oct 10 17:20:12 CDT 2005

The main issue is whether all the dependencies of your website still
function on Windows Server 2003, and only you can determine that. The
Migration tool will be fine to move IIS settings, but that is no guarantee
that your website will be "unaffected". You are migrating, after all.

For example, the migration tool will move the files and reconfigure the IIS
virtual directories for you, so moving simple HTM/ASP sites are easy.

But if your website uses custom ActiveX controls or ISAPI/CGI, then you need
to make sure that the register and function on Windows Server 2003 -- and
that is something that you must determine through experimentation (unless
you can determine from the vendor or the binary's source code as to whether
the custom software your website depends on is actually supporting Windows
Server 2003).

I'm not trying to scare you, but you must realize what a migration tool can
and cannot do within reason and correctness.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Evan" <Evan@discussions.microsoft.com> wrote in message
news:D9D7A153-B643-4E45-A5B7-A4E26EF98565@microsoft.com...

We are currently running a production website on a WinNT 4.0 server. My
question is, if I migrate from IIS4.0 on WinNT to IIS6.0 on Win2003 using
the
IIS6.0 Migration Tool will the current website running on the source
WinNT4.0
server be affected in any way?

--
Thanks,
Evan

Evan
Tue Oct 11 07:57:05 CDT 2005

David - Thanks for your answer, it is very informative. However, the Win2003
(destination) server is not in production yet and I have time to tweak the
migrated website. I was actually needing to know if the original website on
the source WinNT server will be affected in any way after I run the migration.

In other words if the migration does not work correctly and I am unable to
bring up the website on the destination Win2003 server, will I still have a
working IIS4.0 website on the source WinNT server?

Thanks,
Evan
--
Evan


"David Wang [Msft]" wrote:

> The main issue is whether all the dependencies of your website still
> function on Windows Server 2003, and only you can determine that. The
> Migration tool will be fine to move IIS settings, but that is no guarantee
> that your website will be "unaffected". You are migrating, after all.
>
> For example, the migration tool will move the files and reconfigure the IIS
> virtual directories for you, so moving simple HTM/ASP sites are easy.
>
> But if your website uses custom ActiveX controls or ISAPI/CGI, then you need
> to make sure that the register and function on Windows Server 2003 -- and
> that is something that you must determine through experimentation (unless
> you can determine from the vendor or the binary's source code as to whether
> the custom software your website depends on is actually supporting Windows
> Server 2003).
>
> I'm not trying to scare you, but you must realize what a migration tool can
> and cannot do within reason and correctness.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Evan" <Evan@discussions.microsoft.com> wrote in message
> news:D9D7A153-B643-4E45-A5B7-A4E26EF98565@microsoft.com...
>
> We are currently running a production website on a WinNT 4.0 server. My
> question is, if I migrate from IIS4.0 on WinNT to IIS6.0 on Win2003 using
> the
> IIS6.0 Migration Tool will the current website running on the source
> WinNT4.0
> server be affected in any way?
>
> --
> Thanks,
> Evan
>
>
>