I read on a post that there is a patch to fix an issue with the Mirror driver which breaks Aero in Windows 7 after you remote control to a desktop. I also read you have to open a trouble ticket to recieve the patch.
Redeploying the agent without the mirror driver fixes the problem, but I do not want to redeploy a large number of clietns.
Is it possible to get this patch? If so where?
We have just upgraded from LANDesk 8.8 to LANDesk 9.0.3.1.
When we remote control into a PC, send ctrl-alt-delete and attempt to type in the username and password there is approx a 5 second delay before what is type appears.
Once logged on, typing in notepad appears instantly.
Has anyone come accross this issue and know of a resolution?
Thanks
Hi,
I would need some advises on configuring LANDESK's remote control feature, this is what we want to do:
1. By default, all PCs are enabled with LANDESK remote control feature. User will be prompted and grant permission before LANDESK operator/admin can remote control the PC.
2. Now, we have some PCs where we want to remote control without the need of user permissions to troubleshoot some issues. We want to restrict the remote access without user interaction to 1 or 2 LANDESK operators only, not to all remote control operators.
I know that we can create separate set of LANDESK agent to be able to remote control without user permission.
But it does not restrict to approved LANDESK remote control operator only. All LANDESK operators with remote control access can remote control the PC without permission.
What we want is only allow approved administrator to remote control the PC without permission while the rest of the LANDESK operator follows the normal procedures (user gets prompt to ask for remote control access. If the user click "Yes", only one can remote control the screen).
I can't figure out how to restrict the permission to particular admin only.
Is there a way to do this? I am using LANDESK 9, SP2.
Appreciate if someone can shred some lights on this.
Thanks.
Ever since we upgraded the core to 9.5 we haven't been able to remote control any computers. We have yet to roll out the clients as we wanted to make sure everything works normally. There were no errors reported during the upgrade.
Any ideas? We are not using AppBlocking. I read about the whitelist issues, but I don't think that apply's to us.
Configuration:
Windows 7 Pro with autologin on a local account
Without remote control, so on the machine really , to change the login we had to push the "Shift" button and we have the popup loggin (NO PROBLEM)
BUT, on remote control i push the Shift Button and the autologin continue (????????), so I can't change the login!
I try the same agent on a XP machine (NO PROBLEM)
I've just the problem on Windows 7
Can you help me, Please.
Hi there
We are on 2017.1. Admin users in our company have two users, one with "normal user" rights and one with administrative permission. We usually start Chrome with our administrative user and connect to our clients from there. We have to enter our credentials again after choosing a device from the list, is there a way to use the windows credentials there instead of typing them again?
I have various admins reporting that this has worked with 9.6 SP3, it never has for me
Thanks
Dominik
We are starting to upgrade to Windows 10. When we remote connect to the Winodows 10 boxes the connection is really slow. When you send the cont. alt delete command it takes about about minute for it to show the login. The user see it right away. Another example is if you are using Window Eplorer to browse to a location it will take about 20-30 seconds to show what you are typing. We do not have any issues with our Windows 7 boxes. We are set to optize for for fastest connection (LAN). Has anyone else had this issue? we are on landesk 9.60.2.48 sp3. Any help would be appreciated.
thanks
Kathy
Hi All,
Was wondering why does this error happen:
We're unable to use the remote control features on the Core Server Console even though the device is online. Then we tried to using the remote console to remote control to the device and it works. Any idea why cant the core server console cant remote control but the remote console are able to remote to the device? What should I do? (I've tried rebooting the core server but still wont work)
Thanks
With the release of LANDesk Management Suite 2016.3 SU3, and Ivanti Endpoint Manager 2017.x, we have upgraded our hash encryption algorithms to use SHA-256 hashes for the pass-through Authentication Token. This change to the algorithm prevents older agents from being able to decrypt the token, causing the following errors for both HTML and Legacy remote control.
Error when using HTML Remote Control:
Authentication Failed, Invalid Credentials or No rights to Remote Control
Error when using Legacy Remote Control:
The signed rights document was not valid. Authentication failed.
Updating the agent to match the core version will resolve the issue, as the newer agent will be able to decrypt the authentication token.
It has always been the position of Ivanti Support that Agents should be updated as quickly as possible after the core server has been upgraded. Although this is an inconvenience, it is working as designed and is expected Ivanti admins will work to upgrade their agents as quickly as possible to return to full functionality.
There is a workaround for HTML Remote Control that can be used when the agent cannot be updated in a timely fashion, or at all.
When presented with the authentication error, click OK, and you will be prompted for your credentials. Enter your credentials in manually and, provided you have the necessary access, it will successfully initiate the remote control session.
*** There is no work around for Legacy RC. To remote control an older agent, you will need to use HTML RC.***
When you remote control from a remote console and it lauches the remote viewer, you are missing the remote execute (Run bar) as well as the file transfer icon.
Cause:
This is caused by the issftran.dll and issftran64.dll are missing from the remote control install package.
Solution:
Copy the issftran.dll and issftran64.dll from the ManagementSuite directory from your core machine to the ManagementSuite directory on your console machine.
When you then launch the remote viewer, you will again have the remote execute and file transfer options.
Issue
You are remotely controlling a client computer using the Landesk legacy console.
You need to transfer some files to the computer but when you click the "file transfer" option, the "Landesk Remote Control" window shows a blank screen.
No logical volume seems to be detected on the remote client device.
Cause
This is a known issue that is currently being addressed by our engineering team.
Please note that this issue only occurs when doing a remote control session from a legacy remote console.
A bug report has already been opened for this issue: TFS 282932 - File Transfer UI is blank
Workaround
Customers experiencing this issue are advised to use the HTML5 remote control.
They may also initiate the remote control directly from the core server as only remote consoles are affected by this issue.
This is found in LANDesk Management Suite version 9.6 Service pack 2
"Unable to find the remote control web service on <CORE SERVER>"
"Failed short session connection to gateway (3)"
1. This happens when the certificate bound to HTTPS on the core becomes corrupt, missing, or expired.
2. This error can also happen when using the remote control viewer to remote control devices without a core server to authenticate to.
On your core, open the IIS manager.
On the left, find the "Default Web Site" entity.
Right click it and choose "Edit Bindings" from the list.
In the new window, edit the 443 binding. Change the certificate to one that looks like: "LANDesk Secure Token Server"
Reset IIS
If the certificate is already set to the "LANDesk Secure Token Server". This means that you have a bad certificate:
Open your client connectivity settings and look under "Core information". Note which certificates are being used.
If there are many certificates in here, you may need to verify the core name on the certificate and .0 files by opening them in notepad. Check the .crt and .cer expiration dates by double clicking them.
Navigate to \Program Files\LANDesk\Shared Files\Keys and compare to "Core certificates the client will trust". Move the certificates and .0 files that are not in client connectivity (With the exception of LANDesk_CommandsWS) to a new folder. NOTE: File path may vary
Navigate to \Program Files\LANDesk\ManagementSuite\ldlogon and move the .0 files that are not in client connectivity to a new folder. NOTE: File path may vary
Navigate to \Program Files (x86)\LANDesk\Shared Files\cbaroot\certs and move the .0 files that are not in client connectivity to a new folder. NOTE: File path may vary
Add the LANDesk core server name to "Type the authentication core server name:" in the remote control viewer before attempting to remote control.
Make sure that when you ping the CSA name from the core, it is trying to resolve to the internal IP address of the CSA.
When .NET Framework 4.0 is installed it is not "Enabled" by default in IIS 7, you have to "allow" it in IIS 7 manager. Open up ISAP and CGI restrictions under your server name and enable both entries for .NET Framework 4.0. Make sure that you also update the application pools to .net v4.
Unable to talk to core, authentication fails.
Note: If you are unable to install the telnet client in order to test connectivity, this can be done with powershell and is very easy to run when you use the batch file from the EndPoint Manager (EPM) Tool . The EPM Tool can also ,make it really easy and quick to recreate the COM+ objects.
Hello everybody,
I'm requesting your help today because every time I want to start a Remote Control session via the CSA, IEM asks me the CSA username and password
Can you please tell me how can I configure IEM to don't ask for this password ?
Thank you in advance,
Regards
After upgrading the core server from a previous version to 2017.3 the Remote Control might fail with "the signed rights document was not valid. authentication failed." for LANDesk Users, which are not LANDesk Administrators.
This is happening as 2017.3 uses different access for the folder C:\Program Files\LANDesk\Shared Files\keys on the core.
Adding the local group LANDesk Management Suite with Read & Execute, List Folder Contents and Read rights usually fixes this issue.
Does LANDesk Management Server v2016 offer an out-of-band management process besides the use of vPro? If not, is there a reliable 3rd party that can? After 5yrs, I'm purchasing new machines and I'd like to know what is needed on the desktop system board, if anything...Thanks.
Problem:
Right-clicking machine and selecting HTML remote control through LDMS doesn't do anything. No errors, no pop-ups or any other indicators.
How to Fix:
3. Download another browser for testing with (Firefox or Chrome). Make sure to set the new browser as the default browser. After browser completes install, try selecting HTML Remote Control through LDMS again. This should pull up the HTML Remote Control in the new browser.
LANDesk Management Console 9.6 SP3 running on Windows Server 2008R2.
We consistently have to fallback to other remote control methods to help users remotely on our team. There seems to be no rhyme or reason this occurs. The response time from a click can take up to 30seconds, I've seen it!
We have ran the remote control from various machines around the network, even from the main landesk server and the problem still exists.
This happens on hundreds of newly installed Windows 10 Enterprise 64bit machines. This can happen on machines that are on the same subnet as the current remote management console as well. We have removed the posibility that this is network related. The computers in question are all gigabit connected, SSD/i7 desktops that perform excellently locally.
One noticable nuance is that this problem often occurs on computers that have graphics cards installed. Nvidia or AMD seems to make no difference.
Has anyone else noticed these issues?
Many organizations use the web console exclusively to provide an easy way to get to remote control for their technicians. If that is the sole purpose of using the web console you can simply install the remote control viewer as a standalone application. You can accomplish this by following these steps.
1 - Locate the file ENURCSetup.exe on the core server. By default it is under C:\inetpub\wwwroot\common.
2 - Install the package manually on one machine. Note: It says it is an installer for Mozilla Firefox users, but it will work just fine with IE or as a standalone viewer
3 - Find the file isscntr.exe (usually located under Program Files or Program Files (x86)\LANDesk\ManagementSuite
4 - Create a shortcut for isscntr.exe and modify it to have the following command line options: -sServerName -c"remote control" where ServerName is the name of the core server.
5 - Name the shortcut something like "Remote Control Viewer" or "LANDesk Remote Control"
6 - Put the shortcut you created and ENURCSetup.exe in the same folder to be used for a software distribution package
7 - Create a new batch file in the same folder and add the following lines:
ENURCSetup.exe -v"-q"
copy /y NameOfShortcut.lnk "C:\Documents and Settings\All Users\Start Menu\Programs\LANDesk\NameOfShortcut.lnk"
Note: modify both the name of the shortcut and the location you would like to copy it to. The example above assumes the shortcut is called NameOfShortcut and it will be copied to LANDesk folder under the All Programs listing for all users.
8 - Deploy the package to the technicians' machines.
The technician can now use the shortcut that was created for standard remote control tasks.
The technician will need to specify the machine name or the IP Address of the machine they are attempting to connect to.
Information about the command line options that are available:
-s indicates the server to use for authentication. This is required for Integrated or Certificate Based security only.
-c indicates what you would like to do upon connection. Valid options include -c"chat" -c"remote control" -c"file transfer" and -c"reboot"
Note: You can specify more than one option with -c. For example, you can use -c"chat" and -c"remote control" to open both the remote control viewer and the chat window automatically upon connection.
-a specifies a target. This can be used in two scenarios. One is if you remote control the same device very often and would like a shortcut to connect exclusively to that machine. The second is to create a shortcut for Gateway remote control. -agsb://GatewayNameOrIp specifies that you would like to connect to the Gateway for a remote control session.
Hello,
We are on Landesk Managment Suite 2016 v. 10.1.0.168.
I am trying to remote into systems that are set to auto-login, so there is no users present to give permission. I have attempted to hack the registry but the following key doesn't seem to exist.
HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\WUSER32\Permission Required
The path in the registry goes as far as "Landesk". Do I need to add "WUser32" then the Key or did this get moved to another location in this version of Landesk? Or is there a different way to accomplish this task?
Thanks,
Matt