Software Deployment

This question comes up time and again and the answer is - generally speaking - the same each time.

Perform the operation on a test VM/VPC/VirtualBox whilst running a lightweight capture tool e.g. InstallWatch. Incorporate the relevant changes into your package.

does InstallWatch create an msi i can use with sccm after ?

No, it's just a snapshot tool. You'll need to incorporate the relevant changes into your package.

How ? im new in this domain .... can you give me step or articale etc... that can help me

Thanks

From what exploring I've done in the VMWare client, it's configured by XML file content. Thus you'll need some scripting skills to write a script which can update XML files as well as packaging skills.

Long and short? Employ a packager. I don't have time (nor, I suspect, would most experienced responders here) to walk you through.

Don't you just love those helpful answers where they tell you to go hire someone? :)

So the first thing is... What exact version and VMWare application title are you trying to install?

Secondly, have you checked the Package KnowledgeBase on this site? http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=v

Your first thing is to make sure you can manually do what you need to do. Before trying to send it out via SCCM of course. If you can supply some of the info on the name and version, hopefully someone will chime in...

Hmmm...of 6,800-odd posts, I wonder what percentage contain that advice?

Anyway, the point is, sometimes you have to make a call. Look at the question and its follow-up (no offence, Pierre, BTW). Assuming that the OP has no authoring tool other than InstEdit/Orca since none is mentioned, much less no mention of the word 'transform', even a halfway competent packager will know that the hiring is the shortest route.

First install it normaly and setup the things you need (i.e remove updates, accept eula), copy the ini file from your profile to a central location.
Extract the vmware MSI file, install it with serial and so on as any other deployed msi, then make a simple script to copy the prefs ini file in to the user.

*edit*
Oh and read the KB's for how to install it.
*/edit*

Done.

//Eirik

That file is actually called 'preferences.ini', not 'prefs.ini' and, as mentioned here, is not in regular INI format. This thread also details how to disable checking for updates. Although it's about VMWare Player, VMWare Workstation uses the same files.

Using script to copy this file to user's profile folder is amateurish in the extreme. Either set up a user feature and move an existing feature which contains an adevrtised entry-point (e.g. an advertised shortcut) so that it becomes a child of the new feature or use Active Setup. The latter, of course, is a one-off set-up and means you won't get self-healing/repair for the user feature.

Actualy, I didnt call it prefsDOTini, i said "the prefs ini", as in prefs file, and that its an ini file.

And about the script to copy it, atleast it works, not everyone has the knowledge to make features or change packages, and therefor for them, a script (as most system administrators have used in some way at some point) to just copy it in to the users data folder is the easiest solution.

Also, you point to hiring someone to do it, guess what.. Not everyone has the funding to do that, and they actualy have to do things like this themself, even though its not part of theire everyday job, or what they have trained for.

And about the script to copy it, atleast it worksI'm willing to bet it has not a single line of error-trapping, though, eh? So, in other words, it "works" when the installation environment is perfect, in that world where nothing ever goes wrong, objects are never unregistered...Actualy, I didnt call it prefsDOTini, i said "the prefs ini",...which isn't very helpful for those whose primary language isn't English.not everyone has the knowledge to make features or change packages,LOL...they shouldn't be anywhere NEAR packages, then! Either do the job properly or not at all.You - supposedly, if we take your signature at face value - DO have the knowledge. You owe it to newcomers (and your own reputation, surely?) to promote the correct way to package, not how to create lash-ups/hacks.

ORIGINAL: VBScab
LOL...they shouldn't be anywhere NEAR packages, then! Either do the job properly or not at all.You - supposedly, if we take your signature at face value - DO have the knowledge. You owe it to newcomers (and your own reputation, surely?) to promote the correct way to package, not how to create lash-ups/hacks.


And your ranting, is so much more helpfull ;) Telling them to not do it... Yea good help.
Not everyone has the possibility/funding to get others to do it. They need a simple way to get it done, simply because they got told to.
Atleast I gave him an answer ;) Shure.. It aint the optimal way. Its a POSSIBLE way.
Since he has not said anything about how his knowledge level is, i gave him a simple answer, others could get another answer.
All depending on the question asked, and how its asked. ;)

It wont help anyone to tell them to use Features, if they have no idea what it even is ;) That just creates more work for them, instead of telling them how to do it in a general way, so they can get the BASE of how its done, and can do it in another way as they learn more :)

well we already install version 7.0 and i did a script to copy the ini file but we are starting to use sccm soon and yes im learning :-)

the thing is i want to upgrade the version 7.0 to 7.1 so with sccm i will have to run a script to uninstall the version 7.0 and then publish the version 7.1 ?

i was using the packager msi studio but since i have no to much success with this software and no help from them we decide to go with sccm for different reasons .....

Thanks

i will have to run a script to uninstall the version 7.0 No. The VMWare MSIs use the Upgrade table.

Before you get too far into this nonsense, I recommend you get a copy of Phil Wilson's excellent book (e-book?) The Definitive Guide To Windows Installer. You will get to know the fundamentals of Windows Installer which IMV is a pre-requisite before tumbling head-long into packaging.

After that, have your employer spring for a proper authoring tool. Realistically, there are only 2 players: Wise and InstallShield. Have a read on AD about the pros and cons of either: I shan't repeat my views here.

Hi 'i just did a quick test and when i try to install version 7.1 to upgarde version 7.0 it was ask to uninstall the version 7.0 before ...

Thanks

any idea why event my upgarde tables are the same in the propriety table it was ask to uninstall the other version first

Thanks