Microsoft KB Archive/815362

= Exchange SDK: Application Templates Notes and Removal =

Article ID: 815362

Article Last Modified on 5/9/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Enterprise Server

-



IN THIS TASK

 * SUMMARY
 * Application Templates Security Considerations
 * The Setup Wizard May Enable Anonymous Access
 * Set Script Execute Permissions for Public Folders to Permit Scripts to Run
 * You Cannot Install the Application Templates on Exchange 2000 Server Service Pack 2 (SP2) or Later Versions
 * A User May Have Elevated Privileges in the TeamToDo Application Template If the User Is Assigned to the COM+ &quot;Can Register Workflow&quot; Role
 * Application Template Removal
 * The GroupCalendar and TeamToDo Applications Require a Workflow Identity Account That Is a Member of the Exchange Domain Servers Group
 * How to Manually Remove the Application Templates
 * How to Remove Multiple Installations of the Application Templates
 * How to Remove the TeamToDo Application DLL File
 * How to Remove the Application Template Web Form Registration
 * REFERENCES



SUMMARY
The Microsoft Exchange Application Templates are no longer available for download, and the documentation was removed from the Exchange software development kit (SDK).

To develop collaboration applications that function like the Exchange Application Templates, Microsoft recommends that you use the Microsoft SharePoint Portal Server platform. See the &quot;Issue Tracking Application&quot; topic in the Exchange SDK for an example of an application with a recommended architecture.

Application Templates Security Considerations
The following list describes security considerations that apply to the Application Templates:  ==== The Setup Wizard May Enable Anonymous Access ====

The Setup Wizard may enable Anonymous Access for each application folder if the parent public folder is configured for Anonymous Access. The Application Templates Readme file and the Exchange SDK documentation incorrectly instruct you to enable Anonymous Access for the default Web site.

back to the top  ==== Set Script Execute Permissions for Public Folders to Permit Scripts to Run ====

When you deploy the Application Templates in a public folder, Script Execute permissions are not set on the folder. Therefore, the scripts cannot run. If you try to open the Application Templates before you set Script Execute permissions, you receive the following error:

Error 403: &quot;Not authorized&quot;

back to the top  ==== You Cannot Install the Application Templates on Exchange 2000 Server Service Pack 2 (SP2) or Later Versions ====

You must install the Application Templates on a computer that is running Exchange 2000 Server SP1. However, it is highly recommended that you install the latest service packs to obtain the latest security patches. If you deploy the Application Templates on an Exchange 2000 SP1 server, the Application Templates continue to work when Exchange 2000 SP2 or later is installed. After you install Exchange 2000 SP2 or later, you cannot use the Setup Wizard to install the Application Templates.

back to the top  ==== A User May Have Elevated Privileges in the TeamToDo Application Template If the User Is Assigned to the COM+ &quot;Can Register Workflow&quot; Role ====

A user may be assigned to the COM+ “Can Register Workflow” role. However, if the user is assigned to the TeamToDo “Reader” role in the Managed Users page, the user can still use the Application Templates to create new tasks because the COM+ role overrides the role permissions that the application sets.

back to the top 

Application Template Removal
To remove the Application Templates, run the Application Templates Setup Wizard, and then select the uninstall option to remove the Application Templates. The following list describes additional steps that you may have to complete to fully remove the templates:  ==== The GroupCalendar and TeamToDo Applications Require a Workflow Identity Account That Is a Member of the Exchange Domain Servers Group ====

If you remove the Application Templates, the workflow identity account is not removed. If this account is not being used in other workflow applications, remove it manually.

back to the top  ==== How to Manually Remove the Application Templates ====

If the Application Templates Setup Wizard is not available, you must manually remove the templates. To do this, follow these steps: <ol> Remove each virtual directory that contains Application Templates installations.</li> If the TeamToDo applications are installed, use the procedure in the “Remove the TeamToDo Application DLL” section of this article to remove the Todo.dll file.</li></ol>

back to the top </li> ==== How to Remove Multiple Installations of the Application Templates ====

If you installed the Application Templates multiple times, you must remove each installation separately. If you installed the TeamToDo application multiple times, you only have to remove the Todo.dll file one time.

back to the top </li> ==== How to Remove the TeamToDo Application DLL ====

When the TeamToDo application is installed, the application puts a copy of the Todo.dll file in the Program Files\Exchsrvr\Exchweb\Bin folder. The Application Templates Setup Wizard does not remove or unregister this DLL. To manually unregister and delete the DLL, follow these steps <ol>  Open a command prompt in the folder that contains the DLL, and then type the following command: <pre class="fixed_text">regsvr32 /u todo.dll </li> Delete the Todo.dll file.</li></ol>

back to the top </li> ==== How to Remove the Application Template Web Form Registration ====

If you manually delete the Application Templates files but do not delete the folders that contain the templates, the hidden files that contain the registration may remain in the Resources folder. To remove the Web form registration, delete the Application Templates folders. If you use the Application Template Setup Wizard to remove the templates, the application folders are automatically removed.

back to the top </li></ul>

<div class="references_section">