ViewSonic SC-T25 User Manual page 29

At the moment we have four options but may add others in the future. The Option
Flags must all be configured as "Text" not "Integer"
Option 231 point to the VDM3.0 location
Option 232 sets the VDM3.0 Port number
Option 233 sets the IP, Name or URL of the Server to connect to
Option 234 sets the Protocol, in this case Web or HDX
The Linux version of VDM3.0 is built into every version of VTOS, if you wish to use a
SC-T25 as a VDM3.0 console you can do that by switching the Protocol to VDM3.0.
When using the Linux version of VDM3.0 built into VTOS always accept the default
installation location when switching to VDM3.0 mode as this location is writable.
The ViewSonic Device Management 3.0 Software (VDM3.0)
does not discover my VTOS Device, how can I fix this
problem?
On first boot up VTOS Devices use DHCP to obtain an IP Address, DNS information
and also NTP to obtain the correct time and date. You can open an xterm on the
VTOS Device using Ctrl-Alt-t, enter /sbin/ifconfig to view the IP Address, try pinging a
domain name, check that the date is correct by entering "date"
The golden rule when using the default UDP discovery mode is to never run more
than one instance of VDM3.0 at once. When you launch VDM3.0 it sends UDP
discovery packets with the IP ADDRESS and Port number of the system running
VDM3.0, the VTOS clients connect to that System.
If you launch another instance of VDM3.0 on a different system it will not see the
clients as they have already connected to the other system. Close all the instances
of VDM3.0 that are running and then just run the one instance
The SC-T25 does not have a Real Time Clock, ensure your DNS is set up correctly
as the SC-T25 needs to resolve names to contact the Time Server. After the clients
are discovered you can use VDM3.0 to set the IP ADDRESS and Port number of the
system running VDM3.0, you would use this mode to manage your clients anywhere
in the world from one central location.
Use VDM3.0 / Tools / Configuration / VDM3.0 Server configuration, the default UDP
discovery only works on the same Subnet as the clients.
Just switch the protocol to VDM3.0. On some versions of Windows some dll files
required by VDM3.0 are missing VDMserver.exe uses the DLL msvcr100.dll and
srvcli.dll which are both in the folder "C:\Windows\SysWOW64\" These DLLs are
most likely missing if you don't have "Microsoft Visual C++ 2010 SP1 Redistributable
Package (x86)" installed. Downloaded it from here
https://www.microsoft.com/en-us/download/details.aspx?id=8328
VDM is also built into VTOS, you can even use a SC-T25 in VDM mode if you wish
to by switching the protocol to VDM
22