Software Deployment

@echo off

::beg verification
wmic product where (name like '%%.Net 3.5 SP1%%') GET NAME|FIND /I ".NET 3.5 SP1" && GOTO INSTALL
GOTO PREQ

:PREQ
"PATH\TO\.NET\INSTALL.EXE" /q /norestart
wmic product where (name like '%%.Net 3.5 SP1%%') GET NAME|FIND /I ".NET 3.5 SP1" && GOTO INSTALL
GOTO error

:INSTALL
"\\PATH_TO_INSTALL_FILES\setup.exe" /ACTION=INSTALL /QUIET /FEATURES=SSMS,ADV_SSMS /HIDECONSOLE
GOTO EOF

:ERROR
ECHO ERROR ISSUE OUT TO FILE HERE>>FILENAME

:EOF

 

We have deployed SQL Server 2008 Enterprise Client Tools using the vendor setup and a custom configuration file (as described here http://msdn.microsoft.com/en-us/library/dd239405(v=SQL.100).aspx). You could explore this option to fit your needs.

Install with configuration file works fine, but having problems running the uninstall.
Any hints on how to set up the uninstall with configuration file?

Uh? SSMS is installed via an MSI so it'll be a standard MSIEXEC command line: MSIEXEC /X [GUID_from_registry]

Oooooooooor...... I have run it directly from CD-media om sccm 2007 server with command-line: Setup.exe /ConfigurationFile=SQL2k8Tools.INI

I have tried to simply change the "ACTION=INSTALL" to "ACTION=UNINSTALL" :p


SQL2k8Tools.ini:

;SQLSERVER2008 Configuration File
[SQLSERVER2008]

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

ACTION="Install"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.

FEATURES=SSMS,ADV_SSMS

; Displays the command line parameters usage

HELP="False"

; Specifies that the detailed Setup log should be piped to the console.

INDICATEPROGRESS="False"

; Setup will not display any user interface.

QUIET="False"

; Setup will display progress only without any user interaction.

QUIETSIMPLE="True"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.

X86="False"

; Specifies the path to the installation media folder where setup.exe is located.

MEDIASOURCE="\\mssccmalv1\sccmsource$\Applications\MSI\Microsoft-SQL-2008-Tools"

; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.

ERRORREPORTING="False"

; Specify the root installation directory for native shared components.

INSTALLSHAREDDIR="c:\Program Files\Microsoft SQL Server"

; Specify the root installation directory for the WOW64 shared components.

INSTALLSHAREDWOWDIR="c:\Program Files (x86)\Microsoft SQL Server"

; Specify the installation directory.

INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.

SQMREPORTING="False"

; Auto-start service after installation.

AGTSVCSTARTUPTYPE="Manual"

; Startup type for Integration Services.

ISSVCSTARTUPTYPE="Automatic"

; Account for Integration Services: Domain\User or system account.

ISSVCACCOUNT="NT AUTHORITY\NetworkService"

; Controls the service startup type setting after the service has been created.

ASSVCSTARTUPTYPE="Automatic"

; The collation to be used by Analysis Services.

ASCOLLATION="Latin1_General_CI_AS"

; The location for the Analysis Services data files.

ASDATADIR="Data"

; The location for the Analysis Services log files.

ASLOGDIR="Log"

; The location for the Analysis Services backup files.

ASBACKUPDIR="Backup"

; The location for the Analysis Services temporary files.

ASTEMPDIR="Temp"

; The location for the Analysis Services configuration files.

ASCONFIGDIR="Config"

; Specifies whether or not the MSOLAP provider is allowed to run in process.

ASPROVIDERMSOLAP="1"

; Startup type for the SQL Server service.

SQLSVCSTARTUPTYPE="Automatic"

; Level to enable FILESTREAM feature at (0, 1, 2 or 3).

FILESTREAMLEVEL="0"

; Set to "1" to enable RANU for SQL Server Express.

ENABLERANU="False"

; Specifies a Windows collation or an SQL collation to use for the Database Engine.

SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.

ADDCURRENTUSERASSQLADMIN="False"

; Specify 0 to disable or 1 to enable the TCP/IP protocol.

TCPENABLED="0"

; Specify 0 to disable or 1 to enable the Named Pipes protocol.

NPENABLED="0"

; Startup type for Browser Service.

BROWSERSVCSTARTUPTYPE="Disabled"

; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled

RSSVCSTARTUPTYPE="Automatic"

; Specifies which mode report server is installed in.
; Default value: “FilesOnly”

RSINSTALLMODE="FilesOnlyMode"

Have you thrown caution to the wind and actually looked at the UninstallString in the registry?

Do you actually know the answer to my problem or are you trying to make me think by myself?!

Sooner or later the answer will fall into my lap, in the meantime it is to hot for demonstrating so I'll just have a coffee in the cafe.

That doesn't answer my question.

Browse to HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall. From there, search for the text "SQL". One of the GUIDs wil contain installation data about the product. in that branch will be a value "UninstallString".

Spoon-feeding ends.

The problem with Spoon-feeding is the aim.

If you read the INI-file you would see that I installed more than ONE feature, so running one (1) msiexec /x -command won't cut it.

There have to be a solution by running the configuration INI-file.

Oh no! You have the grand total of TWO features so, worst comes to worst, you have to run TWO MSIEXEC commands. Disaster.

Have you checked to see whether those features are contained within the same MSI? Thought not.

Ok, here is the solution (No thanks to backround noise and spoon-feeding of fish and chips)

Command line: Setup.exe /ConfigurationFile=SQL2k8Tools-uninst.INI
(name your INI-file with whatever you like, make sure it is on the SCCM-server with the package)

MEDIASOURCE in the INI-file is of course where your package is on the SCCM server.

SQL2k8Tools-uninst.INI

;SQLSERVER2008 Configuration File
[SQLSERVER2008]

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

ACTION="UNINSTALL"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.

FEATURES=SSMS,ADV_SSMS

; Displays the command line parameters usage

HELP="False"

; Specifies that the detailed Setup log should be piped to the console.

INDICATEPROGRESS="False"

; Setup will not display any user interface.

QUIET="False"

; Setup will display progress only without any user interaction.

QUIETSIMPLE="True"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.

X86="False"

; Specifies the path to the installation media folder where setup.exe is located.

MEDIASOURCE="\\mssccmalv1\sccmsource$\Applications\MSI\Microsoft-SQL-2008-Tools"



Now I think I'll go back to eating Souvlaki.

Oops! http://msdn.microsoft.com/en-us/library/ms144259%28v=SQL.100%29.aspx#Uninstall

VBScab the Merciless reigns supreme!!! [:)] [8D]

Sorry VBScab, couldn't resist [:)]

VBScab please don't scare people away [:)] j/k

I am actually starting to work on a SQL 2008 management tools. Which kind of sucks because I did a normal install first to make my notes and noticed that it requires Windows Installer 4.5 (most of our machines are at 3.5) and .Net Framework 3.5 SP1 (most do not have 3.5) so now I have to really sit down and think about putting some logic like if windows installer is not 4.5 then install and same for Dot Net.

I am just starting out with packaging and have some batch file/command line skill (more than my co-workers but not enough to make my life easier)

If anyone has gone down this road (install SQL 2008 tool, along with Windows installer and framework 3.5) assistance would be appreciated

Oh, I got the silent install working. All I need is to now add a switch to make a log of the install/removal. The config file seems This is the command I used

To Install
\\PATH_TO_INSTALL_FILES\setup.exe" /ACTION=INSTALL /QUIET /FEATURES=SSMS,ADV_SSMS /HIDECONSOLE

To Uninstall
\\PATH_TO_INSTALL_FILES\setup.exe" /ACTION=UNINSTALL /QUIET /FEATURES=SSMS,ADV_SSMS /HIDECONSOLE


The /HIDECONSOLE removes the command prompt window from popping up. I removed that command and used the DOS window as a timer to see how log it takes for the install.


What would be great now is go create a batch file with logic (a bit harder for me) what checks if Windows Installer and .Net 3.5 SP1 is installed and if not install