Zsoldier's Tech Blog

If not, I highly recommend you register.  Not only is it a fun time, it's probably one of the best 'training' experiences you can get.  In combination w/ the hands-on labs, you'll have access to some of the industries best known experts for immediate answers to your pressing questions.  VMware is also offering 50% off their VCP/VCAP examinations if taken while onsite. Registration Link: http://www.vmworld.com/registration.jspa Letter to convince your Boss: http://download3.vmware.com/vmworld/2014/downloads/vmworld-2014-us-justification-letter.doc VMUG Advantage Discount: By joining the VMUG Advantage program, you can take off $100 of registration among other benefits. For those who are attending: VMUnderground -  http://blog.vmunderground.com/ VMWorld 2014 5k Fun Run -  http://download3.vmware.com/vmworld/2014/downloads/fun-run-info.pdf Recommended Session: INF1601 -  Taking Reporting and Command Line Automation to the Next Level with...

I'll keep this short.  Using Java 7 (1.7) seems to cause this issue: Error occurred during initialization of VM Could not reserve enough space for object heap Upgrading/Installing Java 1.8 "JDK" seems to fix the above issue.  Adding -Xmx<#>m would not fix the issue either. Anyway, figured I'd post this since I really couldn't find an answer to this bizarre issue.

[Update: Come to find out LucD wrote a Get-VIEventPlus function that I did not find before making mine.  He adds some other switches that might be useful, same idea though.  Just tells me I really should keep up on his blog more often.] I wrote this function so I could replace the Get-VIEvent cmdlet in my scripts.  The great part is that the output ends up being roughly the same as the cmdlet so just changing my calls to this custom function speeds everything up like 100-fold.  That might be an exaggeration, but yeah, it's WAY faster. It's written so that most get-vievent common switches are included.  Syntax is 'slightly' different, but usable so you don't have to modify any get-vievent calls too heavily.  I added a 'type' switch which will help shave off even MORE time.  Anyway, feel free to give it a try or let me know if you have any feedback. Finally, It's written like a cmdlet so you can import it as a module or dot source it.  I've ...

I've found this post by  Josh Perkins  helpful in more ways than the one demonstrated.  It's allowed me to not only update my vcops plugin registration w/ vCenter, but also helped me to update my Dell vCenter plug-in so that it connects via its DNS address rather than its IP. http://www.vstable.com/2012/04/02/vcenter-operations-5-x-vcenter-plugin-uses-ip-instead-of-dns-hostname/ However, I decided to explore the possibility of using PowerCLI to fix these registrations. Turns out you can and the change is immediate, so you don't have restart the vCenter service. YAY!  No more cert errors!  You still have to ssh into the vCOPs UI vm and update the viClientConfig.xml file, but that's easy enough. Here is my result (specifically for vCOPs): $BaseURL = " https://myvCOPsRegisteredDNS.Name.local " $ExtURL = " /vcops-vsphere/ " Connect-VIServer my1stvCenterServer, my2ndvCenterServer Foreach ( $DefaultVIServer in $global:DefaultVIServers...

What is it?: Simply put, it's flash acceleration.  You install a VIB in ESXi and register the PernixData Management (virtual management appliance) plugin to vCenter.  You can then take flash drives from each of your ESXi servers and clump them together to make a flash tier across all your hosts. Does vSAN render it obsolete?: Not really, it's a good solution to augment any existing SAN you might have.  It also won't require much change.  The scenery maybe changes as vSAN increases its configs max and traditional SANs fade, but that probably won't be for a long while. The cool things: You can use any SSD you want.  You don't have to purchase high-end or vendor specific SSD's. Reads and Writes can be accelerated. If the SSD fails, if configured, replicates that write to another SSD in the cluster. Yes, you would use network bandwidth @ this point only until the failed SSD is replaced. Most flash caching will only do reads because write redundanc...

Summary: Really a benign error especially if you don't use the function, but quite annoying if vCOPs is looking @ vCenter health. Resolution/Workaround: In my case, it appeared as though the vSphere Web Client service was conflicting w/ this Profile-Driven storage service. Stop vSphere Web Client service Start VMware vSphere Profile-driven Storage Service. Start vSphere Web Client service. For some reason this works and the web client seems to have a bit more intelligence in choosing ports  to connect to rather than the storage service which gives up the second a port it tried is in use.  Probably a hard-coded thing. Other Notes: If you are using the vSphere web client (which I wouldn't even bother with until 5.5 or newer), then it might make sense to install it on a different server to mitigate this issue.  Another possibility is to set its service to a delayed start.

Summary: Connect-VIserver MyvCSAServer was not connecting using my service account's (for scheduled tasks) windows account.  It would always prompt for credentials.  Fairly odd since it has permissions and is able to connect to several other vCenters w/o inputting credentials. By the way, this is very convenient since I don't have to insert passwords anywhere in clear text or come up w/ some crazy solution to encrypt the password. Solution/Workaround: Simply log into the web client using the service account once.  Once authenticated, powerCLI should not have prompt for credentials. [This applied when the VCSA's default identity source is set to Active Directory (Windows Integrated Authentication) and is set as the default domain.  Active Directory as a LDAP server option will not work.] Hypothesis: I'm guessing this is some kind of weird SSO thing, where the account needs to get locally cached prior to allowing Windows integrated authentication.  I...