﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>The VNC Manager - SmartCode Solutions Forum / General Discussion / SmartCode ViewerX VNC Viewer ActiveX  / Getting started / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>The VNC Manager - SmartCode Solutions Forum</description><link>http://vncmanager.com/forum/</link><webMaster>forums@s-code.com</webMaster><lastBuildDate>Sat, 04 Jul 2009 14:01:25 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Getting started</title><link>http://vncmanager.com/forum/Topic645-6-1.aspx</link><description>In order to access customers you need them to have a VNC server installed. ViewerX is a client component that connects to a VNC server. So it's probably not exactly what you are looking for. &lt;/P&gt;&lt;P&gt;We are working on a version of VNC server implemented as ActiveX component. This is exactly what you need. You could host such VNC server ActiveX on a web page, then a customer visits the page, the ActiveX gets downloaded and installed to his PC and establishes a reverse connection to one of your engineers listening VNC viewers. After connection is established, the engineer will be able to work with the customer’s remote desktop.&lt;/P&gt;&lt;P&gt;Should you have any questions you can contact me at &lt;A href="mailto:yury@s-code.com"&gt;yury@s-code.com&lt;/A&gt;</description><pubDate>Tue, 13 Dec 2005 22:30:14 GMT</pubDate><dc:creator>Support (s-code)</dc:creator></item><item><title>Getting started</title><link>http://vncmanager.com/forum/Topic645-6-1.aspx</link><description>We're WebEx customers today. Customers call us and we initiate a WebEx session. WebEx is much more than we need. &lt;br&gt;&lt;br&gt;We're newbies to the VNC world, so we're not quite sure what we're facing and if your product is right for us.&lt;br&gt;&lt;br&gt;We want to do a [u]silent [/u]install on the customer's machines so our help desk can access it.  We've already determined that runtime args /V/qb!/S to your msi exe seem to work fine for that.&lt;br&gt;&lt;br&gt;But, then what?  Once your component is installed on the customer's machine, our Delphi app can call it. But, can you give us an overview of what would happen?  We assume that our support engineers run VNC Manager (or any VNC client?). Your activeX component makes the [u]user's[/u] machine a server, right??   &lt;br&gt;&lt;br&gt;Is your ActiveX component a [i]visual [/i]component?  Can our application on the customer's machine call it silently, providing password and client IP and whatever other connection parameters are required?&lt;br&gt;&lt;br&gt;What's the safest configuration to avoid firewall, proxy, admin rights, etc problems? Can this be configured via calls to your component?  &lt;br&gt;&lt;br&gt;Thanks for your help and any pointers to additional information on the web or your site.&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</description><pubDate>Tue, 13 Dec 2005 21:19:15 GMT</pubDate><dc:creator>tfield98</dc:creator></item></channel></rss>