(imported topic written by MichaelG91)
Configuration:
- Fixlet Debugger v 3.0.4 Beta
- BES 8.0.627.0
Operating System:
- Windows 2008 R2 64-bit
- Service Pack 2
Description:
When evaluating the following relevance expression (format: {relevance} - result) I get these results:
{pathname of system folder} - C:\Windows\system32
{pathname of system x32 folder} - C:\Windows\system32
{pathname of system x64 folder} - C:\Windows\system32
{pathname of system wow64 folder} - C:\Windows\SysWOW64
When you try to run an action script that contains something like:
copy __createfile {pathname of system folder}\bigfix_secedit.ini
waithidden cmd /C “{pathname of system x32 folder}\secedit.exe” /configure /db {pathname of system x32 folder}\bigfix_secedit.sbd /cfg {pathname of system x32 folder}\bigfix_secedit.ini /quiet
The net result is that the “bigfix_secedit.ini” file is copied over to the SysWOW64 folder instead of the System32 folder despite the output of the fixlet debugger stating it was copied to “C:\Windows\system32” . When the secedit command runs its looking in the System32 folder for the ini file. While I understand this may be happening as a result of file redirection it seems some consistency or at least appropriate feedback would help resolve debugging issues.
Regards,
- Michael