I am trying to use the following fixlet to enable the Windows Optional Feature XPS Viewer,
https://bigfix.me/fixlet/details/1033
The first issue I’m seeing is with the relevance associated with this fixlet. If I leave the default relevance in place I get exactly zero machines showing up as Applicable:
exists file “dism.exe” of system folder
if( name of operating system starts with “Win” ) then platform id of operating system != 3 else false
if exists property “in proxy agent context” then ( not in proxy agent context ) else true
exists file “DISM.txt” of parent folder of client
exists lines whose (it contains "Xps-Foundation-Xps-Viewer " and it contains “Disabled”) of file “DISM.txt” of parent folder of client
If I remove all the relevance except “exists file dism.exe of system folder” I will finally get some relevant computers showing up.
Once I get this far and try to deploy the fixlet it fails, upon examining the action script I found this
action uses wow64 redirection {not x64 of operating system}
delete __appendfile
appendfile “{pathname of system folder}\dism.exe” /online /enable-feature /featurename=Xps-Foundation-Xps-Viewer
appendfile “{pathname of system folder}\dism.exe” /online /get-features /format:table > "{pathname of parent folder of client}\DISM.txt"
delete __Download\dism.bat
move __appendfile __Download\dism.bat
waithidden __Download\dism.bat
My question is what is the dism.bat? Is that something I’m supposed to create? I also wonder if the argument for the switch /online /enable-feature /featurename=Xps-Foundation-Xps-Viewer is correct. It does not match what I find in other site to use to install XPS viewer from the command line. */Online /Add-Capability /CapabilityName:XPS.Viewer~~~~0.0.1.0.* Which is what I’ve used to succesfully install it while sitting at the desktop.
P.S. I’m pretty new to BigFix and winging some of it.