en-us/about_AutomatedLab_dscpull.help.txt

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
TOPIC
    about_automatedlab_dscpull
 
SHORT DESCRIPTION
    Generic help about the Role 'dscpull' in AutomatedLab
 
LONG DESCRIPTION
DSC Pull Server
    With the DSCPullServer role, new pull or reporting servers for Desired State
    Configuration can be deployed. This role requires a certificate authority
    somewhere in the lab environment. Internet connectivity of the lab host is
    recommended, but not required. If your host is not connected, make sure that
    xPSDesiredStateConfiguration, xWebAdministration and xDscDiagnostics are in
    your module path.
    Starting with Server 1809 (guest operating system) you can choose to deploy
    the pull server with a SQL backend. This option requires a SQL Server in the
    lab which will host the DSC database.
 
    ROLE ASSIGMNENT
    The default role assignment deploys a standard SSL DSC Pull Server using an
    edb backend.
 
    Add-LabMachineDefinition -Name Pulli -Roles DscPullServer
 
    You can optionally specify parameters by using the role definition:
 
    $role = Get-LabMachineRoleDefinition -Role DscPullServer -RoleProperties @{
        DatabaseEngine = 'mdb'
        DatabaseName = 'DSC'
        DatabaseServer = 'SQL01'
        }
     
    Add-LabMachineDefinition -Name Pulli -Roles $role
 
    ROLE PROPERTIES
    DONOTPUSHLOCALMODULES
    Indicates that locally installed DSC resources may not be pushed to the pull
    server
 
    DATABASEENGINE
    Which database engine will be used. Either edb or mdb. Default is edb.
 
    DATABASENAME
    The name of the database to deploy if mdb is selected.
 
    DATABASESERVER
    The name of the database server to deploy the database on if mdb is selected