Sadly It isn't. When I start the exe manually, just from the cmd, it isn't working either, it shows, but I can't connect from the MDT workbench, only the first time.
This couldn't be because of all the new versions, including MDOP? You're saying it only starts remoterecovery and reads inv32.xml, also the first time? The xml is created once and should be available every re-start? Where would that xml be? I'll have to check tomorrow -R From: [email protected] [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Donnerstag, 3. September 2015 12:16 To: [email protected] Subject: RE: [mssms] Eventservice (Dart) in customsettings.ini, ztigather.wsf I don't see any reason why it wouldn't work on subsequent boots. The logic itself to start remoterecovery.exe and then to read the resulting inv32.xml file that it generates with the important information is all contained in the LiteTouch.wsf script itself, just confirm that is executing on the second boot (I think the EnableDART function should be called any time the machine boots into Windows PE). Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Thursday, September 3, 2015 9:08 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] Eventservice (Dart) in customsettings.ini, ztigather.wsf Bump? I figured just starting remoterecovery.exe isn't enough, it's missing all the data handled by ztigather.wsf. Currently I only see to change ztigather.wsf to ignore if there is already a value, letting it process again. Maybe that also requires changes to the xml. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 2. September 2015 12:46 To: [email protected] <mailto:[email protected]> Subject: [mssms] Eventservice (Dart) in customsettings.ini CM2012 R2 SP1 CU1, ADK 10, MDT 2013 Update 1: I have the eventservice defined in the customsettings.ini in the default section, all working. But then I need a reboot into PE again (due bios configuration), so I let gather run again with the same settings, but the log isn't showing processing eventservice, hence the monitoring window wouldn't show. I guess that's because it is only started when that variable is defined the first time, and after a reboot in PE again, it is ignored, right? Can I get that to start again anyway somehow? -Roland
