msi package installation problems

[Kbalert]

We are using Group policies for software deployment. We assign the msi
packages to machines so that the applications get installed on next reboot.

We have six OU's in our domain (Win2k domain with XP clients). In one of the
OU, we are seeing a weird problem when packages are assigned from the group
policies. The msi package does not get installed on first attempt. But
rebooting the machine multiple times (two or more times) install the
package. Surprisingly there is no problem in uninstallaing the packages.
They get removed on the first reboot of the user machine.

We are seeing the following errors on the user machines.

Event Type: Information
Event Source: Application Management
Event ID: 301
User: NT AUTHORITY\SYSTEM
Computer: ITG23
Description:
The assignment of application XYZ from policy ABC OU Application Policy
succeeded.

Event Type: Error
Event Source: Application Management
Event ID: 102
User: NT AUTHORITY\SYSTEM
Computer: ITG23
Description:
The install of application XYZ from policy ABC 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.

Event Type: Information
Event Source: Application Management
Event ID: 303
User: NT AUTHORITY\SYSTEM
Computer: ITG23
Description:
The removal of the assignment of application XYZ from policy ABC OU
Application Policy succeeded.

Event Type: Error
Event Source: Application Management
Event ID: 108
User: NT AUTHORITY\SYSTEM
Computer: ITG23
Description:
Failed to apply changes to software installation settings. Software changes
could not be applied. A previous log entry with details should exist. The
error was : The installation source for this product is not available.
Verify that the source exists and that you can access it.

Event Type: Error
Event Source: Userenv
Event ID: 1085
User: NT AUTHORITY\SYSTEM
Computer: ITG23
Description:
The Group Policy client-side extension Software Installation failed to
execute. Please look for any errors reported earlier by that extension.

Note that the same package gets installed after rebooting the machine
multiple times. The no.of reboots vary from two to five or six. This problem
is not present in other OU's. The package is hosted on a DFS path which is
accessible to all (everyone and NT AUTHORITY\SYSTEM have FULL permissions on
package hosting share).

I have checked the following KB articles.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274274

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q278472

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q815438

All of them talk about the user machine not having permissions etc, which
does not sem to be the isue in our case as rebooting the machine multiple
times installs the package.

Any help will be highly appreciated.

--Regards
Kbalert

[Dmitry Korolyov [MVP]]

This is the expected behavior on computers when Fast Logon Optimization ("Always wait for network at computer startup " in GP) is turned on.

--
Dmitry Korolyov [d_...@removethispart.mail.ru]
MVP: Windows Server - Active Directory

 

 

"Kbalert" <kars...@hotmail.com> wrote in message news:eTOLr2Ak...@TK2MSFTNGP15.phx.gbl...

[Kbalert]

If this is expected, then it should happen in all OU's, right?

Also, how to fix this.

"Dmitry Korolyov [MVP]" <d_...@removethispart.mail.ru> wrote in message news:ucmyCgCk...@TK2MSFTNGP15.phx.gbl...

[Dmitry Korolyov [MVP]]

Configure the setting I mentioned in the previous post to be Enabled. The system will always wait for network connections at startup (this is the same behavior as in Windows 2000).

--
Dmitry Korolyov [d_...@removethispart.mail.ru]
MVP: Windows Server - Active Directory

 

 

"Kbalert" <kars...@hotmail.com> wrote in message news:OgGcX0Ck...@TK2MSFTNGP09.phx.gbl...

[Kbalert]

I can check that setting for a single machine but when I tried to set that at OU level, I could not find the setting. ANy thing wrong?

"Dmitry Korolyov [MVP]" <d_...@removethispart.mail.ru> wrote in message news:e7hJsKEk...@TK2MSFTNGP10.phx.gbl...

[Dmitry Korolyov [MVP]]

You must have outdatet administrative templates in that GPO. Open the GPO from WinXP or Windows Server 2003 for editing - this will automatically update the .adm files stored in GPO, and you will see these settings.

--
Dmitry Korolyov [d_...@removethispart.mail.ru]
MVP: Windows Server - Active Directory

 

 

"Kbalert" <kars...@hotmail.com> wrote in message news:#IGEf8Lk...@TK2MSFTNGP09.phx.gbl...

[Kbalert]

I tried your suggestion but that did not fix the problem.

 

--Kbalert

"Dmitry Korolyov [MVP]" <d_...@removethispart.mail.ru> wrote in message news:ODSklX9k...@TK2MSFTNGP14.phx.gbl...

[Alfredo]

Hi Kbalert!

I had the same problem as yours. I am running Windows 2003 Environment and
Windows XP workstation.

I read "Dmitry Korolyov" answer to your question and he is right. I think
you are missing some steps on how enable the GPO in active directory. I can
give some steps, but I found all my unswers to this problem in a book called
"Group policy, profiles, and Intellimirror" by Jeremy Moskowitz. The answer
is in chapter 3.

Turning off windows XP Fast Boot

"Create and link a GPO (preferrable at the domain level) to simply enable
the policy setting named "Always wait for the network at computer startup and
logon".
This policy can be found:

Computer configuration / Administrative Templates / System / Logon branch of
Group Policy.

Rememebr, to force Windows XP machinmes to receive this computers policy (or
any policy), the computer account must be within the site, domain or OU at
which you set the policy. If you set the policy at the domain level you're
guaranteed that all Windows Xp machines in your domain will get the policy"
by Jeremy

After creating this policy you have to reset the computer in order for the
policy to take affect. Then when you assign application to a computer or
user, the application will be install after the first reboot.

Good Luck.