Customizing the LANDesk Agent using the NTSTACFG.in# file

Version 14

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.x

    The following list of Agent customizations are things that can be changed in the agent configuration.ini files.  Most of these changes are not available in the GUI and must be done manually.

     

    NOTE:  These changes should not be made without careful consideration and testing.  These changes can have negative effects if they are not tested and carefully evaluated.


     

    SDMCache location

     

    To change the default sdmcache folder directly at the agent installation, you can modify the c:\Program Files\LANDesk\ManagementSuite\ldlogon\NTSTACFG.INI file (on the Core Server):

     

    1.  Edit this file using Notepad or a similiar text editor.
    2.  Find the line:

     

    REG00=HKEY_LOCAL_MACHINE, SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast\Cache Directory, %DEST%\SDMCache, , REG_SZ

     

    and change it to:

     

    REG00=HKEY_LOCAL_MACHINE, SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast\Cache Directory, [MY_PATH], , REG_SZ

     

    Note: [MY_PATH] should be changed to the path you want as cache folder.

     

    3.  Open the console on the Core Server, and from the Agent Configuration tool, click on the 'Rebuild all' icon (approximatively on the middle of the icons bar).

     

    4.  Install the agent on client computer.

     

     

    Agent install drive location

     

    1. Modify the ntstacfg.in# file.  Search for the system variable %DEST%.

     

    2. In a command line or cmd windows SET DEST = <the new drive location>.

     

     

    Remote control timeout length

     

    NOTE: In LDMS 9.0 SP2 this configuration option has been added to the Agent GUI options.


    To make this change part of the Agent Configuration use these steps listed below.

     

     

     

    1. Modify the ntstacfg.in# file so that the client install modifies this registry value that controls the remote control timeout:
    HKLM\System\CurrentControlSet\Services\issuser\ImagePath
    2. Change the following:
    Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ISSUSER
    Value: ImagePath
    Example Value: C:\PROGRA~1\LANDesk\LDClient\issuser.exe /SERVICE /A60
    (This will increase the timeout to 60 minutes)

    3. 
    To import the settings from the INI file to the Ntstacfg.in# file, Stamper.exe needs to be run. Restart the inventory service to run Stamper.exe. Execution of Stamper.exe is part of the inventory service starting.


    4.  Build the Agent configuration or run “Rebuild All” to update all existing client configurations.

     

     

    How to include additional files with Agent install

     

    1.  In order to use the Mergeini.exe tool, create an INI file that contains the additional commands that will be added to the Agent configuration INI file. By making these settings in a separate file, LANDesk® Management Suite patches and services packs can modify or replace the Ntstacfg.in# file without overwriting custom modifications. Place the INI file in the Ldlogon directory. Create the custom INI with the following commands:

     

    [Common Base Agent Post Copy]
    FILE150000=MyLogo.bmp, MyLogo.bmp, NOCOPYERROR

     


    2.  Once the INI file has been saved, create a new string value in the registry that contains the full path to the INI file under the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\LANDESK\ManagementSuite\Stamping\Files.

     

    The string name is of your choosing.


    Note: If the path name contains a space be sure to use quotes around the full path (i.e "C:\Program Files\LANDesk\mamangementsuite\ldlogon\MyScript.ini").

     

    3.  To import the settings from the INI file to the Ntstacfg.in# file, Stamper.exe needs to be run. Restart the inventory service to run Stamper.exe. Execution of Stamper.exe is part of the inventory service starting.

     

    4.  Build the Agent configuration or run “Rebuild All” to update all existing client configurations.

     

     

    Increase the SDMCache cleanup time from the default of 14 days


    To change the default sdmcache folder directly at the agent installation, you can modify the c:\Program Files\LANDesk\ManagementSuite\ldlogon\NTSTACFG.IN# file (on the Core Server):

     

    1.  Edit this file using Notepad or a similiar text editor.
    2.  Find the section titled: [Multicast Post Copy]

     

    Add the following line:

     

    REG99=HKEY_LOCAL_MACHINE, SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast\Discard Period, 7776000, , REG_DWORD

     

    3.  Open the console on the Core Server, and from the Agent Configuration tool, click on the 'Rebuild all' icon (approximatively on the middle of the icons bar).

     

    4.  Install the agent on client computer

     

    This setting can also be changed on an existing agent without reinstalling the LANDesk Agent.  To do so, update the registry value shown below:

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast]


    Modify "Discard Period"=dword:0002a300 to reflect # of seconds you want the file to stay in cache


    After making this change, restart the LANDesk Targeted Multicast Service

     

     

    Brokerconfig automation (configurebroker.exe)


    To automate the creation of Management Gateway certificate generation, please see the following LANDesk Community article:

     

    http://community.landesk.com/support/docs/DOC-1888

     

     

    Add custom local scheduler tasks to the Agent Install

     

    1.  In order to use the Mergeini.exe tool, create an INI file that contains the additional commands that will be added to the Agent configuration INI file. By making these settings in a separate file, LANDesk® Management Suite patches and services packs can modify or replace the Ntstacfg.in# file without overwriting custom modifications. Place the INI file in the Ldlogon directory. Create the custom INI with the desired commands:

     

    [Policy Management Post Copy]

     

    EXEC10004=%DEST%\LOCALSCH.EXE /taskid=[Your Task ID ex: 7777] /exe="[path:\YourEXEHere.exe" /cmd="[/Your EXE Parameters]" /freq=[Time to repeat in seconds] /start="[Current date/time ex: 06 Jan 2006 16:56:20]"

     

    2.  Once the INI file has been saved, create a new string value in the registry that contains the full path to the INI file under the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\LANDESK\ManagementSuite\Stamping\Files.

    The string name is of your choosing.

    Note: If the path name contains a space be sure to use quotes around the full p

     

    The list of Local Scheduler parameters and commands can be seen by browsing to \program files\landesk\ldclient\ and running localsch.exe /?.

     

    LocalSchOptions.JPG


     

     

    Change default shortcut parameters (add /F /SYNC to inventory, remove the /showui for vulscan, etc)


    PreReq: Download Orca MSI Editor
    http://www.technipages.com/download-orca-msi-editor.html

     

    1. Create an Advanced Agent of the Agent you wish to modify.

     

    2. Open the agent MSI file with Orca.  The Agent MSI file will be located in the \ManagementSuite\ldlogon folder and will have the same name as the Agent from the console view.

     

    Go to Custom Action, Sort by Source and Look for the following Target’s and add a /F- like below.

     

    Target One: [LDCLIENT]\LDISCN32.EXE /NTT=LANDESK21:5007 /S="LANDESK21" /I=ldappl3.ini /NOUI /NOCD /SYNC /F-

     

    Target Two: [LDCLIENT]\LOCALSCH.EXE /taskid=777 /exe="[LDCLIENT]\LDIScn32.EXE" /cmd="/NTT=LANDESK21:5007 /S=LANDESK21 /I=HTTP://LANDESK21/ldlogon/ldappl3.ldz /NOUI /F-" /freq=86400 /autodelay=0|60

     

    Target Three: InstallShortcut "[ProgramMenuFolder][PROGRAM_GROUP]" "[INVENTORYSCANSHORTCUT]" "[LDCLIENT]\LDIScn32.exe" "/NTT=LANDESK21:5007 /S=LANDESK21 /I=HTTP://LANDESK21/ldlogon/ldappl3.ldz /V /F-" ""

     

    3.  Save the MSI file and now you can create a Self contained executable, a scheduled task deployment, advanced agent deployment, etc. All work and add the switch correctly.