Hello,We have AD running on a 2003 R2 SP2 serverWe have Exchange 2007 running on a 2003 R2 SP2 server on the same domain.I put a distribution group (all staff) on the active directory server. I can e-mail to allstaff@mydomain.com and it goes to everyone I put in that group no problem. However if I do check name, allstaff isn't listed, I have to go to contacts and drop down to find that distribution group (under groups). How do I get it into the global address list so it shows for anyone pressing alt K or checkname along with other members of our domain - I don't want them to have to drop down under the contacts item in outlook to go to groups to find it.Thanks

Have you done anything special with your global address list? Or do you still have the Default Global Address List? Do you have access to ADSIEdit? Can you open up the AllStaff distribution group in ADSIEdit and look at the showInAddressBook attribute? It should include the CN=Default Global Address List.....

Thanks! I don't have ADSIEDIT handy but I may be back at that client Friday. I haven't done anything special with by GAL that I'm aware of. I created another distribution group to see if I had done anything with the all staff group and the second one I created doesn't show either in outlook unless I specially select groups. Is there any way in exchange 2007 Management Console I can change the attribute or is this one of those things I have to spend 20 minutes trying to get the DOS/Powershell command phrased/spaced/attributed correctly to get it to solve the issue? Can't begin to tell you how primitive I think the powershell "feature" is. I can tell you in the management console the column stating hidden from address lists is FALSE

OK - I have no idea why but it has added the test distribution group - didn't have it this morning - I did an update on the exchange server and also downloaded the address book on my outlook client it is there. However I had created Two new Distribution Groups just before forcing the update/generation of address book on exchange and they aren't populated to Outlook yet.

I wonder if this is just something that needs to be updated. You can force the Exchange server to make sure that all recipients show up in the global address list. Of course, it is probably easiest to do using the EMS. Here is the commands you would use: Get-GlobalAddressList | Update-GlobalAddressList This will retrieve all of the global address lists and then pipe each of them to the Update-GlobalAddressList command. I agree that the PowerShell and the EMS might seem a bit cumbersome if you are not used to the command-line, shells, or scripting. I was quite intimidated by it when I first started using E2K7, but I have found some really useful things I could do so I have warmed up to it quite a bit. I think you will be quite pleased with E2K7 SP1 when it comes out, though. Many of the things we have to do via the EMS will be done in the GUI. But, your feedback is certainly things that Microsoft should hear so that as much as possible can be done via the GUI for folks that don't want to use the shell.

Thanks for trying to help. I tried that command as well - waited a while - shouldn't take too long since there are only about 50 users. Did the download address book in outlook - still didn't show. My e-mail maintenance / gal update is scheduled for 5 AM so the new group I created yesterday should have showed in outlook at noon when I tested but it didn't. Also my all staff has been on the server for several days and wasn't showing either. Not sure why it suddenly showed up at 2 or so today. The group I created around 2 still isn't showing up in the GAL however it did show up almost immediately under groups in outlook. I'm not sure why it shows up there immediately but doesn't show up in the address book when you click check name. THis is over my head but I wonder if this is related - http://forums.asp.net/p/1138408/1824551.aspx

I think I have it! After creating the file in EMC, then go to AD and just flip it from distribution group to security group - hit apply - then flip it back, then update/regen the OAB - seems to be an issue between the new Exchange System Manager and AD not being fully integrated.

That was the next thing I was going to suggest. Regenerating the Offline Address Book. The OAB only regenerates once every 24 hours, so if you were looking at data in the OAB, it would usually be a day behind the real system. However, that was the same limitation as E2K/E2K3 for Outlook 2003 or later clients.

Thanks - I don't think the regen of the address book is really the key but modifying the distribution group in AD after you create it in EMC. I had regened the OAB a few times since last friday but the allstaff was only available under groups in outlook. Maintenance runs every morning at 5AM and that didn't update the group into lookup in outlook. It seems to be the broken AD interface between exchange 2007 and windows 2003. You used to be able to see all exchange data for a user or group in AD however now part of it is in Exchange 2007 Management console and some is in AD users and computers. THis is just one more item in my opinion along with the lack of gui control in exchange 2007 that displays the half baked creation that is Exchange 2007. Is the next version of WIndows Server going to require all DOS commands like Exchange 2007 does to do any AD work? Gussy it up with a fancy name like "POWERSHELL" but it is just another way of saying DOS to me. Pretty sure PCs became more popular with GUI interfaces. I used to be an MS FAN (not the same as fanboy who thinks they can do no wrong) but things at MS have taken a SERIOUS turn down hill as of late Vista - incredibly bad performance - no such issue with WIndows 95, 98, 2000, XP - and then they claimed it was drivers, then it was third party apps such as AV or firewalls - 5 months later they finally admit as people set up boxes with all the extras turned off with identical hardware and the latest drivers - hmm XP blows the doors off vista for file copy performance - can't imagine why sales suck for business clients and Dell had to start selling XP again. BTW - I tried their patch for performance - it actually decreased disk to disk performance on the same box while increasing performance by 20% in network copys however since network performance is up to 500% slower than XP that 20% increase doesn't really help enough to offset internal performance slow downs - here is a tip MS - strip out the DRM scanning and you'll get your performance back. Exchange 2007 - ESM worked great in 2003, 2000. 2007 we bring you POWERSHELL known 20 years ago as DOS. Much easier to write scripts like - ## AutoDisco for EWS[array]$SCPCurrent = Get-ClientAccessServer$autodiscoResponse = "<Autodiscover xmlns=`"http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006`">"`+ " <Request>"`+ " <EMailAddress>" + $siSIDToSearch.WindowsEmailAddress + "</EMailAddress>"`+ " <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>"`+ " </Request>"`+ "</Autodiscover>"$strRootURI = $SCPCurrent[0].AutoDiscoverServiceInternalUri.absoluteuri$WDRequest = [System.Net.WebRequest]::Create($strRootURI)$WDRequest.ContentType = "text/xml"$WDRequest.Headers.Add("Translate", "F")$WDRequest.Method = "Post"$WDRequest.UseDefaultCredentials = $True$bytes = [System.Text.Encoding]::UTF8.GetBytes($autodiscoResponse)$WDRequest.ContentLength = $bytes.Length$RequestStream = $WDRequest.GetRequestStream()$RequestStream.Write($bytes, 0, $bytes.Length)$RequestStream.Close()$WDResponse = $WDRequest.GetResponse()$ResponseStream = $WDResponse.GetResponseStream()$ResponseXmlDoc = new-object System.Xml.XmlDocument$ResponseXmlDoc.Load($ResponseStream)$EWSNodes = @($ResponseXmlDoc.getElementsByTagName("ASUrl"))if ($EWSNodes.length -ne 0){$ewsURL = $EWSNodes[0].'#text'}##than just clickin in Exchange System Manager and going to mailbox management like you had to in 2003. Whew glad that trudgery is gone! In just 20 lines I can do what I was forced to do in a couple of mouse clicks in the old version - happy days are finally here. WM6 - the BT stack was horrible in PPC2003, WM5 it was still bad but we've made it intolerable in WM6 - and we've made sure you can't get in touch with anyone at MS to point out these issues. Office 2007 - Gone are all those customizable menus that made your job easy - we've locked them down because we didn't have enough time to fix them after we scrapped our original ribbons interface - we tell you they are locked for security reasons but we'll bring it back as a new feature in the next version of Office. Thanks for letting me dump on the *** coming from MS these days - if their surveys actually let you give open feedback it would be great but their surveys about products are more like - Would you like to give feedback about VIsta? Question 1 - Do you think Vista is a more colorful b more intuitive c more visually stimulating Question 2 Do you think the menu bar a Has better icons b Has better fonts c Looks more user friendly A real question about my Vista experience would be Question 1 What did you think was better about Vista Question 2 What did you think needs fixing in Vista Question 3 Any additional comments MS is determined not to let in any info that might delay releases or improve their products.

I still have a big heart for MS but I have to agree with much of what BoeD is saying...wth is going on in Redmond. Our enterprise network could care less about Yahoo aqquisitions...lets get down to earth with the software then worry about ad revenue. I like google very much but as competition for MS....screw em. They got nothing on Windows or Office. Google office is a joke.

I put a distribution group (all staff) on the active directory server. I can e-mail to allstaff@mydomain.com and it goes to everyone I put in that group no problem. However if I do check name, allstaff isn't listed, I have to go to contacts and drop down to find that distribution group (under groups). How do I get it into the global address list so it shows for anyone pressing alt K or checkname along with other members of our domain - I don't want them to have to drop down under the contacts item in outlook to go to groups to find it. Create new DG only from EMS which correct create group and his attributes. I solve same problem deleting group on the active directory server and re-create from EMS2007. In few minutes I can found group in GAL through outlook 2007 with cache mode.

Hello, We have AD running on a 2003 R2 SP2 server We have Exchange 2007 running on a 2003 R2 SP2 server on the same domain. I put a distribution group (all staff) on the active directory server. I can e-mail to allstaff@mydomain.com and it goes to everyone I put in that group no problem. However if I do check name, allstaff isn't listed, I have to go to contacts and drop down to find that distribution group (under groups). How do I get it into the global address list so it shows for anyone pressing alt K or checkname along with other members of our domain - I don't want them to have to drop down under the contacts item in outlook to go to groups to find it. Thanks Hi ther here in my company we have the same inssue. But in Exchange 2010. Cliente that use outlook cached mode only resolve groups name by selecting all groups. In cached mode the useres only use the offline address list. We change the rebuild of GAL to include the groups to resolve this problem with this steps: open the exchange console Expande Organization Configuration select Mailbox select Offline address Book in default GAL click proprerties in the properties windows select Address List Mark include the default Global Address List (dafault) Mark Include the followng address list click in ADD Select ALL Groups Catalog Click apply Rebuild your GAL Download the new GAL in your cliente ( Default SEND/RECIVED) then the groups will appers in client GLOBAL ADDRESS LIST good luck

Hi, Here's an interesting scenario that maybe you can help with. We have to provision Distribution Groups into a forest where we cannot use Powershell. Is it possible to create DGs in AD and then be able to add them to the GAL without using Powershell or Exchange Management Console which of course sits on Powershell. We are using FIM 2010 to provision the groups. This query is also posted on the FIM forum Cheers Rob

what about if this issue is happening with SBS2003 ? does anyone have any thoughts on this? the issue i am having is a user has 2007 outlook and we have SBS2003 i have created xyz@xyz.com as a distribution group and in the other users that are using outlook 2003 they can see xyz in the GAL, but users with 2007 see it only in ALL Groups. how would i be able to populate this distribution group and others into 2007 outlook users global address list? Any thoughts would be greatly appreciated Thanks, Danny

Hi Danny, Exchange 2007 doesn't run the Recipient Update Service like it did in 2003. To get a DG/Contact etc to appear in the GAL you have to mail enable it using the Exchange Powershell applets. Hope this helps Rob

While I agree with many comments on your frustration on inconsistency, PowerShell != DOS, not by a long shot, they aren't even in the same ballpark.

This worked for me instantly. First after I create the Distribution Group in exchange, I need to go to it in AD change it to a security group and then back to a distrobution group. Once I have done that I run these commands in exchange (PS) powershell (is not DOS) Get-globalAddressList | update=GlobalAddressList (maybe the only one needed to be run here) Get-AddressList | update=AddressList Get-OfflineAddressBook | update=OfflineAddressBook Once these are run I can update the global address list in my outlook via the send receive section making sure I have unselected "download changes since last send receive". And there you have it. all lists updated. I think the main thing learnt here is dont create the group in exchange. Create it in AD first. It looks as though Exchange is not finished in the createing groups in AD department. Hope that Helps

Global Scope - Universal I have the same problem on Win 2008 R2 & Exchange 2007 After trying several times. I found that the AD group which can be used as a distribution group in Exchange is the AD group with universal scope. Active Directory Users and Computer Expand the "User"Select group Double click (open group properties)Click "Universal" in the option Group scope 2. Exchange Management Console Expand "Recipient Configuration"Select "Distribution Group"Menu Action - New Distribution GroupSelect "existing group" and "browse"And so on ....