before i put a ticket in, the 2503 Omnissa client ...
# omnissa-horizon
b
before i put a ticket in, the 2503 Omnissa client isnt' installing as part of an SCCM task sequence anymore, and its causing other apps to fail - Asking if theres a suggested way to install it? Errors saying Windows Firewall needs to be running now... What is the proper way to install this now in a task sequence?
m
I'm not sure if it helps, but I split out the .net component from the installation when I do it. I have a simple bat file for the install itself I use.
@echo off
SET server=server fqdn
cd %~dp0
for %%i in (*.exe) do (
"%%i" /silent /norestart VDM_SERVER=%server% LOGINASCURRENTUSER_DEFAULT=1 ADDLOCAL=ALL DESKTOP_SHORTCUT=0 AUTO_UPDATE_ENABLED=0 SKIP_DOTNET_RUNTIME_INSTALL=1 Remove=DeemAgent
)
.net runtime would be installed as a dependency. Mainly so I keep the most-current iteration there since the horizon installer would use whatever was current at the time it was created, but not move ahead.
also why are you cutting off the firewall in your TS? I'd test enabling it first. Apps put their own rules in there and likely is breaking things by turning it off