Skip to content

Conversation

@FrenzyTheory
Copy link

change path to ts_block.vbs when you import this into task scheduler, this will launch ts_block.vbs everytime a login attempt happens. no need to run as service.

change path to ts_block.vbs when you import this into task scheduler, this will will launch ts_block.vbs everytime a login attempt happens. no need to run as service.
@EvanAnderson
Copy link
Owner

Running as a service seems like a lot cleaner way to run the ts_block script than this method, to me. The service can be started / stopped easily through the service control manager API, whereas starting the script as a task, like this, isn't going to make it as easy to interact with.

You definitely wouldn't want to restart ts_block each time a logon occurred, because that would result in a bunch of instances of the script running (chewing up memory, etc). It looks like your XML file is allowing multiple instances of the script to run. That's really, really not going to do what you want.

I think I'm going to pass on merging this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants