Virtual Centre: Difference between revisions

From vwiki
Jump to navigation Jump to search
m (Added "Update Manager" bits)
m (Typo fix)
 
(47 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Sysprep Setup ==
#REDIRECT [[:Category:vCentre]]
 
The following Sysprep support directories were created during Virtual Center installation, these need to be populated in order for the VC to be able to sysprep VM's as they are deployed using Guest Customisation:
 
<pre>
<ALLUSERSPROFILE>\Application Data\Vmware\VMware VirtualCenter\sysprep
...\1.1\
...\2k\
...\xp\
...\svr2003\
...\xp-64\
...\svr2003-64\
</pre>
where <code><ALLUSERSPROFILE></code> is usually <code>C:\Documents And Settings\All Users\</code>.  Windows 2008 (and Vista) don’t need sysprep files as the function is built into the OS.
 
Download the ‘System Preparation Tool’ or ‘Deployment Tools’ package that contains ‘sysprep’ from the Microsoft download centre. Make sure that you download the correct version for the guest operating system and ‘Service Pack’ that you want to customize.
 
'''1.1:'''
In the case of the generic version 1.1 simply run the downloaded executable to extract the files then copy the contents of the Tools directory into the appropriate directory (see below).
 
'''Windows 2000:'''
In the case of Windows 2000 simply run the downloaded executable to extract the files into the appropriate directory (see below).
 
'''Win XP:'''
In the case of XP run the downloaded executable to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below).
 
'''Windows 2003:'''
In the case of Windows 2003 the downloaded executable is a Hot Fix which must be run (Installed) on a matching OS to create deploy.cab then use something like WinZip to extract the files into the appropriate directory (see below).
 
 
== Update Manager ==
=== Import updates from another VC ===
Useful when you've a isolated VC (without internet access), and another with a full compliment of updates.
# Copy the updates from to the VC, copy the entire Data directory
#* Default location for updates <code> C:\Documents and Settings\All Users\Application Data\VMware\Vmware Update Manager\Data</code>
# On the isolated VC, run a version of the following example command to update the Update Manager database
#* <code> vmware-updateDownloadCli -p <path to patches>\Data -f esx -U <user ac> </code>
 
=== Scan/Remediate fails ===
* '''VMware Update Manager had a failure'''
* '''Patch metadata for <ESX> missing, please download patch metadata first''', despite the fact that Update Manager is fully up to date.
* <code>/var/log/vmware/esxupdate.log</code> shows connection errors
 
# On the VC, stop the VMware Update Manager Service
# Edit vci-integrity.xml file
#* Normally found in <code>C:\Program Files\VMware\Infrastructure\Update Manager\</code>
# Edit the following entry, adding the VC IP address
#* <code><PatchDepotUrl>+http://VC-IP/vci/hostupdates/hostupdate</PatchDepotUrl> </code>
# Restart the VMware Update Manager Service
 
 
 
 
 
[[Category:VMware]]

Latest revision as of 15:30, 4 October 2016

Redirect to:

Retrieved from ‘http://vwiki.co.uk/index.php?title=Virtual_Centre&oldid=2642’