Cisco Systems CVXC6215SK9 Manual De Usuario

AutoConnect=yes \
Colors=16m \
Username=Administrator \
Password=Password \
Domainname=$DN \
Resolution=800x600 \
Reconnect=no \
Drives=J=disk \
Drives=k=floppy \
Sound=off \
LocalCopy=Yes

In the above example, replace x.x.x.x with the IP address of your RDP server.

To push a wlx.ini file to your clients, you must first create a Cisco VXC Manager package, which you 
can then schedule for distribution to your devices. 

Do not modify INI files directly on the Cisco VXC 6215 as doing so can cause configuration issues and 
operational errors. Only use Cisco VXC Manager to push the INI files to the clients. 

With Cisco VXC Manager, you must create and register specific packages to push upgrades and 
configurations to your clients.    

Cisco VXC Manager packages are structured relative to the location of an RSP file. To register the 
package with Cisco VXC Manager, the package must contain a unique RSP file and, at the same folder 
level, a folder with the same name as the RSP filename. This folder serves as the root folder for the 
remaining configuration files in the package.   

For example, assuming <packagename>.rsp is the RSP file, the folder structure required to register the 
package is as follows:

~/<packagename>.rsp
~/<packagename>/wlx
~/<packagename>/wlx/bitmap
~/<packagename>/wlx/certs
~/<packagename>/addons

You can create this structure in any location on your Cisco VXC Manager server, as long as the 
placement of the folders relative to the RSP file remains the same. 

If a folder does not contain a required file for the package, the folder can be omitted from the package 
directory structure. For example, if the package contains no graphics, the /wlx/bitmap folder is not 
required. 

After you register the package, Cisco VXC Manager stores the package files in the software repository 
under c:\inetpub\ftproot\Rapport\<packagename>.