FSE - Active Directory Replication Warning?
-
samedi 12 décembre 2009 23:31I have a single W2K8 R2 domain controller running Microsoft ForeFront Protection2010 for Exchange and whenever I try to configure Antispam components I receive the following error "Active Directory Replication Warning" Exchange management integration has not been enabled. After Active Directory replication of the required credentials has completed, alll functionality, such as antispam managment, on-demand scans, and public folder access, is not available.
The server is completely up to date, there are no other event log warnings and the strangest thing is id I install FSE again it will work just fine but within a 24 hr period i start getting this error. It is a single domain controller so it is not replicating at all. I followed the article "Troubleshooting integration with Exchange Server 2010 Active Directory components." and evrything checks outs? Any ideas?
Toutes les réponses
-
mercredi 16 décembre 2009 02:56Modérateur
Hi,
Thank you for the post.
Before going any further, I’d like to know more information. Would you please help to run FSCDiag.exe out of the FPE install directory and send me the .zip file that it creates?
The FSC diagnostic tool
http://technet.microsoft.com/en-us/library/bb795085.aspx
For your convenience, I have created a workspace for you. You can upload the information files to the following link. (Please choose "Send Files to Microsoft")
Workspace URL: (https://sftasia.one.microsoft.com/choosetransfer.aspx?key=53f26af2-3b10-4193-83ab-b8b2109f0307)
Password: xsU7HWTf935%8
Note: Due to differences in text formatting with various email clients, the workspace link above may appear to be broken. Please be sure to include all text between '(' and ')' when typing or copying the workspace link into your browser.
Regards,
Nick Gu - MSFT -
jeudi 17 décembre 2009 05:48File has been uploaded. Thanks for looking at this!
-
vendredi 18 décembre 2009 13:42Hello,
have you resolved this problem? I'm facing exactly the same warning and some FSE features are not available (antispam and those mentioned in the warning).
Thanks,
-rv-
R.* -
vendredi 18 décembre 2009 20:54No sir, nothing yet, let me know if you find something. Thanks
-
samedi 19 décembre 2009 03:33When I run the Powershell commands to troubleshoot the error as recommended in KB http://technet.microsoft.com/en-us/library/ee358879.aspx I get the following errors. I have verified the the server’s machine account is in the Exchange’s Hygiene Management role group. The thing that kills me most is this is a single domain controller with no replication partners?
Get-FseSpamConnectionFilter : Microsoft Forefront Protection 2010 for Exchange Server does not yet
have the access needed to execute this command. Full Active Directory replication of required cred
entials may not have completed; when replication has completed the command will be available.
At line:1 char:28
+ Get-FseSpamConnectionFilter <<<<
+ CategoryInfo : PermissionDenied: (:) [Get-FseSpamConnectionFilter], ApplicationExce
ption
+ FullyQualifiedErrorId : ExchangeManagementNotAvailable,ForefrontConsole.Powershell.cmdlets.G
et_FSESpamConnectionFilter -
samedi 19 décembre 2009 05:50 What I have found to restore functionality is to stop the "Microsoft Forefront Server Protection Controller" service which stops the "Microsoft Exchange Information Store" and "Microsoft Exchange Transport" service, then restart them. The sad thing about this is that it does not work on a clean reboot you have to do the above steps manually. I am assuming it has something to do with the services not starting in the right order or timing of starting?
- Marqué comme réponse D-a-n_L samedi 19 décembre 2009 05:53
-
dimanche 20 décembre 2009 16:49The other thing that I have noticed is ever since restarting those services manaully the problem has not returned even after multiple reboots, go figure...
-
vendredi 16 avril 2010 18:23Thank you for the incantations. It was certainly easier than removing and re-installing Forefront, which is what I did last time this showed up.
-
vendredi 13 août 2010 19:27I also having exact same issue and as soon as I go to work I will give it a try.
-
vendredi 13 août 2010 20:56
I just came to work and followed D-a-n_L 's way and it worked . Since 3-4 months I was looking for solution so what can I say thank very much:) Obviously this problem by MS and they have to take care of it.
Regards
-
mercredi 18 août 2010 11:28thanks D-a-n_L this perfectly worked and the forefront is now working
-
mercredi 8 décembre 2010 17:02You the man! Worked for me too.
-
mardi 14 décembre 2010 13:23
Same here. Installed FPE on 8 machines, but one sucks. Then I manualle restart FSCController and everything regarding this issue is fine.
BUT: I have to do this manually everytime i restart the machine. There must be a solution.
Furthermore I have a problem with MSExchangeRPC (Microsoft Exchange RPC Client Access on a Unicast NLB Cluster), where the service also needs to be started manually.
Are there any ideas?
Best regards
Stefan
-
jeudi 10 février 2011 20:54
Thanks D-a-n_L, your suggestion to restart the services also resolved the issue for me (something a regular reboot did not fix).
This seems to affect so many people, why haven't Microsoft bothered to fix it yet? Come on MS, get it together please. Service start order is something you really should have nailed down by now.
-
mardi 15 mars 2011 19:44
Thank you for your post
Try changing the startup mode from Manual to Automatic, for some reasons I don't know why Microsoft chose to set this mode to manual,
it is working just fine for me
-
dimanche 14 août 2011 07:31
Open Forefront Management Shell and type the following Windows PowerShell command:
Get-FseExchangeManagementStatus
This returns a value for ExchangeManagementAvailable. If this value is false, Exchange integration has not yet been achieved.
The Domain Administrator can verify if the server’s machine account has been added to Exchange’s Hygiene Management role group.
Do a force AD replication if necessary.
Run the PowerShell commnd Againit resolve my issue please try.
http://technet.microsoft.com/en-us/library/ee358879.aspx
- Proposé comme réponse Leju Joy dimanche 14 août 2011 07:34
-
samedi 31 décembre 2011 04:15
Hello,
I have the same issue with FPE 2010, Exchange Server 2010 SP2, and Windows Server 2008 R2 SP1.
I really dont undestand how is possible MS dont take care of this problem, I found several issues with all that applications is like dont care at all, may be because there are so few people that have bought the product, i dont know.
This Thread was open 2 years ago, and we are experiencing the issue till now.
Unbeleaveble
Cristian L Ruiz -
mardi 1 mai 2012 05:58
This resolved my issue, Thank you much
For some reason my exchange server is no longer in the "Hygiene group". Once I added it there, the value of "Get-FseExchangeManagementStatus" becomes true almost instantaneously.
thank you for the post!
Ed
- Proposé comme réponse ed 4t wowrack.com mardi 1 mai 2012 05:58
.png)
