|
|
Post by thedude on Jun 11, 2019 19:35:40 GMT
Hello,
I am looking to have a zero touch task sequence that applies particular applications with no interaction based on the queried and found OSDComputerName according to another task in the TS. Not sure how to write to the XApplications list without interacting with the UI++ popup.
Thanks,
|
|
|
|
Post by Jason on Jun 15, 2019 22:26:53 GMT
That really has nothing to do with UI++. You simply need to populate a series of task sequence variables named myApps01, myApps02, myApps03, ... or whatever variable you choose, with the name of the applications you wish to install.
You can do this in UI++ with a series of TSVar actions that have conditions attached to them based on the computer name of the system. You can also use a Switch action as well.
Keep in mind that the OSDComputerName variable is **not** populated by the task sequence engine though so unless you are populating first, its value will be blank.
|
|
|
|
Post by thedude on Jul 22, 2019 15:21:35 GMT
Hi Jason!
Thanks for the reply and apologies for the lateness in mine. The notification landed in junk of course! Argh!
This was actually a dumb question as I sat and thought of it more and I meant to dump it/delete it. But regardless thanks. I ended up assigning applications to the collections instead via variables to bypass the touch during imaging.
But on a related, similar note, can a secondary app list be used when an initial dialog box appears querying information? And based on that, a secondary app list in the one XML be used? This feels a big fat NO.
Dude
|
|
|
|
Post by Jason on Jul 26, 2019 3:15:53 GMT
Without knowing or seeing exactly what you intend, I can't say for sure, but if I'm following what you are asking, then the answer is yes. You can create as many TS variable lists as you need -- they of course will each need to have different base variables though.
|
|
|
|
Post by thedude on Jul 29, 2019 17:28:53 GMT
The idea is an initial popup appears indicating the OSDCOMPUTERNAME field as gathered via MDT and a checkbox is below this field for an option. If this option is checked, then the app list that is presented shows according to that checkbox.
Example: there is a "normal app list" and a "secondary app list". And both lists are contained in a single XML. The "secondary app list" ONLY appears if the checkbox is checked on the initial dialog box.
The only part I am unsure about is regarding using a single XML for ALL of this rather than two separate XMLs: one that contains the secondary app list and that appears as an additional step in the task sequenced that detects the true or false result of that checkbox option.
I have this working using an additional step and the task sequence variable true or false setting but would prefer, if possible, to have all of this one single step and one single XML.
|
|
|
|
Post by thedude on Jul 30, 2019 12:54:22 GMT
I figured this out using conditions within the XML in the Action's initial dialog area. Example: Checkbox variable creation/use: <CheckboxInput Variable="KIOSK" Question="Check box if this a Kiosk Deployment" CheckedValue="True" UncheckedValue="False" Default="False"/> Use Conditional item/variable in Apptree: <Action Type="AppTree" Title="Please choose your software" Expanded="False" Size="Tall" ShowBack="True" ShowCancel="True" Condition='"%KIOSK%" = "False"'> This conditional usage is covered in section 8.2 of the manual for UI++. Though not specifically stated that conditionals can be created and then re-used on the fly, it is clear that this is possible and the default XML with UI++ exhibits this possibility. I just kept getting the syntax wrong: had the percent signs in the wrong spot. |
|
