[DISCUSSION] Windows 10 Enterprise (N) LTSB 2016

Ah got you now. Google just brought up loads of results regarding v.a.t

I have used VAMT i use that for my Office MAK key to keep tabs on activations left.

Not ventured into the Active Domain side yet. Hence why it confused me.

 

This filename seems to be incorrect, x21-07421 = non N

SW_DVD5_WIN_ENT_LTSB_2016_64BIT_English_MLF_X21-07421.ISO

 

I took a guess based off the last one I was able to download from my VLSC, and google searches. Thank you for the correct name. Will you be able to post the N version name for me? Probably will be able to find what I need now .

 

That makes sense. It's a lot easier for us to deal with here. We have a very small IT department. 2 in IT for 300+ users.

 

But if you have official VLSC account, why can't you just download it from there?

 

Again, I don't have access to it ATM. I have messed it up, and have a request open with Microsoft to have it corrected. I was trying to update information for the account to due relocating our offices to a new campus, and it locked us out until they go through the verification process that everything is correct.

 

I understand that part about m$ locking the account, had same when the school i worked for relocated up the road to larger premises, took m$ almost a month to sort it even though we gave all information etc.

 

When trying to search out an ISO versus waiting for them to go through the red tape of corrections I found this site with the many different MSDN / few VLSC links I could find. I thought it would be quick to get the one I needed here, but I guess I will just wait it out for them to correct.

 

Code:

SW_DVD5_WIN_ENT_LTSB_2016_64BIT_English_MLF_X21-07421.ISO (3.33 GB)
SW_DVD5_WIN_ENT_LTSB_2016_32BIT_English_MLF_X21-07420.ISO (2.46 GB)
SW_DVD5_WIN_ENT_N_LTSB_2016_64BIT_English_MLF_X21-07487.ISO (3.22 GB)
SW_DVD5_WIN_ENT_N_LTSB_2016_32BIT_English_MLF_X21-07486.ISO (2.38 GB)

 

 

OMG, you are amazing! Thank you! I was able to find the download on here that I needed with that. If there is anything I can ever help with let me know! I will post ISOs as well if needed once I gain access again.

 

You need to login to view this posts content.

 

I really do appreciate the help .

 

Code:

b5d4911bd53ec5029781ade0937dad43c4ed90f6 *en_windows_10_enterprise_2016_ltsb_n_x64_dvd_9057894.iso
b5d4911bd53ec5029781ade0937dad43c4ed90f6 *sw_dvd5_win_ent_n_ltsb_2016_64bit_english_mlf_x21-07487.iso

 

Try it, it doesn't take the VAMT keys. I have already gone through this. Again I have access still to my MSDN. If it worked I wouldn't have been searching out the other.

 

You need to login to view this posts content.

 

I guess that's a question for Microsoft. If you don't believe me though try it. You have VAMT keys it seems since you can get the one that activates just fine with it. The ones from MSDN will not activate each time. I have tried.

 

Probably human error when it failed, i don't have any keys for activating 2016 LTSB.

 

There is no human error involved. The VAMT key is part of Active Directory. You obviously don't understand an Enterprise setup. So I'm done. Thanks for the ISO I needed. See you later.

 

No, i don't know Enterprise setup, what i do know is that 2 exact copies will behave exactly the same.

Last night i wasted quite some time, here, to proof logic

Not to fight you, though, but it's the same with people not trusting svf patches to convert iso's, but when i offer the exact same converted iso as iso, they trust it

 

They will not. Same thing will happen with Office, and Server. VAMT keys require an ISO from VLSC. They will not activate an MSDN ISO. Real life test. Try it sometime. There is no human intervention with VAMT keys. They go into AD. When the client connects it checks against AD. If it was installed with VLSC content the VAMT key activates. If not it doesn't. Plain, and simple.