just wanted to supply an update while playing with the linked program on Windows 11: if you open up the .cmd file and look around line 362 you'll see the following: Code: (new BigInteger(2) << 18) | if you modify the number in parentheses next to "BigInteger" (in this case it's 2), this is enough to modify the generated key packs to allow multiple installs from the tool. Let's say you installed 35 CALs today and next month you install 71 more, without changing this number the licensing wizard will complain that the key pack is "already installed" even though the generated key looks different. how it works: encoded in the terminal services license key pack ID is a 14-bit field that contains the "program selector" (Volume, Select, Open, etc.) and thus within my testing of oddball numbers (3, 5, 19, 77) in addition to more sensible values (like 4, 6, 18, 32, 64) it seems to not care so long as the value can be encoded into 14 bits. reserved (bits 0–2): 0 minorVer (interpreted): 0 The other fields in the 35-character response codes for CAL key pack IDs include among other things: * Reserved fields (bits 0-2) * CHID (bits 46+) (specifies the numeric representation of the CAL type (per-device, per-user, VDI, etc.) * count (bits 32-45) (number of CALs) * program (bits 18-31) (this is the one we're interested in for uniqueness) * platform (bits 10-17) * version (bits 3-9) (the version of the terminal server licensing service (e.g. Windows 2000 is 5.0, 2003/R2 is 5.1, 2008/R2 is 6.0) A lot of this analysis came from AI Assist rather than me fooling around. I am thinking of modifying the line by defining a variable closer to the top then passing that variable in the parens thus you don't have to go spelunking for it. but it would be nice to see that field represented in the GUI some day.