DisplayLink 8.0 M0 Corporate Install Deployment Changes?

atomicd10 · 07-14-2016, 02:48 PM

Hello,

The most recent corporate install files follow a different naming convention than what they have in the past, and the existing corporate deployment instructions still detail how to install DisplayLink using the prior naming convention and files.

Previously there were two files in the corporate installer package named DisplayLinkCore.msi and Setup.msi, now in this latest version there are two named DisplayLink_Win7-10TH2.msi and DisplayLink_Win10RS1.msi.

I was unable to find any deployment documentation on the new files, but I assume the DisplayLink_Win7-10TH2.msi install file is intended for Windows 7 to Windows 10 "Threshold 2" and the DisplayLink_Win10RS1.msi install file is meant ONLY for Windows 10 RedStone. This seems to imply that the versions are incompatible with one another, so when performing an in-place upgrade to Win10 RedStone in an enterprise environment the drivers will likely need to be uninstalled prior to the update and reinstalled after the update which obviously wouldn't be ideal; does anyone know if this is true?

In our environment we are running Win10 Threshold 2. Has anyone found install arguments that work well for them with this new version in Windows 10 TH2? The reason I ask is because we've had a pile of issues installing/deploying DisplayLink in the past, and so I'm curious what others are using for their installation command-line.

Historically we have essentially used the following command-line arguments for installation (and in the same order):

msiexec /i "c:\somePath\DisplayLinkCore.msi" /l*v "c:\somePath\DisplayLinkCore_Install.log" /q/n

msiexec /i "c:\somePath\setup.msi" /l*v "c:\somePath\setup_Install.log" /q/n

Historically we have used the following command-line arguments for uninstalling (and in the same order):

msiexec /qn /x "c:\somePath\setup.msi" DL_PACKAGE_ONLY=Yes REBOOT=ReallySuppress /l*v "c:\somePath\setup_uninstall.log"

msiexec /qn /x "c:\somePath\DisplayLinkCore.msi" REBOOT=ReallySuppress /l*v "c:\somePath\DisplayLinkCore_uninstall.log"

I assume a similar command line will likely work, but I'm curious if anyone does it any differently or has any suggestions for the new version and TH2.

Thanks!

07-14-2016, 02:48 PM	#1
atomicd10 Junior Member Join Date: Sep 2012 Posts: 16	DisplayLink 8.0 M0 Corporate Install Deployment Changes? Hello, The most recent corporate install files follow a different naming convention than what they have in the past, and the existing corporate deployment instructions still detail how to install DisplayLink using the prior naming convention and files. Previously there were two files in the corporate installer package named DisplayLinkCore.msi and Setup.msi, now in this latest version there are two named DisplayLink_Win7-10TH2.msi and DisplayLink_Win10RS1.msi. I was unable to find any deployment documentation on the new files, but I assume the DisplayLink_Win7-10TH2.msi install file is intended for Windows 7 to Windows 10 "Threshold 2" and the DisplayLink_Win10RS1.msi install file is meant ONLY for Windows 10 RedStone. This seems to imply that the versions are incompatible with one another, so when performing an in-place upgrade to Win10 RedStone in an enterprise environment the drivers will likely need to be uninstalled prior to the update and reinstalled after the update which obviously wouldn't be ideal; does anyone know if this is true? In our environment we are running Win10 Threshold 2. Has anyone found install arguments that work well for them with this new version in Windows 10 TH2? The reason I ask is because we've had a pile of issues installing/deploying DisplayLink in the past, and so I'm curious what others are using for their installation command-line. Historically we have essentially used the following command-line arguments for installation (and in the same order): msiexec /i "c:\somePath\DisplayLinkCore.msi" /lv "c:\somePath\DisplayLinkCore_Install.log" /q/n msiexec /i "c:\somePath\setup.msi" /lv "c:\somePath\setup_Install.log" /q/n Historically we have used the following command-line arguments for uninstalling (and in the same order): msiexec /qn /x "c:\somePath\setup.msi" DL_PACKAGE_ONLY=Yes REBOOT=ReallySuppress /lv "c:\somePath\setup_uninstall.log" msiexec /qn /x "c:\somePath\DisplayLinkCore.msi" REBOOT=ReallySuppress /lv "c:\somePath\DisplayLinkCore_uninstall.log" I assume a similar command line will likely work, but I'm curious if anyone does it any differently or has any suggestions for the new version and TH2. Thanks!