MicroStrategy Silent Install Blog #2

Here is more comprehensive blog regarding silent installation. Ignore/Excuse the document format as it is a copy/paste from Microsoft Word.

1.               Required Components

1.       Setup.exe along with supporting installation files for MicroStrategy product

2.       Response.ini

3.       Setup.iss – file containing responses to required input by InstallShield during installation

4.       Batch File - .bat file containing the command to be executed

1.1.         Setup.exe

Setup.exe is shipped with other MicroStrategy installation files. Usually downloaded as a zip file and can be unzipped to any location. For purposes of Silent Install, this file could be located locally or on a network drive.

1.2.         Response.ini

Response.ini file contains responses to input requested by MicroStrategy during installation. Response.ini can be used to install/uninstall MicroStrategy, apply hotfixes as well as to create Project Sources. Although the file could be given any name, it is ideal, safe and recommended to name it as response.ini. Response.ini should be stored in the same location as the setup.exe. There have been issues documented on MicroStrategy forums pointing towards permissions related issues when stored separately from setup.exe.

Response file provides information regarding preparation for the install (stop services, create shortcuts etc), User Registration (company name, license key etc), components offered for installation components to be installed.

1.3.         Setup.iss

Setup.iss file contains responses to input requested by InstallShield during installation. This file provides information such as MicroStrategy version, software creator company name and language code. It is very critical that the MicroStrategy version being installed matches the version that you mention in setup.iss.

1.4.         Batch File

Batch file simply consists of instructions to execute the [un]installation. Batch file can be located anywhere on the system as long as it has fully qualified UNC file path. The batch file samples provided in this document do not contain “-s” flag so users will still see the progress bar on the screen. Including the “-s” flag will make the installation invisible to users and can only be seen in task manager.

2.               Process

2.1.         To Install

Use Batch File sample below.

2.1.1.      Batch File Sample

"\\AppropriateNetworkPath\setup.exe"

-L0009

--ResponseFile="\\AppropriateNetworkPath\response.ini"

-f1”\\AppropriateNetworkPath\setup.iss”

-f2"c:\silentinstall\setup.log"

2.1.2.      Response File Sample

For security reasons, the License Key displayed below is not the actual one.

[Installer]

HideAllDialogs=TRUE

PreventReboot=FALSE

ForceReboot=TRUE

ShowConfigWizard=FALSE

ShowWelcomeScreen=FALSE

StopAllServices=TRUE

CheckRenameOperations=FALSE

TutReportingOverwrite=FALSE

CreateShortcuts=TRUE

 

 ### Company Name ###

[UserRegistration]

CompanyName=Your Company Name

LicenseKey=68xyszdjfPn9gpAnkeetIsAwesomesstyhvqxqBxxznvF7rvW86r4xgcs4xqd93v

 

### Visible Components ###

[ComponentSelection]

HideDialog=TRUE

AnalyticsModulesVisible=FALSE

ArchitectVisible=TRUE

CommandManagerVisible=FALSE

DeliveryEngineVisible=FALSE

DesktopDesignerVisible=TRUE

DesktopAnalystVisible=TRUE

EnterpriseManagerVisible=FALSE

FunctionPluginVisible=FALSE

GISConnectorsVisible=FALSE

IntegrityManagerVisible=FALSE

IServerDistributionServicesVisible=FALSE

IServerOLAPServicesVisible=FALSE

IServerReportServicseVisible=FALSE

IServerTransactionServicesVisible=FALSE

IServerVisible=FALSE

MobileClientVisible=FALSE

MobileServerASPVisible=FALSE

MobileServerJSPVisible=FALSE

MobileVisible=FALSE

NCSAdminVisible=TRUE

ObjectManagerVisible=FALSE

OfficeVisible=FALSE

PortletsVisible=FALSE

ProjectBuilderVisible=TRUE

SDKVisible=FALSE

SequeLinkVisible=FALSE

ServerAdminVisible=TRUE

SubscriptionPortalVisible=FALSE

TMIConnectorVisible=FALSE

TutorialDeliveryConfigureVisible=FALSE

TutorialDeliveryInstallVisible=FALSE

TutorialReportingVisible=FALSE

WebAnalystVisible=FALSE

WebMMTVisible=FALSE

WebProfessionalVisible=FALSE

WebReporterVisible=FALSE

WebServerASPNETVisible=FALSE

WebServerJSPVisible=FALSE

WebServicesASPNETVisible=FALSE

WebServicesJSPVisible=FALSE

 

### Components To Install (TRUE) or Remove (FALSE) ###

AnalyticsModulesSelect=FALSE

ArchitectSelect=TRUE

CommandManagerSelect=FALSE

DeliveryEngineSelect=FALSE

DesktopDesignerSelect=TRUE

DesktopAnalystSelect=TRUE

EnterpriseManagerSelect=FALSE

FunctionPluginSelect=FALSE

FunctionPluginSelect=FALSE

GISConnectorsSelect=FALSE

IntegrityManagerSelect=FALSE

IServerDistributionServicesSelect=FALSE

IServerOLAPServicesSelect=FALSE

IServerReportServicseSelect=FALSE

IServerTransactionServicesSelect=FALSE

IServerSelect=FALSE

MobileClientSelect=FALSE

MobileServerASPSelect=FALSE

MobileServerJSPSelect=FALSE

MobileSelect=FALSE

NCSAdminSelect=TRUE

ObjectManagerSelect=FALSE

OfficeSelect=FALSE

PortletsSelect=FALSE

ProjectBuilderSelect=TRUE

SDKSelect=FALSE

SequeLinkSelect=FALSE

ServerAdminSelect=TRUE

SubscriptionPortalSelect=FALSE

TMIConnectorSelect=FALSE

TutorialDeliveryConfigureSelect=FALSE

TutorialDeliveryInstallSelect=FALSE

TutorialReportingSelect=FALSE

WebAnalystSelect=FALSE

WebMMTSelect=FALSE

WebProfessionalSelect=FALSE

WebReporterSelect=FALSE

WebServerASPNETSelect=FALSE

WebServerJSPSelect=FALSE

WebServicesASPNETSelect=FALSE

WebServicesJSPSelect=FALSE

2.1.3.      Setup.iss File Sample

[InstallShield Silent]

Version=v7.00                                                                

File=ResponseFile

[File Transfer]

OverwrittenReadOnly=NoToAll

[Application]

Name=MicroStrategy

Version=9.3.0

Company=MicroStrategy

Lang=0009

[{8CCF3F6C-55B7-4A27-8C68-ADF21D0585A2}-DlgOrder]

Count=0

2.2.         To Uninstall

2.2.1.      Batch File Sample

"\\AppropriateNetworkPath\setup.exe" 

-L0009 

--ResponseFile="\\AppropriateNetworkPath\response.ini" 

-f1"\\AppropriateNetworkPath\setup.iss" 

-f2"c:\silentinstall\setup.log"

2.2.2.      Response File Sample

[Installer]

PropertiesFilesOverwrite=FALSE

EnableTracing=FALSE

HideAllDialogs=TRUE

ForceReboot=TRUE

PreventReboot=FALSE

CheckTCPIP=TRUE

CheckIIS=TRUE

CheckSP=TRUE

CreateShortcuts=TRUE

CheckRenameOperations=TRUE

AnalyticsOverwrite=FALSE

TutReportingOverwrite=FALSE

TutDeliveryOverwrite=FALSE

BackupFiles=FALSE

RunConfigWizard=FALSE

StopAllServices=TRUE

StopIIS=TRUE

EnableASPServices=FALSE

ConfigWizardResponseFile=

RegistrySizeReq=

LogFile=

[UserRegistration]

LicenseKey=ygzzAnkeetIsAwesomez2PxyslkjsdfWzz2zzzMoreAwesomeNowweev2z94hzzz832B24

[Welcome]

HideDialog=TRUE

RemoveAll=TRUE

[WebVirtualDirectory]

HideDialog=TRUE

VirtualDirectory=MicroStrategy

RemoveVD=YES

[MobileVirtualDirectory]

HideDialog=TRUE

VirtualDirectory=MicroStrategyMobile

RemoveVD=YES

[PortalVirtualDirectory]

HideDialog=TRUE

VirtualDirectory=NarrowcastServer

RemoveVD=NO

[WebServicesDirectory]

HideDialog=TRUE

VirtualDirectory=MicroStrategyWS

RemoveVD=YES

[WebMMTVirtualDirectory]

HideDialog=TRUE

VirtualDirectory=WebMMT

RemoveVD=NO

[Finish]

HideDialog=FALSE

2.2.3.      Setup.iss File Sample

[InstallShield Silent]

Version=v7.00

File=ResponseFile

[File Transfer]

OverwrittenReadOnly=NoToAll

[Application]

Name=MicroStrategy

Version=7.2.3

Company=MicroStrategy

Lang=0009

[{8CCF3F6C-55B7-4A27-8C68-ADF21D0585A2}-DlgOrder]

Count=0

Make sure that the version for MicroStrategy matches the version of MicroStrategy being uninstalled.

2.3.         To Apply Hotfix

Download the hotfix from MicroStrategy website and uninstall it in a network folder (assuming hotfix needs to be applied for more than just one user). This hotfix will come bundled with HFResponse.ini and HFSetup.iss. There is no need to create your own response and setup files.

Following sample is for MSTR 9.3.0 Hotfix 4. When a new hotfix is released in the future, all you would need to do is change the path to the setup, response and iss files in below sample.

2.3.1.      Batch File Sample

"\\AppropriateNetworkPath\setup.exe"

-L0009

--ResponseFile=”\\AppropriateNetworkPath\HFResponse.ini”

-f1"\\AppropriateNetworkPath\HFsetup.iss"

-f2"c:\silentinstall\setup.log"

2.4.         To Create Project Source

All that is needed is a batch file and a response file.

macfgwiz.exe -r "\\AppropriateNetworkPath\ProjectSource_Response.ini"

                               

Below response file will create a 3-tier project source with standard authentication connecting to IServer.yourcompanydomain.com on port 34952. Multiple project source connections can be created in the same response file.

2.4.1.      Response File Sample

[Client1]

Client=1

DataSource=ReplaceWithDataSourceNameHere

ConnType=3

UserName=

ServerName=IServer.yourcompanydomain.com

Port=34952

MDType=0

Hide=False

Authentication=1

 For more information, please refer to MicroStrategy Installation and Configuration Guide.