Before the cmdlet will run,
a test user needs to be created. There is a script located in the scripts directory named
New-TestCasConnectivityUser.ps1 . If the script is not run from a mailbox server, one must
be piped into the script. Figure 6 - 11 illustrates creating the connectivity test user with the
new-TestCasConnectivityUser script.
get-mailboxServer | new-TestCasConnectivityUser.ps1 [-UMDialPlan
< dialplanname > -UMExtension < numDigitsInDialplan > ]
get-mailboxServer foo | new-TestCasConnectivityUser.ps1 [-UMDialPlan
< dialplanname > -UMExtension < numDigitsInDialplan > ]
Figure 6-11
Chapter 6: Confi guring the Client Access Server Role
181
Proxy and Redirection
The CAS provides many different types of client access. Each of the services has a namespace associated
with it. For example, Outlook Web Access, IMAP, and Exchange ActiveSync clients each require a URL to
connect to the service. They do not have to be the same, and in the case of Autodiscover it will likely not
be the same. As illustrated previously in the certificates section, features or security needs may require
more than a single namespace for a certificate. In addition to security the namespace can have implications
on network traffic. In previous versions of Exchange, the front - end server proxy requests to the
mailbox server without regard to physical network topology.
Pages:
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280