Uh... afaik R2 always has 2 disks (or thinks it should)

On MSDN there's two disks for both Standard and Enterprise in the ISO downloads. Exactly what does this media look like?

Guest, Mike wrote:

As an interesting aside,

We noticed recently that using an R2 corporate license key on a 2K3 enterprise (integrated sp1) CD causes the media to request the 2^nd disk – even though there is no second disk in the media kit.. (blame the reseller, who supplied us with the incorrect key)

I’ve not had the opportunity (or enthusiasm) to test whether this is also the case with the standard edition

______________________________________________________
Mike Guest | *Capgemini* | Sale
Server Support | Outsourcing UK
Office: + 44 (0)870 366 1814 | 700 1814 | [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>_
77-79 Cross Street, Sale, Cheshire. M33 7HG

*Join the Collaborative Business Experience*
______________________________________________________

------------------------------------------------------------------------

*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Almeida Pinto, Jorge de
*Sent:* 27 July 2006 16:50
*To:* [email protected]
*Subject:* RE: [ActiveDir] R2 vs w2k3 SP1

(1) I remember seing it somewhere (while writing this, I remembered the location which can be found in the link below! ;-)) ). INTEGRATING R2 onto a server does impact that server. It just adds options to the Add/Remove Programs list. Installing one of the new options should not impact the server or other components within the infrastructure. Just like before you would be adding a new option to the server (e.g. adding the DHCP server role to it). However, SOME of the R2 options REQUIRE a schema change (DFS-R, UnixIDm, distributing printer connections through GPOs....) and SOME of the R2 options REQUIRE the new .NET Framwork v2. For those two I say: test, test and test. As always implementing new technology requires testing, but just introducing an option, that option should not have that great of an impact.

(2) ok, done

(3) now I understand...

If you just want to R2 servers from a network source by using the current source a change is needed.

Remember...

CD1 from the R2 distribution set is W2K3 with SP1 slipstreamed, BUT that media will also trigger the INTEGRATION of CD2 from the R2 distribution set. The NORMAL W2K3 with SP1 slipstreamed will not trigger that integration and that must therfore be triggered manually.

From the R2 documentation placing the I386 dir (CD1) and the CMPNENTS dir (CD2) on the same network share should give you the possibility to install servers with the R2 binaries integrated (don't forget to use the R2 product key during the setup, otherwise during the integration you will need to enter the R2 key as well!!!). After that you still need to install the options manually or during install you need to specify what to install by using an answer file.

For additional info also see:

http://download.microsoft.com/download/4/e/d/4eda5dc2-2842-468e-834e-3756e4221cdb/Windows%20Server%202003%20R2%20Overview%20Guide.doc

jorge

    ------------------------------------------------------------------------

    *From:* [EMAIL PROTECTED]
    [mailto:[EMAIL PROTECTED] *On Behalf Of
    [EMAIL PROTECTED]
    *Sent:* Thursday, July 27, 2006 17:12
    *To:* [email protected]
    *Subject:* RE: [ActiveDir] R2 vs w2k3 SP1


    when the R2 binaries are installed on the server the only thing
    that happens is that the R2 options are INTEGRATED (not
    installed). The options still need to be installed additionally.
    So yes, the only difference is the list in Add/Remove Programs.

    **[Neil Ruston] is that documented as being the only change? I can
    see new login bitmaps etc which indicate (IMO) that certain files
    on CD1 differ from the original w2k3 files.**

    There is a small bug....

    There will be a difference in tombstone lifetime depending on
    which server is used to create the forest. This is a bug within R2
    that introduces an incorrect (nothing dangerous) SCHEMA.INI

    If you use a SP1 server to create the forest the tombstone
    lifetime will be 180 days

    If you use a R2 server to create the forest the tombstone lifetime
    will be 60 days (<not set>), while 180 days is expected.

    **[Neil Ruston] yep, discussed this internally already :)**

    don't understand your 2nd Q

    **[Neil Ruston] let's say I have a build source share which houses
    the server build and has sp1 slipstreamed into w2k3. I now wish to
    build r2 servers only and so I'm asked to slipstream r2 into that
    build repository. Is this even a meaningful statement? I ask
    because of the above and the fact that I believe an r2 server may
    appear differently to a w2k3 sp1 server even if CD2 is *not*
    applied.**

    jorge

        ------------------------------------------------------------------------

        *From:* [EMAIL PROTECTED]
        [mailto:[EMAIL PROTECTED] *On Behalf Of
        [EMAIL PROTECTED]
        *Sent:* Thursday, July 27, 2006 15:56
        *To:* [email protected]
        *Subject:* [ActiveDir] R2 vs w2k3 SP1

        Question 1:
        Server 1 is built with R2 CD1. CD2 is not used at all.

        Server 2 is built with R2 CD1 and r2setup is executed from R2
        CD2 as well.

        Will these 2 servers be configured differently in any way,
        other than the additional hooks in 'add/remove programs'?

        Question 2:
        If I have a build created with sp1 slipstreamed, does the
        statement 'slipstream R2 into the build' make any sense? I
        believe it does not make sense but others disagree :)

        Thanks,
        neil

        PLEASE READ: The information contained in this email is
        confidential and

        intended for the named recipient(s) only. If you are not an
        intended

        recipient of this email please notify the sender immediately
        and delete your

        copy from your system. You must not copy, distribute or take
        any further

        action in reliance on it. Email is not a secure method of
        communication and

        Nomura International plc ('NIplc') will not, to the extent
        permitted by law,

        accept responsibility or liability for (a) the accuracy or
        completeness of,

        or (b) the presence of any virus, worm or similar malicious or
        disabling

        code in, this message or any attachment(s) to it. If
        verification of this

        email is sought then please request a hard copy. Unless
        otherwise stated

        this email: (1) is not, and should not be treated or relied
        upon as,

        investment research; (2) contains views or opinions that are
        solely those of

        the author and do not necessarily represent those of NIplc;
        (3) is intended

        for informational purposes only and is not a recommendation,
        solicitation or

        offer to buy or sell securities or related financial
        instruments. NIplc

        does not provide investment services to private customers.
        Authorised and

        regulated by the Financial Services Authority. Registered in
        England

        no. 1550505 VAT No. 447 2492 35. Registered Office: 1 St
        Martin's-le-Grand,

        London, EC1A 4NP. A member of the Nomura group of companies.

    This e-mail and any attachment is for authorised use by the
    intended recipient(s) only. It may contain proprietary material,
    confidential information and/or be subject to legal privilege. It
    should not be copied, disclosed to, retained or used by, any other
    party. If you are not an intended recipient then please promptly
    delete this e-mail and any attachment and all copies and inform
    the sender. Thank you.

    PLEASE READ: The information contained in this email is
    confidential and

    intended for the named recipient(s) only. If you are not an intended

    recipient of this email please notify the sender immediately and
    delete your

    copy from your system. You must not copy, distribute or take any
    further

    action in reliance on it. Email is not a secure method of
    communication and

    Nomura International plc ('NIplc') will not, to the extent
    permitted by law,

    accept responsibility or liability for (a) the accuracy or
    completeness of,

    or (b) the presence of any virus, worm or similar malicious or
    disabling

    code in, this message or any attachment(s) to it. If verification
    of this

    email is sought then please request a hard copy. Unless otherwise
    stated

    this email: (1) is not, and should not be treated or relied upon as,

    investment research; (2) contains views or opinions that are
    solely those of

    the author and do not necessarily represent those of NIplc; (3) is
    intended

    for informational purposes only and is not a recommendation,
    solicitation or

    offer to buy or sell securities or related financial instruments.
    NIplc

    does not provide investment services to private customers.
    Authorised and

    regulated by the Financial Services Authority. Registered in England

    no. 1550505 VAT No. 447 2492 35. Registered Office: 1 St
    Martin's-le-Grand,

    London, EC1A 4NP. A member of the Nomura group of companies.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

Reply via email to