Distribution group not showing up in Exchange 2007 GAL

Question

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 [email protected] 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

Answer 1

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.