Rocket Man Posted July 24, 2012 Report post Posted July 24, 2012 I have installed WSUS on the primary site.......I have now noticed that the windows internal database service MSSQL$Microsoft##ssee is unknown and can not be found in the system services. The WSUS has now got a constant yellow exclamtion mark on it in server management. The strange thing is that it is still syncing successfully on a daily basis according to the SCCM console and the WSUS console. Has anyone had similar issues and is there a simple fix or do I have to uninstall the SUP and reinstall.or do i leave it as it is??? ....the thing is I have quite a few updates downloaded already and all the clients are also reporting to be managed by the system administrator in the windows update panel, even remote clients on different subnets. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted July 28, 2012 Report post Posted July 28, 2012 I really want to have my remote site server DPs acting as a SUP as i do not want remote clients pulling updtaes across VPNs and I want the remote SUPs syncronising with my Primary site SUP but it has the error as above in the snippet. When I am adding the SUP role to the remote site server DP and I get to the stage to point it to the upstram server it is greyed out, it's as if it does not pick up the SUP above even though this is syncing successfully daily. Anyone?? Rocket man Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted July 29, 2012 Report post Posted July 29, 2012 first things first, when you setup the SUP on your primary how did you install it ? Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted July 30, 2012 Report post Posted July 30, 2012 Hi Niall I followed your documents religiously......I think it was fine on the primary SUP, but after some time i noticed the service was in an unknown state..... I am only beginning to phase in the remote SUPs now but have hit a dead end as seen above with the snippets. As i have mentioned the syncronizations are still working away on a daily basis and are also successful....if i run a syncronization from SCCM and open up the WSUS console i can see it is syncing, so there is still a connection i think...but i have lost the MSSQL$MICROSOFT##SSEE service???? Puzzled. I did do some digging and I found that others ran into difficulty with WSUS and MSSQL$MICROSOFT##SSEE after a hotfix came down for WSUS(Kb2720211)....This is also installed on my site server and no option to uninstall I now have another problem and it may be related..but not sure.......whenever i do a fresh OSD the targeted client(s) are not automatically enabled for updates, I have to manually go in to windows update on each client and turn on the windows updates...they are however managed by the System Administrator which is the expected state, but not sure about the....having to manually turn them on?? I have also checked the registry settings on all clients with the above symptoms and the registry value tells me that they know to go to the WSUS server for updates...but should the updates not be turned on??? Thanks Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted August 5, 2012 Report post Posted August 5, 2012 Have finally made progress on this...... I have simply created software update packages such as win7 critical, office, dotNet etc and distributed to DPs and deployed to collections....... The clients are now getting updated via SCCM deployment even if the automatic upadtes are not turned off...i guess this is normal behavior...but still not sure about the unknown service issue. Will leave it as it is, as it is still syncing successfully. Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
