Jump to content

Recommended Posts

Posted

We know the history of SysInternals, being one of the countless companies/groups all by themselves and gobbled up by Microsoft. At first glace we could say the failings of NEWSID is caused by the fact it was third party software.

NEWSID changes the Security Identifier in Windows that is not in Factory Mode. Well it changes it in factory too but why would you bother?

Anyways, it does not regen the SID used for the account(s) specified in the Task Scheduler so tasks always get broken. Has a newer version of NEWSID even been released that fixes this problem? Or will we be relegated to running schtasks batch files?


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...