SCCM and SQL Licencing

[mikemcsharry]

I have a smallish installation and running SCCM on hyper-v on 2012R2 server.

We had a problem with WSUS and need to remove it / re-install it.

 

I have licence keys for SCCM but can't find any for SQL.

Having a few problems in last few days with SQL not starting (so I can't stop / restart WSUS server as I can't connect via Studio to remove WSUS database).

 

I've found out the problem is my 'evaluation period' for SQL has expired.

 

In VLSC it says SQL licence key not needed.

 

I haven't yet applied SCCM licence.

 

What's the best sequence to work through, and do I need to get a specific licence key for SQL?

 

Thanks for any ideas.

 

Mike

[Boredguy]

Our VLSC has a licence key available for the latest version of SQL.

[Guest Guest]

When you download the SQL ISO from the SCCM section of the VLSC the key is already entered when you run the installer

[mikemcsharry]

Ha.. it gets better, I've tripped myself up then stamped on the back of my knee!

I downloaded the evlaution version, all looked good.

I did the 'in situ' upgrade of SCCM to 1910. All still looked good.

Then the SQL problem showed up.

Now, back in licence centre.. There are no SQL licences to be seen (I think the response there from Kieran is one of the answers).

Back to VLSC ..

 

Latest version there is 1902 .. so I can't even get that installer going as it sees 1910 in situ

 

Might be a 'hose this server and start again' time

 

Does anyone have any suggestions? I can't run SQL studio as SQL licence expired so can't get files / database / info backups..

 

Ta for any ideas

[computer_expert]

Are you not able to run the edition upgrade (Maintenance>edition upgrade) from the SQL media to input the key?

 

If you don't have the SQL media, it should be listed as an option in the part of VLSC where you download SCCM current branch according to replies in my quick search.

 

A new SCCM release was pushed to the slow ring the other day (version 2002). I'd wait for the SCCM 2002 media to be released if you go down the route of a fresh install.

[mikemcsharry]

Here's a screen grab from my VLSC ..

When I opt for download on SCCM SQL doesn't appear to be offered

 

Not sure where I'm supposed to get SQL from which I can apply a licence to..

 

- - - Updated - - -

 

Here's a screen grab from my VLSC ..

When I opt for download on SCCM SQL doesn't appear to be offered

 

Not sure where I'm supposed to get SQL from which I can apply a licence to..

 

 

 

[computer_expert]

What happens if you search VLSC for SQL rather than SCCM? Just make sure you get the same version that is currently installed on your server as the keys will probably be different between versions.

 

 

Stupid question, but you are clicking the download link/button aren't you?

Edited May 14, 2020 by computer_expert

[mikemcsharry]

Nope

I hadn't thought of that - I've selected all products - SQL shows nothing at all..

 

I had done the installs following the info here .. https://www.prajwaldesai.com/sccm-1902-install-guide-using-baseline-media/

 

Now to keep hunting. I'm relatively happy to toast it all and start with 1902 downloaded from VLSC.. wonder what that will do for SQL though?

Edited May 14, 2020 by mikemcsharry

[computer_expert]

You should be able to get the key from another page. I don't have access to VLSC currently, but I think it was on a page called something like 'Relationship summary' which gives you a list of all product keys for products you are licenced for.

[mikemcsharry]

I think we're getting closer.. I'm on a facebook group for SCCM and one of the folks there says that when you install SCCM from VLSC it embeds the licence number for SQL -

Now I'v got my head around it, I think that's what Boredguy was saying. Ta

[mikemcsharry]

An update - I foud out what kieran1990 meant above.. When you click to download SCCM from VLSC, the link expands to offer various other downloads, including SQL 2017 and 2019. It now also provides SCCM 2002.

When you do the install, the SQL licence code is shown.

===>>>> Make sure you grab a copy of this code, as you'll need it for installing SQL reporting Services.