Add Laptop / Desktop Condition To Deployments
It would be great if you could add a check in conditions for Laptops / Desktops.
Example: If its a laptop run if not don't.
0
Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.
It would be great if you could add a check in conditions for Laptops / Desktops.
Example: If its a laptop run if not don't.
Comments
You could do this with an Inventory Collection, and then just deploy to the correct Collection.
Very true but in this case I'm building a package with a lot of nested packages for new PC builds and having that option would be nice
You could build a step that saves the Chassis Type into the registry and read that value in the next step.
Interesting idea! Does the new ChassisType value need to be in inventory or does the condition run on the fly on the target?
His code will run on the fly on the target. The only issue will be that the registry is tainted with the key that gets created, but it is of little worry. Nothing about it is harmful to the system. And, once you have that set, you could do cool things with Registry scanners in Inventory to separate things out based on Chassis type. It's a very cool trick.
Tested it on a target and I think it will work for what i'm doing.
Thanks gents!
I wanted to update you on something I've found. You can write that to the registry but it disappears after a reboot.
Just an FYI
Sounds like something is preventing the registry change from staying. Maybe A/V? Or a GPO?
I just tested it on a new Windows 10 build with no software and not joined to the domain and it disappears after boot.
For what i'm doing that's fine. Again I just wanted to share how it is behaving.
i never know the use of adobe shadow until i saw this post. thank you for this! this is very helpful. Translate Good Evening to Russian