Hi,
I have it set to run directly from the DP on fast connections and as cached on slow ones. I get the same warning message in the logs re UNC paths on successful installations as well. Additionally there is no correlation between failed vs successul installations running in cached vs direct mode. When I remote onto failed installations and run it manually, I'm running it from the DP and not downloading it locally first. So far, none have failed doing it that way.
I'm going to look at abandoning the Cisco script and just putting Execute-MSI into the toolkit script as per your method. Thinking about it, the .cmd from Cisco is doing the same checks for version and chassis detection that I'm already doing using SCCM collections, so I'm duplicating it by continuing to use the Cisco script.
Many thanks for the suggestions and pointers, just curious as why I'm getting this small percentage of failures.
I have it set to run directly from the DP on fast connections and as cached on slow ones. I get the same warning message in the logs re UNC paths on successful installations as well. Additionally there is no correlation between failed vs successul installations running in cached vs direct mode. When I remote onto failed installations and run it manually, I'm running it from the DP and not downloading it locally first. So far, none have failed doing it that way.
I'm going to look at abandoning the Cisco script and just putting Execute-MSI into the toolkit script as per your method. Thinking about it, the .cmd from Cisco is doing the same checks for version and chassis detection that I'm already doing using SCCM collections, so I'm duplicating it by continuing to use the Cisco script.
Many thanks for the suggestions and pointers, just curious as why I'm getting this small percentage of failures.