You can install SQL with a ini file by running from an elevated command line setup.exe /ConfigurationFile=Yourconfigurationfile.ini below is what I use for my own configuration file
; *************************************************************************** ; ; Created: 2017-01-21 ; Version: 1.0 ; ; Disclaimer: ; This script is provided "AS IS" with no warranties, confers no rights and ; is not supported by the authors. ; ; Author - Kris Gross ; ; ; *************************************************************************** ;SQL Server 2016 Configuration File [OPTIONS] ; Agree to terms IACCEPTSQLSERVERLICENSETERMS="True" ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. ACTION="Install" ; Detailed help for command line argument ENU has not been defined yet. ENU="True" ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. ; UIMODE="Normal" ; Setup will not display any user interface. ;QUIET="True" ; Setup will display progress only, without any user interaction. QUIETSIMPLE="True" ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. UpdateEnabled="True" ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. FEATURES=SQLENGINE,RS,CONN,SSMS,ADV_SSMS ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services. UpdateSource="MU" ; Displays the command line parameters usage HELP="False" ; Specifies that the detailed Setup log should be piped to the console. INDICATEPROGRESS="False" ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. X86="False" ; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed. INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" ; Specify the root installation directory for the WOW64 shared components. ThisdirectoryremainsunchangedafterWOW64sharedcomponentsarealreadyinstalled.INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server" ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS). INSTANCENAME="MSSQLSERVER" ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. INSTANCEID="MSSQLSERVER" ; 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" ERRORREPORTING="False" ;UpdateSOURCE="C:\Setup\SQL2014CU" ; RSInputSettings_RSInstallMode_Description RSINSTALLMODE="DefaultNativeMode" ; 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="True" ; Specify the installation directory. INSTANCEDIR="C:\Program Files\Microsoft SQL Server" ; Agent account name AGTSVCACCOUNT="NT Service\SQLSERVERAGENT" ; Auto-start service after installation. AGTSVCSTARTUPTYPE="Manual" ; CM brick TCP communication port COMMFABRICPORT="0" ; How matrix will use private networks COMMFABRICNETWORKLEVEL="0" ; How inter brick communication will be protected COMMFABRICENCRYPTION="0" ; TCP port used by the CM brick MATRIXCMBRICKCOMMPORT="0" ; 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" ; Account for SQL Server service: Domain\User or system account. SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" ; Windows account(s) to provision as SQL Server system administrators. SQLSYSADMINACCOUNTS="home\Administrator" "Home\Domain Admins" ; Default directory for the Database Engine backup files. ;SQLBACKUPDIR="\\IT-CMMP\F:\SQLBCK" ; Default directory for the Database Engine user databases. SQLUSERDBDIR="E:\SQLDB" ; Default directory for the Database Engine user database logs. SQLUSERDBLOGDIR="L:\SQLLOG" ; Directory for Database Engine TempDB files. SQLTEMPDBDIR="T:\SQLTMP" ; Provision current user as a Database Engine system administrator for SQL Server 2012 Express. ADDCURRENTUSERASSQLADMIN="False" ; Specify 0 to disable or 1 to enable the TCP/IP protocol. TCPENABLED="1" ; Specify 0 to disable or 1 to enable the Named Pipes protocol. NPENABLED="0" ; Startup type for Browser Service. BROWSERSVCSTARTUPTYPE="Disabled" ; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system. ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. RSSVCACCOUNT="Home\SQLReporting" RSSVCPASSWORD="P@ssword1" ; 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"
Office 365 by its self is a fairly easy Application to deploy but it can get complicated when you need to remove other Office products or install different versions of Office 365 based on what was installed on the target device. That all being said I wanted to create a reference for getting all the tools that make office deployments easy and throw in a few tips to solve some more unique issues you may have with deploying Office 365.
1. The first thing you want to do is download the Office Deployment Tool. Once you install the Tool you will find a setup.exe file and a configuration.xml.
2. The configuration file controls what will be installed and what will be downloaded. For example if the download switch is used with the configuration file below then Office 365 ProPlus x32 and VisioPro x32 will be downloaded. If you use that same configuration file with the configure switch then ProPlus x32 and VisioPro x32 will be installed from \\Server\Share with the EULA accepted and only the p…
A few weeks ago, I put out a guide on how to create a Task Sequence for windows 10. This post will build off of that that and will show you how to build a TS that will display a GUI that will allow your technicians to set the computer name, enter a description to be updated to AD, choose what operating system image to install and choose from a list of applications to install. You should try to understand this process but I do have a post on how you can just import my own TS that you can customize HERE.
The first thing you will need to do is download a copy the TS example files, you can get them from HERE. In the zip files, you should have a few folders InstallUpdates, SetADDescription, TSGUI_x64 and Windows10Config copy each of the folders where you keep your SCCM content files. 1. Create a package for the GUI, give the package a name like TS_GUI, for the version type x64, check the box "This package contains source files" and brose for the TSGUI_x64 folder.
Over the past few weeks I have been revisiting how I setup new workstations both with SCCM and manually. There are a few script I put together to configure things like the page file and disable Cortana. These scripts are useful but hard to always keep up to date and if I want to use them in a SCCM TS then I need make a step and package for each script. So I have consolidated these script into the Win10Setup script. The script will still remove built in apps and import a custom start menu config file, Below are the changes I have made to the script. A default list of apps to remove if a txt file of apps is not specifiedSwitch to export your start menu layout to use for deploymentParameters to join a computer to a domain (not usable with SCCM or other deployment automation applications)Switch to disable the Consumer ExperienceSwitch to stop and disable Xbox servicesSwitch to move and set the page file Switch to disable the hibernate power optionSwitch to disable Windows TipsSwitch to re…