>>>>>>Hi,
>>>>>>
>>>>>>I am investigating an "issue" with ASP.NET application. So far I cannot figure our one thing. The customer has several of this applications, on different VMs. On some VMs, in the application folder, when I go to Properties -> Security, I see a group (image of two faces) with the name the same as the folder name. For example:
>>>>>>Folder C:\MYAPP_XYZ - the Group name in the Security tab MYAPP_XYZ. This "group" has full rights to the folder. But on some other servers, I don't see this group.
>>>>>>
>>>>>>I asked the customer IT, and he does not see such group in the Domain.
>>>>>>
>>>>>>Any idea how this group (of the same name as the folder) could get in the Security tab?
>>>>>
>>>>>Defined on the same box, not on the domain server?
>>>>
>>>>I don't understand the question. But let me describe in more details.
>>>>
>>>>On a server OHAPP01 there are three folders (each folder is a share for the app):
>>>>C:\APP_1
>>>>C:\APP_2
>>>>C:\APP_3
>>>>
>>>>If I go to folder APP_1 and to Properties -> Security, I see a group APP_1
>>>>If I go to folder APP_2 and to Properties -> Security, I see a group APP_2
>>>>and so on.
>>>>
>>>>Then there is another server, say OHAPP02. And the situation is the same (the folder names are different but each has a group the same as the folder in the Security tab).
>>>>
>>>>Does it answer your question?
>>>
>>>No, or perhaps yes... there is no domainName\groupname syntax in group names? Then the groups are probably defined locally, on the same machine, not on the domain. Just a guess, because I generally try to stay away from IT police matters. But they get in the way too often, so one has to know some of their stuff, willy nilly.
>>
>>I think you gave me an idea. If this group is a local group (not domain group), then it is logical why the IT manger does not see it. So, if this assumption is valid, I need to figure out how to see local groups.
>
>Other things to double-check:
>* The security information for the contents of the folder are in agreement with the containing folder (I'd seen situations where access rights weren't in agreement with the containing folder)
>* Make sure access permissions on the sharing tab are in agreement with what's indicated on the security tab. In particular you need to have write and modify access in *both* tabs.
>* if the server is not a Windows system (e.g. Linux) you may also have to check ownership in underlying system (in *nix, you have not only user ownership but also group owner), as well as making sure that users have been registered properly.
>* mix-n-match combination of local security profile and domain profiles is one recipe for strange problems to crop up..

Thank you for your suggestions. This is a Windows VM. I have not had a chance to connect and check if the user group is local. But, meanwhile, I have come up with the solution, in my application. The less I rely on the customer IT support, the better :).