The removal of the assignment of application from policy failed the error was 2

RRS feed

  • Remove From My Forums

locked

Group Policy Application assignment errors 103 — «The removal of the assignment of application Java(TM) 6 Update 22 from policy Software Installations failed. The error was : %%2»

RRS feed

  • Question

  • I am getting this error for a few different applications all which are being pushed from GP.  I’m thinking maybe it is a computer rights issue to the GP?  Help would be appreciated. Thanks.

All replies

  • Hi,

    To better understand this problem, please help to collect:

    1. Does this error occur on all clients or users?
    2. Does it occur every time on one system? If not, what’s the result of disabling Fast Logon?

    If it happens every time, please refer to the following article to check your settings:

    Event ID 103 — Software Installation Processing
    http://technet.microsoft.com/en-us/library/cc727279(WS.10).aspx

    If it still occurs after suggestions above, please enable Appmgmt log for research:

    How to troubleshoot software installations with Windows 2000 application management debug logging
    http://support.microsoft.com/kb/249621

    Reproduce this issue and send Appmgmt.log file to
    tfwst@microsoft.com or post it here.

    Thanks.

    This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click «Mark as Answer» on the post that helps you, and to click «Unmark as Answer» if a marked post does not actually answer your
    question. This can be beneficial to other community members reading the thread.

  • I just disabled it now.  It was not set so I don’t know if this is going to change anything as I believe disabled is the default.  We shall see.  I’ll post back in a few days.

  • Hi,

    To better understand this problem, please help to collect:

    1. Does this error occur on all clients or users?
    2. Does it occur every time on one system? If not, what’s the result of disabling Fast Logon?

    If it happens every time, please refer to the following article to check your settings:

    Event ID 103 — Software Installation Processing
    http://technet.microsoft.com/en-us/library/cc727279(WS.10).aspx

    If it still occurs after suggestions above, please enable Appmgmt log for research:

    How to troubleshoot software installations with Windows 2000 application management debug logging
    http://support.microsoft.com/kb/249621

    Reproduce this issue and send Appmgmt.log file to
    tfwst@microsoft.com or post it here.

    Thanks.

    This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click «Mark as Answer» on the post that helps you, and to click «Unmark as Answer» if a marked post does not actually answer your question. This can be beneficial
    to other community members reading the thread.

    1.  Error occurs on the server

    2. Occurs every 5 minutes 2x on the server.

    I’ve checked the settings in that article prior to posting.  Everything is correct.

    I will look into this log thing on Monday.  Thanks.

  • Thank you for update. Waiting for your log files.

    Regards 

    This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click «Mark as Answer» on the post that helps you, and to click «Unmark as Answer» if a marked post does not actually answer your
    question. This can be beneficial to other community members reading the thread.

  • Hi,

    Is there any update?

    By the way, Group Policy Software Installation only occurs during computer startup and user logon. Software installation does not apply to computers or users during the periodic background refresh. So it should not occur every 5 minutes.

    Please replace this installation package and test with another package which works before to check if this problem was caused by the Java Installation package itself.

    Thanks.

    This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click «Mark as Answer» on the post that helps you, and to click «Unmark as Answer» if a marked post does not actually answer your
    question. This can be beneficial to other community members reading the thread.

  • This can be closed.

    So what was the resolution? I am having this same issue, we have around 120 pc’s and the application only successfully installed on 14 of them. The others are all getting this same error.

Источник

Problem SOLVED!

I was logging into client machines as domain user with Enterprise/Domain admin privileges and able to access a shared folder containing MSI installation packages without any problem. Though, at some point tried accessing it via IPshare_path_to_msi_packages_folder from another non-domain PC and kept getting a login pop-up.
Basically, even though one allows all domain and non-domain users/groups or ‘Everyone’ read/write permissions on shared folder it would still not work and prompt me for username/password thereby not allowing local client to pull down packages pointed by GPO. This is caused by anonymous access disabled by default. After enabling it and giving read/write permissions to MSI folder was then able to successfully deploy majority of packages and only synology-cloud-station-3.1.-3320.msi failed (need to look into it). I was also able to access the shared folder from any non-domain machine.

I was getting these error messages pretty much every 5 minutes in Events > System:

101
The assignment of application 7-Zip 9.20 (x64 edition) from policy DOMAIN base packages installation failed. The error was : %%1274

103
The assignment of application 7-Zip 9.20 (x64 edition) from policy DOMAIN base packages installation failed. The error was : %%1274

108
Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %%1274

1112
Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %%1274

Setup:

SERVERS DC1 (PDC) + DC2 (BDC) + DC3 (DBC)
Windows 2012 R2 Standard fully updated

CLIENTS
Windows 7 Pro SP1 (clean Dell restore, fully updated, conflicting packages such as old Adobe Flash uninstalled)

Have already tried on clients:

  • gpupdate /force
  • gpupdate /force /boot (both ask to reboot and throw error that policies have not been applied)
  • gpresult /r (looking good)
  • both servers and clients can access shared drive where MSI packages are stored
  • rebooted multiple times DC1 and clients after changes to GPO

GPO disable UAC:


* Computer Configuration
* Policies
* Windows Settings
* Security Settings
* Local Policies
* Security Options
ELEVATE WITHOUT PROMPTING: User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode
DISABLE: User Account Control: Detect application installation and prompt for elevation
DISABLE: User Account Control: Run all administrators in Admin Approval Mode


GPO deploy base software:
* Computer Configuration
* Policies
* Administrative Templates
* System
* Logon
ENABLE: Always wait for the network at computer startup logon
* Group Policy
ENABLE: Specify startup policy processing wait time (temporarily set to 120 will change to 30 later)


* Computer Configuration
* Policies
* Software Installation
* 7-Zip 9.20 (x64 edition) v9.20 Assigned LANIPUtilsSoftwareGPO7zip-7z920-x64.msi
* Google Chrome v66.41 Assigned LANIPUtilsSoftwareGPOgooglechromestandaloneenterprise.msi
* Mozilla Firefox (en-GB) v35.0 Assigned LANIPUtilsSoftwareGPOfirefox-35.0.1-en-gb-msi
* Synology Cloud Station v3.1 Assigned LANIPUtilsSoftwareGPOsynology-cloud-station-3.1.-3320.msi

All GPOs are placed in Group Policy Objects then linked from GPOs directly under our domain. Other settings such as IE restrictions from another GPO setup the same way apply to client correctly.

There is no other errors in AD, DHCP, DNS are working perfect, machines get IPs and can resolve names via nslookup as well as ping each other on IPv4/IPv6.

Источник

A client asked us to install LAPS and SCCM onto their server estate. We had two new VMs provisioned for us to get these applications on the network.

Starting off with the LAPS server, I use the SCCM server as the test client computer as all of the servers will need LAPS on them anyway. To try and shorten the story, after some fiddling, I get LAPS installed and working without much of a problem. I can find the password in the LAPS UI without a problem. Just to provide some additional details about the deployment, LAPS x64 and LAPS x86 (x64 exclusion) are assigned applications in one GPO, with the relevant LAPS settings changed in its own GPO. I square away any extended rights permissions and then decide to deploy the application out to the rest of the estate. This is where my problems start.

I asked the client to run gpupdate /force, restart their computer and then tell me their computer name. I plug the name they gave me into LAPS UI, no result. Not even an expiry date. Turns out the application had not installed on the computer. I log into the computer myself, run gpupdate, restart the computer then check the programs list. Still not there. I’m scratching my head, wondering what the problem could be. I thought it may have been the shared folder permissions, but I later ruled that out after remembering that I was able to deploy the application to the test server without any problem. I also checked if the GPO had applied in the first place with gpresult, it had, showing as an applied GPO with no failures of any sort. After a few more things of messing with security filtering and folder perms, I decide to log off that computer and try again on the server.

I uninstall LAPS from the test server and see if the server was the isolated scenario. Upon uninstalling it, I try a gpupdate to reinstall but get no restart prompt. I decide to restart the computer in case it needed to properly uninstall before it could reinstall again. Restart, try gpupdate again, no luck. I check the Programs Folder, the application is gone. And again, the GPO is showing as applied, but the application is still not installing.

I’m scratching my head here, I was supposed to have completed this LAPS installing in a single day as to not impose on the rest of the works, but this has provided a bit of a setback. The only thing I can think of at this point is to just start from scratch with a fresh LAPS server installation and new GPOs. Any insight is greatly appreciated.

Источник

  • 18th October 2018, 02:12 PM #1

    I’m trying to push out an msi (Geogebra) across our W10 stations, and have the MSI provided — which works fine when run manually

    When applied using GPO though, the client PCs all log the following:

    — The assignment of application GeoGebra Classic from policy GeoGebra 6 failed. The error was : %%1274
    — The removal of the assignment of application GeoGebra Classic from policy GeoGebra 6 failed. The error was : %%2
    — Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was : %%1274
    — The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.

    Now this is a Computer only policy, with the Software Installation pointing to the MSI, which is accessible on the network to all domain joined PCs. They have been rebooted umpteen times as well!

    Is this just a dodgy msi, manually installing is an option but a complete pain.

  • 18th October 2018, 02:19 PM #2

    Geogebra has been a pain since somewhere in the middle of it’s v5 update. It worked fine and then stopped deploying. I got around it by installing it as a startup script:

    Code:

    msiexec.exe /i \servershareGeoGebra-Windows-Installer-5-0-443-0.msi ALLUSERS=2 /qn

    It’s such a lightweight program that it adds very little to the startup time and I only deploy it in the maths classrooms.

  • Thanks to Mako from:

    Sheridan (18th October 2018)

  • 18th October 2018, 02:40 PM #3

    I’ve tried the script method as well — that logs no errors in the event viewer, but the application doesn’t install. I directed the msiexec to output a log file as well, but that just gets created as a empty file! Its literally empty so it looks like the msiexec command hasn’t even started

  • 18th October 2018, 03:04 PM #4

    Not much help but thank you for bringing this up, I was literally about to start working on GeoGebra but had half an eye on getting the maths staff to use the web version. This may be the line I now push to them if the newer versions aren’t deploying properly.

  • 18th October 2018, 03:09 PM #5

    Its a pain — manually install using a batch file or running the MSI directly and you’re fine. Using the msi with GPO just generates errors, and trying to install with a script weirdly does nothing for me, yet has worked for @Mako — although I’m using version 6 instead of 5

    Our maths department say the web version is missing the bit they need — so its on the build list for the next image.

    Its been a while since I pushed an MSI out, so I’m assuming the bulk of the problems will be W10 related.

  • 18th October 2018, 03:18 PM #6

    To be fair I’m not using v6 like you, and I’m also on Win7. I’ll try with v6 and see how it goes, although I’m working on something else at the moment.

  • 18th October 2018, 03:20 PM #7

    When manually installing, are there any user prompts? I’ve had that before with an MSI: a GPO deployment failing because the installation isn’t able to proceed unattended.

    It wasn’t GeoGebra, but we fixed our issue by creating a suitable MST transform file to go with the MSI (effectively working like an answer file).

    Last edited 18th October 2018 at 03:22 PM.

  • 18th October 2018, 03:23 PM #8

    Maybe consider installing PDQ Deploy on your server and use this for deployment? It has a very featured filled free version which should be useful for most deployments and certainly did well for me when setting up my networks.

  • 18th October 2018, 03:23 PM #9

  • 18th October 2018, 03:30 PM #10

    Other MSI’s have worked — just checked and we rolled out a package to W10 PCs in Easter this year. As for the manual install it doesn’t bring up any prompts at all — repackaging it might be an option. Shame there isn’t a portable version.

  • 18th October 2018, 03:32 PM #11

    I would guess that it’s defaulting to per-user install when installed via the GPO (which is why it works with «ALLUSERS=2» done via the startup batch file) so perhaps if you make an MST setting the ALLUSERS property to 2, and apply that on the MSI inside the GPO it might work?

  • 18th October 2018, 03:35 PM #12

    Just checked how we deploy it and there is a portable version available — https://wiki.geogebra.org/en/Referen…a_Installation

    We’ve used that and put it into our main image.

  • Thanks to jthompson from:

    Sheridan (18th October 2018)

  • 18th October 2018, 03:45 PM #13

    Nice one, I hadn’t even seen there was a portable version — giving that a try now.

  • 18th October 2018, 07:51 PM #14

    Quote Originally Posted by Sheridan View Post

    As for the manual install it doesn’t bring up any prompts at all

    That makes me wonder what context it works in/requires. When you ran it manually, were you in an elevated account, command prompt, ‘Run-As Admin’…?

    When you tried your script version, was that under a ‘Computer’ Startup Script, or ‘User’ Logon Script? The latter runs in the security context of the logged on user, the former runs as Local System (Admin) context.

    EDIT: With the above in mind, if you ran the script under the Computer GPO, you’d need to put the MSI file in a location that is accessible from the receiving computers Local System account ‘computer$’. The UNC path to the domain Netlogon folder should be fine. Running the script in User GPO just requires that user to have read/execute access to the MSI file.

    Last edited 18th October 2018 at 08:03 PM.

  • 18th October 2018, 08:17 PM #15

    GPO Msi deployment fails

    It�s in the computer startup scripts, but it mustn�t even start the msi as the log is empty, not even a startup message. Manual install is running the same batch file from file explorer, using run as administrator.

    Testing the portable version has had good results though, so I will probably just use that now as it does seem specific to this application.

    I suppose I could try building my own msi and trying that as well.

    • Источник

    Background:

    Windows Active Directory Domain
    Windows Server 2003R2 and Server 2008R2 Domain Controllers
    Windows XP SP3 and Windows 7 SP1 workstations

    Problem:

    Windows 7 workstations don’t process group policy software installation at all, or process intermittently. This doesn’t affect Windows XP machines.

    Following Events are recorded Windows System Logs:

    Event ID: 5719
    Level: Error
    Source: NetLogon
    Description:
    This computer was not able to set up a secure session with a domain controller in domain [domain-name] due to the following:
    There are currently no logon servers available to service the logon request.
    This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

    Event ID: 1129
    Level: Error
    Source: GroupPolicy
    Description:
    The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has succesfully processed. If you do not see a success message for several hours, then contact your administrator.

    Event ID: 101
    Level: Warning
    Source: Application Management Group Policy
    Description:
    The assignment of application [application name] from policy [policy name] failed.  The error was : %%1274

    Event ID: 103
    Level: Error
    Source: Application Management Group Policy
    Description:
    The removal of the assignment of application [application name] from policy [policy name] failed.  The error was : %%2

    Solution:

    The problem seems to be caused by a delay in initializing network and locating domain controllers. To resolve the issue we need to give system more time to initiate network before proceeding with the logon process.

    First of all try to enable «Always wait for the network at computer startup and logon» via group policy. This option is located in:
    Computer Configuration > Administrative Templates > System > Logon
    In our situation this option was already turned on.

    Issue was fixed by enabling «Startup Policy Processing Wait Time» and setting wait time value to 10 seconds.
    You may need to experiment with time-out values. Although in our situation 10 second was enough fix the problem, you may need to specify higher value.
    Enabling this option will increase client’s login time by specified number of seconds only if computer is genuinely disconnected from the network. In normal circumstances Windows will constantly check the connection status and as soon as it detects that link is up will immediately proceed with the logon process.

    There are two ways to enable this option:

    • Group Policy
      Computer Configuration > [Policies] > Administrative Templates > System >Group Policy > Startup Policy Processing Wait Time – Enable the option and set wait time to 10 — 60 seconds
      Note 1: This option is only supported by Windows Vista and later clients and may be not present on Server 2003 domain controllers
      Note 2: Group policy description tells that the default wait time is 30 seconds, which obviously raises the question how setting time-out to less than 30 seconds can fix the problem. It seems that default 30 seconds interval is not always used and Windows often employs its own algorithms to calculate the time-out (if it’s not enforced by Group Policy or Registry)
    • Registry
      On Client Computer:
      1. Start > Regedit.exe
      2. Navigate to  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon
      3. Create New DWORD value with name GpNetworkStartTimeoutPolicyValue and set Value data (decimal) to the required timeout interval in seconds
      4. Restart the computer
    Источник

    Понравилась статья? Поделить с друзьями:
  • The operation couldn t be completed com apple compressor compressorkit errordomain error 1
  • The operation could not be completed because an error occurred while exporting error 41562
  • The operation cannot complete because of an unknown error иллюстратор
  • The operating system denied access to the specified file как исправить
  • The opengl driver doesn t support wglchoosepixelformatarb как исправить