Is there any problems doing the following. MSFT's only respond, pl

If I take a machine that has MCE 2005 on it, and it was NOT joined to a
domain in the initial setup, is there any issues with changing the registry
key that will allow it to join a domain. I would like a definite answer
before I do this. (and before I wipe it and try to join the domain during
setup).

My take would be there is no problem, since it could be done in the setup,
but was forgotten. I am hoping I am not wrong, but would like a true, from
"the word of GOD" response.

Thank you in advance, anyone who takes the time to answer.
PmCode

 

Extenders will not work with a MCE box that is a domain member. This is a
known issue.

MCE is not supported by PSS, AKA Microsoft support, when joined to a domain.
(This is not the same as "won't work".)

MCE is designed to be sold by OEMs. It is *not* available as a retail
product, so no retail users should ever really need to install it. Given
that, the fact that they didn't remove the domain join functionality during
setup is not the same as it being supported.

 

I know about it not being supported by PSS and the extender issue, neither
of which really concern me at this time.

My main issue is whether or not there are ANY licensing issues by changing
the registry entry allowing domain joining, either in MCE or the server OS
(2K or 2K3 Server). I would love an answer straight from MS, but wouldn't
know who to ask.

Thanks

 

I don't represent Microsoft and I'm not a lawyer, but...

There is absolutely no mention of domain joining
in the MCE 2005 EULA. Search for yourself:

file:///C:/WINDOWS/system32/eula.txt

--
-Bob
_______________________________
Microsoft MVP
Windows XP Media Center Edition
http://www.microsoft.com/ehome

 

Well, let me quote Mike Brannigan [MSFT] from the thread "Operative System"
posted Feb 2.

And later

 

Bob is discussing legal implications.
Doug is discussing support implications.

Who cares about PSS support?
MCE 2005 is an OEM product.
PSS doesn't support it anyway.