Windows Forum

Ask something
Discussion Locked

Software deployment using group policy

0 helpful
4 replies

by thetechguy

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are using Group policy based software deployment method for installing application softwares to client machines. We create a security group and add the msi package of particular software to the group. When any user requests a software we simply add his machine name to the security group and during the next reboot of the machine the software gets installed. This method is very effective and worked well for long time. Recently we are having problems with the software installations -- the msi pacakges are getting installed only after multiple reboots of the machine, typically 3 or 4 reboots. During that time folllowing errors/info is logged in Eventviewer in the same order.

1) Event ID : 301
Source : Application Management
The assignment of application Sybase12 Tools from policy xyz OU Application Policy succeeded.

2) Event ID : 102
Source : Application Management
The install of application Sybase12 Tools from policy xyz OU Application Policy failed. The error was The installation source for this product is not available. Verify that the source exists and that you can access it.

3) Event ID : 303
Source : Application Management
The removal of the assignment of application Sybase12 Tools from policy xyz OU Application Policy succeeded.

4) Event ID : 1000
Source : userenv
The Group Policy client-side extension Application Management was passed flags (1) and returned a failure status code of (1612).

KB artlcle Q278472 says the machine does not have permissions on package share. We checked it and all the permissions are proper and the same setup worked well before and now also after multiple reboots the msi packages are getting installed. Any help is appreciated.

4 replies

by quintar51

Can this user/computer access the share using \\server\share after logging into the domain?

by cul8rm8e

If what your saying here is that for each NEW client you add to the netwotk the (already applied) MSI packages have no problem installing, and, when you assign a NEW package to the network which will assign to all machines on the network, then you have to edit your GP for the refresh intervals of the DC and CLIENTS.

does some of your client machines install asigned software at point of assigning and others dont?

do all of your client machines refer to the error codes you mentioned?

some more info would be a help.

by thetechguy

the share is a dfs share and accessible for all the time. We have redundancy also(dfs share is replicated between two servers).

whether it is a new machine or exisitng machine the package is getting installed only after multiple reboots. This is happening for most of the packages and most of the machines.

This discussion is closed to new replies.