Selecting "manage local users and groups" on a device returns no information

One resolution for this issue is to ensure that the ASP.NET account has read permissions on the Inetpub folder on the LANDesk Core Server.

***Following is more troubleshooting information***

Troubleshooting and log files

Console calls a core webservice to contact CBA and run \ldclient\localaccount.exe on client to perform the local user query or modification.

1- Console.exe.log

Checking console log is a good start, it will record the detail error information when 'Manage local users and groups' window get blank. Most common cause for this issue is wrong IIS permission and directory security setting, console will log the detail http error like "Server Unavailable"...

Console log path: Core or Addition console
\Program Files\LANDesk\ManagementSuite\Console.exe.log

2- Web service access

A. Please confirm following URL can be access from core server or additional console,

http://<corename>/landesk/managementsuite/core/core.secure/LDRemoteManageAccount.asmx

***Replace <corename> by your coreserver host name***

If get any HTTP error here, please check IIS log as well and get HTTP error code at the end of log item,as following,

2010-01-18 22:36:08 W3SVC1 192.168.100.32 POST /landesk/managementsuite/core/core.secure/LDRemoteManageAccount.asmx - 80 - 192.168.100.32Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 5 0

IIS log path: Core
\WINDOWS\system32\LogFiles\W3SVC1

B. HTTP Error code and resolutions

If access LDRemoteManageAccount.asmx failed,please go IIS manager-Default web site-Default web site-landesk-managementsuite-core-core.secure

HTTP 401 5 0
- Right click core.secure and properties,Directory Security tab, Authentication and access control, ensure only 'Integrated Windows authentication' was checked.

HTTP 500 0 0
A. Right click core.secure and properties,Virtual directory tab, confirm the setting like this screen shot,

B. Right click core.secure and Permissions, the default permission should be assigned as following,
Full Control: Administrators,LANDesk Management Suite,SYSTEM
Read&Execute/List Folder Contents/Read: ASPNET,NETWORK SERVICE

C. Identity setting for Application pools - LDAppmain, default identity should be NETWORK SERVICE, change it to LOCAL SYSTEM for test purpose.

Run IISRESET and try again,

Note: This should be used only for testing, Microsoft recommends that AppPools run as Network Service. If this resolves the issue, it usually signifies that the Network Service does not have proper rights to objects in IIS, can be either NTFS or IIS permissions.

3- Client

If console.exe.log have no error and only log message like "call webservice to get local account information",  LDRemoteManageAccount.asmx also can be opened successful, it might caused by network traffic blocking or client side issue.

A. Confirm CBA service can be access from core, the binocular icon display correctly in console network view. if not, check following,
- LANDesk Management Agent service is started,TCP&UDP 9595 is listening on client.
- Browse http://<client_name/IP>:9595 from core can open web page correctly.if not, check client firewall and network security setting to see any policy block the traffic.

B. Check following log for client side issue.

Log path: Client
C:\Program Files\LANDesk\Shared Files\residentagent.log
C:\Program Files\LANDesk\Shared Files\Servciehost.log
C:\Program Files\LANDesk\LDClient\localaccount.exe.log

***Attachment LocalUser_client_log.txt is a success log on client***

When logging in to console on one machine, an error appears which says: Console initialization error: The type initializer for "Computer" threw an exception. This error occurs after changing the password on the domain. After clearing the error, there is nothing listed under "All Devices". Logging into another computer with the remote console results in no problem. Other users can log into the console on the effected machine without a problem.

Cause License cookie for the current user is either damaged or incorrect.

Use the following steps to resolve the issue.  If one step does not fix the problem, continue on to the next step.

Step 1:

Open the registry editor on the machine affected and navigate to:

HKEY_CURRENT_USER\Software\LANDesk\ManagementSuite\Core\

Delete the LicenseCookie value.

Logging back into the console will recreate the license cookie.

Step 2:

Open a command prompt on the computer the console is installed on and run the following commands:

regsvr32.exe "C:\program files\common files\system\ado\msado15.dll"

cd \windows\system32

dir atl*.dll

regsvr32.exe atl71.dll (or whichever atl.dll you have)

regsvr32.exe "%LDMS_HOME%parser.dll"

regsvr32.exe "%LDMS_HOME%ldcache.dll"

regsvr32.exe "%LDMS_HOME%msinterp2.dll"

regsvr32.exe "%LDMS_HOME%idal.dll"'

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.

Step 3:
Run C:\Windows\Microsoft.net\framework\<.NET VERSION>\aspnet_regiis.exe -i

Step 4:
Reinstall the MDAC component on the machine. Right click and reinstall from C:\WINDOWS\inf\mdac.inf and obtain the file off of a windows CD. Or download a new copy from Microsofts site. Check Microsofts download site for the latest version.

Step 5:
Check the console.exe.log. If there is a COMException listed then change the COM+ objects to a different identity.

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.

We have recently installed Ivanti EPM 2017.3.  (I have not got as far as installing any SU's yest)

We have begun to roll out new Windows 10 PC's along side our current Windows 7 PC's and all devices have now had a new agent built from the new EPM 2017.3 server installed.

Pretty much everything seems to be working fine but if we right clikc a Windows 7 device in the console and select Inspect the window states that real time moitoring is not enabled.  I can see in the agent though that it is.

This is the same agent on the Windows 10 PC's and Inspect works fine on those.

Inspect worked on the Windows 7 PC's before we upgraded to 2017.3 from 2016.3 so I am unsure why this would stop working now.

The only thing that has changed is the new server and the new agnet on all the PC's.

Anyone any thoughts why itwould pick on Windows 7 PC's?

Description:

What happens when I right-click a machine in the inventory and select Wake on Wan?

First make sure that you have the red circle in front of the machine to have the option Wake up availble to you.

Core server sends a ##LD_WAKE_ON_WAN## Message to a MDR which in turn send the Magic Packet on port 0 to the machine you want to wake up.

The protocol used is WOL.

In the below wireshark trace

192.168.1.217 ->Core

192.168.1.201 -> MDR

You do not need to have a static MDR.

Description

"Object reference not set to an instance of an object" Error when clicking on tasks - all devices or failed devices in the console.

Applies to 9.0 SP2 cores.

Cause

A bug in the console code.

Resolution

apply the patch following the instructions in the Readme.txt.

Install the following LD90-SP2-MCP_SD-2011-0217 and LD90-SP2-MCP_CONS-2011-0217(the console is needed with the SD patch)

LANDESK Management Suite 9.0 Monthly Component Patches (pre SP3 only)

Problem

"Invalid Product License"

"The LANDESK product license you're using to access Ivanti Web Management Console is invalid."

Cause

Com+ objects stopped

Core server not activated or hasn't been activated since renewing licenses

Information is cached in temporary files.

Solution

Verify if you can login to the core console first. If you can login, continue on. If you get a licensing error when logging in, try activating the core server first.

Start the COM+ objects

The COM+ objects are used to access certain information within the database. If either of the COM+ objects (LANDesk, LANDesk1) stops running, you can run into issues with remote control, software distribution, provisioning, and webconsole. Basically, if it needs to pull information from the database through IIS, it will fail unless both LANDesk and LANDesk1 are running.

1. Click on your start menu and type Component Services
2. Click through to Computers>My Computer>COM+ Applications
3. Right click each of the LANDesk COM+ applications and choose start

If you get any errors while starting the COM+ objects, please rebuild them: How to rebuild the LANDesk COM+ Objects

Activate the Core Server

Click on your start menu and type Core Server Activation

1. Enter your entitlement credentials
   • This was sent to your company contact when you purchased the product. If you don't know your credentials, reach out to support.
2. Click Activate

The following documents will be helpful if you run into activation errors:

Issue: Unable to Build Core Server Activation File

Troubleshooting Core Server Activation

Clear Windows and .Net Temporary Files on the Core Server

1. Go to Windows\temp
2. Delete as many files as the system will let you.
3. Run IISRESET -STOP in an admin command prompt
4. Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
5. Delete all the files in here. If any are held open by a process, run step 3 again.
6. Run IISRESET in an admin command prompt

Hi all,

I've installed the remote console on a Windows Terminal Server and applied the latest SU according to our core server environment. (2017.3 - SU3)

When connecting I'm presented with the following error message:

Console Initialization Error:  A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).

In a post from 2015, a reset of IIS was mentioned, I've restarted the IIS on the core using cmd -> iisreset /noforce but still get the same error.

Any suggestions?

Description

"Object reference not set to an instance of an object" Error when clicking on tasks - all devices or failed devices in the console.

Applies to 9.0 SP2 cores.

Cause

A bug in the console code.

Resolution

apply the patch following the instructions in the Readme.txt.

Install the following LD90-SP2-MCP_SD-2011-0217 and LD90-SP2-MCP_CONS-2011-0217(the console is needed with the SD patch)

LANDESK Management Suite 9.0 Monthly Component Patches (pre SP3 only)

Hello

Hopefuly someone can help with this, i have a colleague in another region if the business who accesses ivanti to citrix. The console loads up fine and hes able to log in , however when he goes into the properties of the say schedule tasks its complety grey. If he goes straight to the citrix server via RDP and loads the console  everything is fine. Does anyone have a ny ideas whats causing this ?

Hello Everyone,

I'm completely new to Ivanti (tried it months ago, followed a training course in march and now i'm installing it and trying to get it work).

Here's what i did so far:

Installed EPM 2017.3 and configured it.

Tried to create an advance agent and to deploy it with a scheduled task but nothing happen. After a while i decided to reboot the Core Server. After reboot i can't open the console (or the remote console) : Windows say the "sa" account is locked.

When i've installed the Core Server i didn't change the "sa" password and don't know it.

How can i unlock it?

Regards,

David

When trying to open persinfo.exe it crashes out

Trying to run as standard user, admin, and the run as admin option all present the same results
We have tried with the latest version and the same result

Event viewer shows the following

Faulting application name: PersInfo.exe, version: 1.1.8.0, time stamp: 0x56effa2c

Faulting module name: KERNELBASE.dll, version: 6.1.7601.24117, time stamp: 0x5add22d4

Exception code: 0xe0434352

Fault offset: 0x000000000001a06d

Faulting process id: 0xb2c8

Faulting application start time: 0x01d404a97dfa9c42

Faulting application path: C:\Program Files\AppSense\Tools\PersInfo.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: bd4dbad2-709c-11e8-8325-0050563f026f

and this one

Application: PersInfo.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentException

   at System.Drawing.Font.CreateNativeFont()

   at System.Drawing.Font.Initialize(System.Drawing.FontFamily, Single, System.Drawing.FontStyle, System.Drawing.GraphicsUnit, Byte, Boolean)

   at System.Drawing.Font..ctor(System.String, Single, System.Drawing.FontStyle, System.Drawing.GraphicsUnit)

   at System.Drawing.FontConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext, System.Globalization.CultureInfo, System.Object)

   at PersInfo.modPublic..cctor()

Exception Info: System.TypeInitializationException

   at PersInfo.modPublic.#=qrllA7tZRMBGNN68tT$nYnKRqghjjj$wUZFyaFNa3FCg=()

   at #=q57nsAPusayLoYMtk8$G2KACJjBrYZp7MIpxgfcbpwLs=.#=qUH3kfD6MpYr7pxXkyAWRmoTsqO7M7JZe_NuBrEKcYnhzzoNwuWbp1nZpZ51eVT9g(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(System.Object, Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(Microsoft.VisualBasic.ApplicationServices.UnhandledExceptionEventArgs)

   at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)

   at System.Windows.Forms.Control.WndProcException(System.Exception)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

   at System.Windows.Forms.NativeWindow+WindowClass.Callback(IntPtr, Int32, IntPtr, IntPtr)

Hello everybody,

we are experiencing some issue about Portal Manager. We deliver to our users link and programs to launch thru Portal Manager. We associated this links to some scopes that are created from queries. These queries are based on AD groups. The problem is often some icons in the Portal Manager are missing, then appear again after minutes. It's not steady. In the task the client is associated and delivered (green) but the user can't show it. Is there a best practice. Maybe some alternative. This system is not working so well... and it's important for our complany. The core is Ivanti 2017.3 Thanks.

Issue:

As seen when you attempt to login to the console (local or remote)

Console Initialization Error:  System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileNotFoundException: 
Could not load file or assembly 'AmpLicensingProxy, Version=3.0.1.72, Culture=neutral, PublicKeyToken=null' or one of its dependencies. 
The system cannot find the file specified. 
File name: 'AmpLicensingProxy, Version=3.0.1.72, Culture=neutral, PublicKeyToken=null' at LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) 

WRN: Assembly binding logging is turned OFF. 
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. 
Note: There is some performance penalty associated with assembly bind failure logging. 
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. 

   --- End of inner exception stack trace ---.

The error on a German console.

Konsoleninitialisierungsfehler: System.Web.Services.Protocols.SoapException: Die Anforderung konnte vom Server nicht verarbeitet werden. ---> System.Data.OleDb.OleDbException: Invalid object name 'ConsoleUser'. bei LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) --- Ende der internen Ausnahmestapelüberwachung ---.

More Info:

The error message seem to indicate that a file [AmpLicensingProxy] could not be loaded.While this is technically true, it is not specific to AmpLicensingProxy.

Cause:

This is caused by the MBSDK not having the access it needs.  Since a variety of issues can interfer with the MBSDK, a variety of solutions exist.

Solutions:

One or more of these *may* work for you.  All are not required.

• add the local "NETWORK SERVICE" user to "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" and "install:\Program Files (x86)\LANDesk\ManagementSuite" with FULL CONTROL
• If you have the database on a seperate SQL instance, be sure "hostname\instance_name" is set as the database server name
• Clear the temporary ASP.NET files.
• reboot the SQL server followed by the core server

Purpose:

Network Mapping is designed to help you understand your companies network. This may or may not be an accurate representation of your environment but will help you determine what is on the network and the bandwidth.

**Note**

THIS IS A NEW FEATURE AND ASK THAT ALL FEEDBACK IS SENT TO SUPPORT TO HELP BUILD A BETTER MAPPING TOOL.

This is using our multicast system and some Access points have Access Point Isolation (AP Isolation)

Prerequisites:

• This is only available on 2018.1
• CSEP is enabled on he subnet (will be covered in the process portion)
• At least one 2018.1 agent on the subnet

Process:

Agent Settings

By default the agent settings for network mapping are turned on. There is not much here other than:

• changing the Route Target- This will send the route info from the client to the target to the core. This could be the core or any other device on the network.
• Frequency- This is how often the route occurs

CSEP

Under the Self-electing subnet services choose the network mapping and in the subnet trees to the right, right click on a subnet and enable.

Network Map

The map will show different layouts based on the traceroute

You will see different colors for the line and this shows the response time of the ping. Green is good response time, yellow is some latency and red is big latency.

Lastly you will be able to drill down and have ability to RC, review provisioning and looking at inventory. You will also see the type of OS for that machine and it's ip.

This network map uses multicast to determine the Rep for the subnet but that rep will perform the traceroute. This route is for the subnet and devices the core knows about within that subnet will be added to the map. This will not tell you devices that are not managed but are in that subnet. This is designed to show you what your network looks like for the devices managed by you the Ivanti admin; this will include agentless scanned devices. The drill down is real time but the latency check is done during the route check which is 7 days by default as you saw but can be changed. This means the map will change as often as your end-users moving around from wired to wireless and vice versa.

DISCLAIMER

The following article contains information that may permanently delete information from the database.

It is CRITICAL that you have a full backup of your database prior to making any modifications to the database.

Failure to backup your database may result in permanent loss of some, or even all data.

How To:

When directed by Ivanti support, use this document to move all of the objects that a user account owns to another account, then back to the original account. These steps have been proven to resolve odd account issues (Possibly caused by updating the software, issues when changing LDAP servers, or other unknown causes). Once that is done you can delete the old account from the database, add the old account back, and then reassign all of the objects back to that user (Queries, scheduled tasks, provisioning templates, software packages etc).

Step by Step:

1) Backup the database if you have not already.

2) Create a local user account (Give that user a name like "TestUser") on the Core Server and add them to the "LANDesk Management Suite Administrators group".

3) You will want to verify that you can log in as the "TestUser" and that they have administrator rights in the Ivanti Console.

4) Stay logged in as the "TestUser" and then delete the user account that is having issues. Select the checkbox "Assign Objects to the Following User or Team" and select the "TestUser" account.

5) Refresh the console and verify that the bad account is gone from the console.

6) If the account is now gone, re-add it back into User Management and assign the account the proper rights/scopes that it should have.

7) Log out of the console and verify that the re-added account can successfully log into the console.

8) Log into the console with an admin user (If you are not already)

9) Delete the "TestUser" account and assign all of the objects back to the original account.

10) Verify that all of your objects are back onto the account.

What is Wake on LAN?

Wake on LAN is a technology whereby a magic packet is sent to a client that is powered off.  If a network card detects a magic packet directed to its MAC address, the computer will power on.  Both the motherboard and network card must support Wake on LAN.  Wake on LAN must be enabled in the BIOS.

How does LANDesk send a Wake on LAN magic packet?

LANDesk can send a Wake on LAN magic packet in one of three ways:

1. In the Delivery Method, configure the Multicast Domain Representative to send the Wake on LAN magic packet.

2. When creating a Scheduled Task, check the Wake on LAN option. 
    
   Note:

   Checking this option when the Delivery Method has the MDR sending the magic packet can result in the WOL packet not being sent at all.

3. In the Console, right click on a device in the Network View and choose Wake on LAN.
    
   Note for options 2 and 3:

   This packet is sent from the computer running the Console.  If the console is open on the Core Server, the Core Server sends the packet.  If a Remote Console is open on a client machine, the magic packet is sent from that client machine running the Remote Console.  If these machines are on different subnets, different results may occur based on network settings.

Is the Wake on LAN magic packet a TCP or UDP packet? Is it unicast or broadcast?

The magic packet is a UDP broadcast packet.  Because the device is off, it does not have an IP Address therefore the magic packet must be broadcast packet.  Also, since the device is off, it cannot give a proper response to a TCP packet, therefore the magic packet must be UDP.  If the packet is crossing networks or subnets, it is a directed broadcast packet.  Note that routers are usually configured to drop directed broadcast packets.

What port does LANDesk use to send the Wake on LAN magic Packet?*

By default LANDesk uses UDP port 0.  This can be configured on the Core Server by going to Configure &gt; Services &gt; Scheduler.  The LANDesk Console must be restarted for this change to take affect.

 
Note:

The MDR always sends using port 0.  In previous version, this cannot be configured.  In 8.7 SP5 and 8.8 or later version, This can be configured by setting the following registry key and restarting the Targeted Multicast service on the MDR.

HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast
Type: DWORD
Name: WOL Port

 
Note:

The web console will always send the magic packet from the core on port 0.

What issues may prevent devices from receiving a Wake on LAN magic packet?

1. If crossing subnets, routers are usually configured to drop directed broadcast packets. 

2. LANDesk uses port 0 for the magic packet by default.  Many firewalls may block this port.  This port is configurable on the Core Server but not on the MDR. 

3. The packet may be arriving but the network card or motherboard may not support Wake on LAN; or Wake on LAN is not enabled in the BIOS.

Why does a device wake up from a Remote Console but not from the Console on the Core Server?

This packet is sent from the computer running the Console.  If the console is open on the Core Server, the Core Server sends the packet.  If a Remote Console is open on a client machine, the magic packet is sent from that client machine running the Remote Console.  If these machines are on different subnets, different results may occur based on network settings.

After changing the Wake on LAN port under Configure &gt; Services &gt; Scheduler, the change does not appear to have occurred.  What could be the problem?

The problem could be two things:

1. If sending the Wake on LAN packet from the console, the console must be restarted for this change to occur.

2. This change does not modify the Wake on LAN port on the Multicast Domain Representative.  The Wake on LAN port on the MDR is not configurable and will always be set to 0.

If network devices such as routers and switches are blocking directed broadcast and not a single machine on a particular subnet is powered on, will Wake on LAN work?

If Wake on LAN magic packets cannot cross subnets, then at least one workstation must be available and running the LANDesk Agent with the Targeted Multicast feature.

Issue

From within the Ivanti EPM Console, one of the more useful features is the ability to right-click a machine and perform administrative tasks.

Some of these tasks are:

• Request an inventory scan
• Wake up a machine
• Shut down a machine
• Request a Security scan

When one of these options is selected the Ivanti EPM console makes a call to IIS and passes the command line parameters to the core.secure/corerequest.asmx page.

The URL for this page on the core server is:

http://localhost/landesk/managementsuite/core/core.secure/corerequest.asmx

This page is seen here being accessed from the core server.

Each command requires a client-side identifier, this can be the Machine GUID (found in the registry under HKLM\Software\Landesk\Common API) or the machines IP address.

Troubleshooting

If the right click commands fail to run, check the following.

1. Can theCoreRequest page be browsed from the Console running the commands?
   
   http://[core server name]/landesk/managementsuite/core/core.secure/corerequest.asmx
   
   
2. Verify that the command is being sent from the core server.
   
   On the core server under the \\[Your Core Server]\LDMAIN share the raxfer.log file will store the attempt to run the remote execute.
   
   

   Thu, 19 Mar 2009 10:20:56 4724 388 Performing remote execute, target 10.16.228.214:9594, hash 5b5c5c77

3. Verify that the command was received on the client.  In C:\Program Files\LANDesk\Shared Files\servicehost.log the command line parameters will be displayed.
   
   

   Thu, 19 Mar 2009 10:36:14 2608: Exec: Exec: Launch request <"C:\Program Files\LANDesk\LDClient\vulscan.exe" /id=7 /run ldiscn32.exe /NTT=slc-smith-88:5007 /S="slc-smith-88" /I=HTTP://slc-smith-88/LDLogon/ldappl3.ldz /NOUI> (sync 0, timeout 300)

Issue

Possible resolutions

1. If the 32-bit Core Console cannot be loaded then contact licensing to correct the license file. After correcting the licensing information, reactivate the core server.
2. Check the c:\windows\Temp directory. If there are a lot of .tmp files then:
   1. Open services.msc and stop the IIS admin service and the dependent services
   2. Delete all the files in the temp directory
   3. Run iisreset

cd %windir%\temp

or select Start -> Run and run:

%windir%\temp

Description

What happens when I right-click a machine in the inventory and select Wake on Wan?

First, make sure that you have the red circle in front of the machine to have the option Wake up available to you.

Core server sends a ##LD_WAKE_ON_WAN## Message to an MDR which in turn send the Magic Packet on port 0 to the machine you want to wake up.

The protocol used is WOL.

In the below Wireshark trace

192.168.1.217 ->Core

192.168.1.201 -> MDR

You do not need to have a static MDR.

Could someone please tell me where (if at all) the installation (setup.exe?) file/media may be on a LDMS 9.6 SP3 core server?

I'm hoping that it's lurking around somewhere so I can install the console software on a new management PC. If it helps, on my existing management PC the installed program that I run is "C:\Program Files (x86)\LANDesk\ManagementSuite\Console.exe".

Cheers

Matthew