Tag Info

Hot answers tagged

6

The public folder replicas and the default public folder database for a mailbox server are two different things. The public folder tree is an organization-level entity, unrelated to any physical database; each folder can have one or more replicas, residing on various mailbox servers. When a user needs to actually access a PF, Outlook connects to the ...


6

Massimo, I had actually wondered the same thing while attending an online "lunch and learn" a while back and was pointed here: http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx The basic premise from what the guy told me (and the article confirmed) is: Each public folder mailbox created contains info on the ...


4

Microsoft has docs describing the procedure in both the GUI and from PowerShell. This assumes you're using Exchange 2010 SP1 (which you really should be). You'll need a public folder database on the E2K10 server to replicate into, obviously. You can background about creating one from Microsoft, too. Once you've got the database created and configured ...


3

Outlook can do that. Exchange on its own can't. There probably are third-party utilities around that can help, but using Outlook is probably the easiest approach. Just open Outlook, create a PST file, right-click on the PF you want to export, select "Copy Folder" and place it in the PST archive. Oh, and don't try to put all of that data into a single PST ...


3

I've run into this a number of times and it's been frustrating. More often than not, I wind up harassing a user who connects to that folder in order to get the full path from them. Once or twice I've just let it go and said "I can't do it without the full path". But it turns out that get-recipient does not require the full path in order to return a result. ...


3

Are you serving it from a Mac OS X Server? I use it to serve a shared folder so that all members of a group have full control of it and everything in it, both from Mac clients connecting over AFP, and linux clients connecting over NFS. I don't have any SMB clients, so I can't comment on whether it works there. My hunch would be that it would, because the ...


3

Now that iPhones (iOS4?) support multiple exchange accounts and Outlook 2010 shows other users folders in exactly the same way as public folders you have another option which does not rely on 3rd party software. Create a dummy mailbox called Shared and give all your users full permissions to use access it using the "Manage Full Access Permission..." tool in ...


3

Using the GAL requires creating contact objects in Active Directory for each contact; this can't normally be done by standard users without custom delegations, and it requires special tools (ADUC, EMC). The main benefit is full integration with Outlook address book(s): if something is in the GAL, you automatically can see it in Outlook. With a public ...


3

Use this Powershell script from the source PF Server C:\Get-PublicFolder -Recurse | Set-PublicFolder -Replicas 'Replica1','Replica2','Replica3' Where Replica1 and so on are your PF Database Names.


3

Exchange 2003 really does use Public Folders for things. Specifically, the Offline Address Book and Free/Busy information storage. However, you CAN nuke all user-generated data in there. That's probably a majority of the consumed space. The System store is in a different public folder root than the one the users see (IIRC, I'm on 2007 so may be ...


3

The short answer is that you have to have execute permission or higher (5) on a directory to list the contents of that directory. You can access files in a directory if you have read permission (4) but you have to know the name of the file because you can't list the contents of the directory. So, the user you are using to access the directory is not the ...


2

I ended up installing the Exchange 2003 administrative tools on a Windows Server 2003 computer and moving the container using Exchange 2003's System Manager, as would be the case in a standard 2003-2007 transition.


2

Here is a posting from technet detailing this exact issue http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/46124982-7161-4241-b6e0-093cedeeda76 Looks like using ADSI Edit to delete out the public folders was the final step needed


2

I doubt you have "way too much data" in public folders. Public folders are stored using the same ESE engine that stores mailboxes, and I've seen Exchange 2003 installations with upwards of 100GB mailbox databases (though, arguably, they performed very badly compared to newer versions of Exchange, they did work fine). Diagnosing your "replication issues" is ...


2

I think that if you facing similar type of situation you should directly use a third party tool instead of running the script which might be sometimes wrong to perform. These tools has the ability to solve this problem of migrating more than 7 GB public folders data to the new exchange server 2010. Thanks


2

Public Folders use Roles to grant permissions "sets" to the PF tree. The default settings (at the root and for all new PF's) is for Anonymous users to have the "Create Items" permission and for Default users to have the Author role (Create items, Read items, Edit own items, Delete own items). The user who creates the PF (excluding the root of the PF tree) is ...


2

Yes, it's possible. You need to mail enable the PF in ESM. The PF will be assigned an email address based on your Default Recipient Policy, but the email address can be changed if needed. You'll need to make sure the Anonymous and Default entities have the Contributor role on the PF in order to recieve email to the PF.


2

You could just create a Shared Mailbox, and have the users add it to their outlook profile. My suggestion however is this: Install SharePoint Foundation 2010 and configure incoming e-mail. This way, you can enable the users to send their "team-related" information directly from Outlook and have it published in a document library on a sharepoint site which ...


2

I have resolved the issue, to solve this, we have to go into Active Directory Users and Computers. Under View, select Advanced Features. Now, under the /Microsoft Exchange System Objects folder, manually delete the Correspondance 81807753 object. To prevent this, you have to mail-disable the public folder before deleting it from the public folders.


2

Even if nobody touches those files for 6 months, I still wouldn't let them disappear for a while. You'll save yourself a lot of potential headaches by replicating these PFs to the 2010 box and simply not making them accessible to the users, if you truly want to phase them out (I bet you can create the PF DB, replicate, then take it offline and get it off ...


2

You may have luck examining the PR_CREATOR_NAME and PR_LAST_MODIFIER_NAME MAPI properties on the items. You can use the MDBVU32 utility to view these properties (background on doing that is available in KB253291). On my test machine (a Customer's E2K3 server I had close at-hand), though, I found that items I copied from my "Inbox" folder to a public folder ...


1

It sounds like they don't have another Exchange Server computer there. If they do, there's a different set of questions and answers for your issue. Assuming they do not, you can use HTTP-over-RPC (aka "Outlook Anywhere") to give them "full blown Outlook" access to your Exchange Server computer, or you can use a VPN. Have a look at: ...


1

An obvious solution is to look at the most recent messages in each folder. If the dates are sufficienly old There is a "Last Accessed" property on each, but that can be touched by your backup scheme. The "Last Updated" will tell you the last time a message was posted, but not last read. If your last updated is sufficiently old, the next best thing to do ...


1

Check to see if you have more than one public folder in the AD schema. Easiest way is to go to EMC and select Toolbox -> Public Folder Management Console. Then connect to the server. If you try to browse and get error for "Multiple MAPI public folder trees detected" you need to do the following: Open ADSI edit and connect to Configuration naming context. ...


1

Can the user view the contents in OWA? If so, then it's an Outlook view problem and you should reset their view. If not, then I'd take a look at the permissions on the PF, what roles have which permissions, is the user listed in the permissions or is the user a member of a group that has permissions and what roles/permissions are granted to the user or ...


1

How about just moving it from an Outlook client?


1

This is a pretty decent step-through of what you're trying to accomplish. It's for Exchange 2000, but the steps should be the same for 2003.


1

Yes you can keep Public Folders on premises and have them visible to migrated users. It ain't easy, but it is possible. http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx


1

Just a suggestion having gone from an Exchange 2003 to Office 365 environment they suggest moving Public Folders to a SharePoint list. With photos SharePoint may offer some benefit in the sense that you can store extended amounts of metadata against each picture as well as indexing and search capabilities. Essentially mailboxes were setup to receive the ...



Only top voted, non community-wiki answers of a minimum length are eligible