Thursday, August 3, 2017

App-V 5x version history


https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v5/about-app-v-51

App-V Version Reference

5.0 RTM              5.0.285.0
5.0 hotfix1           5.0.515.0
5.0 SP1                5.0.1104.0
5.0 SP2                5.0.3361.0
5.0 SP2 hotfix 2   5.0.3384.0 (Clients Only)
5.0 SP2 hotfix 4   5.0.3400.0
5.0 SP2 hotfix 5   5.0.3404.0 (Clients Only)
5.0 SP2 hotfix 6   ?
5.0 SP3                 5.0.10107.0 (sequencer does not upgrade previous versions. The previous version must be removed first.  Client version DOES upgrade.


5.1 client prereqs
.NET 4.5.1 required (KB2858728))
Powershell 3.0 (KB2506143) or higher
Windows 7 Update KB25333623 https://support.microsoft.com/en-us/help/2533623/microsoft-security-advisory-insecure-library-loading-could-allow-remot

5.1 sequencer prereqs
.NET 4.5.1 required (KB2858728))
Powershell 3.0 (KB2506143) or higher

5.1 HF08 sequencer prereqs
above plus KB25333623

update:
KB2533623 superceded by DB2758857
https://sccmentor.com/2013/07/30/kb2533623-superseded-by-kb2758857/

5.1                                    5.1.85.0
5.1                                    5.1.86.0
5.1 HF01                          5.1.99.0 (CO = Clients Only)
5.1 HF02                          5.1.101.0 (CO)
5.1 HF03                          5.1.104.0 (CO)
5.1 June 2016 SR             5.1.106.0 (CO)
5.1 HF05                          5.1.108.0 (CO)
5.1 Sept 2016 SR             5.1.115.0 (CO)
5.1 HF07                          5.1.116.0 (CO)
5.1 HF08  Mar2017 SR    5.1.118 - Offline Client and Sequencers will need a certificate installed.  Clients update, Sequencers full install.

Installing the HF08 sequencer (AppV5.1RTM_Sequencer_KB4014009.exe) can be a bit of a mission.
You must install the KB2533623 update first
If the sequencer is offline then you will need to install the Microsoft Root CA certificate.
How to export the MS Root CA certificate
https://support.microsoft.com/en-us/help/555252
From experience you can just double click and install but make sure you choose Trusted Root Certification Authorities.
How to install a root certificate.
https://msdn.microsoft.com/en-us/library/cc750534.aspx


More detailed client release / version info here
https://support.microsoft.com/en-us/kb/2940578

Tim's page is probably more up to date though
http://www.tmurgent.com/appv/en/resources/app-v-5-versions

Note that the Client UI application has its own version which does not correspond to the App-V Client version.

Windows 10 Anniversary Update version 1607 contains an App-V client which reports itself as 5.2 in the registry location
HKLM\SOFTWARE\Microsoft\AppV\Client\Version

General Microsoft End of Support information (End of Life)
https://support.microsoft.com/en-us/lifecycle/search

App-V 4.6 SP3 ended Mainstream support 14/07/2015
http://www.tmurgent.com/AppV/en/resources/app-v-4-versions

http://parlakyigit.net/ebooks/App_V_Versions.pdf

Friday, July 21, 2017

wscript exit code errorlevel 9009


The same script can end with different command box errorlevel values between cscript and wscript. The command box %errorlevel% after a wscript command will likely be 9009.  This is because the command interpreter immediately becomes ready for the next command even if the script is still running.  It is not able to receive the exit code from the wscript interpreter.  cscript on the otherhand waits for the script to exit before the command box is available again.  In that case the %errorlevel% command reflects the vbscript exit code.

echo %errorlevel%

Friday, July 7, 2017

Windows 10 File Explorer Quick Access - Working on it

Bit of a noddy one this.
Problem:
Attempting to launch File Explorer in Windows 10 results in a window with the "Working on it" status which then hangs and then the explorer shell completely crashes and initializes.

Solution:
Reboot.  Launch File Explorer by entering a known folder name in the search bar.  This launches File Explorer in a specific folder.
In View_Options_Change folder and search options:

Change the Open File Explorer to: setting to point to This PC.
Click Clear and Restore Defaults.

Friday, June 30, 2017

Enable Browser Controls


Enable Browser Controls is activated automatically by the sequencer if they are detected.  Watch out though. It is important to understand this concept described by Tim Mangan here

http://www.tmurgent.com/TMBlog/?p=2240

Briefly, Tim explains that if IE is launching with a connection group to supply visualized components then override settings on the registry keys need to be changed to merge.  Otherwise one of the app-v packages will work while the rest do not.

Thursday, June 29, 2017

Teradata Tools and Utilites (TTU) 15.10


First crack looked fine until the SQL Assistant crashed on launch.  Much head scratching until the realization that the shortcut was pointing to startup.exe but the actual process was SQLA.EXE.  Launching SQLA.EXE in the bubble worked fine, so the shortcut was successfully changed from startup.exe to SQLA.EXE.  startup.exe must be some kind of launcher stub used for unknown reasons and incompatible with App-V 5.

ODBC DSNs may be required so watch out for those.

While troubleshooting, launching during sequencing or use of the PVAD caused this error during the save operation:

The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F

This was tracked down to the TTUProductList shortcut with an invalid path to its icon file.  Correct the icon path to point to a valid file resource and check that the file resources do not have a bad path to the original icon file.  The path seen in the sequencer window had an invalid  ..  (2dots)  in the tree which looked like it could cause trouble.

Tuesday, June 13, 2017

Inmagic DBTextWorks 13 needs PVAD


Inmagic DBTextWorks 13 needs to have the PVAD for a successful sequence.  Using the defaults and sequencing to the VFS results in an error.  During launch the application checks for the presence of critical files and throws an error if it does not find them.  A similar error with a normal path could be generated on a conventional install by renaming the dbtext32.cmx file.  The error from the application showing the strange path led to the idea that the PVAD might correct the problem.













https://lucidea.com/inmagic/dbtextworks/

PVAD


Captain! She's breaking up.  ENGAGE PVAD !

Launch the sequencer with the -EnablePVADControl parameter

http://www.tmurgent.com/TmBlog/?p=2264