SparkLabs Forum.

Community Help.


Disconnect script not working in Windows 10 LTSB

Hello.

I just changed my OS from W10 to W10 LTSB, its a cleaner W10 for Enterprises.

I have been trying for some hours now but i can't get my old disconnect script to work.

It works when i select the .vbs file itself but when it should be used in Viscosity it happens nothing.

Been granting Viscosity Admin rights on startup.

This is how my script looks like.

"Dim objWMIService, objProcess, colProcess
Dim strProcessKill
strProcessKill = array ("qBittorrent", "SRWare Iron")
For Each Process In strProcessKill
Dim strComputer : strComputer = "."

Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& strComputer & "\root\cimv2")

Set colProcess = objWMIService.ExecQuery _
("SELECT commandline FROM Win32_Process WHERE commandline LIKE '%" & Process & "%'")

For Each objProcess In colProcess
objProcess.Terminate()
Next
Next
Dim objShell
Set objShell = WScript.CreateObject ("WScript.shell")
objShell.run "cmd /K netsh interface set interface name=Ethernet admin=disabled"
Set objShell = Nothing"

SRWare Iron is based on Chrome.

I also get a problem with SRWare Iron after I have been using my .vbs script.
On my shortcut to SRWare Iron, I have put --Incognito. To make it start in Incognito mode when starting up.

After running the script it starts as normal (not Incognito) but trying to visit "--Incognito" as a webadress.
I have to remove the shortcut and make a new one and pin in to my taskbar every time.

Would love to get some help on this.

Cheers have a nice weekend!
Hi Hugo,

I'm afraid I don't know a lot about LTSB, our understanding was it was just a featureless and slower updated version of Windows, but if it is designed for Enterprise in more ways than this, there is every chance there is something blocking scripts from being run by other applications as a security feature.

As a test, I recommend creating a very simple VBS script that opens a web page or shows a dialog box and testing that works first, then building your script up from there bit by bit to try and figure out where it is failing.

Regards,
Eric
2 posts Page 1 of 1

Copyright © 2016 SparkLabs Pty Ltd. All Rights Reserved. Privacy Policy