This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Silent Installation on New Hosts

Hi All,

 

I hope someone can point me in the right direction on this one.  I am trying to automate the silent installation on windows AWS EC2 hosts and having a few issues trying to generate the required XML file.  The intention is not to perform remote deployments but a fully silent installation on the host.

When I try and launch the Deployment Wizard on any of the numerous on premise (not EC2) servers we have available to generate the XML file it fails to open.  All servers have version 8.2 installed and I have tried on Windows Server 2008 R2, Windows Server 2012 R2 and Windows Server 2016.

The error received is "RemoteDeploy has stopped working"

Now as I have no need to remote deploy can any share a sample xml file I can use as a basis to run a silent installation?

  • Please upgrade to Litespeed version 8.6.1.36. The error you are seeing is an old bug with that version of Litespeed.

    Once upgraded you will be able to generate the xml files using the remote deploy wizard.


    Hope that helps,
    -Ben-
  • Ben, thanks for the reply. I did as suggested and managed to generate the XML file and perform a silent install. I need to verify all is working as expected but it seems like I am on the correct track.
  • Great! I am glad that resolved it!
  • Got another conundrum on this one, is there any way to configure storing the credentials of cloud accounts in litespeed via command line \ powershell etc rather than the litespeed UI? I need to setup storing an AWS IAM users access keys that will be used to restore the DB backups straight from AWS S3.
  • Please open a support case for further help with this and we can show you the file you can edit which holds the cloud account data.

    Also please note it is not a global setting as each user of the Litespeed console will have their own file which holds this information.

    Thanks,
    -Ben-
  • In the end I didn't need to add the keys programmatically. As the product is installed on an AWS EC2 instance that has an IAM role assigned which has access to the S3 bucket, when I restore a database from backups stored on S3 it works without providing the keys.

    For example:

    exec master.dbo.xp_restore_database @database = N'MyDB' ,
    @filename = N'BACKUPS/MyDB/FULL/MyDB_FULL.BKP',
    @encryptionkey = N'XXXXXXXXXXXXXXX',
    @CloudVendor = 'AmazonS3',
    @CloudRegionName = 'us-east-1',
    @CloudBucketName = 'mybucket',
    @logging = 0,
    @with = N'STATS = 10',
    @with = N'MOVE ''MyDB_data1'' TO ''D:\DATA\MyDB_data1.mdf''',
    @with = N'MOVE ''MyDB_data2'' TO ''D:\DATA\MyDB_data2.ndf''',
    @with = N'MOVE ''MyDB_log1'' TO ''D:\LOG\MyDB_Log.ldf''',
    @with = N'RECOVERY',
    @with = N'REPLACE'
    Go