|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > Unmapped SID in Exchange Security
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Unmapped SID in Exchange Security
|
|
| Chris Kuebler 2002-10-05, 8:22 pm |
| Hello!
I was wondering if anyone could give some confidence about
taking out a couple of unmapped SIDs in Exchange 2000.
For what I can tell, they've always been there since we
migrated from Exchange 5.5. It's setup with Full Control,
and Deny Recieve As and Deny Send As, allowing inheritable
permissions. The unmapped SID appears as:
S-1-5-21-789008014-1313826502-623647154-1519
If I am thinking correctly, the SID is represented this
way because the object cannot be found, or is no longer
available. Typically, such unmapped SIDs are useless to
the server as long as it is not related to a WAN that
isn't currently accessable. My logic follows that the
server doesn't know where the SID belongs, so it won't
miss it when I remove it. However, I just don't want to
honk-up our mail server in the process.
If anyone can shead light here, or supply confidence for
removing the unmapped SID, please reply. Thank you for
reading!
Chris Kuebler
| |
| Ed Woodrick 2002-10-05, 8:23 pm |
| Seeing the GUID is usually a sign that the account has been deleted and is
no longer available. Generally, these are safe to delete.
"Chris Kuebler" <the__elf@hotmail.com> wrote in message
news:150ab01c259b4$85523da0$39
ef2ecf@TKMSFTNGXA08...
> Hello!
>
> I was wondering if anyone could give some confidence about
> taking out a couple of unmapped SIDs in Exchange 2000.
> For what I can tell, they've always been there since we
> migrated from Exchange 5.5. It's setup with Full Control,
> and Deny Recieve As and Deny Send As, allowing inheritable
> permissions. The unmapped SID appears as:
>
> S-1-5-21-789008014-1313826502-623647154-1519
>
> If I am thinking correctly, the SID is represented this
> way because the object cannot be found, or is no longer
> available. Typically, such unmapped SIDs are useless to
> the server as long as it is not related to a WAN that
> isn't currently accessable. My logic follows that the
> server doesn't know where the SID belongs, so it won't
> miss it when I remove it. However, I just don't want to
> honk-up our mail server in the process.
>
> If anyone can shead light here, or supply confidence for
> removing the unmapped SID, please reply. Thank you for
> reading!
>
> Chris Kuebler
>
|
|
|
|
|