4 ms·
Although not even hinted at in the doc, I personally find the tedium of buying and provisioning and monitoring licenses worse than the cost of it. I suppose you
by jhickok 4y ago
Although not even hinted at in the doc, I personally find the tedium of buying and provisioning and monitoring licenses worse than the cost of it. I suppose you are also inviting risk in the form of an audit.
- Xylakant 4y agoMost windows laptops today come with a license key baked into the BIOS. So no need to manage licenses here.
- jhickok 4y agoI do not believe those are sufficient for enterprise licenses, which must be provided separately.
- Xylakant 4y agoThey are sufficient for pro licenses, though, which are what they mention as the required baseline.
- jaywalk 4y agoThere's no requirement to purchase an enterprise license. Large companies just do that to save money.
- trelane 4y agoWait, they buy a second license to save money? How does that work and, more importantly, how can I convince lots of folks to buy my product twice to save money?!
- sumtechguy 4y agoI was looking at a quarter million for a few dozen machines and 2 AD servers and 4 SQL servers. Nearly on par with the cost of the hardware I was buying. Until some bright spark realized it was all testing/dev/qa for those machines, MSDN suddenly was way better cost wise. If all you are doing is testing/dev then MSDN is usually the choice you want (but grab your lawyer to dig into the terms on that one). But in a real env with no dev work, the licenses become a real pain and very costly, and per year recurring many times, and stack because each service type has time, or sometimes they combine. Not dealing with it at all is very tempting.
- trelane 4y agoAlso the always-looming threat of Microsoft telemetry and BSA audit. You can do everything right as far as you can tell, abd they can still come in and make your life miserable.
- dijit 4y agoyou're not really allowed to use those licenses in many contexts. Might be ok for a startup; but at Ubisoft we had to maintain a fleet of KMS infrastructure. https://docs.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys https://docs.microsoft.com/en-us/windows-server/get-started/...
- Kwpolska 4y agoWas your need to maintain KMS actually caused by a Microsoft requirement, or was it rather a cost saving and standarization measure?
- dijit 4y agoIt’s one of those “chicken egg” issues, ultimately it’s not enforced until certain scales. Microsoft does not like >200 machines being activated from 1 IP/Site for example. But you’ll run into issues running the “pro” version of windows, and you’ll need the enterprise version pretty early. Computers don’t ship with enterprise, if any do then it’s certainly not all of them. So you have to license all machines on your network anyway, volume licensing gets cheaper when it’s properly managed. It’s hard to say there’s a hard limit, because there isn’t really one, but it’s sort of expected.
- trelane 4y agoThe more I read of Microsoft licensing, the more it feels like a scam.
- prmoustache 4y ago
- pessimizer 4y agoI've worked at businesses who employed people full-time to manage Microsoft licensing.
- Xylakant 4y agoMicrosoft licensing goes way beyond Windows - there‘s the whole range of office software (which you can also license on Mac), then all the server software, etc., most of which should does not apply to Gitlab (unless they want to deploy on linux and switch to SQL Server as database, but I doubt that). And then, if you‘re big enough, you can negotiate corporate licensing to save money, which requires license management etc. I doubt any of this applies to Gitlab as they stand.