≡ Menu

Setting up my Xbox 360 was surprisingly easy through the Xbox One; with tinkering that is. Like most people, I would have preferred to be able to use the One as a media center extender, but oh well, still using the 360 as a MCE wasn’t that big of a deal for me. My real gripe was having to use the 360′s controller for TV.

Yesterday, talking with a friend, he was kind enough to tell me about reading a few posts where people were successful with controlling the 360′s extender capabilities using the One. I immediately went to Google. The following is a step by step of my findings:

  1. After the initial Xbox One setup and with the Xbox 360 connected to the One’s HDMI in port, turn the Xbox 360 on.
  2. On the Xbox One, Go to settings and select TV & OneGuide from the tiles.
  3. Select Devices.
  4. Select TV – select your TV brand and the One will guide you through a series of command tests until it learns the exact model.
  5. Select Cable or Satellite Box – manually enter Microsoft as the brand. I had to go through the power commands 20-25 times until it was successful in sending a power down signal to the 360.
  6. You can setup your AV receiver or if/when you are done, go back to the previous menu and select OneGuide.
  7. Enter your zip code and select your cable provider.
  8. Optional – you can enable digital surround sound by selecting Troubleshooting from the TV & OneGuide menu. Select Surround Sound (Beta).

Time spent was close to 5 minutes, most of which was configuring the 360 as a STB. Result: success!

For reference: Can I Use The Xbox One HDMI Pass Through To Run My 360 Media Center Extender???

See this thread if you want your Xbox 360 to boot directly into live TV using MCE: Any way to have Xbox 360 boot straight into Live TV?

vSphere 5.5 SSO Installation FQDN Error

In my vCenter lab, I deployed vCenter 5.5 successfully in one cluster (upgrade), but failed on the second. I received an error that the vCenter 5.5 installation had rolled back after “Importing Lookup Service data.” A few unsuccessful re-attempts later, I did a lot of searching through the VMware knowledge base and the web, but no luck. I abandoned the upgrade until about a week or two ago when I came across a poster on the forums with a similar issue. After some more digging, come to find out, I wasn’t the only person with this issue after release.

Upgrade from vSphere 5.1 to vSphere 5.5 rolls back after importing Lookup Service data (2060511)

In short, the issue lies in using the IP address on my secondary cluster instead of a FQDN. By opening up regedit and making a simple change, the installation was a success.

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Infrastructure\SSOServer

vSphere 5.1 SSO Forgotten Master Password

***UPDATED 08/16/2013***
BR IT UG instructions are well written

The most important step in planning out, upgrading, installing, etc. a vSphere 5.5 environment is the SSO master password. Write it down and store it someplace safe, because the supported recovery method by VMware for a forgotten password is to start over.

If, by chance, you happen to misplace, forget, or accidentally write down the incorrect password, there is a proven method to reset it without a new installation from scratch. It is slightly time consuming, but it is well worth the efforts. Took me a little over 30 minutes from start to finish to do.

The original page, in German: vSAN Beta in der vSphere 5.5 Umgebung

Create a new server, install SQL, run the installation for SSO, connect to the SQL instance and run this query:


The results should be a SSHA hash, which you will copy (I suggest notepad) and you will then connect to the SSO database for which you cannot remember the password. After backing up the current database, update running this query, replacing the hash with the one you just copied:


Reboot the machine running the forgotten SSO password and test!