Re: Event ID 108
- From: "Dan DeStefano" <dan.destefanoATinfo-lutionDOTcom>
- Date: Wed, 8 Nov 2006 11:10:12 -0500
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?
The "All Users and Computers" GPO begins with "31B2F3.," so i assume it is
the Default Domain Policy renamed. 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?
"jx" <mc@xxxxxxxxxxx> wrote in message
news:uYS5KNdAHHA.4672@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Can you verify if you have policy in the SYSVOL\policies folder (you
should see a guid folder)? This could also be caused if you tried to
deploy a software package via GPO and did not share the folder where
software resided.
HTH
"Dan DeStefano" <dan.destefanoATinfo-lutionDOTcom> wrote in message
news:unlxRVcAHHA.3380@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- Event ID 108
- From: Dan DeStefano
- Re: Event ID 108
- From: jx
- Event ID 108
- Prev by Date: Re: Interview question Help.....
- Next by Date: Re: Event ID 108
- Previous by thread: Re: Event ID 108
- Next by thread: Re: Event ID 108
- Index(es):
Relevant Pages
|
Loading