2 Replies Latest reply on Jul 23, 2015 1:42 PM by Mike Reider

    Compliance "Command" output different from actual OS output

      noticing a difference in running the compliance Command function on windows targets,


      in my template Im running this cmd to check the Users file, it returns a NULL




      Running same exact command in NSH prompt on target outputs the expected result,




      In fact running a basic 'cat /c/windows/rsc/users' in template returns a NULL on this box, but the secure file is defined and contents can be viewed via NSH shell. I ran this against several win hosts and some of them return a value, others have 'null' even though the secure file has content. Looks like a discrepancy between how compliance runs the Command and how NSH runs the same cmd.


      this is bsa 8.5.1 p4