SMS Application deployment 1

[Jfaraone]

I am having trouble silently deploying applications via SMS.

I have created / advertised the package, and my client target machine receives systray notifications / has the option in add remove programs to install. I didn't have trouble deploying the SMS client, and as the client can see the advertised package, I don't think its a configuration issue.

How would I go about forcing the install? I am obviously new to SMS, any ideas as to what I'm missing?

 

[tbrennans]

Did you set a mandatory run time in the advert?

 

[ncotton]

Check your reports for current advertisements, are you sure that they aren't running, post some more details about the config or your package program, including permissions needed.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[Jfaraone]

Alright....

My initial package was IE6, which I did eventually get deployed using a .sms file.

The next package I am trying to deploy isn't installer friendly, so I have a batch file that copies the appropriate files, reg entries, etc. I checked my .bat file in as a software package, configured everything as I did with IE6, and its a no go.

My process is this:

Create a new package. Aside from Name, Version and Language, nothing is changed.

Add a distribution point.

Add the program. I name it, enter the name of the .bat, give its UNC path in the "Start in:" field, and tell it to restart the machine after running.

In the enviornment tab, I tell it to run whether a user is logged in or not, and have it use the software installation account.

I create an advertisement. Name it, choose the appropriate package, program, and collection. I leave the default (current) start time, give a mandatory assignment of As soon as possible, and set the priority to High.

Done. So, what did I miss?

Is there a way to force clients to check for new software, or an error log on the client machine I can look through?

 

[Jfaraone]

Here is the advertisements error.

The program for advertisement "CHQ2000B" could not be executed ("CHQ0000C" - "Remote Administrator"). The operating system reported error 2147942405: Access is denied. Additional program properties:
Command line: "\\vmsmstest\install\radmin\radmin.bat"
Working directory: \\vmsmstest\install\radmin\
The command line for the program cannot be executed successfully.

Possible cause: This error can be caused by an invalid executable file specified in the command line (such as an Alpha-based executable file on an x86-based computer) or by a corrupt executable file. This error can also be caused if the program is executed from a remote session.
Solution: Make sure that the executable file specified in the program’s command line is valid for the computer it is attempting to run on. Also, manually verify that the specified command line can be executed from within the original package source directory. If necessary, modify the program properties, the package source files, or both. If changes to the package source files are required, use the Manage Distribution Points wizard to update all of the package's distribution points with the new version of the package source files before retrying execution on the client. This program will be retried.

 

[tbrennans]

since the bat file is being run from the smspkg<drive>$\PackageID" directory on the DP. If this is an Advanced client be sure you have configured a Network Access Account.

This is done in the SMS admin console under "Site Settings | Component Configuration | Software Distribution". This account is what the Advanced client uses to access the DP. A legacy client uses the "SMSClient_<sitecode>" account to access the DP. Either one of these needs permissions to the directory and share on the DP. A domain user is usually sufficient.