- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's a classic catch-22. I had the same issue with the Appliance version. Needed more Memory and CPU, and was hit by the "web" only for changing HW. Very silly not to catch this simple problem in development.
P.S. Also, be careful to activate vFlash cache on the vCenter Server Appliance virtual disks... It wasn't a pretty sight. There too You'll end up in a catch-22 problem (it made the Appliance very unresponsive++) when You try and remove the vFlash cache again. In my case it refused to remove the cache because there was allready an active task pending (the task was vCenter reconfiguring itself to remove vFlash). Here too You then run into the Web-only config problem since vFlash config/un-config cant be done from the Client.