As per Microsoft: "When Group Policy is configured to assign a software installation package to client computers, the administrator must specify a share path that hosts the software installation files. If the specified share is located on a Microsoft Windows NT 4.0 file server, the software installation policy may not be successfully applied. When programs are assigned to a computer, the computer tries to access the software installation share by using the credentials of the computer account. Microsoft Windows XP-based and Windows Server-based computers require Kerberos authentication. Windows NT 4.0 is not Kerberos-aware and can provide only NTLM authentication. Therefore, authentication is unsuccessful". See ME323304
to resolve this problem.
If this error appears when you try to install Windows 2000 Service Pack 3 (SP3) Finnish on your Windows 2000 Professional-based computer, see ME813807
for a hotfix.
- Error: "Not enough storage is available to complete this operation" - From a newsgroup post: "I've seen this problem reported a few times. This is caused when some of the appmgmt client's local state gets “corrupted” (for unknown reasons). You should also see a message something like this in the log: "Cannot initialize the data structure for local script <GUID>". The GUID will highlight the identifier for the app which is causing the trouble. It's failing out because a registry subkey can not be found. This was considered something that would indicate a catastrophic failure somewhere, which is why the lame out of memory error code was chosen (because we figured it would never be hit anyway). Possible way to fix this is to find the troubling key. This will be under HKLM (computer policy) or the user's HKCU key (user policy) Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\Appmgmt\\<GUID>.
It's failing because one of these named values under that key is not present: "Deployment Name", "GPO ID", "GPO Name", and “Product ID". All of these are the bare minimum the client code needs to proceed. One remedy is to simply remove the <GUID> key. The appmgmt client will forget about the app in that case. Or you could fix up the missing value (all reg_sz) manually".
- Error: "Access is denied" - From a newsgroup post: "Make sure the share and NTFS permissions on the deployment path are setup to allow "Authenticated Users" read access otherwise you will get this error". See the link to Error code 0x5
for more details on "Access is denied" errors.
- Error: “The installation source for this product is not available. Verify that the source exists and that you can access it” - From a newsgroup post: "This is the expected behavior on computers when Fast Logon Optimization is turned on. Configure the setting “Always wait for the network at computer startup and logon” to be enabled to resolve this problem. The system will always wait for network connections at startup (this is the same behavior as in Windows 2000).
Turning off Windows XP Fast Boot.
Create and link a GPO (preferable 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 at Computer configuration -> Administrative Templates -> System -> Logon branch of Group Policy.
Remember, to force Windows XP machines to receive this 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 are guaranteed that all Windows XP machines in your domain will get the policy.
After creating this policy you have to reset the computer in order for the policy to take affect. Then when you assign an application to a computer or user, the application will be installed after the first reboot".