Critical issue with vCenter appliance 5.1.0.10000

If you use the vCenter appliance, and also use the vSphere Web Client this is a must read. As of the latest vCenter appliance build 5.1.0.10000-1065184 there is a pretty big issue with certificate regeneration. The problem all starts once you turn it on, and reboot. If you do not already know certificate regeneration is required if you are using a self-signed cert, if your cert does not match your host configuration, changed the system IP address after installation, or if the cert is expired. Any of those reasons will prevent you from logging into the Web Client successfully, and require you to turn on certificate regeneration.

Pretty much out of the gate when you deploy a vCenter appliance you either get an IP dynamically or statically if you so configure one. I've found that despite configuring the IP manually when deploying the OVA the IP still has to be configured manually once the virtual appliance is deployed. Once you change the IP address or host name the certificate no longer works for the Web Client. From there if you attempt to login to the web client you will receive the error "Failed to communicate with the vCenter Single Sign On server". 

The fix is to turn on certificate regeneration and reboot. You can turn on certificate regeneration from the admin tab in the vCenter appliance management console via https:// IP Address :5480. Once there you need to click the "Toggle certification setting to enable certificate regeneration.

Per the build listed above if you do your appliance will reboot, go through the startup process, and hang right after loading the database embedded database. I downloaded and re-deployed the appliance once more. I still had the issue. To resolve the problem I downgraded to 5.1.0.5300-947940. In this build it still hangs on "waiting on embedded database to startup" for approximately 10-20 seconds but it does eventually finish the startup process. In the latest build you can wait an hour. It will not move past that point after turning on certificate regeneration.

Google to IE10 - Your Browser is no longer supported

If you are receiving the message "Your Browser is no longer supported" when you use any of Google services you're not alone. Apparently in the latest round of browsing bashing Google has flagged even the latest version of Internet Explorer as being outdated and unsupported even if your computer is up to date.

If you have been using Google services for a while you're probably already aware they want you to use Google Chrome. Despite that I've confirmed HERE that Internet Explorer is still officially supported. According to the Google product forums this is a bug and Google is working on it although I have not found any official confirmation. It is important to note that IE compatibility view mode can also cause this due to how compatibility view mode works.

Regardless there are definitely issues with Google services and browsers other than Google Chrome. If you use Blogger you've probably seen the below message many times. It's almost easier to just give in and use Google Chrome but I like Internet Explorer so I probably won't be switching. The below error is common in IE, Firefox, and Safari.

 

Microsoft's redesign of email

Like most business users, I've been using Microsoft Office (specifically Outlook) for a very long time. Over the years I've used various email systems and clients but I've always found my way back to using the Outlook desktop application. Webmail has never been very good no matter what system is backing it. Also checking multiple accounts that way can be cumbersome. Last year I traded my Windows computer for a Mac. For a period of time, I went back to using webmail. I quickly retreated back to the Outlook desktop application. I did try Outlook for Mac, but for me, it just wasn't the same.

With the advent of Exchange 2013 came a new version of OWA, and it's great. It is a near complete replacement for the Outlook desktop application. The primary reason why is that accessibility from both Mac and Windows. However, the only major drawback is it does not support external accounts. This means you will still need Outlook to sync multiple accounts into a single place. Office365 does this through a feature called Connected Accounts, but those accounts are only synced once an hour, each time you login, or hit refresh under settings. This alone makes the Outlook desktop application stay relevant.

Microsoft is further bolstering it's new OWA and desktop application via 3rd party add-ins. Two of my favorites are Twitter and LinkedIn. One big problem is there aren't that many apps on the Office Store yet. Also, the social network integration supports only the two social networks previously mentioned. If add-ins for Outlook are anything like add-ins for IE that could mean bloatware will be bundled with software you download. That's been a big problem for Internet Explorer to date. So much so that companies like Google bloat Internet Explorer almost on purpose just to get you to use their browser.

The real gem in Microsoft's new line-up is Office Web Apps Server; this is the technology behind Office365. If you're using Office365 and have both email and Office Web Apps it provides a fully functional Office platform across all devices, Mac and Windows alike. The Office Web Apps do work on mobile devices but the experience could be a little better. Overall, I felt Office365 gave me what I really needed, but wasn't very customizable. For instance, when changing the theme in the Outlook Web App, it only changes the color for about a half inch of space at the top of the screen, and some text. Office365 is very good and the pricing is even better. I only wish Microsoft made the pricing for the Office Web Apps technology behind Office365 more competitive.

I really do like what Microsoft has been doing with email. Microsoft has kept their promise of faster releases and they are making big changes. One thing in particular that I think Microsoft has going for it is they are not afraid of bold changes. Sometimes fool hardily, but innovation is trial and error.

Philadelphia VMUG User Conference registration now open

If you are attending the Philly VMUG this year, registration is now open. It will be held Thursday, May 23, 2013 at the Radisson Valley Forge in King of Prussia. As usual there will be keynote sessions presented by VMware experts, sponsor breakout sessions, VMware educational sessions, exhibits from VMware Partners, complimentary breakfast and lunch, and more.

Philadelphia VMUG User Conference

Are you a VMware Profession who likes free stuff?

If you are a VMware Professional who enjoys free stuff, check out https://www.cloudcredibility.com While you're there check out my profile! By answering some easy VMware questions, having a Twitter account, and/or a blogger account you can win free stuff! And who doesn't like free?!

Setting Exchange 2013 Autodiscover URL

Recently I did an Exchange upgrade to Exchange 2013 and needed to confirm the Exchange PowerShell command to set the autodiscover URLs. I didn't want to just issue the Exchange 2010 commands blindly and hoped they worked.. Below is the command. Just set the SERVERNAME to the name of the Exchange server and the URL as needed.

Set-ClientAccessServer –Identity SERVERNAME –AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml

Installing an OEM branded Windows OS in VMware

If you try to install an OEM branded Windows operating system you will likely have issues activating or installing because it cannot check the BIOS/hardware make. This is pretty common with HP, Dell, or IBM branded media. To resolve this issue you will need to add "smbios.reflecthost="TRUE"." to your .vmx config file. I've heard a number of people saying adding it to the .vmx file did not work. Often it's because it was added incorrectly so here is a way to do it via the vSphere client.

1)      Edit your VM and go to the Options tab

2)      Click General under Advanced, and then click Configuration Parameters

3)      Add a row, and paste smbios.reflecthost as the name, and true as the value.

4)      Reboot your VM and install your operating system

Certainly volume licensing is easier, but sometimes you can get OEM for pretty cheap. If you're hosting VMs for a company and being provided the media, or maybe being forced to spend as little possible and ended up with an OEM installation disk this will allow you to virtualize it. Keep in mind however if its HP branded, it must reside on an HP server. Same for Dell, IBM, etc. If that isn’t possible then you either have to get a server of that type or new media.