Discussion Locked

Active Directory/Domains

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello:

Our organization is in the process of implementing a subdomain of our primary domain. We would like to make it to where users of the primary domain can access all resources of the subdomain. Also we would like to make it to where subdomain users cannot access the primary domain. I really can't figure out any good way to do this since the primary domain will always trust the subdomain by default. Any thoughts or suggestions?

21 replies

by ragingbull

OK I am guessing you are running an Active Directory setup (from the title) but to clarify the top level domain is called the root domain and the subdomain is referred to as the child domain.

Can I ask why you want this configuration?

MS used to recommend an empty root domain with all objects in the child domain for additional security but you really don't need it as long as you admin it properly (minimal Domain Admins)

As a tip always look to simplify the logical structure as much as possible - a single domain should be fine for most uses - you can delegate OUs if you need to ...

by altolbert

We basically want the configuration like this as a security measure. Our security folks would like it done this way for some reason. We want it to act like a "barrier" to prohibit our public users (who would be on the child domain) from accessing our root domain's resources which have our administration and staff users authenticating through it. Basically we want the child domain to authenticate our public users and our root domain users to be able to authenticate through our child domain. The key is that we don't want child domain users accessing the root domain. Sort of like a one-way trust. I hope this sort of clarifies the situation.

by bkinsey1

Maybe I'm missing something in what you're wanting, but the presence of a trust doesn't grant access in and of itself. . . . If your child domain users have no rights in the root domain, they can't access any of its resources, period. The trust merely allows for the granting of access rights across domain boundaries.

Works the other way, too; users in your root domain will not automatically have access to child domain resources (unless they're Enterprise or Forest Admins, of course), just because the domains trust one another. You'll still have to grant access on a resource by resource basis, or do some kind of group mapping.

by bfilmfan

The number one use for a Peer-Root forest design is if you have a non-contiguous DNS name space, as well as, making attacks on the root domain from the peers more difficult.

In addition, if you have different security requirements such as password length and how often it changes, you will be forced to have separate domains.

Since 70% of security incidents are from insiders, this keeps the users of boogiewoogie.org out of heavymetal.com, so to speak. :)

by altolbert

On our root domain we have enabled the "Deny logon locally" option for the user accounts of the child domain. Now when the child domain users attempt a logon of the root domain from a workstation they receive the error message "The local policy of this system does not permit you to log on interactively" Are we on the right track in doing this? Bascically this looks like what we want to have happen. Subdomain users are prohibited from logging on to the root domain. Is there a better way to do this?

by ragingbull

Well,

You can only manipulate trusts between forests and not domains - transitive trusts exist within a forest but the admin of having two forests isn't worth the effort - how do your public users log on? Is there a single generic account or do they each have an account?

You're really not going to achieve much with two domains that you can't achieve with proper GPOs and permissions ...

by altolbert

I myself think it would be better to have a single domain. However, our network and security folks don't like the idea of public and internal users authenticating through the same DC. So, we have to go this route. Our public users will have their own individual accounts to logon to the child domain. As I have been saying we don't want them to be able to login to the root domain. However, we want the root domain users to be able to login to the subdomain. Basically we want to setup an authentication scheme that would enable us to do this.

by djameson

what are your public logons accessing? is there another way to control their authentication? your Internal network should be for you. If this is like a sublease/tenant arrangement, I would explicityl seperate them, not just with child domains, different servers differnt forest, you can still authenticate against them you will just have to have a seperate username and password for that box.

by altolbert

It is all our network. We are the same organization, just a different division of the IT Department. Our network/security folks are the other division. We basically just want users to be able to logon to machines. We won't our public users to just be able to logon to a machine. They do not need to access any resources such as shares--just authentication.

by djameson

just use an OU structure to isolate them, You would be better off to add another DC to your root domain then to build a seperate domain, use the OU structure and Group Policy to isolate the users, you can use the domain security policy to get most of it done, also, you can use the local security policy on the servers that aren't DC's and explicityly deny access to the groups that you don't want access, if it is a load problem and the other systems are on different subnets which is a pretty good Idea you can use seperate DNS Server and modify the entry and make sure that the DC you want them to authenticate is resolved every time.

by ragingbull

Alberto,

I assume you are the sys admin - TELL your network / security guys how it's going to be - don't just implement what they have read in a few technet articles!!!

Single domain seperate OUs - end of! Loads of Group Policy and that's it!

Your only other option would be for 2 forests and create a one way trust ... but OMG so not worth it - if they insist tell the network / security guys that they can design and implement it because you want nothing more to do with their cr*p architecture!

by altolbert

Is there a way in active directory and policies that I can specify an automatic logout after X minutes of inactivity? I would like for the machine to logout of the inactive account and go back to the logon screen without prompting for any saving or other dialogue boxes appearing.

by altolbert

Ok, just to let everyone know we got our subdomain up and working the way we wanted it to. The issue with authentication was solved since the "logon to" option gives users the option of choosing the root or subdomain to login to. We "denied logon locally" to the subdomain users group on the root domain which solves that problem.

I did a search of Google to try and find a solution to the logout problem. I must have been using the wrong keywords or something. The solution in that article works just like we wanted it to.

Thanks!

by ragingbull

But they are still trusted by the root domain - so they COULD still access resources in the root domain ...

But if it works for you good on ya!

by altolbert

As you can probably tell from my posts I am fairly new to domains and Active Directory.

I have searched and cannot find a good solution to setup my machines where they will automatically shutdown at a specific time at night. I know this can be done using task scheduler and the shutdown.exe program on WinXP machines. However, I would like to centrally manage and control this. I don't want to put the script on all my images and then have a need to go back and change it at some later point due to some reason.

Is there any good way to use GPOs or scripts in Active Directory to accomplish a shutdown of all machines? We would like for all of our machines to shutdown at night since nobody is using them and to reduce "wear and tear" on the machines.

by ragingbull

This thread should be in Tech Q&A really - not for generally discussion!

Anyhow, shutdown.exe can be used to shutdown remote computers - run a script from your server.

Personally I want all my machines left on overnight and I force a reboot once a week. This is so I can send SMS jobs out overnight, support out of hours etc etc ... As for "wear and tear" - the machines should be under warranty.

by djameson

This script is a little rough, I modified a script I use to log everybody off to a restart script.

dim ou
dim cn
dim ouarray
dim cnarray
dim objarray
dim objarray1
dim objarray2
dim objouarray
dim DomainName
dim split0
dim split1
dim FTPserver
dim localpath
dim start
dim dn

'BUILD CONFIG FILE -->
set objFS = CreateObject("scripting.FileSystemObject")
set objNewFile = ObjFS.CreateTextFile("computers.txt")

FTPserver = "server8.emerytelcom.com"
DomainName = "dc=emerytelcom,dc=com"
start = main(domainName)

function main(ldpath)
Set objOUS = GetObject("LDAP://" & ldpath)

For Each objOU In objOUS
objouarray = split(objOU.Name,"=")
split0=objouarray(0)
if split0 = "OU" then
objNewFile.WriteLine("'" & objou.Distinguishedname)
end if
split1=objouarray(1)
'BEGIN CN CONFIG -----------------------------------
if split0 = "CN" then 'if The object isn't a OU We assume it is a user,Group,or person.
'we need to test to see if the object is in fact a user we don't want to send to groups at this point.
objarray = split(objou.objectcategory,",")
objarray1 = split(objarray(0),"=")
objarray2 = objarray1(1)
'objNewFile.WriteLine(objarray2)

if objarray2 = "Computer" then

objNewFile.WriteLine("'\\" & split1)

Set OpSysSet = GetObject("winmgmts:{(Shutdown)}//" & split1 & "/root/cimv2").ExecQuery("select * from Win32_OperatingSystem where Primary=true")
'
for each OpSys in OpSysSet
OpSys.Win32Shutdown 2
next

end if

end if

'BEGIN OU INTERATION ----------------------------------
if split0="OU" then
dn = objOU.DistinguishedName

'objNewFile.WriteLine()
' objNewFile.WriteLine()
'objNewFile.WriteLine()
' objNewFile.WriteLine()
' objNewFile.WriteLine()
'
' objNewFile.WriteLine(dn & "---------------------------------------------------------")

if dn <> "OU=Exchange Servers,DC=emerytelcom,DC=com" and dn <> "OU=Domain Controllers,DC=emerytelcom,DC=com" and dn <> "OU=COMPUTERS,OU=SERVERS,DC=emerytelcom,DC=com" and dn <> "OU=COMPUTERS,OU=CALL CENTER,DC=emerytelcom,DC=com"then
start = main(dn)
end if

end if

Next
end function

objNewFile.Close

by djameson

this liine:
if dn <> "OU=Exchange Servers,DC=emerytelcom,DC=com" and dn <> "OU=Domain Controllers,DC=emerytelcom,DC=com" and dn <> "OU=COMPUTERS,OU=SERVERS,DC=emerytelcom,DC=com" and dn <> "OU=COMPUTERS,OU=CALL CENTER,DC=emerytelcom,DC=com"then
start = main(dn)
end if

Tells you what not to shutdown, because this script shuts down everything in the ad environment.

by syedshafi

I'm working in an organization of 300+ employees. For network resources to be shared by different preveleges I want to imeplement active directory. I went through few resources available on the net. but didn't find a clear solution. I need help in this regard. We use Windows 2003 Server statdard edition and Widows XP as terminals.

This discussion is closed to new replies.