So, I work for a university and we use Faronics DeepFreeze to maintain the state of our computers.
I am upgrading our management process to leverage the remote capabilities of PowerShell. The problem is, I am trying to use the command line utility for DeepFreeze, DFC.exe, to remotely, via a script, check whether all the computers are frozen or thawed
Most of the DFC command line switches work fine through powershell, such as "DFC get /VERSION". It will correctly display the version of DeepFreeze that is currently installed. However, the command "DFC get /ISFROZEN" does not work in PowerShell. It doesn't display an error, or anything, it just returns me to the powershell prompt.
Here is the kicker though. All the DFC switches work perfectly from the old cmd.exe application. I have tried many variations of Invoke-Command, Start-Process, CMD /c, etc. To try and get the /ISFROZEN switch to work properly powershell,
but so far I have not had any success.
One thing I did notice though, according to the documentation /ISFROZEN returns a boolean value. My question is, is there some reason why this returned boolean value would cause powershell to completely ignore what /ISFROZEN is trying to display to the screen? When /ISFROZEN is working properly in cmd.exe, it displays "FROZEN" or "THAWED" based on the state of the computer. Has anyone ran into a similar problem with another command line utility, where some switches work and others don't return anything?
Any insight or advice would be appreciated.
TLDR: I have a command line application that works perfectly in cmd.exe, but in PowerShell, some of the switches do not work. The switch in question returns a boolean value. I have tried many different ways to get this command to work including variations of Invoke-Command, Start-Process, and CMD /C. Everything I have tried produces the same result.