@JaredBusch said in MS SQL on Linux rpm missing in repo:

Good work Microsoft......

4fa92e0a-5451-4bf7-a310-aaad98001f48-image.png

msodbcsql17-17.4.1.1-1.x86_64. FAILED https://packages.microsoft.com/rhel/7/prod/msodbcsql17-17.4.1.1-1.x86_64.rpm: [Errno 14] HTTPS Error 404 - Not Found --:--:-- ETA Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. mssql-tools-17.4.1.1-1.x86_64. FAILED https://packages.microsoft.com/rhel/7/prod/mssql-tools-17.4.1.1-1.x86_64.rpm: [Errno 14] HTTPS Error 404 - Not Found --:--:-- ETA Trying other mirror. Error downloading packages: mssql-tools-17.4.1.1-1.x86_64: [Errno 256] No more mirrors to try. msodbcsql17-17.4.1.1-1.x86_64: [Errno 256] No more mirrors to try.

There is no 17.4 in the repo... https://packages.microsoft.com/rhel/7/prod/

Something they released and then pulled, maybe?

Looks like Microsoft finally allowing licenses to be used in hosting services in a way that doesn't mean purchasing a license for every server at the host, but only for a select few places. I'll grant you that they are the major hosting providers, but that still leaves out a bunch of our favorites around here.

@Dashrender I just checked a couple of clients and Time To Live where set to 3600 at most and counting down.

@Obsolesce If it's default then one hour it is.

That screwed me over the other day with Exchange 2016, I clicked on Check updates and it started installing updates without any permission....

I was only looking at exchange online plan 1, but possibly also Azure AD functionality since I was getting into O365 by a toe.

@Obsolesce said in What Happens When Microsoft Doesn't Issue Licenses:

@scottalanmiller said in What Happens When Microsoft Doesn't Issue Licenses:

So the reset and query tool that Microsoft provide do not work (they don't claim that they do in 2016, just that they thought that they would.) They report that all is well, and then RDS fails anyway. So there is both the licensing issue, and an issue with a lack of working tooling.

Next time do it properly?

And not use Microsoft? We did everything we were supposed to do, Microsoft messed it up. Short of not using anything that depends on Windows, what's the solution? Right now Insight and Microsoft are still going back and forth blaming each other.

Unfortunately, not using Windows isn't something we control. But without being able to control that, having a reliable product isn't always something IT determines.

@scottalanmiller
This may also help:
https://blogs.partner.microsoft.com/mpn/myth-busting-software-asset-management-and-compliance-audits/?ln=en-us
https://www.microsoft.com/en-us/licensing/learn-more/compliance-verification-faq

Things like:

Microsoft SAM programs are voluntary services... A compliance audit is a mandatory review of a company’s use of Microsoft’s products and services...
These compliance verifications are initiated across less than 5% of Microsoft’s licensing customers worldwide

But ignoring things like:

We believe that SAM can be a strategic advantage for all our customers

@pmoncho said in The Hidden Cost of Licensing Windows Server - Activation:

@scottalanmiller said in The Hidden Cost of Licensing Windows Server - Activation:

Just looking at this with a customer that just put in a new Windows 2019 server. The machine was purchased with a volume license agreement for Server 2019 Standard. Everything should be super easy, in theory. Problem is, license key from the volume license center doesn't work. We spend a bit of time trying to get this to apply, but no luck.

I have run into a similar situation this morning and not being able activate the VLSC liscense.

Before I decided to call MS and getting frustrated, I was able to activate from an elevated command line.
cscript c:\windows\system32\slmgr.vbs /ipk <product key>

Throwing this out here in case someone comes along this post at a later time.

I've heard that that often works. We had tried that in our case and it had failed.

@wrx7m said in PowerShell - Off-boarding Script:

@dafyre said in PowerShell - Off-boarding Script:

@wrx7m said in PowerShell - Off-boarding Script:

@dafyre I think I found where you got it - https://www.powershelladmin.com/wiki/Powershell_prompt_for_password_convert_securestring_to_plain_text

Anyway, I am not sure where, in my script, I should place that function.

You'd put the actual function at the top of your script, and then just

$myPassword=convertFrom-SecureToPlain -securepassword $MySecurePassword

Wherever you need the password in plain text form.

Thanks. It mostly works. The only problem is that it isn't actually using the password I specify at the top. It is somehow generating its own and then writing it at the end. I put in

write-host "Plain Text Says: $plainText"

and it shows the password that I typed in for the secure variable at the beginning, followed by the one that it generated.

Plain Text Says: $#@%4#@177 Jof91348

Works fine for me here.... Check and make sure you don't have an extra write-host or anything somewhere.

4a0db1d0-785c-4771-9ad2-9cec6cb0434a-image.png