Add-DAClient

Syntax

Add-DAClient
   [-ComputerName <String>]
   [-PassThru]
   [-SecurityGroupNameList <String[]>]
   [-GpoName <String[]>]
   [-CimSession <CimSession[]>]
   [-ThrottleLimit <Int32>]
   [-AsJob]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]

Add-DAClient
   [-DownlevelGpoName <String[]>]
   [-DownlevelSecurityGroupNameList <String[]>]
   [-EntrypointName <String>]
   [-ComputerName <String>]
   [-PassThru]
   [-CimSession <CimSession[]>]
   [-ThrottleLimit <Int32>]
   [-AsJob]
   [-WhatIf]
   [-Confirm]
   [<CommonParameters>]

Description

The Add-DAClient cmdlet adds one or more client computer security groups (SGs) to the DirectAccess (DA) deployment, adds one or more DA client Group Policy Objects (GPOs) in one or more domains, adds one or more SGs of down-level clients to the DA deployment in a multi-site deployment, or adds one or more down-level DA client GPOs in one or more domains in a multi-site deployment.

The client SG and GPO parameters are treated as independent entities. The basic paradigm is that client GPOs can be created independent of the SGs and the represented domains. Every SG that is added to the DA deployment is added in all current client GPOs. Therefore all GPOs always contain all SGs even if all the corresponding domains are not represented in all the SGs.

There will never be a scenario where an SG is present only in some of the GPOs. If this happens, then it means that the state of the configuration is bad.

Extending this paradigm, adding clients to an SG is a pure SG level operation which can be accomplished using AD cmdlets, such as the Add-ADGroupMember cmdlet.

Although AD cmdlets are already available for the addition of SGs and GPOs, the additional capabilities of this cmdlet are justified as follows.

-- When an SG is added it is added in all Client GPOs. If user does not have permissions to edit a GPO, then the SG is not added to any of the Client GPOs in any of the domains. When using the AD cmdlet, the user would have to carefully ensure that it is run for each of the domains and it is difficult to handle the case where the user does not have permissions on some domains.

-- When a GPO is added all SGs are added in the GPO and DA client specific policies are created. This cmdlet takes care of the conditions where the GPO is created if not already present. If the GPO is already present, then it is merely edited

The following are additional behavior notes for the cmdlet.

-- At least one client GPO is always present. The Install-RemoteAccess cmdlet always creates a GPO even if there are no SGs added. There is never a case where there are no client GPOs. However, if this situation occurs, then adding an SG without specifying a domain or GPO is not allowed. A GPO can still be added alone, but only when there is no client GPO already present in that domain.

-- If DA is configured to be deployed only on laptops and notebooks, then when a domain or GPO is added, a WMI filter to enforce this policy is created in that domain and applied to all the SGs. If the user does not have the permissions to create a filter in a domain, then a GPO is not created in that domain and a non-terminating error is issued.

-- When adding a new GPO, if it is already present in the domain, then it is merely configured with the list of SG and DA client specific policies. Essentially, it is brought into the DA deployment. If it is not present, then it is created first.

-- Attempting to re-add a domain or specify the same GPO name for the domain again will result in no changes being made.

-- Attempting to add a new GPO in a domain that already consists of a client GPO will result in no action being taken and the display of a non-terminating error.

-- Attempting to add SGs in even a single GPO without the correct permissions will result in the cmdlet terminating the processing of the entire list of SGs that were specified. However, the cmdlet still processes the list of GPOs that have been specified.

-- Attempting to create or configure one of the specified GPOs without the correct permissions will result in the cmdlet proceeding with the processing of the remaining GPOs.

-- In a multi-site deployment.

---- Clients that are added can connect to all the sites.

---- A separate set of parameters is available for adding down-level clients. Additional information can be found under parameter description.

-- If multi-site has not been deployed, attempting to add down-level GPOs or SGs using the DownlevelGpoName and DownlevelSecurityGroupNameList parameters will display an error.

Examples

EXAMPLE 1

PS C:\> Add-DAClient -SecurityGroupNameList 'corp.contoso.com\DirectAccessLaptopClients','corp.contoso.com\DirectAccessMobileClients' -PassThru
SecurityGroupNameList          : {corp.contoso.com\DirectAccessLaptopClients, corp.contoso.com\DirectAccessMobileClients} 
GPOName                        : {corp.contoso.com\DirectAccess Client Settings} 
OnlyRemoteComputers            : Disabled 
Downlevel                      : Disabled 
ForceTunnelingStatus           : Disabled 
ForceTunnelingNrptSuffix       : 
EntrypointName                 : 
DownlevelSecurityGroupNameList : 
DownlevelGpoName               :

This example will add the SGs corp.contoso.com\DirectAccessLaptopClients and corp.contoso.com\DirectAccessMobileClients to DA configuration. corp .contoso.com/DirectAccess Client Settings is the DA Client GPO configured at the time of DA installation.

Two new SGs DirectAccessLaptopClients and DirectAccessMobileClients are created and DA Connectivity is provisioned for these SGs. This cmdlet will add the SGs to DA configuration. This essentially means that the existing Client GPO configuration corp.contoso.com/DirectAccess Client Settings will be filtered on the two SGs.

This cmdlet will only provision Windows® 8 clients. Down-level clients have to be provisioned separately.

EXAMPLE 2

PS C:\>Add-DAClient -GPOName 'child.corp.contoso.com' -PassThru
SecurityGroupNameList          : {corp.contoso.com\DirectAccessLaptopClients, corp.contoso.com\DirectAccessMobileClients} 
GPOName                        : {corp.contoso.com\DirectAccess Client Settings, child.corp.contoso.com\DirectAccess Client Settings} 
OnlyRemoteComputers            : Disabled 
Downlevel                      : Disabled 
ForceTunnelingStatus           : Disabled 
ForceTunnelingNrptSuffix       : 
EntrypointName                 : 
DownlevelSecurityGroupNameList : 
DownlevelGpoName               :

This example will provision DA for the domain child.corp.contoso.com which is the child of corp.contoso.com. This will create a GPO named child.corp.contoso.com/DirectAccess Client Settings, using default naming convention). This cmdlet makes sure that all the SGs present in DA Client configuration are added to this GPO.

EXAMPLE 3

PS C:\>Add-DAClient -DownlevelSecurityGroupNameList 'child.corp.contoso.com\DownlevelClients' -DownlevelGPOName 'child.corp.contoso.com\DownLevelClientsGPO' -EntrypointName '2-Edge-Site' -PassThru
SecurityGroupNameList          : {corp.contoso.com\DirectAccessLaptopClients, corp.contoso.com\DirectAccessMobileClients} 
GPOName                        : {corp.contoso.com\DirectAccess Client Settings, child.corp.contoso.com\DirectAccess Client Settings } 
OnlyRemoteComputers            : Disabled 
Downlevel                      : Disabled 
ForceTunnelingStatus           : Disabled 
ForceTunnelingNrptSuffix       : 
EntrypointName                 : 
DownlevelSecurityGroupNameList : child.corp.contoso.com\DownlevelClients 
DownlevelGpoName               : child.corp.contoso.com\DownLevelClientsGPO

This example provisions DA for firstref_client_7 clients present in the domain child.corp.contoso.com enabling them to connect to site 2-Edge-Site. 2-Edge-Site is the site configured for the child domain. A new GPO ( DownlevelClientsGPO ) can be added to the DiretAccessConfiguration. This GPO is filtered on DownlevelClients SG which contains Windows® 7 clients in the child domain. Note: The Windows® 7 clients can only connect access the site specified in the EntrypointName parameter.

Optional Parameters

Inputs

None

Outputs

Microsoft.Management.Infrastructure.CimInstance#DAClient

The Microsoft.Management.Infrastructure.CimInstance object is a wrapper class that displays Windows Management Instrumentation (WMI) objects. The path after the pound sign ( # ) provides the namespace and class name for the underlying WMI object.

The output object contains the following properties:

-- The list of client SGs present in the DA deployment.

-- The list of client GPOs present in the DA deployment.

-- The status of force tunnel.

-- The Name Resolution Policy Table (NRPT) object (for force tunnel properties).

-- The status of the policy to deploy DA only on laptops and notebooks and not on all computers in the domain.

-- The status of whether appropriate policies should be deployed on down-level clients (Windows® 7) to enable them to connect to the Windows Server 2012 DA server.

If multi-site is enabled, then the following additional properties are present:

-- The name of the entry point (identity of a site) to which down-level clients are added.

-- The name of the down-level client GPO.

-- The list of SGs of down-level clients.

Related Links

• Get-DAClient
• Remove-DAClient
• Set-DAClient