Software Deployment

I completely disagree. You should ALWAYS restart after a capture. Failure to do so could result in, for example, the failure to capture any files which were updated but in use at capture time (plus, of course, you'd capture the 'PendingFileRenameOperations' registry entry).

Agree with VBScab, you should ALWAYS include the reboot in your capture if the application install asks for it. Then go through the registry and clear out the obvious stuff, like TCPIP update keys and anything your not sure off at this point you can then check agaisnt a clean machine to see if the keys exists already and can be safely cleanred out the resulting MSI.

P

...if the application install asks for it. I reboot anyway. I've been caught out in the past by vendors omitting to add one to their set-up EXEs, it's just habit nowadays.

Thats just experiances though, aint had an application that has failed to work when it hasnt requied a reboot, so far at least :)

P

Hi, I have tried going through the process as described by zipsantro but I get the same error. The error occurred right at the end of the after snapsh for the base PC (before restart), it's as though the after snapshot isn't completing. I get a box with the title "Conversion Error" and the error code inside the box "Error processing service LightScribeService: service executable file LSSrvc.exe not found in package."

any other idea's?

I have a print screen image that I have wanted to attach to this message so that you could see the error for yourselves but apparently the file attachment feature is disabled or I do not have sufficient permission to add an attachment

thanks

Is the LSSrvc.exe in the package, also check in the Services section in Wise (is your using Wise) also as VBScab has said always reboot with every package you create.

unfortunately im not using Wise as I do not ahve the software!! Im using Winstall,

I could try the wise software if I could lay my hands on a copy, but at the moment Im not using it. Any idea's on how to get round it without wise?
As for "is the LSSrvc.exe in the package", how can I check that?

Wait a second...isn't this all somewhat moot? Isn't Nero already supplied in MSI form? Although it might *appear* to be an EXE, I thought it extracted an MSI. If that's the case, you only need a transform: re-capturing MSIs is a really bad idea.

- Clear your %TEMP% folder
- Run the Setup.EXE and pause at the first screen.
- Check your %TEMP% folder for an MSI.
- Copy this MSI, renaming it to something sensible along the way, to your staging/project area
- Use your packaging tool to create a transform for this MSI

Wait a second...isn't this all somewhat moot? Isn't Nero already supplied in MSI form? Although it might *appear* to be an EXE, I thought it extracted an MSI. If that's the case, you only need a transform: re-capturing MSIs is a really bad idea.

- Clear your %TEMP% folder
- Run the Setup.EXE and pause at the first screen.
- Check your %TEMP% folder for an MSI.
- Copy this MSI, renaming it to something sensible along the way, to your staging/project area
- Use your packaging tool to create a transform for this MSI ORIGINAL: VBScab

Wait a second...isn't this all somewhat moot? Isn't Nero already supplied in MSI form? Although it might *appear* to be an EXE, I thought it extracted an MSI. If that's the case, you only need a transform: re-capturing MSIs is a really bad idea.

- Clear your %TEMP% folder
- Run the Setup.EXE and pause at the first screen.
- Check your %TEMP% folder for an MSI.
- Copy this MSI, renaming it to something sensible along the way, to your staging/project area
- Use your packaging tool to create a transform for this MSI



Cheers VBScab, I tried that already but still get the same error message. I tried the transform in orca following the intructions given by someone else above

TBH, if you're re-packaging the MSI, you're on your own. It's a really, really bad idea.

As for how you can check if "the LSSrvc.exe in the package", check for its presence in the File table using Orca (IIRC, WinInstall has no facility to directly edit the tables.) I'd wager it won't be there, because the engine already told you it wasn't in the package.

At this moment, you have captured entire installation process including restart of PC.
Ideally speaking doing so may require lot of fine tune of you MSI as captures other unnecessary chnages during restart. Best practice to capture application require restart is don't capture restart.
1. Take a before snapshot of your machine.
2. Install your application and skip restart.
3. Take a after snapshot of your machine.
4. Create your MSI(base) and save it.
After this step experinced packagers won't capture restart as they will identify what are teh changes application is going to make after restart. As i see you are at your beginning level. I suggest you to perform the below steps.
5. Again take a before snapshot and restart you computer manually.
6. After restart launch application and take after snapshot.
7. Create your MSI(restart) and save it.
Now from here take backaups of your MSIs and figure out application related changes in your restart MSI and incorporate those things to your base MSI.
About services, you need to understand how Windows Installer understand and behave.
Make sure that you use ServiceControl and ServiceInstall tables. Kindly go through MSDN for full details.

Cheers!
Santro.