Connecting Linux to a Windows domain?

xyeLz

Limp Gawd
Joined
Oct 16, 2011
Messages
134
Is this a normal thing to do? I have a server set up and I would like to dual-boot into Linux (CentOS) while connecting to the Windows domain if possible. Whether this is possible or not, what would the best solution be here? Should I set up a CentOS domain VM on my server along with the Windows environment and just have two servers running for whichever OS I choose to use? Is this the most normal thing to do/best practice?

I use Windows primarily for gaming and office functions.
I use Linux primarily for C++ and Java.

For those wondering, my main reason for doing this with the different OSs and server is to familiarize myself with the environment (Windows Server 2008 R2 and RHEL).

(note the keywords primarily - I use them both for various other tasks)
 
it is possible. I have actually thought of doing that myself at one point. Active Directory is just a modified version of LDAP.

There are various articles out there for joining a Linux machine to a AD domain.

Real question is what is actual end goal you hope to get out of this? All it really gains you is that you can use your AD user accounts on the Linux machine. if that isn't what you want then there isn't a need to join it to the domain. If both OSs are on the same machine then you couldn't join it to the domain as you would need both up and running at the same time to join it to the domain and then for login verification.
 
You are definitely correct in saying that I would like to connect my Linux OS to the Windows domain. (ie: ...use your AD user accounts on the Linux machine.) However, it is a bit more complex then that.

I have APC PowerChute and would like that to be installed to manage the 2 UPSs connected to both the server and the workstation. I am not sure if it's best practice to install the PowerChute Suite only on one server or if I should put the entire suite on each server. For PowerChute, it seems like it might make more sense to be centrally controlled using Windows Server.

However, this leads me into ESET (anti-virus). In the Windows environment, I would have it push out the installation to the desktops. However, I am going to assume that it will not do that with the Linux environment. Therefore, I am going to go out on a limb and say that I will need a separate license of ESET for the Linux workstations?

Both workstation OSs will be on the same machine in a dual-boot setting, but Server 2008 R2 and CentOS 6.2 Samba would be running on VMware so they can run concurrently, as an FYI.

Ergh help!
 
However, this leads me into ESET (anti-virus). In the Windows environment, I would have it push out the installation to the desktops. However, I am going to assume that it will not do that with the Linux environment.

Why not? Once it's on the domain you should be able to create/push a linux installation package.

Therefore, I am going to go out on a limb and say that I will need a separate license of ESET for the Linux workstations?

I would say maybe.. Depends on the licencing. If it's for a set number of seats, it won't matter, because you would only be running either one seat for windows, or one seat for linux.....it's one at a time.
 
Hi Monkey.

I may be confused on the first statement, but what I meant with ESET was the fact that it is installed on the Windows Server and pushed out to Windows machines. I was assuming that you would not be able to push the installation from Windows Server to Linux machines as this would require a separate license on a Linux server to push to Linux machines, right?

How ESET works is they have a business license. 1 x server and 5 x licenses. In purchasing the business license, I believe it is separate for each OS. For example, you can purchase ESET Windows and ESET Linux. This is why I think they need to stay separate.

What about PowerChute? Should this be centrally administered or put on each server for management? APC has PowerChute Server, Console, and Agent. I think Server requires central administration though I could be wrong. Console usually goes with Server and Agent goes individually on any system that will manage the UPS via a web browser. Thoughts on this?

The big question for me is whether or not I will need to create another VM as the Linux domain so that I can connect to the domain with CentOS. What's the best practice here? For example, envision that I work for an organization of 100 people where 90 are using Windows systems and 10 are using Linux for C++. What would be the most ideal way to set this up?
 
Hi Monkey.

I may be confused on the first statement, but what I meant with ESET was the fact that it is installed on the Windows Server and pushed out to Windows machines. I was assuming that you would not be able to push the installation from Windows Server to Linux machines as this would require a separate license on a Linux server to push to Linux machines, right?How ESET works is they have a business license. 1 x server and 5 x licenses. In purchasing the business license, I believe it is separate for each OS. For example, you can purchase ESET Windows and ESET Linux. This is why I think they need to stay separate.

What about PowerChute? Should this be centrally administered or put on each server for management? APC has PowerChute Server, Console, and Agent. I think Server requires central administration though I could be wrong. Console usually goes with Server and Agent goes individually on any system that will manage the UPS via a web browser. Thoughts on this?

The big question for me is whether or not I will need to create another VM as the Linux domain so that I can connect to the domain with CentOS. What's the best practice here? For example, envision that I work for an organization of 100 people where 90 are using Windows systems and 10 are using Linux for C++. What would be the most ideal way to set this up?
Well, I'd have to read the licencing. I haven't dealt with ESET. Mainly SEP, and they deal by the seat. Last one was a small business, got 9 seats - 8 for the workstations, and one for the server (they're all the same no matter the OS or role). You can create installation packages for Windows, mac, and linux.....whatever....as long as you have the seats available. I deal small business exclusively.
 
Well, I'd have to read the licencing. I haven't dealt with ESET. Mainly SEP, and they deal by the seat. Last one was a small business, got 9 seats - 8 for the workstations, and one for the server (they're all the same no matter the OS or role). You can create installation packages for Windows, mac, and linux.....whatever....as long as you have the seats available. I deal small business exclusively.

If I recall correctly from using pile of shit, errr SEP you couldn't push out the Mac OS or Linux. I installed it on an iMac once and had to create the package on the server then go and install it manually on the machine.
 
But it would make the most sense to host a second domain as a Linux domain for anyone using Linux rather than using Server 2008? Would this mean that I would have two primary domain controllers, each for different OSes?
 
How is your network setup? You don't really need to have a Linux domain. I have a windows domain setup at work, then about 7 or so standalone Linux servers. ISP side of the house has who knows how many Linux servers (30+) and all of them are setup as standalones with their own set of usernames and passwords.

If you have a need / desire to be able to use as few accounts as possible to log into every single device then 1 windows domain with Linux servers tied in would be fine. Especially if you will have workstations using both Windows and Linux with a single user maybe having a machine with both OSs that they are logging into that way they only need to remember 1 account. If you only have a few Linux servers there isn't much of a need to setup a domain just for them. Either have them be tied to the Linux server or be standalone.

You also need to take into consideration if files need to be shared between the systems. if the Linux servers are accessing windows shares and windows users accessing shares on the Linux server then you are going to want to have a single domain.

If you don't need them to share any data then there isn't a need to join them.

Without knowing how machine machines you are talking about for the Linux side and what your overall end desire is, it is hard to give you good advise as it would all depend on what you are trying to do. That is like asking if you should get a 2 door car, 4 door car, truck, van, suv or semi but then not tell us what you expect to be doing or what your needs are. if you have 5 kids and haul a boat every weekend then a 2 door car wouldn't be what you would want. if you want a small car to get you alone back and forth to work and never tow anything or have other people in the car very often then a 2 door car is fine. if you are wanting to haul cargo trailers around then you would need a semi. Same thing here. without us knowing exactly what you are trying to do and what your needs are we can't tell you the "best way" to set up your network as there isn't a best way to set it up that works for everyone. Every network is different and has different needs and has a different "best way" to set it up.
 
I have joined Ubuntu/Mac OS clients to Active Directory domains.. it can work okay but you can't really enforce policies just share resources and use central user management.
 
Back
Top