MicroStrategy MicroStrategy

Views: 4.1k  |  Created: 09/15/2009

Average Rating: 0
MicroStrategy has 3 inventory records, 1 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (7)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 5 / 5 (Very Difficult) based on 4 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
or cancel
4
Command Line
I tried to repackage the application with Wise but owing to the size of the application (12,000+ files and 40,000+ reg keys) using just the components we needed, it was unmanagable.

I therefore went with the method recommended in the deployment documentation of using a command line, a setup.iss file and a response.ini file.

The eventual command line I used for the Desktop components was

setup.exe -L0009 --ResponseFile="C:\response.ini" -f1c:\setup.iss -f2c:\temp\microdt.log

The -L0009 denotes English language, the next two switches denote the configuration files and the -f2c:\temp\microdt.log makes the log file output to c:\temp rather than the root of C:.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Note

Be careful if using the response file method of deploying this application and the Installation and Configuration Guide pdf, as the command line specified in the guide is incorrect. The double quotes have been written incorrectly as “ and ” rather than " and this means the setup.exe completely ignores the response file.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Note
There is a runonce registry key installed as part o the vendor's installation, which requires admin priveleges after restart to register some .dll files which appear to have been missed off the initial installation. To get round the requirement for an administrator to log on to every PC SCCM deploys this application, the following vbscript was used:

Set WSHShell = WScript.CreateObject("WScript.Shell")

WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\ATL.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\COMCAT.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\COMCT232.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\COMDLG32.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MFC40.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MFC42.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSCOMCTL.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSSTDFMT.dll""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSVBVM60.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\msxml3.dll""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\msxml4.dll""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\msxml6.dll""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\OLEAUT32.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\OLEPRO32.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\RICHTX32.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\sqaote32.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\THREED32.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\ACTBAR.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\COMCT332.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\COMCTL32.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\GRID32.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSCOMCT2.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSFLXGRD.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\ntsvc.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\TLBINF32.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\VCF15.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\VCFI5.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\smartui.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\Program Files\Common Files\MicroStrategy\REGOBJ.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\Program Files\Common Files\MicroStrategy\BARDES.DLL""", 1, true
WSHShell.Run "regsvr32 /s ""C:\Program Files\Common Files\MicroStrategy\ChartActiveX.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\iGrid250.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\AddFlow4.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\HFlow.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSCAL.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\MSCHRT20.OCX""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\PropertyGrid.ocx""", 1, true
WSHShell.Run "regsvr32 /s ""C:\WINDOWS\system32\WEBPRO32.OCX""", 1, true
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Note

Microstrategy 9.3 - I spent weeks on this damn thing until I finally got it captured and converted into a working MSI using Installshield.  Takes sooooooooooo long to view, build, copy, install etc etc........

Initially the 'Desktop' app would not run, then when it did run it did not show the toolbar.

Ultimately the fix for this was to capture the app after rebooting AND logging on as Admin (because logging on as Admin completes the install) then building the ISM without using Merge Modules. If you use Merge Modules then it breaks the app.

You obviously have to exclude various unwanted stuff from the capture - particularly some CurrentControlSet Services stuff I seem to remember.

krb5.ini was not written properly using INIfile table so install it as a file.

Need to open up permissions for Users on :
HKLM\Software\MicroStrategy
C:\Program Files\MicroStrategy and C:\Program Files\Common Files\MicroStrategy

Had to create Immediate Custom Actions to run BEFORE InstallInitialize to delete various reg entries for HKLM\SOFTWARE\ODBC\ODBCINST.INI\MicroStrategy ODBC Driver etc etc... 
which were left behind by the previous version's uninstall and prevent new version installing.
Make sure these are removed by your uninstall to avoid future grief.

Good luck - it is a bit of a beast!

 

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
It took me ages to find out how to generate a response file because the Installation & Config guide is way to big and very messy (602 pages and 11 chapters with thousands of paragraphs all refering to each other for more info)

So, in a nutshell, the most efficient way to do this killer app:

setup.exe /r /f1"%temp%\my-answer-file.iss"

This generates your answer file, just like you're used to, the classic installshield way (see related links as well). And don't forget to back it up.

Now, when you're done, use the installed Microstrategy to make the response file:

Go to Start --> Programs --> Microstrategy --> Configuration Wizard.

Walk through the wizard. Only 1 config at a time possible. So repeat this step if you have more configurations to make (like multiple project sources for example). At the end you get the option to save this config to a response file, in INI format.

If you have generated more than 1 INI file, copy/paste the contents of the files together into one file and check to make sure there are no conflicting sections in the final response file. (example: mutlipe project sources will all use [Client], so rename the 2nd and 3rd, and so on to [Client1], [Client2], etc...)

The language codes that can be used are:
English 0009
Italian 0010
Portugese 0016
German 0007
Spanish 000A
Japanese 0011
Korean 0012
Chinese 0004
Swedish 001D
French 000C


Hopefully this is all you need. If not, good luck searching the guide!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Command Line
For 9.2.1m (and presumably anything in the 9.2.x range), I was unable to create a response transform using InstallShield AdminStudio Tuner. It would keep complaining that:

"The MicroStrategy Office install cannot be launched. Please install Windows Installer 4.5 or a later version."

To get around this, I just created a new, NON-RESPONSE transform. Within the transform, I could then add our company-specific registry keys move Start Menu items around. I then needed to customise the installed components, and change the WSURL. I did this from the command-line, as follows:

start /w msiexec /i MicroStrategyOffice.msi ALLUSERS=2 TRANSFORMS=MicroStrategyOffice.mst WSURL=http://microstrategy_server_name/MicroStrategyWS/MSTRWS.asmx LP=2 LW=2 REBOOT=ReallySuppress /qn /Liv %TEMP%\MicroStrategyOffice_9.2.1m.log

...Where LP=2 means do NOT install the Add-in for PowerPoint. I added LW=2 to prevent installation into Word. I didn't need to specify anything for Excel, because by leaving it off the command-line, it just installs that component.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Command Line

Installations/setup.exe --ResponseFile=”response.ini” -s  -f1setup.iss

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (3)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

MicroStrategy

Version

9

Questions & Answers (1)

Questions & Answers related to MicroStrategy MicroStrategy

Blogs (0)

Blog posts related to MicroStrategy MicroStrategy

Reviews (0)

Reviews related to MicroStrategy MicroStrategy