Technical

Install Microsoft SQL on Linux – Ubuntu Server

I recently had the pleasure of installing Microsoft SQL Server on Linux – Ubuntu Server. This was a very straight-forward installed and just works. The following steps are what were taken to install and configure this server.

My Setup:

  • Ubuntu 17.10 Server – VMware Template
  • Network Connectivity
  • SQL Server Management Studio 17 – Testing connectivity to SQL Server

Prerequisites:

  • Ubuntu Linux Server – Memory: 3.25, Disk Space: 6GB, CPU (x64): 2 Cores
  • Internet Access – Offline Installs are also possible
  • Root or SU Access
  • Time – 5-6 Minutes

Steps:

  1. Log into Ubuntu Linux server via console or SSH (Preferred), su into root
  2. We need to import the repository GPG Keys by first downloading and adding it with he following command: curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add –
  3. Next we register the repository by entering: add-apt-repository “$(curl https://packages.microsoft.com/config/ubuntu/16.04/mssql-server-2017.list)”
  4. Next we need to upload the repository list and install SQL with the following commands: apt update | apt install mssql-server -y
  5. After the SQL Server package has completed installing.  You will be instructed to run mssql-config setup to setup the SQL Server version you will be installing, in addition to password credentials.  This is done by issue the following command: /opt/mssql/bin/mssql-conf setup
  6. Optional – Open your firewall if enabled to allow for SQL’s TCP/1433 from remote hosts.
  7. Test connecting to your newly install SQL Server via SSMS.
  8. Done!

Screenshot:

Video:

Tech Short: Configure WDS Server

You have installed your WDS Server Role and now its time to configure.  I hope my steps below help you.

Requirements

  • Installed WDS Role
  • Administrative Rights
  • Installation Media

 

WDS Server Configuration:

  1. On the Server Manager tool, click Tools and then click Windows Deployment Services.
  2. On the Windows Deployment Services console, expand Servers.
  3. Right-click your WDS server name and select Configure Server.
  4. Navigate to the Install Options page, choosing Integrated with Active Directory or Standalone server button is selected and then click Next.
  5. On the Remote Installation Folder Location page, select a folder or click Next to accept the default value. This folder will hold the WDS images.
  6. On the PXE Server Initial Settings page exists there options: Select the Respond to all client computers (known and unknown) then click Next.
  7. On the Operation Complete page, you have the option to Add images to the server now by selecting the check box and click Finish.  This will guide you through the initial image setup.

 

Video:

Done!

 

Tech Short: How-To WDS Server Role – Server 2016

 

Background:

Windows Deployment Services (WDS) is a service role that allows you to deploy operating systems to the PXE supported clients without the need of physical media.

Requirements:

  • Windows Server 2016 Server Install
  • Administrative rights on Server

Install of Windows Deployment Service

  1. On the Server Manager tool, click Manage, and then click Add Roles and Features.
  2. Accept the default selections and click Next until you get the Select server roles page.
  3. On the Select server roles page, as shown in the following figure, select the Windows Deployment Services check box.
  4. On the Add Roles and Features Wizard window, click Add Features.
  5. Accept the default selections and click Next, until you get the Confirm installation selections page.
  6. Click Install to complete the installation.

Video:

 

Done – Next up is to configure WDS

 

 

 

Tech Short: How To Change The MTU – Server 2016

 

Troubleshooting an application issues which could possibly be network related.  I found myself needing to make some adjustment to the maximum transmission unit (MTU) setting of my server.  As such what better time to post a quick technical short on how to go about doing this.

 

How To Change The MTU – Windows Server 2016

Requirements:

  • Logon and Administrator permission on Server
  • Network Connectivity
  • Time to reboot

 

Procedure:

From the desktop of your Windows Server 2016 server open an Administrative command prompt by Right-Clicking on the start button and select  – Command Prompt (Admin).

Once in the command prompt you we be using netsh to determine the IDX of the installed interface devices. this is performed by using the following command:  netsh interface ipv4 show interfaces

Take note of the IDX interface that you would like to change the MTU on as this is what we need to specify when changing the MTU settings.

Using netsh again you issue the following command: netsh interface ipv4 set subinterface “number-goes-here” mtu=1400 store=persistent

Please note that the subinerface will be the IDX number from the first netsh command and that the MTU setting is a value less than the original 1500.

Now you can reboot to have the changes take effect.  I have also noticed the disabling the interface and  re-enabling also works.

 

 

Windows 10 Cumulative Update KB4041676 Fixed

On Tuesday, October 10, 2017 Microsoft released KB4041676 as an update that includes quality improvements. What many started to notice was that it was accompanied by an issue included systems unable to boot and those cause in boot-loops.

 

Jump to quick fix: for those of you who already installed this

In the cmd line of the advanced repair options type:

Dism /Image:C:\ /Get-Packages (could be any drive, had it on D, F, and E.)
Dism /Image:C:\ /Remove-Package /PackageName:package_ for_###
(no space between package_ and for)

Remove every update that’s pending – There are 3 updates that are causing the issue they are:

  • Rollupfix_wrapper~31bf3856ad364e35~amd64~14393.1770.1.6
  • Rollupfix~31bf3856ad364e35~amd64~14393.1770.1.6
  • Rollupfix~31bf3856ad364e35~amd64~14393.1715. 1.10

 

Microsoft explained in a support article that this has been caused by what it describes as a “publishing issue,”

““We have corrected the publishing issue as of the afternoon of October 10th and have validated the cumulative security updates. We recommend all customers take these cumulative security updates,”.

 

At the office and in the lab:

I have taken steps to flush the update from my WSUS environments as a precaution and to allow for the corrected package to be downloaded.

 

ref:

https://support.microsoft.com/en-ca/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-o