Be sure that we’ll get there. The roadmap is pretty big and we’ll continuously add new features/functionality. We won’t copy competition… we have enough new things that we want to add in it, but still we have to keep our users happy :).
With all respect, Matt is describing/advocating a bloatware in my opinion.
1. It doesn't monitor or keep your software patched like Secunia PSI.
2. Start up manager.
3. It won't optimize Windows Services like Vista Services Optimizer.
4. It won't keep your drivers or software up-to-date for you.
It's pretty much like like making shortcuts to Windows features for your desktop.
I don't think so...
It won't let you do Windows Updates without Windows Updates turned on.
No software will. Microsoft won't let it as Windows Update is one of the major antipiracy tools of them.
Personally, I feel that 1 and 4 are crucial to CPM. Vulnerabilities are only fixed when updates are applied so it is very important to monitor installed software and report any vulnerabilities and updates that can fix these vulnerabilities.
So CPM turns an *.exe into an *.msi which can then be deployed within a domain? For example, if I installed CD (Dragon), made changes to the default settings, I could then re-package with these settings included?
Yes, but also the installable package makes a redistributable not only for .msi packages, but also for all the rest as long as it gets monitored. Indeed, the changes made during the install phase will be saved. As for the settings you customize for a application after you close the setup screen, they are also saved and will be successfully redeployed with your old settings.
Indeed it is.
For folks like me that perform regular installs of Windows and all the applications that are commonly used,it’s extremely useful to have a quick way to install pre-configured software. :-TU
But what settings are kept?
The installation path, the install options?
What more? For instance, Firefox profile is included? Settings made after the installation? Which ones? It could “import” settings in an .ini file?
The installation path - yes
The install options - yes [ both of them, as long as the installable package is redeployed on a machine similar in build ( x86 or x64 ) and os ]
If the .ini file or registry key firefox keeps it’s settings in is not created in a different folder than the ones created at setup time it will be redeployed along with the installable package - so yes, the settings file(s) will be redeployed successfully - we tried with 3.6.8, don’t know about firefox’s beta behaviour regarding it’s setting location. The regular mozilla usually stores it’s settings files in it’s install directory %PROGRAMFILES%\Mozilla Firefox\ or %PROGRAMFILES(x86)%\Mozilla Firefox\ and there should be no trouble restoring them to their initial state [ i’m referring especially to the settings made (changed) after install, at any time ]. So there is no need to import the .ini file.