Having a problem deploying the KACE Agent via GPO to windows 7 computers.
I am attempting to deploy the KACE Agent to several hundred Windows 7 computers in our local domain.
Here are the steps I have done so far.
1.)Copy and rename agent [ampagent-5.3.53177-x86_eskbox.xxxxxxxx.local.msi]
2.)Copy agent to file share on network that all users have access to.
3.)Configure GPO with the following settings:
Deployment Informationhide
General Setting
Deployment type Assigned
Deployment source \\172.x.x.x\Data\ampagent-5.3.53177-x86_eskbox.xxxxxxx.local.msi
Uninstall this application when it falls out of the scope of management Disabled
Windows Settingshide
Security Settingshide
Local Policies/Security Optionshide
Network Accesshide
Policy Setting
Network access: Sharing and security model for local accounts Classic - local users authenticate as themselves
User Account Controlhide
Policy Setting
User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode Elevate without prompting
User Account Control: Detect application installations and prompt for elevation Disabled
User Account Control: Run all administrators in Admin Approval Mode
Administrative Templateshide
Policy definitions (ADMX files) retrieved from the central store.Network/Link-Layer Topology Discoveryhide
Policy Setting Comment
Turn on Mapper I/O (LLTDIO) driver Enabled
Allow operation while in domain Enabled
Allow operation while in public network Disabled
Prohibit operation while in private network Disabled
Policy Setting Comment
Turn on Responder (RSPNDR) driver Enabled
Allow operation while in domain Enabled
Allow operation while in public network Disabled
Prohibit operation while in private network Disabled
4:)Applied the gpo to the test OU.
On the test machine. I reboot the machine and login with domain administative credentials.
Software does not install.
Group Policy Results report:
Component Status hide
Component Name Status Last Process Time
Group Policy Infrastructure Success 3/21/2012 10:11:03 AM
Group Policy Services Success 3/21/2012 10:11:02 AM
Registry Success 3/21/2012 10:09:33 AM
Security Success 3/21/2012 10:09:33 AM
Software Installation Failed 3/21/2012 10:11:03 AM
Software Installation failed due to the error listed below.
The installation source for this product is not available. Verify that the source exists and that you can access it.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 3/21/2012 10:11:02 AM and 3/21/2012 10:11:03 AM.
Windows Event Viewer reports:
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 : %%1612
And:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
And:
The install of application Dell KACE Agent from policy KACE Agent Install (internal) failed. The error was : %%1612
The computer is on the domain and can browse to the share without prompting for credentials.
The computer can resolve the share location by hostname and by IP Address.
The computer can run the msi from the location manually.
Any thoughts would be helpful.
Here are the steps I have done so far.
1.)Copy and rename agent [ampagent-5.3.53177-x86_eskbox.xxxxxxxx.local.msi]
2.)Copy agent to file share on network that all users have access to.
3.)Configure GPO with the following settings:
Deployment Informationhide
General Setting
Deployment type Assigned
Deployment source \\172.x.x.x\Data\ampagent-5.3.53177-x86_eskbox.xxxxxxx.local.msi
Uninstall this application when it falls out of the scope of management Disabled
Windows Settingshide
Security Settingshide
Local Policies/Security Optionshide
Network Accesshide
Policy Setting
Network access: Sharing and security model for local accounts Classic - local users authenticate as themselves
User Account Controlhide
Policy Setting
User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode Elevate without prompting
User Account Control: Detect application installations and prompt for elevation Disabled
User Account Control: Run all administrators in Admin Approval Mode
Administrative Templateshide
Policy definitions (ADMX files) retrieved from the central store.Network/Link-Layer Topology Discoveryhide
Policy Setting Comment
Turn on Mapper I/O (LLTDIO) driver Enabled
Allow operation while in domain Enabled
Allow operation while in public network Disabled
Prohibit operation while in private network Disabled
Policy Setting Comment
Turn on Responder (RSPNDR) driver Enabled
Allow operation while in domain Enabled
Allow operation while in public network Disabled
Prohibit operation while in private network Disabled
4:)Applied the gpo to the test OU.
On the test machine. I reboot the machine and login with domain administative credentials.
Software does not install.
Group Policy Results report:
Component Status hide
Component Name Status Last Process Time
Group Policy Infrastructure Success 3/21/2012 10:11:03 AM
Group Policy Services Success 3/21/2012 10:11:02 AM
Registry Success 3/21/2012 10:09:33 AM
Security Success 3/21/2012 10:09:33 AM
Software Installation Failed 3/21/2012 10:11:03 AM
Software Installation failed due to the error listed below.
The installation source for this product is not available. Verify that the source exists and that you can access it.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 3/21/2012 10:11:02 AM and 3/21/2012 10:11:03 AM.
Windows Event Viewer reports:
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 : %%1612
And:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
And:
The install of application Dell KACE Agent from policy KACE Agent Install (internal) failed. The error was : %%1612
The computer is on the domain and can browse to the share without prompting for credentials.
The computer can resolve the share location by hostname and by IP Address.
The computer can run the msi from the location manually.
Any thoughts would be helpful.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
ewagner
12 years ago
Two things come to mind:
1. "The installation source for this product is not available. Verify that the source exists and that you can access it." When the GP fires to install the agent, it is running under machine permissions, as opposed to when you run it yourself, in which case it is running under your user perms. Try assigning read permissions on the install directory to 'Everyone' and see if your error changes or disappears.
2. "The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly." This error would seem to imply that you have broader problems than this one GP. Are your other GPs working properly, especially other software pushes? If not, you might have to take a long hard look at your DNS setup....problems with AD are almost always DNS-related.
1. "The installation source for this product is not available. Verify that the source exists and that you can access it." When the GP fires to install the agent, it is running under machine permissions, as opposed to when you run it yourself, in which case it is running under your user perms. Try assigning read permissions on the install directory to 'Everyone' and see if your error changes or disappears.
2. "The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly." This error would seem to imply that you have broader problems than this one GP. Are your other GPs working properly, especially other software pushes? If not, you might have to take a long hard look at your DNS setup....problems with AD are almost always DNS-related.
