skip to content »

inbasys.ru

Msexchange adaccess when updating security for a remote procedure call

Msexchange adaccess when updating security for a remote procedure call-63

Beware of some architects that are not the ones having to deal with the architectures they design, they are often empty suits.Anyway, I see an issue that could be a warning of more to come.

Msexchange adaccess when updating security for a remote procedure call-18Msexchange adaccess when updating security for a remote procedure call-36Msexchange adaccess when updating security for a remote procedure call-9

Good thing this is a blog about IT issues because holey crap what a time eating, confusing and rather pointless mess government administration can be.I also remember happening this to me once before somewhere in February 2010 with another setup of Exchange 2010 on Windows 2008 R2.And in that case the NIC order in the binding list was also OK. But since I build those Exchange 2010 setups myself I just know they are close to godliness both in design and implementation :-).The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.Log Name: Application Source: MSExchange ADAccess Date: 8/19/2010 AM Event ID: 2501 Task Category: General Level: Error Keywords: Classic User: N/A Computer: dagmember1.Description: Process MSEXCHANGEADTOPOLOGY (PID=1620).The process to get to the desired outcome is very tedious, prone to misunderstanding & pretty inefficient .

What the entire duration of the process and the number of administrative entities involved contribute to the desired result is a mystery. But OK, we took the day of to finally get it all sorted after 5 months of patiently waiting for this day.

and after these errors i am getting this information .

Event Type: Information Event Source: MSExchange ADAccess Event Category: Topology Event ID: 2080 Date: 3/31/2009 Time: PM User: N/A Computer: Description: Process MSEXCHANGEADTOPOLOGYSERVICE. Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: DC01 CDG 1 7 7 1 0 1 1 7 1 DC02 CDG 1 7 7 1 0 1 1 7 1 Out-of-site: HO-DC01. WTPK.local CDG 1 7 7 1 0 1 1 7 1 For more information, see Help and Support Center at

Those NIC where OK when I configured those servers.

Checking that has become a second nature on multi homed and clustered servers.

We did some firmware and upgrade recently after hours but that didn’t affect the NIC binding order.