Jump to content

Recommended Posts

Posted

It seems everytime I edit a GPO in software installation it complains with this error

 

"Error no package in the software installation data in the active directory meets the criteria"

 

Its fine creating a new one, but its editing existing ones, for example I updated the with java update 18 yesturday, once I removed it from the list and tried to add the new one I would not add it, so I had to create another GPO just for Java to install.

 

It see that even when I make a new one, close it and try to add another packages it comes up with this error again

 

 

Seems the only way to is recreate a whole new GPO but this will always cause all the software to reinstall which we cant do

 

 

Any sugguestions?

Posted

funny enough I've just started to get this error on w2k8 DC's if I use a w2k3 DC I don't get the error.

 

Now I have'n done enough playing to see whether I still have a problem on w2k3 DC and just don't get the error message or whether its a w2k8 issue. as the article says the error message goes away if I create a fresh GPO, BUT this would be a BIG headache if I had to do this

  • 3 weeks later...
Posted

ok today I have just redone my pc running 2008 r2 that I am using for setting up the policys until we upgrade the servers to 2008r2

 

So nice and fresh install, all updates and latest drivers, just the group policy role installed, nothing else

 

Tried making a new policy, I put a few msi programs on the software list. Closed it, reopened it and tried to added another one, same problem and error again.

 

This is really anoying

 

There is some newer software we need to deploy, but I want to use the same group policy object, I dont want to keep making new ones. This needs to be sorted, I believe this happens in server 2003 now too (Need to double check)

Posted (edited)

There's a theory out there that suggests this is a bug mixed up with OLE32 and a function called CoInstall()[1]. Whether that is the case or not, they claim the problem goes away when *all* your DCs are 2008. As above, the workaround was running GPMC from an earlier OS - they used XP.

 

Do you all have one or more 2003 DCs then?

 

[1] Based on this MSDN search for CS_E_PACKAGE_NOTFOUND (which is the error code behind that message).

Edited by PiqueABoo

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...