Knowledgebase
Knowledgebase:
sbs2003 to sbs2011 migration problems
Posted by Russ Richards, Last modified by Russ Richards on 30 November 2012 02:26 PM

The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Remove" because:
This server is the Recipient Update Server for the domain "domain.local". You cannot uninstall this server until you select a different Recipient Update Server for this domain. You cannot remove a server that is a target bridgehead for a routing group connector. This server is a target bridgehead for the following connectors: SBS2011

Moved the recipient update service from SBS 2003 to SBS 2011 server.

Removed Routing group connectors. from sbs 2011 server using power shell command .
[PS] C:\>Get-RoutingGroupConnector
Creating a new session for implicit remoting of "Get-RoutingGroupConnector" command...

[PS] C:\>Remove-RoutingGroupConnector -identity "sbs2011"

Confirm
Are you sure you want to perform this action?
Removing routing group connector "sbs2011".
Y

[PS] C:\>Remove-RoutingGroupConnector -identity "sbs2011"
Tried to remove again using integrated setup.
This time it started successfully.

 

"Active Directory Replication is taking longer than expected" message stops SBS installation

  1. On the source server, open Registry Editor. To do this, click Start, type regedit, and then click regedit underPrograms.
  2. Expand the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
  3. In the right pane, double-click BurFlags.
  4. In the Value Data box, type D4, and then click OK.

  5. Exit Registry Editor.
  6. Open Services, and then restart the File Replication Service service.
  7. Check the File Replication Service event log for new errors.
When the Journal Wrap condition is corrected, an event log entry that resembles the following should be logged:

Event Type: Information
Event Source: NtFrs
Event ID: 13516
Description:
The File Replication Service is no longer preventing the computer SERVER from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.

After the Journal Wrap error is corrected, click Yes in the warning dialog box, and then let SBS Setup retry the operation.

If you have more than one working Domain Controller in the environment, follow the steps in the following Microsoft Knowledge Base article to resolve the NTFRS errors:
290762 Using the BurFlags registry key to reinitialize File Replication Service replica sets

The second most common cause of NTFRS issues is connectivity or name resolution problems. In this case, the File Replication Service log will show an an Error event that resembles the following:

Event Source: NtFrs
Event ID: 13508
Description: The File Replication Service is having trouble enabling replication from SERVER1 to 
SERVER2 for c:\windows\sysvol\domain using the DNS name server1.contoso.local FRS 
will keep retrying. Following are some of the reasons you would see this warning.

To troubleshoot this issue, follow these steps:
  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. Use the Ping command together with the internal fully qualified domain name (FQDN) of the source server to test the connection. To do this, run the following command:
    Ping<FQDN>
    Note In this command, <FQDN> represents the FQDN of your source server.
  3. Try to map a network drive to the sysvol share of the source server. To do this, run the following command:
    Net use * \\<Source_Server_Name>\sysvol
    Note In this command, <Source_Server_Name> represents the name of your source server.
  4. Check to make sure that no firewall programs on the source server are blocking RPC connectivity from the SBS 2011 Standard server.
  5. Open services.msc on the SBS 2011 server, and restart the File Replication Service service.
  6. Check the File Replication Service event log on the SBS 2011 server to see whether any errors occured.
If the NTFRS service is working correctly, you should receive the following event:
Log Name: File Replication Service
Source: NtFrs
Event ID: 13516
Description:

The File Replication Service is no longer preventing the computer CONTOSOSERVER from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
After this event is recorded in the File Replication Service event log, click Yes in the warning message dialog box, and then let SBS Setup retest the replication.

 

(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).