Re: msi package installation problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kbalert (karsudha_at_hotmail.com)
Date: 09/01/04 

Date: Wed, 1 Sep 2004 19:37:57 +0530

If this is expected, then it should happen in all OU's, right?
Also, how to fix this.
  "Dmitry Korolyov [MVP]" <d__k@removethispart.mail.ru> wrote in message news:ucmyCgCkEHA.1800@TK2MSFTNGP15.phx.gbl...
  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__k@removethispart.mail.ru]
  MVP: Windows Server - Active Directory

    "Kbalert" <karsudha@hotmail.com> wrote in message news:eTOLr2AkEHA.1348@TK2MSFTNGP15.phx.gbl...
    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

Relevant Pages

  • Re: msi package installation problems
    ... The msi package does not get installed on first attempt. ... Event Source: Application Management ... The install of application XYZ from policy ABC OU Application Policy ... Failed to apply changes to software installation settings. ...
    (microsoft.public.windows.group_policy)
  • Re: JRE Mistake - Help
    ... applied a GPO to assign the package via user software installation to only ... Although the policy had "uninstall when falls out ... The new policy's installation routine succeeds, it does not have "uninstall ...
    (microsoft.public.windows.group_policy)
  • RE: Deploying a .msi
    ... because I can access the installation file just fine once I'm logged ... Event Source: Application Management ... from policy WMP 11 Policy succeeded. ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • Re: msi package installation problems
    ... The msi package does not get installed on first attempt. ... Event Source: Application Management ... The assignment of application XYZ from policy ABC OU Application Policy ... The installation source for this product is not available. ...
    (microsoft.public.windows.group_policy)
  • Re: msi package installation problems
    ... It sounds like a network connectivity issue during startup. ... for network" thing won't happen until policy is applied which won't happen ... > Event Source: Application Management ... The installation source for this product is not available. ...
    (microsoft.public.win2000.group_policy)