cheesypete Posted January 8, 2009 Posted January 8, 2009 We started off by moving certain ict rooms over to vanilla clients, this was usefull because it enabled us to setup and test tools such as Italc and steadystate. It also enabled us to make deployment images in advance for these rooms. Jose We are probably following the same path as you, by having one ICT room as "vanilla" - how did this work in terms of user experience? Having created an OU outside of the Establishment structure, and blocking inheritance, we still find that the user GPOs are still being applied (ie RM User Types such as Standard / Advanced Staff). In reality we actually wanted the security settings to be taken across, but we are experiencing such strange issues we kind of want a fresh start! Did you have any problems using the same user accounts for both RM and Vanilla? If you did, how did you get around them? Pete
PiqueABoo Posted January 11, 2009 Posted January 11, 2009 (edited) Perhaps I'm wrong, but I've never understood the widespread CC3 "block inheritance" meme, because if you make a new OU off the AD root then computers in there will only be inheriting Default Domain policy - RM haven't done anything scary in there. Anyway, to stop CC3 user policy applying when CC3 users log on to vanilla machines: Set the computer GPO policy for the vanilla machines to use loopback-replace and then link any user GPOs you want to your vanilla computer OU. If you need different GPOs for different user groups logging on the vanillas, you'll have to security filter them. Honestly, group policies are easy to set up from scratch Naah.. if a complete vanilla from scratch configuration (GPOs and everything else) takes significantly less than 2 months, it's not finished to a reasonable standard or you've imported lots of configuration from elsewhere. Edit: Or there's more than one of you. Edited January 11, 2009 by PiqueABoo
Jose Posted January 12, 2009 Posted January 12, 2009 as the other guy said, just use loopback processing to create user policies. In my personal opinion it does not take 2 months to setup a new nework domain. Our Servers were up and running within days and we just had to rejoin machines to the new domain, configure network printers etc. I hope you are not put off your project by certain people who think everything is difficult when its not
russdev Posted January 12, 2009 Posted January 12, 2009 I have always been of the mind that RM networks are right for some schools and not for others and it is upto the school to decide the way to go. When it comes to it schools choose what is right for them and nobody has right to say that is wrong choice as long as that choice is based on informed decision. @Jose I agree for me it should take about 8 weeks (two months) to setup a vanillia network that is ready, sturdy and bug free. Russ Russ
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now