We have an interesting issue I cannot seem to find a proper resolution for. We migrated from Exchange 2003 to Exchange 2010 a few months ago and in doing so everything went smooth. However, there is one outstanding issue I cannot seem to resolve. In our company we use Organizational Forms, and in the past the forms have worked a certain way. Ever since moving to Exchange 2010 the custom forms (in our Organizational Form Library) act somewhat different. The custom form is a contact for with a few extra tabs for customer information. This custom contact form is published to our Organizational forms Library and all users have access to view and use the form (that part is working). The problem comes in when said employee fills out the custom form data, saves it (to their local contacts) and then tries to forward the Outlook contact on to another employee. When sending the contact via email the Message Type goes from "IPM.Contact.NewAccount" (custom form), back to simply IPM.Contact (default contact type). On the senders end the contact placed in the email is still of the IPM.Contact.NewAccount type, only once the email is sent does it change format/types. It is as if Exchange 2010 is not keeping the custom form in tact when sending it. Both employees have proper access to the Organizational Form Library (or at least seems so, they both can open the custom form). Not sure what is going on, has anyone else ran into a similar issue? Just to note, since migrating we do get the [80004005-501-4B9-560] error in Sync Issues, which is related to syncing forms. This seems to be a known issue with how logging in done in Exchange 2010. Though I have tried a workaround to this issue by deleting our Organizational Form folder and re-creating from scratch, it did not help with that error. Not sure if its related to the problem I'm seeing or not. I simply do not know where to go from here to test this issue. I do not want to check the box on the form to send formatting data with the form. I would like it to work as it should (by allowing a sender to email a custom contact form to a recepient and have the custom form stay without changing to regular contact).

Hello, Firstly, you need to check the Org Forms folders in the Exchange 2010 public folder database and see if all the contents are available. Secondly, make sure all the users have the permission to access it. In addtion, make sure all the Exchange 2010 public foder database is the default public folder to all the users. For more information, the sync issue "[80004005-501-4B9-560]" is a known issue in Exchange 2010. Generally, we can safely ignore this sync error. Thanks, Simon

Hello, Firstly, you need to check the Org Forms folders in the Exchange 2010 public folder database and see if all the contents are available. Secondly, make sure all the users have the permission to access it. In addtion, make sure all the Exchange 2010 public foder database is the default public folder to all the users. For more information, the sync issue "[80004005-501-4B9-560]" is a known issue in Exchange 2010. Generally, we can safely ignore this sync error. Thanks, Simon Sorry for the delay in responding. 1). The Org forms are in our Public Folder and everyone has the public folder as their default folder. 2). All users have at least access to view the forms and can do so properly. They can open up the form, use it, save it, everything works fine until they email the form. I understand "[80004005-501-4B9-560]" is a known issue due to how Exchange 2010 is logging information (makes Outlook essentially create a false positive sync error). But I was not sure if the error also caused this side effect of custom forms not keeping their format when sent via Exchange 2010. We did not have this problem with Exchange 2003, but emails are sent differently with Exchange 2010 (even internally) due to how Exchange 2010 uses the CAS and SMTP roles. Everything appears fine from a permission standpoint and we only use one Public Folder, which is the default for everyone. All forms and folders within the Public Folder database can be seen and used by all. I guess I am trying to find out if custom forms should work in Exchange 2010 the way they did in Exchange 2003, or due to how Exchange 2010 processes emails is this issue working as intended? The issue again is that our custom form IPM.Contact.NewAccount changes back to IPM.Contact upon emailing to anyone (even emailing to yourself). I am the owner of the folder(s) and not even I can get this to work. Even when I send an email to myself the format changes back to IPM.Contact when I receive the email, yet the format is IPM.Contact.NewAccount in my Sent Items. So it seems to change as it traverses the Exchange 2010 environment.