Software Distribution Help!!!!!!

[mnt25]

Hello Everyone,
I have been placed in a situation that is capturing the true essence of what SMS software distribution is all about. Unforutunely, it has me strangely in a loop with no answer. Although quite basic to some, here is what I need to accomplish.

On all machines, I need to simply copy (NOT INSTALL) a new executible version down using SMS 2003. is SMS intelligent enough to replace files if the same named file exists or does it require additional programs/scripts,etc?

here are the steps I need to accomplanish to complete this (and which I need guidance on):
1. Ensure no users are logged on
2. Kill the process executable (specifically how in SMS)
2. Backup the existing executable by renaming it to .bak (not sure if this is needed, it all depends if SMS can replace intelligently without additional scripting and programs)
3. Copy the new executable down but not install it.
4. Inventory or Report that the new executable has been copied down by creating a MIF when it’s successful. (not sure how to do this)

I'd appreciate any help you all could provide. Its got me dazzed and confused.

-Matt

 

[Jpoandl]

This is a pretty simple and reasonable situation to use SMS to distribute software; however, remember, SMS package distribution is simply a means to run packages on remote machine. Inheritly, it does not have the ability to perform the functions you are looking for. SMS distribution will only run an EXE.

Therefore, you have to create a script to perform the functions you want implemented. You have a few choices on how to do this: The SMS Installer, WISE Installer, other third party product, or just create a simple batch script.

1. Ensure no users are logged on (When you advertise the package through SMS, you can specify that the package should only run when NO ONE is logged on.)

2. Kill the process executable (specifically how in SMS) (This is a task for your script...Kill program.exe or something similar should be in your script.)

2. Backup the existing executable by renaming it to .bak (not sure if this is needed, it all depends if SMS can replace intelligently without additional scripting and programs) (This would also be part of your script...ie Copy file.dll file.old)

3. Copy the new executable down but not install it. (Again, part of your script...)

4. Inventory or Report that the new executable has been copied down by creating a MIF when it’s successful. (not sure how to do this) This can be done through SMS. Wise Installer has a nice feature where it creates the status mif automatically from you script. You first write the script, then compile the script into an EXE. When the script is executed through SMS on a remote machines, a MIF file is generated for reporting reasons. This MIF file has a name, by defualt, of the script EXE name. For example, if your EXE is called REPLACEDLL.exe, the MIF will be called REPLACEDLL.Mif.

You will have to configure SMS to use the MIF file. You can do this when you create the SMS package. There is a tab called Reporting. The only thing you have to set if the file name (REPLACEDLL.MIF) no path is needed.

-hope this helps...




Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)