
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2008 05:28 AM
Mr. Moernaut,
I am very impressed with the upgraded 3.0! Everything that 2 had plus everything it didn't!. Good show.
But as I started working with 3.0, I noticed my computer descriptions aren't being populated. I followed the guide, but did I miss/misconfigure something?
Also, where are the queries stored/how do I make new ones? I didn't see any way in the admin console.
Thank you!
Sofa King
I am very impressed with the upgraded 3.0! Everything that 2 had plus everything it didn't!. Good show.
But as I started working with 3.0, I noticed my computer descriptions aren't being populated. I followed the guide, but did I miss/misconfigure something?
Also, where are the queries stored/how do I make new ones? I didn't see any way in the admin console.
Thank you!
Sofa King
Labels:
- Labels:
-
Archive
6 REPLIES 6

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2008 10:16 PM
That script works perfectly. Thanks much.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2008 04:51 PM
I have a .vbs that does exactly that.
Just make the following a .vbs script. I run it as a login script in my domain.
'AD Info to local description'
'This info will show up after a reboot of the system.
'If you want it updated in LanSweeper, shorten the rescan time for the OS Scan
' -------------------------------------------------------'
Const HKEY_LOCAL_MACHINE = &H80000002
On Error Resume Next
Set objSysInfo = CreateObject("ADSystemInfo")
strComputer = objSysInfo.ComputerName
Set objComputer = GetObject("LDAP://" & strComputer)
objProperty = objComputer.Get("Description")
'If you wanted the AD Location info copied to the local description you could use the following line
'We use it since LanSweeper gives us the computer description
'objProperty = objComputer.Get("Location")
strDescription = objProperty
strComputer = "."
Set objRegistry = GetObject("winmgmts:\\" & strComputer & "\root\default:StdRegProv")
strKeyPath = "System\CurrentControlSet\Services\lanmanserver\parameters"
strValueName = "srvcomment"
objRegistry.SetStringValue HKEY_LOCAL_MACHINE, strKeyPath, strValueName, strDescription
Just make the following a .vbs script. I run it as a login script in my domain.
'AD Info to local description'
'This info will show up after a reboot of the system.
'If you want it updated in LanSweeper, shorten the rescan time for the OS Scan
' -------------------------------------------------------'
Const HKEY_LOCAL_MACHINE = &H80000002
On Error Resume Next
Set objSysInfo = CreateObject("ADSystemInfo")
strComputer = objSysInfo.ComputerName
Set objComputer = GetObject("LDAP://" & strComputer)
objProperty = objComputer.Get("Description")
'If you wanted the AD Location info copied to the local description you could use the following line
'We use it since LanSweeper gives us the computer description
'objProperty = objComputer.Get("Location")
strDescription = objProperty
strComputer = "."
Set objRegistry = GetObject("winmgmts:\\" & strComputer & "\root\default:StdRegProv")
strKeyPath = "System\CurrentControlSet\Services\lanmanserver\parameters"
strValueName = "srvcomment"
objRegistry.SetStringValue HKEY_LOCAL_MACHINE, strKeyPath, strValueName, strDescription

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2008 04:02 PM
I don't necessarily need it scanned, if I can automate copying the data to the local computer description where it is scanned.
Unfortunately, I can't figure out how to pull the AD description from a computer. Is there an easy way that I could do that at the command line or -- if necessary -- through vbs? If I had a means to pull it, copying it to the local computer description through a registry import would be trivial.
Unfortunately, I can't figure out how to pull the AD description from a computer. Is there an easy way that I could do that at the command line or -- if necessary -- through vbs? If I had a means to pull it, copying it to the local computer description through a registry import would be trivial.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2008 03:16 PM
Is there a way to auto-refresh the Service webpage? I have tried using the <meta http-equiv="refresh" content="30" /> style tag, but I don't think it's designed to work in a .config file.
There is no way to autorefresh it at the moment (but you can always press F5)
Actually, I'm wondering if the AD Descriptions are being stored anymore and, if so, where. That was useful information in our reporting. Is there a way to get that information in 3.0?
In the current version, the AD computer info isn't scanned anymore. -> you can make a post in the "wishlist" for the next release.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2008 07:28 AM
Actually, I'm wondering if the AD Descriptions are being stored anymore and, if so, where. That was useful information in our reporting. Is there a way to get that information in 3.0?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2008 09:29 PM
I'm silly. I was expecting AD Descriptions, not local computer descriptions. You can scratch that one.
You can scratch the query question too. Figured it out as well.
But I do have a new question.
Is there a way to auto-refresh the Service webpage? I have tried using the <meta http-equiv="refresh" content="30" /> style tag, but I don't think it's designed to work in a .config file.
Thanks again!
You can scratch the query question too. Figured it out as well.
But I do have a new question.
Is there a way to auto-refresh the Service webpage? I have tried using the <meta http-equiv="refresh" content="30" /> style tag, but I don't think it's designed to work in a .config file.
Thanks again!
