Retrieving configuration settings

[TylerApache]

I'm bringing another server into our little ESX farm so I thought this would be a good opportunity to upgrade to 3.5 from 3.0.2. I upgraded VC and am now ready to install 3.5 on my new box. I'd like to pull the configs from the other boxes just for comparison sake. How do I pull those?

[gary1012]

You could pipe the results of esxcfg-info into file. There's a lot of info there, so I'm not sure if you'll be able to see the trees through the forest. Also, /etc/vmware/esx.conf might contain helpful info.

[lamw]

Depends on the level of detailed configurations you're looking for, did you not provision the host using kickstart or set of defined scripts?

You can take a look at this popular ESX 3.x script to extract configurations, this will only work on classic ESX w/Service Console: http://esxhealthscript.svn.sourceforge.net/viewvc/esxhealthscript/

I believe there are some other graphical utilities that can extract configurations, but not sure on their support prior to ESX 3.5

If you want to extract the configurations from your current ESX 3.5 system, you can take a look at script I wrote: Note: this will only work for ESX 3.5+

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

[depping]

I use the COS Healthcheck script. But as far as I'm concerned there isn't much to worry about besides your network setup. You could easily recreate it in most of the cases anyway. I would suggest to do a scripted install this time and save the script and document it.

Duncan

VMware Communities User Moderator | VCP | VCDX

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[TylerApache]

I guess my foggy memory recalls doubling a couple of the recommended partition spaces and fighting with some domain name issues because we are in a hybrid domain/workgroup environment. So, default partition sizes etc are fine in 3.5?

[lamw]

Run the following to see the current partitions on your old hosts:

 vdf -h -P

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

[depping]

No default partitioning isn't fine in my opinion. I would sugges the one in this article I wrote a while ago:

http://www.yellow-bricks.com/2008/10/23/partitioning-your-esx/

Duncan

VMware Communities User Moderator | VCP | VCDX

-

---

Blogging: http://www.yellow-bricks.com

Twitter:

If you find this information useful, please award points for "correct" or "helpful".