6. Understanding and Using Password Recovery
Users can create passwords for their mobile devices. If a user forgets his or her password, you can obtain a recovery
password that unlocks the device and lets the user create a new
password. The user can also recover his or her device password by using
Outlook Web App.
To use Outlook Web App to recover a user's device password, complete the following steps:
-
Open a Web browser. In the Address field, type the Outlook Web App URL, such as https://mail.cpandl.com/owa, and then press Enter to access this page. -
When prompted, provide the user's logon credentials. Do not provide your administrator credentials. -
On the Outlook Web App toolbar, click Options. -
The left pane of the Options view provides a list of options. Click Phone. -
The user's mobile devices are listed in the details pane. Select the device for which you are recovering the password. -
Click Display Recovery Password.
You also can display the device recovery password by completing the following steps:
-
In the Exchange Management Console, expand the Recipient Configuration node, and then select the Mailbox node. -
Right-click the user's mailbox, and then select Manage Mobile Device.
The device recovery password is displayed in the Manage Mobile Device
dialog box.
In the Exchange Management Shell, you can display the device recovery password using the –ShowRecoveryPassword parameter of the Get-ActiveSyncDeviceStatistics cmdlet. Example 11 provides the syntax and usage.
Example 11 Recovering a device password
Syntax
Get-ActiveSyncDeviceStatistics -Mailbox MailboxIdentity
-ShowRecoveryPassword $true {AddtlParams}
Get-ActiveSyncDeviceStatistics -Identity ActiveSyncDeviceIdentity
-ShowRecoveryPassword $true {AddtlParams}
{AddtlParams}
[-GetMailboxLog <$true | $false>] [-DomainController DCName]
[-NotificationEmailAddresses AliasOrEmail1, AliasOrEmail2, . . . ]
Usage
Get-ActiveSyncDeviceStatistics -Mailbox "[email protected]"
-ShowRecoveryPassword $true
7. Understanding and Configuring Direct File Access
By default, Exchange Server 2010 allows users to access files
directly through Outlook, Outlook Web App, and related services. This
means that users will be able to access files attached to e-mail
messages. You can configure how users interact with files using one of
three options in the Exchange Management Console:
-
Allow Allows users
to access files of the specified types, and sends the users' browser
information that allows the files to be displayed or opened in the
proper applications -
Block Prevents users from accessing files of the specified types -
Force Save Forces users to save files of the specified types prior to opening them
Table 1
lists the default file extensions and default Multipurpose Internet
Mail Extensions (MIME) values that Exchange Server allows, blocks, or
sets to force save by default. These settings are applied to the OWA
virtual directory on Client Access servers. If a server has multiple OWA
virtual directories or you have multiple Client Access servers, you
must configure each directory and server separately.
Note
If there are conflicts between the allow, block, and force save
lists, the allow list takes precedence. This means that the allow list
settings override the block list and the force save list. As updates are
applied to Exchange Server, the default lists can change. Be sure to
check the currently applied defaults.
Table 1. Default File Extensions and Default MIME Values for Direct File Access
|
OPTION |
DEFAULT FILE NAME EXTENSIONS |
DEFAULT MIME VALUES |
|---|
|
Allow |
.avi, .bmp, .doc, .docm, .docx, .gif, .jpg, .mp3, .one, .pdf, .png,
.ppsm, .ppsx, .ppt, .pub, .rpmsg, .rtf, .tif, .tiff, .txt, .vsd, .wav,
.wma, .wmv, .xls, .xlsb, .xlsm, .xlsx, .zip |
image/jpeg, image/png, image/gif, image/bmp | |
Block |
.ade, .adp, .asx, .app, .asp, .aspx, .asx, .asx, .bas, .bat, .cer,
.chm, .cmd, .com, .cpl, .crt, .csh, .der, .exe, .fxp, .gadget, .hlp,
.hta, .htc, .inf, .ins, .isp, .its, .js, .jse, .ksh, .lnk, .mad, .maf,
.mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mda, .mdb, .mde,
.mdt, .mdw, .mdz, .mht, .mhtml, .msc, .msh, .msh1, .mshxml, .msh1xml,
.msi, .msp, .mst, .ops, .pcd, .pif, .plg, .prf, .prg, .ps1, .ps2, .psc1,
.psc2, .ps1xml, .ps2xml, .pst, .reg, .scf, .scr, .sct, .shb, .shs,
.spl, .swf, .tmp, .url, .vb, .vbe, .vbs, .vsmacros, .vss, .vst, .vsw,
.ws, .wsc, .wsf, .wsh, .xml |
application/hta, application/javascript, application/msaccess,
application/prg, application/x-javascript, application/xml,
text/javascript, text/scriptlet, text/xml, x-internet-signup | |
Force Save |
.vsmacros, .mshxml, .aspx, .xml, .wsh, .wsf, .wsc, .vsw, .vst, .vss,
.vbs, .vbe, .url, .tmp, .swf, .spl, . shs, .shb, .sct, .scr, .scf, .reg,
.pst, .prg, .prf, .plg, .pif, .pcd, .ops, .mst, .msp, .msi, .msh, .msc,
.mdz, .mdw, .mdt, .mde, .mdb, .mda, .maw, .mav, .mau, .mat, .mas, .mar,
.maq, .mam, .mag, .maf, .mad, .lnk, .ksh, .jse, .its, .isp, .ins, .inf,
.hta, .hlp, .fxp, .exe, .dir, .dcr, .csh, .crt, .cpl, .com, .cmd, .chm,
.cer, .bat, .bas, .asx, .asp, .app, .adp, .ade, .ws, .vb, .js |
Application/x-shockwave-flash, Application/octet-stream, Application/futuresplash, Application/x-director |
Exchange Server considers all file extensions and MIME types not
listed on the allow, block, or force save list to be unknown files and
file types. The default setting for unknown file types is force save.
Based on the user's selection, the configuration of his or her
network settings, or both, Exchange divides all client connections into
one of two classes:
-
Public or shared computer A public computer is a computer being used on a public network or a computer shared by multiple people. -
Private computer A private computer is a computer on a private network that is used by one person.
You can enable or disable direct access to files separately for
public computers and private computers. However, the allow, block, and
force save settings for both types of computers are shared and applied
to both public and private computers in the same way.
You can configure direct file access by completing the following steps:
-
In the Exchange Management Console, expand the Server Configuration node, and then select the Client Access node. -
In the upper portion of the details pane, you'll see a list of your
organization's Client Access servers. Select the server you want to
configure. -
In the lower portion of the details pane, you'll see a list of option
tabs for the selected server. On the Outlook Web App tab, right-click
the virtual directory for which you are configuring direct
file access, and then select Properties. Typically, you'll want to
configure the OWA virtual directory on the Default Web Site because this
directory is used by default for Outlook Web App. -
To enable or disable direct file access for public computers, on the
Public Computer File Access tab, select or clear the Enable Direct File
Access check box, as appropriate. (See Figure 5.)
-
To enable or disable direct file access for private computers, on the Private Computer File Access tab (shown on the right in Figure 5), select or clear the Enable Direct File Access check box, as appropriate. -
On either the Public Computer File Access tab or Private Computer
File Access tab, click the Customize button on the Direct File Access
panel. The Direct File Access Settings dialog box appears, as shown in Figure 6.
-
In the Direct File Access Settings dialog box, you can configure
allowed files by clicking Allow. The Allow List dialog box appears, as
shown in Figure 7. Use the following techniques to configure allowed files, and then click OK:
-
To allow a new file extension, type it in the text box provided. Be sure to include the period, such as .xhtml, and then press Enter or click Add. -
To allow a new MIME type, enter it in the text box provided. Be sure to include the full MIME type designator, such as text/xhtml, and then press Enter or click Add. -
To stop allowing a file extension or MIME type, select it and then click the Remove button. This button shows an X.
-
In the Direct File Access Settings dialog box, you can configure
blocked files by clicking Block. The Block List dialog box appears. Use
the following techniques to configure blocked files, and then click OK:
-
To block a new file extension, type it in the text box provided. Be sure to include the period, such as .src, and then press Enter or click Add. -
To block a new MIME type, enter it in the text box provided. Be sure to include the full MIME type designator, such as application/src, and then press Enter or click Add. -
To stop blocking a file extension or MIME type, select it, and then click the Remove button.
-
In the Direct
File Access Settings dialog box, you can configure allowed files by
clicking Force Save. The Force Save List dialog box appears. Use the
following techniques to configure force-saved files, and then click OK:
-
To force save a new file extension, type it in the text box provided. Be sure to include the period, such as .aap, and then press Enter or click Add. -
To force save a new MIME type, enter it in the text box provided. Be sure to include the full MIME type designator, such as application/stream, and then press Enter or click Add. -
To stop force saving a file extension or MIME type, select it, and then click the Remove button. This button shows an X.
-
In the Direct
File Access Settings dialog box, you can configure allowed files using
the selection list on the Unknown Files panel. Set the desired action to
Allow, Block, or Force Save. Click OK to save your settings, and then
click OK to close the Properties dialog box for the virtual directory
you selected.
In the Exchange Management Shell, you can use the Set-OWAVirtualDirectory
cmdlet to manage the direct file-access configuration. Set the
–Identity parameter to the identity of the virtual directory on the
server with which you want to work, such as:
Set-OWAVirtualDirectory -Identity "Corpsvr127\owa (Default Web Site)"
-DirectFileAccessOnPublicComputersEnabled $false
-DirectFileAccessOnPrivateComputersEnabled $true
If you are unsure of the virtual directory identity value, use the Get-OWAVirtualDirectory
cmdlet to retrieve a list of available virtual directories on a named
server, as shown in the following example:
Get-OWAVirtualDirectory -Server "Corpsvr127"
|
