New-NfsNetgroup
New-NfsNetgroup
Creates a netgroup.
Syntax
Parameter Set: AllParameterSets
New-NfsNetgroup [-NetGroupName] <String> [[-AddMember] <String> ] [[-LdapServer] <String> ] [[-LdapNamingContext] <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Detailed Description
The New-NfsNetgroup cmdlet creates a netgroup. It can also add members to the new netgroup. The netgroup provides access to shares that Network File System (NFS) server exports.
You can create a netgroup in Active Directory Domain Services (AD DS), on an Active Directory Lightweight Directory Services (AD LDS) server, or on Lightweight Directory Access Protocol (LDAP) servers. If you do not specify a netgroup store, New-NfsNetgroup creates a netgroup in the netgroup store that is configured on the local computer.
The cmdlet creates the netgroup as a relative distinguished name in an LDAP naming context (directory partition). For example, if the specified naming context is DN=netgroups,CN=Contoso,CN=com", the distinguished name of the netgroup Contoso-PrintServices is "DN= Contoso-PrintServices ,DN=netgroups,CN=Contoso,CN=com".
You can group NFS client computers logically into netgroups to easily manage mount permissions for all the computers that are in the group. Because netgroups are a server-side setting, New-NfsNetgroup is not available on client operating systems.
Parameters
-AddMember<String>
Specifies the host names or IP addresses of the client computers to add to a netgroup.
Aliases |
none |
Required? |
false |
Position? |
2 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-LdapNamingContext<String>
Specifies the LDAP naming context of the new netgroup store.
Aliases |
none |
Required? |
false |
Position? |
4 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-LdapServer<String>
Specifies the LDAP server name of the new netgroup store. The LDAP server name can be a domain name, AD LDS server name, or other LDAP server name.
Aliases |
none |
Required? |
false |
Position? |
3 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-NetGroupName<String>
Specifies the name of a new netgroup.
Aliases |
none |
Required? |
true |
Position? |
1 |
Default Value |
none |
Accept Pipeline Input? |
True (ByPropertyName) |
Accept Wildcard Characters? |
false |
-Confirm
Prompts you for confirmation before running the cmdlet.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Required? |
false |
Position? |
named |
Default Value |
false |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
- Microsoft.FileServices.Powershell.Nfs.NetGroup
Examples
Example 1: Create a netgroup and add a member
This command creates a netgroup that is named Contoso-PrintServices and adds one member that is named Contoso-PS02.
PS C:\> New-NfsNetgroup -NetGroupName "Contoso-PrintServices -AddMember "Contoso-PS02" -LdapInstanceName "Contoso.com" -LdapNamingContext "CN=MappedIdentity,DC=Contoso,DC=com"
Example 2: Create a netgroup and add multiple members
This command creates a netgroup that is named AppServers and adds two members that are named Contoso-APPS-11 and Contoso-APPS-12.
PS C:\> New-NfsNetgroup -NetGroupName "AppServers" -AddMember "Contoso-APPS-11","Contoso-APPS-12" -LdapServer "Contoso.com" -LdapNamingContext "CN=netgroup,DC=Contoso,DC=com"