The MSI Utility for Microsoft Application Virtualization is a new tool designed to extend virtual application deployment in certain key scenarios. In cases where a computer running Microsoft System Center Virtual Application Server is not available, the MSI Utility allows delivery of sequenced applications directly to Microsoft SoftGrid Application Virtualization for Desktops and Microsoft SoftGrid Application Virtualization for Terminal Services.

The MSI Utility enables the distribution of virtual applications without streaming. Instead, it uses Windows Installer to load and configure virtual applications. By leveraging this standard format, the MSI Utility achieves Microsoft Systems Management Server 2003 and Microsoft System Center Configuration Manager 2007 platform version-agnostic distribution of virtual applications if supported by organizational Electronic Software Distribution (ESD) systems. As such, the MSI Utility is a stepping stone to the richer deployment options available in Microsoft System Center Virtual Application Server 4.5.

The MSI Utility extends application deployment methods to a broad range of ESD systems, including Systems Management Server 2003 and System Center Configuration Manager, as well as other methods such as network shares, removable disks, and memory keys. By using an ESD system to deploy virtualized application packages to disconnected SoftGrid Application Virtualization Desktop Clients, users can run virtualized applications without connecting to a computer running Microsoft System Center Virtual Application Server.

Download at www.microsoft.com/downloads/

A nice tool for Softgrid SFT-files in a new version.

You wanted to see what’s inside SoftGrid package (SFT) file without using SoftGrid Sequencer?
By using SFT Explorer now you can, it will show all that’s inside your SFT package. Files, folders, virtual registry, virtual services … all! And you can optionally export selected content out of the package, to examine files more closely or to migrate virtual registry settings to another package by importing exported reg-file.

With Virtualized System View™, you can even simulate how that package would look like on your local machine when run with SoftGrid SystemGuard environment up, enabling new type of troubleshooting possibilities when you can clearly see what is virtualized against your local system and in what manner.

With filtering you can quickly find certain filetypes, individual files or to see what files constitute the launch-data for package (files belonging to Feature Block 1 section of file).

By using new Fast package loading -option, even extremely large packages are snap to open with SFT Explorer (with only loss of ability to see individual blocks per files).

Download at: www.virtualapp.net/sft-explorer.html

Agent – (MOMAgent.msi)
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP= MANAGEMENT_SERVER_DNS= ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER= ACTIONSDOMAIN= ACTIONSPASSWORD=

Typical – (MOM.msi)
msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMTypical_install.log ADDLOCAL=ALL USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP= MANAGEMENT_SERVER_DNS= SQLSVR_INSTANCE= ADMIN_ROLE_GROUP=”DomainName/Account” ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER= ACTIONSDOMAIN= ACTIONSPASSWORD= SDK_USE_COMPUTER_ACCOUNT=0 SDK_ACCOUNT= SDK_DOMAIN= SDK_PASSWORD=

Database –(MOM.msi)
msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMDB_install.log ADDLOCAL=MOMDB USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP= SQLSVR_INSTANCE= DB_SIZE=500 ADMIN_ROLE_GROUP= DATA_DIR= LOG_DIR=

Server –(MOM.msi)
msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMServer_install.log ADDLOCAL=MOMServer USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP= MOM_DB_SERVER= ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER= ACTIONSDOMAIN= ACTIONSPASSWORD= SDK_USE_COMPUTER_ACCOUNT=0 SDK_ACCOUNT= SDK_DOMAIN= SDK_PASSWORD=

UI –(MOM.msi)
msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMUI_install.log ADDLOCAL=MOMUI USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP= ROOT_MANAGEMENT_SERVER_DNS=

WebConsole (MOM.msi)
msiexec.exe /i \\path\Directory\MOM.msi /qn /l*v \logs\MOMUI_install.log ADDLOCAL=MOMWebConsole WEB_CONSOLE_AUTH_TYPE=0 ROOT_MANAGEMENT_SERVER_DNS=
( ’0′ is windows auth and ’1′ is Forms auth)

Data Warehouse- (Reporting2007.msi)
msiexec.exe /i \\path\Directory\Reporting2007.msi /qn /l*v “D:\LOGS\REPORTING_INSTALL.LOG” ADDLOCAL=”MOMREPORTINGDB” SQLSVR_INSTANCE=”” MOMREPORTINGDBNAME=”SCOMDW” DB_SIZE=”1000″

Reporting Server (Reporting2007.msi)
msiexec.exe /i \\path\Directory\Reporting2007.msi /qn /l*v “D:\LOGS\REPORTING_INSTALL.LOG” ADDLOCAL=”MOMREPORTING” SQLSVR_INSTANCE=”” MOMREPORTINGDBNAME=”SCOMDW” MGSERVER= PREREQ_COMPLETED=”1″ REPORT_SERVER_FULL_HTTP_PATH=”http://%COMPUTERNAME%:80/ReportServer$INSTANCE1″ DATAREADER_USER= DATAREADER_PASSWORD= DATAREADER_DOMAIN= DBWRITEACTIONSUSER= DBWRITEACTIONSPASSWORD= DBWRITEACTIONSDOMAIN=

Gateway Server (MOMGateway.msi)
msiexec /i \\path\Directory\MOMGateway.msi /qn /l*v D:\GATEWAY_SERVER_INSTALL_1.LOG ADDLOCAL=MOMGateway,MOMNonRootServer SECURE_PORT=5723 MANAGEMENT_GROUP=MyConfigGroup MANAGEMENT_SERVER_DNS= IS_ROOT_HEALTH_SERVER=0 ROOT_MANAGEMENT_SERVER_AD= ROOT_MANAGEMENT_SERVER_DNS= ROOT_MANAGEMENT_SERVER_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER= ACTIONSDOMAIN= ACTIONSPASSWORD=

Audit Collection Server (AdtSetup.exe)
The cmd line you will use would look like this:\\PATH\Directory\AdtSetup.exe /i /s /p:ACSInstallParameters.xml
You will need to specify ACSInstallParameters.xml while passing the command line you will configure all your setting in the XML file before passing it. The XML file is attached.

For ‘/i’ is for ‘install’, ‘/s’ is for ‘silent’, and ‘/p’ is for parameter (file)…

These are the command line parameter to upgrade from OpsMgr 2007 RTM to SP1 RC. Users must upgrade the RMS first which will remotely upgrade the DB. When you upgrade the Reporting Server setup will remotely upgrade the Data Warehouse as well. In order to upgrade the RMS, MS or UI you will need to run step 1 and then step 2 of the command line.

SP1RC Upgrade of RMS, MS and UI: Step 1
msiexec /p MOM2007QFEPreSP1.msp REINSTALLMODE=omus REINSTALL=ALL /qn /l*v D:\logs\QFERollup.log

SP1 RC Upgrade of RMS, MS and UI: Step 2 (DB gets upgraded automatically)
msiexec /p MOM2007SP1.msp SP1UPGRADE=1 REINSTALLMODE=omus REINSTALL=ALL /qn /l*v D:\logs\SP1Update.log

SP1 RC Upgrade of Gateway Server
msiexec /i MOMGateway.msi SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL /qn /l*v D:\logs\GatewayUpdate.log

SP1 RC Upgrade of Reporting (DW gets upgraded automatically)
msiexec /i Reporting2007.msi SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL /qn /l*v D:\logs\ReportingUpdate.log

SP1 RC Upgrade of Agent
msiexec /i MOMAgent.msi SP1UPGRADE=1 SET_ACTIONS_ACCOUNT=0 REINSTALLMODE=vomus REINSTALL=ALL /qn /l*v D:\logs\AgentUpdate.log

SP1 RC Upgrade of Audit Collection
msiexec /i AdtServer.msi ADDLOCAL=ALL REINSTALLMODE=vamus REINSTALL=ALL /qn /l*v D:\logs\ACSUpdate.log