Previous Next

Jared Barneck's Blog

Currently Being Moderated

Console Add-on: LANDesk Support Tools Beta 2

Posted by rhyous on Feb 6, 2009 1:34:46 PM

Hey all,

 

I made an update.  The added changes are easy to get. To upgrade, just close the Console and run the new installer.

 

Here is where you can read more about it:

 

Console Add-on: LANDesk Support Tools

 

 

Version: 8.80.2.2
===================

  1. Updated version of LDValidate.exe (Jan 27, 2009) and updated the XML.  Sorry, the xml is still for 8.8 flat and there is not an 8.8 SP2a version of the XML yet.
  2. On upgrade, if the Console is open an error replacing cxExtender.dll occurs even if cxExtender is not a newer version and doesn't need to be replaced.  Fixed installer to ignore this error unless this file needs updated.
  3. Added who.vbs to see who is logged in to a remote system.
  4. Added RemCom.exe to be able to open a remote command prompt.
  5. Added the ability in cxExtender.dll to use %ldmain% in the command line of cxExtender.xml.  %ldmain% will evaluate to the path to the ManagementSuite directory, which can be different depending on where you install LANDesk.
  6. Updated right-click ability in UDD to have the same features as right-click in all devices.  It does have one more feature in UDD for Remote Desktop Protocol.  Since it is an Unmanaged Node, you may not have the LANDesk agent yet so LANDesk Remote Control may not be available yet.

 

Hope you like the new features.



Feb 6, 2009 5:12 PM spastic_toad spastic_toad    says:

Thank you for adding the "Who is logged in" feature.  We have been doing that manually and time consuming when you have to do it a lot.  In general this console add on is fantastic!!  Highly recommend to all LANDesk administrators to use this add on.
Feb 7, 2009 10:07 AM Jack Coates Jack Coates    says:

the download links are both broken for me...
Feb 8, 2009 6:01 PM rhyous rhyous    says in response to Jack Coates:

Yeah...sorry...I forgot to chang the link.
Feb 18, 2009 6:30 PM Facebook_Thomas    says in response to spastic_toad:

just a bit of feedback, most our MAC systems aren't registering with DNS; the SSH and VLC tools would be applicable to MACS if the addin could use IP addresses (or the "Agent Discovery ; Discovery Methods priority).
Feb 18, 2009 10:11 PM spastic_toad spastic_toad    says:

can you add a full software sync inventory function to the support tools?  currently we have to drag the device/s to a task that runs this in a batch file so it would be more efficient if we could right click and run the software sync.  Thanks!

 

BTW this console addon rocks!  its working great for us!
Feb 18, 2009 10:30 PM Facebook_Thomas    says in response to spastic_toad:

Ah yeah, +1 for adding full inventory sync, another +1 for restarting remote control services on the client.

 

Of what I've noted however, the console addin is mostly calling external command so unless you can call LDMS Scripts from that context menu I don't know how this would work out.
Feb 19, 2009 9:58 AM rhyous rhyous    says in response to Facebook_Thomas:

I just noticed this with the VNC Viewer and my Linux nodes.  The VNC Viewer should be using IP Address.  I will do this to SSH as well.
Feb 19, 2009 5:22 PM rhyous rhyous    says in response to spastic_toad:

Full Sync scan will be in my next version.But it will simply call the scanner as follows:

 

C:\Program Files\LANDesk\LDClient\LDiscn32.exe /L /F /Sync

 

If your agent is not installed on C, this won't work.  If you do not have the ldappl3 already downloaded to the agent (which would be rare) it won't work.

 

To make it work everywhere there are some problems. There are variables that may be different:

 

Core Name

path to ldclient

 

If I try to get this information from the agent's inventory scan, it might not work because the whole reason you are doing a full sync scan is because inventory information such as the path to ldclient may be missing.

 

So I need the variable resolution to happen on the client side not the Core Server side which means some code re-writes.
Feb 27, 2009 1:22 PM Dan Pixley Dan Pixley    says in response to rhyous:

When using who.vbs, I seem to get this error message a lot:

 

line:17

char: 1

error: The remote server machine does not exist or is unavailable: 'GetObject'

code: 800A01CE

source: Microsoft VBScript runtime error

 

Anyone have any ideas?  I am running this in an Active Directory environment.  What requirements are needed for this script to work?  Thanks!
Feb 27, 2009 1:33 PM spastic_toad spastic_toad    says in response to Dan Pixley:

one reason this is displayed, is if you are not a local admin on the remote system.
Feb 27, 2009 10:45 PM rhyous rhyous    says in response to Dan Pixley:

This is really caused by one of three reasons usually, though there may be more reasons:

 

1. The machine is off.

2. The machine is on but the firewal is enabled and Remote Scheduled Task Management (RPC) is not enabled through the firewall.

3. The machine is on and the firewall is off or configured to all RPC but RPC is disabled.

 

http://support.moonpoint.com/os/windows/xp/firewall/rpc-server-unavailable/
Mar 31, 2009 4:25 PM Rich Sterling Rich Sterling    says in response to rhyous:

I'm noticing that in our mixed workgroup/domain (in the process of a migration), as spastic toad mentions, you are not a local admin on the remote system.  Just an fyi, I was able to get around this by a bit of vbs tweaking which I am sure can be passed with the arguments as optional.

 

Option Explicit
Dim objWMIService, objWbemLocator, StrComputer, strNamespace, args
Dim colNamedArguments, colComputer, objComputer
Const WbemAuthenticationLevelPktPrivacy = 6


Set colNamedArguments = WScript.Arguments.Named
If colNamedArguments.Exists("S") Then
strComputer = colNamedArguments.Item("S")
Elseif WScript.Arguments.Count = 0 then
Dim objNetwork
Set objNetwork = WScript.CreateObject("WScript.Network")
strComputer = objNetwork.ComputerName
Else
Wscript.Echo "Usage: Who.vbs /S:ComputerName"
Wscript.Quit
End If


  strNamespace = "root\cimv2"
  Set objWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set objWMIService = objwbemLocator.ConnectServer _
      (strComputer, strNamespace, "<Admin_ID>", "<password>")
  objWMIService.Security_.authenticationLevel = WbemAuthenticationLevelPktPrivacy


Set colComputer = objWMIService.ExecQuery _
    ("Select * from Win32_ComputerSystem")

For Each objComputer in colComputer
If not objComputer.UserName = "" Then
  Wscript.Echo vbCr & _
  "Machine Name: " & strComputer & vbCr & _
  "Logged-on user: " & objComputer.UserName & vbCr & vbCr
Else
  Wscript.Echo vbCr & _
  "No one is currently logged into '" & StrComputer & "'" & _
  vbCr & vbCr
End If
Next
Mar 31, 2009 4:54 PM Rich Sterling Rich Sterling    says in response to Rich Sterling:

And for those who need to enter credential to browse the file system: (This will prompt for credentials just like running Start/Run)

 

<Menu>

<Text>Browse File System (Using the C$ share)</Text>

<Command>cmd.exe</Command>

<Parameter>/c start \\%"Computer"."Network"."TCPIP"."Host Name"%\c$</Parameter>

</Menu>
Apr 1, 2009 10:26 AM rhyous rhyous    says in response to Rich Sterling:

Rich,

 

Thanks.  I will test both of those and if they work (which I assume you have already tested), I will make sure to make use of them in beta 6.
rhyous

rhyous

 Member since: Nov 19, 2007

View rhyous's profile

Actions

Popular Blog Posts

LANDesk Community powered by Jive Software's Clearspace ® Subscribe| Legal Notices| Investor Relations| Avocent| Privacy Policy © 2009 LANDesk Software