Hello all-So here is the run down on what has been going on with my Exchange 2003 server. About a year ago we did a swing migration from SBS2003 to our current configuration (this will come into play in a sec.). About five months ago we started getting Free/Busy errors on our Exchange Server:EventID: 8207Error updating public folder with free-busy information on virtual machine RANSOM. The error number is 0x8004010f. So, after some reading and Google work I attempting opening Outlook with the /cleanfreebusy switch. This worked for new accounts that had been created after our migration, but not for accounts from the old SBS days. After some more digging, I starting comparing the two different account type using ADSI Edit, and found that the legacyExchangeDN entry was different. For Example:Old SBS account:/o=SCOTTUSA/ou=first administrative group/cn=Recipients/cn=usernameNew User:/o=Scott USA Email/ou=First Administrative Group/cn=Recipients/cn=usernameSo, seeing that they were different, I went through and changed all the legacyExchangeDN values to match. The errors went away, and besides a few delivery problems (I had expected this) everything seemed fine.....Until last week. I installed some security patches for Exchange last week, and the error in the EventLog came back(EventID: 8207). Digging back in using ADSI Edit, I found that all the old SBS user account's legacyExchangeDN values had returned to their old SBS format.So, for the question:I am pretty sure this is due to something not being done (done right, or at all) during the migration. I also have no problem changing all the legacyExchangeDN values to match again, since we only have 150 users that way, but this is not something I want to do every time I install updates.So, where is this old value being pulled from? Is it something I can change? Is there a better solution than changing the legacyExchangeDN?Any ideas on how to resolve this problem would be greatly appreciated. As an end result, I would like to get rid of these errors without too much trouble and pain.Thanks for any input you can provide!**I have also reset the system folders GUID to no avail.-Daniel Westendorf

For each user, can you create an X500 address on the E-mail Addresses property page that uses their old legacyExchangeDN? Try this for a test user or two and see if it fixes the problem. If not, you probably need to open up a PSS ticket. You have tried almost everything else I would have tried.

Yeah, I gave that a try, but it was unsuccessful as well. I decided to just get down and dirty and change each one and hope the problem doesn't come back.... high hopes I know. Thanks for the help though....-Daniel