Sequencing SQL Server Management Studio 2014

28 Shares

Sequencing SQL Server Management Studio 2014 with App-V 5.x normally throws the error “Invalid license data. Reinstall is required” at lauch. This error is not coming from Management Studio itself, but from the prereq Microsoft Visual Studio 2010 (isolated) version which is installed as part of the application.

Sequencing SQL Management Studio 2014 01

Stuff like Visual C++ and Visual Studio should (if possible) be installed in the base image to keep the App-V packages size down. Rory Monaghan has already written an App-V Recipe: SQL Management Studio 2012, but it’s rather complex. Let me show you a very simple way to sequence SQL Server Management Studio 2014.

By now you probably now that I love automation, and my Powershell scripts below are extremely fast and flexible to customize. When I’m doing testing I always use Amazon because the downloads normally take only 1 minute compared to 30 minutes in my home lab. The VM’s even stop and start on demand as explain in my post Automatically Start and Stop Amazon VMs.

Before Sequencing

Run the following two Powershell scripts on the sequencing machine to download and install Microsoft Visual Studio 2010 with Service Pack 1.

Sequencing SQL Management Studio 2014 02

Sequencing SQL Management Studio 2014 03

Now since the prereqs are already installed, the sequencer won’t capture those and keep the package at a nice 226 MB in size.

Configure the Sequencer

Download Microsoft SQL Server Express 2014.

Run the SQLEXPRWT_x64_ENU.exe to extract files. Close the setup and restart.

Sequencing SQL Management Studio 2014 04

Download and load the App-V 5 Sequencer Template from Aaron Parker.

Exclusions

Add the following directory exclusion to the sequencer (VRF):

  • [{Profile}]
  • [{Common AppData}]\Microsoft\RAC
  • [{UserProfiles}]
  • [{AppVPackageDrive}]\Source

Sequence with App-V

The is sequencing is straight forward from here.

Sequencing SQL Management Studio 2014 05

Select features as shown below.

Sequencing SQL Management Studio 2014 06

Select to customize the package so you can delete unwanted icons.

Sequencing SQL Management Studio 2014 07

Sequencing SQL Management Studio 2014 08

Sequencing SQL Management Studio 2014 09

Now the final part is to make sure Microsoft Visual Studio 2010 with Service Pack 1 is installed on the clients. If you’re using Citrix Lifecycle Management you can use the script as is.

With other OSD tools you just need to change the path to the installation media. There’s tons of examples with Microsoft Deployment Toolkit here on the blog.

Sequencing SQL Management Studio 2014 11

Sequencing SQL Management Studio 2014 10

28 Shares

20 Responses to Sequencing SQL Server Management Studio 2014

  1. Wish there was a way to get around the 1.2 Gb install of VSIsoShell 2010 on the client.

  2. I used this recipe for sequencing SSMS 2012. Is worked fine. But the compoment “SQL Server Object Explorer is missing” on my APP-V.
    Do you know how to fix it ?

    Thank You

  3. This worked for me for SSMS 2014 but now we also need SSMS 2012 to do some DBs not upgraded yet. When I follow the same steps I get the error ‘Invalid License data. Reinstall is required’. Which is the same error I was getting before I found this article.
    To resolve for 2014 I applied your two Powershell scripts to install MS Visual Studio 2010 (Isolated), .Net Framework 4 Multi-Targeting Pack, MS Visual C++ 2010 x86 runtime – 10.0.30319, MS SQL Server 2008 R2 Mgmt Objects, MS SQL Server System CLR Types and finally MS Help Viewer 1.0.
    If we already have a current .NET version on our images can this be the culprit or is there another recipe to follow other than Rorymon’s?
    Any help is appreciated.

  4. Followed the steps above on Server 2008 r2 and I am continually getting error message when attempting to launch “SQL Server 2014 Configuration Manager”:
    “Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
    Invalid namespace”
    Anyone else experience this and/or have a workable solution?

      • Thanks Trond. Our company is looking for an App-V solution for this product. We are governed to only one virtual solution. Have you or anyone else successfully used “SQL Server 2014 Configuration Manager” with their App-V package?

  5. Looks like the VS 2010 components are for SSMS 2012. SSMS 2014 (SSMS-Setup-ENU) appears to require VS 2015 components.

    May have changed with a newer release of 2014.

Leave a reply