This is the legacy (meaning old) way of installing updates, and is referenced to as slipstreaming in the SQL documentation. Now, when you verified it works, go to Step 2 – Prepare the unattended file for the SQL Setup engine.Running the SQL Setup with the /UpdateSource switch. Once the wizard starts, continue until you see the Product Updates page, and then click Cancel. To verify that the setup process can find the CU8 update, run SQL Setup (setup.exe) with the /Action=Install /UpdateSource="D:\Setup\SQL Server 2012 SP1 CU8" switch.Download CU8 for SQL Server 2012 SP1 ( ), and extract the file you downloaded (*_zip.exe), into the D:\Setup\SQL Server 2012 SP1 CU8 folder.Having the SQL setup engine install the CU8 update as is during setup is quite elegant. In this guide, I have my SQL Server 2012 with SP1 setup files in the D:\Setup\SQL Server 2012 SP1 folder. Option 2 – You can extract the CU8 bits to a folder, and use the CUSOURCE option (legacy, but still supported).Option 1 – You can use the new UpdateSource option to have the SQL setup install the CU8 update as is.Preparing the SQL setup files can be done in two ways: Prepare the unattended file for the SQL Setup engine.In the scenario the SQL Server setup is intended for ConfigMgr 2012 R2 but you use the same technique for all types of SQL Installs. Either way, both versions supports installing updates as part of the setup, and here follows the step to install SQL Server 2012 SP1 with CU8. It could be the SQL Server Express edition because you are using the Database for MDT 2013 Lite Touch, or the full SQL Server to support a System Center 2012 R2 product. Every once in a while you need to install SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |