The services info in the inventory is under OS > Drivers and Services > Service
All I show in my inventory for services is the name and if it is running or not, I'm not aware of getting which credentials it is using through LDMS
Thats pretty much what I'm seeing as well, and I wasn't sure that LD was the tool I used ... so frustrating.
Is there any other tols you know of or methods to use for this? Since LD uses WMI scanning, cant that info be extracted from that?
If the credentials information are stored in the registry you can pick them up by custom data.
There is a FREE tool from managed planet that will do the trick it is called LOGON AS. It is installable on your cores. It adds a file and instructions that you need to send down to your systems that will pull in the services logon info.
Here is a link for a screenshot - http://managedplanet.com/images/screenshots/logonas/LogOnAs.gif
To download - http://managedplanet.com/downloads/freeware/
and No, i don't work for them.
I downloaded and installed this and the console extender from Managed Planet on our test box. Now everytime I go to open the console, it tries to go out to Managed Planet's web site. Anybody know why this would be?
I haven't seen that on my test servers that i am aware of.
How are you aware that it is going out to the site? Is it by a browser popping up or are you looking at the network traffic?
Here are the instructions, although sparse, do not mentin anything about it -
Managed Planet Free Log On As Inventory Extender
~ The Log On As Inventory Extender is a client executable that is used to gather what user a service is logging in with. The results will show up in the inventory tree as a new attribute of the Service component called Log On As.~
~ INSTALLATION INSTRUCTIONS~
~ 1. During the installation of this product, Managed Planet's database installation ran. Verify that it correctly modified the database schema by going into the Query dialog and looking at Computer.OS.Drivers and Services.Service and verify that an attribute called Log On As is present. If it is not, please rerun the Managed Planet Database Installation tool.~
~ 2. \Program Files\LANDesk\ManagementSuite\LDLogon\MP_PACKAGESManagedPlanet.Client.ServiceLogin.exe and ManagedPlanet.Core.dll must be copied to the client's LDCLIENT folder.~
~ 3. The client must have at least the .NET Framework 1.1 installed.~
~ 4. Edit the ldscnhlp.ini file on the client so it looks like this:~
~ LAUNCH1=\Program Files\LANDesk\LDClient\ManagedPlanet.Client.ServiceLogin.exe~
~ DATA1=\Program Files\LANDesk\LDClient\ServiceLogin.dat~
~ You might have other launch and data entries, if so just increment the numbers. Also, change the path if necessary.~
~ Now when a client scan is run, it will create a servicelogin.dat file in the LDCLIENT folder that has the service login info and it will be added to the scan file.~
Actually it popped up on the server because it had enhanced IE security on it. IE was prompting if I wanted to add it to trusted sites. If I let it go, this huge Managed Planet logo came up. I actually called them and asked. They said it was something that came up with their ad(s) on it. They said it isn't required to run the program. I added the site to the restricted sites zone and it stopped coming up. Just worries me when a new program does that. Not a fan of phoning home for ads or otherwise.
Makes sense, we have the managed planet console extender installed and that was added to the allowed sites prior.
Yeah, i don't like it either, but the price makes it somewhat worth dealing with.
But shouldn't WMI be able to pull the info?
Not a huge deal, and I'm beginning to think the data wasn't pulled from LD the first time. Still looking for a solution that doesnt include installing more software though.
Thanks for all the feedback though folks.