Work Group to Domain

Discussion in 'Server Networking' started by Eric, Apr 23, 2009.

  1. Eric

    Eric Guest

    Hi All,

    I need to move Windows 2008 enterprise from WorkGroup to domain. Should I
    expect any problems?
    This server is used only for web site and is not being used by other
    computers under the same network.

    I have Vista Ultimate that from that computer I use LogMeIn to get into the
    server and use the network to copy files etc..

    Any feedback is appreciated.

    Thanks,

    Eric
     
    Eric, Apr 23, 2009
    #1
    1. Advertisements

  2. A workgroup and a Domain are two different animals. Do you have experience
    managing a domain?


    DDS
     
    Danny Sanders, Apr 23, 2009
    #2
    1. Advertisements

  3. Eric

    Eric Guest

    Hi Danny,

    I understand they are 2 different animals.
    Don't have an experince in managing domain name.

    Maybe there is an article some where about it.

    Thanks,

    Eric
     
    Eric, Apr 23, 2009
    #3
  4. There are tons - and better yet, there are lots of books. I suggest you do
    some serious reading first. If you're hosting a public website on this
    server you don't want to set it up in a domain or make it a domain
    controller - that's a very dangerous thing to do from a security standpoint.
     
    Lanwench [MVP - Exchange], Apr 23, 2009
    #4
  5. I would agree with Lanwench.

    I would suggest taking your time and doing some reading up on AD before
    trying to setup a domain for production use. Set up a test lab with about 2
    computers and 2 servers (Virtual will do). Test having all of them in a
    workgroup, then promote one to a DC and join the workstations to the domain
    and see what happens.

    hth
    DDS

    "Lanwench [MVP - Exchange]"
     
    Danny Sanders, Apr 23, 2009
    #5
  6. Eric

    Eric Guest

    Hi Danny and Lanwench,

    Thanks for the replies.
    As far as I know I thought installing domain in Windows 2008 will increase
    security. This is just an internal domain only to be called WG-1.Local

    I needed also to install the Symantec Backup Exec 12.5 and the software
    mentioned as well that it needs to run under a domain. To install this
    servive as far as I know I need to run DCPromo.exe

    Appreciate your feedback.

    Regards,

    Eric

     
    Eric, Apr 24, 2009
    #6
  7. Thanks for the replies.
    It does increase security to a certain extent. Mostly it centrializes
    how/where you manage your network.

    It's not as easy as running dcpromo. You will have to go to each client and
    join them to the domain, their profiles will change when they join the
    domain. To most users this is percieved as a problem and they will call you
    about it. DNS has to be setup correctly or your clients will not "find" the
    domain to join it.

    If you are moving to a domain only because of Symantec, and you have limited
    experience with Windows domains, IMHO it's not worth the disruption unless
    you "get it right" the first time.

    You say it's a local domain but I assume your users will use the Internet?
    I would strongly suggest getting Virtual server and setting up a workgroup
    and then go through the process of making it a domain. That way you will get
    a chance to see what is happening, ask questions and pin down a working plan
    to do it on your production network.

    hth
    DDS

     
    Danny Sanders, Apr 24, 2009
    #7
  8. Eric

    Eric Guest

    Hi Danny,

    Thanks for your reply.
    That server is not to serve any client really. The router provides the DHCP
    for the clients in the same network, there are only 5 computers.

    That server will run a web site where hundreds of users will perform some
    data search. The server is part of the Network so I can copy files and
    perform updates on it, but that basically it. I actually did it yesterday
    (the domain) while my friend which is a network person helped me to perform
    that. All other clients their work group is the same name as of the domain,
    including my own computer so I can access and all seem to work fine.

    Worth case I always can remove that feature. Also this server is not yet in
    production - still in development mode.

    Regards,

    Eric


     
    Eric, Apr 24, 2009
    #8
  9. Eric

    Eric Guest

    Hi Bill,

    Thanks for your reply. The domain did not exist and I created it. Now for
    the web server will run via a Virtual Machine such as a Hyper_V. So the
    database which is ms sql 2008 will run within the Physical machine.

    At any event it seems the domain is a bad idea. I guess before the computer
    will get into production I will need to remove that feature. On the Virtual
    Machine will have only one account and I guess a Work group will do just
    fine.

    Any other thoughts?

    Thanks,

    Eric
     
    Eric, Apr 24, 2009
    #9
  10. For security reasons, a public-facing webserver should not belong to a
    domain - it should be in a DMZ, isolated from your business network.
     
    Lanwench [MVP - Exchange], Apr 25, 2009
    #10
  11. Eric

    Eric Guest

    Thanks for all the replies.
     
    Eric, Apr 25, 2009
    #11
  12. Hello Eric,

    Following the posting, that youa re not having experience with managaing
    a Domain, i can agree with all the others. Also a webserver should NEVER
    run on a domain controller and be connected to the internet.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Apr 26, 2009
    #12
    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.