Hi everyone,

I have specific needs of a brazilian customer that need provide access by web console for external users that work out of company, but the customer no want give to them the access to query and reports. The users should have access only to list of devices defined in your scope for the remote control. The system don't have the rule condition to no allow the access to query.

Any Ideia, ?

Thanks

32-bit Console for LANDesk Management Suite

Web Console for LANDesk Management Suite

The Web Console is an http based LANDesk console. The web console lacks many of the features and powers that the 32-bit console has as it was designed to be portable, easy to install, and serve basic IT functions. The web console can be loaded by pointing a web browser to the following location on a core server:

http://coreservername/remote

Initial Install and Configuration

The web console is installed by default on the core server and should be ready to go once the core is up and running. An Off-Core Web Console server is available to help off-load demand on the core server and will require a separate install. The Off-Core will also need to be patched separately. Configuration of the web console is performed automatically during install.

Troubleshooting

• Video:"Unable to validate the current user with the database"
• How to troubleshoot the web console error: "Unable to validate the Current User with the Database"
• Error: Invalid Product License when opening the Web Console
• Web Console - Remote Control Error: "The Remote Control Viewer was not installed properly"
• Explanation of LANDesk Abstraction Layer messages (logevents)

Additional Options and Information

Performance enhancements are often requested of the web console. However, most optimization has already been done in LANDesk 9.0. If the web console is slow then temporary files on the core, core performance (cpu and disk), and database server performance should be checked. It is possible to isolate applications to their own application pool however due to dependencies and other factors this should only be done by a LANDesk Support Engineer.

• Video:LANDesk® Management Suite Web Console
• How to enable filter by "Login Name" in the LANDesk Web Console

Notice: Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE:This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to the Web Console if this page hasn't helped.

In prior versions (8.6 SP5) the find filter was always open when you launch the web console.  In the current v9 version, it is closed and you have to click on the funnel to enter a criteria that you want to find.  Our techs use this on a frequent basis and wondered if there was a way to change it back to the having it always open.

Please advise if there is a way to change this back to always open.

We run multiple Support Groups, eg Infrastructure, Applications, Desktop Support. At 80% of SLA we need to send a message to the manager of the Assignee's Support Group only and not all the managers. How would I do this using Response Levels within Service Level Management?

Old LDAP causing usermanagement to hang. Need to have the users from old LDAP look to new LDAP

1) Yes, this will move any user that is curently using LDAP connection "1" 9or what ever the IDN for the LDAP is) to your new ldap. LDAP queries is resolved in my previous email.

2) Locate the APM_LDAP_SERVER table in your LDMS Database and note the APM_LDAP_SERVER_IDN of your current LDAP connection. Lets say that it is "1".

3) Create the new LDAP connection. DO NOT delete the old one yet.

4) Now go back to your database to the APM_LDAP_SERVER table and note the APM_LDAP_SERVER_IDN of your new LDAP connection. Lets say it is "2".

Now execute the following SQL staement;

update ConsoleUser set APM_LDAP_SERVER_IDN = '2' where APM_LDAP_SERVER_IDN = '1'

**Make sure to change out the values of 1 & 2 to your actual LDAP values.**

5) This will move all of your users and all of their settings to your new LDAP connection.

Here are the statements that will change the LDAP queries as well;

update apm_policy_query set ldap_server_dbid = '2' where ldap_server_dbid = '1'

update apm_policy_query set queryroot = 'newLDAPname' where queryroot = 'oldLDAPname'\

**Make sure you swap out the 2 & 1 for the same values you found for the consoleuser statements I gave you, and replace the "oldLDAPname" and "newLDAPname" with the correct values.

Also, check your ld_ldap_targets table in your DB and tell me if you have anything in there with values in the ldap_source_Idn column that match the values from the consoleuser table. If you do, you will also need to run the following statement;

update ld_ldap_targets set ldap_source_Idn = '2' where ldap_source_Idn = '1'

**Make sure you swap out the 2 & 1 for the corresponding values

6) Running this will go pretty quick. It will depend on the # of users that you have in your DB. Running it after hours is probably not necessary, but is a good idea if you can wait. I would also backup the Database before you make any changes.

Hi,

We have been testing Windows 8 Pro in our Office with Landesk 9.5 and noticed that the remote control is very slow accessing a Windows 8 Machine and I can only see the top left hand corner of the screen as if it's not scalling correctly. Has anyone encountered this issue?

Testing remote control on a Windows 7 Machine doesn't experience these issues

Using Landesk 9sp3.  Content replication claims to be successful and while inventory updates from child to rollup core just fine, the packages I create on the rollup are not appearing on the child cores.  Are the packages suppose to be sent from rollup core to child cores on each replication pass?

Chris.

I am trying to install the remote console on my machine after successfully upgrading my core server to 9.5, and the install keeps failing.  I am not sure why it is failing either.  I have installed .net 4.0 and fully patched my machine.  I have attached the log file that I am receiving from the installation failure.  I am running this install from a network drive, not sure if that makes any difference.

I am trying to upgrade my LDMS Remote Console to v9.5.  I have successfully upgraded my core, installed .net 4.0 on my workstation, installed all other required windows updates, and when I run the installer, it fails on Upgrading Remote Console.  I have uninstalled all LANDesk components, disabled SEP, and it still fails.  I am not sure why.  I have attached the log file to this post.  Since there is very little information on upgrading the console, I was going off of what others have posted in similar discussions. I kicked off the remote console from the main setup.exe file for LDMS9.5.  I was never given the option to select what I wanted to do since, at first it detected my current installation of the console.  Even after uninstalling the Landesk components, and several reboots, the installer still picks up where it left off, on the Upgrading the Remote Console portion.

Any help would be appreciated.

I am trying to upgrade my LDMS Remote Console to v9.5.  I have successfully upgraded my core, installed .net 4.0 on my workstation, installed all other required windows updates, and when I run the installer, it fails on Upgrading Remote Console.  I have uninstalled all LANDesk components, disabled SEP, and it still fails.  I am not sure why.  I have attached the log file to this post.  Since there is very little information on upgrading the console, I was going off of what others have posted in similar discussions. I kicked off the remote console from the main setup.exe file for LDMS9.5.  I was never given the option to select what I wanted to do since, at first it detected my current installation of the console.  Even after uninstalling the Landesk components, and several reboots, the installer still picks up where it left off, on the Upgrading the Remote Console portion.

Any help would be appreciated.

Hi,

I'm having an issue after OS deployment using Landesk Management Console 9.5

Long story short: I have a new notebook (Fujitsu Lifebook LH532) that I sysprepped. I am able to PXE boot from this machine and I am able to hit F8 and load WinPE. I am able to start the capture script and everything goes well. I reboot the machine and I PXE boot again, load WinPE, start the deploy script and shut down the machine.

When I power it up I'm getting the following error message on a black screen:

File: \Boot\BCD

Status: 0xc000000f

Info: An error occurred while attempting to read the boot configuration data.

I was able to capture and deploy the OS on that machine the first couple of times I tried, but the image was something like 24 - 26GB (too big for just a Windows 7 Professional SP1 image, without software nor patches installed). I had 3 partitions, one reserved (2GB), one recovery (14GB) and the last one was the OS. In this scenario I was able to power on the machine without the \Boot\BCD error. To slim down the OS image, I deleted all the partitions, reinstalled the OS from the DVD, installed the necessary drivers and now I have two partitions (100MB reserved and the OS partition). I am able to reboot the pc and it work just fine, so I assume that the image is ok. The image I am able to capture is only 8GB (only OS and drivers, no programs or patches installed). Unfortunately if I deploy it to that machine I get the \Boot\BCD error.

I would like some help on this, especially I want to know what is causing the \Boot\BCD error. Maybe the capture and deploy scripts I'm using? O maybe something else?

Capture script:

[VALUES]

Task=7

ScriptName=Marco_Capture_Windows_7_Imagew

ScriptDescription=Capture Windows 7 image with IMAGEW.EXE v2

FallBackNIC=

UseFallBackNIC=FALSE

ImageUserName=mtagliabue

ImageDomain=PRAXIDOMAIN

ImagePassword=20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F

ImageToolType=11

ImageUNC=\\ifas\ITSGROUP\LANDesk\images

ToolUNC=\\landesk\ldmain\osd\imagew 2\imagew.exe

ImageToolCmd=H:\osd\IMAGEW~1\imagew.exe /b /uy /d:0 /rb:0 /max:2GB /f:"""i:\LANDesk\images\%Computer - Device Name%"""

[OWNER]

GUID=630c4e24-8a69-4000-a0f3-3400c6940b90

OSDPLUG=TRUE

DESCRIPTION=Capture Windows 7 image with IMAGEW.EXE v2

NAME=Marco_Capture_Windows_7_Imagew

TYPE=WinPE

[JOBPARAM]

ABORT_ON_CMD_FAILURE=1

TASK_COMPLETION_ENABLED=FALSE

[MACHINES]

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/bootfile.exe" /disableclientqueue

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr16.dll" /disableclientqueue

REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr32.dll" /disableclientqueue

REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/lddefrag.exe" /disableclientqueue

REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/FlushBuffer.exe" /disableclientqueue

REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cicfgmgr.vxd" /disableclientqueue

REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cindis.vxd" /disableclientqueue

REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/copyfile.exe" /disableclientqueue

REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.img" /disableclientqueue

REMEXEC9=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ChangeBCD.exe" /disableclientqueue

REMEXEC10=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="%LDMS_CLIENT_DIR%\BCD" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/BCD.dat" /disableclientqueue

REMEXEC11=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe" /disableclientqueue

REMEXEC12=<qt/>%LDMS_CLIENT_DIR%\ChangeBCD<qt/> <qt/>%LDMS_CLIENT_DIR%\bcdedit.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/>

REMEXEC13=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="C:\boot.wim" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.wim" /disableclientqueue

REMEXEC14=<qt/>%LDMS_CLIENT_DIR%\copyfile.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/> \boot\BCD

REMEXEC15=<qt/>%LDMS_CLIENT_DIR%\lddefrag.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/>, STATUS

REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\FlushBuffer.exe<qt/>, STATUS

REMEXEC17=<qt/>%LDMS_CLIENT_DIR%\bootfile.exe<qt/> %LDMS_CLIENT_DIR%\boot.img /keep /bootunsafe, ASYNC

BEGINWINPE=TRUE

REMPING18=WINPE, TIMEOUT=1800

REMEXEC19=diskpart /s X:\LDClient\rmvol.txt

REMEXEC20=ldrun drvmap.exe PRAXIDOMAIN\mtagliabue 20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F I: """\\ifas.praxi.com\ITSGROUP""", STATUS FACILITY=3513

REMEXEC21=ldrun drvmap.exe PRAXIDOMAIN\mtagliabue 20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F H: """\\LANDESK.praxi.com\ldmain""", STATUS FACILITY=3513

REMEXEC22=ldrun sdclient /f /o /dest="X:\LDClient\assvol.txt" /p="http://%CUSTJOBHOSTIP%/landesk/files/assvol.txt" /disableclientqueue, STATUS

REMEXEC23=ldrun tokreplw X:\LDClient\assvol.txt partition=2

REMEXEC24=diskpart /s X:\LDClient\assvol.txt

REMEXEC25=cmd /c del /f /q C:\boot.wim

REMEXEC26=ldrun H:\osd\IMAGEW~1\imagew.exe /b /uy /d:0 /rb:0 /max:2GB /f:"""i:\LANDesk\images\%Computer - Device Name%"""

REMEXEC27=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixVista.bat"

REMEXEC28=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/fixntfs.exe"

REMEXEC29=ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe"

REMEXEC30=ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixWindows.exe"

REMEXEC31=ldrun reboot, timeout=2

Deploy script:

[VALUES]

Task=8

ScriptName=Marco_Deploy_Windows_7_Image

ScriptDescription=Deploy Windows 7 image with IMAGEW.EXE v2

MCast=0

FallBackNIC=

UseFallBackNIC=FALSE

ImageUserName=mtagliabue

ImageDomain=PRAXIDOMAIN

ImagePassword=20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F

ImageToolType=11

ImageUNC=\\ifas\ITSGROUP\LANDesk\images\LD5C9AD8653BE9.TBI

ToolUNC=\\landesk\ldmain\osd\imagew 2\imagew.exe

Partition=2

ImageToolCmd=h:\osd\IMAGEW~1\imagew.exe /r /o /d:0 /f:"""i:\LANDesk\images\LD5C9A~1.TBI""" /rb:0

ImageToolCmdsFile=\\LANDESK\LDMAIN\LANDESK\FILES\Marco_Deploy_Windows_7_Image.txt

IsSysPrepImage=1

IsVistaSysPrep=1

UseExistingSysPrep=0

ExistingSysPrepFile=

SysPrepFile=\\LANDESK\LDMAIN\LANDESK\FILES\Marco_Deploy_Windows_7_Image.xml

RemoteSysPrepCopyPath=c:\unattend.xml

SysPrepTargetedType=8

UseInventoryName=1

ComputerNameTemplate=LD$MAC

ComputerNameStartNumber=0

ClientInstallDomain=PRAXIDOMAIN

ClientInstallUsername=mtagliabue

ClientInstallPassword=20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F

ClientInstallUNC=\\landesk\ldlogon

ConfigProcessors=0

ImageHWType=0

ImageOSType=0

ImageProcessorType=0

RemoteProcessorPath=%windir%\inf\hal.inf

ConfigAdvancedMCast=0

UseWOL=FALSE

WOLSeconds=120

DiscoveryType=0

MaxTMCThreads=5

MinTMCSleep=1

MaxTMCSleep=200

BANDWIDTH_WAN=100

BANDWIDTH_LAN=100

SubrepTTL=14

TargetTTL=2

[OWNER]

GUID=3a0035d1-0433-4b53-ad02-ece95da037ca

OSDPLUG=TRUE

DESCRIPTION=Deploy Windows 7 image with IMAGEW.EXE v2

NAME=Marco_Deploy_Windows_7_Image

TYPE=WinPE

[JOBPARAM]

ABORT_ON_CMD_FAILURE=1

TASK_COMPLETION_ENABLED=FALSE

AUTOCOMPUTERNAME=LD$MAC

AUTOCOMPUTERNAMESTARTNUMBER=0

[MACHINES]

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/bootfile.exe" /disableclientqueue

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr16.dll" /disableclientqueue

REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tlibr32.dll" /disableclientqueue

REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/lddefrag.exe" /disableclientqueue

REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cicfgmgr.vxd" /disableclientqueue

REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/cindis.vxd" /disableclientqueue

REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/copyfile.exe" /disableclientqueue

REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/tokreplw.exe" /disableclientqueue

REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.img" /disableclientqueue

REMEXEC9=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/vboot/ChangeBCD.exe" /disableclientqueue

REMEXEC10=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="%LDMS_CLIENT_DIR%\BCD" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/BCD.dat" /disableclientqueue

REMEXEC11=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe" /disableclientqueue

REMEXEC12=<qt/>%LDMS_CLIENT_DIR%\ChangeBCD<qt/> <qt/>%LDMS_CLIENT_DIR%\bcdedit.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/>

REMEXEC13=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /dest="C:\boot.wim" /p="http://%CUSTJOBHOSTIP%/landesk/vboot/boot.wim" /disableclientqueue

REMEXEC14=<qt/>%LDMS_CLIENT_DIR%\copyfile.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/> <qt/>%LDMS_CLIENT_DIR%\BCD<qt/> \boot\BCD

REMEXEC15=<qt/>%LDMS_CLIENT_DIR%\lddefrag.exe<qt/> <qt/>%LDMS_CLIENT_DIR%\boot.img<qt/>, STATUS

REMEXEC16=<qt/>%LDMS_CLIENT_DIR%\bootfile.exe<qt/> %LDMS_CLIENT_DIR%\boot.img /keep /bootunsafe, ASYNC

BEGINWINPE=TRUE

REMPING17=WINPE, TIMEOUT=1800

REMEXEC18=diskpart /s X:\LDClient\rmvol.txt

REMEXEC19=ldrun drvmap.exe PRAXIDOMAIN\mtagliabue 20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F I: """\\ifas.praxi.com\ITSGROUP""", STATUS FACILITY=3513

REMEXEC20=ldrun drvmap.exe PRAXIDOMAIN\mtagliabue 20EDE9C29C2A1F9A23AE59DBA4C3EDD5826280A115F H: """\\LANDESK.praxi.com\ldmain""", STATUS FACILITY=3513

REMEXEC21=ldrun sdclient /f /o /dest="X:\LDClient\LDPathExist.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/LDPathExist.exe" /disableclientqueue, STATUS

REMEXEC22=ldrun LDPathExist.exe """I:\LANDesk\images\LD5C9AD8653BE9.TBI""", STATUS

REMEXEC23=ldrun LDPathExist.exe """H:\osd\imagew 2\imagew.exe""", STATUS

REMEXEC24=diskpart /s X:\LDClient\WIPECLEANDISK0.TXT

REMEXEC25=ldrun h:\osd\IMAGEW~1\imagew.exe /r /o /d:0 /f:"""i:\LANDesk\images\LD5C9A~1.TBI""" /rb:0

REMEXEC26=ldrun sdclient /f /o /dest="X:\LDClient\diskinfo.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/diskinfo.exe" /disableclientqueue, STATUS

REMEXEC27=ldrun sdclient /f /o /dest="X:\LDClient\assvol2.txt" /p="http://%CUSTJOBHOSTIP%/landesk/files/assvol.txt" /disableclientqueue, STATUS

REMEXEC28=ldrun sdclient.exe /f /o /dest="x:\ldclient\RMVOLLETTER.TXT" /p="http://%CUSTJOBHOSTIP%/landesk/files/RMVOLLETTER.TXT" /disableclientqueue

REMEXEC29=ldrun tokreplw X:\LDClient\assvol2.txt partition=2

REMEXEC30=diskpart /s X:\LDClient\RMVOLLETTER.TXT

REMEXEC31=diskpart /s X:\LDClient\assvol2.txt

REMEXEC32=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixVista.bat" /disableclientqueue

REMEXEC33=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/fixntfs.exe" /disableclientqueue

REMEXEC34=ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe" /disableclientqueue

REMEXEC35=ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixWindows.exe" /disableclientqueue

REMEXEC36=ldrun x:\cba8\FixWindows.exe 2

REMEXEC37=ldrun sdclient /f /o /dest="C:\unattend.xml" /p="http://%CUSTJOBHOSTIP%/landesk/files/Marco_Deploy_Windows_7_Image.xml" /disableclientqueue, STATUS

REMEXEC38=ldrun sdclient /f /o /dest="C:\ldsleep.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/ldsleep.exe" /disableclientqueue, STATUS

REMEXEC39=ldrun tokreplw C:\unattend.xml COMPUTERNAME=%Computer - Device Name%

REMEXEC40=cmd /c copy /y X:\LDClient\guid.pds C:\LDISCAN.CFG

REMEXEC41=ldrun tokreplw C:\LDISCAN.CFG DEVICEID=%Computer - Device ID%

REMEXEC42=ldrun tokreplw C:\LDISCAN.CFG IMAGEPATH=\\ifas.praxi.com\ITSGROUP\LANDesk\images\LD5C9AD8653BE9.TBI

REMEXEC43=sdclient.exe /f /o /dest="x:\ldclient\FixUnattend.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixUnattend.exe" /attemptpref /disableclientqueue

REMEXEC44=ldrun x:\ldclient\FixUnattend.exe

REMEXEC45=ldrun diskinfo extend_last_partition

REMEXEC46=ldrun sdclient.exe /f /o /dest="x:\ldclient\HIIClient.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/HIIClient.exe" /disableclientqueue

REMEXEC47=ldrun /qt HIIClient /uncpath

REMEXEC48=ldrun x:\Windows\system32\bcdboot.exe C:\Windows

REMEXEC49=ldrun reboot, timeout=2

Reading similar problems on the internet, I modified the default scripts adding these lines:

for the Capture script I added these lines:

REMEXEC27=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixvista.bat" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixVista.bat"

REMEXEC28=ldrun sdclient.exe /f /o /dest="x:\ldclient\fixntfs.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/fixntfs.exe"

REMEXEC29=ldrun sdclient.exe /f /o /dest="x:\ldclient\bcdedit.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/bcdedit.exe"

REMEXEC30=ldrun sdclient.exe /f /o /dest="x:\cba8\FixWindows.exe" /p="http://%CUSTJOBHOSTIP%/landesk/files/FixWindows.exe"

for the Deploy scritp I added this line:

REMEXEC48=ldrun x:\Windows\system32\bcdboot.exe C:\Windows

Unfortunately I still have this issue.

Any help on this?

Thank-you

Hey Peeps,

We are experienceing some performance issues with the remote console for LDMS. The console on the core is fine. If we drag an OSD script to the PXE menu, it takes about 30seconds for the item move to work - normally the mouse pointer wold change when you drag an item to the PXE menu list before you drop the item - this is also delayed.

Another example of behaviour is selecting cliens from the "All Devices" tree. In LDM9SP3 we could highlight any client and then begin typing the client computer netbios name to jump to that client in the list. You have to type the whole computer name within a second otherwise you jump to an incorrect client in the list - again, you can select clients by typing in their name fine on the core console.

Has anyone else expereicnce this? We done an inplace upgrade of all of the remote consoles.

We have a ticket open but, unusually, the response to this ticket is somewhat painfully slow.

Cheers

I want to do a software monitoring report but only for active ( turned on) machines. I need to produce a report of all microsoft products that are installed on active machines only. But I can't seem to figure out how to tell the query within software monitoring or using the query tool on the management console.

LD9.5

Does anyone know if they are making any changes in 9.5 SP1 to make the console faster responding to device status?

I have set my agent setting in the console every which way and nothing makes a difference. Here is what I've noticed.

1. Whether I set it to all visible items DNS or not or selected items Dns or not  I see at the bottom of the console it pinging devices  not in my visible screen or the one I have selected. As you scroll down the list of devices things get worse which makes sense if its trying to ping every computer in my database.

2. Sometimes I get the red circle but when I click on the device the circle goes away so I can't get some of the options, wake on lan/wan etc.

3.It seems to be slower on my core console.

4. If you do a query I notice at the bottom of the console, so many devices selected so it must be trying to ping every device since it thinks they are all selected even though I can't veiw them all at once and have not selected any on the screen.

There is no support for Common Access Cards in LANDesk Web Console. It currently only supports NTLM authentication. You can submit an enhancement request with the link below.

Submit an Enhancement Request

Two servers, new install of 9.5, schedulder with an AD account and COM+ objects configured with ad account. Local admin rights and Landesk console administrator rights assigned on both cores for the account. I can manually "Copy to another core", but I can not for the life of me get auto sync to work. Auto Sync stays in a pending state, and an ldms file is never copied to the exportableque folder.

Any suggestions or something I'm missing?

I have a report that shows me the value of one registry key on all of my systems. What I need is only grab one device per subnet instead of everything. Does anyone know how to do this? The goal here is to have this trimmed down query and attach to a scheduled task so unless there is a way to export to excel, trim from there an reimport the list from excel into a new group, that won't work. Thanks in advance guys ... I'm anxious to see what bubbles up here.

Hello Inspector Team,

You guys did a really good job on developing the Inspector. This got some great possibilities for the future.

Looking at the xml code I can see how you added the processes and services to the inspector and I would like to do the same for the Application and System Event viewer.

Can you help me get started?

Kind Regards,

Ruud Blom

Error

When opening the Console, after entering your credentials and trying to login, you receive the error: Console Initialization Error:  The network path was not found landesk.

In the Console.exe.log, you will see errors like this:

05/30/2013 11:58:13 INFO  3280:Main Thread RollingLog : Disconnect network connection '\\CORESERVER\LDMAIN'

05/30/2013 11:58:13 INFO  3280:Main Thread RollingLog : Canceling network connection '\\CORESERVER\LDMAIN' failed.  Retrying

05/30/2013 11:58:15 INFO  3280:Main Thread RollingLog : Failed to map drive to \\CORESERVER\LDMAIN. Verify that a connection has not already been established. Error: The network path was not found.

Reason

Opening a Console requires access to the LDMAIN share on the Core Server using the credentials entered to log into the LANDesk Console. If you opened already a connection to the LANDesk Core server to access another share, with a different set of credentials, you will get this error. Windows will not let you connect to the same server from another device with multiple credentials.

So, if you have opened a share on the Core server using account X, you can't login to the Console using account Y.

Check with the 'Net use' command in a command prompt if not sure.

Resolution

Close all exisiting connections to the Core Server before logging into the Console. Check with the 'net use' command and use 'net use path/driveletter /d' to close any remaining open connections.