-
Notifications
You must be signed in to change notification settings - Fork 80
Computer: Error: MSFT_Computer.psm1 is not digitally signed #199
Description
Details of the scenario you tried and the problem that is occurring
Currently I'm using an ARM Template to create new Windows 10 virtual machines in Azure and added the PowerShell DSC extensio so that I can configure the newly created Windows 10 machine properly. This configuration requires to join the computer to the domain.
The compilation of the DSC configuration fails with the following error:
[2018-11-14 11:18:36Z] [ERROR] Importing module MSFT_Computer failed with error - File C:\Program Files\WindowsPowerShell\Modules\ComputerManagementDsc\DscResources\MSFT_Computer\MSFT_Computer.psm1 cannot be loaded. The file C:\Program Files\WindowsPowerShell\Modules\ComputerManagementDsc\DscResources\MSFT_Computer\MSFT_Computer.psm1 is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
Verbose logs showing the problem
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Computer DomainJoin
{
Name = $env:ComputerName
DomainName = $domainName
Credential = $AdminCredential
}The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise N
OsOperatingSystemSKU : WindowsEnterprise
OsArchitecture : 64-bit
WindowsVersion : 1709
WindowsBuildLabEx : 16299.637.amd64fre.rs3_release_svc.180808-1748
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
Name Value
PSVersion 5.1.16299.666
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.16299.666
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
2.22.0.0