You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md
+5-138Lines changed: 5 additions & 138 deletions
Original file line number
Diff line number
Diff line change
@@ -6,16 +6,6 @@ schema: 2.0.0
6
6
# New-MapiVirtualDirectory
7
7
8
8
## SYNOPSIS
9
-
!!! Exchange Server 2013
10
-
11
-
This cmdlet is available only in on-premises Exchange.
12
-
13
-
Use the New-MapiVirtualDirectory cmdlet to create Messaging Application Programming Interface (MAPI) virtual directories on Microsoft Exchange 2013 servers A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol.
14
-
15
-
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
16
-
17
-
!!! Exchange Server 2016
18
-
19
9
This cmdlet is available only in on-premises Exchange.
20
10
21
11
Use the New-MapiVirtualDirectory cmdlet to create Messaging Application Programming Interface (MAPI) virtual directories that are used in Internet Information Services (IIS) on Microsoft Exchange servers. A MAPI virtual directory is used by supported versions of Microsoft Outlook to connect to mailboxes by using the MAPIHTTP protocol.
@@ -25,47 +15,25 @@ For information about the parameter sets in the Syntax section below, see Exchan
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Client Access virtual directory settings" entry in the Clients and mobile devices permissions topic.
39
-
40
-
!!! Exchange Server 2016
41
-
42
23
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).
43
24
44
25
## EXAMPLES
45
26
46
-
### Example 1 -------------------------- (Exchange Server 2013)
The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values for this parameter are:
180
-
181
-
- Basic
182
-
183
-
- Negotiate
184
-
185
-
- NTLM
186
-
187
-
You can specify multiple values separated by commas.
188
-
189
-
190
-
191
-
!!! Exchange Server 2016
192
-
193
97
The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values for this parameter are:
194
98
195
99
- Basic
@@ -205,7 +109,6 @@ You can specify multiple values separated by commas.
205
109
The default values are NTLM, OAuth, and Negotiate. We recommend that you always have the virtual directory configured for OAuth.
206
110
207
111
208
-
209
112
```yaml
210
113
Type: MultiValuedProperty
211
114
Parameter Sets: (All)
@@ -239,41 +142,7 @@ Accept pipeline input: False
239
142
Accept wildcard characters: False
240
143
```
241
144
242
-
### -Role
243
-
This parameter is reserved for internal Microsoft use.
244
-
245
-
```yaml
246
-
Type: ClientAccess | Mailbox
247
-
Parameter Sets: (All)
248
-
Aliases:
249
-
Applicable: Exchange Server 2013
250
-
251
-
Required: False
252
-
Position: Named
253
-
Default value: None
254
-
Accept pipeline input: False
255
-
Accept wildcard characters: False
256
-
```
257
-
258
145
### -Server
259
-
!!! Exchange Server 2013
260
-
261
-
The Server parameter specifies the Exchange server that will host the virtual directory. You can use any value that uniquely identifies the server. For example:
262
-
263
-
- Name
264
-
265
-
- FQDN
266
-
267
-
- Distinguished name (DN)
268
-
269
-
- Exchange Legacy DN
270
-
271
-
If you don't use the Server parameter, the virtual directory will be created on the server where the remote PowerShell session is established. This will always be a Mailbox server. If you want to create the virtual directory on a Client Access server or another Mailbox server, you need to use the Server parameter.
272
-
273
-
274
-
275
-
!!! Exchange Server 2016
276
-
277
146
The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
278
147
279
148
- Name
@@ -285,7 +154,6 @@ The Server parameter specifies the Exchange server that hosts the virtual direct
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
203
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
336
204
337
205
## INPUTS
338
206
@@ -349,4 +217,3 @@ To see the return types, which are also known as output types, that this cmdlet
0 commit comments