|
|
|||||||
On Server 2019, @PRODUCTTYPE reports the server as Windows Server 2016 Also would be useful if when checking Windows 10, it returned more useful information like 1909 or 21H1. |
||||||||
|
|
|||||||
Thanks for the report. Not sure if Ruud will be doing any more updates at this point or not |
||||||||
|
|
|||||||
*BUMP* Windows 11 is detected as Windows 10. So, is anyone else (besides me) still using Kix for Logon Scripts or are folks moving to Powershell? I am getting pressure to move away from Kix but doing so is a major under-taking that I ... 1) Don't have time to do; and 2) Don't want to do (to be quite honest) |
||||||||
|
|
|||||||
I sent an email to Ruud. Hoping he will respond or show up here in the forums. |
||||||||
|
|
|||||||
I don't remember the key off hand, but fairly certain you can get OS info using registry reads as well. This removes the dependency on the built-in macro being updated. |
||||||||
|
|
|||||||
http://www.kixtart.org/forums/ubbthreads.php?ubb=showflat&Number=213202 |
||||||||
|
|
|||||||
Ruud responded to my email and says that as time allows, he plans to update Kixtart. |
||||||||
|
|
|||||||
Cool to hear he's still doing updates after all these years |
||||||||
|
|
|||||||
Just to be sure you have all seen this.... here's a link to a test-version of 4.69: KiXtart 4.69 This version recognizes Windows 11, Windows Server 2019, 2022 (and the builds in between) and it also features 2 new macros: @RELEASEID (eg: 1909, 2003, etc) @RELEASENAME eg: 21H2) If nothing unexpected comes up, I'll share a final build shortly. |
||||||||
|
|
|||||||
Hello, Thank you Rudd for still providing updates to KiXtart, which I have been using for almost 2 decades. I really think there is still use for this awesome program, when you don't want to mess with Powershell and GPOs. By the way, wouldn't putting KiXtart to github be an opportunity to make this project live on? |
||||||||
|
|
|||||||
Ruud - we have Kix-based apps running on over 90-K endpoints. The ReleaseId/Name macros will be very useful. I'll see what I can do to test 4.69. Thanks for your continued support!! FYI - We still experience issues with scripts tokenized on an earlier version reporting strange errors when executed on newer versions. This error is often something like "invalid method/function call: missing comma!" referencing a source line that is blank or in the middle of a series of comments. This does not occur with small or simple scripts, but our source code often exceeds 10,000 lines with up to 150 UDFs referenced. Happy to share an example privately if that will help Glenn |