« Previous Next »

Thread: Testing MSDeploy with -whatif

Last post 01-29-2009 4:36 PM by yaminij. 11 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (12 items)

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 01-13-2009, 2:31 PM

    Testing MSDeploy with -whatif

    Reply Contact

    I am having a little trouble getting through the verification of the migration behavior part of the instruction for MSDeploy.  I have a fairly simple environment; one IIS 6 box that I want to migrate to a new IIS 7 box.  I got to the point where you test the migration behavior before actually performing the migration; I used the follwing command:

    msdeploy –verb:migrate –source:webserver60,targetName=http://SourceComputername/msdeploy –dest:webserver60 –whatif > msdeploy_test.log

    I get the following error that I cant explain and was hoping someone could help me shed some light on:

    Fatal:  Unrecognized object parameter 'targetName'
    Fatal count: 1
    Tags:

  • 01-13-2009, 3:14 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    targetName is no longer supported. You should use computerName=<machineName> instead

     

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team

  • 01-13-2009, 3:16 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Thanks, sorry for basic question; I starting testing with MSDeploy.  Do you know of a current reference?

  • 01-13-2009, 10:40 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    You could start here http://learn.iis.net/page.aspx/346/web-deployment-tool/

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team

  • 01-14-2009, 9:28 AM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Thanks for your help.  One more quick question, does the migration process leave the source machine in tact after the migration is complete?  I have created a snap shot of the machine just incase, but was wondering what is the normal behavior?  Thanks again

  • 01-14-2009, 1:55 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Yes, migration will leave the source machine intact.

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team

  • 01-14-2009, 4:22 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    I have read some documents on how NTFS ACLs are handled, but didnt really get what I ws looking for; can you point me to a good source on the subject?  I am moving an intranet server that has some granular folder and file permissions.  Thanks for taking the time to answer my questions; as you can probably tell, I am fairly new at this process.

  • 01-14-2009, 4:44 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    You can use the includeAcls switch to accomplish copying ACLs to the destination. You can also look at the help file for msdeploy for more information.

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team

  • 01-21-2009, 4:45 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    C:\Program Files\IIS\Microsoft Web Deploy>msdeploy -verb:migrate -source:webserver60,computername=SERVER01,includeAcls=TRUE -dest:webserver60 -whatif > msdeploy_test.log

    I am trying to gage someone elses experience with the migration process. I ran the above command and now I have this large log file: Example

    Action: Adding child metaProperty (/LM/W3SVC/AspEnableAspHtmlFallback) Action: Adding child metaProperty (/LM/W3SVC/AspKeepSessionIDSecure) Action: Adding child metaProperty (/LM/W3SVC/AspLCID) Action: Adding child metaProperty (/LM/W3SVC/AspMaxRequestEntityAllowed) Action: Adding child metaProperty (/LM/W3SVC/AspQueueTimeout) Action: Adding child metaProperty (/LM/W3SVC/AspScriptErrorSentToBrowser) Action: Updating metaProperty (/LM/W3SVC/AuthFlags) Action: Adding child metaProperty (/LM/W3SVC/130010) Action: Adding child metaProperty (/LM/W3SVC/130008) Action: Adding child metaProperty (/LM/W3SVC/130004) Action: Adding child metaProperty (/LM/W3SVC/130003) Action: Adding child metaProperty (/LM/W3SVC/CGITimeout) Action: Updating metaProperty (/LM/W3SVC/DirBrowseFlags) Action: Adding child metaProperty (/LM/W3SVC/LogExtFileFlags) Action: Adding child metaProperty (/LM/W3SVC/LogInUTF8) Action: Adding child metaProperty (/LM/W3SVC/6269) Action: Updating metaProperty (/LM/W3SVC/AnonymousUserName) Action: Adding child metaProperty (/LM/W3SVC/AnonymousUserPass)

    Should I be getting some kind of error if there is an issue?

  • 01-21-2009, 4:52 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Yes, you would get an error if the migration did not go through and the changes made to the destination would get rolled back

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team

  • 01-23-2009, 10:56 AM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Thanks for the clarification.  One last question before D-Day:)  Looking at my script, can you tell me if I am using the "includeAcls" switch correctly?

    Microsoft Web Deploy>msdeploy -verb:migrate -source:webserver60,computername=QAINET01,includeAcls=TRUE -dest:webserver60 -whatif > msdeploy_test.log

    Is it really that simple; just run this and all is migrated (including content)?

  • 01-29-2009, 4:36 PM In reply to

    Re: Testing MSDeploy with -whatif

    Reply Contact

    Yes, you are doing the right thing. Yes, content will also get pulled in during migrate using contentExtensions

    Thanks
    Yamini Jagadeesan, SDET, Microsoft IIS Team
Page 1 of 1 (12 items)
Microsoft Communities