RebateMonger
Elite Member
A client insisted that I try to integrate his new HP Media Center PC into his Windows Small Business Server 2003 domain.
Here's what happened:
The HP MCE computer didn't come with ANY CDs. I tried to create a set of System Restore disks for MCE 2005, in case the client ever wanted it back. But the HP program that creates them said it'd take about twenty CDs! I didn't have the time to write twenty CDs. There IS a Recovery Partition on the hard drive. I didn't touch that.
I preformed the "Banana" Registry modification of MCE. I then ran the standard SBS "ConnectComputer" wizard to join the MCE to the SBS Domain. The Domain join went flawlessly.
All seemed well. I could access the computer remotely, I could access the Server using cached Domain Credentials, and Group Policy seemed to be applied. However, I noticed in the Server's Event Log that every hour, this computer tried to become the "Master Browser". The SBS Server always won the election, but this shouldn't be happening at all.
Also, after a week or so, the client reported that the MCE computer would drop off the network occasionally.
I decided to install Windows XP Professional on top of the MCE 2005 installation. The only XP Professional available to me was an Upgrade Edition. XP Professional isn't an allowed upgrade from MCE 2005, but we DO have an (unused) Windows 98 license for the upgrade.
However, when I tried running the Upgrade from within Windows MCE, the XP Pro install routine kept denying the Product Key from the XP Pro box. It reported the key was incorrect.
I gave up and rebooted with the XP Pro Upgrade CD. I told it to delete the MCE partition and to reformat and install XP Professional. The install went well. The XP Pro Upgrade did NOT ask for any other proof of prior license. Apparently, it saw the MCE files on the hard drive and said, "Good enough", even though that's not an allowable upgrade under Microsoft's policies.
In summary, it seemed like the "Banana" registry fix works fairly well, but there seem to be some minor problems that weren't acceptable on our SBS network. And you can't do an upgrade installaton of XP Professional over an MCE 2005 installation.
I was tempted to try a "Repair Installation" of XP Pro on top of MCE 2005, but I didn't have time and this project has already taken way too much time.
Here's what happened:
The HP MCE computer didn't come with ANY CDs. I tried to create a set of System Restore disks for MCE 2005, in case the client ever wanted it back. But the HP program that creates them said it'd take about twenty CDs! I didn't have the time to write twenty CDs. There IS a Recovery Partition on the hard drive. I didn't touch that.
I preformed the "Banana" Registry modification of MCE. I then ran the standard SBS "ConnectComputer" wizard to join the MCE to the SBS Domain. The Domain join went flawlessly.
All seemed well. I could access the computer remotely, I could access the Server using cached Domain Credentials, and Group Policy seemed to be applied. However, I noticed in the Server's Event Log that every hour, this computer tried to become the "Master Browser". The SBS Server always won the election, but this shouldn't be happening at all.
Also, after a week or so, the client reported that the MCE computer would drop off the network occasionally.
I decided to install Windows XP Professional on top of the MCE 2005 installation. The only XP Professional available to me was an Upgrade Edition. XP Professional isn't an allowed upgrade from MCE 2005, but we DO have an (unused) Windows 98 license for the upgrade.
However, when I tried running the Upgrade from within Windows MCE, the XP Pro install routine kept denying the Product Key from the XP Pro box. It reported the key was incorrect.
I gave up and rebooted with the XP Pro Upgrade CD. I told it to delete the MCE partition and to reformat and install XP Professional. The install went well. The XP Pro Upgrade did NOT ask for any other proof of prior license. Apparently, it saw the MCE files on the hard drive and said, "Good enough", even though that's not an allowable upgrade under Microsoft's policies.
In summary, it seemed like the "Banana" registry fix works fairly well, but there seem to be some minor problems that weren't acceptable on our SBS network. And you can't do an upgrade installaton of XP Professional over an MCE 2005 installation.
I was tempted to try a "Repair Installation" of XP Pro on top of MCE 2005, but I didn't have time and this project has already taken way too much time.