------------------------------------------------------------------------ MasterScope WinShare Ver7.0 Copyright (C) NEC Corporation 1996-2018. All rights reserved. Apr 9, 2018 ------------------------------------------------------------------------ Contents -------- 1. Introduction 2. Functional enhancements in version 7.0 3. Operating environment 4. Cautions and limitations 5. License 6. Trademarks 1. Introduction --------------- WinShare makes it possible to remotely operate a "Remote PC" connected to a network from a local PC (referred to as an "Operation PC"). Operation PC and Remote PC users can share the screen during remote operation because it is displayed on both the Operation PC and Remote PC. In addition, operations on the target screen can be permitted for both or either of the Operation PC and Remote PC users. WinShare can be used in a wide range of applications; for example, for remote maintenance of Remote PCs and remote support for users such as training and help desk services. 2. Functional enhancements in version 7.0 ----------------------------------------- (1) Remote connection via a relay server By installing a relay server that both an Operation PC and Remote PCs can access, it is now possible to easily establish remote connection to a Remote PC that is installed inside a firewall and difficult to connect from outside the firewall. (2) Improved operability of the Remote PC management The Remote PC Management dialog box has been improved so that a group and Remote PC can be moved to another registration folder in a tree view by dragging and dropping. (3) Specification of a port to be used for remote connection A port to be used for remote connection can now be specified explicitly by specifying a colon (:) and port number following a Remote PC name. (4) Revised log output contents on an Operation PC The contents of the connection history and power control/status confirmation history that are output on an Operation PC have been revised. The GUIs to display histories have also been revised. (5) Support of the console connection The console can now be connected to Windows and Linux machines. (6) Specification of an allowed remote connection period It is now possible to specify a period during which an Operation PC can connect to a Remote PC. (7) Improved recording performance Users can now specify a codec to be used to record the contents of remote operation. (8) Support of construction automation (Ansible) NEC started providing Ansible. It is now possible to automate construction by using a playbook. 3. Operating environment ------------------------ The hardware and software requirements for operating WinShare are as below. - Compatible hardware Mate series, VersaPro series, Express5800 series (excluding MIPS models) and PC/AT Compatibles - OS - WinShare Operation - Windows Server Windows Server 2016 Standard / Datacenter *1 Windows Server 2012 R2 Standard / Datacenter *1 Windows Server 2012 Standard / Datacenter *1 Windows Server 2008 R2 Standard / Enterprise *1 Windows Server 2008 Standard (x86,x64) / Enterprise (x86,x64) *1 Windows Server 2003 R2 Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 Windows Server 2003 Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 - Windows Windows 10 Pro (x86,x64) *3 Windows 8.1 Pro (x86,x64) Windows 8 Pro (x86,x64) Windows 7 Professional (x86,x64) Windows Vista Business (x86) Windows XP Professional (x86) *4 - WinShare Remote - Windows Server Windows Server 2016 Standard / Datacenter *1 Windows Server 2012 R2 Standard / Datacenter *1 Windows Server 2012 Standard / Datacenter *1 Windows Server 2008 R2 Standard / Enterprise *1 Windows Server 2008 Standard (x86,x64) / Enterprise (x86,x64) *1 Windows Server 2003 R2 Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 Windows Server 2003 Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 - Windows Windows 10 Pro (x86,x64) *3 Windows 8.1 Pro (x86,x64) Windows 8 Pro (x86,x64) Windows 7 Professional (x86,x64) Windows Vista Business (x86) Windows XP Professional (x86) *4 - Windows Embedded Server Windows Server 2016 for Embedded Systems Standard / Datacenter *1 Windows Server 2012 R2 for Embedded Systems Standard / Datacenter *1 Windows Server 2012 for Embedded Systems Standard / Datacenter *1 Windows Server 2008 R2 for Embedded Systems Standard / Enterprise *1 Windows Server 2008 for Embedded Systems Standard (x86,x64) / Enterprise (x86,x64) *1 Windows Server 2003 R2 for Embedded Systems Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 Windows Server 2003 for Embedded Systems Standard Edition (x86,x64) / Enterprise Edition (x86,x64) *2 - Windows Embedded Enterprise Windows 10 IoT Enterprise (x86,x64) *3 Windows Embedded 8.1 Pro (x86,x64) Windows Embedded 8 Pro (x86,x64) Windows 7 Professional for Embedded Systems (x86,x64) Windows Vista Business for Embedded Systems (x86) Windows XP Professional for Embedded Systems (x86) *4 - Windows Embedded Industry / Windows Embedded POSReady (WEPOS) Windows 8.1 Industry Pro (x86) Windows Embedded POSReady 2009 Windows Embedded for Point of Service 1.1 - WinShare Relay - Windows Server Windows Server 2016 Standard / Datacenter *1 Windows Server 2012 R2 Standard / Datacenter *1 Windows Server 2012 Standard / Datacenter *1 *1: The Server Core installation environment is not supported. *2: Windows Server 2003 R2 SP2 or later and Windows Server 2003 SP2 or later are supported. *3: Windows 10 Version 1709 (Fall Creators Update) or earlier is supported. *4: Windows XP SP3 or later is supported. - Memory 256MB or more - Disk Free space of 100MB or more - Display resolution (WinShare Operation and WinShare Remote) VGA (640 x 480) to 4K (3840 x 2160) - Display color depth (WinShare Operation and WinShare Remote) 256 colors, High Color (65,536 colors), True Color (approximately 16,770,000 colors) - Console connection (WinShare Operation only) Windows: Windows PowerShell 2.0 or later Windows Remote Management (WinRM) 2.0 or later Linux: Tera Term 4.92 or later - Power control (WinShare Remote only) Wake on LAN, Intel AMT 6.0 or later 4. Cautions and limitations --------------------------- 4.1. Cautions ------------- (1) If both the Operation PC and Remote PC are running version 6.1 or later, all communications are encrypted with AES256. You can allow connections from an Operation PC of version 6.0 or earlier by making the appropriate settings on the Remote PC, but in this case, communications with an Operation PC running version 6.0 or earlier are encrypted with AES256. If you want to enable connections, clear [Deny connections from Operation PCs of version 6.0 or earlier] on the [Connections] tab of the WinShare Utility. For New installation, this item is not selected by default (connections are allowed). (2) If you select [Deny connections from Operation PCs that are not registered as an permitted host] on the [Connections] tab of the WinShare Utility, you must register at least one Operation PC from which connections are to be allowed by clicking the [Permitted Hosts] button. Otherwise, connections cannot be made from any of the Operation PCs. (3) A user with [Confirmation of connection to Remote PC user] on the [Advanced User Settings] dialog box of the WinShare Utility set to [Connect after confirmation] connect to the Remote PC by the WSFT (file transfer function), the [connection confirmation] dialog box is always displayed in the console session. (4) If you want to connect to a remote session of a Remote PC, the display resolution and color depth of the remote session must satisfy the operating requirements of WinShare. (5) In WinShare version 6.2, the type and format of the logs output by a Remote PC are changed. Therefore, if you upgrade a Remote PC from an old version to version 6.2 or later, the log setting information that is set in the old version are not inherited. To output logs from the Remote PC, make the settings again on the [Logs] tab of the WinShare Utility. (6) If the Remote PC is using multiple displays, the identification number of the display displayed on the Remote PC's control panel may not match the display number displayed in the status bar of the WinShare Client during remote operation. (7) When you connect to the console session of the Remote PC and log on to the operating system with WinShare remote operation, reconnection may occur. At this time, the video-recording file that was recorded just before reconnection may not be created correctly. (8) The following cautions apply to Remote PCs on which Windows 10 or Windows Server 2016 is installed. - In Windows 10 is Version 1607 (Anniversary Update) or earlier, Japanese cannot be entered by entering NAVIPAD characters. To input Japanese using NAVIPAD character input, you need to apply "2017-05 Cumulative Update for Windows 10 Version 1607 (KB4019472)" after applying Anniversary Update (Version 1607). - In Windows Server 2016, Japanese cannot be entered by entering NAVIPAD characters. To input Japanese using NAVIPAD character input, you need to apply "2017-05 Cumulative Update for Windows Server 2016 (KB4019472)". (9) Remote operation via the Relay Server is available only when the versions of both the Operation PC and Remote PC are version 7.0 or later. (10)To end a Windows console connection, enter EXIT on the Windows PowerShell window. If you end the connection by clicking the close "x" button of the window, the unnecessary cmd.exe process remains. (Even if the unnecessary process remains, you can continue to use the console connection. The unnecessary process can be removed by signing out or stopping the machine.) (11)If WinShare Operation or WinShare Remote is first uninstalled in an environment where WinShare Relay coexists with WinShare Operation or WinShare Remote, the WinShare Relay stopped. Also, WinShare Relay cannot be uninstalled. Uninstall the WinShare Relay first if uninstalling WinShare Operation or WinShare Remote in an environment where WinShare Relay and WinShare Operation or WinShare Remote coexist, regardless of whether or not the WinShare Relay is continuously used. To continue using the WinShare Relay, reinstall it after uninstalling WinShare Operation or WinShare Remote. 4.2. Limitations ---------------- (1) WinShare Operation and WinShare Remote can be installed on the same PC. To do so, they must be of the same version. (2) If you switch between users with the fast user switching function, the operation window of the Operation PC that is connected to the Remote PC turns black before the switching. In this case, you can display and operate the window to which you have switched by re-establishing the connection. You cannot, however, display or operate the window if the active user session ID is 16 or above. (3) On the Logon window, Security window, and Welcome window, you cannot change the operation mode to [deterrent mode]. (4) When you connect to the Windows Logon window, log on with WinShare remote operation, and switch to the desktop window of a logon user, you may not be able to perform remote operation. In this case, remote operation can be enabled by re-establishing the connection. (5) During auto zoom or due to the user-specified value of image size, white lines may be displayed on the operation window of the Operation PC. These white lines do not affect the remote operation itself. If they prove troublesome, select a fixed magnification (100%, 75%, or 50%) for the image size on [Action Setting] of WinShare Client. (6) When you connect to a logon/unlock Remote PC, password entry may fail if the CAPS/kana setting of the Remote PC is changed before you actually enter a password. In this case, re-establish the connection. (7) With the file transfer function, you cannot send or receive files to or from a network drive. (8) If the Remote PC has a high DPI setting, the frame (rubber band) displayed when you drag the Remote PC-side window may not be drawn properly on the Operation PC-side operation window. (9) If the Remote PC uses a touch panel environment, touch operations such as tapping and swiping are not suppressed even if you change the operation mode to [deterrent mode]. (10)The following limitations apply to Windows Vista or Windows Server 2008 or later. - If the data handled by WinShare, such as the character strings displayed on the GUI of WinShare (for example, the registration names of Remote PCs) and the data used with the clipboard transfer function, includes characters inherent to JIS2004, problems such as garbled characters occur. You can avoid these problems by taking either of the following actions under Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2. 1. Limit the IME input range to JIS90 Select IME Properties > Conversion tab > Conversion Character Limitations, and check Display only words/characters made up of JIS X 0208 characters as conversion candidates. 2. Install the JIS90-compatible font supplied by Microsoft From the Microsoft download center, search for "KB927490" and install the font as described on the webpage. (11)The following limitations apply to Remote PCs on which Windows 10 or Windows Server 2016 or later is installed. - If, during remote operation, you access the "Start Menu", "Microsoft Edge", or "Windows Store App (UWP App)", screen updating may be delayed on the Operation PC. In this case, you can reduce the delay by setting the screen updating interval to 0.5 seconds or less under Action Setting of WinShare Client. Note that the CPU usage may be increased by reducing the screen updating interval. Adjust the interval according to your environment. - You cannot perform remote operation from an Operation PC with a touch panel. (12)Up to 10 Remote PCs can be registered in one Relay Server. Up to two Operation PCs can be connected to one Remote PC via the Relay Server. (13)If you install Tera Term in a folder different from the default path ("%PROGRAMFILES%\teraterm" or "%PROGRAMFILES(x86)%\teraterm") for a Linux console connection, specify the installation folder path for the following registry. 32-bit system: HKEY_LOCAL_MACHINE\SOFTWARE\NEC WinShareVer2\Client 64-bit system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\WinShareVer2\Client Key name: tt_home Type: REG_SZ Data: Tera Term installation folder path 5. License ---------- This software product is developed by NEC Corporation. When using this software, you are requested to comply with the "License Agreement" supplied this product. The password encryption for this product uses the MD5 message-digest algorithm of RSA Data Security, Inc. Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software. This product includes parts of FreeBSD, developed by the University of California and the Contributor under the following conditions for use. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The Regents of the University of California. Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors. 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The Institute of Electrical and Electronics Engineers and the American National Standards Committee X3, on Information Processing Systems have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the second BSD Networking Software Release, from IEEE Std 1003.1-1988, IEEE Standard Portable Operating System Interface for Computer Environments (POSIX), copyright C 1988 by the Institute of Electrical and Electronics Engineers, Inc. In the event of any discrepancy between these versions and the original IEEE Standard, the original IEEE Standard is the referee document. In the following statement, the phrase "this material" refers to portions of the system documentation. This material is reproduced with permission from American National Standards Committee X3, on Information Processing Systems. Computer and Business Equipment Manufacturers Association (CBEMA), 311 First St., NW, Suite 500, Washington, DC 20001-2178. The developmental work of Programming Language C was completed by the X3J11 Technical Committee. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the Regents of the University of California. 6. Trademarks ------------- Microsoft, Windows, Windows Server and Windows Vista are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The official name of Windows is Microsoft Windows Operating System. Intel and vPro are registered trademarks or trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries. MasterScope and WinShare are registered trademarks or trademarks of NEC Corporation in Japan.