Hello,Currently I am facing the same issue as a lot of persons. The group memberships aren't synchronized anymore with the WSUS groups. The errors I'm getting are the 30103 event ID The SCE Group identified by 'a039467b-a43e-3d25-e7d0-c468879fba4a' could not synchronize to its associated WSUS Group identified by 'f89652cf-f164-4d6a-979f-0933f1e91760' because a connection to the SCE server could not be made. The synchronization will be retried. Management Group: BESRV29_MGRule: System.SCE.MP.GroupSynchronizationRuleInstance: f89652cf-f164-4d6a-979f-0933f1e91760.a039467b-a43e-3d25-e7d0-c468879fba4aInstance Id:{7B1D7D86-C549-C73E-AD84-07B25924B132} The following error occurred. Microsoft.EnterpriseManagement.Common.ServerDisconnectedException: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. ---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:30:00'. ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:30:00'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote hostat System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager)at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count)at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) --- End of inner exception stack trace --- at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count)at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager)at System.ServiceModel.Channels.FramingDuplexSessionChannel.OnSend(Message message, TimeSpan timeout)at System.ServiceModel.Channels.OutputChannel.Send(Message message, TimeSpan timeout)at System.ServiceModel.Channels.TransactionDuplexChannelGeneric`1.Send(Message message, TimeSpan timeout)at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)at Microsoft.EnterpriseManagement.Common.ITypeSpaceDataAccess.GetManagementPackLastChangeTime(String languageCode, Boolean forceDatabaseSync)at Microsoft.EnterpriseManagement.DataAbstractionLayer.TypeSpaceOperations.GetManagementPackLastChangeTime(String languageCode, Boolean forceDatabaseSync) --- End of inner exception stack trace --- at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)at Microsoft.EnterpriseManagement.DataAbstractionLayer.TypeSpaceOperations.GetManagementPackLastChangeTime(String languageCode, Boolean forceDatabaseSync)at Microsoft.EnterpriseManagement.Configuration.TypeSpaceCacheBaseWithManagementPacks.GetLatestManagementPackChangedTime(String languageCode, Boolean forceDatabaseSync)at Microsoft.EnterpriseManagement.Configuration.TypeSpaceCache.Refresh(Boolean forceDatabaseSync, ManualResetEvent acquireCacheUpdateLockEvent)at Microsoft.EnterpriseManagement.ManagementGroupInternal.RefreshTypeCacheInternal(Boolean forceDatabaseSync, ManualResetEvent acquireCacheUpdateLockEvent)at Microsoft.EnterpriseManagement.ManagementGroup.RefreshTypeCache() at Microsoft.EnterpriseManagement.SCE.Modules.DeploymentGroupWriteActionModule.StartWriteAction() I believe this is started around the installation of SP2 of WSUSI've already checked the tables in the SUSDB and OperationsManagerDB to find wrong entries but everything seems OK over thereMany thanks already for the assistancebrgds,Mike

Hello Mike, How many computer groups were created on the SCE server? There is a design limit of 29 groups. If more groups were created, you will see the error(30103) in the event log.Thanks,Yog Li - MSFT

Hello Yog Li,I have verified this, only 20 groups are created.All the groups are not synchronizing. And we believe it started after upgrading the WSUS to Service Pack 2.There once was the fact that we were over 29 groups but it isn't anymore. Could this have broken the synchronization for good?Brgds,Mike

Hello Mike,Generally, the WSUS 3.0 SP2 will not cause a synchronizing issue. I'll keep you informed if I have further information.Thanks,Yog Li - MSFT

Hello Yog Li,For testing purposes I've returned to 16 groups and the problem remainsBrgds,Mike