MCE 2005: Need to join domain as first class citizen

Discussion in 'Windows Media Center' started by John Scobey, Mar 31, 2005.

  1. John Scobey

    John Scobey Guest

    I am a software developer and my clients are on domains. I need to join
    their domains and get my Group Policies and run their login scripts.

    I just bought a high-end Dell Inspiron notebook with MCE 2005 installed.
    I'd like to get a TV tuner at some point and record my favorite shows and do
    some of the other things MCE promises. I doubt I'll need/want to use the
    Media Center Extenders.

    My problem is that MCE never offered me the opportunity to join a domain on
    my initial install.

    Other posts on this group by MVPs and other authorities have variously said:

    1. You can't join a domain with MCE 2005 (period),

    2. You can join a domain with MCE 2005, but only during the initially setup
    process.

    3. I spent 3.5 hours on hold for and talking to people at Dell. The last
    person I talked to there said you can't join a domain.

    Q1: So, who's right?

    Q2: Do different OEMs offer differing versions of MCE 2005?

    Q3: Are all editions of MCE 2005 the same, or is there a difference between
    MCE 2005 with or without Service Pack 2?


    I tried to get going on the hack process referred to by several people and
    it went awry right away in step 1. as I was installing the Recovery Console.
    Several dozen of the files that are supposed to copy didn't getting Retry,
    Skip. Had to skip them as Retry didn't do anything.

    Q4: It that SP2 in action stopping me from modifying my OS

    Q5: does the hack not work on currently shipping editions of MCE 2005, or,
    do I not have sufficient rights on my own computer anymore. Do I have to be
    an MCSE to work on my computer ? (joke)


    What I'm about to attempt next is a New Installation of MCE 2005 from the
    January 2005 MSDN Universal distribution.

    Q6: Will this give me an opportunity to join a domain?

    Sorry for so many questions, but I'd like to get to the bottom of this.

    John Scobey
    [email protected]_MEcambridgec.com
     
    John Scobey, Mar 31, 2005
    #1
    1. Advertisements

  2. John Scobey

    GBK Guest

    As far as I know here is the problem.
    When you initially install Windows MCE it's really installing XP Pro Sp2
    that is why you CAN join the domain during the initial setup. Once you
    insert the MCE disk 2 it's going to disable the ability to join domains. so
    if you install and join the domain you will be on the domain however you
    can't change to a different one. MCE is not setup to be a corporate windows
    version which is why the domain is disabled. Personally I would love to
    have the full XP pro functionality as well as MCE running on top of it.
     
    GBK, Mar 31, 2005
    #2
    1. Advertisements

  3. John Scobey

    Jimbo Guest

    Hi John,

    The install SHOULD allow you to join a domain. The problem occurs if you do
    not do it duing setup. This is further compicated by the fact that most
    network card/wireless drivers do NOT get installed by XP and therefore
    joining the domain will fail due to lack of connectivity.

    There is a hack out there - which I have used on my laptop (didn't want me
    main home MCE box on a domain anyway...), but I would have to look for it in
    my files.

    Not sure if posting it here would be 'appreciated'.

    I love MCE and have always been supportive of most things MS, testing stuff
    etc..., but this and a couple of pther decisions regarding MCE are a bit
    odd. Hopefully fixed with the next update or in the next version.

    JS
     
    Jimbo, Mar 31, 2005
    #3
  4. John Scobey

    me Guest

    Personally I would love to
    Mega dittos!
     
    me, Mar 31, 2005
    #4
  5. Answers inline

    You can only join a domain during the actual initail install processes for
    MCE 2005. Post install you cannot.
    No they are the same base OS. This has nothing to do with the doain
    joining - see Q1.
    MCE 2005 is already patched to Windows XP SP2.
    If you use any "hack" to join a domain you will not be supported by your OEM
    (primary provider of support to these machines), nor will you be supported
    by Microsoft if your client has a Premier Support Contract.
    See Q4.
    Yes of course - you are doing a full clean install and you will see the
    dialog box to join a domain during the setup process. However this is
    irrelevant to your client as MSDN operating systems may not be used in a
    production environment. Doing so is a breach of the licensing for these
    products. So while your development and test machines may be domain members
    your clients will continue to not be.

    Maybe you should approach Dell and request a swap out fo the MCE licenses
    for regular Windows XP Professional ones. MCE 2005 is not targeted as a
    corporate desktop solution


    --

    Regards,

    Mike
    --
    Mike Brannigan [Microsoft]

    This posting is provided "AS IS" with no warranties, and confers no
    rights

    Please note I cannot respond to e-mailed questions, please use these
    newsgroups
     
    Mike Brannigan [MSFT], Mar 31, 2005
    #5
  6. John Scobey

    Jason Tsang Guest

    You won't get the option to join, if no network devices are detected during
    install (i.e. if Windows has built in drivers for the network device, you'll
    then get the option to join the domain, if windows does not, then you won't
    get the option to join the domain).
     
    Jason Tsang, Mar 31, 2005
    #6
  7. John Scobey

    John Scobey Guest

    Mike and everyone, thanks very much,

    I'm getting a handle on what's going on with MCE.

    Mike, with respect to
    ====================================
    Yes of course - you are doing a full clean install and you will see the
    dialog box to join a domain during the setup process. However this is
    irrelevant to your client as MSDN operating systems may not be used in a
    production environment. Doing so is a breach of the licensing for these
    products. So while your development and test machines may be domain members
    your clients will continue to not be.

    ==================================

    I'm only talking about one machine: mine, and that's my only machine which I
    use for development and everything else. Are you saying watching a TV
    program on my machine constitutes production use. What if I play minesweeper?

    No clients are involved, except when I'm developing software and I'm at
    their site. I have the license to MCE 2005 that came with the machine from
    Dell. Are you saying that if I use my MSDN copy of MCE 2005 to fix the
    problem I'm having, then I'm in violation when I watch a TV program on that
    machine? Seems pretty bizarre to me.
     
    John Scobey, Mar 31, 2005
    #7
  8. Yes - both of the example you site are production use of the system. The
    MSDN licensing FAQ contains other examples such as sending e-mail via an
    MSDN installed Exchange Server etc etc. MSDN product is for dev and test
    use only. If you intend to make production use of these system then you
    must not use your MSDN product and must purchase appropriately licensed
    product.
    http://msdn.microsoft.com/subscriptions/faq/default.aspx#licensing
    Yes, see above. If you use your MSDN product it may not be used for
    production use - dev/test only.



    --

    Regards,

    Mike
    --
    Mike Brannigan [Microsoft]

    This posting is provided "AS IS" with no warranties, and confers no
    rights

    Please note I cannot respond to e-mailed questions, please use these
    newsgroups
     
    Mike Brannigan [MSFT], Apr 1, 2005
    #8
  9. John Scobey

    GWRiderNW Guest

    I just did it. Was tricky but it worked well. Here is how.

    I fought with it same as all the other threads but this worked well once I
    reasoned it out. I have done it now simply with two other systems.

    My systems have GIG NICs and thus no drivers to connect to the network and
    then be joined to a domain during the initial install. I dug through a box of
    NICs and tried first a Netgear, then a D-Link 10/100 card with no luck. I
    then found a 3COM 3C900TPO card which the drivers were in the install I
    assigned it a static IP for my network and set the gateway and DNS to my
    servers IP (SBS2003). it took and all is well. Once the OS was loaded, I
    removed the older NIC and installed the drivers for the GIG NIC and I am
    fully funtional.

    Pays to have old hardware laying round sometimes but these older NICs can be
    had online for pennies. Worth every cent.

    Hope this helps.

    Too bad theres not a place to post solutions away from all the questions.
     
    GWRiderNW, Feb 4, 2006
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.