WSUS showing Internal Database as Not Available when I'm using SQLserver

Everything's working right on my W2K8 server but I have this annoying little message in Server Manager/Roles.

One of the roles this server is running is WSUS which in turn is using SQLserver 2008 installed on the same server for its database.

In Server Manager, if I click on Roles, then WSUS, the summary page shows extracts from the event log (all info only) but in the System Services pane underneath, it shows a Warning that the service with the name MSSQL$MICROSOFT##SSEE (and a null Display Name) is Not Available.  Well, of course it isn't because I'm using SQLserver and have no need for the Windows Internal Database.

Anyone know how I can impress upon server manager that this is not a fault and that it shouldn't show as a warning?
LVL 9
losipAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
Check if this article helps you
 
 
Migrating from Windows Internal Database to SQL Server
http://technet.microsoft.com/en-us/library/dd939918(WS.10).aspx 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
losipAuthor Commented:
Yes, thanks.  It was a good thought (especially the wYukonInstalled flag) but I find that all the registry entries, etc are as suggested.  I guess the difference is that I installed WSUS initially to use SQLserver and never migrated from WID.  The only significant areas for concern are that SQLserver is installed locally; not remotely and the article also warns that the instance of SQLserver should not be on a domain controller - it is.  The first may be relevant.

It's not a big problem; I just like everything to be tidy with no errors or warnings.

Thanks for your help
0
losipAuthor Commented:
No one else has bothered so you might as well have some points even though the problem is unsolved after two months.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.