Remote Storage recall notifications do not work in Windows XP Service Pack 2 or in Windows XP Tablet PC Edition 2005

After you upgrade to Microsoft Windows XP Service Pack 2 (SP2) or to Windows XP Tablet PC Edition 2005, if you open a file on a share where Remote Storage is turned on, you may not receive a "Recall in progress" notification if the file is out on tape. However, the file is still recalled and available for your use.

This behavior occurs because of DCOM hardening and firewall changes in Windows XP SP2. Because of these changes, Windows XP no longer sends recall notifications in Remote Storage.

Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

If you must re-enable Remote Storage recall notifications, use one of the following methods:

• Add anonymous access to DCOM limits in Component Services.
• Add RsNotify.exe and TCP port 135 to your firewall exception list.

Add anonymous access to DCOM limits in Component Services

Note We do not recommend that you add anonymous access and start permissions to the DCOM computer-wide limits. Adding these permissions relaxes the computer-wide limitations for remote access. Therefore, follow these steps only if you must continue to receive recall notifications on the client computers.

To add anonymous access to DCOM limits in Component Services, follow these steps:

1. Click Start, click Run, type dcomcnfg.exe in the Open box, and then click OK.
2. Locate the Console Root node, expand Component Services, expand Computers, and then click My Computer.
3. If you receive a Windows Security Alert, click Unblock to unblock Microsoft Management Console.
4. Right-click My Computer, and then click Properties.
5. In My Computer Properties, click the COM Security tab.
6. In the Access Permissions area, click Edit Limits.
7. Click Add, type Anonymous Logon, and then click OK.
8. In Permissions for Anonymous Logon, click to select all the Allow settings, and then click OK.
9. In the Launch and Activation Permissions area, click Edit Limits.
10. Click Add, type Anonymous Logon, and then click OK.
11. In Permissions for Anonymous Logon, click to select all the Allow settings, and then click OK.
12. Click OK, and then quit Component Services.

Add RsNotify.exe and TCP port 135 to your firewall exception list

1. Click Start, click Run, type Firewall.cpl in the Open box, and then click OK.
2. On the Exceptions tab, click Add Program.
3. Click Browse, locate the Rsnotify.exe file, and then click OK.
   
   Note By default, the file is located in the Installation drive:\Windows\System32 folder.
4. In the Programs and Services list, click the Rsnotify option button.
5. On the Exceptions tab, click Add Port.
6. In the Port number text box, type 135, and then click the TCP option button.
7. In the Name text box, type RsNotify for the exception, and then click OK.
8. In the Windows Firewall dialog box, click RsNotify in the Programs and Services list, and then click OK.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.