Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 310
  • Last Modified:

GAL updates not reaching clients although clients are downloading GAL & Old Exchange Server (2003) is still showing in the BPA tool

We removed the last 2003 server in the organization a few weeks ago but it is still showing up in the BPA tool.

In addition users added to the GAL a week ago aren't populating in people's GALs when they download it again.  Their GAL download processes without errors, but no changes are actually synchronized.

Are these related?  Other than the Exch 2003 server that BPA thinks is missing there isn't any other red flags in the BPA tools report.
  • 5
  • 3
1 Solution
ChocolateRainAuthor Commented:
I've looked through this guide and everything checked out to the extent that I could check it (as the 2003 server has already been removed from the network and uninstalled).  I've went through multiple guides.  Below is one of my error messages that I'm seeing in the primary exchange servers event log:

- System

  - Provider

   [ Name]  MSExchangeMailboxAssistants
  - EventID 14029

   [ Qualifiers]  49156
   Level 2
   Task 15
   Keywords 0x80000000000000
  - TimeCreated

   [ SystemTime]  2011-10-24T16:45:07.000000000Z
   EventRecordID 540983
   Channel Application
   Computer AGCV10k.domain.lcl

- EventData

I think there is still a reference to it in AD. You will need to go into adsiedit. Please look at the last two items in this KB.

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

ChocolateRainAuthor Commented:
That article regarding ADSI edit doesn't apply to us.

"If you cannot install or run Exchange System Manager, you can use the Active Directory Service Interfaces (ADSI) Edit snap-in to manually remove enough of the server attributes so that you can try a successful reinstallation. This method does not perform cleanups of references to the server object outside the server's own container. We do not recommend that you use this method unless you intend to immediately reinstall the server in the same administrative group. This is because you may have to manually remove or edit many attributes on objects throughout Active Directory"

Going to look at option #2 on Petri and report what I find.

Thanks for the links!
Sorry that was misleading. There is probably a reference to the old Exchange 2003 server that has to be removed using adsiedit. Let me see if I can find the correct step-by-step.

Start ADSIEdit.
Expand the Configuration Container.
Expand CN=Sites.
You will see three folders below sites:
a. CN=Default-First-Site-Name
b. CN=Inter-site Transports
c. CN=Subnets
Expand CN=Default-First-Site-Name.
See if there is a referenc for the old Exchange 2003 server?

CN = configuration
CN = Services
CN = Microsoft Exchange
CN = Domain Name
CN= administrtive groups
CN = Servers
See if there is a server reference for the old Exchange server.
Also you run adsiedit on the domain controller.
ChocolateRainAuthor Commented:
Ended up calling Microsoft.  It was a mix of a few things but this was included as part of our fix.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now