So the answer to your question is 'Sort of'. The issue here is that the provisioning agent is a 32 bit app so running as 'Execute File' occurs in the 32 bit subsystem. My current solution for this in LDMS9.5.1 is to use software distribution action item and have the batch file package execute in 64 Bit mode on a 64 Bit OS. My problem in LDMS9.6.2 is that the new V9.6 agent uses the default task config which we need to inform End User of 'Success/Failure', this causes the provisioning task to hang till User acknowledges success.
↧