Management core server ip address has changed, Provisioning fails, No user image – Lenovo Secure Managed Client User Manual
Page 62: Landesk logs, Unique network failure points
4.
When the authentication is verified, browse to tcm\dist\\SMCBoot-
<version>.img
and select Update.
It will take a few minutes to load, but all the information should be up-to-date,
and the clients should be able to boot.
Management Core Server IP address has changed
If the core server has been moved and the DHCP IP address for that server has
changed, do the following to fix it.
1.
Reset the IP to original IP address (set static)
2.
Reboot the core to cause another inventory scan so that the inventory is
synchronized. If you do not want to reboot, enter this from the command line:
\<path to landesk install>\ManagementSuite\ldlogon\ldiscn32
/ntt= NATIONWI-IX4CN8
/s= NATIONWI-IX4CN8
/sync
/v
Provisioning fails
When provisioning fails, check the following:
v
If LANDesk was attempted to be installed multiple times on the server, check
that the certificate in c:\Program Files\LANDesk\Shared Files\certs folder and
ensure it matches with the protect.ini file.
v
Make sure that pinging occurs from the Secure Managed Client Storage Array to
the Secure Managed Client Management Console Server and from the
Management Console Server back to the storage array. The problem could be the
firewall on the core server. Check this: C:\program files\landesk\shared
files\keys\Protect.ini.
No user image
If the user creation operation appears to complete successfully and produces a user
entry in the users branch of the storage array but no image is created for that user,
there is a lack space on the storage array for that image.
LANDesk logs
When troubleshooting Secure Managed Client problems, there are two LANDesk
logs and two Web sites that you can use for troubleshooting:
1.
Program Files/LANDesk/Management Suite/console.exe.log.
2.
Program Files/LANDesk/Management Suite/logs/san_portal.log .
3.
https://localhost/connectionmanager/connectionmgr.asmx.
4.
https://localhost/san_portal/sanportal.asmx.
Unique network failure points
Table 5. Network failure points
Symptom
Possible reason
Impact
Client system crashes,
lockups
Windows driver/app
Switch failure
Storage array failure
Bad Ethernet cable
One to a few clients report crashes
All systems on switch are affected
All clients on storage array affected
System attached to cable effected
54
Secure Managed Client Version 2.0 Deployment Guide