They should work. Works for all cores of your host system. Also you can download ESXi from here.
SQL Server 2017 | |
---------------- | |
Enterprise Core - 6GPYM-VHN83-PHDM2-Q9T2R-KBV83 | |
Developer - 22222-00000-00000-00000-00000 | |
Enterprise - TDKQD-PKV44-PJT4N-TCJG2-3YJ6B | |
Standard - PHDV4-3VJWD-N7JVP-FGPKY-XBV89 | |
Web - WV79P-7K6YG-T7QFN-M3WHF-37BXC | |
https://www.teamos-hkrg.com/index.php?threads/microsoft-sql-server-english-2017-rtm-teamos.42103/ |
#!/usr/bin/env python | |
import sys | |
import json | |
import requests | |
import logging | |
import urllib | |
import urllib2 | |
from requests.auth import HTTPBasicAuth | |
reload(sys) |
############ REPLACE app/models/enterprise_token.rb in the source code with this file! ################ | |
############ also be sure to RESTART OpenProject after replacing the file. ################ | |
############ it doesn't show that enterprise mode is enabled in the settings, but all ################ | |
############ enterprise mode features, such as KanBan boards, are enabled. ################ | |
#-- copyright | |
# OpenProject is an open source project management software. | |
# Copyright (C) 2012-2023 the OpenProject GmbH | |
# | |
# This program is free software; you can redistribute it and/or | |
# modify it under the terms of the GNU General Public License version 3. |
The list of actions listed below was taken mostly from Book Of Zeus with minor modifications and did the job well for Ubuntu version, which was available at that moment (May 2016). This gist was created for internal use and was never meant to be discovered by the web, although Google managed to find and index this page, which was a great surprise for me. Please check the original source for the updated information (links are provided in most of the sections), and read the comments below: they provide more details about the usage experience.
http://bookofzeus.com/harden-ubuntu/initial-setup/system-updates/
Keeping the system updated is vital before starting anything on your system. This will prevent people to use known vulnerabilities to enter in your system.
Shared memory is an efficient means of passing data between programs. Because two or more processes can use the same memory space, it has been discovered that, since shared memory is, by default, mounted as read/write
, the /run/shm
space can be easily exploited.
That translates to a weakened state of security.
If you’re unaware, shared memory can be used in an attack against a running service. Because of this, you’ll want to secure that portion of system memory.
This is me documenting my journey moving my Homelab from a Qnap NAS and a Single host Proxmox server to a Hyper-converged multi-node Proxmox Cluster.
The reason to document it here is twofold:
- Information often it scattered 'all over the place', but never 100% applicable to the setup I have.
- To remember 'what the fuck' did I do some months ago.
- Writing it for 'a public' forces me to think it all through again and make sure it's correct.
It's written 'first to scratch my own itch' but hopefully it benefits others too, or even better, that others improve upon my implementations. Feel free to comment or share improvements and insights!
Part of collection: Hyper-converged Homelab with Proxmox
Keepalived is a Loadbalancer to add ‘high availability` to Linux systemen. See the Keepalived documentatie for more background information.