Author Posts

June 2, 2015 at 1:45 pm

Hello everyone,

I've been running DSC Pull Servers for awhile now and I've noticed a new problem. When I deploy a PullServer on PowerShell Version 5 it seems to lose the ability to distribute resources. I've been using a fairly basic deployment:


WindowsFeature DSCService
{
Ensure = 'Present'
Name = 'DSC-Service'
Source = 'c:\sources\sxs'
}
xDSCWebService PullServerWebService
{
Ensure = 'Present'
EndpointName = 'PSDSCPullServer'
Port = 8080
PhysicalPath = "$env:SystemDrive\inetpub\wwwroot\PSDSCPullServer"
CertificateThumbPrint = 'AllowUnencryptedTraffic'
ModulePath = "$env:ProgramFiles\WindowsPowerShell\DSCService\Modules"
ConfigurationPath = "$env:ProgramFiles\WindowsPowerShell\DSCService\Configuration"
State = 'Started'
DependsOn = '[WindowsFeature]DSCService'
}
xDSCWebService PullServerComplianceService
{
Ensure = 'Present'
EndpointName = 'PSDSCComplianceServer'
Port = 9080
PhysicalPath = "$env:SystemDrive\inetpub\wwwroot\PSDSCComplianceServer"
CertificateThumbPrint = 'AllowUnencryptedTraffic'
State = 'Started'
IsComplianceServer = $true
DependsOn = '[xDSCWebService]PullServerWebService'
}

Anyhow, I wonder if anyone else has run into this.

No matter what the resource is if it's on the Pull Server I get the following error:

The PowerShell DSC resource C:\Program
Files\WindowsPowerShell\Modules\xComputerManagement\DscResources\MSFT_xComputer does
not contain the corresponding MOF file C:\Program Files\WindowsPowerShell\Modules\xCompu terManagement\DscResources\MSFT_xComputer\MSFT_xComputer.schema.mof

I have successfully built other pull servers and used them to deploy resources. I do have the Module Zipped with a checksum value and the version in the name.