Access Public Folder in Exchange
Using CF8, I currently can access mailboxes and folders in my
exchange information store except for folders in the public store.
Does anyone know how to access information in the public folders
using CF8's exchange tags.
Trevor
Has anyone figured this out?
This would be an incredibly useful feature. Perhaps there is a way to do this by interacting directly with the Java?
Similar Messages
-
Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3
Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
MuflehI ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread -
Will CF9 cfexchangecalendar access public calendars in Exchange Server 2007?
We need to create something in CF9 that will allow us to access public calendars in Exchange Server 2007. I've Googled it but only come up with dead ends. Any help would be appreciated.
I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread -
Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013
Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
Team,
users are unable to expand public folder from outlook, but they are able to navigate through outlook web access.
noticed the outlook connections are connected to other child domain PF server rather than local site public folder server.
due to this issue, users are unable to navigate to pf's , by restarting RPC Client access service , now users are able to connect to local public folder servers.
all the databases are pointed to local pf database. all the settings looks good.
any suggestions would be appreciated.
Regards
Srinivasa K
Srinivasa KHi Srinivasa,
How about OWA?
If it works in OWA, it seems an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I also suggest make sure the Outlook client has the latest patch.
Also try to re-install Outlook.
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Publishing Public Folder Calendars Exchange 2013
Hi Guys
I'm trying to publish an exchange 2013 public folder calendar. from outlook when I go to publish it give me the following error:
The mailbox folder identity ":S4ABAQH/////LgAAAAAAAAAoEFwKAAAAAPUAAAAAAAAAVhBcCgAAAAAAAAAAGkRzkKpmEc2byACqAC/EWgMAvY9C6z7Df0uoy78J0eSm+gAARbBnPwAAAAAAADihuxAF5RAaobsIACsqVsIAAEVNU01EQi5ETEwAAAAAAAAAAByDAhCqZhHNm8gAqgAvxFoGAAAAOTkzMDU4ZGMtOGY5Yy00Yzc5LThkZGQtMTE5NzEyNTgwMDA3QGtpbmdzY2h1cmNoLm5ldC5hdQAvbz1raW5nc2NodXJjaC9vdT1FeGNoYW5nZSBBZG1pbmlzdHJhdGl2ZSBHcm91cCAoRllESUJPSEYyM1NQRExUKS9jbj1SZWNpcGllbnRzL2NuPWUwMzkxYTQ3MmI0ODQxZDg4NDE4MzI5MjQ1MmUxNGY3LUR5bGFuIE1jTGVvZAAC" isn't in the correct format. The correct format should look like this: "<MailboxIdentity>:<FolderPath>".
I've been searching but am unable to find any information regarding the error.
Is there something that i'm missing which would allow me to publish the calendar?
Regards
DylanHi Ed
From within outlook 2010 i right click on my public folder calendar and select "Share" and then "Publish This Calendar". it loads owa asking to login, i login and a error popup show straight away over the calendar publishing webpage with the error above.
the account i'm testing with is a domain account and have full permissions to exchange, public folders etc. -
Can't access Public folder as guest
Since installing Leopard computers on the network will not connect to my Public folder as guest.
When trying to access the Public folder under 10.4 the "Guest" option is grayed out, although connecting as a user (entering user/pass) is possible.
When trying under 10.5, once I select the computer name from the Finder's window left menu "Connection Failed" appears on the dark-grey bar at the top. Still, like in Tiger, connecting as a user is possible, but when trying to disconnect by pressing the "Disconnect" button on top nothing happens. I get the same "Connection Failed" message and the user remains logged.
Where I may have messed up: I have 2 accounts in my computer (1 admin, 1 standard). I almost never use the admin account so I deleted it's Public folder from "Shared Folders" under Sharing in System Preferences. Then, on the standard account I deleted by mistake the "Staff" group from it's Public folder permissions. When trying to add "Staff" back, the option is not available.
All of that may have nothing to do with my problem, but I know very little about Unix, so who knows.
Any ideas as to why no one can access my Public folder as guest?That would be in the case I wanted a Guest Account on my same computer to be able to access my Public folder. My problem is with computers on the network. Thanx anyways
-
Windows Users Accessing Public Folder
I would like to know the way to allow Windows users to access only the Public folder on my mac.
When I try to access folders from Windows I go to My Network Places and click on the icon representing my Mac then I'm prompted for a password; as I have only my account on the Mac I have to put my user ID and password, thus allowing access to all my folders - not only Public.
I know that Mac users can access Public, but how to allow the Windows camp to do that?
17' PowerBook G4 Mac OS X (10.4.4)SharePoints is a great tool to allow access to peripheral drives, volumes, and the like. But you shouldn't have to use it to access the Public folder via a PC as you can a Mac. That is a very big question on the boards that has yet to be answered.
Apple says it happens. If so, what's the secret to accessing the Public folder via a PC.
Any information will be greatly appreciated. -
Importing into public folder on Exchange 2013
Outlook 2013 Pro
Exchange 2013 SP1
I created the public folders and granted publisher rights to the outlook client. I exported a list of contacts to contact.pst from another account. In the exchange account, I import, point to the contact.pst and say place in same folder (public). Nothing
is imported.
If I expand contact.pst tree and select the contact folder (e.g. vendors), I get error ... Item cannot be created in the root of public folders.
How do I import into public folder?
John LenzOutlook 2013 Pro
Outlook doesn't support importing into a public folder.
You would either need to open the PST file in Outlook and then copy/move the contact items in the PST file to the applicable public folder.
Alternatively, if this is something that you're going to do on an on-going basis - any of the ContactGenie Import/Export programs may be of interest
ContactGenie Import Overview
http://www.contactgenie.com/import_overview.htm
Karl Timmermans [Outlook MVP] "Outlook Contact Import/Export/Data Mgmt" http://www.contactgenie.com -
Public Folder in exchange server 2013
We are using an legacy application developed in Classic ASP. In this application we are rendering the message items in the public folder on the exchange server 2003.
Now we are going to migrate our exchange server 2003 to exchange server 2013.
Do exchange server 2013 have public folder? Is this migration have impact on the public folders usage.
Please let me know for any clarifications.There will be no co-existence support for Exchange Server 2003. In your scenario, you will have to migrate twice, once from Exchange 2003 to Exchange 2007 or 2010, then again to Exchange 2013 or another option you have to proceed that by using any third-party
migration tool to accomplish this task in one go. When you preparing to migrate mailbox, you can have a look at
exchange server deployment assistant to see the current recommended steps for your configuration. A good resource for swing migration direct from exchange 2003 to 2013 can be explored at
here.
In the same way, You cannot migrate public folders directly from Exchange 2003. You will have to move all public folder databases and replicas to Exchange 2007 SP3 RU10 or later. No public folder replicas can remain on Exchange 2003.
I would like to refer on couple of links mentioned below. It will help you better to clarify the scenario further :
Understanding the public folder architecture
Public folder migration -
Start-up script to access public folder on iMac from iBook
I have a public folder on my iMac (running Leopard) that I can access from my iBook (running Tiger) by routing through with Finder each time I start up my iBook. I would like to have a script automatically run at start up on my iBook to connect to the public folder on my iMac. If the iMac is powered on, the connection is to be made; if the iMac is off, obviously the connection is not made, but the iBook does not hang-up, it continues without the public folder connection.
Well this can be done with some caveats. Here is what I did(on Tiger iBook G3( I didn't try on my Panther ibook G4), but it should work on that too. Forgive me. This G3 is a tester so....) and some explanations about it.
I made a unix executable with pico in Terminal. Ran chmod u+x on it. Called it contoamac.
#!/bin/bash
open afp://192.168.0.6/
The 0.6 is my other machine(your iMac per se) with Leopard. I put the executable in my iBook(your iBook also as reference) in Sys.Pref., Accounts,LoginItems. Only turned on sharing on Leopard machine. But you either have to catch the Leopard machine awake or set it in energy savings to never sleep. Possibly you could have both machines never go to sleep and that would work unless there is a time out on server uptime. Rebooted ibook and it autoed to login password(to do with no pass is another story involving visudo, etc.) on Connect to server menu. I know I have forgotten something to explain.
I'm going to run this reboot and try and get a quick screen shot of boot/connect process next. Right back. Whew! -
Public folder migration Exchange 2007 to Ex2013
Hi Team,
Below is my co-existence enviroment . Everything is working fine but getting issue while migrating public folder
Dc-2003 , Ex2007 SP3 rollup10 , Ex2013 with Rollup2
==============================================
[PS] C:\Documents and Settings\Administrator.HCL>C:\Script\PublicFolderToMailbox
MapGenerator.ps1
Parameter declarations are a comma-separated list of variable names with option
al initializer expressions.
At C:\Script\PublicFolderToMailboxMapGenerator.ps1:15 char:144
+ HelpMessage = "Size (in Bytes) of any one of the Public folder mailbo
xes in destination. (E.g. For 1GB enter 1 followed by nine 0's)")] <<<<
[PS] C:\Documents and Settings\Administrator.HCL>thanks Martina for your reponse . I have tried all the ways please see print shot below no help. But the same command was working with Ex2010 i have successfully migrated public folder also from Exchge 2010 to 2013
[PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.txt
Parameter declarations are a comma-separated list of variable names with optional initializer expressions.
At C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
+ HelpMessage = "Full path of the output file to be generated. If only
filename is specified, then the output file will be generated in the current directory.")] <<<<
=====================================
[PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.csv hcl-ex2007
Parameter declarations are a comma-separated list of variable names with optional initializer expressions.
At C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
+ HelpMessage = "Full path of the output file to be generated. If only
filename is specified, then the output file will be generated in the current directory.")] <<<<
======================================
[PS] C:\PFScript>.\Export-PublicFolderStatistics.ps1 C:\PF\stats.csv hcl-ex2007.
hcl.com
Parameter declarations are a comma-separated list of variable names with option
al initializer expressions.At
C:\PFScript\Export-PublicFolderStatistics.ps1:16 char:168
+ HelpMessage = "Full path of the output file to be generated. If only
filename is specified, then the output file will be generated in the current di -
Public Folder Migration Exchange 2010 to 2013 Stuck on Queued
I submit the request New-PublicFolderMigrationRequest and the status is stuck on "Queued". What are the steps to troubleshoot this? I have followed the article in on Technet to perform my PF migration.
[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server "exchange3.a
npinetwork.com") -CSVData (Get-Content "C:\PFMigration\foldertomailbox.csv" -Encoding Byte)
Name SourceDatabase
Status
PublicFolderMigration Public Folder Database 1055175278 Queued
[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport |
Format-List
RunspaceId : c2270d62-665e-44ad-8829-43f5befde1f9
Name : PublicFolderMigration
Status : Queued
StatusDetail : Queued
SyncStage : None
Flags : IntraOrg, Pull, SuspendWhenReadyToComplete
RequestStyle : IntraOrg
Direction : Pull
Protect : False
Priority : Normal
Suspend : False
SourceVersion : Version 14.3 (Build 123.0)
SourceDatabase : Public Folder Database 1055175278
SourceServer : exchange3.anpinetwork.com
BatchName :
OutlookAnywhereHostName :
RemoteCredentialUsername :
AuthenticationMethod : Basic
RemoteMailboxLegacyDN :
RemoteMailboxServerLegacyDN :
BadItemLimit : 0
BadItemsEncountered : 0
LargeItemLimit : 0
LargeItemsEncountered : 0
FolderToMailboxMap : {\}
QueuedTimestamp : 1/16/2014 1:44:08 PM
StartTimestamp :
LastUpdateTimestamp : 1/16/2014 1:44:10 PM
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp :
CompletionTimestamp :
SuspendedTimestamp :
OverallDuration : 00:00:23
TotalFinalizationDuration :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 00:00:23
TotalInProgressDuration :
TotalStalledDueToCIDuration :
TotalStalledDueToHADuration :
TotalStalledDueToReadThrottle :
TotalStalledDueToWriteThrottle :
TotalStalledDueToReadCpu :
TotalStalledDueToWriteCpu :
TotalStalledDueToReadUnknown :
TotalStalledDueToWriteUnknown :
TotalTransientFailureDuration :
TotalIdleDuration :
MRSServerName :
EstimatedTransferSize : 0 B (0 bytes)
EstimatedTransferItemCount : 0
BytesTransferred :
BytesTransferredPerMinute :
ItemsTransferred :
PercentComplete : 0
PositionInQueue : 6/6 (Position/Queue Length)
PreventCompletion : True
FailureCode :
FailureType :
FailureSide :
Message :
PoisonCount : 0
FailureTimestamp :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : 238914aa-baf7-42b2-91d0-4b27e22e3a81
RequestQueue : ANPIMDB02
ExchangeGuid : 0c62c485-3fd1-4aaf-b29d-67cfa078ac41
Identity : 6209b848-c493-4147-9937-d91e3f16f846\238914aa-baf7-42b2-91d0-4b27e22e3a81
DiagnosticInfo :
Report : 1/16/2014 1:44:07 PM [LSVGNV04EXC01] 'anpinetwork.com/Springfield/Users and
Computers/Network Services/Users/Mitch Givner' created request.
ObjectState : New
[PS] C:\Windows\system32> -
Exchange 2013 user cann't access exchange 2013 public folder
Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007:(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013:(primary site)shcas01,shcas02; (DR site)wxcas01
Identity : SHCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHCAS02\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : WXCAS01\Rpc (Default Web Site)
InternalHostname : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : True
ExternalHostname : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL04\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : SHMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL05\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}
Identity : DRPMAIL06\Rpc (Default Web Site)
InternalHostname :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl : False
ExternalHostname : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl : True
IISAuthenticationMethods : {Ntlm}Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver -
Exchange 2013 users cannot open public folders on exchange 2010
Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggestHello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support
Maybe you are looking for
-
Exception Handling in RFC lookup
Hi Experts, I have a query in RFC Lookup function working with PI 7.1, file to Idoc scenario. I am using Enhance Receiver Determination to find the dynamic recivers.Here we have used a Functional Module which gives an output according to the the inp
-
after running mac tuneup got a red dot on the hard drive icon, nothing would respond, now on restart cant get past white screen with apple logo, mac tune up disk still in laptop
-
I have an HP desktop in my classroom. I do most of my work on my mac, I have files I would like to send to my desktop. Is this possible?
-
My iPod is locked (stop to work) do 1 hour
I was doing a Mobli, and it lock, do 1 hour and it don't answer nothing. I tried pressing the, place to load and nothing. Please help me.
-
OracleVM doesn't see all available memory
After installing OracleVM on DELL 6650 with 8GB of RAM, OracleVM can see only 679MB?? BIOS detected proper 8G of memory. Any ideas?