topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Saturday May 18, 2024, 1:19 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Recent Posts

Pages: prev1 2 3 4 [5] 6 7 8 9 10next
41
Hey there,

I've been using 2.1.0 beta 67 today and I've run into a kinda new issue.

With previous versions it already happened from time to time that, while launching a command with a button, I'd get the attached error message. It was not a very common occurrence and the command ran anyway with no other issue, so I didn't mind much.
What's new with this latest beta is that, after running into that error, now I can't seem to interact with the Variable field any more. I can open the drop-down list (which appears to be empty while it shouldn't be) but can't get the blinking cursor to appear inside the field itself, or select the current value by double clicking it, or even replace it by selecting a favorite… seems the only way out is to exit CRAP and restart it.
-ConstanceJill (May 10, 2024, 11:43 AM)

I think I have traced to how the history works so I don't think it is command related at all in the end based on the translation of that message. So I should be able to fix.

Edit: Thanks for reporting it. Pretty sure I have tracked the issue down now to fix.
42
I can't tell for sure but I think so far I mostly had it happen with the ping command, which happens to be the first in my layout (in case that's relevant).
-ConstanceJill (May 10, 2024, 04:42 PM)
Okay I will see if I can track the mystery down before I request more info.
43
I can't tell for sure but I think so far I mostly had it happen with the ping command, which happens to be the first in my layout (in case that's relevant).
44
Hey there,

I've been using 2.1.0 beta 67 today and I've run into a kinda new issue.

With previous versions it already happened from time to time that, while launching a command with a button, I'd get the attached error message. It was not a very common occurrence and the command ran anyway with no other issue, so I didn't mind much.
What's new with this latest beta is that, after running into that error, now I can't seem to interact with the Variable field any more. I can open the drop-down list (which appears to be empty while it shouldn't be) but can't get the blinking cursor to appear inside the field itself, or select the current value by double clicking it, or even replace it by selecting a favorite… seems the only way out is to exit CRAP and restart it.
-ConstanceJill (May 10, 2024, 11:43 AM)

Same command each time or different? If same might have to investigate that command myself if possible to debug.
45
Hello all,

I'm updating this entire thread for brevity, as I've been researching this situation and I've learned a few things. 

- The Detection Script will check for a condition, in my case if a MAK license is installed on a device (a laptop). No output is required other than the value of 0 for an unlicensed device.
- If a license is not detected, it should output that value which should in turn refer this device to the Remediation Script (if refer is the right word)
- The Remediation Script should then activate the device with a valid MAK license using slmgr.
- I've added 5 pilot devices to a group in Intune to test.

Questions - What conditions must be present for this custom script to run and activate the device?
- Is any kind of credential required to run the script?
- How is the script run, would it be when the device is restarted or should it run on some kind of schedule?

And more importantly:
- Must the device be joined to Azure AD before the script will run against it?     
      - These are workgroup devices that have not been joined to the on-prem AD.
      - They have been onboarded to Intune.

The Detection script is simple:

$license = get-ciminstance softwarelicensingproduct | where-object {$_.PartialProductKey}
# check if the license object is a MAK license
if ($license.description -like "*MAK*") {
    # if it is a MAK license, exit with error code 1
 exit 1
} else {
    # if it is not a MAK license, exit with error code 0
 exit 0
}

Thanks in advance.
46
Hey there,

I've been using 2.1.0 beta 67 today and I've run into a kinda new issue.

With previous versions it already happened from time to time that, while launching a command with a button, I'd get the attached error message. It was not a very common occurrence and the command ran anyway with no other issue, so I didn't mind much.
What's new with this latest beta is that, after running into that error, now I can't seem to interact with the Variable field any more. I can open the drop-down list (which appears to be empty while it shouldn't be) but can't get the blinking cursor to appear inside the field itself, or select the current value by double clicking it, or even replace it by selecting a favorite… seems the only way out is to exit CRAP and restart it.
47
DC Gamer Club / Re: Latest Game Giveaway
« Last post by Deozaan on May 10, 2024, 12:24 AM »
If you have a subscription to Amazon Prime then the following games can all be redeemed on GOG through Amazon Prime Gaming:


https://gaming.amazon.com/
48
2.1.0 build 67 BETA BUILD is on the beta page for download.

What's New/Modifications
Each layout file now has a layout configuration section where each option only applies to that layout file.
When loading a large width/height image file for the icon it should now ask if you want to save a copy at a smaller size to use.
Added the ability to shorten the title bar down a little.
More bug fixes and optimizations.
Further theme fixes.

I also ended up adding one last feature to this beta...

Added not one but two new prefix/suffix macros as follows:
<login:user> and <login:pass> which will pop a dialog asking for them right before the launch happens.
Please note that the value will not show in the launch confirm window for more security.

As always let me know if bugs are found no matter how BIG or small of a bug it may be.
Also let me know your thoughts/feedback on this program/build in general even if no bugs are found...
49
I'm wondering if having it hide as long as no button uses the variable may be confusing for new users that didn't read about the feature first, especially if it's hidden when they start a new layout (which by default would be empty), or if they just start by making one such button and then the field disappears.

Maybe having it just be a toggleable option for each layout would keep it more simple (also when it comes to maintaining the code, even though I guess that's not for me to worry about).
-ConstanceJill (May 07, 2024, 02:31 AM)

Here is what I did currently for a toggleable option. I changed up the layout management dropdown a tiny bit to accommodate for a layout config section by moving switch layouts into a sub menu of it. Then I added a variable bar preference of "On, Off, Auto" with "On" being the default setting to the new layout config submenu in the layout management dropdown. Since the layout listing was dynamic menu items it was easier to have those in a submenu. Then I switched the other portion of layout management to be created at design time which the layouts config needed to already be in place. Also the variable bar options also have a tooltip explaining each if hovered. This should allow for expanding with more layout specific settings should the need/want arise.
50
I'm wondering if having it hide as long as no button uses the variable may be confusing for new users that didn't read about the feature first, especially if it's hidden when they start a new layout (which by default would be empty), or if they just start by making one such button and then the field disappears.

Maybe having it just be a toggleable option for each layout would keep it more simple (also when it comes to maintaining the code, even though I guess that's not for me to worry about).
Pages: prev1 2 3 4 [5] 6 7 8 9 10next