it looks like the 3.1.0 beta (14/11 edition) is causing a problem on XP. the execution of the powershell.exe is being looped causing the cmd box to open briefly, next I see in the title bar that jumps to an administrative cmd box (Administrator: c:\windows\system32\WindowsPowerShell\v1.0\powershell.exe )
The first 30s this loops so fast that it is not possible to read this, but if you wat a while the loop slows down, but it does continue the whole time. Which is logical I guess as taskmanager is keeping a "ServiceUIx86.exe" process and a "Powershell.exe" process in memory for each of those popups!
I'm running this on a XP SP3 x86 with the mandatory Powershell 2.0 patch installed. previous versions worked fine but I get this now 3 different machines.
Closing one of the cmd boxes with the X button causes the intial Welcome screen to popup though! (all other processes stay in memory also)
AppDeployToolkitStartup.log reports:
OS Architecture : x86
Process Arch : x86
Running under SYSTEM context : True
Running under Session 0 : True
ServiceUI; x86
thanks for looking into this.
Comments: Sorry Maarten, almost missed your question :) We thought we had ServiceUI nailed but we kept hitting problems once we went into production environments. Worse still, we ended up causing a bunch of problems in 3.0.8 trying to reverse out all of the ServiceUI changes. We've prided ourselves on getting to be a really stable toolkit that works well in an enterprise environment. So we're very sorry for the shoddiness of 3.0.8 and have taken a number of steps (a QA process and test scripts) to ensure we don't have these issues going forward. So to answer your question, we're going to scrap ServiceUI completely (feel free to use it directly but it won't be integrated into the Toolkit) and we're doubling down on fixing bugs rather than introducing new features at the moment. Dan
The first 30s this loops so fast that it is not possible to read this, but if you wat a while the loop slows down, but it does continue the whole time. Which is logical I guess as taskmanager is keeping a "ServiceUIx86.exe" process and a "Powershell.exe" process in memory for each of those popups!
I'm running this on a XP SP3 x86 with the mandatory Powershell 2.0 patch installed. previous versions worked fine but I get this now 3 different machines.
Closing one of the cmd boxes with the X button causes the intial Welcome screen to popup though! (all other processes stay in memory also)
AppDeployToolkitStartup.log reports:
OS Architecture : x86
Process Arch : x86
Running under SYSTEM context : True
Running under Session 0 : True
ServiceUI; x86
thanks for looking into this.
Comments: Sorry Maarten, almost missed your question :) We thought we had ServiceUI nailed but we kept hitting problems once we went into production environments. Worse still, we ended up causing a bunch of problems in 3.0.8 trying to reverse out all of the ServiceUI changes. We've prided ourselves on getting to be a really stable toolkit that works well in an enterprise environment. So we're very sorry for the shoddiness of 3.0.8 and have taken a number of steps (a QA process and test scripts) to ensure we don't have these issues going forward. So to answer your question, we're going to scrap ServiceUI completely (feel free to use it directly but it won't be integrated into the Toolkit) and we're doubling down on fixing bugs rather than introducing new features at the moment. Dan