rename a domain and email domain ie: form .co.uk

Discussion in 'Windows Small Business Server' started by stuart macleod, Jul 23, 2005.

  1. I want to build a spare server for our clients in a disaster recovery
    scenario but i want to call it server and call the domain DOMAIN for instance
    and if say the server for tescos falls over i want to rename the disaster
    recovery domain form DOMAIN to TESCOS
     
    stuart macleod, Jul 23, 2005
    #1
    1. Advertisements

  2. yes, or more likely no, depends on the question.
     
    SuperGumby [SBS MVP], Jul 23, 2005
    #2
    1. Advertisements

  3. well i guess i should expain myself better :)

    i want to have aserver sitting in the office already built and all i want
    to do is if one of our clients servers fail i want to rename this server and
    place this in their business whilst we repair the faulty server
     
    stuart macleod, Jul 23, 2005
    #3
  4. stuart macleod

    Matt Gibson Guest

    Then why would you want to change the domain name? That would require all
    the client be rejoined to the new domain, and it would mean a lot of icky
    work.

    The best way would be to join the server to the domain as a secondary DC
    (and GC), then leave it.

    Unless you want this to be a cold swap copy of SBS.

    Matt Gibson - GSEC
     
    Matt Gibson, Jul 23, 2005
    #4
  5. yes i want a cold swap server of sbs2003 the clients only have around 10 pc's
    so its not that much of a task to rejoin them to the domain
     
    stuart macleod, Jul 24, 2005
    #5
  6. Without making this sound likan an oversimplistic answer, you can't do that.

    This is really not the right answer to try to offer your customer(s) as a
    general rule. You are far better off to look into one of two other options:

    1. An additional server running under VPC in your network, possibly even on
    the same SBS Server hardware. Yes, this has some expense by including a
    server license, VPC, and the additional hardware requirements (trivial) to
    accomplish this, and the maintenence of that configuration. This at least
    reduces the cost by the amount of the hardware itself


    2. Disaster Recovery Skill is really the answer here. For instance, your
    plan would work brilliantly if you simple abandon the idea that you are
    going to build a "domain controller" to keep in your office, and instead you
    learn how to do disaster recovery of a DC to different hardware. That would
    mean that you would need to understand how to take a System State backup
    (actually a full system backup) from the customer's server backup and
    restore it onto different hardware (which you would provide).

    The point I'm trying to make here is that there are two ways to recover a
    DC/domain when you have only 1 DC, like with SBS. Either you have another DC
    running in the domain, or you have to learn how to restore the solo DC from
    backup. Anything else is a rapidly declining compromise, and moves from
    server/AD recovery very quickly into Exchange recovery, Sharepoint recovery,
    workstation reconfiguration, and an office full of unhappy staff....plus the
    likely condition of a _very_ unhappy business owner.

    Recovery of a DC/AD to same hardware or different hardware really isn't that
    complicated if you gains some very basic skills. If you have those skills,
    you can quickly move past doing disaster recovery to the same server and do
    recovery...or migration...to any other kind of server hardware. AD is quite
    transportable, and therefore it's very recoverable. What AD is not
    convenient for is renaming, or transitioning in construction phase from "one
    domain to another domain". Therefore, the topic you have proposed is
    actually THE MOST DIFFICULT APPROACH to plan on using. You likely will fail
    in that attemp, because you are doing a very difficult task, and you haven't
    mastered the steps in between, and that's the two alternatives that I
    proposed.

    It just so happens that I am preparing a brand new session for SMB Nation
    2005 in Seattle (Sept 05) in which I will be talking about this exactly
    concept and topic. I would like to say that I can condense the topic into a
    bite size answer for this post, but it's pretty complicated stuff. If you
    really want to get a jump start on the concepts I'm talking about in
    September, and what I've mentioned above, the Disaster Recovery chapter I
    wrote published in Harry Brelsfords SBS Advanced Best Practices book covers
    the ground work for understanding what I'm proposing.

    Rebuilding a domain from scratch is not easy if you intend it to be
    transparent, or even moderately transparent to the business. Most any
    solution that doesn't include either the ability to recover the server to
    different hardware or from another operating DC will require at least a day.
    By contrast, the alternatives for recovery could be as little as 1 hr. Skill
    really is the answer.

    - Jeff
     
    Jeff Middleton [SBS-MVP], Jul 24, 2005
    #6
    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.