Yea all devices are to write to a share for SLM. I don't use it currently in pools only dedicated VMs. The errors are now only with the VMs.
↧
Re: Scheduler Account Audit errors lead to account lockout
↧
VMWare ESXi Update causing BSOD stating cismbios.sys error
We patched one of our ESXi hosts (5.1) yesterday to release 2583090 and now our Windows 7 VMs with LANDesk (9.6 SP1) on them are rebooting on a loop with the error message below. The host we patched only contains Windows 7 VMs for testing so we are not sure if this affects any Server OS as well. Before we update other hosts with Servers we wanted to be sure. I found this post concerning the same issue at vSphere 5.1 patch - may cause LANDesk cismbios.sys to blue screen which is dated March 20, 2015. His suggestion was to modify the registry key HKLM\SYSTEM\CurrentControlSet\services\CISMBIOS to a value of 4. This did work when we applied the change (via Safe mode) on one of the VMs however I don't want to have to push this out to every VM. The post indicates that LANDesk is aware of the issue and is working on a fix. Has anyone else run into this issue and has a patch for it been released yet? I tried searching the LANDesk support site but could not find any mention of this specific issue.
↧
↧
Re: VMWare ESXi Update causing BSOD stating cismbios.sys error
Log a ticket with LANDESK referencing the defect number. As well as increasing what is probably already a high priority it means you should be notified directly if the patch is already out or when it is. LANDESK doesn't release every patch straight away as they can't go through the same level of testing as for component patch bundles, but if you want early access then you need to log a support ticket.
Mark McGinn
MarXtar Ltd/MarXtar Corporation
http://landeskone.marxtar.co.uk
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
↧
Re: VMWare ESXi Update causing BSOD stating cismbios.sys error
THis is fixed in the the latest Component Update you can get from support, or wait a bit for SP2 which will contain all fixes and will be realeased soon.
Frank
↧
PolicySync.exe fails through CSA
Windows Agents on the internet (9.6 SP1) cannot sync policies through CSA. Patch, Inventory and Remote Control DO work through the CSA, and if I do a Portal sync BEFORE putting the computer in the Internet, I CAN download and install the listed packages through the CSA. It is just policy sync that is failing, all else works great.
The Portal Manager quickly throws "Failed to load packages" when clicking the refresh/sync button. The same computer syncs just fine when connected to the corporate network.
PolicySync.log:
Fri, 15 May 2015 09:32:03 GetLdapInfo: ldapwhoami.exe failed - err=1355 << NET HELPMSG 1355 returns "The specified domain controller either does not exist or could not be contacted"
Fri, 15 May 2015 09:32:03 GetLdapInfo: use cached logon info
Fri, 15 May 2015 09:32:03 GetLdapInfo: not a valid ldapinfo, return E_FAIL
PolicySync.exe.log:
| 05/15/2015 09:32:03 INFO 4188:1 | RollingLog : Run PolicySync.exe |
| 05/15/2015 09:32:03 INFO 4188:4 | RollingLog : LoadLocalPolicyInfo: load local machine |
| 05/15/2015 09:32:03 INFO 4188:4 | RollingLog : LoadLocalPolicyInfo: load user |
| 05/15/2015 09:32:03 INFO 4188:3 | RollingLog : Request: failed get target info. |
| 05/15/2015 09:32:03 INFO 4188:1 | RollingLog : PolicySync: failed request |
| 05/15/2015 09:32:03 INFO 4188:1 | RollingLog : Exit PolicySync.exe with code -3 |
Of course this machine cannot talk to a domain controller when it is off the corporate network, so why is the whole Sync failing just because of an expected condition?
Also, when I manually run ldapwhoami.exe from a command prompt, it does return data but also a 1355 exit code. Shouldn't PolicySync be treating 1355 as a SUCCESS instead of FAIL when not connected to corporate network?
↧
↧
Workstation and Domain Computers on the Same Server? Good, Bad, Otherwise?
I have been asked to join a couple hundred Windows 7 and 8 computers to our LANDESK (9.5 SP2) core server that are not in our domain. Can anyone provide me with documentation on joining computers in a Workgroup to an LDMS core that by default has been servicing domain joined computers explicitly?
↧
Re: 9.6 console unbearably slow
↧
Trying to connect to PXE rep
Hi,
I'm working on getting the imaging setup for LANDesk, I created a Capture Template and now i'm having issues booting to the PXE server. I hit F12 on the computer and choose the NIC but it cannot find the PXE server.
Are there any steps in the Core server i have to perform first before booting to the network to pull down the image?
Thanks,
↧
Re: 9.6 console unbearably slow
So I have recently switched pc's & moved to an i5 processor - this one with only 4 gb RAM, but the console is significantly more responsive on it.
I guess the console needs more processing power, since both pc's were fairly similarly loaded up otherwise.
↧
↧
Bad usernane access request to Active Directory
After upgrade to LDMS 9.6 SP1 on the AD of a customer appears a logon request from user LANDesk_CommandsWS.
It does not exists on their AD. What is this request and how can we block it?
This is the error found on the monitoring tool:
X509N:<S>C=NA,S=5914,L=L DMS Core Server,O=Unspecified,OU=LANDES K2012,CN=LANDesk_CommandsWS
On the core are present the files LANDesk_CommandsWS.crt .key .p12, are they involved in the behaviour?
Thank you
↧
Re: PolicySync.exe fails through CSA
What patch level are you on? Can you try replacing the policysync.exe with an older version, like SP1 flat?
↧
Re: Install LANDesk MS on Terminal Server - Log in fails
LANDesk Console is installed on TS with success? Did you check the logs?
If yes, did you install all patches you've installed on core on this TS too?
You've installed a LANDesk Console on another computer with which OS? W7 64bit?
↧
Re: UEFI PXE Boot issues - PXE-E99: Unexpected network Error
Hello Sylvain,
is it possible to boot NON UEFI clients with PXE? Which hardware model has the problem? http://support.lenovo.com/us/en/documents/ht001342?tabName=Solutions
We have had a similar problem with newer hardware two years ago...
Could you check the settings of your PXE configuration? You can use the PXEConfig.exe in PXE directory to view/set the MTFTP setting or check the entry MCAST_ENABLE in registry here:
32bit: HKEY_LOCAL_MACHINE\SOFTWARE\Intel\PXE\Mtftpd
64bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\PXE\Mtftpd
In both cases, the value should be set to "0", otherwise you will get MTFTP problems ...
Issue: WINPE Menu option does not work on new computers or new BIOSes.
BR
Axel
↧
↧
What is the proper way to migrate from 9.0.3.1 to 9.6
Is there a migration path for me to migrate LANDesk Management Suite from 9.0.3.1 to 9.6??
Thanks
Cathy
↧
Re: What is the proper way to migrate from 9.0.3.1 to 9.6
Hi,
It's always possible, but do you still meet Core Server and Database version requirements?
If yes, I would say to update 9.0 to SP3, than upgrade to 9.5, update with 9.5 SP2, upgrade to 9.6 and install the latest updates. SP2 is just released.
Just be prepared... Lots of changes! No more OSD Scripts for example, and no more delivery methods. I really recommend you build a new 9.6 server, migrating some things and creating other things new. It gives you much more opportunity to test and learn.
Frank
↧
Re: PolicySync.exe fails through CSA
Maybe interfering with this setting ?
↧
Brute Force Notfication from SEP
Hi
We've got from several MAC Client Brute Foce notification which has SEP installed.
The source is our Core Server. Has someone else seen this? It occurs only on MAC Clients.
Could this be from the remote login from the CBA?
Regards,
↧
↧
Re: Core Sync of Client Connectivity Settings (v9.6 SP1) - certificate and server hostname issues.
Also be aware that if you copy to other core Preferred Servers it does NOT copy the password for the user. This will eventually lock out the account you are using for pref server. They indicate that this is working by design since they don't have strong enough encryption to coresync it to the other core (could have heard this incorrectly since my head was on fire). Well that is not entirely correct, and if you change the functionality of an operation that has overly detrimental results, don't document it, and simply say well we did not feel like doing it and hope nobody notices. If a burnt out 52 year old engineer can do it in SQL can't see why they can't. To me this just shows lack of customer focus and understanding, well to be fair lack of.....to us multiple core users (MultiCoreists, One who subscribes to the black arts of Multicoreism). So you will have to create a separate agent setting per core, This will allow you to take part in MultiCore Hoping (MH - Is the the frustrating endeavor of hoping from core to core to complete a simple task)
I have suggested to LANDESK that they function in a multi core environment (have them use 4 cores - 3 productions cores and a rollup) in there everyday production environment so they can understand what it is to try and operate this way in the real world, however, I've heard nothing but crickets. Actually crickets would be cool since they are good luck and rather soothing to listen to in the evening.
↧
Re: PolicySync.exe fails through CSA
Have you installed the LD96SP1-CP_2015-0321 BASE patch and thereby using PolicySync.exe v9.60.3.24 on the client?
I discovered the exact same issue when I tested this component patch in our DEV environment. I also found that if I on the client replaced PolicySync.exe with the version from the 0114 BASE patch (which is v9.60.3.9) then it worked as it should and I could refresh the portal through the CSA.
This is all reported in case 00833109, but support has not confirmed my findings yet.
↧
Re: Not a product question but if you manage the Landesk system(s) for your company....
Thank you all so much! Do any of you have job description/salary requirements for your positions you would be willing to share?
↧