Integration of Linux and MS Server 2003 on one network

SUSE Linux Standard Server
I am in the process of installing an ERP product that runs on MS SQL Server 2000 and so I will need an MS Server 2003 box on which to run the database. So far simple enough. I also want the run the network using Linux wherever possible - Linux (SUSE Probably) for DNS, DHCP, FIREWALL, and file servers (Samba) the Intranet and Extranet servers will probably end up running apache and we will use PHP and Mysql to hold databases for these. My question is can I easily run MS Server 2003 on such a Linux oriented network - or does 2003 insist on running Active Directory and "take over the domain"? I have heard that MS SQL Server insists on being part of an Active Directory tree! Any truth in that ? Anyone have experience of such a set up? Thanks in Anticipation. Nic

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you just install Server 2k3 and do not make it a domain controller (one of the available roles) then there is no “take over”. Actually, even AD does not “take over” anything, so you would be good there as well. All you need to do is install a fresh Server 2k3 sp1 instance on a box and then install sql 2k sp3 and you are good to go. ERP apps are usually very transactional, so make sure you configure your hardware for this.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Amigus
    You can configure your Windows Server 2003 box in a stand-alone fashion and then have it refer to the Linux machines for DNS, DHCP, etc. You can even have it join an NT4 style domain hosted by your samba servers. You could also run Active Directory with a different domain name than the ones your samba servers use and they can exist side-by-sid What I often do to take full advantage of the possibilites for integration is setup Active Directory and make the Linux boxes members. Samba can do this and using winbindd you can also unify your user-bases. Futher you can use Linux to provide secondary DNS and DHCP. The main rubs for Linux people with this setup is that the Windows box does have to be the primary DNS, LDAP and Kerberos server. The hardest part is the work required in making your Linux DNS, DHCP, LDAP implementations work with Active Directory as well as getting Kerberos authentication going. Given all the above it is possible to have a very tight integration between Linux, UNIX and Windows Server if you're willing to put in the work and you think the advantages are worthwhile. As for your direct questions, no SQL2000 does not require Active Directory and no Active Directory won't "take over" anything unless you tell it to.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: