Quantcast
Channel: Ivanti User Community : Popular Discussions - Remote Control
Viewing all 11070 articles
Browse latest View live
↧

Issue: LANDESK Remote Control mirror driver incompatible with Windows 10 Update Anniversary Edition update

August 4, 2016, 11:03 am
$
0
0

Issue

 

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".

Workaround

 

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.

↧
Search

remove controle unable to connect

October 25, 2016, 6:26 am
$
0
0

Hello

 

I am running LDMS 2015 SU-5 now. I can connect to remote machine when lauching from Landesk Management console.

 

But If I try running it from Remote console application as strandalone, I cannot and get error Unable to send a request to the remote computer.

 

Any information why ?


Thank you and regards

Philippe RITTER

↧
↧

ALT TAB Missing When Remotely Connected

December 15, 2017, 11:02 am
$
0
0

We are building a new image staging system.

 

The OS is Windows 10. We are using LANDESK Management Suite 2016 10.1.0.168.

 

When we first stage our systems and install Win10, everything is working as expected.

I am able to remote into a system and issue an ALT-TAB command and I see the standard Win10 ALT-TAB box appear showing all running applications and allows me to stop on one to switch too.

 

During the staging process, we replace the windows shell with an in house shell application (our systems are highly locked down and the users only have access to a handful of applications we present them).

 

Once we have replaced the Windows shell, when we remote into a system and issue ALT-TAB the system will immediately switch to the next application without presenting the popup showing all running applications.

 

If I hit ALT-TAB locally on the Win10 system, I get a popup showing all running applications that is similar to the way Windows 7 displayed the ALT-TAB window.

 

We staged our previous Windows 7 images the same way, using the same shell replacement application and do not have this issue.

 

This will present problems to our support staff of knowing what windows are open, how to get to the appropriate window, and making sure not to accidentally leave something running that shouldn't be visible to users.

 

We have tried this with the standard remote view client and with the HTML5 client.

 

Upgrading LANDESK is not an option, we still support legacy systems running WinXP and this is the newest version we could find that also supports XP systems. Part of this new Win10 image is to replace those systems, but we need to support both until that conversion is complete.

 

Any ideas?

↧

Remote desktop in LANDESK

September 24, 2012, 11:49 pm
$
0
0

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.

↧

Remote control to PE gone in 2016?

December 22, 2016, 2:13 pm
$
0
0

We used to be able to connect to computers in PE. This was especially helpful when a vbooted template died and we needed to start another one remotely. Has this ability been removed or am I missing something?

↧
↧

Remote Control Console for Mozilla Prompt - Odd Behaviour

May 5, 2009, 11:25 am
$
0
0

I have a user that gets prompted with "LANDesk Remote Control Console for Mozilla" and is looking for the LANDesk Remote Control Console for Mozilla.msi whenever he right clicks to do a copy paste (strange behaviour).  Anyone seen this before?  Suggestions?  Where can I get a copy of the msi?  Maybe I could load it on his PC locally and have him select it when he is prompted.

 

Thx

↧

Unable to use RCViewer (isscntr.exe) - The logged in user does not have rights to access the remote computer...

February 5, 2009, 11:58 pm
$
0
0

Hi to All,

I have tried to read most of the available solutions but to no avail.

I am able to do remote control via Remote Web Console, but I am unable to use RCViewer("isscntr.exe") to perform the same function.

Location: C:\Program Files\LANDesk\ServerManager\RCViewer

Does anyone encountered the same problem as me?

Filename: isscntr.exe

Version: 8.80.0.249

Would appreciate any help available.

Thanks so much!

 

RC Error.JPG

↧

LANDesk Remote Control Viewer Crash after remote user accept the connection

September 6, 2017, 7:11 am
$
0
0

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

↧
Search

Bad Remote Control - Even issuser.exe 8.8.2.3 upgraded on 8.8.2.5

February 17, 2009, 9:20 am
$
0
0

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

↧
↧

Remote Control session without Management Console

March 10, 2010, 1:31 am
$
0
0

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  

↧

Remote Control not working

August 6, 2013, 2:19 am
$
0
0

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

↧

Disabling or Removing the LANDesk Remote Control Mirror Driver

October 1, 2008, 7:44 am
$
0
0

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!

↧

Black screen

January 10, 2012, 11:57 am
$
0
0

Some of my servers do not display for remote control.  I have three identical servers.  One works correctly.  Two display only a black screen when using remote control.  Web console does not work.  Mirror driver and screen blanking is off.  Any ideas?

↧
↧

Keyboard and Mouse greyed out

November 16, 2010, 10:31 am
$
0
0

When I remote one of my clients in this case (Windows 7 Pro 64bit Laptop), I am unable to use the mouse or keyboard remotely but can see the desktop of the client.  Keyboard and mouse is greyed out.  I have remoted another client with same OS and works fine.  Have removed and added agent on machine and disabled firewall.  Still not luck.  Any ideas?

↧

Issue: LANDESK Remote Control mirror driver incompatible with Windows 10 Update Anniversary Edition update

August 4, 2016, 11:03 am
$
0
0

Issue

 

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".

Workaround

 

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.

↧
Search

LANDesk Remote Control Viewer Crash after remote user accept the connection

September 6, 2017, 7:11 am
$
0
0

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

↧

"Authentication Failed Because The Signed Rights Document Has Expired"

October 31, 2008, 2:49 am
$
0
0

 

Any ideas?  I have reinstalled the client a number of times with the exact same error message when I attempt a remote control connection.

 

What does this error message mean?

↧
↧

Remote Control on Lock Workstation doesn't work (anymore)

April 7, 2015, 5:45 am
$
0
0

Hello everybody,

 

Since a year we have a strange behavoiur about our RC.Remote Control on the status of Workstation Locked or waiting for Login (Ctrl+alt+del) doesn't work. In the past we could and we know how important is in some situation. The settings are fine (we haven't changed). I tried set for modem connection, switch off the "keyboard setting", I think I changed everything. The system hangs at "Initializing keyboard filter". I attached a log for example. This happens both RC with the program and HTML. Thank you in advance.

↧

Upgraded to 9.5 from 9.0 SP3 - Remote Control - The signed rights document was not valid. Authentication failed.

November 20, 2012, 2:08 pm
$
0
0

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.

LDMS-9.5Upgrade-RemoteControlFailed.JPG

 

Any ideas?  We are not using AppBlocking.  I read about the whitelist issues, but I don't think that apply's to us.

↧

Is remote control not supported for Windows 10 client on the LDMS 2016 server? It is greyed out.

August 25, 2017, 12:44 pm
$
0
0

I just added a new Windows 10 client to my LDMS 2016 server.  All my other clients are Windows 7 and I have no problems with Windows 7 but this is the first client with Windows 10.  The agent installed with no errors.  I see it on the LDMS 2016 console but I can't seem to remote control it.  It is greyed out.  I also did a software/hardware scan on the client and it says it can communicate with the LDMS 2016 server but it doesn't update it on the LDMS 2016 server.  What am I missing?

↧
Viewing all 11070 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>