Cannot add local group in security tab of a folder in WInDows 2003

Hi,


I have created in AD 2 groups: Global Group and Local Group

After that I go to the folder which I want to add the security but I can just add the Global Group. When I try to add the Local Group I can't find it. Why?
LVL 1
SAM2009Asked:
Who is Participating?
 
Paul MacDonaldConnect With a Mentor Director, Information SystemsCommented:
Yes, much!  You're porting the group between domains...
0
 
smangognaCommented:
If you mean to add groups to other groups you have to raise Active Directory domain and forest functional levels and create universal groups

How to raise Active Directory domain and forest functional levels
http://support.microsoft.com/kb/322692/en-us

Otherwise I don't understand.....
0
 
SAM2009Author Commented:
No I just want to add the local group that I just cretaed in the security tab of the folder but when I clicked on ADD I could not see the local group.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
MedflyConnect With a Mentor Commented:
If it's a LOCAL group..
when you are looking at the security permissions to ADD an object.. make sure the LOCATIONS option is set to the local machine.  By default it may be poiting to your domain.
 ScreenShot
0
 
SAM2009Author Commented:
Hey ya it works but I don't understand...  my local group is created in a domain why I should choose as location the server name instead the domain?
0
 
oBdACommented:
There are two kinds of local groups: "real" local groups on a stand-alone machine or a domain member (not on a DC!), and "domain local" groups. The former are not created on a DC, but with the "Local users and groups" MMC on the machine itself. Domain local groups can only be created in AD.
The scope of a real local group is the single machine on which it was created.
Domain local groups are basically local groups on a DC. The scope of this group type is DCs, unless the domain is running at least in Windows 2000 native mode.
In other words: if you've created a domain local group on a DC, and you don't see it on a domain member, then your domain functional level is still Mixed. Unless you have down-level DCs in your domain, you can raise the level.
How to raise Active Directory domain and forest functional levels
http://support.microsoft.com/kb/322692
If you've created a real local group on a member server, then medfly is correct that the object picker's location has to be changed to the local server.
0
 
SAM2009Author Commented:
This is what happen.


1- I open AD and in domain: Dom1.com, I create a local group: Grp_Local.Dom1.com
2- I go to server Server1 and create a folder: FOLDER1
3- I go to security tab of FOLDER1 and want to add the local grp: Grp_Local.Dom1.com, but the server can't find it.
4- If I change the location and choose the server Server1 and try to add Grp_Local.Dom1.com, it works. Windows is abled to find it.

That why I don't understand.

My domaine is:

Domain functional level: Windows Server 2003

Domain server level: Windows 2000
0
 
MedflyCommented:
That IS certainly odd behavior..
It sounds like you somehow created a group Local to Server1, not a Domain Local group in your AD ... That's the only explanation I know for the situation you have described.

When you say you created a Local Group... did you create it as a Global -Security Group (default option), or did you select the radio button for a Domain Local -Security Group?  Either way, it should still be visible in your AD, but just trying to understand what you did.

Also.. based on your comments.. all your domain controllers are Windows Server 2003 but you have member servers still running Server 2000?
0
 
SAM2009Author Commented:
I create my domain local group in AD by selecting the radio button for Domain Local -Security Group and yes I still have Windows 2000 servers.
0
 
MedflyCommented:
I'm afraid I don't have any explanation for why you needed to select the server as the location in order to add the AD group.  But ... at least you were able to accomplish your task.  Glad I could get you that far at least.
0
 
SAM2009Author Commented:
HAHHAH that's weird! It's the first time I see that! :)
0
 
oBdACommented:
Is "Server1" a DC?
If not, which OS, and did you check whether there is a real local group named "Grp_Local" on this machine?
0
 
SAM2009Author Commented:
No the server is a DFS  and in Server1 there is no group like "Grp_Local" and by the way when I added it I put: Dom1\Grp_Local, so there is no confusion.
0
 
SAM2009Connect With a Mentor Author Commented:
Hey Sorry guys the Server1 is an NT4 domain and Dom1 is Windows 2003 domain maybe that why I need to choose the local server first as location and add domain local group by adding: "Dom1\Grp_Local"

Does it make more sense?
0
 
oBdAConnect With a Mentor Commented:
That's why I explicitly asked for the machine's OS in http:#a34979430 ...
Yes, that makes more sense, because the NT4 object picker doesn't know the first thing about domain local groups on a member server.
On any other domain member with W2k or a later OS, you should be able to find the DL group through AD.
0
 
SAM2009Author Commented:
Thank you!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.