Skip to main content

Applications to Run don't run

Thread solved
Beginner
Posts: 2
Comments: 5

We have had this issue since we started with Snap Deploy 4.  Now on Snap Deploy 5.0.1924 and we still can't get the "Applications to Run" to actually run.  We are a training department so are deploying 10 to 20 machines at a time and having to do these activities manually is a bit of a pain. 

We have 2 powershell scripts that rename the workstation (hostname) after the deployment and modify a text file using the hostname.  The following 3 methods have been tried

  1. Add one or both powershell scripts (*.ps1) to the "Application to Run" section of the deployment template
    • Result:  Nothing happens
  2. Add the cmd.exe as the application with the Parameter to run the powershell script
    • Application = c:\Windows\System32\cmd.exe
    • Parameters = /c start C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -File c:\scripts\RenameShortcut.ps1
    • Result: Partial Success. Only 1 Application can be added to the list of Applications to Run
  3. Create a Windows batch script to run both the powershell scripts and run that batch script from the template
    • Application = c:\Windows\System32\cmd.exe
    • Parameters = /c c:\scripts\runPS.bat
    • Result: Nothing happens

Any help or advice would be appreciated in solving this issue.

0 Users found this helpful
Forum Member
Posts: 3
Comments: 39

#1

That reminds me that my application (just a simple .bat file that renames the hostname using the Dell Service Tag number) isn't working either...  Actually, it's intermittent, but fails probably 90% of the time.  It was working, and I hadn't been able to pin-point the issue or when it stopped working, so I just kinda forgot about it.  We're running 1924 as well.

Are you pulling the application(s) from a network share or just from a spot on the local client?  Ours is on the client.

 

Beginner
Posts: 2
Comments: 5

#2

All our scripts are baked into the client Master Image so are available immediately.  Our issue isn't intermittent though.  This happens (or fails to happen) every time the image is deployed.

Beginner
Posts: 2
Comments: 5

#3

Just thought I would upload a screenshot of the Application to Run window.  I have verified that the path to the runPS.bat file is correct and that cmd.exe is in the c:\Windows\System32 folder.  This should be a no-brainer I would have thought.

Attachment Size
504634-169882.png 24.12 KB
Beginner
Posts: 0
Comments: 2

#4
Eric Grau wrote:

Just thought I would upload a screenshot of the Application to Run window.  I have verified that the path to the runPS.bat file is correct and that cmd.exe is in the c:\Windows\System32 folder.  This should be a no-brainer I would have thought.

Have you tried just set
Application = c:\scripts\runPS.bat ?

Beginner
Posts: 2
Comments: 5

#5

Just read the Release Notes for Snap Deploy 5.0.1971 (the latest release).  It states that "The Applications to run setting does not work after deployment of Windows 7 or Windows 2008".  Unfortunately all of our deployments currently happen to be Windows 7.  There is a workaround in the Release Notes involving the "Files to transfer" setting and the Startup folder.  We will try that and let you know how that goes.

Beginner
Posts: 2
Comments: 5

#6

This workaround of using "Files to transfer" worked.  It is not ideal but, then again, this is Windows 7 so one should expect issues.  :-)