Quantcast
Channel: LANDESK User Community : Document List - All Communities
Viewing all articles
Browse latest Browse all 6338

Troubleshooting and Log Gathering for LDMO 9.5

$
0
0

Environment

LDMS 9.5 SP1 with LDMO 9.5

 

Here is a list of useful logs to gather and analyze when troubleshooting LDMO issues;

 

STS.DLL.Log -- This log is useful for checking STS related information like the STS\Issue Token command.

BrokerServices.log -- Useful for investigating CSA connection issues.

Console.log -- Used to view any communication from the Core side.

IIS logs -- Used to check IIS related information, both LDMO and the core use IIS.

LDMOUpgrade log -- Used to verify data syncs between the core and AOD.

MobInvUpdate log -- Also used to track data syncs between core and AOD.

 

Configuring Mobility Logging on CORE

 

1. Go to LDMAIN->landesk

2. Right-click PremiseServices and give IUSER Modify permissions and save.

3. Drill down into PremiseServices folder

4. Edit web.config file

5. Set “add key=”LogEnabled” value to true and save.

6. Logs should be kept in log folder

 

Configuring Broker DEBUG logging (if you suspect a problem with the CSA)

 

1. Go to LDMAIN

2. Edit BrokerServiceConfig.xml

3. Set <Logging> to true and save.

4. Open Registry

5. HKLM->System->CurrentControlSet->services->LDGSB

6. Open ImagePath key

7. Add /verbose after the last set of double quotes on the key value.

8. Restart the LANDesk broker service.

9. Logs kept in PremiseServices folder and LDMAIN->log folder.


Viewing all articles
Browse latest Browse all 6338

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>