Open qewade0701 opened 4 years ago
It looks like you've not added PowerShell to your boot image. Could you please verify if it's added?
Thanks. PowerShell was not in the boot image.
From: Nickolaj Andersen notifications@github.com Sent: Monday, May 18, 2020 3:50 PM To: MSEndpointMgr/ConfigMgr ConfigMgr@noreply.github.com Cc: Wade, Quinn QWade@mmsd.com; Author author@noreply.github.com Subject: [EXT] Re: [MSEndpointMgr/ConfigMgr] TS Error Received trying to run the PS Invoke-CMApplyDriverPackage Script (#232)
It looks like you've not added PowerShell to your boot image. Could you please verify if it's added?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/MSEndpointMgr/ConfigMgr/issues/232#issuecomment-630427818, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO7GIQYXYMWVVIIQ5DLFA7LRSGNPJANCNFSM4NEMH6EQ.
After adding the PS components the initial was resolved. Thanks. The retry of the TS step resulted in the following. What could I be missing?
Check the ApplyDriverPackage.log file for the real error.
Thanks again for your reply Nickolaj. Really appreciate your responses. The ApplyDriverPackage.log states a successful connection. I wonder if this is my user error :). The pkg I am currently using is a Pilot pkg. The log mentions an operational mode of 'Production'. Is this just a matter of switching the pkg to Production?
Have you added the service account used o the application pool in IIS in ConfigMgr and given it read only permissions?
Yes. The service acct is in ConfigMgr as a read-only analyst
Have you created any packages with DAT?
Yes. The tool has been working fine creating and distributing the initial (Pilot) pkgs.
I did just move one of those Pilot pkgs to Prod. I haven't tested just yet that outcome.
Please see the attached for the error received during the driver step. Any thoughts would be greatly appreciated.