What are your settings for:
/AgentSetup/preloadedKMs<br />/AgentSetup/loadOnlyPreloadedKMs<br />/AgentSetup/disabledKMs<br />
I don't yet have a test 18.104.22.168 Agent or else I would check it myself. I may by the end of the day, however as we're currently planning an upgrade.
preloaded is NT_LOAD.kml
disabledKMs is empty
loadOnly is no
As I say, the kms do seem to be preloaded.
I noticed exactly the same thing. Maybe you should log a call with support - I'm over my quota!
Yep. Logged a call. Basically BMC are saying it is "by design" and is due to new "KM parsing code" and that you now get the same message regardless of if the KM is preloaded or not. I sent a message back saying this was a bit daft since the agent saying it is loading a KM when it has in fact already loaded it is just plain misleading. As I said in my earlier thread, the key issue arising is the fact that every time a console connects, the errs file gets all the "loading KMs" messages. Very peculiar decision on BMC's part. My own feeling is that it is a "bug".
i have also found this behaviour on new products - appeared to start after one of some upgrade processes (perhaps to 3.6 agent or 3.5.60 classic console?) (before it normally stated: '... already loaded by agent' afterwards it changed to 'loaded locally' on classic console connection (pco web/win remains on already loaded msg)