- Joined
- Jan 10, 2020
- Messages
- 4
- Reaction score
- 0
I'm a Linux guy who is having a difficult time solving a permissions issue (at least that's what I think it is). My cmd scripts used to work in Windows but now they have stopped. OpenVPN has no problem assigning the pushed ip's and routes for the Tap device, however it will no longer execute scripts on Windows 10 clients. The scripts work fine from the user and administrator command prompts (currently I am only writing to a file), but when OpenVPN calls the scripts I get errors in the log and the scripts have not written to the file. This is the feedback from the OpenVPN log;
Looking in the Event Viewer I see no 'Error' or 'Warning' events coinciding with the starting and stopping of the OpenVPN Tap connection. However, there are four events coinciding with the reboot of the computer;
ERROR #1
ERROR #2
ERROR #3
WARNING
All applications and scripts have been given 'Run this program as an administraor' on the 'Compatibility' tab of the properties pop-up or 'Run as administrator' on 'Advanced Propties' pop-up of links.
So far, I have tried the following
- starting app locker service then adding the script folder to app locker with Administrator\Local Service\Network Service\Everyone as user.
- Adding OpenVPN service trigger as task when connected to particular SSID with evelvated privlages.
- Editing and adding 'Local Service', 'Network Service' and 'DESKTOP-FP9UVBJ\david' as groups to the tagged CLSIS/APPID in the lo.
Nothing seems to work. I have been working on this for too long now! An help would be greatly apprecieated.
Thanks, Dave
Code:
Thu Jan 09 19:41:47 2020 us=896429 C:\Users\user\OpenVPN\config\user\scripts\client-tap.cmd Tap 1500 1584 192.168.XXX.XXX 255.255.255.XXX init
Thu Jan 09 19:41:47 2020 us=896429 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Looking in the Event Viewer I see no 'Error' or 'Warning' events coinciding with the starting and stopping of the OpenVPN Tap connection. However, there are four events coinciding with the reboot of the computer;
ERROR #1
Code:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user DESKTOP-FP9UVBJ\david SID (S-1-5-21-772083243-123503260-1006230852-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
ERROR #2
Code:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
ERROR #3
Code:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
WARNING
Code:
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.
All applications and scripts have been given 'Run this program as an administraor' on the 'Compatibility' tab of the properties pop-up or 'Run as administrator' on 'Advanced Propties' pop-up of links.
So far, I have tried the following
- starting app locker service then adding the script folder to app locker with Administrator\Local Service\Network Service\Everyone as user.
- Adding OpenVPN service trigger as task when connected to particular SSID with evelvated privlages.
- Editing and adding 'Local Service', 'Network Service' and 'DESKTOP-FP9UVBJ\david' as groups to the tagged CLSIS/APPID in the lo.
Nothing seems to work. I have been working on this for too long now! An help would be greatly apprecieated.
Thanks, Dave