KB Articles

Page 1 of 75212345...102030...Last »

Email messages that you send from a shared mailbox are not saved in the Sent Items folder in Outlook for Mac

Consider the following scenario:
  • You have a primary mailbox that has Full Access and Send As permissions to a shared mailbox.
  • You configure Microsoft Outlook for Mac for Office 365 or Outlook for Mac 2011 to open a primary mailbox that is hosted on Microsoft Exchange Server 2013, Exchange Server 2010, or Exchange Server 2007.
  • In the same Outlook identity, you open a secondary shared mailbox that is hosted on Exchange Server 2013, Exchange Server 2010, or Exchange Server 2007.
  • You use the credentials of the primary mailbox to access the shared mailbox.
  • You send email messages from the shared mailbox.

In this scenario, email messages that you send from the shared mailbox are not saved in the Sent Items folder of the shared mailbox. Instead, the messages are saved in the Drafts folder of the primary mailbox on the Exchange Server. Additionally, the messages in the primary mailbox’s Drafts folder are not synchronized to the Outlook for Mac client, and they are visible only when you use Outlook Web Access or a Windows Outlook client.

This issue occurs because the Exchange Web Services GetMessageParentFolderIdAndSession function incorrectly uses the SendAndSaveCopy method.
This issue was resolved in Exchange Server 2013 in Cumulative Update 5 http://support.microsoft.com/kb/2936880

(http://support.microsoft.com/kb/2936880)

After you install this cumulative update, the messages will be saved in the Sent Items folder of the Shared mailbox.

If you run Exchange Server 2010 or Exchange Server 2007, the following workaround methods are applicable.

Method 1

  1. In Outlook for Mac, click Tools > Accounts.
    Note
    If you have the shared account added here, select it and then click the Minus Sign (-) to remove it. Click Delete to confirm.
  2. Click Advanced, and then click Delegates.
  3. In the People I am a delegate for: section, click the Plus Sign (+).
    Note You do not have to be a delegate for the shared account in order to add it here, you only need permissions to access this mailbox.
  4. Enter the alias of the Shared Account, and then click Find. Select the correct account, and then click OK.
  5. Click OK, and then close the Accounts window.
  6. Allow for time for the shared account to appear in the folder list in Outlook for Mac 2011.

Now, when an email is sent from the Shared mailbox, the message will be saved in the Sent Items folder of the Primary mailbox.

Note If you prefer the messages to be saved in both the Primary and Shared mailbox Sent Items folders and you are running Exchange Server 2010 Service Pack 2 (SP2) RU4 or a later version, you can run one of the following Windows PowerShell commands depending on whether you use the Send As or Send On Behalf permission.

Send As: Set-MailboxSentItemsConfiguration <SharedAccountAlias> -SendAsItemsCopiedTo SenderAndFrom
Send On Behalf: Set-MailboxSentItemsConfiguration <SharedAccountAlias> -SendOnBehalfOfItemsCopiedTo SenderAndFrom

Method 2

  1. In Outlook for Mac, click Tools > Accounts.
  2. Select the shared account, and then click the Minus Sign (-) to remove it. Click Delete to confirm.
  3. Close the Accounts window.
  4. Click File, click Open, and then click Other User’s Folder.
  5. Enter the name of the shared mailbox, select Inbox as the folder type, and then click OK.

Note When you use this method, only the Inbox folder of the shared mailbox is available. If you must have access to other folders, use method 1.

Article ID: 2928846 – Last Review: October 31, 2014 – Revision: 6.0


Applies to
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
  • Microsoft Outlook for Mac 2011
  • Outlook for Mac for Office 365
kbsurveynew kbprb kbtshoot KB2928846

View post:
Email messages that you send from a shared mailbox are not saved in the Sent Items folder in Outlook for Mac

Meetings appear in the calendar as Tentative but the user didn’t receive the requests in the inbox or meeting reponses from others don’t appear in the inbox

A user experiences one or both the following symptoms in Outlook:
  • The user doesn’t receive meeting requests in their inbox. However, the meetings appear in the user’s calendar as Tentative.
  • When the user creates a meeting request, the user doesn’t see meeting responses from attendees. However, tracking information for the meeting is updated in the user’s calendar.

In this scenario, the user does not have a delegate set up.

This issue occurs if the meeting requests were processed incorrectly in the user’s mailbox and they get delivered to the user’s Deleted Items folder instead of the Inbox folder or the meeting requests were processed incorrectly as if a delegate was set up. 

This can occur if the Receive folder for the IPM.SCHEDULE.MEETING message class was changed to the /Schedule folder or if the PR_RULE_MSG_PROVIDER property of messages that have as message class of IPM.Rule.Version2.Message is set to Schedule+ EMS Interface.

To resolve this issue, start by following the steps in Solution 1. Depending on the scenario, you may have to use the steps in Solution 2. You will not know which solution applies to the user until you start troubleshooting by using the steps in Solution 1. 

Note The exact steps will vary based on the version of the MFCMAPI tool that you’re using. Use caution when you modify mailboxes by using MFCMAPI. Using this tool incorrectly can cause permanent damage to a mailbox.

Solution 1

  1. Download MFCMAPI from http://mfcmapi.codeplex.com/

    (http://mfcmapi.codeplex.com/)

    .

  2. Start MFCMAPI.
  3. On the Session menu, click Logon.
  4. Select the user’s online mode Outlook profile, and then click OK.

    Note If the user doesn’t have an online mode profile, create a profile. Or, on the Tools menu, click Options, and then make sure that both the Use the MBD_ONLINE flag when calling OpenMsgStore check box and the Use the MAPI_NO_CACHE flag when calling OpenEntry check box are selected.

  5. In the list, double-click the user’s primary mailbox.
  6. In the new window that appears, on the MDB menu, point to Display, and then click Receive folder table.
  7. In the window, look for IPM.SCHEDULE.MEETING. Then, do one of the following:
    • If IPM.SCHEDULE.MEETING is not present, go to Solution 2. 
    • If IPM.SCHEDULE.MEETING is present, go to step 8 of this procedure.
  8. Expand the Root container.
  9. Right-click Schedule, click Advanced, and then click Set Receive Folder.
  10. Enter IPM.SCHEDULE.MEETING in the box.
  11. Click Delete Association, and then click OK.
  12. Repeat step 6 and 7 to make sure that the IPM.SCHEDULE.MEETING association is removed from the list.
  13. Test to see whether the user can receive meeting responses and meeting requests in their inbox.

Solution 2

  1. Download MFCMAPI from http://mfcmapi.codeplex.com/

    (http://mfcmapi.codeplex.com/)

    .

  2. Start MFCMAPI.
  3. On the Session menu, click Logon.
  4. Select the user’s online mode Outlook profile, and then click OK.

    Note If the user doesn’t have an online mode profile, create a profile. Or, on the Tools menu, click Options, and then make sure that both the Use the MBD_ONLINE flag when calling OpenMsgStore check box and the Use the MAPI_NO_CACHE flag when calling OpenEntry check box are selected.

  5. In the list, double-click the user’s primary mailbox.
  6. Expand the Root container, and then expand Top of Information Store.
  7. Right-click Inbox, and then click Open Associated Contents Table.
  8. In the upper part of the window, scroll to locate the Message Class column.
  9. Click Message Class to sort the Message Class column.
  10. Look for all messages that have a message class of IPM.Rule.Version2.Message.
  11. Click each message that has a message class of IPM.Rule.Version2.Message, and then in the lower part of the window, look for a property that’s called PR_RULE_MSG_PROVIDER.
  12. Check whether the PR_RULE_MSG_PROVIDER property has a value of Schedule+ EMS Interface.
  13. In the upper part of the window, delete messages whose PR_RULE_MSG_PROVIDER property have a value of Schedule+ EMS Interface.
  14. Test to see whether the user can receive meeting responses and meeting requests in their inbox.
For more info about Receive folders, go to MAPI Receive Folders

(http://msdn.microsoft.com/en-us/library/office/cc815405.aspx)

.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2966790 – Last Review: October 31, 2014 – Revision: 5.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
o365e o365m o365p o365022013 after upgrade o365 o365a KB2966790

See more here:
Meetings appear in the calendar as Tentative but the user didn’t receive the requests in the inbox or meeting reponses from others don’t appear in the inbox

"Error Message: 403.6 – Forbidden" error when you open an IIS Webpage

You have a Web site that is hosted on Internet Information Services (IIS). When you visit the Web site in a Web browser, you may receive an error message that resembles the following:

HTTP 403.6 – Forbidden: IP address rejected

Each client has a unique IP address. If the server defines a list of IP addresses that are not allowed to access the site and the IP address you are using is on this list, you will receive the error message.

This is a feature that grants or denies specific users access to a Web site, directory, or file.

To resolve this problem, follow these steps.
  1. Using the Internet Service Manager (Microsoft Management Console), open the Internet Information Server (IIS) snap-in and select the Web site reporting the 403.6 error. Right-click the Web site, virtual directory, or file where the error is occurring. Click Properties to display the property sheet for that item.
  2. Select the appropriate Directory Security or File Security property page. Under IP Address and Domain Name Restrictions, click Edit.
  3. In the IP Address and Domain Name Restrictions dialog box, if the Denied Access option is selected, then add the IP address, network ID, or domain of the computer that requires access to the exceptions list.

    In the IP Address and Domain Name Restrictions dialog box, if the Granted Access option is selected, then remove the IP address, network ID, or domain of the computer that requires access to the exceptions list.

Important

  • When you set security properties for a specific Web site, you automatically set the same security properties for directories and files belonging to that site, unless the security properties of the individual directories and files have been previously set.
  • Your Web server will prompt you for permission to reset the properties of individual directories and files when you attempt to set security properties for your Web site. If you choose to reset these properties, your previous security settings will be replaced by the new settings. The same condition applies when you set security properties for a directory containing subdirectories or files with previously set security properties.

Notes

  • By default, some sites are only granted access from the IP address 127.0.0.1, which corresponds to the computer name localhost and is considered a different address/name than the NetBIOS or fully qualified domain name (FQDN) of the Web server. To access a site restricted to localhost, you must be at the console of the computer with the localhost restriction.
  • Computers accessing your server across proxy servers will appear to have the IP address of the proxy server.
  • Restricting by domain name is not recommended because it decreases the performance of your Web server by forcing the Web server to perform a reverse DNS lookup for each connection to that site. In addition to increasing the load on the Web server, reverse lookups can also result in unexpected denials.
If the product documentation was installed with IIS, one of the following links will be available when viewed on the IIS server:
Internet Information Services 5.0 Documentation
http://localhost/iishelp/iis/misc/default.asp?jumpurl=../htm/core/iigdasc.htm

Internet Information Server 4.0 Documentation
http://localhost/iishelp/iis/htm/core/igdasc.htm

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

172218

(http://support.microsoft.com/kb/172218/
)

Microsoft TCP/IP host name resolution order

163391

(http://support.microsoft.com/kb/163391/
)

Troubleshooting problems communicating with a server on the Internet using a dial-up networking connection in Windows 2000, Windows NT 4.0, or Windows NT

Read more here:
"Error Message: 403.6 – Forbidden" error when you open an IIS Webpage

"Access Denied" error message when you save a workbook to a UNC share in Excel 2010 or Excel 2013

Assume that there is a Universal Naming Convention (UNC) share for which you do not have Delete permissions. When you try to save an Excel workbook to the UNC share in Microsoft Excel 2010 or Microsoft Excel 2013, you receive the following error message:

Access Denied. Contact your administrator

This issue occurs because Excel tries to delete the temporary copy of the original workbook on the UNC share.

When a user saves an Excel workbook to a UNC share location, Excel creates a temporary copy of the workbook. In the final step of the saving process, Excel deletes the original Excel workbook and replaces it with a temporary copy. If Delete permissions are not granted to the user, Excel cannot complete the saving process, and the user receives the error message that is mentioned in the “Symptoms” section.

To resolve this issue for for Excel 2013 on a computer that has Windows 8 or Windows 8.1 installed or for Excel 2010, apply the following appropriate update and follow the steps in the Registry key information section:
2553034

(http://support.microsoft.com/kb/2553034/
)

Description of the Office 2010 hotfix package (Mso-x-none.msp): August 30, 2011

2889848

(http://support.microsoft.com/kb/2889848/
)

September 9, 2014 update for Office 2013 (KB2889848)

Note To resolve this issue for Excel 2013 on a computer that has Windows 7 installed, you only have to follow the steps in the Registry key information section.

Registry key information

Important This section, method, or task contains steps that tell you how to
modify the registry. However, serious problems might occur if you modify the
registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information
about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/
)

How to back up and restore the registry in Windows

You have to follow these steps to enable the hotfix:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select one of the following registry subkeys:

    For Excel 2010

    HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonGeneral

    For Excel 2013

    HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0CommonGeneral

  3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
  4. Type EnableSimpleCopyForSaveToUNC, and then press ENTER.
  5. In the Details pane, right-click EnableSimpleCopyForSaveToUNC, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.

Limitations

The resolution has the following limitations:

  • If you do not have Delete permissions for the UNC share, the temporary copy of the original workbook is not deleted after you save the workbook.

    Notes

    • To delete the temporary copy of the original workbook, use a script from an account that has Delete permissions. These files follow the .tmp naming scheme and can be safely deleted at any time without affecting Office 2010 and Office 2013.
    • You do not have this limitation if you have Delete permissions for the UNC share.
  • If you are disconnected from the network when you try to save the workbook, the workbook may be corrupted.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

Article ID: 2589410 – Last Review: October 30, 2014 – Revision: 5.0


Applies to
  • Microsoft Excel 2010
  • Microsoft Excel 2013
kbqfe kbsurveynew kbexpertisebeginner kbhotfixallversions KB2589410

View article:
"Access Denied" error message when you save a workbook to a UNC share in Excel 2010 or Excel 2013

Outlook hangs when it connects to an Exchange Online mailbox that was migrated from on-premises Exchange Server

Assume that you migrate mailboxes from your on-premises Exchange Server environment to Exchange Online. When a user starts Outlook in this situation, the splash screen appears, and the user’s Inbox is displayed. However, if the user takes any other action in the Outlook window, the title bar changes to Not Responding and remains like this for several minutes.
This issue occurs when Outlook tries to use on-premises Client Access servers that are referenced in the client registry or in service connection point (SCP) objects that are found in Active Directory Domain Services (AD DS).
Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration

(http://support.microsoft.com/kb/322756/
)

in case problems occur.

To resolve this issue, set the value of the ExcludeSCPLookup DWORD value in the HKEY_CURRENT_USERSoftwareMicrosoftOfficeOutlookAutodiscover registry key to 1. To do this, follow these steps:

  1. Exit Outlook.
  2. Click Start, type regedit in the search box, and then press Enter to open Registry Editor.
  3. Locate and then select the following registry key:

    HKEY_CURRENT_USERSoftwareMicrosoftOfficeOutlookAutoDiscover

    Note In the registry key path, corresponds to the version of Outlook that’s installed:

    • For Outlook 2013, is 15.0
    • For Outlook 2010, is 14.0
    • For Outlook 2007, is 12.0
  4. Do one of the following:
    • If the ExcludeSCPLookup DWORD value already exists, go to step 5.
    • If the ExcludeSCPLookup DWORD value doesn’t exist, create it. To do this, follow these steps:
      1. On the Edit menu, point to New, and then click DWORD Value.
      2. Type ExcludeSCPLookup, and then press Enter.
  5. Right-click ExcludeSCPLookup, click Modify, type 1 in the Value data box, and then click OK.
  6. Exit Registry Editor, and then restart Outlook.

Article ID: 3012603 – Last Review: October 28, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365p o365022013 o365 o365a KB3012603

More:
Outlook hangs when it connects to an Exchange Online mailbox that was migrated from on-premises Exchange Server

Free/busy lookups between Exchange Online and on-premises users don’t work as expected

Free/busy lookups between on-premises Exchange users and Exchange Online users in an Exchange hybrid deployment don’t work correctly. Users see hash marks (\) instead of availability information in their calendars. However, free/busy lookups between on-premises Exchange users still work as expected.
This issue may occur if an accepted domain is missing from the on-premises Exchange organization, the Exchange Online organization or both in the hybrid deployment configuration. 
To resolve this issue, follow these steps:
  1. Make sure that the domain or domains are added to your on-premises organization as accepted domains. For more information, see Accepted domains

    (http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx)

  2. Make sure that the domain or domains are added to Exchange Online as accepted domains. For more information, see Verify a domain at any domain name registrar

    (http://technet.microsoft.com/en-us/library/jj151803.aspx)

    .

  3. Rerun the Hybrid Configuration Wizard. When you’re prompted to add your domain or domains, select the domains that you added. For more information, see step 5 of Create a hybrid deployment with the Hybrid Configuration Wizard

    (http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx)

    .

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

 website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 3012701 – Last Review: October 28, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a hybrid KB3012701

See the original article here:
Free/busy lookups between Exchange Online and on-premises users don’t work as expected

Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 4

This article lists the issues that are fixed in Rollup 1 for Microsoft Forefront Unified Access Gateway (UAG) 2010 Service Pack 4 (SP4).

Issues that are fixed in this rollup package

The issues that are fixed are listed in the following articles. Click the KB number to view the article in the Microsoft Knowledge Base.

Collapse this tableExpand this table

KB number Title
2997481

(http://support.microsoft.com/kb/2997481/
)

FIX: You are not authorized to access applications published through Forefront Unified Access Gateway
2997483

(http://support.microsoft.com/kb/2997483/
)

FIX: Source IP and user name missing from Event ID 14 in the Web Monitor log file
2997485

(http://support.microsoft.com/kb/2997485/
)

FIX: “An unknown error occurred while processing the certificate” error when you access an application that is hosted on an Apache web server
2997486

(http://support.microsoft.com/kb/2997486/
)

FIX: The Forefront Unified Access Gateway portal may be unavailable
2997487

(http://support.microsoft.com/kb/2997487/
)

FIX: “You have attempted to access a restricted URL” error when you try to access OWA and are close to the idle session time-out period
2998352

(http://support.microsoft.com/kb/2998352/
)

FIX: “Your client does not support opening this list with Windows Explorer” error when you try to open a SharePoint document library
2998733

(http://support.microsoft.com/kb/2998733/
)

FIX: You cannot start a RemoteApp application when its name contains accented characters
2998739

(http://support.microsoft.com/kb/2998739/
)

FIX: The VPN connection disconnects immediately when a Unified Access Gateway 2010 client uses SSTP
2998752

(http://support.microsoft.com/kb/2998752/
)

FIX: “Authentication failed” error when you try to log on to Unified Access Gateway by using the UPN format
2998769

(http://support.microsoft.com/kb/2998769/
)

FIX: Exception occurs when you use the Export2Tspub application to export the configuration to a .tspub file
3003977

(http://support.microsoft.com/kb/3003977/
)

FIX: “Sign-in Error” errors for Internet Explorer 11 clients when they access a Unified Access Gateway portal trunk that has ADFS 2.0 authentication
3004023

(http://support.microsoft.com/kb/3004023/
)

FIX: Client connections for Form-based SSO fail authentication in Forefront Unified Access Gateway 2010 SP4
3006827

(http://support.microsoft.com/kb/3006827/
)

FIX: Forefront Unified Access Gateway 2010 template improvements for SharePoint Server 2013
3006828

(http://support.microsoft.com/kb/3006828/
)

FIX: Forefront Unified Access Gateway 2010 template improvements for Exchange Server 2013
3006892

(http://support.microsoft.com/kb/3006892/
)

FIX: Windows Firewall is detected as running after a third-party firewall is installed on a computer that is running Forefront Unified Access Gateway 2010
3006938

(http://support.microsoft.com/kb/3006938/
)

FIX: Soft lockout does not apply if Outlook Anywhere uses KCD for SSO to Exchange Server
3006940

(http://support.microsoft.com/kb/3006940/
)

FIX: Portal toolbar is not displayed in Forefront Unified Access Gateway 2010
3007519

(http://support.microsoft.com/kb/3007519/
)

FIX: “Bind the source IP address to the session” option does not work correctly in Forefront Unified Access Gateway 2010
2997456

(http://support.microsoft.com/kb/2997456/
)

FIX: French client access to Unified Access Gateway trunk by using two-factor authentication fails when user password nears expiration
2997493

(http://support.microsoft.com/kb/2997493/
)

FIX: “Invalid URL path” error when an external user tries to connect to a shared calendar
3007842

(http://support.microsoft.com/kb/3007842/
)

FIX: “The website cannot display the page” or “HTTP 500″ error if the first user logon is unsuccessful
3009885

(http://support.microsoft.com/kb/3009885/
)

FIX: Applications that use the Socket Forwarder component may stop responding in Forefront Unified Access Gateway 2010
3009904

(http://support.microsoft.com/kb/3009904/
)

FIX: “You cannot access this site due to an internal error” error when you log on to Outlook Web App again

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing one or more of these specific problems.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this update, you must be running Service Pack 4

(http://support.microsoft.com/kb/2861386/
)

for Forefront Unified Access Gateway 2010.

Restart requirement

You must restart the computer after you apply this hotfix.

File information

Collapse this imageExpand this image

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Activationmonitor.exe 4.0.4160.10100 244,432 16-Oct-2014 23:11 x86
Adfs.internalsite.inc Not applicable 46,998 12-Feb-2014 04:00 Not applicable
Adfs.postvalidate.asp Not applicable 24,510 16-Oct-2014 22:34 Not applicable
Adfs.whlclientinst.inc Not applicable 1,690 16-Oct-2014 22:34 Not applicable
Agent_lin_helper.jar Not applicable 4,688,758 07-Oct-2014 14:55 Not applicable
Agent_mac_helper.jar Not applicable 3,990,170 07-Oct-2014 15:05 Not applicable
Agent_win_helper.jar Not applicable 2,417,563 07-Oct-2014 15:37 Not applicable
Appwraptemplates.https_whlfiltappwrap_forportal.xml Not applicable 96,093 16-Oct-2014 22:34 Not applicable
Appwraptemplates.http_whlfiltappwrap_forportal.xml Not applicable 93,939 16-Oct-2014 22:34 Not applicable
Boostregex.1.39.dll Not applicable 600,272 16-Oct-2014 23:07 x64
Cegapaceclient.dll 4.0.4160.10100 65,744 16-Oct-2014 23:15 x64
Cegffilestaticwrapper.dll 4.0.4160.10100 21,200 16-Oct-2014 23:16 x64
Certmanagement.dll 4.0.4160.10100 293,072 16-Oct-2014 23:09 x64
Certmapper.dll 4.0.4160.10100 71,888 16-Oct-2014 23:15 x64
Clientcompres.cab Not applicable 264,701 16-Oct-2014 23:26 Not applicable
Clientconf.cab Not applicable 9,322 16-Oct-2014 23:26 Not applicable
Clientconf.xml Not applicable 8,568 16-Oct-2014 21:40 Not applicable
Clientconf.xml.sig Not applicable 128 16-Oct-2014 21:40 Not applicable
Conf.formlogindatadefinitions.xml Not applicable 5,708 04-Feb-2014 16:36 Not applicable
Conf.wizarddefaults.wizarddefaultparam.ini Not applicable 70,709 25-Mar-2014 04:00 Not applicable
Configdatacomlayer.dll 4.0.4160.10100 274,640 16-Oct-2014 23:16 x64
Configdatalayer.dll 4.0.4160.10100 4,255,440 16-Oct-2014 23:19 x64
Configmgrcom.exe 4.0.4160.10100 231,632 16-Oct-2014 23:17 x64
Configmgrcomlayer.dll 4.0.4160.10100 2,587,856 16-Oct-2014 23:09 x64
Configmgrcore.dll 4.0.4160.10100 1,529,040 16-Oct-2014 23:09 x64
Configmgrinfra.dll 4.0.4160.10100 1,860,816 16-Oct-2014 23:16 x64
Configmgrlayer.dll 4.0.4160.10100 278,736 16-Oct-2014 23:12 x64
Configmgrutil.exe 4.0.4160.10100 76,496 16-Oct-2014 23:09 x64
Configuration.exe 4.0.4160.10100 9,873,104 16-Oct-2014 23:13 x64
Cvcore.dll 4.0.4160.10100 138,960 16-Oct-2014 23:17 x64
Da.dca.msi Not applicable 3,530,752 16-Oct-2014 23:14 Not applicable
Danlbcfg.dll 4.0.4160.10100 229,584 16-Oct-2014 23:15 x64
Dasessionmgrwrappercpp.dll 4.0.4160.10100 70,864 16-Oct-2014 23:11 x64
Dawrappercpp.dll 4.0.4160.10100 40,656 16-Oct-2014 23:11 x64
Detection.vbs Not applicable 324,736 16-Oct-2014 23:17 Not applicable
Detectjava.jar Not applicable 6,553 07-Oct-2014 15:50 Not applicable
Editor.exe 4.0.4160.10100 369,360 16-Oct-2014 23:15 x64
Egapsnmpagent.dll 4.0.4160.10100 26,320 16-Oct-2014 23:10 x64
Egfdata.dll 4.0.4160.10100 18,128 16-Oct-2014 23:16 x86
Export2tspub.exe 4.0.4160.10100 64,720 16-Oct-2014 23:17 x86
Iiswrapper.dll 4.0.4160.10100 60,112 16-Oct-2014 23:12 x86
Iiswrappercpp.dll 4.0.4160.10100 78,544 16-Oct-2014 23:07 x64
Internalsite.inc Not applicable 46,998 12-Feb-2014 04:00 Not applicable
Interop.configdatacomlayerlib.dll 4.0.4160.10100 35,536 16-Oct-2014 23:09 x86
Interop.nlbdriver.dll 4.0.4160.10100 17,616 16-Oct-2014 23:13 x86
Interop.testability.oci.dll 4.0.4160.10100 64,208 16-Oct-2014 23:12 x86
Interop.uagmanagementconsole.dll 4.0.4160.10100 14,032 16-Oct-2014 23:07 x86
Localcainstaller.exe 4.0.4160.10100 27,344 16-Oct-2014 23:12 x64
Localcainstallinfra.dll 4.0.4160.10100 56,016 16-Oct-2014 23:14 x86
Logoffmsg.asp Not applicable 8,958 16-Oct-2014 22:34 Not applicable
Metadataparser.dll 4.0.4160.10100 68,304 16-Oct-2014 23:17 x86
Microsoft.uag.adfsv2.interop.monitormgrcomlayerlib.dll 4.0.4160.10100 76,496 16-Oct-2014 23:11 x86
Microsoft.uag.adfsv2.website.dll 4.0.4160.10100 51,920 16-Oct-2014 23:14 x86
Microsoft.uag.certificatehelper.dll 4.0.4160.10100 43,728 16-Oct-2014 23:12 x86
Microsoft.uag.common.dll 4.0.4160.10100 146,128 16-Oct-2014 23:14 x86
Microsoft.uag.monitorhelper.dll 4.0.4160.10100 72,400 16-Oct-2014 23:13 x86
Microsoft.uag.transformer.common.dll 4.0.4160.10100 6,306,512 16-Oct-2014 23:09 x86
Microsoftclient.jar Not applicable 120,787 07-Oct-2014 16:20 Not applicable
Mobileinternalsite.interop.configmgrcomlayerlib.dll 4.0.4160.10100 117,456 16-Oct-2014 23:16 x86
Mobileinternalsite.interop.sessionmgrcomlayerlib.dll 4.0.4160.10100 96,976 16-Oct-2014 23:09 x86
Mobileinternalsite.interop.usermgrcomlayer.dll 4.0.4160.10100 51,920 16-Oct-2014 23:09 x86
Mobileinternalsite.interop.whlcomtracelib.dll 4.0.4160.10100 11,984 16-Oct-2014 23:15 x86
Mobileinternalsite.microsoft.uag.cominterop.dll 4.0.4160.10100 72,400 16-Oct-2014 23:14 x86
Mobileinternalsite.microsoft.uag.exception.dll 4.0.4160.10100 17,104 16-Oct-2014 23:07 x86
Mobileinternalsite.microsoft.uag.mobilebrowsing.dll 4.0.4160.10100 64,208 16-Oct-2014 23:13 x86
Mobileinternalsite.microsoft.uag.mobileinternalsite.dll 4.0.4160.10100 39,632 16-Oct-2014 23:17 x86
Mobileinternalsite.microsoft.uag.traces.dll 4.0.4160.10100 16,080 16-Oct-2014 23:08 x86
Mobileinternalsite.microsoft.uag.usermanager.dll 4.0.4160.10100 19,664 16-Oct-2014 23:10 x86
Mobileinternalsite.microsoft.uag.utility.dll 4.0.4160.10100 22,736 16-Oct-2014 23:08 x86
Monitorlauncher.exe 4.0.4160.10100 42,192 16-Oct-2014 23:16 x64
Monitormgrcom.exe 4.0.4160.10100 179,408 16-Oct-2014 23:13 x64
Monitormgrcomlayer.dll 4.0.4160.10100 1,473,744 16-Oct-2014 23:14 x64
Monitormgrcore.dll 4.0.4160.10100 806,096 16-Oct-2014 23:09 x64
Monitormgrinfra.dll 4.0.4160.10100 1,178,832 16-Oct-2014 23:14 x64
Monitormgrlayer.dll 4.0.4160.10100 441,040 16-Oct-2014 23:09 x64
Monitormgrlayerc.dll 4.0.4160.10100 36,048 16-Oct-2014 23:08 x64
Nlbcore.dll 4.0.4160.10100 203,472 16-Oct-2014 23:09 x64
Nlbmgr.dll 4.0.4160.10100 122,576 16-Oct-2014 23:07 x64
Oc.managedtargets.dll 4.0.4160.10100 17,104 16-Oct-2014 23:09 x86
Oc.registrationtableswrappers.dll 4.0.4160.10100 43,728 16-Oct-2014 23:09 x86
Ocregistrationtables.dll 4.0.4160.10100 245,456 16-Oct-2014 23:11 x64
Ocuagcommon.dll 4.0.4160.10100 18,128 16-Oct-2014 23:11 x64
Oesislocal.jar Not applicable 60,446 07-Oct-2014 18:58 Not applicable
Offlineclientsetup.clientcompres.cab Not applicable 264,701 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.clientconf.cab Not applicable 9,322 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.clientconf.xml Not applicable 8,568 16-Oct-2014 21:40 Not applicable
Offlineclientsetup.clientconf.xml.sig Not applicable 128 16-Oct-2014 21:40 Not applicable
Offlineclientsetup.rsast.cab Not applicable 82,253 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.sfhlprutil.cab Not applicable 66,248 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.uagqec.cab Not applicable 71,930 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlcache.cab Not applicable 274,725 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlclntproxy.cab Not applicable 253,336 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlcompmgr.cab Not applicable 1,076,085 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whldetector.cab Not applicable 272,690 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlio.cab Not applicable 198,113 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whllln.cab Not applicable 177,425 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlllnconf1.cab Not applicable 7,409 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlllnconf2.cab Not applicable 7,498 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whlllnconf3.cab Not applicable 7,487 16-Oct-2014 23:26 Not applicable
Offlineclientsetup.whltrace.cab Not applicable 260,996 16-Oct-2014 23:26 Not applicable
Otp.whlclientinst.inc Not applicable 1,690 16-Oct-2014 22:34 Not applicable
Owa.flogon.js Not applicable 10,010 05-Mar-2014 04:00 Not applicable
Owa.login.asp Not applicable 30,464 27-Mar-2014 04:00 Not applicable
Owa.logoffmsg.asp Not applicable 8,137 05-Mar-2014 04:00 Not applicable
Passwordexpired.asp Not applicable 2,262 16-Oct-2014 22:34 Not applicable
Portalhomepage.bin.interop.configmgrcomlayerlib.dll 4.0.4160.10100 117,456 16-Oct-2014 23:16 x86
Portalhomepage.bin.interop.monitormgrcomlayerlib.dll 4.0.4160.10100 76,496 16-Oct-2014 23:11 x86
Portalhomepage.bin.interop.sessionmgrcomlayerlib.dll 4.0.4160.10100 96,976 16-Oct-2014 23:09 x86
Portalhomepage.bin.interop.whlcomtracelib.dll 4.0.4160.10100 11,984 16-Oct-2014 23:15 x86
Portalhomepage.bin.microsoft.uag.cominterop.dll 4.0.4160.10100 72,400 16-Oct-2014 23:14 x86
Portalhomepage.bin.microsoft.uag.detectionagent.dll 4.0.4160.10100 43,728 16-Oct-2014 23:14 x86
Portalhomepage.bin.microsoft.uag.exception.dll 4.0.4160.10100 17,104 16-Oct-2014 23:07 x86
Portalhomepage.bin.microsoft.uag.expressioneval.dll 4.0.4160.10100 14,544 16-Oct-2014 23:07 x86
Portalhomepage.bin.microsoft.uag.locators.dll 4.0.4160.10100 60,112 16-Oct-2014 23:15 x86
Portalhomepage.bin.microsoft.uag.portal.core.dll 4.0.4160.10100 43,728 16-Oct-2014 23:11 x86
Portalhomepage.bin.microsoft.uag.portal.handlers.dll 4.0.4160.10100 43,728 16-Oct-2014 23:10 x86
Portalhomepage.bin.microsoft.uag.portal.model.dll 4.0.4160.10100 105,168 16-Oct-2014 23:14 x86
Portalhomepage.bin.microsoft.uag.portal.navigation.dll 4.0.4160.10100 56,016 16-Oct-2014 23:17 x86
Portalhomepage.bin.microsoft.uag.portal.ui.dll 4.0.4160.10100 39,632 16-Oct-2014 23:15 x86
Portalhomepage.bin.microsoft.uag.portal.util.dll 4.0.4160.10100 51,920 16-Oct-2014 23:09 x86
Portalhomepage.bin.microsoft.uag.portal.virtualpaths.dll 4.0.4160.10100 43,728 16-Oct-2014 23:15 x86
Portalhomepage.bin.microsoft.uag.portal.website.dll 4.0.4160.10100 56,016 16-Oct-2014 23:12 x86
Portalhomepage.bin.microsoft.uag.traces.dll 4.0.4160.10100 16,080 16-Oct-2014 23:08 x86
Portalhomepage.bin.microsoft.uag.ui.dll 4.0.4160.10100 76,496 16-Oct-2014 23:07 x86
Portalhomepage.bin.microsoft.uag.utility.dll 4.0.4160.10100 22,736 16-Oct-2014 23:08 x86
Portalhomepage.bin.portal.modules.dll 4.0.4160.10100 39,632 16-Oct-2014 23:15 x86
Portalhomepage.whlclientsetup_all.msi Not applicable 3,813,376 16-Oct-2014 23:14 Not applicable
Portalhomepage.whlclientsetup_basic.msi Not applicable 3,813,376 16-Oct-2014 23:16 Not applicable
Portalhomepage.whlclientsetup_networkconnector.msi Not applicable 3,813,376 16-Oct-2014 23:14 Not applicable
Portalhomepage.whlclientsetup_networkconnectoronly.msi Not applicable 3,813,376 16-Oct-2014 23:09 Not applicable
Portalhomepage.whlclientsetup_socketforwarder.msi Not applicable 3,813,376 16-Oct-2014 23:16 Not applicable
Postvalidate.asp Not applicable 24,510 16-Oct-2014 22:34 Not applicable
Rsast.cab Not applicable 82,253 16-Oct-2014 23:26 Not applicable
Ruleset.level0.ruleset_forexchangepub2010.ini Not applicable 20,940 20-May-2014 03:00 Not applicable
Ruleset.level0.ruleset_forexchangepub2013.ini Not applicable 27,766 30-May-2014 08:43 Not applicable
Ruleset.level0.ruleset_forsharepoint15.ini Not applicable 27,325 25-Apr-2014 11:08 Not applicable
Ruleset.level0.ruleset_forsts.ini Not applicable 810 20-Jun-2014 03:00 Not applicable
Ruleset.level1.ruleset_forexchangepub2010.ini Not applicable 20,940 20-May-2014 03:00 Not applicable
Ruleset.level1.ruleset_forexchangepub2013.ini Not applicable 27,766 30-May-2014 08:43 Not applicable
Ruleset.level1.ruleset_forsharepoint15.ini Not applicable 27,325 25-Apr-2014 11:08 Not applicable
Ruleset.level2.ruleset_forexchangepub2010.ini Not applicable 20,940 20-May-2014 03:00 Not applicable
Ruleset.level2.ruleset_forexchangepub2013.ini Not applicable 27,766 30-May-2014 08:43 Not applicable
Ruleset.level2.ruleset_forsharepoint15.ini Not applicable 27,325 25-Apr-2014 11:08 Not applicable
Ruleset.level3.ruleset_forexchangepub2010.ini Not applicable 20,940 20-May-2014 03:00 Not applicable
Ruleset.level3.ruleset_forexchangepub2013.ini Not applicable 27,766 30-May-2014 08:43 Not applicable
Ruleset.level3.ruleset_forsharepoint15.ini Not applicable 27,325 25-Apr-2014 11:08 Not applicable
Runtimeelevator.jar Not applicable 7,453 07-Oct-2014 18:43 Not applicable
Sessionmgrclient.dll 4.0.4160.10100 87,760 16-Oct-2014 23:08 x64
Sessionmgrcom.exe 4.0.4160.10100 360,144 16-Oct-2014 23:08 x64
Sessionmgrcomlayer.dll 4.0.4160.10100 2,078,928 16-Oct-2014 23:10 x64
Sessionmgrcore.dll 4.0.4160.10100 842,960 16-Oct-2014 23:17 x64
Sessionmgrinfra.dll 4.0.4160.10100 1,481,936 16-Oct-2014 23:17 x64
Sessionmgrlayer.dll 4.0.4160.10100 318,672 16-Oct-2014 23:18 x64
Sessionmgrnotifier.dll 4.0.4160.10100 45,264 16-Oct-2014 23:13 x64
Sfhlprutil.cab Not applicable 66,248 16-Oct-2014 23:26 Not applicable
Sp4_sp4ru1.diffpkg Not applicable 52,311 26-Jun-2014 03:00 Not applicable
Sslbox.dll 4.0.4160.10100 77,520 16-Oct-2014 23:13 x64
Sslvpnclient.jar Not applicable 311,434 07-Oct-2014 14:46 Not applicable
Tacacslib.dll 4.0.4160.10100 24,784 16-Oct-2014 23:13 x64
Testability.ocit.dll 4.0.4160.10100 146,128 16-Oct-2014 23:13 x86
Uagnetsh.dll 4.0.4160.10100 44,240 16-Oct-2014 23:16 x64
Uagqec.cab Not applicable 71,930 16-Oct-2014 23:26 Not applicable
Uagqessvc.exe 4.0.4160.10100 209,616 16-Oct-2014 23:15 x64
Uagrdpsvc.exe 4.0.4160.10100 150,224 16-Oct-2014 23:10 x64
Uagschemaupgradeutil.exe 4.0.4160.10100 1,055,440 16-Oct-2014 23:16 x86
Uagsstp.dll 4.0.4160.10100 103,120 16-Oct-2014 23:11 x64
Uninstalluagupdate.cmd Not applicable 183 16-Oct-2014 23:32 Not applicable
Uninstalluagupdate.exe 8.0.7600.16385 178,384 16-Oct-2014 23:13 x64
Usermgrcom.exe 4.0.4160.10100 139,472 16-Oct-2014 23:14 x64
Usermgrcomlayer.dll 4.0.4160.10100 839,376 16-Oct-2014 23:16 x64
Usermgrcore.dll 4.0.4160.10100 1,022,160 16-Oct-2014 23:09 x64
Usermgrinfra.dll 4.0.4160.10100 638,672 16-Oct-2014 23:15 x64
Usermgrlayer.dll 4.0.4160.10100 89,808 16-Oct-2014 23:11 x64
Whladfshelper.dll 4.0.4160.10100 79,568 16-Oct-2014 23:12 x64
Whlasynccomm.dll 4.0.4160.10100 130,256 16-Oct-2014 23:17 x64
Whlcache.cab Not applicable 274,725 16-Oct-2014 23:26 Not applicable
Whlclientinst.inc Not applicable 1,690 16-Oct-2014 22:34 Not applicable
Whlclntproxy.cab Not applicable 253,336 16-Oct-2014 23:26 Not applicable
Whlcompmgr.cab Not applicable 1,076,085 16-Oct-2014 23:26 Not applicable
Whlcomtrace.dll 4.0.4160.10100 48,848 16-Oct-2014 23:09 x64
Whlcomtracelib.dll 4.0.4160.10100 11,472 16-Oct-2014 23:12 x86
Whlcppinfra.dll 4.0.4160.10100 817,872 16-Oct-2014 23:18 x64
Whlcrypt.dll 4.0.4160.10100 41,168 16-Oct-2014 23:12 x64
Whlcspgeneral.dll 4.0.4160.10100 25,808 16-Oct-2014 23:11 x64
Whlcspmanager.dll 4.0.4160.10100 45,776 16-Oct-2014 23:18 x64
Whlcspssl.dll 4.0.4160.10100 175,312 16-Oct-2014 23:14 x64
Whldetector.cab Not applicable 272,690 16-Oct-2014 23:26 Not applicable
Whlds.dll 4.0.4160.10100 46,800 16-Oct-2014 23:18 x64
Whlerrsrvd.exe 4.0.4160.10100 42,192 16-Oct-2014 23:08 x64
Whlfiltappwrap.dll 4.0.4160.10100 341,712 16-Oct-2014 23:16 x64
Whlfiltauthorization.dll 4.0.4160.10100 390,864 16-Oct-2014 23:12 x64
Whlfiltencoding.dll 4.0.4160.10100 54,480 16-Oct-2014 23:08 x64
Whlfilter.dll 4.0.4160.10100 946,384 16-Oct-2014 23:09 x64
Whlfiltformlogin.dll 4.0.4160.10100 367,824 16-Oct-2014 23:16 x64
Whlfiltlogoff.dll 4.0.4160.10100 195,792 16-Oct-2014 23:17 x64
Whlfiltparamremove.dll 4.0.4160.10100 35,024 16-Oct-2014 23:14 x64
Whlfiltrecorder.dll 4.0.4160.10100 92,880 16-Oct-2014 23:15 x64
Whlfiltruleset.dll 4.0.4160.10100 653,008 16-Oct-2014 23:15 x64
Whlfiltsecureremote.dll 4.0.4160.10100 1,136,336 16-Oct-2014 23:16 x64
Whlfiltsnt.dll 4.0.4160.10100 177,360 16-Oct-2014 23:09 x64
Whlfiltsslvpn.dll 4.0.4160.10100 287,952 16-Oct-2014 23:11 x64
Whlfiltsso.dll 4.0.4160.10100 56,528 16-Oct-2014 23:12 x64
Whlfirewallinfra.dll 4.0.4160.10100 515,280 16-Oct-2014 23:11 x64
Whlgenlib.dll 4.0.4160.10100 583,376 16-Oct-2014 23:07 x64
Whlglobalutilities.dll 4.0.4160.10100 112,848 16-Oct-2014 23:10 x64
Whlgzip.dll 4.0.4160.10100 78,032 16-Oct-2014 23:17 x64
Whlhttpparser.dll 4.0.4160.10100 104,656 16-Oct-2014 23:14 x64
Whlio.cab Not applicable 198,113 16-Oct-2014 23:26 Not applicable
Whlioapi.dll 4.0.4160.10100 77,008 16-Oct-2014 23:14 x64
Whliolic.dll 4.0.4160.10100 16,592 16-Oct-2014 23:14 x64
Whlios.exe 4.0.4160.10100 138,960 16-Oct-2014 23:09 x64
Whllln.cab Not applicable 177,425 16-Oct-2014 23:26 Not applicable
Whlllnconf1.cab Not applicable 7,409 16-Oct-2014 23:26 Not applicable
Whlllnconf2.cab Not applicable 7,498 16-Oct-2014 23:26 Not applicable
Whlllnconf3.cab Not applicable 7,487 16-Oct-2014 23:26 Not applicable
Whlmgr.dll 4.0.4160.10100 1,147,088 16-Oct-2014 21:36 x86
Whlowa2013.js Not applicable 536 06-Mar-2014 04:00 Not applicable
Whlradiusauth.dll 4.0.4160.10100 102,608 16-Oct-2014 23:09 x64
Whlrdpmng.dll 4.0.4160.10100 168,144 16-Oct-2014 23:09 x64
Whlsecurityutilities.dll 4.0.4160.10100 288,976 16-Oct-2014 23:09 x64
Whlserverproxy.dll 4.0.4160.10100 478,416 16-Oct-2014 23:08 x64
Whlsocket.dll 4.0.4160.10100 84,176 16-Oct-2014 23:15 x64
Whlsqm.dll 4.0.4160.10100 36,560 16-Oct-2014 23:09 x64
Whlsqm.exe 4.0.4160.10100 26,832 16-Oct-2014 23:17 x86
Whlssocrypt.dll 4.0.4160.10100 81,616 16-Oct-2014 23:08 x64
Whltrace.cab Not applicable 260,996 16-Oct-2014 23:26 Not applicable
Whltrace.dll 4.0.4160.10100 92,880 16-Oct-2014 23:18 x64
Whltsgauth.dll 4.0.4160.10100 203,984 16-Oct-2014 23:15 x64
Whltsgconf.dll 4.0.4160.10100 91,344 16-Oct-2014 23:13 x64
Whltsgconfig.exe 4.0.4160.10100 17,104 16-Oct-2014 23:14 x86
Whlvaw_srv.dll 4.0.4160.10100 138,960 16-Oct-2014 23:08 x64
Whlwflbcore.dll 4.0.4160.10100 107,728 16-Oct-2014 23:11 x64
Wioconfig.dll 4.0.4160.10100 507,600 16-Oct-2014 23:18 x64
Xmlog.dll 4.0.4160.10100 34,512 16-Oct-2014 23:13 x64

Collapse this imageExpand this image

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 2922171 – Last Review: October 28, 2014 – Revision: 2.0


Applies to
  • Microsoft Forefront Unified Access Gateway 2010
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew kbbug KB2922171

Read this article:
Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 4

FIX: "Bind the source IP address to the session" option does not work correctly in Forefront Unified Access Gateway 2010

After Service Pack 2 (SP2) for Microsoft Forefront Unified Access Gateway 2010 is installed, the Bind the source IP address to the session setting doesn’t work when it is selected on the Session tab of the Advanced Trunk Configuration dialog box. Even when this optional setting is selected, TCP connections from Unified Access Gateway to the back-end published resource do not use the IP address that’s defined in the Unified Access Gateway PostPostValidate.inc file. Instead, these connections use the primary IP address that’s defined on the Unified Access Gateway internal network adapter.
This problem occurs because of the Session Parameter updates in SP2 for Forefront Unified Access Gateway 2010 and later updates.
This problem is fixed in Rollup 1

(http://support.microsoft.com/kb/2922171/
)

for Forefront Unified Access Gateway 2010 Service Pack 4.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the Bind the source IP address to the session

(http://blogs.technet.com/b/edgeaccessblog/archive/2010/03/18/what-is-the-bind-the-source-ip-address-to-the-session-option.aspx)

option.

Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 3007519 – Last Review: October 28, 2014 – Revision: 1.0


Applies to
  • Microsoft Forefront Unified Access Gateway 2010, when used with:
    • Microsoft Forefront Unified Access Gateway 2010 Service Pack 4
    • Microsoft Forefront Unified Access Gateway 2010 Service Pack 3
    • Microsoft Forefront Unified Access Gateway 2010 Service Pack 2
kbqfe kbfix kbexpertiseinter kbsurveynew kbbug KB3007519

Originally posted here:
FIX: "Bind the source IP address to the session" option does not work correctly in Forefront Unified Access Gateway 2010

FIX: Forefront Unified Access Gateway 2010 template improvements for Exchange Server 2013

Rollup 1 for Microsoft Forefront Unified Access Gateway (UAG) Service Pack 4 (SP4) contains several changes to the Exchange Server 2013 template that fixes bugs and improves integration.
This problem is fixed in Rollup 1

(http://support.microsoft.com/kb/2922171/
)

for Forefront UAG 2010 SP4.

Rollup 1 for Forefront UAG 2010 SP4 contains changes to the Exchange Server 2013 Template, URLSet, and AppWrap configuration.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 3006828 – Last Review: October 28, 2014 – Revision: 1.0


Applies to
  • Microsoft Forefront Unified Access Gateway 2010, when used with:
    • Microsoft Exchange Server 2013 Enterprise
kbqfe kbfix kbexpertiseinter kbsurveynew kbbug KB3006828

Read the original:
FIX: Forefront Unified Access Gateway 2010 template improvements for Exchange Server 2013

FIX: Soft lockout does not apply if Outlook Anywhere uses KCD for SSO to Exchange Server

You configure Microsoft Forefront Unified Access Gateway (UAG) 2010 to perform a soft lockout on a user after several failed authentication tries. If you also configure Microsoft Outlook Anywhere to use Kerberos Constrained Delegation (KCD) for Single Sign-On (SSO) access to Microsoft Exchange Server, you find that the soft lockout process does not apply.

In this configuration, Outlook authenticates to UAG by using NTLM authentication.

This problem occurs because the “Integrated Windows Authentication” handler in UAG does not check the account lockout status correctly.
This problem is fixed in Rollup 1

(http://support.microsoft.com/kb/2922171/
)

for Microsoft Forefront Unified Access Gateway 2010 Service Pack 4 (SP4).

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 3006938 – Last Review: October 28, 2014 – Revision: 1.0


Applies to
  • Microsoft Forefront Unified Access Gateway 2010
kbqfe kbfix kbexpertiseinter kbsurveynew kbbug KB3006938

Continue reading here:
FIX: Soft lockout does not apply if Outlook Anywhere uses KCD for SSO to Exchange Server

Page 1 of 75212345...102030...Last »

Recent Comments

    Archives

    Categories