/build/static/layout/Breadcrumb_cap_w.png

K1000 KScript "Verify Folder Exists" misreporting

I am setting up a script to verify whether a folder exists at c:\Windows\System32\oobe\info\backgrounds.  This script also runs a batch file as part of the remediation that creates the folder, then copies an image into that folder.  

The issue is kind of strange.  When I first run the script it correctly reports that the folder doesn't exist, and runs the batch file.  The batch file reports back that the file was sucessfully copied into the new folder.  The issue is that the folder never gets created, but the script reports back that the folder exists.  Even if I remove the remediation portion and only check if the folder exists, I still get a false positive.  

If I run the same "Check" on another machine, it reports correctly until I try to remediate the new machine again.  From that point forward it consistently misreports the existence of that folder.  Now I have a few machines without the background folder that I can't force remediation on because the KACE doesn't think they need remediation.

Any ideas?

Thanks 


0 Comments   [ + ] Show comments

Answers (3)

Answer Summary:
Posted by: jgrotkier 10 years ago
Yellow Belt
0

Just found this thread outlining my exact issue, with no final resolution

http://www.itninja.com/question/k1000-changing-the-logon-bakground

Posted by: jgrotkier 10 years ago
Yellow Belt
0

Just found this thread outlining my exact issue, with no final resolution

http://www.itninja.com/question/k1000-changing-the-logon-bakground

Posted by: flip1001 10 years ago
Black Belt
0

In the kscript change System32 to SysNative.


Comments:
  • Thanks! Finally got it working. - jgrotkier 10 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ