VMware Horizon Community
piney84
Contributor
Contributor
Jump to solution

VMware Horizon Client 4.5.0 REBOOT=Reallysuppress still reboots?

Hey guys thought I'd update my clients to 4.5.0 but when I tested the silent install it installed great but it forced a reboot even with REBOOT=Reallysuppress switch.

%~dp0VMware-Horizon-Client-4.5.0-5650915.exe /s /v"/qn ADDLOCAL=ALL LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1 DESKTOP_SHORTCUT=1 STARTMENU_SHORTCUT=1 VDM_SERVER=************** REBOOT=ReallySuppress /l*v "%TEMP%\log.txt""

Any ideas?

1 Solution

Accepted Solutions
techguy129
Expert
Expert
Jump to solution

You are correct it doesn't work. VMware changed the installer for 4.5. You need to include a /norestart

Example:

VMware-Horizon-Client-4.5.0-5650915.exe /silent /norestart ADDLOCAL=ALL LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1 DESKTOP_SHORTCUT=1 STARTMENU_SHORTCUT=1 VDM_SERVER=**************

View solution in original post

0 Kudos
8 Replies
techguy129
Expert
Expert
Jump to solution

You are correct it doesn't work. VMware changed the installer for 4.5. You need to include a /norestart

Example:

VMware-Horizon-Client-4.5.0-5650915.exe /silent /norestart ADDLOCAL=ALL LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1 DESKTOP_SHORTCUT=1 STARTMENU_SHORTCUT=1 VDM_SERVER=**************

0 Kudos
nzorn
Expert
Expert
Jump to solution

They changed a few things, starts on page 27: https://www.vmware.com/pdf/horizon-view/horizon-client-windows-45-document.pdf

Example:  VMware-Horizon-Client-4.5.0-5650915.exe /silent /norestart VDM_SERVER="view.server.url"

They also removed the ability to control the desktop icon which is sad.

BenFB
Virtuoso
Virtuoso
Jump to solution

We discovered that even when specifying the correct "/norestart" switch there are some mandatory prerequisites that will still unexpectedly restart the system (This also happens with the Horizon Agent). We've only tested with Horizon Agent 7.1 and Horizon Client 4.5 but we found that if the following prerequisites were missing it will install them and restart the system. You then have to run the silent install again. We've seen multiple restarts depending on how many of the prerequisites are missing from the system.

Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148

Microsoft Visual C++ 2015 Redistributable (x64) - 14.0.24212

Microsoft Visual C++ 2015 Redistributable (x86) - 14.0.24212

EricSPeriard
Contributor
Contributor
Jump to solution

As a SCCM admin I had to package the horizon client software and to prevent the reboot I ran the extract command on the installer exe.

In my script I installed the VC exe's individually with the no restart switch on each of them and that worked just fine.

so essentially:

***SCRIPT UPDATED***

TASKKILL /F /IM vmware-view* /T

REM Dependencies

dotNetFx40_Full_x86_x64.exe /q /norestart

vcredist_x64.exe /qn /norestart

vcredist_x86.exe /qn /norestart

vc_redist.x64.exe /install /quiet /norestart

vc_redist.x86.exe /install /quiet /norestart

REM Client install

setup.exe /silent /install /norestart ADDLOCAL=ALL INSTALL_SFB=1 VDM_SERVER=URL-Here

EXIT /B

0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

Thank you EricSPeriard​! This some process can be used for Horizon Agent 7.x and now we no longer need 3 reboot.

EricSPeriard
Contributor
Contributor
Jump to solution

You're welcome Smiley Happy

0 Kudos
EricSPeriard
Contributor
Contributor
Jump to solution

False, the no restart switch is broken.

See my posting above.

There's VC++ dependencies, if it's not installed on the system it will install the dependencies and promptly reboot the system no matter of the switch is specified.

The way to avoid the reboot is to extract the exe and install the VC++ redists... In my case I had to manage 200+ PCs with Horizon 4.5 client and it worked like a charm.

0 Kudos
valkenaer
Contributor
Contributor
Jump to solution

We are experiencing a similir issue: during the installation VMware-Horizon-Client-4.6.1-6748947.exe installs to additional runtimes on our computers, but these are actually older than the ones embedded in the Windows 10 version 1709 image.

Any way to bypass this?

Naamloos.jpg

0 Kudos