It’s important because when we use the ‘copy’ or ‘move’ commands, they will fail if the target file already exists (the command will not overwrite an existing file). If the disk.bat file existed, this would remove it. If the relevance was working, this lets the relevance check that XPS has actually been successfully added. Looks like it would regenerate the dism.txt file with the new package list, which should now include the XPS package. This second command line gets appended to _appendfile. Once I get this far and try to deploy the fixlet it fails, upon examining the action script I found thisĪction uses wow64 redirection \DISM.txt" If I remove all the relevance except “exists file dism.exe of system folder” I will finally get some relevant computers showing up. If exists property “in proxy agent context” then ( not in proxy agent context ) else trueĮxists file “DISM.txt” of parent folder of clientĮxists lines whose (it contains "Xps-Foundation-Xps-Viewer " and it contains “Disabled”) of file “DISM.txt” of parent folder of client If( name of operating system starts with “Win” ) then platform id of operating system != 3 else false If I leave the default relevance in place I get exactly zero machines showing up as Applicable: The first issue I’m seeing is with the relevance associated with this fixlet.
I am trying to use the following fixlet to enable the Windows Optional Feature XPS Viewer,