/build/static/layout/Breadcrumb_cap_w.png

Remedy client will not install via group policy

Hello,
I'm trying to get Remedy User v6 client to install using group policy on several XP computers. This same policy/package works great on Windows 2000 PC's, but on an XP computer it starts to install and then hangs for about 30 min. Finally it errors out and gets to the logon screen but the app doesn't install. The only entry in the event logs is:

Date: 5/8/2007
Source: MsiInstaller
Time 9:41:45 AM
Category: None
Type: Warning
EventID: 1001
User: NT AUTHORITY\SYSTEM
Computer A601972B
Description:
Detection of product '{DEC72C1F-8129-487A-8030-68CE6DBCFA01}', feature 'Complete' failed during request for component '{304FB251-7270-4E9B-9B17-BD538A97E1F9}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

Any thoughts on what might be causing this to fail on XP computers?

0 Comments   [ + ] Show comments

Answers (5)

Posted by: jllotz1 17 years ago
Senior Yellow Belt
0
This is still an issue for me! Can anyone help?
Posted by: alanho 17 years ago
Senior Yellow Belt
0
Is the MSI a native MSI or has it been repackaged? If it has been repackaged, have you tested it outside of your AD/GPO scenario?
Posted by: jllotz1 17 years ago
Senior Yellow Belt
0
Thanks for your response.
It was repackaged in-house several years ago. I have since repackaged it several times in an attempt to fix the issue of it not installing on XP, but I got the same result.
I have not tested it outside of our environment.
The package works fine on XP if you run it manually (after you are logged on to the PC), but it just won't push.
Posted by: alanho 17 years ago
Senior Yellow Belt
0
I can only assume that the application (or a component of the application) cannot be installed by the SYSTEM account. Have you tried setting up the package under User Configuration instead of Computer Configuration? This would force the package to install after a user has logged on.
Posted by: jllotz1 17 years ago
Senior Yellow Belt
0
I just tried that, but it didn't make any difference. It still hangs as it's trying to install, and I get the same error in the logs.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ