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
Under Remote Control Settings there are 4 main options, for security purposes, I need the Client to prompt to accept the connection I have tried all the options with the following results:
Option 1: "Permission not needed, full access"
RESULT: Works fine
Option 2: "End User must grant permission and must be logged in"
RESULT ERROR: Remote User has denied permission to remote control (No prompt)
Option 3: "End User must grant permission but only if they are logged in"
RESULT ERROR: Connects but takes over the machine, only 1 user allowed (logs the normal user out)
Option 4: "End user must grant permission"
RESULT ERROR: Timed out waiting for the remote user to grant permission
Using Integrated Security.
Any suggestion is appreciated.
Is anyone using this feature, when connect to ONLY the CSA?
Is it just me or does the remote control portion of Landesk suck. i have tried different solutions that have been applied by their tech support and yet there are still many machines that i cannot remote to. Our environment consists of HP and Dell workstations (laptops and desktops) computers. I guess my issue is that when we try to support a user and it crashes their machine, we look like the idiots for using a utility that creates this type of behavior on random machines. Why the hell does this happen? i would understand if it happens, 1 in 100 machines, but the ratio is much lower than that. Furthermore, if the machine does not crash/bsod it will error out a message on the client side. At that point we need to deploy the agent back to the machine...WHYYYYYYYYYYYYYY? Sometimes this works and sometimes it doesnt.
We've tried to reconfigure the Landesk client remote options every which way you cant think of, but the issue is that sometimes it works, but most times it doesn't. We have resulted on installing UltraVNC on 70% of the client computers and maybe by the end of the '09 we'll get the rest. My plea to Landesk, is that they invest a good portion of their earnings to remote control R&D.
We were initially a Netware shop and had Landesk running on Server 2003 with no problems taking remote control of workstations. Two weeks ago we migrated to Windows networking, and now remote control no longer works. We are always asked for credentials, but entering AD credentials doesn't work. We need a full explanation of how to set up administrators to use remote control once the Landesk server and all workstations have been added to a Windows domain. The documents I have found so far don't explain the process completely and don't seem to work anyway.
Thanks for any assistance. Rob
Hello all,
I had heard that the main purpose of the mirror driver is to speed the video rendering on older computers for remote control. We are on LD 8.8 SP4 and have recently started installing the agent on Win7 machines.
The mirror driver has been killing Aero and I saw that there is a patch to resolve this issue. The vast majority of our Win7 machines are going to be newer, beefier machines. If the mirror driver doesn't do anything beyond speeding a remote session on an older machine, I'm inclined just to remove it.
Anyone have a good justification for patching it and leaving the mirror driver on the agents?
Thanks.
Anyone ever seen a problem with trying to remote control from a laptop while on battery.? This is using the LDMS remote console.
I can plug the laptop in and the remote control window comes up normally. If I unplug the laptop and click on remote control, it does nothing. No remote window even appears.
I am running Windows 7 pro x64. Both power policies for plugged in and unplugged are the same in Windows.
Hi, has anyone else seen this? When installing our LANDesk clients on x64 Windows 7, the remote control service is installing to c:\progra~\LANDesk\LDclient\issuser.exe instead of c:\progra~2\LANDesk\LDclient\issuser.exe. Is there a way to change the install path so that the service will start as it should? The other LANDesk services install to C:\Program Files(x86)\LANDesk\LDClient\ so I'm not sure why the remote control agent installs using the incorrect 8.3 path.
When attempting to upgrade a Surface Pro 4 device to Windows 10 1607 (Anniversary Update) via the Windows 10 Update Assistant, the Display prerequisite reports "Display: The display is not compatible with Windows 10".
Close Windows 10 Update Assistant. Uninstall the Landesk Remote Control Mirror Driver from Device Manager. Run Windows 10 Update Assistant, the prerequisite check will now show "Display: OK".
It is unknown whether the Remote Control Mirror driver causes any issues with the actual Windows 10 1607 update, so far indications are it only conflicts with the update process.
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
It looks like after the SP5 Update of Landesk, all new installed Computers have the problem above. (installed Computers still work fine.)
Any Idea?
Thanks in advanced.
Miriam
I would like to have a scheduled task available that would allow me to disable the permission required prompt when using remote control. I would also like to have a task enable it also. I have done this in the past but cannot remember how to accomplish this.
Hello
Is it possible to start a remote control seesion on a PC without a console installation. I copid some files like "isscntr" and other and the session started - the request come but i get no remote screen an my PC. have anybocy an idea or a solution - thanks
greeting Thomas
Morning,
can anyone tell me where i can get the viewer install from?
I've tried running the ENURCsetup.exe but its installing the Mozillia version?
thanks
Chris
We have found an issue with the installed remote control mirror driver on our systems. It interferes with our Unix thin client installations when we remote into these systems. It appears that you really have no choice when installing the client agent with Remote Control capabilities as to whether the mirror driver gets installed or not, is this correct? I've tried unchecking the settings within the agent configuration to not use the mirror driver under Remote Control | Indicators | Agent Settings and then rolling out an agent update, but this doesn't seem to change anything. The only way I've found to remove the mirror driver is either disabling it or totally removing it from Device Manager. I found another thread that stated the mirror driver used to be in Add/Remove Programs, but was removed in later versions by LANDesk. We are running v8.8 SP1. I'm primarily looking for an easy way to either disable or remove the mirror driver from all of our clients through LANDesk. Any suggestions? Thanks in advance!
Under Remote Control Settings there are 4 main options, for security purposes, I need the Client to prompt to accept the connection I have tried all the options with the following results:
Option 1: "Permission not needed, full access"
RESULT: Works fine
Option 2: "End User must grant permission and must be logged in"
RESULT ERROR: Remote User has denied permission to remote control (No prompt)
Option 3: "End User must grant permission but only if they are logged in"
RESULT ERROR: Connects but takes over the machine, only 1 user allowed (logs the normal user out)
Option 4: "End user must grant permission"
RESULT ERROR: Timed out waiting for the remote user to grant permission
Using Integrated Security.
Any suggestion is appreciated.
Is anyone using this feature, when connect to ONLY the CSA?
Hi everybody,
I'm an LANDesk Management Suite's administrator of more than 2000 Client
-We have LDMS 8.6 and all it works with this version. But no upgrade for OS deploiement, package, etc.
-We upgrade to LDMS 8.7 to update functionnality. No problem.
-We upgrade to LDMS 8.8 to integrate vbs distribution and some options.
Since this upgrade, the remote control is breakable.. We can use the remote control on aleas.. It work.. It don't work.. So this hotline can't optimize bug and question fix remote..
A solution was find by LANDesk's intervention, patch a file on the client part. (issuser.exe, initial version is 8.8.2.3 and patch it in 8.8.2.5)
That fix the most of bug on remote control, but the service don't hold.. it break really offen.. The auto-correction repair the agent and it work once again.. but not stable.. the service still break for an indeterminated time..
Do you have a solution to fix this bug ? And do you have already see this problem ?
Configuration of remote control
No security apply - Local system for remote control - So direct talk on target et source, no stream with core server.
Thanks for your help.
XeNo
Hi Community
first we had the problem that the patching of our clients did not work.
On advice of the LANDesk-Support we installed LDMS 9.5 SP1.
Now on my test clients the Remote Agent is not working.
System:
Testclient 1 running on: Windows XP Professional, 32-bit, SP3
Testclient 2 running on: Windows 8 Pro, 64-Bit
LDMS 9.5 SP1 running on: Windows Server 2008 R2 Standard, 64-bit, SP1
Symptoms:
1. Errormessage when trying to remote control one of those clients:
Unable to establish a secure session with the remote computer (-5)
2. Due the installation of the LANDesk-Agent we got the following error message on the client: "The application could not be started, because LIBEAY32MT.dll was not found. Reinstalling the application may solve the problem". I receive the same error message when i try to un- and reinstall the issuser with the following commands:
C:\Program Files\LANDesk\LDClient\issuser.exe /remove
C:\Program Files\LANDesk\LDClient\issuser.exe /resident
3. When i have a look at the agents on the client (right click client - properties - agents) the remote control agent status is not loaded. On the clients which are working the agent status is loaded.
4. The remote agent service (issuser.exe) couldn't be installed on the client.
5. In the survey of all devices in the LDMS the fault clients just got the symbol with the "field glasses". The "remote control symbol" is missing.
Troubleshooting:
1. Created a new Agent
2. Created a Advanced Agent
3. Run Uninstallwinclient.exe and reinstalled the agent after a reboot.
4. Reinstalled the old Agent which is working properly.
Does anybody have some ideas?
Thank you very much for help
Best regards
Hello,
I am facing a random issue with LANDesk Remote Control Viewer in LANDesk 2016
Here is how I am doing
I am using "C:\Program Files (x86)\LANDesk\ServerManager\RCViewer\isscntr.exe" -c"Remote Control" from the computer
The target receive a message to accept the connection and accept it
The target screen become Black
The LANDesk Remote Control Viewer become grey on my computer then crash
Sometime doing Windows + L and enter the credentials will make remote screen back to normal and sometime not.
In this case the only option left is reboot...
Here is the error in event ID
Faulting application name: isscntr.exe, version: 10.1.0.168, time stamp: 0x57e31561
Faulting module name: isstnmp.dll, version: 10.1.0.168, time stamp: 0x57e31559
Exception code: 0xc0000005
Fault offset: 0x000059f0
Faulting process id: 0x2884
Faulting application start time: 0x01d3270cf2c98c13
Faulting application path: C:\Program Files (x86)\LANDesk\ServerManager\RCViewer\isscntr.exe
Faulting module path: C:\Program Files (x86)\LANDesk\ServerManager\RCViewer\isstnmp.dll
Report Id: 6f8a5d9c-9300-11e7-9926-028037ec0200
I can try seral time to get remote control on same target from same computer, sometimes it works sometime not
I will apreciate your help
Thank you in advance
Rémy
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?
I have a lenovo t510 that is having an issue with the issuer.exe processs. Whenever it starts up for the first time it consistently gives an error of: The instruction at "0x004167ca" referenced memovery at "0x0000000c" The memory could not be "read". The computer is on SP3. I have uninstalled and re-installed the client as well. The computer's OS is Windows XP SP3. Any thoughts would be appreciated.