We currently have a defect open for this. Defect ID is 147401. This is set to be addressed in our next defect sprint which should place it in July or Augusts component patch. Please let me know if you have any questions.
Hi yes - i believe it was me that raised that Defect - we have a call open and are awaiting the patch.
Your Avatar is making the exact same face I made when I discovered that you said that PS is not working over http.
I have the same problem with my powershell packaging.
Do you have any solutions ?
I confirmed, with our TAM, that the fix is going either to SP3 or to load 9.6.x. We will begin our migration to 9.6 in Q2 or 2015 so we are just using UNC to deploy PowerShell builds. All of our PS builds are for servers or configuring them so that is not a serious problem. It would be if we had to deploy to any of the 220 plus branches since they all use HTTP to deliver their files.
I think waiting will be better than to set testing and migration of a new core back 3 months. Besides, there is always something that does not do what you either hoped or expected. If this is the only thing I find it is certainly the best release of LANDesk that we have fielded.
Thank you so much for responding to my message.
I also tried with a UNC path but it does not work.
I just send you my log files if you have some idea.
I am assuming that your PS script is running OK from the machine (without LANDesk). I might point out also that it is important to remove restrictions to PS before attempting to execute the bulk of your code. They added a feature to do this automatically into LANDesk with release 9.50, however I still found it necessary to run our own. Perhaps it was due to security on our Group Policy, dunno. Microsoft covers restrictions rather well here http://technet.microsoft.com/en-us/library/ee176961.aspx . I am also going to assume that other UNC deployments are all working fine in your build (BTW we are on SP2 of 9.50 - with the 2014-0625 loaded for BASE and RC). That could indeed make the difference.