Normally, the best places to look at the results are the log files. I want to show the result of the deployment of the new Client Settings. In this case it would be easy to just show a good result of the deployment of the Configuration Baseline, but I want to show some more. Select the new policy and on the Home tab, in the Client Settings group, select Deploy.Īs always, now it’s time to take a look at the result.On the Computer Agent page, select next to PowerShell execution policy Bypass and click Ok.On the General page, fill in with Name and select Computer Agent.On the Home tab, in the Create group, select Create Custom Client Device Settings and the Create Custom Client Device Settings –popup will show.In the Configuration Manager Console navigate to Administration > Overview > Client Settings.The easiest way to configure this, for the Configuration Baseline, is to follow the next steps: All Signed (default in ConfigMgr 2012 SP1):The ConfigMgr client runs scripts only if they are signed by a trusted publisher and applies independently from the current PowerShell configuration on the local system.Restricted (default in ConfigMgr 2012): The ConfigMgr client uses the current PowerShell configuration on the local system, which determines whether, or not, unsigned scripts can run.Bypass: The ConfigMgr client bypasses the PowerShell configuration on the local system so that unsigned scripts can run.The only pitfall in here is that it means something different then someone might think. In the Client Settings, under Computer Agent, there is an option to configure the PowerShell execution policy. So just let the ConfigMgr client “manage it” and then the solution is actually very simple. In most cases it’s not possible, or allowed, to change the execution policy for PowerShell on the system. The deployment of the baseline resulted in error 0x87D00327, which translates to ‘Script is not signed’ (see picture). That baseline is completely based on one Configuration Item, which consists of eight script setting types and those scripts are all written in PowerShell. During that I was working with the Configuration Baseline of UE-V. In between I was still doing some work and trying to find a subject for a presentation/ demo.
This week my post will still be a small one, as my time is still limited during the move to our new home.