I wonder if anyone can tell me if the Migration tool will allow me to migrate
IIS 6.0 services from W2K3 standard to a x64 Windows 2003 R2 Ent OS ?
we are going through a hardware and OS Refresh project and I can't find
anything on this - any extra advice/links that can be offered would be much
appreciated
--
jobbsy@discussions.microsoft.com
On Dec 4, 4:02 am, Jobbsy
> I wonder if anyone can tell me if the Migration tool will allow me to migrate
> IIS 6.0 services from W2K3 standard to a x64 Windows 2003 R2 Ent OS ?
>
> we are going through a hardware and OS Refresh project and I can't find
> anything on this - any extra advice/links that can be offered would be much
> appreciated
> --
> job...@discussions.microsoft.com
That scenario was never tested, but it should work... because you are
responsible for making sure that any referenced DLLs are the correct
bitness on 64bit Windows, just like you are responsible that the same
pathnames are used for migrated Application Mappings.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
hmmm never tested - don't like the sound of that
Can you perhaps elaborate on ' you are responsible for making sure that any
referenced DLLs are the correct bitness on 64bit Windows'
failing that we don't feel confident with migrating to x64 - is there a step
by step white paper that includes all checks that should be carried out pre
migration etc?
What is the recommendation? - to perform the migration to boxes with
alternate IP addresses (obviously with all required NATing & FW Rules in
place) - this would perhaps be the preferred route as any probs we can just
switch the old boxes back on.
--
jobbsy@discussions.microsoft.com
"David Wang" wrote:
> On Dec 4, 4:02 am, Jobbsy
> > I wonder if anyone can tell me if the Migration tool will allow me to migrate
> > IIS 6.0 services from W2K3 standard to a x64 Windows 2003 R2 Ent OS ?
> >
> > we are going through a hardware and OS Refresh project and I can't find
> > anything on this - any extra advice/links that can be offered would be much
> > appreciated
> > --
> > job...@discussions.microsoft.com
>
>
> That scenario was never tested, but it should work... because you are
> responsible for making sure that any referenced DLLs are the correct
> bitness on 64bit Windows, just like you are responsible that the same
> pathnames are used for migrated Application Mappings.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
Migrating to 64bit will not be hands-free. I don't know of any tool
that just takes an existing 32bit setup and make it work on 64bit
Windows.
The ease of migration is completely dependent on how well the user
kept track of the binary dependencies of their web application as well
as that dependency's cooperation with 64bit Windows.
In other words, there's a lot of IFs that have to line up in order for
migration to be hands-free, and I wouldn't hold my breath.
For example, suppose your application relies on ASP.Net 2.0 32bit,
which resides in a different directory than ASP.Net 2.0 64bit, so
Application Mapping values are different. Since neither ASP.Net
versions are default on Windows Server 2003, no tool should
automatically map them on migration, and if you use the old
Application Mapping settings on 64bit Windows, that will fail because
you cannot load 32bit DLLs into 64bit processes. Migration fails.
Basically, in the above example, if you copy old values, it's wrong;
if you delete the old values, it's wrong; if you use new values but
ASP.Net is not installed, it's wrong; if you change IIS6 to run in
WOW64 emulation mode, that works only if there are no 64bit DLLs
loaded anywhere else in IIS. Thus, unless the Migration tool has
appropriate binaries for all your applications, the migration will not
magically work.
I don't know of a tool that does the above. There may be tools that
claim to migrate, but unless they do the above, I don't believe those
tools migrate correctly.
For most people, I recommend building out a new box and reinstall all
applications and settings, making sure to validate ALL binary
dependencies either have a 64bit version of the binary (i.e. make sure
your apps say they support 64bit Windows), or function properly in
WOW64 emulation mode on 64bit Windows. Very few people have their IFs
lined up to migrate, so the only sure way is to do it from scratch.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Dec 4, 5:13 am, Jobbsy
> hmmm never tested - don't like the sound of that
>
> Can you perhaps elaborate on ' you are responsible for making sure that any
> referenced DLLs are the correct bitness on 64bit Windows'
>
> failing that we don't feel confident with migrating to x64 - is there a step
> by step white paper that includes all checks that should be carried out pre
> migration etc?
>
> What is the recommendation? - to perform the migration to boxes with
> alternate IP addresses (obviously with all required NATing & FW Rules in
> place) - this would perhaps be the preferred route as any probs we can just
> switch the old boxes back on.
> --
> job...@discussions.microsoft.com
>
>
>
> "David Wang" wrote:
> > On Dec 4, 4:02 am, Jobbsy
> > > I wonder if anyone can tell me if the Migration tool will allow me to migrate
> > > IIS 6.0 services from W2K3 standard to a x64 Windows 2003 R2 Ent OS ?
>
> > > we are going through a hardware and OS Refresh project and I can't find
> > > anything on this - any extra advice/links that can be offered would be much
> > > appreciated
> > > --
> > > job...@discussions.microsoft.com
>
> > That scenario was never tested, but it should work... because you are
> > responsible for making sure that any referenced DLLs are the correct
> > bitness on 64bit Windows, just like you are responsible that the same
> > pathnames are used for migrated Application Mappings.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -