
Verify that the service on the destination is running and is accepting requests.Ĭonsult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.

The client cannot connect to the destination specified in the request. If I push a DSC config without configuring WSMan, I hit a wall and get this message: There’s a myth about PSRemoting that was uncovered by PowerShell Magazine and Windows PowerShell MVP Aleksandar Nikolic: To configure Windows Updates settings, some registry keys, services,… DSC (Desired State Configuration) is the way to go as it’ll ensure the PC remains compliant even if there’s a drift later between 2 resets or/and the PC isn’t connected to any network.Īs you may know DSC depends on WSMan and not on PSRemoting.

When the PC is provisionned or reset, the PBR image is applied/expanded to the C: drive and the post-install script is run at the end of the OOBE (Out-of-Box Experience) phase, just before the user can logon. These laptops will run Windows 8.1 and the PBR image is actually a sysprep image that is configured to run a post-install script.

I’ve been working on a deployment scenario where I’ll provision new computers from a PBR (Push Button Reset) image.
