petersonmd's Posts

Thanks...I'll take a look.  As I said, it's just a cosmetic/UI issue that doesn't affect functionality whatsoever.  I just don't login to the console very often (no need to), and I always do a double... See more...
Thanks...I'll take a look.  As I said, it's just a cosmetic/UI issue that doesn't affect functionality whatsoever.  I just don't login to the console very often (no need to), and I always do a double-take seeing the warning and double-check to make sure that yes, I'm on 7.x.
This is a basic UI problem that I can't figure out how to fix.  It doesn't affect anything except my OCD.   We are running  ESXi 7.0U3 - but for some reason, during the upgrade, the file that contain... See more...
This is a basic UI problem that I can't figure out how to fix.  It doesn't affect anything except my OCD.   We are running  ESXi 7.0U3 - but for some reason, during the upgrade, the file that contains the text that we're running a customized Dell image was not deleted.  Every time I login to the web console, ESXi informs me that we're running 6.0.0U2 A02, even though we're obviously not.  The text is contained in /etc/vmware/oem.xml, but ESXi 7 won't let me chmod / rm the file.  Any ideas on how to get around this?  It's really just an annoyance...but one I'd like to fix.   
Thanks for the input. Management of ESXi will be from the local subnet only (192.168.10.x). No DMZ or network storage - the server itself has 36 GB and 2 TB of local storage which is more than ... See more...
Thanks for the input. Management of ESXi will be from the local subnet only (192.168.10.x). No DMZ or network storage - the server itself has 36 GB and 2 TB of local storage which is more than enough for what we're doing. It's a pretty basic small office environment - just have multiple conflicting software packages that necessitate the separation into virtual machines.
Just getting into the ESXi arena after a couple of years of messing around with VMWare Server. I have a brand spanking new server with 6 NICs - and am looking for advice on how they should be co... See more...
Just getting into the ESXi arena after a couple of years of messing around with VMWare Server. I have a brand spanking new server with 6 NICs - and am looking for advice on how they should be configured. Right now - I have one NIC dedicated for the management interface (192.168.10.2) in vSwitch0. The other 5 NICs are pooled in vSwitch1 and will be allocated across my 5 virtual machines (I guess). Each virtual machine will have a static IP in the 192.168.10.11-.20 range. Am I better off leaving all 5 NICs in vSwitch1 and letting ESXi handle the routing to/from the virtual machines (getting some sort of redundancy I suppose), or should I setup separate switches for each virtual machine and dedicate a single NIC to each? 2 of the 5 virtual machines in use will be hit fairly regularly (file/print server and application terminal server). The other 3 virtual machines will get light use. Have attempted to find a best practices document (or something similar) but haven't stumbled across it yet. Thanks! Mark