
There is no way to get closer to how Specops Deploy App is deploying software to the machines in your network.

PsExec v2.32 - Execute processes remotely Copyright (C) 2001-2021 Mark Russinovich Sysinternals - Password: PsExec could not start cmd.exe on end-user-pc: Logon failure: the user has not been granted the requested logon type at this computer. In other words, this is the perfect way to test your installations. C:\PSTools>psexec \\end-user-pc -u Administrator cmd.exe. In the Command Prompt opened as LOCAL SYSTEM so that you can test your installations before you move them into Specops Deploy. This is the same account Specops Deploy App uses when installing applications.

Open a Command Prompt as admin and enter the command below:īy 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.Unzip the content and copy PsExec.exe to C:\Windows\System32.To do this I recommend a little tool from Sysinternals called PsExec.exe Well, starting cmd.exe to run a batch file which contains only one command line to run psexec.exe with wrong path for 32-bit environment is not needed at all. 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. When an application is deployed using Specops Deploy, LOCAL SYSTEM is the account performing the installation. Save the trace in pml native format saving all the events and share the trace.

Start to capture a trace just before running on the remote machine the psexec command. This blog post might shed some light on your issue. perform the same step as before, delete the service and reboot the machine, then start process monitor on the host where you would like to start the psexecsvc. and then use the Select-String cmdlet to search for Cannot find the Help. 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. just search through a specific IP range cmd /c start /min powershell.
