Mobile Control Center (MCC) server
MCC licenses for managed devices
Psion Windows CE 5.0 mobile terminals
Occasionally remote support staff will want to collect network debug from the terminal. While MCC is an excellent tool for remote control, remote control sessions tend to use considerable bandwidth and may flood the log file with MCC traffic instead of helping identify the cause of the network problem.
When troubleshooting Windows CE 5.0 devices, MCC can be used to begin a network capture remotely without generating a flood of network traffic. The following document will instruct how to send a script command to the remote terminal that will start and stop the network capture.
Select the device in your device tree from which you would like to capture the network log file. Right click the device and choose Send -> Script.
The script interface contains pre-defined scripts that ship with MCC as well as any scripts that have been manually created by MCC administrators. Scripts can be sent to terminals using MCC IP connections or SMS (SMS scripts can only be received by Windows Mobile devices and therefore does not apply to this document).
Click the ‘Scripts’ button to open the Manage Scripts interface
Existing scripts can be edited or deleted from this interface.
The software will automatically fill in your username and today’s date.
Add to the script file the command that activates the network capture: netlogctl start
This script will end the network capture with the command: netlogctl stop
The script will automatically erase any existing network captures in the device TEMP folder and move the newly created captures into the TEMP folder. ***Because netlog files are automatically erased, it is important to run this script only ONCE (an alternative script might use COPY instead of MOVE)
NOTE: It is important that the netlog process be stopped before an attempt is made to move or retrieve the file from the terminal. Copying a file from the device before the netlog software is ended will result in a file that cannot be read by the debug software.
There is more information available on the netlogctl command and its command line switches. For more information, please refer to the following community portal posting and its linked MSDN document.
Once the scripts are created, MCC managers may have access to send the scripts to any device in the device tree.
Using the scripts described in this document, network capture files will be moved to the TEMP folder of the Windows CE device file system. Logs are saved as ‘netlog0.cap’ and then ‘netlog1.cap’. If ‘netlog1.cap’ becomes full, the software will begin overwriting ‘netlog0.cap’
The files are moved to the TEMP folder so that they can be easily retrieved from the Windows CE terminal using the FTP protocol. In the MCC manger, take note of the IP address of the terminal.
In your web browser, use the FTP protocol identifier and the terminal IP address to access the TEMP folder on the device directly. In the example shown here, the URL is ftp://10.65.3.76/
The .CAP file extension may already be registered to an application on your PC. To safely save the file, right click the link and choose “Save target as…” then choose the location on your PC where you would like to save the file.
Some network administrators do not allow the FTP protocol to be used on the network for security reasons. If FTP does not work, MCC remote control can be used to access the terminal and copy the file within the remote control session.