My company (management department secondary school) has asked me to solve the following problem:environment: Exchange 2007, OWA, Outlook 2007the secretaries have made / keep up to date a contacts folder inside the public folders and people use that list (address book) to e-mail, phone or fax contacts outside our organization, this list can not be used in the same way using OWAthe IT department publishes (using AD) lists that contain the contacts inside the organization and these lists can be used by both Outlook and OWA usersthe IT manager has asked for a solution that meets the following demands:contains both contacts inside and outside the organizationcan be accessed by both Outlook and OWA and have the same look and feelmust be the only list availableall necessary contact information must be available (phone, addres, postal code, phone numbers, etc...) and be easy to printmust be kept up to date by one department.does anyone know a solution?thanks in advance,

What do you mean by "the list must also be used to share calendars inside the organization"?

Sorry mjolinor, the line "the list must also be used to share calendars inside the organization" does not meet the demands. So i'v change the question. Thanks if you know the answer,

First of all, to meet the requirement of everything being available in consistent list in OWA and Outlook means it all has to be in AD. Those public folder contact lists have to go.How to make it maintainable by one department is going to depend on which department is going to maintain it. If it's ouside of IT, then you're going to have to do some permission delegation and training.If I had to set this up, I'd use Powershell and Quest's PowerGUI to create an application for managing the contact information, delegate AD permissions to create new contacts, and update the contact information in the AD users, and work toward giving that application to the secretaries and letting them do the maintenance and printing.IMHO

Thanks for your answer, So if I understand it right it is not possible to make a public folder. I have to put all the contacts in the AD. But the contacts are people inside our organisation an customers. It seems to me that you don't want to have customers in your AD. De department that is going to maintain the list is somebody of the adminstration who has no knowledge at all, than the standard outlook featuresMVE

The problem is that Outlook and OWA get their address lists from AD. If you want them to show up there, that's where they have to be. The customers would just be contact objects in AD, they won't be security principals.I've used PowerGUI to set up an application for managing the company phone numbers so that someone who's not technically savvy can do it. Basically, you just give them a view of AD that only contains the data they're responsible for, and a set of scripts that let them enter a value for a field, does some valildation checks on the data, and if it passes, commits it to AD.It's not particularly fast, so you'd probably want to do a scripted bulk export from your public folder data and create AD contacts from that, and then use the app for ongoing maintenance. It also has built in facilities for selectively exporting the data as .csv or html.

Ok, thanks. I'm going to look for PowerGUI. Thanks for your help!RegardsMVE