13 replies
by vconover Accepted solution
by naughtymonkey Accepted solution
by vconover Accepted solution
by naughtymonkey Accepted solution
by ic-it Accepted solution
(Assuming proper application of the policy to the right object)
Sometimes all the Group policies will not "kick in" on the first startup because of their efforts to lessen the boot time.
You can test this by opening a command prompt and typing gpupdate /force
Another factor may be the propagating of policies to other DCs.
by vconover Accepted solution
I did the /force thing but it didn't make a difference.
I have no idea what "propagating of policies to other DCs" means.
On another note, the login time is sometimes upwards of 4 minutes although it seems that every time I log in to a workstation it gets a little faster.
by cg it Accepted solution
by vconover Accepted solution
by Member 30634329 Accepted solution
Your Group Policy object contains two sections: Computer configurations, which are applied to a computer object no matter which user logs in to it...and User configurations, which are applied to a user object no matter what computer they log into.
If yor policy contains a Computer configuration, you need to apply it to a container that has computer objects in it (such as the Computers OU). Otherwise the policy will not apply to the computer.
Likewise, if your policy contains a User configuration, you must link it to a container that contains User objects, like the Users OU.
At the workstation, you can launch a command prompt and type "gpresult" to see how Group Policy was applied.
by vconover Accepted solution
When I run gpresult on the workstation I get "policy object does not exist".
Looking at the Group Policy Management window, I see my domain and under that I see my OU's, one called Domain Controllers where my one server is shown. The others are the OU's I have created, Students, Staff, Teachers.
Looking at the Active Directory Users and Computers windows I see all of above plus some toher folders - LostAnd Found, System, Users.
I have tried creating users in OU's of my own making and linking Group Policies to no avail.
I have tried creating a user within the Domain Controller OU and linking a GP to no avail.
This really should be simple. I have one physical machine, one domain, one domain controller and three small groups. I want to give everyone a home folder, create some shared folders where teachers can put files for student access, make sure each user can only log in to one computer at a time, make sure users can only see and access their own home folder, and restrict all users from making any changes on the local workstation. I also want to audit user access to the internet. Eventually, I will want to push updates out to workstations.
I used the wizards to set up the server so it is a file server, a DNS server and a Domain. I am wondering if there is something wrong with the setup in DNS.
When I select DNS in the Admin Tools the only thing listed is my Domain Controller. Looking at the properties there, I see that under interfaces it says Listen on all IP addresses. Should I put in the range of my IP addresses in the "Only the following IP addresses" option?
by cg it Accepted solution
OUs are containers. When you install AD on a server there are default containers created in Active Directory. You access these containers from the domain controller in Active Directory users and computers.
now, there is a default group policy when you install the server and Active Directory. A unofficial best practice is to not modify this default configuration so if there is a hickup, you always have the default available that you can fall back on. So that's where OUs come in. you don't apply your GPO to the default domain GP rather to OUs. Group Policy is applied in this order. local, site, domain, OU where local is the local machine [workstation] site is what the name implies [a site in the domain] domain is as the name implies, and OU which is a container.
so, now back to OUs. As first said, OUs are containers and you can collect users and computers into these containers and then apply a GPO to it.
So, what I would suggest is that you test out what your trying to do on a test network, and create some OUs inside the default computers OU in AD, then move 1 computer into that, create a GPO and then apply it to that OU. Test it out.
That way if the GPO doesn't work out, you can unattach it from the OU. you can move the 1 computer back to the default domain computers OU and the computer will revert back to the default config [about 90 minutes later without a GP refresh command or a restart/logoff logon.
added note: OUs and GPOs can get quite complex very quickly. Without some form of written plan, what does what to what can get lost so that you have no idea what GPO being applied to what OU gives what configuration.
plan it out on paper, then test it out on a test network before you try it on your production network.
by naughtymonkey Accepted solution
by vconover Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending