1. SQL SERVER DEPLOYMENT & MANAGEMENT WITH PSADK, SCCM & EM

2. DAVID KOENIG  Product Manager for SCCM Addon‘s @ Matrix42  Blog: https://crankdesk.wordpress.com | Twitter: @davidkoenig09https://crankdesk.wordpress.com  Founder of SCUG Rhein/Main & SCUG Munich  Likes: My Family, Bouldern, Travelling, Whiskey, Music > 90db

3. START WITH WHY 1.For automated testing, my team needed an automated SQL Server installation 2.I didn‘t want to click through the wizard every time i install SQL Server for a customer 3.An installation procedure which let customize everything as input parameter could be useful for an integration in a client-management solution 4.I thought it could be a cool solution for the community and could show how to build bridges between Client- and Servermanagement 5.Get rich ;-) !!! WHY I STARTED THE PROJECT

4. THEN EXPLAIN YOUR IDEA 1.Reading the technet article about automating the installation of SQL Server  https://msdn.microsoft.com/en-us/library/ms144259.aspx https://msdn.microsoft.com/en-us/library/ms144259.aspx 2.Use Powershell (Powershell Appdeployment Toolkit/ PSADK) to build the cmdline parameters 3.Defined everything as Powershell input parameter to be flexible 4.Create a presentation THE MASTERPLAN

5. WHAT I HAVE DONE  Feature Management with switch parameter  SQLEngine, Replication, Fulltext, Backward Comp., Books Online, Connectivity, Basic/Advanced Tools  Update Installation during Setup  Instance Management  Detect existing Instances during Installation / Uninstallation  Switch to enable SQL Security THE FEATURES OF THE SCRIPT (FEATURES AND DATABASE ENGINE)

6. WHAT I HAVE DONE  Check given collation against delivered csv file  Auto Fallback for Sysadmins to Local Account in case of no value or SYSTEM  Modify account settings and start-behavior of Agent, Service and Browser  Modify path settings for Instance, Data, Backup, TempDB, TempDBLog, UserDB and UserDBLog THE FEATURES OF THE SCRIPT (SETTINGS)

7. WHAT I HAVE DONE  Advanced logging (thanks to PSADK)  Auto-Install of.NET Framework 3.5  Advanced error handling (Example: If component is already installed, script will finish with „success“  Register every Installation to registry THE FEATURES OF THE SCRIPT (SEVERAL ADDITIONAL OPTIONS)

8. WHAT I HAVE DONE  Windows Server 2012 R2  Windows 10 Enterprise  SQL Server 2014  SQL Server 2016 TESTED ON... / TESTED WITH...

9. WHAT I HAVE DONE # Installation of SQL Server with windows authentication and use of locally logged in user as administrator Deploy-Application.exe -DeploymentType Install -FeatureSQL -InstanceName "Test01a„ # Simple installation of SQL Server with SQL Server Security Mode and defined Sysadmin account Deploy-Application.exe -DeploymentType Install -FeatureSQL -InstanceName "Test02b" - SqlSecurityMode -SAPassword "Coffee2Go" -SysAdmins "perfectbeer\app_sql_admins„ # Simple installation of SQL Server with TCP enabled, defined Sysadmin account and service autostart Deploy-Application.exe -DeploymentType Install -FeatureSQL -InstanceName "Test03c" -TCP -Collation SQL_Latin1_General_CP1_CI_AS -ServiceStartType Automatic EXAMPLES / HOW TO USE

10. How the script is working Integration in SCCM Optional: Improve functionality with „Enterprise Manager for SCCM“