|
Post by supalynnz on Jun 12, 2018 14:21:48 GMT
Hi Guys First post and somewhat new to tinkering with UI++ Firstly I'd like to say we do have a working UI++ within our PE TS that works fine. I have created a pre-flight xml to use before we upgrade machines to Win 10 1709, which in preliminary testing was working fine. For some reason though now the UI++ will not appear when the TS tries to load it. The task sequence will then sit at 'installing'. Looking at the logs all seems fine and at first I thought it was hanging, but now it seems that the UI++ is running on the test machine and appears to be waiting for user input, but annoyingly the window never appears despite the program running in Task manager. If I kill the UI process the Task Sequence fails (which is correct as I have continue on error unticked) Anyone seen this before...the UI++ program running but no GUI is presented? I have tried creating numerous new packages and also downloaded a fresh set of programs from your website. Also if I manually run the program on the test machine the program and xml work flawlessly, even if i use the content cached by the TS. Pulling my hair out
|
|
|
Post by robertlth on Jun 12, 2018 16:52:54 GMT
If you take a look at C:\windows\temp\ui++.log you should get a clue about what is wrong.
Without the actual XML-file i can not see whats wrong but it sounds like the XML-file can not be found or has some validation error.
|
|
|
Post by supalynnz on Jun 12, 2018 17:57:51 GMT
Hi Robert
Thanks for that, I don't think the xml is the issue because if I manually launch the program it runs the xml fine. I have got around this issue for the moment by added the ServiceUI.exe to my package and amending the TS command to launch UI++ that way, again using the same xml.But we definitely had it working without it before. The UI++ log did not error it merely paused whilst it waited for interaction. It only errors after I killed the UI process in Task Manager.
|
|
|
Post by RJ on May 31, 2019 13:33:41 GMT
We have the same issue, did you ever find a solution?
|
|
|
Post by Jason on May 31, 2019 19:46:10 GMT
The solution is as described -- you need to use ServiceUI (from MDT) to inject the window onto the session 1 desktop. Basically, since the TS runs as local System, any UI displayed by anything that it runs will show on the session 0 desktop. This is a hidden desktop that cannot be directly interacted with. ServiceUI has the (sneaky, security boundary breaking) ability to "move" the UI of any process to the session 1 desktop so that it can be interacted with. This is not in any way specific to UI++.
|
|