« Previous Next »

Answered Thread: Migrate intranet website from iis6/2003 to iis6/2008

Last post 12-04-2009 2:47 PM by driftfly. 32 replies.

Average Rating Rate It (5)

RSS

Page 1 of 3 (33 items) 1 2 3 Next >

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 11-03-2009, 3:20 PM

    Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Hello,

    I recently purchased a new server running Windows 2008 and IIS 7.  I bought this server to replace our aging 2003/IIS6 box.  We have a large intranet site that I need to move over to the new box.  I am not an IIS expert by any means.  Is there a painless or semi-painless approach to doing this? 

     Thanks

  • 11-03-2009, 4:11 PM In reply to

    Answered Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    One very simple step that would carry over all your settings, sites, content etc from the old server to the new one is given below. From the location where you have msdeploy installed run the following:

    msdeploy -verb:sync -source:webserver60 -dest:webserver60,computername=yournewiis7server  -whatif -verbose

    This command you have to run from your old w2k3 box. -whatif will make it NOT sync and It will show you the changes it will carry out when you actually sync. This way you can know what all will happen. When you are all set to go then you can run the command without the whatif switch and it should do the job for you. For this you need to have msdeploy installed on the destination server as well as the source. [If you dont have it on the destination then you can use tempAgent]

    Let us know if you need more information

  • 11-04-2009, 9:51 AM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Moshaikh,

     Thanks for the quick reply.  Would I plugin the names of my servers under -source: and -dest: instead of webserver 60?  I know this seems pretty obvious, I just want to get it right.  I'm also concerned about some of the programs the website uses like a datepicker and spellchecker.  I guess I'll have to double-check the program to see where the references point.  I would also like to fine tune it once the swap is complete and working.  Any tips would be greatly appreciated.

     Thanks,

    Mike

  • 11-04-2009, 12:30 PM In reply to

    Answered Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    webserver60 is a provider and not the computer name. You can read more about providers here. So if you are syncing from COMP1 to COMP2 and you are running this command from some other system (not one of these) then you would do it as follows:

    msdeploy -verb:sync -source:webserver60,computername=COMP1,username=<yourusername>,password=<yourpassword> -dest:auto,computername=COMP2,username=<yourusername>,password=<yourpassword>

    If you are logged in a user that has admin permissions on COMP1 and COMP2 then you dont need to specify the username and password.

    You either have to install msdeploy on all those servers and start the msdepsvc agent or if you dont have msdeploy installed on those servers then you dont need to and you can use tempAgent switch as follows: [As long as you have WMI allowed thru the firewall on those boxes]

    msdeploy -verb:sync -source:webserver60,computername=COMP1,tempAgent=true -dest:auto,computername=COMP2,tempAgent=true

    Let us know if you need more information.

  • 11-04-2009, 12:51 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Moshaikh,

    Once again, thanks for the great information!  I noticed you went from the "webserver60" provider to the "auto" provider for the destination server on this latest post.  We are going from a 2003/IIS6 box to a 2008/IIS7 box.  I read that you cannot use the "webserver60" provider going the other way, but it doesn't say anything about going this way.  Is there any significance to this provider change?

    Thanks,

    Mike

  • 11-04-2009, 1:04 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    All auto does is it tells msdeploy to get the right provider for the destination based on the source provider. SO in this case it knows the source is a webserver60 so it will resolve to webserver60 for destination automatically.

    webserver60 is the provider you use from syncing from win2k3/WinXP to IIS07 or iis 7.5 and  for win2k3 to win2k3.

    For iis7 to iis7 (or 7.5 to 7.5) you use webserver provider.

     

  • 11-04-2009, 1:05 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Moshaikh,

    What would the command be to go from a 2003/IIS6 box to a Vista Ultimate 64/IIS7 box?

    Thanks,

    Mike

  • 11-04-2009, 2:56 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Same command as above. No difference. 

    msdeploy -verb:sync -source:webserver60,computername=COMP1,username=<yourusername>,password=<yourpassword> -dest:auto,computername=COMP2,username=<yourusername>,password=<yourpassword>

     The only time you will use webserver is when BOTH servers are iis7 or higher.

     

  • 11-05-2009, 11:49 AM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Moshaikh,

     Actually, the last post was asking about a migration from iis6/2003 to a iis7/Vista Ultimate 64 bit machine.  I don't know where the iis6/2003 to iis6/2008 came from.  I greatly appreciate the correspondence though.  This is valuable information.

    Anyway, when I perform this migration, does the IIS service need to be stopped on both servers or anything?  Can this be done while the source server is serving up web pages (live)?  Once again, I really appreciate your knowledge.

    Thanks,

    Mike

  • 11-05-2009, 1:58 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Where do I find the msdepsvc agent to start?

  • 11-05-2009, 2:01 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Okay, it is the Web Deployment Agent Service.  Sorry!

  • 11-05-2009, 2:44 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Mashaikh,

     I ran the command with the whatif verbose switches and everything seems fine.  I have a couple of warnings though.

     Warning: The DependencyCheckInUse rule handler detected HttpRedirect. Use Windows Setup to install the component.

    Warning: The Dependency Check In Use Rule detected ASP.NET version v1.1. Make sure that ASP.NET is installed and configured with IIS on the destination.

    Any tips and/or thoughts on these warnings?

     Thanks,

    Mike

  • 11-05-2009, 2:54 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    MSDeploy does not install IIS components or dependencies for you. So the message is trying to tell you that you can go ahead with the sync but make sure that you install and / or configure the required components, modules etc on the target server

     

  • 11-05-2009, 3:45 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    Moshaikh,

    The only warning I'm not able to get rid of is the second one:

    Warning: The Dependency Check In Use Rule detected ASP.NET version v1.1. Make sure that ASP.NET is installed and configured with IIS on the destination.

    Exactly how do I check this one?  As far as I can see, ASP.NET is installed.  In Server Manager under Web Server (IIS) and Role Services directly under Application Development it is definitely installed.

    Thanks,

    Mike

  • 11-05-2009, 8:32 PM In reply to

    Re: Migrate intranet website from iis6/2003 to iis6/2008

    Reply Contact

    You may have other issues going from Windows 2003 server/IIS6 to non-server Vista OS and IIS7. Vista the desktop OS is not designed as a server for websites.

    http://www.iisportal.com
Page 1 of 3 (33 items) 1 2 3 Next >
Microsoft Communities