SOLVED Unified Write Filter detection

[pcb]

We are trying to create deployments with multiple deployment types to handle different scenarios like Deep Freeze and Microsoft's Unified Write Filter. Deep Freeze was easy, but creating a deployment type with requirements for UWF fails when UWF is NOT installed on the target.

If we create a custom global condition like this:

and then add the requirement that UWF is currently inactive:

It works. However, when UWF is NOT installed DCMWmiProvider.log shows:

and the application fails install even though there is another deployment type that should run when UWF is not present. The deployment type that has highest priority looks for a registry key that is only present when UWF is installed and should run if it doesn't exist. I confirmed that by deleting the second deployment type that queries WMI for the UWF_Filter class. The application immediately installed.

If UWF is installed, the above UWF_Filter query works and the application installs without error when UWF CurrentEnabled is false. It is only when UWF is not installed that the whole thing fails. I have tried adding the reqistry key exists requirement to the UWF Active deployment type without success and I tried adding a requirement that the CurrentEnabled property exists, but both attempts failed. We get the same invalid class error in the DCMWmiProvider.log.

Anyone have an idea how we can get this working when UWF is not installed?

 

[pcb]

Seems like this might be a bug? I'm not sure why one deployment type failing would cause all of them to fail - even the ones that have higher priority... There are three in the above situation (two with higher priority) and the one with highest priority installs successfully if Deep Freeze and UWF are not installed as long as this last deployment type is not included.

 

[Prajwal Desai]

It could be a bug, may I know what's the version of ConfigMgr?.

 

[pcb]

 

[pcb]

Attempting to work around this with powershell:
We created the following script (truncated here):
#Query uwfmgr.exe for filter status and return to MECM
# Global variables
$NAMESPACE = "root\standardcimv2\embedded"

########################################################################################################################

# Get current state of UWF
if ($objUWFFilter) {$objUWFFilter = Get-WmiObject -Namespace $NAMESPACE -Class UWF_Filter;}
if(!$objUWFFilter) {
echo disabled
return;
}

# Check if UWF is enabled
if(($objUWFFilter.CurrentEnabled)-or($objUWFFilter.NextEnabled)) {
echo enabled
} else {
echo disabled
}

# SIG # Begin signature block

Then tested the script on the target computer - it runs successfully and echos "disabled"

Then created a new global condition:



Then added the requirement that the script returns "disabled"


And it does not work. AppDiscovery.log shows:


And I don't know where to go from here...

 

[pcb]

Does anyone know the trick to getting a script to return a value to CM? I've tried the echo command (as indicated in the dialogs within CM), but I am not sure how to troubleshoot and see if the returned value is actually received by CM. I have tried returning a string (disabled or enabled) and an integer (0 or 1), but neither seems to work. --I'm not even sure the script runs on the target. I have tried self-signing the script and importing that certificate to the target machine and also tried eliminating the signature and setting the execution policy to "unrestricted", but I seem to be flailing...

 

[Prajwal Desai]

No, I am not sure about that. Best thing is you can contact Microsoft support for this.