Software Deployment

I got ur PM. Ok as far as I remember with Roxio packages, they do contain a Setup.exe as well as folders like RCPAudio, RCPData, MYDVD, Activation etc. Now you don't have to rely on the Setup.exe. Within each of these folders, Let say Audio, there is an MSI and language MST. Choose the language MST u want, let say English (1033.mst). This is where you can edit the MST to disable the registration etc. This way you can also choose the features that you don't want. Let say you want to leave out the MYDVD component.

I think the 1st step you should do is find out the sequence that the Setup.exe installs and uninstalls. This you can run it and then check the Event Viewer and see which gets installed first and second and etc. After that you do the same by using a batch file with the msiexec instead. In the batch you may suppress all reboots and have one reboot at the end of the install.

If I still remember, the MSI which holds the registry for the registration is in the folder RCP_Core. If you can't figure out, after installing, launch the app, use ProcMon to tell you which registry is modified. IT could be HKCU\Software\Roxio\Registration. Or it could be HKLM\SW\Roxio\Registration\RoxioCentral36 (RunRegApp) and try setting it to 0 or 1 and see whats what. You have test it out as I packaged it long time back.

From the original setup, the only thing you may delete is the Setup.exe, other files related to it like autorun etc and also the unused language transforms. Thats all. Don't delete anything else. There many versions of Roxio and some comes with OEM's but basically all comes back using the same install method.

Rest assured that the Setup.exe does nothing else than installing the MSI sequentially.Hope this helps.

This will help you, it has some info on the registration as well

http://itninja.com/link/microsoft-msde-home5

I would ignore the advice in the above and in the 'Package KB' articles, suggesting that you edit the supplied transforms. Create your own and just add it to the list specified via the command line in the TRANSFORMS property entry. Multiple transforms are specified in a semi-colon delimited list, e.g. TRANSFORMS="MyTransform.MST;YourTransform.MST;SomeoneElsesTransform.MST" http://msdn.microsoft.com/en-us/library/aa372085%28VS.85%29.aspx

ORIGINAL: VBScab
I would ignore the advice in the above and in the 'Package KB' articles, suggesting that you edit the supplied transforms.


If we are to edit the transform with one HKCU registry addition and a change of property value from Yes to No, I don't see the need to have a separate transform. After all, it's based on the same MSI and the only difference in the transforms are the language properties.

"Hello, Technical Support, Wayne speaking. How can I help you?"
"We're deploying Roxio using an edited version of your language transform and it's not working."
"[Insert the answer you expect here]"

Always, always, ALWAYS keep your hands OFF the vendor-supplied stuff wherever possible. That gives them no opportunity to take the cop-out route of saying that you're using a non-supported set-up. It really isn't hard to add your own transform, is it? Really?

LOL alright master I understand what you mean. Not to touch the vendor MST as well. No it's not hard but I was just wondering why Wayne? Has it something to do with Wayne Rooney becoming a dad few days back? haha JK

ORIGINAL: VBScab

I would ignore the advice in the above and in the 'Package KB' articles, suggesting that you edit the supplied transforms. Create your own and just add it to the list specified via the command line in the TRANSFORMS property entry. Multiple transforms are specified in a semi-colon delimited list, e.g. TRANSFORMS="MyTransform.MST;YourTransform.MST;SomeoneElsesTransform.MST" http://msdn.microsoft.com/en-us/library/aa372085%28VS.85%29.aspx


Thanks so much for your time and informative responses guys.

VBScab, 90% of what you suggest I do is new to me--but, I'm up for the challange! I downloaded Orca and used it for the first time last week so I'm still learning this application. But I understand that I need to learn how to edit and create my own Transforms. This is done with Orca I assume? How do I know what the command line/database entry information is for this registry stuff that pops up?

To me, this seems like a fairly simple thing to surpress in theory--and it actually sounds like it could be once I learn and understand what transforms are--but I know better, especially considering I'm a beginner here. I apologize in advanced for my ignorance.

One *can* work with Orca (actually, I prefer InstEdit http://www.instedit.com) but it's really for those who know what they're doing (no offence!) or for very quick and dirty edits.

Beginners are best advised to use a full-blown authoring tool. The fly in that particular ointment, however, is that they're quite expensive. The two principal players are Symantec/Altiris/Wise (Wise Package Studio and family) and Acresso (InstallShield AdminStudio and family). There are others but you'll find most readily-available information and help relates to these two.

Before you do any of that, though, you could do worse than get a copy of Phil Wilson's Definitive Guide to Windows Installer. Also browse the forums here, those on Symantec's Connect portal (WPS is buried a bit https://www-secure.symantec.com/connect/endpoint-management-virtualization/forums/wise-application-packaging) and take a look at John McFadyen's blogs on Windows Live.

Good news! Knowing that my supervisor would never approve a dime for this project (yet!) I began poking around our application server and found "Wise Installation Studio 7.0"--will this work?

I should mention that my deadline for this project is days away so I dont know if I have time for a book unfortunately. But that doesnt mean I won't pick it up for future use. :)

Is Wise fairly straight forward? Also, could you point me in the right direction on how to find out what I should be looking for to disable the registration dialog from popping up? Would it be in the 1033.mst?

Thanks!

I think WIS is more or less the same as WPS, in that it spits out MSIs. Without a license key, you get a fully-functional 30-day trial version, I believe.

The golden rule, generally speaking, is: leave anything that the vendor supplies alone. That includes MSTs. Besides, 1033.MST is just a (US English) language transform. So, create your own. I'm not sure if WIS includes InstallTailor but, if it does, you can use it to "record" your installation settings into a transform.

As for the registration-suppression etc., check the 'Package KB' http://itninja.com/link/microsoft-msde-home5 and this thread http://itninja.com/question/migrate-2000-professional-workstation-snmp224 and include the relevant changes into the transform you created above.

I think the best way to surpress this registration information pop-up from appearing is through a registry setting. The package Kb states:

If you want to supress the registration box at first startup this is the way:

When you start Roxio first time it will write this to the registry

[HKEY_CURRENT_USER\Software\Sonic\Registration\Roxio Central Core 3.0]
"RemindForNLaunches"=dword:00000005
"RemindAfter"=dword:00000003
"ShowRegistration"=dword:00000001 (If this stand to 00000000 no registration will come).
"ReminderCount"=dword:00000002
"Last"=dword:46dbe68a

You will have to make a reg file (OR script) that write these values right after the installation to the registry.

Though I'm tempted to use Wise, I would like to state one more time (just to make sure it's out there) that I'm using Ghost's Auto Installer software (which basically records a systems configuration before and after you make changes and spits out an .exe). If I were to set up the AI to monitor, install the Roxio software and make the registry changes, and then have it spit out an exe--that might be the way to go.

Tell you what, I will try it and report back with the details.

Eek! How do you manage uninstalls? Upgrades, patches? [shudder...]

We rarely uninstall software in our environement since 90% of the enterprise has the exact same software on their computers. We have a standardized image that I created that has that software already on it. Any specialty software is either distributed through AI (ghost console server) or SCCM. This image is updated every 3-6 months with software updates, but really it depends on what's needed and whether or not it's worth the time.

honestly our push and backup process is fairly well refined to the point that re-pushing a machine with the latest image is faster than uninstalling and reinstalling software (or roughly the same time depending).

All our users save their documents/data in the My Documents folder which is located on our NAS/SANS and backed up hourly (via snapshots) and nightly (via tape). We do create an image (backup) sometimes before we push the machines in case there might be some missing files, but it's hardly ever needed.

Updates are handled through our WSUS and SCCM servers.

Any luck, Warcrow?

I'm looking to add that same HKCU setting but I don't really have a method of doing so. I was able to deploy the product just fine through the supplies MSI's and then tweaking the supplied MST but I don't know how to add that HKCU setting. I've read some of the Self-Healing stuff but it explains things in a manner assuming you've already done similar deployments.

We have Altiris Rapid Installer which works similarly to your Ghost Installer but I try not to use it when possible because the snapshot method is horrible for deployment, especially for products like Roxio. When you install Roxio I believe it takes note of the type of burner you have. If we installed it via the snapshot method it may get confused when dropped on a machine with a different burner model.

Hi folks,
sometimes, it helps to search the Appdeploy Forum. ;-)
See: http://itninja.com/question/migrate-2000-professional-workstation-snmp224
There is the hole receipt, to do the job.
Good luck.
Regards, Nick