Please suggest what can be the reason for few devices we are getting failed while patching with error "Attempt to logon as Specified user failed"
Find attached vulscan log file too.
Regards,
Sujith
↧
LANDesk Patching failed with error “Attempt to logon as Specified User failed”.
↧
Re: LANDesk Patching failed with error “Attempt to logon as Specified User failed”.
From the log file:
Error: Unable to logon as user landesk. Code 1326
System Error Codes (1300-1699) (Windows)
- ERROR_LOGON_FAILURE
- 1326 (0x52E)
The user name or password is incorrect.
This would indicate the the credentials you have entered in your "SGGLBDLANDSK01_v122029" scan and repair settings in the "MSI information" / "Run as Information" section are incorrect. Try verifying the credentials (if it's a domain user, then make sure the DOMAIN\Account format is correct), save the settings to update the XML file and then try again so the device will download the updated settings.
Is there a particular reason for installing the patches as a specific using instead of leaving that information blank and thereby install the patches as LOCAL SYSTEM?
↧
↧
Re: Any way to hide Fuse in LANDesk Group
Understood. I loaded my SP1 server and it does display the same way. So kshuman you can simply just uncheck the box under the "LANDESK workspace" section of the Agent configuration.
↧
Beast Vulnerability CVE-2011-3389 9.6 SP1
Hello All,
We experiencing the Beast vulnerability on our LANDESK 9.6 SP1 core server. ( call @ support )
The server is 2012R2 the CSA is upgraded to higest lvl.
Only TLS 1.0 / 1.2 are on rest is disabled via de registry keys. Can't turn TLS 1.0 off as we don't have connection to the console anymore.
Anybody already found how to solve this vulnerability ?
↧
Re: Beast Vulnerability CVE-2011-3389 9.6 SP1
Hi Casper,
We are having the same issue and can't find a solution on the Landesk community.
↧
↧
Agent getting continually prompted for reboot 9.6 SP1
I have a computer in our QA testing group that has been getting prompted regularly for a reboot. No patches are assigned to it and there have been no Windows updates applied to it since over a week ago. This person has rebooted his machine in response to the prompt several times, but it still pops back up.
Looking in the Security and Patch information tool for this machine, the last vulnerability it fixed was an Adobe Reader patch applied 6 days ago.
In the Vulscan log, it refers to a taskid that I cannot find that is prompting a reboot:
Thu, 28 May 2015 14:27:31 Updating task 559: 'C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe' '/rebootWithUI /offline'
I also cannot find any log files relating to task 559 on the client. In the Diagnostics and Logs tool, there is no 559 Task ID listed.
I have run UninstallWinClient.exe on this machine and reinstalled it, but the mysterious reboot prompt returned.
I've attached the vulscan and reboot logs from the client. Any idea what may be going on here?
Thanks.
↧
Lab exercise documentation from Interchange 2015?
A couple of the instructors for the labs I attended mentioned the documents and perhaps some slides would be made available in the community. Is this out there yet?
↧
Re: Agent getting continually prompted for reboot 9.6 SP1
Try running a Patch and compliance scan using a distribution and Patch setting with the repair option "Start repair even if a reboot is already pending" enabled.
This workaround should work (90%, for the remaining 10% I have a case still open, no solution so far)
↧
Core activated but no license
I have received new licenses. I have two core servers, each in its own domain. I have enough licenses for both of the core servers. I can activate both core servers, but only one acccepts the license. What is going wrong here?
↧
↧
Re: Core activated but no license
Are they both at the same LANDESK version?
Mark McGinn
MarXtar Ltd/MarXtar Corporation
http://landeskone.marxtar.co.uk
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
↧
Re: Agent getting continually prompted for reboot 9.6 SP1
I've ran that command on the machine. I'll have to check it the beginning of next week and report back.
Thanks.
↧
Re: Core activated but no license
One is running 9.5 SP1 and the other one 9.5 SP2
↧
Re: Workstation and Domain Computers on the Same Server? Good, Bad, Otherwise?
Hi Jebolick,
This should be very similar to the tasks you have had to join the computers on the domain to the core. You just bare in mind the differences between an 'no domain controlled machine' and an 'domain controlled one'. A few being:
- The administrator will have to be set manually on all machines - this is important as a user with admin rights is needed to install the agent
- The above can be over-ridden completely if you use a self-contained agent as this will need admin rights to install the agent, which the local IT should know
- Once the agent is installed it should function identically to your other machines connected to the core. But only in terms of the LDMS tasks you can do with it.
Martin
↧
↧
Re: PolicySync.exe fails through CSA
The SP2 version of PolicySync.exe probably contains other fixes, but just not this one, which would explain the incremented version number.
I've just been told by support that this particular issue will be fixed in the next component patch for LD9.6 SP2.
↧
Re: Workstation and Domain Computers on the Same Server? Good, Bad, Otherwise?
Thanks again Martin,
One more question please. As these potential clients are not members of the domain, will the agents have to be installed locally? They do reside on a network segment our current core can see. Will UDD find these devices and install the agent so long as I provide the core with the Local Admin credentials?
Thanks again,
Jeremie B
↧
Re: Workstation and Domain Computers on the Same Server? Good, Bad, Otherwise?
Hi Jeremie B,
UDD can work, but the amount of local administrators you will have to enter will be quite large as the scheduled service requires a domain name format to work correctly. I.e nameofmachine\administrator etc. But you can try this with just the user name 'administrator' and a password, but this is not guaranteed. A self-contained exe may be best in this scenario.
I would suggest that you test with a few methods and see which one works best for your specific environment.
Martin
↧
Re: Bad usernane access request to Active Directory
Hi,
If you don't have Mobility set up and in use can you try stopping the Landesk Command Service and see if that gets any better? The files you mentioned are responsible for correct/ secured communication between the Avalanche on Demand console and the Core server.
Thanks,
Mariusz
↧
↧
no trending for vulnerability
we are trying to measure the number of servers that are patched at the moment for a particular vulnerability but for some reason there is no trending data for the particular vulnerability and the status doesn't match the history. I have attached a few screenshots for reference.
Anyone have any ideas?
↧
Re: Bad usernane access request to Active Directory
We had same thing and needed to put in the user in the com connector again after it worked.
↧
Re: Lab exercise documentation from Interchange 2015?
Hi RClements,
The documentation is not yet available online as we are working a few things out, but will be posted soon. Keep an eye on community.landesk.com, and on interchange.landesk.com to see the information once it is posted.
Thanks,
Bryce
↧