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

February 5, 2013, 7:12 am

≫ Next: WSCFG32 not installing services

≪ Previous: Update agent settings via a Policy

$

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.

---

WSCFG32 not installing services

July 10, 2008, 1:52 pm

≫ Next: Scheduled Tasks never complete in LD 9.5

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

$

0

0

After an OSD script with Sysprep runs, our machines run wscfg32.exe with the standard switches (used LD wizard to create the OSD scripts).  The agent gets installed, but there are some services missing.  Specifically:

 

-LANDesk Policy Invoker

and

-LANDesk Out of Band Monitor Service (about 50% of the time installs fine)

 

Once the machine reboots and is all checked in with the Core, if I push the same Default Agent config as a scheduled task the services are then installed properly.  Basically I've had at least 50 machines roll out recently that do not have these services installed.

 

Any idea why wscfg32.exe isn't creating these services?  This hurts us because we use the Software Deployment Portal pretty frequently as well as policy-based software distribution.

 

We're on 8.8.  Thanks.

Scheduled Tasks never complete in LD 9.5

April 9, 2013, 9:01 am

≫ Next: Mirror Drivers disable Windows Aero on Windows 7 64 bit

≪ Previous: WSCFG32 not installing services

$

0

0

I've deployed new 9.5 agents to all of the computers in the company recently. A problem has come up where my scheduled tasks never complete. The computers in the task will say for instance 14 active 3 pending at 10 failed. The task stops changing or updating the information once it gets a certain point. Restarting the scheduler service on the core allows me to alter the task and restart it but the information never changes. It still says there are 14 active 3 pending and 10 failed computer even after restarting the scheduler. The only way to reset the information is to delete all the devices from the task.

 

How can I get the scheduled tasks to finish and to update the task info/graphs with the proper information?

Mirror Drivers disable Windows Aero on Windows 7 64 bit

January 25, 2010, 10:03 am

≫ Next: Getting LDLOG.exe error on clients

≪ Previous: Scheduled Tasks never complete in LD 9.5

$

0

0

I discovered that if you install an agent using the Remote Control Mirror drivers on a Windows 7 64 bit pc it disabled the Windows Aero feature.  This was not the case on a 32 bit Windows 7 machine.  The machines I used were a Dell 755 (64bit) and a Dell D820 laptop (32bit).  Just wanted to pass this on should anyone else see it.  Once I changed the client and rebooted Aero started working again.  This was a version 9 client.

Getting LDLOG.exe error on clients

July 21, 2011, 8:28 am

≫ Next: Unable to deploy the LANDesk windows to client Machines

≪ Previous: Mirror Drivers disable Windows Aero on Windows 7 64 bit

$

0

0

Has anyone seen this issue happening on Windows 7 and XP computer???

Unable to deploy the LANDesk windows to client Machines

March 27, 2013, 5:48 am

≫ Next: Update agent settings via a Policy

≪ Previous: Getting LDLOG.exe error on clients

$

0

0

HI Team,

 

I unable to install the LANDesk windows agents to client machines thru LANDesk, getting an error failed to build the agent installation Package, Can someone pls help me to resolve this issue.

 

Regards

Srinath YN

Update agent settings via a Policy

February 2, 2010, 5:29 am

≫ Next: Agent Deployment error (0xC0000471)

≪ Previous: Unable to deploy the LANDesk windows to client Machines

$

0

0

Hi All

 

LDMS 9.0

 

We have many machines that communicate to the Core Server only over the Management Gateway, these computers will never be on the network.

 

I want to update some of the agent settings for these machines. When I create a "Schedule update to agent settings" task, I don't have the option of choosing the delivery method, it is set as a push only.

 

As I cannot push to machines over the Management Gateway, how do I update the agent settings for these remote machines?

 

Has anyone else solved this problem? Is there maybe a script that could be scheduled as a policy to do this?

 

I am hoping that the answer is not that I have to install a full agent every time.

 

Cam

Agent Deployment error (0xC0000471)

February 19, 2010, 2:56 am

≫ Next: LDMS 9 - Agent Failing when Pushed

≪ Previous: Update agent settings via a Policy

$

0

0

When I'm deploying some agent, i'll the wscfg32.exe process will be terminated with statuscode 0xC0000471.

This also happens when i run it from ldlogon share without any installation options.

When it's run from scheduled task the return code is "successfull".

But there ain't get any files copied/installed !!

 

According to ntstatus.h in winsdk the errormsg  says :

STATUS_INVALID_CRUNTIME_PARAMETER #An invalid parameter was passed to a C runtime function.

 

This happens only at a view machines. Didn't find any shared issuses on that computers. (different software, OS: Win7 64 and XP32)

Since this sounds for me like an .net related problem. I tried to update all .net frameworks, removed all VisualC++ runtimes and installed that ones from ldlogon shrare.

Doesn't get any further. (also disabled virus scanner )

 

 

Does someone have same problem, hints or solutions ?

Thanks in advance!

 

System info : running LDMS 9.0 on windows server 2003 standard 32bit in vmware, with external oracle db.

---

LDMS 9 - Agent Failing when Pushed

February 24, 2010, 8:00 am

≫ Next: agent deployment on different domain & failed inventory scans

≪ Previous: Agent Deployment error (0xC0000471)

$

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.

agent deployment on different domain & failed inventory scans

July 7, 2011, 2:10 am

≫ Next: Advance Agent Failure - cba8cleanup.exe missing

≪ Previous: LDMS 9 - Agent Failing when Pushed

$

0

0

Good morning,

 

I'm trying to push an Agent configuration to a site we have that's on a different domain (Unfortunately SBS 2003 so no domain trust possible). I've added in credentials for this domain to the Scheduler.

 

My plan was to push the advance agent via GPO, which works up to the point of installing the full agent but goes no further. (advance agent msi installs & copies the full exe from our core servers ldlogon folder). Information on the cleint from c:\windows\temp\advanceagent.log as follows:

 

Wed, 06 Jul 2011 16:21:54 Create process succeeded - "C:\Program Files\LANDesk\LDCLient\cba8cleanup.exe" /w /g

Wed, 06 Jul 2011 16:21:54 Unable to create process - C:\WINDOWS\TEMPldtemp.exe

Wed, 06 Jul 2011 16:54:28 3148: Starting Stop

Wed, 06 Jul 2011 16:54:28 3148: Stopping: Unable to control service. Error: 1062

Wed, 06 Jul 2011 16:54:28 3640: Starting Unregister

Wed, 06 Jul 2011 16:54:28 3640: Starting Stop

Wed, 06 Jul 2011 16:54:28 3640: Stopping: Unable to control service. Error: 1062

Wed, 06 Jul 2011 16:54:28 3640: Successful Unregistered service

 

As an alternative I've tried installing the full agent on a test machine; this works up to the point of trying to run an inventory scan, when I am given the following error:

 

"Application has failed to start because elogapi.dll was not found. Re-installing the application may fix this problem"

 

I can only find elogapi.dlm in \windows\system32 on the test client; reinstalling the agent makes no difference. Running an inventory scan from the core fails and gives the result "Unknow Status code (0xC0000135,0:309)

 

The agent has been tested and known to work correctly on the domain where our core server is located, so I assume this is related to permissions used to install.

 

Any advice would be appreciated on this matter.

 

Many thanks

David

Advance Agent Failure - cba8cleanup.exe missing

April 16, 2013, 9:40 am

≫ Next: Agents are dropping from the Management console

≪ Previous: agent deployment on different domain & failed inventory scans

$

0

0

I am trying to create create an Advance Agent but the background process fails.

 

Looking at the log I see:

 

FCIAddFile() failed(cba8cleanup.exe): code 1 [Failure opening file to be stored in cabinet]

 

Add File [cba8cleanup.exe] failed!

 

MakeCAB failed

 

 

When I search for cba8cleanup.exe on all the drives on the core.  I cannot find it.  Any ideas how I can restore it?

 

Thanks,

 

Jim

Agents are dropping from the Management console

April 15, 2013, 10:24 am

≫ Next: UDD via Active Directory Security Group Memebership

≪ Previous: Advance Agent Failure - cba8cleanup.exe missing

$

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. 

UDD via Active Directory Security Group Memebership

April 16, 2013, 4:29 pm

≫ Next: Discovering computers with Windows 8

≪ Previous: Agents are dropping from the Management console

$

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?

Discovering computers with Windows 8

February 1, 2013, 4:05 pm

≫ Next: Uninstall for Windows 7 64-bit

≪ Previous: UDD via Active Directory Security Group Memebership

$

0

0

I did a searchon my networkwithLANDesk9.0 SP2versionand discoveredcomputerswith Windows 8but inthenameof the operating systemmarks it asunknown, you know how to correctthis problem?

Uninstall for Windows 7 64-bit

February 11, 2010, 3:32 pm

≫ Next: Advance Agent Failure - cba8cleanup.exe missing

≪ Previous: Discovering computers with Windows 8

$

0

0

A couple of our techs deployed some Windows 7 machines before we had a chance to modfy GPO which deploys the LANDesk agent. The WinClientUninstall.exe doesn't properly uninstall on 64-bit Windows 7. Some files remain in %programfiles%\LANDesk\Shared and a service is not uninstalled.

 

Is there a better uninstall available? We're still on 8.8 SP3. Is the uninstaller in 9.0 any better

---

Advance Agent Failure - cba8cleanup.exe missing

April 16, 2013, 9:40 am

≫ Next: Agent settings for security and compliance manager

≪ Previous: Uninstall for Windows 7 64-bit

$

0

0

I am trying to create create an Advance Agent but the background process fails.

 

Looking at the log I see:

 

FCIAddFile() failed(cba8cleanup.exe): code 1 [Failure opening file to be stored in cabinet]

 

Add File [cba8cleanup.exe] failed!

 

MakeCAB failed

 

 

When I search for cba8cleanup.exe on all the drives on the core.  I cannot find it.  Any ideas how I can restore it?

 

Thanks,

 

Jim

Agent settings for security and compliance manager

May 3, 2010, 7:47 am

≫ Next: Policy Invoker not starting after Agent Install from GuiRunOnce

≪ Previous: Advance Agent Failure - cba8cleanup.exe missing

$

0

0

Hello,

 

When configuring the agent I have security and compliance manager set to scan daily. My issue is every time it scans it pops up to the end user. I want this behavior to be completely silent. Are there settings associated with this I can change?

 

Thank you.

Policy Invoker not starting after Agent Install from GuiRunOnce

July 16, 2010, 2:31 pm

≫ Next: Miniscan.exe Application Error

≪ Previous: Agent settings for security and compliance manager

$

0

0

We are deploying images to computers throughout our district.  The image has been syspreped and we have the Agent deployment configured to run during the GuiRunOnce section of the sysprep.inf file along with the install of Sophos AntiVirus and lastly a gpupdate /force /boot to force the AD policies to refresh and reboot the computer so that it is not left logged in as the local Administrator.  Below is the GuiRunOnce section of the sysprep.inf file (server names and passwords changed):

 

[GuiRunOnce]
Command0="c:\ldsleep.exe 30"
Command1="net use \\LDSERVER\ldlogon Password /u:DOMAIN\LANDesk"
Command2="cmd /q /c \\LDSERVER\ldlogon\wscfg32.exe /F /L /STATUS /NOREBOOT"
Command3="net use \\LDSERVER\ldlogon /d /y"
Command4="cmd /q /c del /q c:\ldsleep.exe"

Command5="cmd /q /c del /q c:\ldiscan.cfg"
Command6="net use \\AVSERVER\SophosUpdate Password /u:DOMAIN\LANDesk"
Command7="\\AVSERVER\SophosUpdate\CIDs\S000\SAVSCFXP\setup.exe -user DOMAIN\LANDesk -pwd Password -mng yes"
Command8="net use \\AVSERVER\SophosUpdate /d /y"
Command9="gpupdate /force /boot"

 

The imaging has been going fine - during the first boot, after the automated mini-setup completes, the system automatically logs in once and runs the various GuiRunOnce commands to install the agent, the antivirus, and refresh group policy and reboot.

 

We are able to deploy software through pushes and remote into these machines after imaging like normal, but the machines do not install any software deployed from LANDesk that has been configured using a Policy or as a Policy-Supported Push if the machine was not on at the time of the initial push.

 

Upon further investigation, it appears that the policy invoker service is not working correctly for the systems to be able to pull installs through policy.  We recieve this error in the Desktop Manager when we go to  try to refresh the policy "Policy synchronization has failed"

 

 

If we re-install the agent again manually by navigating to the ldlogon share and running wscfg32.exe, when the install finishes, the policy invoker starts and the system begins receiving software deployment through policies as it should.

 

Here is the question:  Why does the policy invoker service not start when the agent is installed suring the GuiRunOnce leaving the system unable to receive software?  This is extremely detrimental to our re-imaging process as the systems need to install certain location and department specific software packages after they have been imaged.  We would like to have these deployments setup as policies so that when the system gets re-imaged, it begins installing any necessary software packages immediately following the imaging process and mini-setup while the system is waiting at the login prompt.

Miniscan.exe Application Error

April 17, 2008, 6:45 am

≫ Next: WSCFG32 not installing services

≪ Previous: Policy Invoker not starting after Agent Install from GuiRunOnce

$

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!

 

 

WSCFG32 not installing services

July 10, 2008, 1:52 pm

≫ Next: Install issues with AdvanceAgent GPO

≪ Previous: Miniscan.exe Application Error

$

0

0

After an OSD script with Sysprep runs, our machines run wscfg32.exe with the standard switches (used LD wizard to create the OSD scripts).  The agent gets installed, but there are some services missing.  Specifically:

 

-LANDesk Policy Invoker

and

-LANDesk Out of Band Monitor Service (about 50% of the time installs fine)

 

Once the machine reboots and is all checked in with the Core, if I push the same Default Agent config as a scheduled task the services are then installed properly.  Basically I've had at least 50 machines roll out recently that do not have these services installed.

 

Any idea why wscfg32.exe isn't creating these services?  This hurts us because we use the Software Deployment Portal pretty frequently as well as policy-based software distribution.

 

We're on 8.8.  Thanks.