2 minutes reading time (390 words)

SQL Server Management Studio 18.5 (SSMS) App-V Recipe

App_V_Block_2020

The old recipe for SSMS 17.x was a nice success for me with about 1000 hits. Especially the comments were enlightening. The licensing problem could be solved with a simple registration key. With 18.5 there is nothing more to do here.

Comment 1

Extracting components is no longer necessary. The package runs perfectly on all platforms. I always wanted to add to this point and also thank you again for all the great comments. The old App-V recipe for does not work anymore for some time now (https://www.andreasnick.com/91-app-v-5-recipe-for-sql-server-management-studio-2016-or-ssms-17-x.html).

For a later version we have not found a solution even on the fast one. But now we finally have a working App-V recipe again. The reason for this was again a comment in the old article:

Comment 2

Again many thanks to LCBakkie!

Now we have tested it thoroughly. The package works with an alternative path (PVAD). Unfortunately the application as App-V package, which was created on a 1909 sequencer, is only executable on older systems. So I rebuilt the whole thing on a 8.1 sequencer with App-V 5.1. Then the package works universally. Here are some instructions. If you try it with a new sequencer then it works best with Windows 10 2004 or 20H1.

Recipe SSMS 18.5

  1. i use here a Windows 8.1 sequencer with App-V 5.1 HF 10. You are welcome to use a newer system. I was successful with this.
  2. reset the snapshot an the Sequencer 
  3. Install dotNet 4.7.2 ( LINK )
  4. Copy SSMS 18.5 to the sequencer (LINK)
  5. start the sequencer for PVAD with -EnablePVADControl
  6. optional: deactivate the acquisition of Visual C++ runtime components
  7. select "C:\SSMS\" as PVAD path. Otherwise there seem to be problems if the file paths become too long.
  8. install the application to "c:\SSMS" instead of "C:\Program Files (x86)\Microsoft SQL Server Management Studio 18
    InputBox
  9. do not start or configure the application after installation switch to edit mode
  10. under GAC_MSIL in the folders ending with ".resources" delete all items (folders) with "zh-HANS" (I know I should build a template for this)

[{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.resources\v4.0_15.0.0.0_zh-HANS_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.Common.resources\v4.0_15.0.0.0_zh-HANS_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.Common.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.VstaTemplate.resources\v4.0_15.0.0.0_zh-HANS_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.VstaTemplate.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.ProjectRetargetService.resources\v4.0_15.0.0.0_zh-HANS_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.ProjectRetargetService.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Utilities.ProjectRetargetService.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a [{Windows}]\Microsoft.NET\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Common.resources\v4.0_15.0.0.0_zh-HANT_b03f5f7f11d50a3a

11. delete all MSI files under c:\Windows\Installer (optional)
12. delete the Package Cache folder under "[{Common AppData}]\Package Cache This makes the package much smaller
13. save now Note: The first start always takes a little longer.

If you like, you can experiment with the first start of the application

 

 

Starting MSIX and AppX packages with PowerShell fr...
Recipe: Virtualize Edge with App-V

Related Posts

 

Comments 10

Guest - Mike on Friday, 30 October 2020 03:28

Hi Andreas,

Thank you for the offer, but that won't be necessary.

We had just built a new W2016 server and neglected to manually update the App-V version.
Very silly oversight on our part!
We were still running on version 10.0.15063.0
We updated to 10.1.17763.1 (ADK 1809), but the same issue occurred.
We then attempted to sequence it again, by enabling PVAD. This time it works!

Thank you very much for your assistance with this. It's always the simple things that get missed!

MSIX does sound interesting though, thanks for the tip! We will look into this and see how it compares to App-V.

Hi Andreas, Thank you for the offer, but that won't be necessary. We had just built a new W2016 server and neglected to manually update the App-V version. Very silly oversight on our part! We were still running on version 10.0.15063.0 We updated to 10.1.17763.1 (ADK 1809), but the same issue occurred. We then attempted to sequence it again, by enabling PVAD. This time it works! Thank you very much for your assistance with this. It's always the simple things that get missed! :) MSIX does sound interesting though, thanks for the tip! We will look into this and see how it compares to App-V.
Guest - Mike on Monday, 26 October 2020 04:22

Hi Andreas,

Thank you for providing this fantastic AppV recipe! We have used it to successfully sequence 18.7 SSMS.

However we get the error below on launch. If we click on No to stop the error from coming up it goes away until the user logs out and then the issue comes back again. Do you know how to resolve this error or at least where that setting is stored in the registry so that we can ensure that the error prompt is disabled on startup?

"The 'Microsoft.VisualStudio.Editor.Implementation.EditorPackage' package did not load correctly."

If we look into the ActivityLog.xml it says the issue is because of:

"SetSite failed for package [Microsoft.VisualStudio.Editor.Implementation.EditorPackage]
Description: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."

https://files.slack.com/files-pri/T02G1N114-F01CZJLT60N/image.png

Hi Andreas, Thank you for providing this fantastic AppV recipe! We have used it to successfully sequence 18.7 SSMS. However we get the error below on launch. If we click on No to stop the error from coming up it goes away until the user logs out and then the issue comes back again. Do you know how to resolve this error or at least where that setting is stored in the registry so that we can ensure that the error prompt is disabled on startup? "The 'Microsoft.VisualStudio.Editor.Implementation.EditorPackage' package did not load correctly." If we look into the ActivityLog.xml it says the issue is because of: "SetSite failed for package [Microsoft.VisualStudio.Editor.Implementation.EditorPackage] Description: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters." [img]https://files.slack.com/files-pri/T02G1N114-F01CZJLT60N/image.png[/img]
Andreas Nick on Thursday, 29 October 2020 22:20

18.7 has now been packaged. The recipe is the same. We are using a 1809 sequencer (ADK) on server 2019, please note that the ADK sequencer 1903 and 1909 are buggy. My package for 18.7 runs flawlessly and now starts even faster as I think. than about 35 seconds until the GUI appears after a release. By the way, I have just successfully created 18.7 as a MSIX package :-) My company offers the App-V packages as a service. Would you be interested? I can send you an offer or SSMS as Sample if you like

18.7 has now been packaged. The recipe is the same. We are using a 1809 sequencer (ADK) on server 2019, please note that the ADK sequencer 1903 and 1909 are buggy. My package for 18.7 runs flawlessly and now starts even faster as I think. than about 35 seconds until the GUI appears after a release. By the way, I have just successfully created 18.7 as a MSIX package :-) My company offers the App-V packages as a service. Would you be interested? I can send you an offer or SSMS as Sample if you like ;)
Guest - Johnny Dag Hansen on Monday, 19 October 2020 12:21

Thank You again very much - I will test this package as soon as possible! OK, I have been using AppMan Sequencer v10.1.18362.1 (aka 1903) so I will test with the 1809 version instead as soon as possible. I have also been using Windows Server 2016 (build 1607) as sequencing machine OS, since that is the "lowest" common platform for our RDS Environment. Maybe Windows Server 2019 would be a better choice for this exact use case!

Thank You again very much - I will test this package as soon as possible! OK, I have been using AppMan Sequencer v10.1.18362.1 (aka 1903) so I will test with the 1809 version instead as soon as possible. I have also been using Windows Server 2016 (build 1607) as sequencing machine OS, since that is the "lowest" common platform for our RDS Environment. Maybe Windows Server 2019 would be a better choice for this exact use case!
Guest - Johnny Dag Hansen on Sunday, 18 October 2020 16:03

Hi, and thank You for Your reply! But the issue here is that after running the sequencer while installing Citrix Studio, nothing is recorded! I am left with an "empty packet"; no files, registry or anything collected by the sequencer. I have never experienced anything like that before!

Hi, and thank You for Your reply! But the issue here is that after running the sequencer while installing Citrix Studio, nothing is recorded! I am left with an "empty packet"; no files, registry or anything collected by the sequencer. I have never experienced anything like that before!
Andreas Nick on Sunday, 18 October 2020 16:20

I built the package on a Windows Server 2019 with a 1809 (ADK) sequencer. The installation was silent with single packages. The 1903 and 1909 sequencers have bugs. But empty packages I do not know! If it helps you, here is a link to my package (will be deleted soon) https://www.nick-it.de/DesktopStudio_x64_19.12.1.0.zip

I built the package on a Windows Server 2019 with a 1809 (ADK) sequencer. The installation was silent with single packages. The 1903 and 1909 sequencers have bugs. But empty packages I do not know! If it helps you, here is a link to my package (will be deleted soon) https://www.nick-it.de/DesktopStudio_x64_19.12.1.0.zip
Guest - Johnny Dag Hansen on Thursday, 15 October 2020 13:32

Hi, and thank You for a lot of great articles, of which many have been a great help! Now I'm struggling to sequence Citrix Desktop Studio of any newer versions (not sure when it stopped working)...! The last one I sequenced was Dekstop Studio v7 1903, but now I hve tried every version from 7 1912 and upwords; and nothing works! The strange thing is local installations work, and even on the Sequencer Machine during sequencing evertyhing gets installed to C:\Program Files etc. But nothing is "recorded" by the Sequencer - not VREG, not VFS - nothing! Have You had any experience with this?

Hi, and thank You for a lot of great articles, of which many have been a great help! Now I'm struggling to sequence Citrix Desktop Studio of any newer versions (not sure when it stopped working)...! The last one I sequenced was Dekstop Studio v7 1903, but now I hve tried every version from 7 1912 and upwords; and nothing works! The strange thing is local installations work, and even on the Sequencer Machine during sequencing evertyhing gets installed to C:\Program Files etc. But nothing is "recorded" by the Sequencer - not VREG, not VFS - nothing! Have You had any experience with this?
Andreas Nick on Sunday, 18 October 2020 14:20

One more thing: The required MMC is included in the package. After the installation I create the necessary verküpfung manually
New-Shortcut -TargetPath "$env:windir\System32\mmc.exe" -linklocation CommonStartMenu -ShortcutFilePath "DesktopStudio.lnk" `
-IconLocation "C:\Program Files\Citrix\Desktop Studio\Console.ico" -WorkingDirectory "C:\Program Files\Citrix\Desktop Studio\" `
-Arguments """c:\Program Files\Citrix\Desktop Studio\Studio.msc"""

One more thing: The required MMC is included in the package. After the installation I create the necessary verküpfung manually New-Shortcut -TargetPath "$env:windir\System32\mmc.exe" -linklocation CommonStartMenu -ShortcutFilePath "DesktopStudio.lnk" ` -IconLocation "C:\Program Files\Citrix\Desktop Studio\Console.ico" -WorkingDirectory "C:\Program Files\Citrix\Desktop Studio\" ` -Arguments """c:\Program Files\Citrix\Desktop Studio\Studio.msc"""
Andreas Nick on Sunday, 18 October 2020 13:32

It is not that easy and in my opinion it was the same with older versions. The last time I packaged the studio for 7.8. First of all I automate the installation and install single packages. But you can also use the Citrix disk. But now the studio doesn't start with the application "LaunchConsole.exe" but only with a separate MMC. So start the mmc into the virtual bubble of the package (for example: mmc.exe /appvve:931024e3-e1fc-403d-9955-e755048e5ecc_3709619a-4911-47e5-8e64-7fea81121b05) now you can add the studio as a SnapIn. Maybe there is a better way, which I do not know.

It is not that easy and in my opinion it was the same with older versions. The last time I packaged the studio for 7.8. First of all I automate the installation and install single packages. But you can also use the Citrix disk. But now the studio doesn't start with the application "LaunchConsole.exe" but only with a separate MMC. So start the mmc into the virtual bubble of the package (for example: mmc.exe /appvve:931024e3-e1fc-403d-9955-e755048e5ecc_3709619a-4911-47e5-8e64-7fea81121b05) now you can add the studio as a SnapIn. Maybe there is a better way, which I do not know.
Andreas Nick on Friday, 16 October 2020 08:24

Hi and thank you! I will test the studio in the next days. We also have an older version in use at a customer. The studio is a good candidate for our packaging service for App-V standard packages. I also build SSMS fully automated with a script for our customers. Unfortunately we still have a performance problem with it.

Hi and thank you! I will test the studio in the next days. We also have an older version in use at a customer. The studio is a good candidate for our packaging service for App-V standard packages. I also build SSMS fully automated with a script for our customers. Unfortunately we still have a performance problem with it.
Already Registered? Login Here
Guest
Thursday, 26 November 2020

Captcha Image

@nickinformation Tweets

My german Blog: 

http://www.software-virtualisierung.de

in 

Cookies make it easier for us to provide you with our services. With the usage of our services you permit us to use cookies.
More information