StarwarsKidStarwarsKid
Seasoned Scripter
Registered: 2005-06-15
Posts: 506
Loc: Oregon, USA
No it's not. In fact, MSI packages are extremely easy to deploy with SMS 2003. When you want to create a new package from an MSI, just rightclick on the Packages container as select from the tasks menu something that says, "Create package from program OR Create program from package" (i'm not in the office now so I don't have the exact syntax.)
When you do this, a wizard will appear and it will walk you through the programm creation. SMS will discover several canned Programs from the MSI, which will cut several steps out of the process, including the syntax modifications of the text string you referenced.
_________________________
let the wise listen and add to their learning, and let the discerning get guidance- Proverbs 1:5
jtokachjtokach
Seasoned Scripter
Registered: 2001-11-15
Posts: 513
Loc: PA, USA
I've seen that option, but I didn't relate the word "definition" to MSI. Thanks!
While we're on the subject, I'm coming to SMS from WinInstall. WinInstall had/has great features that allowed logic to be used to determine whether packages were deployed (with detailed logging), such as: If my.exe version exists and version >= 1.0, then install NewPackage 1.0
or
If MyWinInstallPackage 2.0 is installed, then install NewPackage 1.0
I haven't found anything remotely like this in SMS. Is this to be handled at the MSI level?
_________________________
-Jim
...the sort of general malaise that only the genius possess and the insane lament.
StarwarsKidStarwarsKid
Seasoned Scripter
Registered: 2005-06-15
Posts: 506
Loc: Oregon, USA
I usually create a SQL query and apply that to a new COLLECTION that has the specific purpose of holding all computer accounts that adhere to the SQL query parameters.
For my organization, I've created a toplevel collection called, "_App Installations". Under that I have 2nd level collection containers that I name for each program I intend on upgrading/installing. The 3rd level collection container is specific to a certain upgrade/installation for that program.
So for example: I have a collection tree as follows - _App Installation>Symantec>Clients Needing AV 10.0.2.2020 Patch
I create an SQL query that searches the results of each computer's Hardware Inventory. Based on the query, all computers that do not have Symantec AV version 10.0.2.2020 but DO have version 10.0.2.2000 are members of this collection.
I then create a new program package based on the Symantec Patch ( I think it was an MSI so I used the package creation wizard), and then I assign an advertisement to the "Clients Needing AV 10.0.2.2020 Patch" collection.
I know the collection tree is a little deep being three layers for this patch, but when you're looking at deploying a lot of applications it helps to organize them in a way that is easy to traverse, and is logical.
Sometimes you'll find that you want to change the frequency of hardware inventory or require a full hardware inventory after a package is deployed in order to keep the membership of your software deployment collection up to date.
I hope that helps!
_________________________
let the wise listen and add to their learning, and let the discerning get guidance- Proverbs 1:5
