Install Net 3.5 Framework on Windows Server 2012 or 2016 without DVD

You can configure server to use Windows Update as a source for for optional components installation. And then install .NET 3.5 through the Add Roles and Features Wizard.

This worked for me. Windows has to download the .NET 3.5 installation files, but the server is configured not to use Windows Update (common for managed servers), but WSUS.

1. Start the Local Group Policy Editor or Group Policy Management Console (WIN+R and type gpedit.msc).
2. Expand Computer Configuration, expand Administrative Templates, and then select System.
3. Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled.
4. Select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) checkbox.

Now start installing .NET Framework 3.5 through the Add Roles and Features Wizard and get it installed successfully.

Apply Patch to 2 or 3 Node Cluster

Implementation

Before patching change starts you need to perform below steps :

  1. Log Onto Nodes N1,N2 and N3 in the cluster

Connect to the sql Instance and execute below T-SQL script to check the current patch level:

SELECT

SERVERPROPERTY(‘Edition’) AS ‘Edition’,

SERVERPROPERTY(‘ProductVersion’) AS ‘ProductVersion’,

SERVERPROPERTY(‘ProductLevel’) AS ‘ProductLevel’,

SERVERPROPERTY(‘ResourceLastUpdateDateTime’) AS ‘ResourceLastUpdateDateTime’,

SERVERPROPERTY(‘ResourceVersion’) AS ‘ResourceVersion’

2. Check for Missing msi and msp files . Please check below link how to find out missing files and fix it

https://support.microsoft.com/en-in/help/969052/how-to-restore-the-missing-windows-installer-cache-files-and-resolve-p

OR

You can use MSI-Moksha.exe  tool  to find out missing msi and msp files ,also you can repair the missing files by using this tool itself .

  1. If there are any – repair the missing files.
  2. And Make sure that above steps are completed successfully.
  3. During maintenance Window perform below steps :
  • Put Node 1 N1 into maintenance mode
  • Log into passive node xxx
  • Failover SQL instances, if any, off of Node1 to any other node
  • Run the patch executable
  • Make sure all rules have passed. If not, take required actions to fix.
  • Accept the license term on next page and proceed
  • Select all SQL server features that needs to be Upgraded
  • Files in use will be checked on next page – hit next when checking complete
  • Verify the list of features that will be upgraded and hit Upgrade
  • Wait until it completes and make sure it’s successful. See the Summary. txt error log located at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log and check the detail logs for troubleshooting if failure happens
  1. Reboot Node 1 if required
  2. Log on to Node 2 N2 and failover all instances that exist on this node to other nodes
  3. Repeat steps 1- 9 for each Node- N2 and N3
  4. Do manual failover to move instances to preferred node. OR if you have any automation to move instance to preferred node RUN that.
  5. Once above steps are completed successfully you can remove the Nodes from MM(Maintenance Mode).
  1. Validate in the Monitoring Tool ( if you have any ) to make sure the corresponding Patched Instances are being correctly monitored.

Once above all steps are completed successfully Connect to SQL Instances that were patched and run below SQL to see SQL Version is at correct level:

SELECT

SERVERPROPERTY(‘Edition’) AS ‘Edition’,

SERVERPROPERTY(‘ProductVersion’) AS ‘ProductVersion’,

SERVERPROPERTY(‘ProductLevel’) AS ‘ProductLevel’,

SERVERPROPERTY(‘ResourceLastUpdateDateTime’) AS ‘ResourceLastUpdateDateTime’,

SERVERPROPERTY(‘ResourceVersion’) AS ‘ResourceVersion’

Back-Out Plan :

If any issues with Patching perform below steps

Log onto all nodes of the cluster

  • On each node do the following
  • Open Add and Remove Programs from control panel
  • Check the Show Updates box on add remove programs window
  • Go down the page and locate (Sp info), check the box to mark it and hit remove
  • Follow the wizard until the feature is completely removed
  • Reboot if required
  • Do manual failover to move instances to preferred node. OR if you have any automation to move instance to preferred node RUN that.

Patching for Standalone SQL Instance

Implementation

Before patching change starts you need to perform below steps

  1. Log Onto the Standalone SQL Windows box.

Connect to the sql Instance and execute below T-SQL script to check the current patch level:

SELECT

SERVERPROPERTY(‘Edition’) AS ‘Edition’,

SERVERPROPERTY(‘ProductVersion’) AS ‘ProductVersion’,

SERVERPROPERTY(‘ProductLevel’) AS ‘ProductLevel’,

SERVERPROPERTY(‘ResourceLastUpdateDateTime’) AS ‘ResourceLastUpdateDateTime’,

SERVERPROPERTY(‘ResourceVersion’) AS ‘ResourceVersion’

2. Now check for Missing msi and msp files . Please check below link how to find out missing files and fix it

https://support.microsoft.com/en-in/help/969052/how-to-restore-the-missing-windows-installer-cache-files-and-resolve-p

                                                                                  OR

You can use MSI-Moksha.exe  tool  to find out missing msi and msp files ,also you can repair the missing files by using this tool itself .

  1. If there are any – repair the missing files.
  2. And Make sure that above steps are completed successfully.
  3. During maintenance Window perform below steps :
  • Put SQL windows box into maintenance mode
  • Run the patch executable
  • Make sure all rules have passed. If not, take required action to fix.
  • Accept the license term on next page and proceed
  • Select all SQL server features that needs to be Upgraded
  • Files in use will be checked on next page – hit next when checking complete
  • Verify the list of features that will be upgraded and hit Upgrade
  •     Wait until it completes and make sure it’s successful. See the Summary. txt error log located at C:\Program     Files\Microsoft SQL Server\100\Setup Bootstrap\Log and check the detail logs for troubleshooting if failure   happens
  1. Reboot SQL window box if required
  2. Perform SQL Health check
  3. Once above steps are completed successfully you can remove the SQL Box from MM(Maintenance Mode).
  4.  Validate in the Monitoring Tool ( if you have any ) to make sure the corresponding Patched Instances are being correctly monitored.

Once above all steps are completed successfully Connect to SQL Instances that were patched and run below SQL to see SQL Version is at correct level:

SELECT

SERVERPROPERTY(‘Edition’) AS ‘Edition’,

SERVERPROPERTY(‘ProductVersion’) AS ‘ProductVersion’,

SERVERPROPERTY(‘ProductLevel’) AS ‘ProductLevel’,

SERVERPROPERTY(‘ResourceLastUpdateDateTime’) AS ‘ResourceLastUpdateDateTime’,

SERVERPROPERTY(‘ResourceVersion’) AS ‘ResourceVersion’

Back-Out Plan :

If any issues with Patching perform below steps

Log onto Standalone SQL windows box

  • Open Add and Remove Programs from control panel
  • Check the Show Updates box on add remove programs window
  • Go down the page and locate (Sp info), check the box to mark it and hit remove
  • Follow the wizard until the feature is completely removed
  • Reboot if required
  • Perform SQL Health check.