en-us/about_AutomatedLab_dynamics365.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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
TOPIC
    about_automatedlab_dynamics365
 
SHORT DESCRIPTION
    Generic help about the Role 'dynamics365' in AutomatedLab
 
LONG DESCRIPTION
Dynamics 365
    AutomatedLab is capable of deploying Dynamics 365 either as a full
    installation or using the groups Frontend, Backend and Administration.
    Deploying Dynamics 365 in a lab requires a fitting SQL machine, a domain
    environment and ideally a certificate authority.
    All required Active Directory OUs, users and groups will be automatically
    created and group membership configured as outlined in
    the official docs
    .
 
    SAMPLE SCRIPT
    For a bare-bones sample script, have a look at the following code:
 
 
    New-LabDefinition -name dynamics -DefaultVirtualizationEngine HyperV
    Add-LabDomainDefinition contoso.com -AdminUser Install -AdminPassword Somepass1
    Set-LabInstallationCredential -Username Install -Password Somepass1
    Add-LabIsoImageDefinition -name SQLServer2017 -Path $labsources/ISOs/en_sql_server_2017_enterprise_x64_dvd_11293666.iso
    Add-LabMachineDefinition -Name DDC1 -Memory 4GB -Roles RootDc,CARoot -Domain contoso.com -OperatingSystem 'Windows Server 2019 Datacenter (Desktop Experience)'
    Add-LabMachineDefinition -Name DDB1 -Memory 8GB -Roles SQLServer2017 -Domain contoso.com -OperatingSystem 'Windows Server 2019 Datacenter (Desktop Experience)'
    Add-LabMachineDefinition -Name DDY1 -Memory 16GB -Roles DynamicsFull -Domain contoso.com -OperatingSystem 'Windows Server 2019 Datacenter (Desktop Experience)'
    Install-Lab
 
    ROLE PROPERTIES
    In order to specify installation parameters, you can use the `Properties`
    parameter of the `Get-LabMachineRoleDefinition` cmdlet. All four roles,
    `DynamicsFull`, `DynamicsFrontend`, `DynamicsBackend`, `DynamicsAdmin`
    support the same set of properties.
    - LicenseKey: Supply your own license key, otherwise a trial license will be used
    - SqlServer: Server name (optionally include the instance) of a SQL Server
    that is part of the lab
    - ReportingUrl: If using reporting services, specify the URL
    - OrganizationCollation: Collation for the database that is created
    - IsoCurrencyCode: The three-letter ISO currency code, e.g. USD
    - CurrencyName: Currency name, arbitrary
    - CurrencySymbol: Currency symbol, arbitrary
    - CurrencyPrecision: Precision, between 2 and 4
    - Organization: Friendly name of the organization
    - OrganizationUniqueName: Organization name part of the URL, max 30 characters
    - CrmServiceAccount: AppPool identity
    - SandboxServiceAccount: Sandbox processing svc
    - DeploymentServiceAccount: Deployment svc
    - AsyncServiceAccount: Async processing
    - VSSWriterServiceAccount: VSS writer svc
    - MonitoringServiceAccount: Monitoring svc
    - CrmServiceAccountPassword: Plaintext string
    - SandboxServiceAccountPassword: Plaintext string
    - DeploymentServiceAccountPassword: Plaintext string
    - AsyncServiceAccountPassword: Plaintext string
    - VSSWriterServiceAccountPassword: Plaintext string
    - MonitoringServiceAccountPassword: Plaintext string
    - IncomingExchangeServer: Specify an Exchange server part of the lab to
    configure incoming mail
    - PrivUserGroup: Distinguished name of the privileged user group. Domain-DN
    is replaced with lab domain/machine domain
    - SQLAccessGroup: Group accessing the SQL server. Domain-DN is replaced with
    lab domain/machine domain
    - ReportingGroup: Distinguished name of the reporting group. Domain-DN is
    replaced with lab domain/machine domain
    - PrivReportingGroup: Distinguished name of the privileged reporting group.
    Domain-DN is replaced with lab domain/machine domain