Machine Label Not Working After Upgrade from 6.4 to 7.1 Kace Defect k1-19513
I was wondering if anyone has been able to get around the Machine Label not working since the release of 7.0. I have called Quest and have found out that the Machine label has been broken since 7.0 and will not fixed until the release of v.9.
Kace Defect K1-19513
Bottom line I am trying to restrict user downloads based on machine specs. Machines with less than 8 gigs for ram and less than a i5/i7 processor will only see one software package that generates a message that their machines does not meet the minimum system requirements. While the machines that do meet the system requirements will see another software package that will allow users to download the software.
The machine labels will work but not when applied to user downloads.
In the past I have able to assign a label to User downloads and only machines in that label can see the download. That is no longer the case since 7.0. Has anyone been able to workout a work around for this? I am looking at powershell and custom script to run on the machine to check its system specs and running different tasks in one script but I am not a powershell guru.
Any help in this would be great!
Kace Defect K1-19513
Bottom line I am trying to restrict user downloads based on machine specs. Machines with less than 8 gigs for ram and less than a i5/i7 processor will only see one software package that generates a message that their machines does not meet the minimum system requirements. While the machines that do meet the system requirements will see another software package that will allow users to download the software.
The machine labels will work but not when applied to user downloads.
In the past I have able to assign a label to User downloads and only machines in that label can see the download. That is no longer the case since 7.0. Has anyone been able to workout a work around for this? I am looking at powershell and custom script to run on the machine to check its system specs and running different tasks in one script but I am not a powershell guru.
Any help in this would be great!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Nico_K
6 years ago
unfortunately there is not much to do as a workaround. (it works with the 9.0 alpha)
Depending on what you need to know to decide the differences between machines, this may help.
Depending on what you need to know to decide the differences between machines, this may help.
For IA32 vs IA32_64 (usually called x86 against x64) you can use this snippet in a batch file:
goto %PROCESSOR_ARCHITECTURE%
:AMD64
<enter commands to run 64 bit installer here>
goto :exit
:x86
<enter commands to run 32 bit installer here>
goto :exit
:ExitComments:
-
Thanks for the help but all of our systems are 64bit. I am needing to differentiate between i3 and i5/i7. I will look into this - fharris1977 6 years ago
