Loadsim Tool ------------ You can use Load Simulator to test how your messaging server performs under different message loads. You can define specific workloads in Load Simulator to test servers in a controlled manner. This allows you to accurately study server behavior under specific conditions. You can use this information to help determine the optimum number of users per server, locate performance bottlenecks, and evaluate server hardware performance. Installing Loadsim ------------------ You can install Loadsim by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install Loadsim 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Admin\Loadsim. 2. Copy loadsim.exe, loadout.dll, and lslog.exe to your local disk. Using Loadsim ------------- Running a Load Simulator Test ----------------------------- 1. Set up your Load Simulator topology. 2. Configure your test properties and customize the user profile, if necessary. 3. Create and initialize mailboxes. 4. Run the test. 5. Generate a score. 6. Analyze the data. 7. Modify and repeat the test, if necessary. Defining the Topology --------------------- You must specify the names of servers that support user mailboxes, how many users will connect from each type of client, the security account to use, the number and size of distribution lists, and the number and depth of the public folder hierarchy. Review the topology and workload to verify that it reflects the behavior of your users. 1. On the Load Simulator Configuration menu, choose Topology Properties. 2. To add servers to your test, click Add, and then type the name of the server you want to include. 3. Select Custom Properties to configure the public folders for each server as well as the messages contained in the folders. 4. Set the server and location properties: Admin Group, Organization, and Internet Address. 5. Click the Users tab. 6. Enter the number of users for each protocol, and then click Set to save the changes for each protocol. 7. Click OK. 8. Click OK. 9. Click the Security tab. 10. Select Use one account for all users. Enter account names in domain\user format. 11. To customize distribution lists, click the Distribution Lists tab, and then select Use distribution lists. Configure the number and size of the distribution lists. 12. Click OK. 13. On the File menu, click Save As to save the .sim file. Note When running Outlook client modules, you must use a single Windows 2000 account. Using only one account has a negligible affect on the results of the experiment because the users stay connected instead of being connected and disconnected. Configuring Test Properties --------------------------- 1. In the Load Simulator program, click Test Properties on the Configuration menu. 2. In the Duration of simulation text box, set the amount of time the test will run. The recommended length is five hours. 3. In the Length of daytime text box, enter the number of hours in your business day. The default is eight hours. This value indicates how long users take to complete a day's tasks. 4. In the Length of nighttime text box, enter the number of hours your server is inactive each day. The default value is zero hours. Setting this value to a number greater than zero simulates a period of inactivity. 5. To add a user group to your test, click Add. 6. In the Edit User Group dialog box, configure the properties for each user group. Option Description Server The name of the Microsoft Exchange 2000 Server computer where the user group's mailboxes reside. Protocol The messaging protocol the user group uses to communicate with the Microsoft Exchange 2000 Server computer. User type The workload the users emulate. Choose a standard profile, or customize a profile by choosing Edit Tasks in the Customize Test dialog box. Client machine The name of the computer running Load Simulator that emulates the user group. First user The number of the first user in the user group. Loadsim.exe creates aliases in the format of -<#> where # starts at 0 and continues for the number of users using the same protocol on the same server. You use First user to specify the first user in the series. For example, if you have 100 Outlook users on ServerA, their aliases would be ServerA-Outl0 to ServerA-Outl99. If you want the first 50 users on a certain client, enter 0 in First user and 50 in Number of users. Number of users The number of users in the user group. To customize your user groups box --------------------------------- 1. In the Test Properties dialog box, select the user group you want to customize in the User groups list, and then click Customize. 2. Click the Tasks tab. 3. Select each task, and then select Enable/Disable task to choose whether that task is activated. 4. Select Edit tasks to customize each task in the user group. 5. Click OK to save your changes and close the Test dialog box. 6. Click the Test/Logon tab in the Customize dialog box. 7. Choose the Logon/logoff properties options you want to enable. 8. Click the Initialization tab. Note You can view the predicted message traffic that Load Simulator will generate based on your settings, in the test report section. 9. Enter the values that you want Load Simulator to use when initializing Microsoft Exchange 2000 Server Web Storage System. 10. Click OK to save your changes. Creating and Initializing Mailboxes ----------------------------------- You must create Address Book entries for the users and distribution lists that will be used in the experiment, and then initialize the mailboxes. You must delete the existing distribution lists before running Load Simulator again. Creating a new topology will only increase the size of the existing distribution lists, not replace them. Deleting mailboxes and distribution lists ensures consistent starting conditions for each experiment. To ensure consistent starting conditions ---------------------------------------- 1. Stop the information store service. 2. Delete the database files Priv.edb and Pub.edb. Delete the edb*.log file in the information store log directory. 3. Restart the information store. 4. In the Microsoft Exchange Server System Administrator, delete all entries in the Load Simulator container for the sites you are using in this test. Skip this step if you have not run Load Simulator before. The Load Simulator container does not exist until you choose Create Topology on the Run menu in Load Simulator for the first time. Creating Mailboxes ------------------ After the system is in a clean state, you can import mailboxes and distribution lists using Load Simulator. 1. In the Load Simulator program, click Create Topology on the Run menu to import mailboxes and distribution lists into the directory. 2. On the Run menu, click Initialize Test to populate the mailboxes and public folder tree with folders and messages. Note Any Load Simulator client computer can create the entire topology if you copied the same .sim file to all clients. You should create the topology from a single client computer in a multi-client experiment. As Load Simulator creates your topology, Creating mailbox and Creating DL messages are displayed in the Load Simulator window and in the log file. If you see the message Modifying dl, click Stop Now on the Run menu to stop creating the topology. The message indicates that users are being added to the distribution lists, which will cause the lists to be larger than specified. Before creating the test topology again, delete the distribution lists so the number of users per distribution list is correct. Initializing Mailboxes ---------------------- Initializing mailboxes gives your tests a more realistic starting condition. During initialization, the Microsoft Exchange and Outlook modules create and populate a folder hierarchy for each user in the topology. 1. On each client computer, click Initialize Test on the Run menu. 2. Choose whether or not to initialize public folders. Note Although the initialization step must be performed on each client computer, the initialization of public folders should only be done on one client computer per organization. Running a Test -------------- A typical test with a medium number of users (2,500 to 3,200) takes five hours. You must run your experiment for at least two hours to allow an adequate warm-up time and run length. This means allowing the clients to reach a steady-state load pattern and allowing the server to reach a steady-state behavior pattern. The server reaches a steady-state behavior pattern after it starts up and code is paged into memory as it is executed for the first time. If the information store database is new, more b-tree activity can occur as index pages split. The server is not in a steady-state behavior pattern until this activity level decreases. After the system is in a steady-state, let it run long enough to collect statistically significant data. The amount of time this takes depends on the complexity of the user model, and the cumulative rate at which user actions are being generated. Make a long calibration run before running your real experiments. For example, if you make an eight-hour run and find variation from hour to hour, but not between two-hour segments, the results are consistent. This indicates that you should do runs of two hours or more of steady-state behavior in your experiments. In general, the more users you have, the shorter the run must be. For best results, start the Windows Performance Monitor program on the server and client computers to collect information about resource usage. To run a test ------------- In the Load Simulator program, click Run Simulation on the Run menu on each client computer. Load Simulator will generate user actions at the rates specified and run them against the servers. When the scenario is running, messages about actions that are being performed and the users performing them are displayed in the Load Simulator window. These messages are also logged to the Loadsim.out file. Timing information that will later be used to generate scores is written to the Lsperf.log file. The test runs for the duration specified in the test properties. You can stop it at any time by selecting Shut Down or Stop Now on the Run menu. Stop Now immediately stops all client activity. Shut Down performs an orderly logoff of the clients. After the scenario is run, rename the Lsperf.log and Loadsim.out files so they are not overwritten on the next run. Also, check the Loadsim.out file for error messages. Depending on the type and number of errors that occurred, the entire test might be invalid. Generating the Score -------------------- The Lsperf.log file is generated when Load Simulator is run. It contains the individual response times for the generated actions. The actions listed vary by protocol. The data is recorded in comma-separated value format. The third field is the time in milliseconds for the server to complete the action. The following is a sample of the information contained in the Lsperf.log file. Date/Time,Action,Time(ms),Unique ID,Weight,Module Nov 02 10:19:44,FORWARD,688,0x000001c4,1,exch Nov 02 10:19:44,READ,203,0x000001c4,1,exch Nov 02 10:19:46,RESOLVE NAME,203,0x000001c4,1,exch Nov 02 10:19:46,SUBMIT,422,0x000001c4,1,exch Nov 02 10:19:46,FORWARD,735,0x000001c4,1,exch Nov 02 10:19:46,READ,156,0x000001c4,1,exch Nov 02 10:19:48,DELETE,484,0x000001c4,1,exch Nov 02 10:19:48,READ,563,0x000001c4,1,exch Nov 02 10:19:50,DELETE,375,0x000001c4,1,exch Nov 02 10:21:02,READ,359,0x00000130,1,exch Nov 02 10:21:04,SUBMIT,297,0x00000130,1,exch Nov 02 10:21:04,REPLY,344,0x00000130,1,exch Nov 02 10:22:09,S+ CHANGE,453,0x000001ca,1,exch You can use the Load Simulator Log (Lslog.exe) program and the Lsperf.log files to generate a score. Lslog.exe generates 95th percentile scores, 50th percentile scores, mean, and standard deviation by default for all the user actions in your experiment. If a Resolve Name/ command takes 200 milliseconds at the 95th percentile, it means that 95 times out of 100 the Resolve Name command takes less than 200 milliseconds to complete. For more information about Lslog.exe, type Lslog at a command prompt. To generate the score --------------------- 1. If your experiment used more than one client, you must copy all the log files to one directory and use Lslog.exe to merge the logs into one time-ordered log file like in the following example. lslog merge client?.log >run1.log 2. Truncate log entries that are in the warm-up period or beyond the desired length of the run. The following example saves data from 30 minutes to two hours into the run1.trunc fil. lslog truncate :30 2:00 run1.log >run1.trunc 3. Generate the score. Tip If the clocks on your clients are not synchronized, you can specify the /r flag to rebase all your files at Jan 01 00:00:00 before merging. The score is one point on the response time curve. Based on the score, you may decide to run another scenario at a higher or lower user load, or to alter the topology in some way. Running a single scenario is rare. Typically, you should repeat the scenario. Mailbox Statistics Tool ----------------------- You can use the Mailbox Statistics tool to gather data about e-mail usage patterns. This MAPI tool analyzes a user’s mailbox and then develops statistics, such as the number of rules in a folder and the amount of mail sent and received daily. You can export this data into several formats, including .txt files and .csv files. You can use a Microsoft Visual Basic macro that runs in Microsoft Excel to explore Mailbox Statistics results in more detail. Using Microsoft Excel, you can customize column names, convert the data into a chart, and manage Mailbox Statistics results. Installing Mailbox Statistics ----------------------------- You can install Mailbox Statistics by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install Mailbox Statistics ----------------------------- 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Admin\Storstat. 2. Copy Storstat.exe to your local disk. Using Mailbox Statistics ------------------------ When you use Mailbox Statistics, you set up an administrator’s mailbox for collecting results and sending the tool to your users. Before you send the tool to your users, test it with approximately 10 people to ensure the tool works as expected and to become familiar with the different kinds of results. When users submit results, you can run the tool in Administrator mode and export results in a variety of formats. To use Mailbox Statistics ------------------------- 1. Create an Exchange mailbox named StorStat. 2. Attach Storstat.exe to a message and send it to the users you want to survey. How a User Works with Mailbox Statistics ---------------------------------------- The user opens the message and starts a copy of the tool. The tool opens the Message Stores Statistics Analyzer dialog box, which lists all the user’s message stores. At least one message store must be selected before analysis can begin. By default, all message stores are selected. The user can select Clear All and then select specific message stores to analyze, or select Select All to select all the message stores. If the user selects Exit, no analysis occurs. When the user clicks Start Analyzing, Mailbox Statistics analyzes the user's stores and then generates statistics, including the number of folders, the number of rules, and the amount of e-mail per day in each folder. A progress indicator bar and folder names appear as Mailbox Statistics processes messages. When the Mailbox Statistics tool finishes analyzing the folders, it displays the following message: “Results have been automatically sent to your administrator. Thank you for your cooperation.” The user can also save the results. When the user deletes the announcement message, they also delete Storstat.exe. Running Mailbox Statistics in Administrator Mode ------------------------------------------------ This procedure assumes that an administrator’s mailbox (named StorStat) exists and is available to collect results from users. You can check the number of responses by opening the Inbox and viewing the number of messages containing “UserResults.” After you receive enough responses, you can tabulate them by running the Mailbox Statistics tool in Administrator mode. To run Mailbox Statistics in Administrator mode ----------------------------------------------- 1. At the command prompt, type Storstat.exe -a. 2. Set the default messaging profile to the Mailbox Statistics administrator’s mailbox, or select a profile. 3. After Mailbox Statistics processes all messages, the Summary Results dialog box appears. 4. Click Save As to save results in a file you specify, or click Exit to discard the results. Exporting Results ----------------- 1. Run Mailbox Statistics in Administrator mode. 2. In the Save As dialog box, select a file type for your results. 3. Save the results. Interpreting Results -------------------- Remember that the Mailbox Statistics tool works with available data. For example, if some users empty the Deleted Items folder when quitting Microsoft Outlook and others do not, you can see differences in the statistics calculated from the Deleted Items folder. Using the Excel Macro to Interpret the Administrator Results ------------------------------------------------------------ 1. Run Mailbox Statistics in Administrator mode. 2. In the Save As dialog box, select the .csv file type for your results. 3. Start Excel, and open the Statmac.xls file (included in the resource kit). Ensure that macros are enabled. 4. Open the .csv file you saved. 5. On the Tools menu, click Format Spreadsheet to format your data and display four charts. MAPISend Tool ------------- The MAPIsend tool (Mapisend.exe) sends messages with optional file attachments through Microsoft Exchange 2000 Server. Computers running Windows 2000 unattended can better communicate their status by acting proactively rather than by being constantly polled by remote performance monitors or operators using administration tools. The MAPIsend tool enables task reporting to an operations group by sending standard Exchange 2000 Server messages. Examples of the kinds of tasks that MAPISend can report include: - Performance Monitor alerts - Tape backup job status - Disk quota information Note Administrators can run this program automatically by using the Scheduled Task wizard in Control Panel. Installing MAPISend ------------------- You can install MAPISend by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install MAPISend ------------------- 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Admin\MAPISend. 2. Copy Mapisend.exe to your local disk. Using MAPISend -------------- MAPISend Command Line Sytax --------------------------- mapisend -r {-u -p} or {-i} [-c][-s][-m][-t][-f][-l][-v][-?] IMPORTANT The -u, -p, and the -i switches are exclusive. You can either use -u or -p to log on with the profile name and password or use -i to log on interactively. The profile must exist if you wish to log on in non-interactive mode using -u and -p. Switch Description -u Mail profile of the sender -p Login password -i Interactive login, prompts for profile and password -r Recipient(s) (separate recipients with ';' and ensure they are not ambiguous) -c Mail copy list (cc: list) -s Subject line -m Message body -t Path of text file for contents of mail message -f Path and filename to attach to message -l Path and filename of the batch output log file -v Generates verbose output -? or -h Displays help for this command Note If you use both the -t (filename) and the -m (message body) switches, MAPISend processes the -t switch and ignores the -m switch. To use a space in the command line, surround the space with double quotation marks. Example ------- mapisend -i -r UserA;UserB -s "Test Message" MAPISend prompts you to log on to the messaging system and sends a message with the subject line "Test Message" to UserA and UserB. - You can run the MAPISend tool as a scheduled task. For instructions about how to set up a scheduled task, see the Windows 2000 online documentation. - You can use variables in any order. - You must type a space between the parameter ID and the parameter (-uUserName is not valid). - When you specify multiple files, you cannot use a space between file names. For example: -f c:\logs\file1.log; c:\logs\file2.log is not valid. -f c:\logs\file1.log;c:\logs\file2.log is valid. Avoiding Recipient Ambiguity Problems ------------------------------------- Recipient ambiguity problems can occur when you use MAPISend. Therefore, recipient names in the To and Cc boxes must not be ambiguous. If recipient names are ambiguous, MAPISend fails. To test for ambiguity of names 1. Type the recipient names in the To box of a Microsoft Outlook client message. 2. Click To, or press CTRL + K. 3. If the names are immediately resolved without any prompting, they are not ambiguous. 4. Repeat this test each time the address book changes and run the test from the computer on which you run MAPISend. Password Expiry Warning Application Tool ---------------------------------------- Password Expiry Warning Application (PEWA) is a command line application you can use to warn Exchange clients seven days before their user account password expires. PEWA exists because Windows 3.x clients using the NetWare Netx redirector and Macintosh-based clients do not receive password expiration warnings from Windows 2000 domain controllers. Prerequisites ------------- - You must run PEWA on a computer participating in a trusted domain. - You must manually create an Exchange profile. - You must create a Windows account and Exchange mailbox to use in the profile that is specifically used to send the password expiration warnings. Use the profile defaults. - The actual text that appears in the expiration message body must be in an RTF file named Pewa.rtf located in the same folder as Pewa.exe. Installing Password Expiry Warning Application ---------------------------------------------- You can install the Password Expiry Warning Application (PEWA) tool by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install PEWA --------------- 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Admin\Pewa. 2. Copy Pewa.exe to your local disk. Using Password Expiry Warning Application ----------------------------------------- To use PEWA ----------- Open the command prompt and type Pewa.exe. Use the following syntax and commands to customize PEWA: pewa -d \\{servername} -f {path to RTF file} [-u {profile}] [-v] [-x] [-z {days}] Switch Description -d Name of a domain controller in user accounts domain. This switch must be first and is required. -f Path to .rtf file for message text. -u Exchange profile name. -v Verbose output. -x Disable sending messages to sent mail folder. -z Number of days before expiration to send warning; default is seven. Note Use quotations marks if there is a space in the profile name. PEWA uses a default profile if you do not specify a profile. Tip Use the Windows 2000 schedule service to run PEWA during off-peak hours. PEWA performs best when run on a domain controller in an accounts domain. Public Folder Administration Tool --------------------------------- The Public Folder Administration tool helps an administrator manage public folders. You can change the replicas and permissions on a folder or folder tree. Installing Public Folder Administration --------------------------------------- You can install Public Folder Administration by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install Public Folder Administration --------------------------------------- 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Pftools\Pfadmin. 2. Copy Pfadmin.exe to your local disk. Using Public Folder Administration ---------------------------------- The following sections describe how to use the Public Folder Administration tool (PFAdmin). Batch and Interactive Mode -------------------------- The PFAdmin tool has two methods of use, interactive and batch. When using PFAdmin in interactive mode, the user opens the tool and enters commands at the prompt. In batch mode, the user starts PFAdmin with the name of the server and the name of the batch file that the user wants to run as shown in the following example. pfadmin server publicfolder.cmd This line runs the commands listed in the file publicfolder.cmd against the Exchange 2000 server. The user can also add a log file for batch runs as shown in the following example. pfadmin server publicfolder.cmd out.log PFAdmin Commands ---------------- The following are commands used with the PFAdmin tool. Command Description List List of public folders the server has access to. ListRepl List of the public folders with the name of the store and server that public folder is replicated to. ListRights Prints the list of rights that PFAdmin can manipulate. ListACL Lists the public folders, the owner and group, and every account that has permissions on the folder and which permissions the account has. MessageClass Counts every item in a folder and lists the number of items and what message class they are. SetRepl Change what server the public folder is replicated to. Rehome Change the replication of the public folder to a single server specified. SetACL Change the permission on a folder. Warning If a replica of a folder is removed from the server that PFAdmin is running on, the user will be allowed to change the folder, but the contents under this folder will not be accessible. Command Syntax -------------- Commands have the following syntax. A tab must separate each item of the syntax. List Commands Command Scope SetRepl Command Scope Add/Delete/Replace Server/Store Rehome Command Scope Server/Store SetACL Command Scope Add/Delete/Replace Account Right Allow/Deny Scope ----- Each command has a scope. The scope can be all for the full server hierarchy. The scope can also be for a public folder tree, which runs the command against every folder in the tree. The scope can also be for an individual folder. If there are multiple folders and folder trees with the same name in the hierarchy, the first folder or tree found is the one PFAdmin works with. The scope is optional for the List, ListRepl, ListRights, and ListACL commands. If the command doesn't include a scope, then PFAdmin assumes all for the full server hierarchy. Scope Description Add/Delete/Replace For the commands that modify folders, this allows the user to add a new item, delete an item, or replace the current items with the item supplied. Server/Store This is the replicated server or public store. Account A Windows 2000 account in the Exchange Server domain. This can either be Domain/user or user. Rights ------ The rights to the folder the account will have. For a complete list of the rights, use the ListRightcommand. Right Description Allow/Deny Causes the right to be either allowed or denied. PFAdmin tries to keep the right on one or the other list; however, there are some cases where a right appears on both allow and deny lists. If this happens, deny takes precedence. Examples -------- The following is an example of the list command. This example shows the list of the entire server public folder tree. testserver>list Did not find the scope assuming ALL. PFT:Public Folders PF :Internet Newsgroups PF :Lab Discussion PF : Biology Lab PF : Animal Lab PF : Plant Lab PF : Physics Lab PF : Chemistry Lab PFT:Researcher Folders PF :Chemistry PF : Lab Reports PF : Test User PF : Test User2 PF : Test User3 The following example shows what folders are replicated to which servers. The public folder Lab Reports is replicated on the server testserver, but not on either of the servers testserver2 and testserver3. The folder Test Folder is replicated to all three servers. testserver>listrepl Researcher Folders PF :Chemistry In the Repl List:[Public Folder Store] on server [testserver] Not in Repl List:[Chemistry Store(testserver2)] on server [testserver2] Not in Repl List:[Chemistry Store(testserver3)] on server [testserver3] PF : Lab Reports In the Repl List:[Public Folder Store] on server [testserver] Not in Repl List:[Chemistry Store(testserver2)] on server [testserver2] Not in Repl List:[Chemistry Store(testserver3)] on server [testserver3] PF : Test Folder In the Repl List:[Public Folder Store] on server [testserver] In the Repl List:[Chemistry Store(testserver2)] on server [testserver2] In the Repl List:[Chemistry Store(testserver3)] on server [testserver3] PF : Test Folder2 In the Repl List:[Public Folder Store] on server [testserver] Not in Repl List:[Chemistry Store(testserver2)] on server [testserver2] In the Repl List:[Chemistry Store(testserver3)] on server [testserver3] PF : Test Folder3 In the Repl List:[Public Folder Store] on server [testserver] In the Repl List:[Chemistry Store(testserver2)] on server [testserver2] Not in Repl List:[Chemistry Store(testserver3)] on server [testserver3] The following example removes the replica of the folder Test Folder from the testserver3 server. testserver>setrepl Test Folder delete testserver3 PF : Test Folder testserver>listrepl Test Folder PF : Test Folder In the Repl List:[Public Folder Store] on server [testserver] Not in Repl List:[Chemistry Store(testserver2)] on server [testserver2] Not in Repl List:[Chemistry Store(testserver3)] on server [testserver3] The following example adds the replica of the folder Test Folder to the testserver3 server, using the public store name. testserver>setrepl Test Folder add Chemistry Store(testserver3) PF : Test Folder The following example shows that the account OURLAB\User1 has the ability to Read Body, Write Body, and Delete on the Lab Reports folder. User2 is denied to Write Body and Delete. testserver>listacl Lab Reports PF : Lab Reports Owner: NT AUTHORITY\SYSTEM Primary Group:BUILTIN\Administrators Allowed ACE :OURLAB\User1 Read Body Write Body Delete Denied ACE :OURLAB\User2 Write Body Delete The following example removes Deny to Write Body for the public folder Lab Report for User2. testserver>setacl Lab Reports delete User2 Write Body Deny PF : Lab Reports testserver>listacl Lab Reports PF : Lab Reports Owner: NT AUTHORITY\SYSTEM Primary Group:BUILTIN\Administrators Allowed ACE :OURLAB\User1 Read Body Write Body Delete Denied ACE :OURLAB\User2 Delete Public Folder Tree Information Tool ----------------------------------- The Public Folder Tree Information tool counts all the messages in a selected folder and all subfolders. This tool is useful for verifying public folder replication between servers. Installing Public Folder Tree Information ----------------------------------------- You can install Public Folder Tree Information by running Microsoft Exchange 2000 Server Resource Kit Setup or you can use the following procedure. To install Public Folder Tree Information ----------------------------------------- 1. Open the Microsoft Exchange 2000 Server Resource Kit compact disc and navigate to \Exreskit\Tools\Pftools\Pftree. 2. Copy Pftree.exe to your local disk. Using Public Folder Tree Information ------------------------------------ You can use the Public Folder Tree Information tool to perform the following tasks on the MAPI Clients public folder tree or on general purpose public folder trees. - Count messages recursively. - Count subfolders recursively. - Count messages and subfolders recursively. To count messages recursively ----------------------------- 1. Open Public Folder Tree Information. 2. Select the appropriate tree or folder. 3. Select Count Messages. 4. Click Start Count. To count subfolders recursively ------------------------------- 1. Open Public Folder Tree Information. 2. Select the appropriate tree or folder. 3. Select Count Sub Folders. 4. Click Start Count. Tip To count both messages and subfolders recursively, select both check boxes, and then click Start Count.