Flexible Security For Your Peace of Mind
Using PsExec to become the LOCAL SYSTEM account

How to: become the LOCAL SYSTEM account with PsExec

(Last updated on February 7, 2020)

If you are an administrator using Specops Deploy, you may have had the following experience: an application can be deployed without any problems when you are trying it on your local machine but when you try to deploy it you can’t seem to get it to work. This blog post might shed some light on your issue.

When an application is deployed using Specops Deploy, LOCAL SYSTEM is the account performing the installation. To ensure that your application is installed in the exact same way as Specops Deploy App, you need to act as the LOCAL SYSTEM account. To do this I recommend a little tool from Sysinternals called PsExec.exe

  1. Download PsTools from https://download.sysinternals.com/files/PSTools.zip
  2. Unzip the content and copy PsExec.exe to C:\Windows\System32
  3. Open a Command Prompt as admin
  4. Launch a new Command Prompt using PsExec.exe. By using PsExec.exe you will open the new Command Prompt in the System Context and the account doing all the operations will be the LOCAL SYSTEM account. This is the same account Specops Deploy App uses when installing applications.

Using PsExec to become the LOCAL SYSTEM account

In the Command Prompt opened as LOCAL SYSTEM so that you can test your installations before you move them into Specops Deploy.

Open LOCAL SYSTEM account in the command prompt

In other words, this is the perfect way to test your installations. There is no way to get closer to how Specops Deploy App is deploying software to the machines in your network.

Tags: , , ,

>

Written by

Mikael Ingelin

Product Specialist, Specops Software

More Articles
Back to Blog