1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problem Problems applying MSI Group Policy updates from Server 2003.

Discussion in 'Software' started by Darkfunnyguy, Apr 27, 2011.

  1. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    Me and my IT Support co-workers are experiencing problems with the brand new desktop Fujitsu Esprimo E3521 pc as it does not apply MSI group policy updates from the Server 2003, only the group policy setting successfully applied.

    We the problem is with the onboard network adapter as the problem as we variety other Realtek drivers but does not work. We installed a D-Link network card and used it detected and used the Realtek 8139 driver rather the D-Link driver without any problems, the MSI group policy updates successfully applied through this PCI network card.

    We contacted Fujitsu support people and suggested an bios update which did but the onboard network adapter still not successful.

    So is anybody who has experience the same problem and know how to solved would greatly be appreciated.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  2. kevicho

    kevicho Gigabyte Poster

    1,219
    58
    116
    Do a search of the registry for items with the same name as the GPO you are trying to apply.

    Usually somewhere around here (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy)

    If it is listed in something along the lines of GPO history then delete these corresponding keys (usual registry changes can screw up your machine disclaimer applies - they will be listed as SIDs - do not delete the history key), then do a gpupdate /force

    These items should then run on the next reboot or two.
     
    Certifications: A+, Net+, MCSA Server 2003, 2008, Windows XP & 7 , ITIL V3 Foundation
    WIP: CCNA Renewal
  3. kevicho

    kevicho Gigabyte Poster

    1,219
    58
    116
    Also im assuming the GPO works with other machines, doesnt have WMI filters or some other security restriction in place.

    Also check the event log (System Log) for any failures
     
    Certifications: A+, Net+, MCSA Server 2003, 2008, Windows XP & 7 , ITIL V3 Foundation
    WIP: CCNA Renewal
  4. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    We built a new image using Xp Pro SP3 into the machine and created a test OU and put the computer in that container testing a fee msi updates to it so the computer it done from scratch.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  5. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    We have no problems with other brand pc's or laptops and we install new images from Ghostcast Server and apply msi update no problem, it just a recent order of 5 new Fujitsu E3521 machine is the problem, problem with onboard network adapter as I said msi gpo is successfully applied when a d-link pci network card is installed and suggested to our User support Manager this is maybe the best solutions as it won't apply when network cable is plug into the onboard network adapter.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  6. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    I entered a gpresult command and I get a message it these msi gpo is not applied as it filtered out.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  7. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    Apologized there is no WMI filter plus the msi gpo is applied through computer setting and the user setting is not defined so the filter out message in user setting is correct when I did a GPRESULT command. So it definitely not the gpo setting is the problem, most defintely the onboard network adapter.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  8. Sparky
    Highly Decorated Member Award

    Sparky Zettabyte Poster Moderator

    10,191
    299
    319
    Can you try a basic GPO and see if that works?

    Also have updated drivers etc. on the PC after the image has been installed? Perhaps it may be an issue with the image you are using.
     
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) Security+ Network+ A+
    WIP: Exchange 2007\2010
  9. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    We solved the problem. This how we did it.

    In registry editor we added a dword of GpNetworkStartTimeoutPolicyValue of decimal 200 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon.

    Also added a dword of DisableDHCPMediaSense with hexidecimal value of 1 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

    This policy setting specifies how long Group Policy should wait for network availability notifications during startup policy processing.

    We also created a .reg file and logon script .bat file but I believe there is a policy called Startup policy processing wait time will probably best way to go.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,
  10. Sparky
    Highly Decorated Member Award

    Sparky Zettabyte Poster Moderator

    10,191
    299
    319
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) Security+ Network+ A+
    WIP: Exchange 2007\2010
  11. Darkfunnyguy

    Darkfunnyguy Byte Poster

    195
    3
    22
    No definitely not as we also got this enable in our group policy computer settings before we fixed the problem.
     
    Certifications: A+, N+, MCP, MCDST, MCSA 2003
    WIP: Server+, Vista,

Share This Page

Loading...