I am trying to install a package I created capturing a vendor setup. The package contains a service creation and a service start for that service.

When I install the package manually (being local admin) the service is properly created and started. Also when assigned in AD through a Computer based GPO the service is properly created and started.

However when assigned in AD through a User based GPO the service is (properly?) created but will not start. It does not matter whether the user is admin or not, either way the service won't start. If I try starting it using the MMC Services snap-in I get an error 1053: Service control request did not respond in a timely fashion. No enrty in the system event log is made for this failed service starting request.

Does anyone know what might cause this behaviour?

Thanx in advance...
Marcel Dingenouts
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Well it probably is not user rights so it might have something to do with the feature structure of the MSI. What I do is if I made my own setup capture is take all components and put them in the main feature. Then I delete all the empty features. This method might not work for some vendor MSIs but it at least ensures that the whole product is installed when a user clicks one of the icons related to the package. This can be useful when dealing with laptop users as they might need a portion of the application to install when they are not able to connect to the corporate network.
Answered 11/30/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
I don't think it is possible at all to snapshot a service, it needs a call to a Windows API Create Service

but there is many types of services.

Just like You can't snapshot a PnP device driver.

What about the vendor setup it might contain another option.

MSI files are some times wrapped into one setup.exe by vendor.

have you used filemon to see what or Setup /? Setup /A

Sweede ;-)
Answered 11/30/2004 by: Sweede
Second Degree Green Belt

Please log in to comment
0
You can snapshot a service as long as it is not running at the kernel level. I.E. device driver. There are ways to install those but MSI definately supports the installation of services.
Answered 11/30/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
I already did move all components to the main feature (allways do). And unfortunately the application is not an MSI wrapped in a setup: no msiexec proces is started during installation and in the Add/Remove Programs panel the application is shown with a single Change/Remove button.

Thanks for the responce, if you have any further thoughts let me know.
Answered 11/30/2004 by: MDingenouts
Senior Yellow Belt

Please log in to comment
0
Well I am not sure what the root problem is but does the service start after a reboot? You could just cheat and set the REBOOT property to FORCE. Or you might want to remove the ALLUSERS property from the MSI. Don't ask me why but I have had two installations where removing the ALLUSERS property fixed things.

Other than that I dunno what else to say other than something is wrong with your package. [8D]
Answered 12/01/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Already tried forced reboot. Did not check ALLUSERS however: it was absent (equals 0). Tried both setting it to 1 en 2, but neither made a difference. Guess I'm stuck with machine-based distribution.

Thanks for your input,
Marcel
Answered 12/02/2004 by: MDingenouts
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity