« Previous Next »

Thread: MS Deploy

Last post 11-26-2008 4:49 PM by paymasterr. 7 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (8 items)

Sort Posts:

  • 11-20-2008, 5:58 PM

    MS Deploy

     Hello,

     How do i migrate IIS6 (Win2k3 server) to IIS7 (Win2k8 server enterprise)  using the MS Deployment toolkit?

    I know about all those tutorials. For instance i followed this one http://technet.microsoft.com/en-us/mscomops/cc424869.aspx and i ended up with unknow factory fatal error when i tried to execute migrate command.

    I guess it is my broken English so i do not understand well those "on" target server "on" your server etc. pretty confusing for someone with English as second language.

    So, i was wondering if i can explain my situation and ask for some help. Thank in advance for understanding.

    1. i have about 1500 websites to the current WEB server (Win2k3). ServerOne

    2. i bought a new dedicated servers (both web and db Win2k8 driven).ServerTwo

    3. I need to move all the 1500 websites including the SSL certificate and all the other settings to the ServerTwo.

    4. I found that actually my only option is MSDEPLOY toolkit. Is this correct?

     

    I hope this is enough .. otherwise please ask me for additonal info if needed.

     

    Thanks in advance

  • 11-20-2008, 6:30 PM In reply to

    Re: MS Deploy

    You should install the Beta2 version of msdeploy from here

    After installing the Beta2 version, please do "net start msdepsvc" from the command-line on ServerTwo. Run the following command from ServerOne to start migration of your sites from ServerOne to ServerTwo

    msdeploy -verb:migrate -source:webserver60 -dest:webserver60,computername=ServerTwo

    By "target server", we mean the destination server to which you want all your sites to sync to. In your example, it is ServerTwo.

    "your server" is ServerOne which acts as the source

    Yes, msdeploy can help move all your sites including SSL certs from ServerOne to ServerTwo. I dont know if it is your only option, but it's probably the coolest option available :-)

    Please let us know if you run into any issues.

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team
  • 11-21-2008, 5:31 AM In reply to

    Re: MS Deploy

    Thanks for the quick answer Yamini,

     

    Actually i ran into some issues already.

    Therefore i have a few questions. thanks in advance :)

     

    According your answer, does it mean that webserver60 is sort of predefined variable or something like that.Otherwise it looks like both, dest and source happens on the same server which is ServerOne (iis 6.0) in my case.

    msdeploy -verb:migrate -source:webserver60 -dest:webserver60,computername=ServerTwo

    I believe that in my case it should be:

    msdeploy -verb:migrate -source:http://121.34.122.222 -dest:http://78.38.102.90,computername=ServerTwo  

    Currently it seems like MSDEPLOY knows my both machines IP's and names. But it doesn't if i am right.

     - actually do i need to set computername attribute for the ServerOne as well?

     

    Thank you very much

     

    P.S. this is the most confusing part for me. -source:http://121.34.122.222 is that all i need or there should be provided the name of the server or settings location e.g. lm/w3svc/1 ???

  • 11-21-2008, 2:58 PM In reply to

    Re: MS Deploy

    You should provide -source:webserver60 if you want to migrate the complete server with all sites, appPools, certs to IIS 7.0.

    If you want to migrate just a single site, then you should give -source:metaKey=/lm/w3svc/1.

    There is no need to specify computername=ServerOne if you are running the msdeploy command from ServerOne

     

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team
  • 11-21-2008, 3:05 PM In reply to

    Re: MS Deploy

    Means it will be fine if i execute the next command?

    msdeploy -verb:migrate -source:webserver60 -dest:webserver60,computername=ServerTwo

    even if the old server is named ServerONE and new server is named ServerTWO ?

    In that case it seems that webserver60 is sort of predefined variable. Please correct me if i am wrong.

    But why webserver60 for the new server "-source" if i want to migrate to IIS70 actually?

    don;t you think it should be webserver70 or something?

    OK it seems i am already asking too much .. i will try the command you gave to me and back if i run into troubles.

     

    Thanks for the explanations Yamini :)

  • 11-21-2008, 3:26 PM In reply to

    Re: MS Deploy

     ok i tried few combinations and i kept getting errors e.g.

     

    C:\Program Files\IIS\Microsoft Web Deploy>msdeploy -verb:migrate -source:webserv
    er60 -dest:webserver60,computername=H-KULERSRV.win.liquidweb.com
    Fatal:  Request to remote agent URL 'http://h-kulersrv.win.liquidweb.com/MSDE
    PLOYAGENTSERVICE' failed.
    Fatal:  The remote name could not be resolved: 'h-kulersrv.win.liquidweb.com'

    Fatal count: 1


    C:\Program Files\IIS\Microsoft Web Deploy>msdeploy -verb:migrate -source:webserv
    er60 -dest:webserver60,computername=H-KULERSRV
    Fatal:  Request to remote agent URL 'http://h-kulersrv/MSDEPLOYAGENTSERVICE'
    failed.
    Fatal:  The remote name could not be resolved: 'h-kulersrv'
    Fatal count: 1


    C:\Program Files\IIS\Microsoft Web Deploy>msdeploy -verb:migrate -source:webserv
    er60 -dest:webserver60,computername=http://55.205.164.128/H-kulersrv.win.liqu
    idweb.com
    Fatal:  Request to remote agent URL 'http://55.205.164.128/H-kulersrv.win.liq
    uidweb.com' failed.
    Fatal:  The remote server returned an error: (404) Not Found.
    Fatal count: 1


    C:\Program Files\IIS\Microsoft Web Deploy>msdeploy -verb:migrate -source:webserv
    er60 -dest:webserver60
    Fatal:  The Migrate6To7 dependency check detected a migrate attempt from IIS ver
    sion 6 to IIS version 6 which is not supported.  Migration is only allowed betwe
    en IIS 6 and IIS 7.
    Fatal:  The dependency check 'Migrate6to7' found issues up to 'Fatal' level that
     must be resolved before the current operation can be processed.  See previous m
    essages.
    Change count: 0
    Fatal count: 2

    C:\Program Files\IIS\Microsoft Web Deploy>

     

    Any idea? Maybe i needed to set webserver70 for the -dest attribute?

    Thanks in advance

  • 11-26-2008, 4:40 PM In reply to

    Re: MS Deploy

    Given your examples in your message, you probably want to run (assuming 12.34.56.78 is your remote destination server):

    msdeploy -verb:migrate -source:webserver60 -dest:webserver60,computername=12.34.56.78

    Make sure the remote agent is installed and running before running this, however.  The first word after -source: and -dest: is the type of item you wish to migrate/sync/dump.  In this case, 'webserver60" means an entire IIS6 server.  computername specifies the DNS name, IP address or URL for the web deployment agent service. There are also parameters for specifying a username, password, etc.

    If you're trying to figure out what commands will work, I'd suggest using -whatif so the commands do not actually start changing things until you're ready and sure you've got it figured out.  You can also sync the webserver to an archivedir or package (giant ZIP file) and manually copy this file to the destination and then migrate it onto the server, similar to the process described here.

  • 11-26-2008, 4:49 PM In reply to

    Re: MS Deploy

     uh it seems i have forgoten to mark the post as answered. Actually i couldn't find this option.

    However thanks for the input ckitching. :)

Page 1 of 1 (8 items)
Microsoft Communities