OK - so I was hallucinating again. But I could have sworn I'd seen it in the GAL.
Oh, well. Thanks for your help. Kurt On Sun, Jun 26, 2016 at 6:15 PM, Michael B. Smith <[email protected]> wrote: > Any/EVERY Exchange object will have an lEDN. EVERY. A DG. A mail-enabled SG. > A contact. A mailbox. A remote mailbox. Etc. etc. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Friday, June 24, 2016 7:54 PM > To: [email protected] > Subject: Re: [Exchange] A very strange problem with a DL - Exchange 2010 > > Yes, I'm looking at the group in ADSIEdit, and there's no LegacyExchangeDN - > or rather it says <not set>, which I take to mean the same thing.. > > I didn't create the group, but it's in the OU we have reserved for Exchange > DLs. > > I suppose that someone could have created a security group and mail-enabled > it. > > Any way to tell if that's the case? > > However, if it's a mail-enabled security group, I have no idea where it was > applied, which is gonna suck for somebody if I have to kill it and start over. > > Kurt > > On Fri, Jun 24, 2016 at 4:42 PM, Michael B. Smith <[email protected]> > wrote: >> FOR THE GROUP? >> >> Then it isn't an Exchange object. Not possible. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Friday, June 24, 2016 7:34 PM >> To: [email protected] >> Subject: Re: [Exchange] A very strange problem with a DL - Exchange >> 2010 >> >> By edit, do you mean add the '\' character in front of the '#' >> character? Yes, I can do that. >> >> But, what is the IEDN? I'm not seeing anything that looks like that in the >> attribute list for ADSIEdit. Oh, wait - do you mean the LegacyExchangeDN? >> That's empty. >> >> Kurt >> >> On Fri, Jun 24, 2016 at 3:58 PM, Michael B. Smith <[email protected]> >> wrote: >>> Can you manually edit the bad field in adsiedit? >>> >>> If so, go for it. >>> >>> If not, blow it away and start from scratch. I recommend you save the lEDN >>> and overwrite that on the new group before you start adding members to it. >>> That will allow for replies to continue working. >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Friday, June 24, 2016 6:39 PM >>> To: [email protected] >>> Subject: Re: [Exchange] A very strange problem with a DL - Exchange >>> 2010 >>> >>> Hmmmm.... >>> >>> After a bunch of failures with dsget, I finally, I tried this: >>> dsquery group -name re* >>> and got a list, including >>> "CN=ReSharperC#Users,OU=ExchangeDLs,OU=US,DC=example,DC=com" >>> >>> So I then did: >>> >>> C:\Batchfiles> dsget group >>> "CN=ReSharperC#Users,OU=ExchangeDLs,OU=US,DC=example,DC=com" >>> dn >>> desc >>> CN=ReSharperC#Users,OU=ExchangeDLs,OU=US,DC=example,DC=com >>> dsget succeeded >>> >>> This looks like what I see in ADUC (and incidentally in ADSIEdit) >>> >>> Does this make sense? Are there next steps for me in trying to recover this >>> in Exchange? >>> >>> BTW, just for grins, I've used get-distributiongroup with -like filters for >>> name, displayname and alias, with negative results. >>> >>> Kurt >>> >>> On Fri, Jun 24, 2016 at 10:42 AM, Michael B. Smith <[email protected]> >>> wrote: >>>> The distinguishedName is probably the right answer. Easy to test on a DC: >>>> >>>> dsget group >>>> "CN=ReSharperC\#Users,OU=ExchangeDLs,OU=US,DC=example,DC=com" >>>> >>>> Should give you a couple of lines of data about the group. >>>> >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Kurt Buff >>>> Sent: Thursday, June 23, 2016 9:03 PM >>>> To: [email protected] >>>> Subject: Re: [Exchange] A very strange problem with a DL - Exchange >>>> 2010 >>>> >>>> Michael, >>>> >>>> Sorry again for the delayed response - this floated down on my list >>>> of priorities until a couple of other things got finished. >>>> >>>> I probably used ADUC to change the name. >>>> >>>> I'm having problems with renaming back to what it was though - >>>> either I've misremembered the old name, or the effort to rename it >>>> isn't restoring it back to the GAL, for whatever reason, so it's not >>>> showing in the EMC. >>>> >>>> I would guess that I have to restore the original name exactly - am I >>>> correct? >>>> >>>> Regardless, I just performed the following in Powershell: >>>> get-adgroup -filter {name -like "*sharp*"} -properties * >>>> >>>> and I get back the following attributes that mention the name: >>>> >>>> CanonicalName : >>>> example.com/US/ExchangeDLs/ReSharperC#Users >>>> CN : ReSharperC#Users >>>> DistinguishedName : >>>> CN=ReSharperC\#Users,OU=ExchangeDLs,OU=US,DC=example,DC=com >>>> Name : ReSharperC#Users >>>> SamAccountName : ReSharperC#Users >>>> >>>> If this is too much of a bother to pursue, or too risky to fuss >>>> with, I'm OK with noting the members of the group, trashing it and >>>> recreating it - I don't think this list gets much traffic. >>>> >>>> Kurt >>>> >>>> On Sun, Jun 19, 2016 at 3:58 PM, Michael B. Smith <[email protected]> >>>> wrote: >>>>> '#' is a special character in LDAP and in PowerShell. So it has be >>>>> escaped. (And in C and C++ for that matter. I don't think it is in >>>>> C#, somewhat ironically.) >>>>> >>>>> What tool did you use to change the name? >>>>> >>>>> Any object has a bunch of name-related attributes associated with it. >>>>> 'name', 'displayName', 'simpleDisplayName', 'CN=another-name', etc. If >>>>> it's an Exchange object and you changed it with ADUC I’m not surprised it >>>>> 'disappeared'. Change it back with ADUC and then rename it with EMS or >>>>> EMC. >>>>> >>>>> -----Original Message----- >>>>> From: [email protected] >>>>> [mailto:[email protected]] On Behalf Of Kurt Buff >>>>> Sent: Saturday, June 18, 2016 5:17 PM >>>>> To: [email protected] >>>>> Subject: [Exchange] A very strange problem with a DL - Exchange >>>>> 2010 >>>>> >>>>> Someone recently created a DL with a '#' in the name and alias (it's for >>>>> our C# programmers). It displayed fine, but when using PS to manipulate >>>>> the group, it showed up with '\#' - which was interesting. >>>>> >>>>> I wasn't happy with the name used (it didn't match our naming >>>>> standard) so I changed the name to use 'CSharp' instead, as well as to >>>>> match our naming standard. >>>>> >>>>> Now I can't find the group in Exchange - at all. Not in the GAL via >>>>> Outlook, not in the EMC, and not with get-distributiongroup, even more >>>>> than 24 hours later. I haven't rebooted the box yet - I'll probably do >>>>> that tomorrow morning. >>>>> >>>>> I can see the group with get-adgroup, but that doesn't expose many of the >>>>> properties, including 'Alias', which I believe still has '#' in the name, >>>>> and which I suspect is causing the problem, though I don't know for sure. >>>>> >>>>> I could just delete the group through AD and recreate it, but that seems >>>>> like a less than optimal approach. >>>>> >>>>> It's quite baffling, and I'd love a clue as to how I can proceed. >>>>> >>>>> Kurt >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
