1.0
Table Of Contents
- Introduction and System Requirements
- Learning the Basics of VMware ACE Manager
- Installing and Configuring VMware ACE Manager
- Creating Projects
- Setting Policies and Customizing VMware ACE
- Creating Packages to Deploy to Users
- Deploying and Maintaining Packages
- Installing and Running VMware ACE
- Using Virtual Disks
- Preserving the State of a Virtual Machine
- Networking Virtual Machines
- Configuring Video and Sound
- Connecting Devices to Virtual Machines
- Using Parallel Ports
- Using Serial Ports
- Using USB Devices in a Virtual Machine
- Notes on USB Support in VMware ACE
- Enabling and Disabling the USB Controller
- Connecting USB Devices
- Using USB with a Windows Host
- Replacing USB 2.0 Drivers on a Windows 2000 Host
- Installing USB Devices as a Non-Administrator
- Who Has Control over a USB Device?
- Disconnecting USB Devices from a Virtual Machine
- Human Interface Devices
- Understanding Policies
- Glossary
- Index
- File extensions
- .lck 171
- .REDO 184
- .vmdk 169
- .vmhf 151
- .vmpl 220
- .vmprj 150
- .vmss 180
- .wav 204
- A
- Access
- Adapter
- Add
- Address
- Administrator access
- Athlon 12, 14
- Audio
- AudioPCI 204
- Authentication
- Autorun
- B
- BIOS
- Bridge 189
- Bridged networking
- BSD
- BusLogic 16
- C
- CD
- Celeron 12, 14
- Centrino 12, 14
- Checklist
- Clock
- Color
- Comm port
- Configuration
- Configure
- Connect
- Copy protection
- CPU
- Create
- Creative Labs 17, 204
- Ctrl-Alt 38
- D
- Date
- Decrease
- Defragment
- Deploy
- Devices
- DHCP
- Direct memory access
- Disable
- Disconnect
- Disk
- Disk files 169
- Disks
- Display
- Distribute
- DMA
- DNS 197
- Driver
- Drives
- Duron 12, 14
- DVD
- E
- Enable
- Encryption
- Ethernet
- Expiration
- F
- Files
- Firewall 198
- Floppy
- Forums 20
- FreeBSD
- FTP 197
- Full screen
- G
- Grab
- Graphics
- Guest operating system
- H
- Host computer
- Host operating system 260
- Host quarantine 237
- Host virtual adapter 189
- Host-only networking
- Hot fix
- Hot keys
- I
- ICMP 197
- IDE
- Image file
- Input
- Install
- interface
- Iomega
- IP address
- ISO image file 16, 175, 177
- K
- Keyboard
- Knowledge base 20
- L
- Link
- Linux
- Lock files 170
- LSI Logic 16, 58
- M
- Memory
- MIDI 204
- Mode
- Modifier keys
- Mouse
- MP3 204
- MS-DOS
- Mylex 16
- N
- Named pipe 210, 211
- NAT
- NetLogon 198
- NetWare
- Network
- adding and modifying virtual Ethernet adapters 195
- advanced quarantine 234
- advanced quarantine policies for guest 240
- bridge 189
- bridged networking 259
- changing the configuration 195
- common configurations 191
- components 189
- DHCP server 190
- host virtual adapter 189
- host-only 193, 259
- NAT 192, 196, 260
- NAT as firewall 198
- NAT device 189
- quarantine policies for host computer 237
- restricting host computer access 234
- switch 189
- Token Ring 192
- virtual DHCP server 192, 193
- virtual Ethernet adapter 190
- Virtual Network Editor 261
- virtual switch 189
- zones for advanced quarantine 235
- Network address translation
- Network quarantine 85
- New Virtual Machine Wizard 168, 260
- Newsgroups 20
- NIC
- Novell NetWare
- nq-set 146
- O
- Operating system
- Opteron 12, 14
- P
- Package
- Parallel ports
- Password
- Pentium 12, 14
- Ping 197
- Pipe
- Plug-in
- Policies
- advanced network quarantine for guest 240
- authentication 81, 222
- copy protection 84, 225
- encryption 222
- expiration 83, 224
- network quarantine 85, 230, 234
- network quarantine for host 237
- overview 220
- removable devices 85
- setting 71
- setting for a virtual machine 81
- setting for VMware ACE 74
- using scripts 244
- VMware ACE application 226
- Policy
- Power off
- Preferences
- Printer
- Priorities
- Process scheduler 39
- Processor
- Project
- Q
- Quarantine
- Quit
- R
- RAM
- Real Media 204
- Reclaim
- Redo-log file 184
- Registration 21
- Removable devices 85
- Remove
- Reset
- Restore
- Resume
- Return
- Revert
- Run
- S
- Save
- Screen
- Script
- SCSI
- Security
- Serial connection
- Serial port
- Server
- Set
- Set up
- Settings editor
- Shared folder
- Shortcut
- Shrink
- Silent
- Size
- Snapshot
- Software
- Sound
- Sound Blaster 204
- Start
- Stop
- Suspend
- Swapping
- Switch
- T
- Telnet 197
- Time
- Token Ring 192
- Tools
- Troubleshooting
- U
- UI
- Uninstall
- Unplug
- USB
- V
- Version
- Virtual disk
- Virtual machine
- Virtual machine settings editor
- Virtual Network Editor 261
- Virtual switch 189
- VMnet8 196
- VMware ACE
- VMware ACE Manager
- VMware Tools
- W
- Windows
- Windows 95
- Windows 98
- Windows NT
- Wizard
- Workspaces
- X
- Xeon 12, 14
- Z
- Zip drives
- Zones
CHAPTER 7 Deploying and Maintaining Packages
141
Updating Virtual Machines
From time to time, you may need to update your end users’ virtual machines. In
general, there are two ways of providing updates.
• You may need to update the guest operating system or provide an update to a
program running in the guest operating system.
• You may need to update either the virtual machine itself or policies applied to
the virtual machine or add a new virtual machine to the package.
Distributing Software Updates
If you simply need to update the operating system or other software running inside
the virtual machine, in most cases you should use the same mechanisms you use to
distribute software updates to physical computers.
The advantage of distributing updates in this way is that end users’ data stored in their
virtual machines is not affected by the update.
If you are using virtual machine versions to ensure that your end users are running up-
to-date virtual machines, see Using nq-set to Update Network Quarantine Versions on
page 146 for information on how to update the version number when the user
updates software in the virtual machine.
If you plan to distribute additional copies of the virtual machine, you should also use
nq-set to update the version number in your local copy of the virtual machine and
create an updated package for future distribution.
Creating Update Packages
If you need to provide a completely new virtual machine to your end users — either
as a replacement to an existing virtual machine or in addition to any existing virtual
machines — or if you need to change the policies applied to the virtual machine, you
can create an update package for your users to install. You create the update package
using the same project you did to create the original package.
Note: If your users replace an existing virtual machine by installing the update
package, everything in the virtual machine is replaced. This means any user data and
settings stored in the original virtual machine are lost.
In general, when you create an update package, you follow the same steps you do to
create a new package.
1. Using VMware ACE Manager, make any needed changes to the virtual machines.
For example, you may want to update software installed in the virtual machines