This message was deleted.
# _general
s
This message was deleted.
a
good question! i always do it before sealing for good measure but not sure if its nessesary
r
I generally have MCS environments with KMS, so it shouldn't matter?
n
So have I, but our W11 master is unable to activate, and don't want to seal this if we need to troubleshoot it.
r
hmm, i don't have any Win11 MCS or i'd look for you. Sorry
Never was a problem with any other OS
n
Yeah, I imagine it's fine, I just don't want to double my effort. This project has already been a massive PITA.
r
😞
have to ask the stupid question, is the Win11 key properly installed in KMS? 🙂
n
That's a great question
r
😄
n
Welp, checking DNS returns servers that are most definitely not KMS servers, so I guess I found our problem, lol
r
hahahaha
you're welcome. 😄 😄
j
KMS/ADBA
j
You are in azure I am assuming …. Those KMS servers may not look like KMS servers, but they could be well be…https://azure.microsoft.com/en-au/updates/new-kms-dns-in-azure-global-cloud/ I see people screwing with azure activation all the time… make sure azure vms use azure kms
n
We are definitely using on-prem KMS servers for this, as our AD team confirmed. I'll send them this link.
j
You’ll never be able to activate multi session win11 with on prem, but normal enterprise will work with 1688 opened. But best to use azure kms
n
We're moving to S19 MS instead of W11 MS...
j
Late to the party, but...
😂 4