Software Deployment

There is a known issue that is listed in the release notes for 5.4

3316: The installation of the 5.4 Agent using GPO (Group Policy Object) fails when the language of theclient machine is not Traditional Chinese. This is because the 5.4 Agent installer supports multiplelanguages and GPO arbitrarily chooses the language with the lowest locale ID (LCID) as the default,which happens to be Traditional Chinese. To resolve the issue, change the locale ID of the installer tothe appropriate locale. To obtain a script that changes the locale ID, contact Dell KACE Technical

As luck wouldn't have it, we fixed this through a Microsoft call. It turns out that synchronization wasn't happening between all of our Domain Controllers. Once this issue was fixed the GP push started working like a champ. The instructions worked just fine, it was our AD that was slightly broken.

Where did you put the msi that you are calling?  We put our's in a subdir under the domain netlogin directory, then there were no rights issues.

It might be related to where the MSI is located, do you have it set in a spot where everybody has access? For our main site, and our remote sites we place ours on the file server's software folder which is shared out.

You have tried a GPupdate /force on a machine in the test group right? I just recently upgraded all our KACE Agents via GPO and when I was testing it prompted me to restart after a GPupdate and it uninstalled the old (or upgraded, I don't know) and installed the new agent then.

So I used the VB script to alter the locale of the msi file successfully, or so it said anyways. I then changed the file name to match the hostname of our K1000 per instructions. Our KBOX operates inside of our network only, so the msi filename is ampagent-5.4.5315-x86_helpdesk.msi . If I drop it into a command line with /qn on the end it will install the agent silently and the computer reports to the KBOX. The trick is when I get to creating the GPO. I follow the directions to set up the GPO which is straight forward enough. I even used the UNC path to my share that everyone has access to. When I run gpupdate /force on my test vm (placed in my test OU where the GP is active and enforced) I get the failure text shown below.