Extraction of VBScript from PrimalScript packaged executable
Posted: Wed Jun 22, 2016 8:57 am
Packaged with Primal Script 2016 7.2.90.0 64 bit
Issue confirmed independent of OS, but experienced on: Windows 8.1 Pro 64 bit, Windows 7 Pro, Windows 10
I have a packaged VBScript file that is run with Alternate credentials using the "RunAs user" Run Mode. The RunAs user is necessary as the script is initiated by non admins, but requires admin privileges. Before I updated PrimalScript, it would extract a .vbs packaged executable to the "C:\Temp" folder and then execute from there. This has worked excellent for years. With the latest update(Or at least my latest update after I got around to updating), listed above, It is now extracting the temp vbs file to the location that the script was called from. The packaged script is actually called from a group policy logoff script. Since the logoff script is executed from "C:\Windows\System32\GroupPolicy\User\Scripts\Logoff", it is now trying to extract the packaged .vbs file to that location. The .exe is actually in another folder. Since the logoff script is run as a non admin, it does not have permission to create the script in that folder, so the process now fails. Other than going back to a previous version of Primal Script to get it to extract to c:\temp, is there a way I can designate where executable extract the temp VB script to? If it could extract to where the executable resides, rather than where it is called from, that would work. Currently the process still works if the user is an admin on the PC, but not if they are not an administrator. I don't want to grant non admins write access to the "C:\Windows\System32\GroupPolicy\User\Scripts\Logoff" folder.
Issue confirmed independent of OS, but experienced on: Windows 8.1 Pro 64 bit, Windows 7 Pro, Windows 10
I have a packaged VBScript file that is run with Alternate credentials using the "RunAs user" Run Mode. The RunAs user is necessary as the script is initiated by non admins, but requires admin privileges. Before I updated PrimalScript, it would extract a .vbs packaged executable to the "C:\Temp" folder and then execute from there. This has worked excellent for years. With the latest update(Or at least my latest update after I got around to updating), listed above, It is now extracting the temp vbs file to the location that the script was called from. The packaged script is actually called from a group policy logoff script. Since the logoff script is executed from "C:\Windows\System32\GroupPolicy\User\Scripts\Logoff", it is now trying to extract the packaged .vbs file to that location. The .exe is actually in another folder. Since the logoff script is run as a non admin, it does not have permission to create the script in that folder, so the process now fails. Other than going back to a previous version of Primal Script to get it to extract to c:\temp, is there a way I can designate where executable extract the temp VB script to? If it could extract to where the executable resides, rather than where it is called from, that would work. Currently the process still works if the user is an admin on the PC, but not if they are not an administrator. I don't want to grant non admins write access to the "C:\Windows\System32\GroupPolicy\User\Scripts\Logoff" folder.