Schedule+ Free/Busy system folder is missing

When you migrate the first Microsoft Exchange Server 5.5 computer in the site to Microsoft Exchange 2000 Server or to Microsoft Exchange Server 2003, and it is the last server in the site, you may have problems with your system folders.

After you reset the system folders with the Guidgen utility, users may still get the following error message when they try to create appointments with themselves or others: For more information about using Guidgen or resetting the system folders, click the following article number to view the article in the Microsoft Knowledge Base:

This behavior occurs because the only instance of the "Schedule+ Free/Busy" system folders has been deleted or contains invalid data. The new Exchange 2000 or Exchange 2003 Server points to an incorrect Exchange Server computer as being the public folder server for the administrative group.

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk. To resolve this problem, follow these steps:

1. Open ADSI Edit from the Windows 2000 Support Tools, and locate the following item:
   CN=[YourAdministrativeGroup],CN=Administrative Groups,CN=[YourOrg],CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[YourDomain],DC=com
   To locate the this item, double-click each of the following objects to expand them:
   Configuration Container [Computer.Domain.Com]
   CN=Configuration, DC=(YourDomainController),DC=com
   CN=Services
   CN=Microsoft Exchange
   CN=(YourOrganization)
   CN=Administrative Groups
   CN=(YourAdministrativeGroup)
2. Open the properties of CN=(YourAdministrativeGroup).
3. On the Attributes tab, under Select a Property to View, click SiteFolderServer. The information displays the old deleted server.
4. If there is more than one server in the administrative group, choose a server in the administrative group to home the public folders.
5. In ADSI Edit, locate the following item:
   CN=First Storage Group,CN=InformationStore,CN=[YourServer],CN=Servers, CN=[YourAdministrativeGroup],CN=Administrative Groups,CN=[YourOrg], CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[YourDomain],DC=com
   To locate this item, double-click each of the following objects to expand them:
   Configuration Container [Computer.Domain.Com]
   CN=Configuration, DC=(YourDomainController),DC=com
   CN=Services
   CN=Microsoft Exchange
   CN=(YourOrganization)
   CN=Administrative Groups
   CN=(YourAdministrativeGroup)
   CN=(Servers)
   CN=(YourServer)
   CN=InformationStore
   CN=First Storage Group
6. In the right pane, double-click CN=Public Folder Store (YourServerName) to open the properties.
7. Under Select a Property to View, click distinguishedName.
8. Copy the value.
9. In ADSI Edit, use the instructions in step 1 to locate the following item:
   CN=[YourAdministrativeGroup],CN=Administrative Groups,CN=[YourOrg],CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=[YourDomain],DC=com
10. Open the properties of CN=(YourAdministrativeGroup).
11. On the Attributes tab, under Select a Property to View, click SiteFolderServer.
12. Paste the distinguishedName value in the Edit Attribute field.
13. Click Set, and then click OK.
14. Exit ADSI Edit.
15. Restart the Microsoft Exchange Information Store service on all servers that are running Exchange Server in the site. After you do this, the change takes effect.

Note On the client side, click Start, click Run, type Outlook /cleanfreebusy, and then press ENTER. This forces Outlook to locate and publish the user's free/busy data to the new Schedule+ Free Busy system folder. Alternatively, send a test meeting request to all users homed to this server and ask them to accept the request.