none
DPM2012 Sql 2012 silent install RRS feed

Answers

  • Hi,

    Yes, most likely a bug in the installer. SQL 2012 as DPMDB was not added until late in the DPM 2012 SP1 development cycle, so may have never been tested.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 21, 2013 8:21 PM
    Moderator

All replies

  • Hi,

    I have not tried unattended using local SQL 2012, so not sure if these switches will still work, but you basically want to use the section for remote SQL server.   Avoid SQL Server instance named MSDPM2012 as that is reserved by setup code for DPM installation of SQL.

    Performing Unattended Installation
    http://technet.microsoft.com/en-us/library/jj663108.aspx

    [OPTIONS]
    UserName = <A user with credentials to install DPM>
    CompanyName = <Name of your company>
    ProductKey = <The 25-character DPM product key in the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx>
    SqlAccountPassword = <The password to the DPM$ account>
    # StandardAgentLicenses = <No. of standard agent licenses you have purchased>
    # EnterpriseAgentLicenses = <No. of enterprise agent licenses you have purchased>
    # ProgramFiles = C:\Program Files\Microsoft Data Protection Manager
    # DatabaseFiles = C:\Program Files\Microsoft Data Protection Manager\DPM\DPMDB
    # IntegratedInstallSource = <Location of the DPM setup files>
    # ---For using a remote SQL Server instance ---
    # YukonMachineName = <Name of the SQL Server computer>
    # YukonInstanceName = <Name of the instance of SQL Server that Setup must use>
    # YukonMachineUserName = <User name that Setup must user>
    # YukonMachinePassword = <Password for the user name Setup must use>
    # YukonMachineDomainName = <Domain to which the SQL Server computer is attached>


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 21, 2013 7:27 PM
    Moderator
  • Hi mike thanks for the reply

    spent some time yesterday testing this however the install fails..in the logs it looks like it keeps looking for a 2008 instance of SQL. Have tested with both a local and remote copy of sql2012. I could send through the logs if it could help?

    I have previously used the silent install with sql2008 first attempt with 2012... Could this be a bug in the install routine?

    .

    Thursday, February 21, 2013 7:56 PM
  • Hi,

    Yes, most likely a bug in the installer. SQL 2012 as DPMDB was not added until late in the DPM 2012 SP1 development cycle, so may have never been tested.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 21, 2013 8:21 PM
    Moderator
  • Hi,

    Recent feedback from the DPM product group.

    Unattended installation of DPM will not detect the local SQL 2012 instance, but we can mention the instance name to which DPM has to be installed using the YukonInstanceName parameter.

    Command for Unattended Install of DPM of Customized Local Instance is:

        start /wait [media location]\setup.exe /i /y /localSql /f <path>\Dpmsetup.ini /l <path>\dpmlog.txt


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, March 1, 2013 5:00 PM
    Moderator
  • Thanks for the follow up Mike,

    I tried using the above command specifying the local SQL instance which was SQL 2012. however the installer bailed out with an error about a user account not specified during the install.

    Could you confirm that the above will work with a 2012 instance of SQL server and if possible provide an example dpmsetup.ini file with dummy parameters required to be specified.

     Thanks

    Steve

    Sunday, March 3, 2013 9:05 PM