|
Post by Jason on Jun 4, 2019 15:22:30 GMT
That's a typo in the documentation. XML is case-sensitive so it does matter and should be PkgID (capital I and D).
Also, per your log above, "Make sure the application is marked for dynamic app install". That means any applications and packages that you reference must have the option set to allow installation without being deployed.
|
|
|
Post by Jason on Jun 5, 2019 19:36:03 GMT
👍👍
|
|
|
Post by jawman on Jun 11, 2019 21:29:07 GMT
Looking at the documentation again, I see that "Label" is actually the program name. If that's the case, then what should "ProgramName" be? I just made sure that the value for Label and ProgramName were the same and the apps installed during the OSD task sequence. This UI is very slick. Jake, see u are doing what I need to do, and im a little stuck. I have created my xml file now how do I call it in my TS ? can I test the XML file 1st ? without adding to the TS Thanks JAWMAN
|
|
|
Post by Jason on Jun 15, 2019 22:22:54 GMT
Yes, UI++ runs fine outside of a task sequence. Just run it like any other application and validate that the task sequence variables that you are expecting to be created are using the log.
If your xml configuration file is named ui++.xml and is in the same directory as the UI++ exe, then UI++ will automatically load it. To specify an alternate file or a file in an alternate location, use the /config parameter on the command-line.
|
|