If you are running in a networked environment where a firewall separates LISA Workstation from your VSE server, you will notice a problem with using the VSE dashboard to deploy a service image to the VSE server.
Because of the size of service images, it is not practical to use RMI (LISA's standard mode of communication between components) to deploy a service image to a VSE server. Because of this, service image deployment through the VSE dashboard uses a different scheme. The scheme employs functions very much like using an FTP server in passive mode. The dashboard makes an RMI call to the server to start a transfer operation and the server returns the network endpoint (address and port) that the workstation should connect to to transfer the service image. As with FTP, the VSE server picks an available port to listen on for the transfer.
The problem with this is that the port selected by the VSE is not predictable (being assigned by the native operating system) which means that if a firewall separates LISA Workstation from the VSE server, there is no way to know what ports should be opened.
This same issue is true of the VSEManager command line tool because it uses the same mechanism as the VSE dashboard to transfer a service image to a VSE server.
Because LISA Workstation and the VSE server share database connectivity information (as provided by the registry), this shortfall is easy to overcome by using the View | Virtual Service Images application menu item to show the Virtual Service Images dialog. Because the workstation talks to the same database as the VSE server, using the Import function on this dialog has the same effect as the deploy service image function on the VSE dashboard.
If your environment is configured so that LISA Workstation and the VSE server point to different VSE database instances, you must either (temporarily) reconfigure LISA Workstation to point to the same VSE database instance as the server to do the import or transfer the exported service image file to the VSE server by some other means and then from that machine use the ServiceImageManager tool to perform the import locally.