Skip to content

Add known troubleshooting case for Pull Server #4250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 2, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Add known troubleshooting case for Pull Server
where the certificate common name is different than the DNS name.  
fyi @Austinm2559
  • Loading branch information
mgreenegit authored May 2, 2019
commit 874f26f20a3b6140ef0d904b6bb9cc3a0c46752d
17 changes: 17 additions & 0 deletions dsc/troubleshooting/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -707,6 +707,23 @@ onlyProperty PSComputerName
14 localhost
```

## DSC returns "unexpected response code InternalServerError" when registering with Windows Pull Server

When applying a metaconfiguration to a server to register it with an instance of Windows Pull Server,
you might encounter the following error.

```PowerShell
Registration of the Dsc Agent with the server https://<serverfqdn>:8080/PSDSCPullServer.svc failed. The underlying error is: The attempt to register Dsc Agent with AgentId <ID> with the server
https://<serverfqdn>:8080/PSDSCPullServer.svc/Nodes(AgentId='<ID>') returned unexpected response code InternalServerError. .
+ CategoryInfo : InvalidResult: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : RegisterDscAgentUnsuccessful,Microsoft.PowerShell.DesiredStateConfiguration.Commands.RegisterDscAgentCommand
+ PSComputerName : <computername>
```

This can occur when the certificate used on the server to encrypt traffic has a common name (CN)
that is different than the DNS name used by the node to resolve the URL.
Update the Windows Pull Server instance to use a certificate with a corrected name.

## See Also

### Concepts
Expand Down