International About LANDesk| Partners| Contact Us
Up to Discussions in Agent Deployment and Installation

This Question is Possibly Answered

1 "correct" answer available (20 pts) 1 "helpful" answer available (10 pts)
7 Replies Last post: Sep 6, 2008 12:13 AM by MarXtar  
Zachry Sum Rookie
Zachry Sum
17 posts since
Jan 31, 2008
Currently Being Moderated

Sep 5, 2008 9:10 AM

Cannot deploy agent after upgrade to 8.8

We recently went from 8.7 sp3 to 8.8 and since doing so, we cannot deploy the agent through the LANdesk console. If you manually run the installer from the client it works, but pushing it fails, on any unmanaged pc. Here is the log file from one of the attempted pushes:

 

[Operation failed] RemoteExecute, cmd /c mkdir C:\$ldcfg$
CBA 8 X509 operation : -2147481845 (8000070b8u) : Unable to contact the remote agent.
NT File Sharing : 1222 (4c68u) : The network is not present or not started.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
NT File Sharing : 1312 (5208u) : A specified logon session does not exist. It may already have been terminated.
Secure Shell : 1805 (70d8u) : An unspecified error in the protocol occured.
Remote execute using TCP failed, result 0x0000057a (1402)
On unmanaged systems this operation will attempt to access the ADMIN$ file share and remotely start a service

Ty Expert
Ty
212 posts since
Dec 12, 2007
Currently Being Moderated
1. Sep 5, 2008 9:35 AM in response to: Zachry Sum
Re: Cannot deploy agent after upgrade to 8.8

Resolution

To resolve this issue, please follow the steps below:

1) In the Console on the Core Server, open Configure > Services
2) Click on the tab 'Scheduler'
3) Click on 'Change Login'
4) Enter an administrative account that has the rights to access and create the temporary installation folder on the clients.
Report Abuse
Zachry Sum Rookie
Zachry Sum
17 posts since
Jan 31, 2008
Currently Being Moderated
2. Sep 5, 2008 9:41 AM in response to: Ty
Re: Cannot deploy agent after upgrade to 8.8

I don't believe this to be the issue. It is set to use localsystem. In addition to that it has alternate credentials entered for the machines local administrator account. What else could cause this?

Report Abuse
Ty Expert
Ty
212 posts since
Dec 12, 2007
Currently Being Moderated
3. Sep 5, 2008 9:43 AM in response to: Zachry Sum
Re: Cannot deploy agent after upgrade to 8.8

The main account should not be localsystem.  Change it and prove me wrong.

Report Abuse
Zachry Sum Rookie
Zachry Sum
17 posts since
Jan 31, 2008
Currently Being Moderated
4. Sep 5, 2008 9:57 AM in response to: Ty
Re: Cannot deploy agent after upgrade to 8.8

It did not work. Changed it to a domain account with administrative rights, and get this:

 

[Operation failed] RemoteExecute, cmd /c mkdir C:\$ldcfg$
CBA 8 X509 operation : -2147481845 (8000070b8u) : Unable to contact the remote agent.
NT File Sharing : 1222 (4c68u) : The network is not present or not started.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
Secure Shell : 1805 (70d8u) : An unspecified error in the protocol occured.
Remote execute using TCP failed, result 0x0000057a (1402)
On unmanaged systems this operation will attempt to access the ADMIN$ file share and remotely start a service

Report Abuse
Ty Expert
Ty
212 posts since
Dec 12, 2007
Currently Being Moderated
5. Sep 5, 2008 10:05 AM in response to: Zachry Sum
Re: Cannot deploy agent after upgrade to 8.8

The scheduler absolutly has to be an admin account for deploying agents.  Did you apply sp1 for 8.8?

 

Also,  Manually re-start the scheduler service after changing account.

Report Abuse
Zachry Sum Rookie
Zachry Sum
17 posts since
Jan 31, 2008
Currently Being Moderated
6. Sep 5, 2008 4:24 PM in response to: Ty
Re: Cannot deploy agent after upgrade to 8.8

Restarting the core server did it. Ahh...sometimes LANDesk confuses me. Thanks for the assistance Ty.

Report Abuse
MarXtar Expert
MarXtar
608 posts since
Jul 2, 2008
Currently Being Moderated
7. Sep 6, 2008 12:13 AM in response to: Ty
Re: Cannot deploy agent after upgrade to 8.8

The scheduler service does not need to be an admin if redeploying agents since it will use the file transfer and remote execute functions of the agent already in place.  Still a good idea to have it set though since often you will redeploying the agent because it doesn't work properly so relying on a faulty agent to redeploy is not a good idea.

 

Mark Star - MarXtar LANDesk Enhancements

Home of Power State Notifier & Wake-On-WAN for LANDesk

Report Abuse

More Like This

  • Retrieving data ...
LANDesk Community powered by Jive Software's Clearspace ®                                                                        Subscribe| Legal Notices| Investor Relations| Privacy Policy © 2007 LANDesk Software