VMware has introduced an Update Manager tool to facilitate patching of its products, and must have a SQL database server (or you can choose to use an embedded database when installing Update Manager) to install the update Manager program server and administration client side, the following is an example of using the SQL R2 database on Windows Server R2, which describes the installation steps and considerations for the tool in detail.
1. Create a database on the SQL Server, with Vum as an example
650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M00/7F/7F/wKiom1cgiQSzicNFAAF6TyOLiIg090.jpg "title=" 0.jpg " Style= "Float:none;" alt= "wkiom1cgiqszicnfaaf6tyoliig090.jpg"/>
2. Insert the SQL2008R2 disc on the server where you want to install the Update Manager program, install the Client Connection tool
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M00/7F/7C/wKioL1cgidHT9j3VAAH2hkH84CA619.jpg "title=" 1.jpg " Style= "Float:none;" alt= "wkiol1cgidht9j3vaah2hkh84ca619.jpg"/>
3. Locate the ODBC data source when the installation is complete
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/7F/7D/wKioL1cgidPyDXgfAAHnzQv4i1Y694.jpg "title=" 2.jpg " Style= "Float:none;" alt= "wkiol1cgidpydxgfaahnzqv4i1y694.jpg"/>
4. Select the 32-bit local client
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7F/7F/wKiom1cgiQmD1Od4AAE2hBorOLg479.jpg "title=" 3.jpg " Style= "Float:none;" alt= "wkiom1cgiqmd1od4aae2hborolg479.jpg"/>
5. Create a data source named Vum, and the data source name is consistent with the following
650) this.width=650; "src=" http://s4.51cto.com/wyfs02/M01/7F/7D/wKioL1cgidWQvWncAAF2Rv6O2Y8779.jpg "title=" 4.jpg " Style= "Float:none;" alt= "wkiol1cgidwqvwncaaf2rv6o2y8779.jpg"/>
6. Modify the default database for the newly created Vum database
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M02/7F/7D/wKioL1cgidfg5NjUAAFpKpEUULk981.jpg "title=" 5.jpg " Style= "Float:none;" alt= "wkiol1cgidfg5njuaafpkpeuulk981.jpg"/>
7. Test the data source connection
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M00/7F/7D/wKioL1cgidryvVD_AALhJkOOh34839.jpg "title=" 6.jpg " Style= "Float:none;" alt= "wkiol1cgidryvvd_aalhjkooh34839.jpg"/>
8. Exit SQL and place the vcenter installation disk, Update Manager setup on the vcenter installation disk
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7F/7D/wKioL1cgid2hPrxLAALaVLf6Mok478.jpg "title=" 7.jpg " Style= "Float:none;" alt= "wkiol1cgid2hprxlaalavlf6mok478.jpg"/>
9. Enter the vcenter address and account password
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M02/7F/7F/wKiom1cgiRSSvz_oAAGnzWdD8x8575.jpg "title=" 8.jpg " Style= "Float:none;" alt= "wkiom1cgirssvz_oaagnzwdd8x8575.jpg"/>
10. Enter the name of the created data source, but at this point you will find an error, although using a 32-bit ODBC data source
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/7F/7D/wKioL1cgieHh3hHSAAHdpppy87A671.jpg "title=" 9.jpg " Style= "Float:none;" alt= "wkiol1cgiehh3hhsaahdpppy87a671.jpg"/>
11. The reason is that the ODBC data source path in the management tool is under System32
650) this.width=650; "src=" http://s5.51cto.com/wyfs02/M00/7F/7D/wKioL1cgieOgX7LoAAOl37ljeRs652.jpg "title=" 10.jpg "Style=" Float:none; "alt=" wkiol1cgieogx7loaaol37ljers652.jpg "/>
12. But 64-bit operating systems require the use of 32-bit ODBC data sources under SYSWOW64
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M01/7F/7F/wKiom1cgiRzwYQVBAAQou0oCeS0167.jpg "title=" 11.jpg "Style=" Float:none; "alt=" wkiom1cgirzwyqvbaaqou0oces0167.jpg "/>
13. Re-use the 32-bit ODBC under SYSWOW64 to create the DSN and proceed normally
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/7F/7D/wKioL1cgienSj8XaAAIC6UHhI34841.jpg "title=" 12.jpg "Style=" Float:none; "alt=" wkiol1cgiensj8xaaaic6uhhi34841.jpg "/>
14. After the installation is complete, go to install the Vsphere client terminal to open the management plugin
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/7F/7D/wKioL1cgierQGgTiAAEjALHyOHo448.jpg "title=" 13.jpg "Style=" Float:none; "alt=" wkiol1cgierqggtiaaejalhyoho448.jpg "/>
15. Can find update Manager in available Chajian, select download and install
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/7F/7D/wKioL1cgieuTQ-zzAAEljJNheII954.jpg "title=" 14.jpg "Style=" Float:none; "alt=" wkiol1cgieutq-zzaaeljjnheii954.jpg "/>
16. After installation, you will find that there is no update manager under the Web Client interface
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/7F/7D/wKioL1cgie6C43eZAAIYDROQGUs997.jpg "title=" 15.jpg "Style=" Float:none; "alt=" wkiol1cgie6c43ezaaiydroqgus997.jpg "/>
17.update Manager can only be managed via vsphere client side
650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M02/7F/7F/wKiom1cgiSSCewLFAAF6aCMFems364.jpg "title=" 16.jpg "Style=" Float:none; "alt=" wkiom1cgisscewlfaaf6acmfems364.jpg "/>
18. The reason is that when you select download and install in step 15th, he actually installs the update Manager to the client's directory
650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M02/7F/7D/wKioL1cgifDQAihRAAF8H09elJE337.jpg "title=" 17.jpg "Style=" Float:none; "alt=" wkiol1cgifdqaihraaf8h09elje337.jpg "/>
This article from "Rabbit-like rabbit sen Broken" blog, please be sure to keep this source http://arkling.blog.51cto.com/2844506/1768307
Installing vsphere Update Manager and Considerations