<KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
<KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
I don't love doing disinfections remotely but sometimes you do what ya gotta do. I'd like to be able to kill off all the potentially nasty softwares while still leaving my connection open. Just tested the two commands and, not surprisingly, it killed my remote connection to the laptop on my workbench.
Could a parameter be added (or some other workaround) so we can enter the name of our remote software in the script and not have it kill it? Or maybe hard-code in a list of common remote softwares as built-in exceptions?
Could a parameter be added (or some other workaround) so we can enter the name of our remote software in the script and not have it kill it? Or maybe hard-code in a list of common remote softwares as built-in exceptions?
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
That seems pretty easy.
I remember I made something similar for Bill a while ago.
First, in your bench machine, create the exceptions list from the Process manager. Don't forget to click Save.
In the Options section, export the settings to an INI file, upload it to your website.
In the remote machine, download the UVKSettings.ini file to the same path where UVKPortable is.
Run UVKPortable. The ignore list is automatically imported.
Of course, you can make a self-extracting package that contains both files, and also other files you may need.
I remember I made something similar for Bill a while ago.
First, in your bench machine, create the exceptions list from the Process manager. Don't forget to click Save.
In the Options section, export the settings to an INI file, upload it to your website.
In the remote machine, download the UVKSettings.ini file to the same path where UVKPortable is.
Run UVKPortable. The ignore list is automatically imported.
Of course, you can make a self-extracting package that contains both files, and also other files you may need.
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
Fred
Fred
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Following on all of that except the very first "create the exceptions list" .... In process manager, can't find anything to do with exceptions.
BUT I opened the INI and it looks like I'd already done that. However, ScreenConnect recently dropped the "Elsinore" from their filenames because they're now owned by ConnectWise so I just had to edit the INI.
BUT I opened the INI and it looks like I'd already done that. However, ScreenConnect recently dropped the "Elsinore" from their filenames because they're now owned by ConnectWise so I just had to edit the INI.
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Xander,
If you click the kill all processes tab in process manager you can add exceptions there in the right hand box.
If you click the kill all processes tab in process manager you can add exceptions there in the right hand box.
Play stupid games….win stupid prizes
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Ah, there it is. Thanks.
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
This was a huge issue for me with my remote software. Had to exclude this from all my scripts. Or I would screw up remote support sessions.
Glad I found this thread!
Is it possible to add multiple programs, also... Does the program path change between OS versions. Should I create an INI file built of multiple PC's to make sure im
Not missing anything. Cheers
Glad I found this thread!
Is it possible to add multiple programs, also... Does the program path change between OS versions. Should I create an INI file built of multiple PC's to make sure im
Not missing anything. Cheers
-
- Posts: 1529
- Joined: Sun May 25, 2014 7:44 am
- Location: Missouri
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Wrc
At the very least you would have the potential of program files and program files (x86).
The paths for some things are different between win 7 and win xp if you still fool with xp at all.
At the very least you would have the potential of program files and program files (x86).
The paths for some things are different between win 7 and win xp if you still fool with xp at all.
Jim
It is not "Can it be done?" but rather, "How can we do it?"
It is not "Can it be done?" but rather, "How can we do it?"
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
There are no paths, just file names. explorer.exe, chrome.exe, teamviewer.exe, etc. case insensitive.
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
Fred
Fred
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Fred wrote:That seems pretty easy.
I remember I made something similar for Bill a while ago.
First, in your bench machine, create the exceptions list from the Process manager. Don't forget to click Save.
In the Options section, export the settings to an INI file, upload it to your website.
In the remote machine, download the UVKSettings.ini file to the same path where UVKPortable is.
Run UVKPortable. The ignore list is automatically imported.
Of course, you can make a self-extracting package that contains both files, and also other files you may need.
I don't quite see the "create the exceptions" feature.
Can anyone provide support?
- Attachments
-
- 2.png (170.98 KiB) Viewed 15163 times
-
- UVk.png (869.77 KiB) Viewed 15163 times
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Jono, press "Kill all processes". In the right pane of the dialog box that shows up, you'll see what you need.
http://www.carifred.com/uvk/help/proces ... p#kill_all
http://www.carifred.com/uvk/help/proces ... p#kill_all
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
Fred
Fred
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Sebastian, Fred IS the support/developer of this software.
Do you know where you are on the internet?
Ahhh, you added text to my quote to make it look like I made that statement. Yeah, you're just a spammer and you're reported.
Do you know where you are on the internet?
Ahhh, you added text to my quote to make it look like I made that statement. Yeah, you're just a spammer and you're reported.
Re: <KillNonCriticalProcesses>and/or <KillNonTrustedProcesses> Exceptions for remote work
Thanks for reporting this Xander!
One thing we humans have in common is that we are all different. So, if you think you're weird because you're different from everyone else, then we are all weird.
Fred
Fred