Skip to content

Updating Pull Server info #2300

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.

Sign up for GitHub

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
Apr 5, 2018
Merged

Updating Pull Server info #2300

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 6 additions & 2 deletions dsc/pullClient.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,17 @@ ms.topic: conceptual
keywords: dsc,powershell,configuration,setup
title: Setting up a DSC pull client
---

# Setting up a DSC pull client

> Applies To: Windows PowerShell 4.0, Windows PowerShell 5.0

Each target node has to be told to use pull mode and given the URL or file location where it can contact the pull server to get configurations and resources, and where it should send report data.
> [!IMPORTANT]
> The Pull Server (Windows Feature *DSC-Service*) will be deprecated in a future version of Windows Server. It is recommended to
> begin transitioning managed clients to [Azure Automation DSC](/azure/automation/automation-dsc-getting-started)
> (includes features beyond Pull Server on Windows Server) or one of the community solutions
> listed [here](pullserver.md#community-solutions-for-pull-service).

Each target node has to be told to use pull mode and given the URL or file location where it can contact the pull server to get configurations and resources, and where it should send report data.

The following topics explain how to set up pull clients:

Expand Down
7 changes: 6 additions & 1 deletion dsc/pullClientConfigID.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,16 @@ ms.topic: conceptual
keywords: dsc,powershell,configuration,setup
title: Setting up a pull client using configuration ID
---

# Setting up a pull client using configuration ID

> Applies To: Windows PowerShell 5.0

> [!IMPORTANT]
> The Pull Server (Windows Feature *DSC-Service*) will be deprecated in a future version of Windows Server. It is recommended to
> begin transitioning managed clients to [Azure Automation DSC](/azure/automation/automation-dsc-getting-started)
> (includes features beyond Pull Server on Windows Server) or one of the community solutions
> listed [here](pullserver.md#community-solutions-for-pull-service).

Each target node has to be told to use pull mode and given the URL where it can contact the pull server to get configurations. To do this, you have to configure the Local Configuration Manager (LCM) with the necessary information. To configure the LCM, you create a special type of configuration, decorated with the **DSCLocalConfigurationManager** attribute. For more information about configuring the LCM, see [Configuring the Local Configuration Manager](metaConfig.md).

> **Note**: This topic applies to PowerShell 5.0. For information on setting up a pull client in PowerShell 4.0, see [Setting up a pull client using configuration ID in PowerShell 4.0](pullClientConfigID4.md)
Expand Down
7 changes: 6 additions & 1 deletion dsc/pullClientConfigNames.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,16 @@ ms.topic: conceptual
keywords: dsc,powershell,configuration,setup
title: Setting up a pull client using configuration names
---

# Setting up a pull client using configuration names

> Applies To: Windows PowerShell 5.0

> [!IMPORTANT]
> The Pull Server (Windows Feature *DSC-Service*) will be deprecated in a future version of Windows Server. It is recommended to
> begin transitioning managed clients to [Azure Automation DSC](/azure/automation/automation-dsc-getting-started)
> (includes features beyond Pull Server on Windows Server) or one of the community solutions
> listed [here](pullserver.md#community-solutions-for-pull-service).

Each target node has to be told to use pull mode and given the URL where it can contact the pull server to get configurations.
To do this, you have to configure the Local Configuration Manager (LCM) with the necessary information.
To configure the LCM, you create a special type of configuration, decorated with the **DSCLocalConfigurationManager** attribute.
Expand Down
Loading