Here is my script, trying to write the bitlocker status to a file. The script runs and creates an empty file. I actually have 2 scripts that do the same thing on 64 bit laptops:
1. Launch “%windir%\syswow64\cmd.exe” with params “/C” c:manage-bde.exe -status >c:\cn.txt“”.
2. Launch “C:\Windows\system32\cmd.exe” with params “/C ”manage-bde.exe -status >c:\cn.txt“”
Anyone have any advice?
4/30/14 -tried removing quotes on both scripts, still get an empty cn.txt file and "error creating process".
Community Chosen Answer
I see what you mean it works fine on 32 bit but not 64 bit machines. Even tried as a custom software inventory and got same results. The problem is the kace client is a 32bit application, so when it tries to run an .exe file under %Windir%/system32 it is automatically redirected to %Windir%/syswow64, and the manage-bde.exe file doesn't exist in this location.
I use the link below to hide the cmd window from showing but you can just use the line in the batch file as your parameters
so as a custom software inventory for 64bit:
as a hidden script file:
create 2 files, invisible.vbs and bitlocker.bat and add them as dependancies
As a script that will flash the cmd window past the user: