Install issues with AdvanceAgent GPO

January 25, 2012, 8:04 am

≫ Next: Agents are dropping from the Management console

≪ Previous: WSCFG32 not installing services

$

0

0

I thought our GPO for the LANDesk 9 Agent was working fine but i'm I seem to be noticing an issue on some Windows 7 machines where the agent is not getting installed.

 

I recreated a new AdvanceAgent and confirmed the path to the .exe was correct.

 

I did gpupdate /force on my machine.

 

I get the following error in c:\windows\temp\AdvanceAgent.  This is from a previous attempt at installing the Agent. I dont see any new logs being created.

 

Fri, 20 Jan 2012 16:24:43 1616: Windows Platform 2, version 6.1 Service Pack 1

Fri, 20 Jan 2012 16:24:43 1616: Could not start ctrl dispatcher (0x00000427, 1063)

Fri, 20 Jan 2012 16:25:05 3552: Windows Platform 2, version 6.1 Service Pack 1

Fri, 20 Jan 2012 16:25:05 3552: Could not start ctrl dispatcher (0x00000427, 1063)

Fri, 20 Jan 2012 16:25:12 788: Windows Platform 2, version 6.1 Service Pack 1

Fri, 20 Jan 2012 16:25:12 788: Could not start ctrl dispatcher (0x00000427, 1063)

I checked under HKEY_CLASSES_ROOT\Installer\Products for an AdvanceAgent GUID to delete but couldnt find any.

Event Log is showing..

The assignment of application Advance Agent from policy LANDesk 9 Agent Install failed.  The error was : %%1274

The removal of the assignment of application Advance Agent from policy LANDesk 9 Agent Install 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.

I have also attached a screenshot of my GPO.  Any ideas? 

---

Agents are dropping from the Management console

April 15, 2013, 10:24 am

≫ Next: Advance Agent Installation Problem

≪ Previous: Install issues with AdvanceAgent GPO

$

0

0

So I have pushed out the new landesk 9.5 agent to existing 9.0 sp2 machines. The install completed fine and all the machines have been moved to the new server. I have shut down the old 9.0 sp2 server and now I am just using the 9.5 consoles. Everything was great until today , I have 25 clients that have dropped of the mamagement console. I still see their computer icons that represent the machines but it seems like I can't manage them anymore. It dosn't show the owner and it as if the machine is offline. When I walk over to the machine the agent and the remote access looks like its installed, See attached screenshot of the machines and their status. Granted the ones that show "offline" are online and pingable or unc accessable. 

Advance Agent Installation Problem

February 15, 2009, 8:00 pm

≫ Next: Query for LANDesk version

≪ Previous: Agents are dropping from the Management console

$

0

0

Hi,

 

We are currently experimenting with how to best deploy the Advance Agent for our environment (LD 8.8 SP2a - installed and running for about 12 months). As you already know LD now recommends using the Advance Agent for upgrading existing agents in the field.

 

I have created the Advance Agent - and have tried the following methods of deploying to a newely SOE'ed machine which when provisioned LANDesk installs the agent automatically since the machine was already in the inventory:

 

- GPO:  Set up a GPO with the Advanced Agent msi. Unit picks up the GPO and installs the msi, event log records msi started and then later records successfully installed, on the target machine Processes lists "TEMPldtemp.exe" as using 50% CPU. left machine for four hours, no agent deployed and still 50% utilisation on the CPU. Rebooted machine and everything back to normal except that the new agent configuration did not deploy. Event log indicates that the "msi installation was rolled back successfully".

 

- Push Install:  Advance Agent was 'pushed'  out to the machine using LANDesk, same results as above. Scheduled Tasks list the task as Successful and a result of  "The agent setup program ran successfully".

 

- Manual Install:  Ran the Advance Agent msi from the "\\core-server\ldlogon\AdvanceAgent" directory, agent installs as expected and within about 15 minutes. Processes change as expected and CPU utilisation varies during install.

 

I'm really pulling my hair out on this one. I can't imagine that I'm going to have to go to each machine and run it manually.

 

Has anyone got any suggestions...?!?!?!?

 

thanks,

 

Matt

Query for LANDesk version

January 29, 2009, 7:33 am

≫ Next: Agent deployment success but don't work

≪ Previous: Advance Agent Installation Problem

$

0

0

I am doing an agent install for 8.80 SP2A.  So I created a query based on who needed the patch, no problem.

 

Then I summed up those who have with those who needed and I didn't come up with all my devices.

 

Now I'm wondering if all the users didn't get SP2 and are on SP1

 

Can I create a query to find out what version of the agent is installed?

 

Thank you,

 

S.....

Agent deployment success but don't work

April 22, 2013, 2:09 am

≫ Next: UDD via Active Directory Security Group Memebership

≪ Previous: Query for LANDesk version

$

0

0

Hi,

 

The agent was successfull deployed. The icon is in the task bar of the client. (As you can see on the screenshot).

 

But on the core server, the client doesn't appear in "All device" and I can't do anything (remote control, ...).

As you can see there is just the server in the list.

I tried to drag and drop the client in the list of "All device", but he doesn't detect the LDAP user and show a "?" on the icon.

 

Can you help me?

 

Thanks.

UDD via Active Directory Security Group Memebership

April 16, 2013, 4:29 pm

≫ Next: Advance agent shared folder permission

≪ Previous: Agent deployment success but don't work

$

0

0

Greetings,

 

After carefully reading through the product manual and trying to find an answer in the forums, I have yet to find a solution in using an Active Directory "security group" -only- as a method for UDD. There are options for "NT Domain" and "LDAP", however neither seem to support anything other than a Top Level Domain, or an Organizational Unit, respectively. Every option in the Scanner Configuration pane is deselected except for which option I'm attempting to configure. We absolutely cannot perform a “ping sweep” function, too many networks.

 

1) If I navigate the UDD Scanner Configuration pane and choose "Discover device using NT Domain" without an IP range selected, and I enter a FQDN to the OU where I have unmanaged computers, it fails. Error is as such "The following error occurred while trying to connect to the server: Unknown error (0x80005004). Add anyway? (Yes) (No)." However if I only enter a top level domain, it succeeds but will scan every computer object in that domain.

 

2) If I navigate the UDD Scanner Configuration pane and choose "Discover devices using LDAP" without an IP range selected, and I enter the LDAP Distinguished Name for the security group (Canonical Name) as such “LDAP://corp.domain.com/CN=UniversalSecurityGroup,OU=Landesk,OU=Division,DC=Corp,DC=Domain,DC=com”, I can see right away in the Scanner Configuration pane that anything in the “Select individual OUs” list that starts with “CN=” is greyed out, and only “OU=” is highlighted. Scanning yields no results.

 

The idea is to have administrators in other domains easily add a Universal Group/Global Group to these machines, and UDD will find them based on membership. Ideas?

Advance agent shared folder permission

October 10, 2012, 12:46 am

≫ Next: Bulk add machines into inventory

≪ Previous: UDD via Active Directory Security Group Memebership

$

0

0

Hi,

 

I am deploying agent using the advance agent method. But during the deployment, I get this error from the AdvanceAgent.log:

 

Download failed to connect server - hs=0x80004005, try bypass proxy

Attempting to download file: \\xxxxxxxx

Couldn't download file \\xxxxxx, returned 80004005

 

I believe that the error 80004005 is because of shared folder permission. Do anyone have the list of user need to be entered in the share/ntfs permission?

 

Thanks.

Bulk add machines into inventory

April 26, 2013, 11:58 am

≫ Next: Prevent Uninstallation of Agent

≪ Previous: Advance agent shared folder permission

$

0

0

Is there a way to do this yet in 9.5? I have a bunch of machines (over 200) that are missing the agent. They have somehow alluded both UDD and GPO installs. I will troubleshoot those later but for now I just want them all added to LD so I can push the agent.

---

Prevent Uninstallation of Agent

February 1, 2013, 2:52 pm

≫ Next: Agent Status not Loaded

≪ Previous: Bulk add machines into inventory

$

0

0

Landesk 9.0.2.3

 

Is there a way to prevent the Landesk agent from being uninstalled from a machine by the user? Our users have admin access to their machines.

Agent Status not Loaded

October 12, 2012, 3:21 am

≫ Next: Visual C+ Runtime Error when trying to install agent

≪ Previous: Prevent Uninstallation of Agent

$

0

0

Hi everybody,

 

ok so here is my Problem,  I'm working on since two weeks already.

 

When I install an SP3 Agent on a new Machine (Windows 7 or XP) everything works fine for a few minutes. After 5 Minutes nearly every PC loses the Binocular in the Management Console and under Properties it shows "Common Base Agent Status" not loaded- but again, 5 Minutes before it was loaded.

Well at the beginning i thought that it is Windows 7 Problem- but it also came up on XP Machines. My second thought was that it could be our Image (the Agent is not included in the Image) but after installing our LD Software on a clean Windows 7 PC from CD it didn't work either or to be more specific... it worked but only for the famouse few minutes.

What did I try?

- Checking the Agent Settings but I don't find any Option that could be responsible for that Issue (or is there?!)

- Uninstalling the Agent with a /forceclean, deleting the Machine from the MMC and reinstalling the Agent... that works but again... only for a few Minutes =/

- Trying to execute the "cba8inst.msi". I found a Discussion on the Landesk Community where they say that this could help... but in my case it didn't.

- Comparing the Registry Entries of the Agents who work with those who don't but beside the ID's and some other indivudual characteristics, everything looks fine.

 

That what bothers me is the fact, that from 10 Installations in the same Network, on the same Hardware with the same Image, 1 or 2 Installations work. So therefore I can exclude the Firewall too.

The services are all started and the in the Eventviewer there are no Problems.

 

Now I know that most of you guys who are reading this are from Great Britain. Therefore I beg you to take out your Sherlock Holmes Pipe and to help me to resolve that case. 

 

Thank you for every answer in advance,

greetings from Italy

Visual C+ Runtime Error when trying to install agent

February 29, 2008, 12:01 pm

≫ Next: Error when going to video properties

≪ Previous: Agent Status not Loaded

$

0

0

 

Whether via Startup Script, or manual, when I try to run the install agent, I get the following error:

 

 

Title Bar: Microsoft Visual C++ Runtime Library

 

 

Runtime Error

 

 

Program c:\Documents and Settings\%username%\local Settings\Temp\$LDTemp$\wscfg32.exe

 

 

 

 

 

This application has requested the Runtime to terminate it in an unusual way.  Please contact the applications's support team for more information.

 

 

 

 

 

Anyone seen this before?

 

 

Error when going to video properties

January 30, 2012, 2:12 pm

≫ Next: Internal Error - Return Code 1208

≪ Previous: Visual C+ Runtime Error when trying to install agent

$

0

0

When trying to view the video properties I recieve an error.

 

Invalid Display Settings.  The currently selected graphics display driver can not be used.  It was written for a previous version of Windows, and is no longer compatible with this version of Windows.

 

I am using Windows XP SP3.

 

This error will go away if I uninstall the Mirror Driver and will reappear as soon as I load it back.

Internal Error - Return Code 1208

June 28, 2010, 1:15 pm

≫ Next: Query for LANDesk version

≪ Previous: Error when going to video properties

$

0

0

I have created an Advance Agent Default Windows Configuration for deployment of LanDesk 9.  We installed LanDesk on our D: drive on our core server.  I see the AdvanceAgent folder and the files created within the folder.

 

I tried to Push the Adv Agent to a Windows 7 machine and a Windows XP machine.  Both resulted in Failed: Status, An internal error occurred, Return Code 1208.  I've been searching for this error and haven't found anything to determine what this error is or a solution.  The Management Console for LanDesk9 in on our core server and hasn't been installed on our Tech's computers.  Our current version on our client machies is 8.80.0.249 and we are trying to upgrade to version 9.

Query for LANDesk version

January 29, 2009, 7:33 am

≫ Next: Agents are dropping from the Management console

≪ Previous: Internal Error - Return Code 1208

$

0

0

I am doing an agent install for 8.80 SP2A.  So I created a query based on who needed the patch, no problem.

 

Then I summed up those who have with those who needed and I didn't come up with all my devices.

 

Now I'm wondering if all the users didn't get SP2 and are on SP1

 

Can I create a query to find out what version of the agent is installed?

 

Thank you,

 

S.....

Agents are dropping from the Management console

April 15, 2013, 10:24 am

≫ Next: Common Base Agent Not Loaded

≪ Previous: Query for LANDesk version

$

0

0

So I have pushed out the new landesk 9.5 agent to existing 9.0 sp2 machines. The install completed fine and all the machines have been moved to the new server. I have shut down the old 9.0 sp2 server and now I am just using the 9.5 consoles. Everything was great until today , I have 25 clients that have dropped of the mamagement console. I still see their computer icons that represent the machines but it seems like I can't manage them anymore. It dosn't show the owner and it as if the machine is offline. When I walk over to the machine the agent and the remote access looks like its installed, See attached screenshot of the machines and their status. Granted the ones that show "offline" are online and pingable or unc accessable. 

---

Common Base Agent Not Loaded

January 15, 2013, 2:11 pm

≫ Next: LDMS 9 - Agent Failing when Pushed

≪ Previous: Agents are dropping from the Management console

$

0

0

Having a problem with the common base agent not loading onto some of our servers(Server 2003 and Server 2008). Does anyone have any idea why the agent would not be able to load from the deployment. We tried doing it through Unmanaged Device Deployment and through loading the agent directly on the server.

 

See attached image for details.

 

 

Thanks in Advance,

 

Matt

LDMS 9 - Agent Failing when Pushed

February 24, 2010, 8:00 am

≫ Next: How do we remove an agent?

≪ Previous: Common Base Agent Not Loaded

$

0

0

I have a question regarding my LDMS9 Test Environment. I've successfully discovered a device using Unmanaged Device Discovery within my small 2 PC / 1 Core test environment. After I discovered PC1 I wanted to push the Agent I created out to it. When I do so the Scheduled Task fails. It states Unable to contact the specified machine. The machine may be off or unreachable. Well, the machine is on and is pingable from the core. Anyone have any suggestions to why this may be failing?

 

Other notes: PC1 is a Windows 7 Machine and these computers are in a a WORKGROUP.

How do we remove an agent?

January 15, 2008, 10:44 am

≫ Next: Miniscan.exe Application Error

≪ Previous: LDMS 9 - Agent Failing when Pushed

$

0

0

I've been thru the manual, and can only find 1 or 2 instances of "remove agent", and hundreds of instances of either word by itself.

 

We have one user who is being harrassed by LD.  Every day LD wants to install some update/patch...even after we apply everything there is to apply manually, using remote control.

 

We don't know specifically what it's trying to install.  We thought for the moment that we'd just remove the agent.  But we don't know how.  I had seen LANDesk listed under Add/Remove SW on my PC, but when I connected to his, it wasn't there.  We're assuming that my LANDesk listing was for the console, rather than for the agent.

 

Thanks in advance for the assistance,

 

Tom

Miniscan.exe Application Error

April 17, 2008, 6:45 am

≫ Next: 9.5 - LANDesk Agent Deployment Upgrade "Agent setup program returned an error" (Push Deployment)

≪ Previous: How do we remove an agent?

$

0

0

 

After removing the 8.7 client and installing the 8.8 client I an getting Miniscan.exe Application Error.  The event log shows:

 

 

Faulting application MINISCAN.EXE, version 8.80.0.249, faulting module MINISCAN.EXE, version 8.80.0.249, fault address 0x00001702.

 

 

All Suggestions welcome!

 

 

9.5 - LANDesk Agent Deployment Upgrade "Agent setup program returned an error" (Push Deployment)

February 5, 2013, 7:12 am

≫ Next: Windows Embedded Standard Agent Configuration

≪ Previous: Miniscan.exe Application Error

$

0

0

Upgraded agents from 9.0SP3 to 9.5AllPatches and a good portion of the agents failed to update during the push deployment. The error received in the scheduled tasks window is "Agent setup program returned an error". I remember seeing this occasionaly the last time we did a deployment but rerunning the task on the computers that had failed generally came back successful. Not the case with 9.5.

 

Every machine that fails has the same symptoms, which leads me to beleive they are failing for the same reason. If you check the services on a computer that had a failed installation, the ONLY landesk services that are present are "LANDesk Targeted Multicast" and "LANDesk(R) Management Agent". A way to repair the agent on the computer, is that I can run Uninstallwinclient.exe then install the agent manually with a self contained exe and the installer goes through just fine. The problem is I cannot afford to do this on every single computer that has failed. I am still working on a way to identify all of the agents that did not install correctly. At the moment I am considering a loginscript vbs file that checks for the existance of the core landesk services.

 

I have attached the wscfg32.xlg file with the hops that someone can point out why the agent install is failing on so many machines. If any other information is needed please let me know.