|
Yes, if you deleted and recreated the GPO, it would have a
different GUID. So I'm guessing that one of those packageRegistration objects is
the package you've deployed and one is a package that has been removed. I can't
think of any reason why software deployment would just fail like that, across
GPOs. Can you successfully deploy another package--say adminpak.msi--just to see
if its something with that media you're using?
Darren
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano Sent: Wednesday, November 08, 2006 11:09 AM To: [email protected] Subject: RE: [ActiveDir] Event ID 108 I did delete and
recreate the deployment GPO so that may be the reason for the 2 packages.
However, since the GPO was deleted and recreated, wouldn’t the new GPO have a
different GUID? If so, then why would the old package be in the new
GPO? Additionally, the MSI
packages is directly from the Outlook 2003 media that works fine when run
manually. Also, when I create other software deployment GPOs, they fail as well.
The AIP that I used to create the GPO is the exact same AIP used on a different,
w2k3 domain for a different client and it works fine. So I think the problem is
with software deployment GPOs in genera. Does that make
sense? OK, I will rename the
DDP back to the default. Dan
DeStefano From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Darren
Mar-Elia Dan- The 2
packageRegistration objects represent two separate packages. The MSI and MST are
referenced within the msiFileList attribute on each packageRegistration object.
Its possible that one of those packageRegistration objects is a "removed"
package--removed packages don't actually get deleted in AD--they just lie around
forever :-). So, I'm not sure why you're getting errors since it does appear
that the packages are getting created properly. Renaming the DDP is not
a problem for Windows, but it can be confusing to administrators looking at it.
I would rename it back to "DDP" to avoid any
confusion. Darren From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Dan
DeStefano Thanks for your
help. When I look in the
SYSVOL folder, I do see the software deployment policy I have created. I can
also see the policy in the \System\Policies AD container. There are 2
packageRegistration objects in the Domain\System\Policies\GUID\Machine\Class Store\Packages
container. I assume one is for the MSI and one for the MST, correct?
Yes, the “All Users and
Computers” GPO does begin with “31B2F3…” Also, there is a container named
“Default Domain Policy” under the System container in
AD. Does renaming the DDP
cause problems? Would it be advisable to name it back to
DDP? Dan
DeStefano From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Darren
Mar-Elia Dan- I would resolve the
problem before upgrading. It sounds like you have at least two things going
on. First off, the sw. deployment error sounds like something deeply wrong with
AD. The software installation data object referred to below is probably
something called a packageRegistration object, which should exist in AD under
the GPC portion of the GPO. The fact that you don't seem to have or be able to
fix the DDP GPO is strange. What is the GUID of the "All Users and
Workstations" GPO? If it starts with {31B2F3.., then its probably just the DDP
renamed. Darren From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Dan
DeStefano I am having a problem when deploying
applications via GPO in a Windows 2000 SP4 AD domain. The clients do not receive
the package and I receive Event ID 108 "There is no software installation data
object in the Active Directory". I have followed the recommendations
from http://eventid.net/display.asp?eventid=108&eventno=1181&source=Application%20Management&phase=1,
as well as from other MSKB articles, but without
success. I have deleted/recreated the GPO,
msi and mst packages, but the problem persists. This is a network I inherited and
when looking around in AD I noticed that the “Default Domain Policy” has either
been deleted or renamed because it no longer exists. The only policy bound to
the domain is one called “All Users and Workstations”, which I do not recognize
as a built-in policy. I have run dcdiag /fix and netdiag /fix on all DCs and
netdiag /fix on the test-deploy workstations, but this has not solved the
problem. Everything else with the domain
including authentication, name resolution, etc.. works fine, but I think this
error may be evidence of a larger problem with AD. We are planning on upgrading the
domain to WS2k3 within the next few weeks. Does anyone think that may fix the
problem? If not, would it be wise to put off the upgrade until this issue is
resolved? Thanks in advance for any
help, Dan
DeStefano If you have received
this message in error please notify the sender, disregard any content and
remove it from your possession. |
- [ActiveDir] Event ID 108 Dan DeStefano
- RE: [ActiveDir] Event ID 108 Darren Mar-Elia
- RE: [ActiveDir] Event ID 108 Dan DeStefano
- RE: [ActiveDir] Event ID 108 Darren Mar-Elia
- RE: [ActiveDir] Event ID 108 Dan DeStefano
- RE: [ActiveDir] Event ID 108 Darren Mar-Elia
- RE: [ActiveDir] Event ID 108 Dan DeStefano
