Wiki source code of Lizenzen

Last modified by Jannis Klein on 2024/08/13 07:31

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	40
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
2.1	7	The licenses are entered and managed in this tab. The licenses must be assigned to a product and specified in more detail.
1.1	8
2.1	9	= Add licences =
1.1	10
2.1	11	Add a new licence via //Add// in the ribbon bar or edit an existing licence by double-clicking on the licence in the list.
1.1	12
2.1	13	In the wizard that appears, give the license a suitable name, e.g. //Windows 10 Pro//. Then enter the License ID, the number of licenses purchased and the procurement channel.
1.1	14
2.1	15	This specifies the licensing model for the respective license. You have the following choices that can be specified:
1.1	16
	17	(% style="width:1465.99px" %)
2.1	18	\|Volume\|(% style="width:1156px" %)Purchase and use of several licenses or multiple licensing.
	19	\|OEM\|(% style="width:1156px" %)Combination of hardware and software in one product, i.e. the software is already installed on the purchased machine.
	20	\|Full Packaged Product (FPP)\|(% style="width:1156px" %)Purchase of a single licence from a retailer.
	21	\|Education\|(% style="width:1156px" %)Purchase of a licence for educational institutions, e.g. schools or universities.
	22	\|System Builder\|(% style="width:1156px" %)Purchase of licenses directly for the system manufacturer.
	23	\|Leasing\|(% style="width:1156px" %)Purchase of licenses by rental rather than buying.
	24	\|Gift\|(% style="width:1156px" %)License is donated.
	25	\|Used Software\|(% style="width:1156px" %)Purchase of a license that has already been used by a previous owner.
1.1	26
	27	{{aagon.infobox}}
2.1	28	If you want to add additional Acquisition Channels to the list, you can add them in advance under //System > Settings> License Management > Acquisition Channels//.
1.1	29	{{/aagon.infobox}}
	30
2.1	31	If available, enter the licence key and serial number.
1.1	32
2.1	33	Then enter the correct licence type. Here you have the option of choosing between a full version, i.e. a fully functional software that can be used correctly according to licensing law, and Upgrade, i.e. an extension of a full version. If you have selected the latter, you must then also specify the basic licence in the next step. This option can also be used to create entire licence chains (full version - Upgrade - Upgrade from Upgrade...).
1.1	34
2.1	35	The next step is to determine the licence metric, which must match the product. As with the product metric, you can choose between Installation based, User CAL and Device CAL, which have different advanced metric properties.
1.1	36
	37	{{figure}}
2.1	38	[[image:63_LicMan_Lizenzmetrik Installationsbasiert_1306.png\|\|height="749" width="800"]]
1.1	39
	40	{{figureCaption}}
2.1	41	Licence metric Installation based
1.1	42	{{/figureCaption}}
	43	{{/figure}}
	44
2.1	45	This method of calculation takes into account the relationship between the physical machine and the virtual machine.
1.1	46
2.1	47	* Per physical device = Here, all virtual machines running on the physical device are also licensed. You can limit the number via the enter.
	48	* Per Operating System Envirnonment (OSE) = Here, several instances can run on one machine, i.e. any number of SQL Servers of one type can be installed.
	49	* Per installation = Here, a suitable licence is required for each individual instance.
1.1	50
2.1	51	The option //Secondary Usage// includes the right for a user of a licensed device to use the software on other devices.
1.1	52
	53	{{aagon.infobox}}
2.1	54	Note that a primary user must be defined for this right. You can define this via the //Client Details > Contacts > Linked Contacts// by checking the //Primary user //box.
1.1	55	{{/aagon.infobox}}
	56
2.1	57	For Server software or operating systems, it is possible to store a coefficient for the licenses via the option //License has a coefficient//. This coefficient serves as a multiplier for hardware-specific licence models. This multiplication factor can be CPU cores, for example. ACMP provides common coefficients by default.
1.1	58
	59	{{figure}}
2.1	60	[[image:63_LicMan_Lizenzmetrik Benutzer CAL_1308.png\|\|height="750" width="800"]]
1.1	61
	62	{{figureCaption}}
2.1	63	Licence metric User CAL and Device CAL
1.1	64	{{/figureCaption}}
	65	{{/figure}}
	66
2.1	67	User and Devices CALs have the same metric properties. This is relevant if the option //Consider consumer that has been added several times // is enabled in the product.
1.1	68
2.1	69	* Per consumer = Duplicate consumers are licensed.
	70	* Per accessed instance = Dual consumers are not licensed, i.e. they must be licensed individually.
1.1	71
2.1	72	Once you have decided on one of the three licence metrics and entered the correct properties, you can set additional rights for the licence in the next step.
1.1	73
2.1	74	First you can enter //Downgrades//. Use the right to downgrade to enter the products to which a downgrade can be made.
1.1	75
2.1	76	Then you can transfer to //New version right//. This right includes the right to receive free updates or upgrades to a new version of the software under a maintenance contract that Microsoft offers with Software Assurance. You can therefore use this date field to specify when the maintenance contract for the licence expires.
1.1	77
	78	{{aagon.infobox}}
2.1	79	If ACMP DNA2 is used and a newer version with a matching release date is found within the runtime, you can see from the product and licence status that the licence can be moved.
1.1	80	{{/aagon.infobox}}
	81
2.1	82	//Reassignment is restricted// allows you to specify whether and when a licence can be reassigned. I.e. the license may only be reassigned after X days after uninstalling.
1.1	83
	84	{{aagon.infobox}}
2.1	85	This right is optional and has no effect on the licence calculations.
1.1	86	{{/aagon.infobox}}
	87
2.1	88	You can use //Has expiration date// to set whether the license is a limited use permit for a certain period of time or when it ends. In addition, you can set here how many days before the expiration date the license should appear in the Dashboard as a warning. This allows you to renew the license before it expires.
1.1	89
2.1	90	In the next step, you can optionally enter master data of the contractual partners as well as information about the finances on the following pages.
1.1	91
2.1	92	Lastly, you have the option to add custom fields for a query here as well, as well as attaching any associated contract documents to the license.
1.1	93
2.1	94	= Apply coefficients =
1.1	95
2.1	96	You can enter a coefficient for a license and thus influence the licence calculation. A coefficient serves as a multiplier for hardware-specific licence models. These multiplication factors can be CPU cores or cores, for example.
1.1	97
2.1	98	ACMP provides some common coefficients by default.
1.1	99
	100	{{figure}}
	101	[[image:63_LicMan_Koeffizient_1147.png\|\|height="590" width="830"]]
	102
	103	{{figureCaption}}
2.1	104	Apply licence coefficient
1.1	105	{{/figureCaption}}
	106	{{/figure}}
	107
2.1	108	When adding licenses, you can use an existing coefficient or create a new coefficient in the ribbon bar via //Coefficient//.
1.1	109
2.1	110	== Create a coefficients ==
1.1	111
2.1	112	Click on// Add Coefficient//.
1.1	113
	114	{{figure}}
	115	[[image:63_LicMan_Koeffizient erstellen_1481.png\|\|height="597" width="825"]]
	116
	117	{{figureCaption}}
2.1	118	Create your own coefficients
1.1	119	{{/figureCaption}}
	120	{{/figure}}
	121
2.1	122	In the upper area there is an input/display field. Here you can enter the formula for the coefficients manually. You can also include the functions below in your formula. To do this, you can use basic mathematical functions. You can add max, min, round up, round down and an if statement to the mathematical operators.
1.1	123
2.1	124	To check that the results are correct before saving the licence coefficient, it is advisable to select a Client in the right-hand area. This gives access to a query. The variables are automatically filled in based on the stock data and used in the test calculation accordingly. When you have calculated all the necessary elements, click on //Test//. You will now see the results of the coefficients. Any errors in the calculation are displayed in the message window.
1.1	125
2.1	126	If the result is as expected and there are no errors in the calculation, you can leave the creation of the coefficients by clicking on //Done//.
1.1	127
2.1	128	== Understanding the syntax for calculating coefficients ==
1.1	129
2.1	130	It is possible to combine the individual elements.
1.1	131
	132	{{aagon.infobox}}
2.1	133	Note that when entering decimal numbers, you use a dot as the decimal separator!
1.1	134	{{/aagon.infobox}}
	135
	136	=== Syntax If ===
	137
2.1	138	With the If statement, you can specify a condition for which a certain action is to be carried out.
1.1	139
2.1	140	If (Condition, Then, Otherwise)
1.1	141
	142	=== Syntax Max ===
	143
2.1	144	With this command you can determine the largest numerical values of the entered values / variables. There is no limit to the values / variables.
1.1	145
2.1	146	Max (Value1, Value2, Value3, ...)
1.1	147
	148	=== Syntax Min ===
	149
2.1	150	With this command you can determine the smallest numerical values of the entered values / variables. A limitation of the values / variables is not provided.
1.1	151
2.1	152	Min (Value1, Value2, Value3, ...)
1.1	153
2.1	154	=== Syntax Round up ===
1.1	155
2.1	156	With this command you can round up the entered number.
1.1	157
2.1	158	RoundUp (value, number of digits)
1.1	159
2.1	160	=== Syntax RoundDown ===
1.1	161
	162
2.1	163	With this command you can round off the entered number.
1.1	164
2.1	165	RoundDown (value, number of digits)