SPAM and Exchange 2010 Mail-enabled Public Folders
Is there a way to determine if mail sent to our Exchange 2010 mail-enabled Public Folders by our customers is ever rejected because it was tagged as spam? The concern is that we might not be receiving some email. We rely on the mail-enabled PF's
heavily, but since they aren't a mailbox there is no Junk E-mail folder to check. We do not have the resources to check EOP on a regular basis throughout the day, and the customer would not get an NDR or anything like that.
HDL
Hi,
You can consider to use Message Tracking tool under EMC -> Toolbox to track these messages.
Understanding Message Tracking
https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
Search Message Tracking Logs
https://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support
Similar Messages
-
We are in the process of trying to decommission our Exchange 2003 server, all of the replicas have been moved to the Exchange 2010 SP3 servers. However, each time we dismount the public folder store on the 2003 server (just to see what won't work) nobody
from outside the company can send mail to the mail-enabled public folders (we use these to communicate with vendors and customers).....they sit in the 2003 mail queue until I remount the store.
I have mail disabled them on the 2010 PF server, waited a few hours and then mail enabled them again. Same issue. Interesting to note is that when the PF store on the 2003 server is dismounted people inside
the company can still send to the mail-enabled PFs (which is good). I am stumped.
HDLHi,
There is similar issue in the below post.
https://social.technet.microsoft.com/Forums/exchange/en-US/20dc0f53-41c2-4275-a391-fd9b0907a7e1/after-move-all-replicas-to-exchange-2010-mail-enable-public-folder-stops-receiving-external-emails?forum=exchangesvrdeploylegacy -
Collect name, Identity, parentpath and PrimarySmtpAddress of all mail enabled public folders.
Hi,
I’m trying to collect the name, Identity, parentpath and PrimarySmtpAddress of all mail enabled public folders. PrimarySmtpAddress returns empty whatever I do. If I use this same cmd-line then it works fine.
What am I doing wrong? Here is the powershell code I'm using:
Get-PublicFolder \ -Recurse -resultsize unlimited | ? {$_.MailEnabled -eq $true} | Select-Object Name,Identity,parentPath, `
@{label='PrimarySmtpAddress';expression={"$((Get-MailPublicFolder '$_.Identity').PrimarySmtpAddress)"}}
Thanks in advance!
win_builderThe ps code next is getting the info i want to collect:
Credit goes to travis5150 and Chris Dent from expert exchange
cls
$publFolders = get-publicfolder -resultsize unlimited -recurse | ? {$_.MailEnabled -eq $true}
@(foreach ($publFldr in $publFolders){
$objProp = "" | Select Name,Alias,Identity,ParentPath,PrimarySmtpAddress
$objProp.name = $publFldr.name
$objProp.Identity = ($publFldr.Identity)
$objProp.parentpath = $publFldr.parentpath
$objProp.Alias = (get-mailpublicfolder -id $publFldr.identity | select -exp Alias)
$objProp.PrimarySmtpAddress = (get-mailpublicfolder -id $publFldr.identity | select -exp PrimarySmtpAddress)
$objProp
Thanks for your help and time!!
win_builder -
Mail-enabled Public Folders not showing as enabled in PFMC or EMS
Good morning
I have some PF's that are mail enabled, but running the Get-PublicFolder cmdlet shows "mailenabled" attribute as False. Also, in the PF Management Console, the folder shows as not mail enabled (with an option to enable it).
I found this thread that seems to be related:
http://social.technet.microsoft.com/Forums/exchange/en-US/918aad03-c96f-4023-89cc-ec2c66e51b93/mailenabled-public-folders-not-showing-as-mailenabled?forum=exchangesvrgenerallegacy
I'd like to do some testing, but recreating this issue with a test PF is actually really hard.
Does anyone know a way to force that "mailenabled" attribute to False after mail-enabling a PF? I can't find any ADSI attribute that is obvious. I changed MsExchRecipientTypeDetails to <not set> but that didn't do it...
**UPDATE** I just found out that msExchMailboxGuid is missing from that object. Does anyone have any kind of suggestion for how I can find the Guid of the mailbox that is no longer associated with this PF?
**UPDATE 2** I have found other PF's that are missing this attribute, but they are not displaying any symptoms. They are showing as mail enabled in the EMS and PFMC. So I guess this isn't a required attribute.
Could anyone explain the purpose of this attribute for mail-enabled public folders? I just assumed it was required.
Thanks!Hi,
Do you migrate these mail-enabled public folders from previous Exchange server to Exchange 2010?
Please check if you can see the SMTP address for mail-enabled public folders via Properties of Public folders.
Please check if they show in the Microsoft Exchange System Objects in ADUC.
Besides, I recommend you mail disable the public folder and then mail enable it again to check the result in the Public Folder Management Console.
For a mail-enabled recipient, a minimum set of attributes is required to make all Exchange components work properly. For example, a mail-enabled entry (a user, contact, group, or public folder) has to have at least these attributes: mailNickname, legacyExchangeDN,
and displayName. Without the mailNickname attribute, an object is not considered mail-enabled.
Best regards,
Belinda
Belinda Ma
TechNet Community Support -
Mail-enabled Public Folders Not showing as Mail-enabled
We have completely migrated from Exchange 2003 to Exchange 2007 (SP1 Rollup 5). Many, but not necessarily all, of our mail-enabled public folders do not appear to be mail enabled in either the 2007 PF Management Console or the Shell, yet they are mail-enabled in the 2003 System Manager and we can send email to them. If we mail-enable a folder in the EMC, it blows away any previous email addresses and creates a new one.
Any reccomendations on how to get 2007 to accurately display the properties of these folders??Issue description: Mail-enabled public folders can’t show as mail-enabled status in the EMC and EMS after migrated from exchange 2003 to exchange 2007, right?
Troubleshooting:
1. Please use “Get-PublicFolder” to check the output of a migrated problematic public folder, see if the value of “MailEnabled” is “True”
Get-PublicFolder -Identity "\problematic public folders name"
2. Please find out where migrated problematic public folder objects exist in the AD. By default, mail-enabled public folders should stay in the “Microsoft Exchange System Objects” container. You can use ADUC or ADSIEditor to verify their current location
3. I assume that link between mail-enabled public folder and its AD object has been broken during the migration. So, I suggest you to create a test mail-enabled public folder, and compare the attributes of its AD objects with the problematic one with ADSIEditor. This will tell us if there are any incorrect values in the attributes of the problematic public folder objects
a. Launch the ADSIEditor (Start->run-> ADSIEditor.msc)
b. Locate problematic mail-enabled public folder object and the new created one
c. Right-click the objects and select “Properties”. Then, compare their attributes in the “Attribute Editor” tab
Notes: Please select all three checkboxes in the “Attribute Editor” tab, it will save more time during the comparison -
Exchange 2010 Mail Enabled Distribution Group Won't Receive from External Address
Let me pre-empt the usual first response: yes, I've unchecked "require that all senders are authenticated" on the Message delivery Restrictions properties of Message Delivery Restrictions. I cannot get a message from an external mail server to
send to an internal mail-enable distribution group. It's working internally. I've checked our ironport and the message is being sent to exchange (at least I think it is).
How can I troubleshoot this?!
tfgeorgeIronport is definitely sending this email to exchange. Please read:
06 Jun 2011 08:53:20 (GMT -05:00)
Protocol SMTP interface Main Interface (IP Gateway IP) on incoming connection (ICID 17720578) from sender IP 65.54.190.154. Reverse DNS host bay0-omc3-s16.bay0.hotmail.com verified yes.
06 Jun 2011 08:53:20 (GMT -05:00)
(ICID 17720578) ACCEPT sender group UNKNOWNLIST match sbrs[-1.0:6.0] SBRS 3.0
06 Jun 2011 08:53:20 (GMT -05:00)
Start message 2136865 on incoming connection (ICID 17720578).
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 enqueued on incoming connection (ICID 17720578) from
[email protected].
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 on incoming connection (ICID 17720578) added recipient ([email protected]).
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 contains message ID header '<[email protected]>'.
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 original subject on injection: TEST
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 (1471 bytes) from
[email protected] ready.
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 matched per-recipient policy DEFAULT for inbound mail policies.
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 scanned by Anti-Spam engine: CASE. Interim verdict: Negative
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 scanned by Anti-Spam engine CASE. Interim verdict: definitely negative.
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 scanned by Anti-Spam engine: CASE. Final verdict: Negative
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 scanned by Anti-Virus engine Sophos. Interim verdict: CLEAN
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 scanned by Anti-Virus engine. Final verdict: Negative
06 Jun 2011 08:53:20 (GMT -05:00)
Message 2136865 queued for delivery.
06 Jun 2011 08:53:20 (GMT -05:00)
SMTP delivery connection (DCID 1658840) opened from IronPort interface 100.100.100.100 to IP address 100.100.100.100 on port 25.
06 Jun 2011 08:53:20 (GMT -05:00)
(DCID 1658840) Delivery started for message 2136865 to
[email protected].
06 Jun 2011 08:53:21 (GMT -05:00)
(DCID 1658840) Delivery details: Message 2136865 sent to
[email protected]
06 Jun 2011 08:53:21 (GMT -05:00)
Message 2136865 to
[email protected] received remote SMTP response '2.6.0 <[email protected]> [InternalId=919833] Queued mail for delivery'.
tfgeorge -
Exchange 2013 delivery reports for mail enabled public folder
How can I get delivery reports for mail enabled public folders? Would I search the related public folder mailbox?
Hi,
When you track messages using Delivery Reports, you can only choose user mailbox when you select mailbox to search. Under the option "Mailbox to search", there is no mail-enabled public folder listed there for you to select from
the address book.
But you can search messages sent to or received from mail-enabled public folder.
Track messages with delivery reports
http://technet.microsoft.com/en-GB/library/jj150554(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support -
Mail Enabled Public Folder Issues after migration online
Hi
We have recently migrated our Legacy (Exchange 2010) Public Folder Infrastructure to Exchange Online - we have a hybrid setup, SSO and DirSync.
We initially had an issue where some of our mail enabled public folders had lost their link with the associated MailPublicFolder objects and as such could not receive email.
We resolved this issue ourselves however we are now experiencing a different issue which i believe should be easily resolvable however this isn't the case at the minute.
The issue is that when a user emails a Mail Enabled Public folder Exchange online is attempting to relay the email back to our onPrem servers. This is occuring for the bulk of our Mail Enabled Public Folders - we have ~1200 of these. The only
folders that are working as expected are those that had the initial issue above and for which we had to remove and re mail enable these folders. We also had to recreate any secondary smtp address for these folders. This accounts for 88 of our total
MEPFs.
I have checked the attributes on the MailPublicFolder objects for those that are not working and those that are functioning as expected. The only difference in these that I can see is that the MEPFs with the issue have a value set in the ExternalEmailAddressAttribute.
I have tried to programatically set this value to $Null however i receive the following error:
The external e-mail address $null is not an SMTP e-mail address.
I have also tried the following : set-mailpublicfolder -Identity "MEPF"-ExternalEmailAddress "<not set>"
with the same resultAttempting to use the following syntax -externalemailaddress @{remove=$oldAddress} returns the following error:
Cannot process argument transformation on parameter 'ExternalEmailAddress'.Cannot convert the "System.Collections.Hashtable" value of type"System.Collections.Hashtable" to type "Microsoft.Exchange.Data.ProxyAddress".
At present the only fix that I have for this is to take a copy of the email addresses for an affected public folder, Mail disable it, wait for the object to be cleared, re-enable the public folder as a mail public folder and then re-add the email addresses.
This is ok on an adhoc basis but not for the ~1200 folders that are affected. Especially when from what i can see it should be relatively straightforward to resolve this with a simple PowerShell script.
I do have a case open with MS for this but I am hoping that somebody here can help also.
Thanks
JoeOk so i fixed it myself.
The thinking here is that the ExternalEmailAddress was set using the Primary SMTP address while the Public Folders were on premises.
In order to get the required information we ran a script to export all the MailPublicFolder objects which had a value in the ExternalEmailAddress attribute. We exported the Name, ExternalEmailAddress and GUID
We then ran a second script to export the Identity, MailRecipientGuid from Get-PublicFolder -recurse.
The MailRecipientGUID is what ties the Mail Enabled Public folder to the MailPublicFolder object.
Using Excel I then matched the two up and created a csv file with the Identity Attribute from the get-PublicFolder command and the ExternalEmailAddress Attribute from Get-MailPublicFolder.
The following script then used this csv file to first Mail Disable the Public Folder, then Mail Enable the Public Folder.
Once these steps have been completed the final stage is to add the SMTP address back in to the Public folder.
To do this it is necessary to retrieve the new MailRecipientGUID and use it to return the MailPublicFolder for the Set-MailPublicFolder command.
I was happy to use this script after i tested with a small subset of the data. It is provided as is with no guarantee that it will be suitable for you to use and any use of this script is at your own risk.
Script to Automatically fix brokenn Public Folder Objects
Created By: Joe McGrath
Created On: 18/02/2014
$Path = "C:\PublicFolders.csv"
import-csv -Path $Path | ForEach-Object `
Disable-MailPublicFolder -identity $_.Identity -Confirm:$False
Write-Host "Broken Public Folders Now Mail Disabled"
Write-Host "Waiting for commands to be fully processed online - the script will continue in 5 minutes"
Start-Sleep 300
Write-Host "Re MailEnabling Public Folders"
import-csv -Path $Path | ForEach-Object `
Enable-MailPublicFolder -identity $_.Identity
Write-host "Broken Public Folders now enabled"
Write-Host "Now waiting to allow online service to catch up - script will continute in 5 minutes"
Start-Sleep 300
Write-Host "Updating email addresses for broken public folders"
import-csv -Path $Path | ForEach-Object `
$NewPF = get-publicfolder -identity $_.Identity
Write-Host $NewPF.Identity
Write-host $newPF.MailRecipientGuid
$EmailAddresses = $_.AdditionalEMailAddresses
$NewMailPF = get-MailPublicFolder -resultsize unlimited | Where-Object {$_.Guid -eq $NewPF.MailRecipientGuid}
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddresses $EmailAddresses -EmailAddressPolicyEnabled:$FALSE
Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$TRUE
$EmailAddresses = ""
Write-Host "Completed!" -
Migrating email-enabled public folders corrupted
We migrated our public folders from EX 2010 to 2013 but currently face 2 issues with the import:
a. All public folders/subfolders became email disabled - about 300 + folders
b. More importantly there is a mismatch between folder name and assigned smtp addess.
For example imported folder name is qa1 smtp associated with the folder is [email protected]
is there a powershell script we can run to fix these issues ?
alex serdyukovHi,
A. If you use serial migration to migrate public folders, then Mail-enabled public folders that are created after a public folder migration is started won't be mail-enabled in the destination organization. You'll need to manually mail-enable
these public folders manually when the migration is complete. This also applies to public folders that existed prior to migration starting, but were mail-enabled after migration started.
Refer from
https://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
B. After these public folder are enabled, then check these mail-enabled public folders’ SMTP address.
If they are also mismatched, please check if the emailaddresspolicy is assigned to them with the following command
Get-MailPuclicFolder “PF path” | fl EmailAddressPolicyEnabled
If the value is true, then set this value to false and use the following command to correct them (or check email address policy)
$allPF = Get-MailPublicFolder -Resultsize unlimited
Foreach ($PF in $allPF)
{Set-MailPublicFolder -Identity $PF.identity -PrimarySmtpAddress ($PF.alias+’@company.com’)}
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx -
Hello,
I'm trying to allow a mail enabled public folder permissions to send to a mail universal security group. In the past if I wanted to add a PF as an allowed sender I would do it via the AuthOrig setting on that group using adsiedit. I just noticed today
that if I add the PFs DN to that attribute of the group, nothing happens. No matter how long I wait the PF never shows up under the allowed senders list on the group. If you try and send as the PF you get a bounce about not being allowed to send to that
group. If I go back into AD and check, the PF is still listed under the AuthOrig attribute. I tried this on a few different groups and with a few different PF and I'm stumped. I think the last time I had to update this setting on a group
was before I installed roll-up 5 for SP3.
If I do the same test with a user, it works as it should and they show up in the allowed senders list.
If I take a group that isn't restricted to specific senders and add a PF DN to the AuthOrig attribute of the group, the button in the message delivery restrictions for that group in the EMC will change from all senders to only senders in the following list,
but the PF wont be listed in the box of allowed senders. If I remove it from the AuthOrig attribute the group will change back to allow all senders. It's really weird, so any help or light you can shed on this would be greatly appreciated.
-MarkHello,
I check many threads and articles, but there is no related information to verify the issue.
If your purpose is that adding a mail-enabled public folder to allowed senders on a distribution group, there is a workaround method. You can create a new distribution group, and then add the public folder to the new distribution group, and add
the new distribution group to the Only senders in the following list field of the target distribution group.
Here is an article for your reference.
http://support.microsoft.com/kb/2746885
Cara Chen
TechNet Community Support -
Hi. I'm migrate to Exchange 2013. I moved mailbox, moved public folders ( 20 folders in one pf-mailbox). I can see structure public folders, but when i send mail to public folders, i see error: this recepient not found
Формирующий сервер: EXCHANGE2013.polikomm.local
Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'
Can you help meHi,
Please use the Get-PublicFolderStatistics command to check result.
Please disable this affected public folder and re-enable it to check result.
Please create a new public folder and mail-enable it, then send message to this new folder to check result.
And please check if this issue persists in OWA.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support -
EXCH 2007: All email addresses forwarded to a mail-enabled Public Folder
I need to find all mailboxes and their aliaes that are setup to be Forwarded to a mail-enabled public folder. Is there an Exchange Mangement Shell script that I can run that will produce that list for me? Or some other way of finding those mailboxes/aliases?
Thanks
MattHi Matt,
We can try the following command (proposing that Winnie is the Mail-enabled public folder):
Get-Mailbox | Where-Object { $_.ForwardingAddress -eq “Domain.com/Microsoft Exchange System Objects/Winnie” } | Select Name, ForwardingAddress, DeliverToMailboxAndForward
Hope it works.
Thanks,
Winnie Liang
TechNet Community Support -
My macbook air cannot sync with my office microsoft exchange 2010 mail server
My macbook air cannot sync with my office microsoft exchange 2010 mail server.
It used to work perfectly, and then I lost connection and was never able to establish one. I re-istalled my e-mail account several times, no success.I am sure all of you got your email issues sorted out by now but i was having trouble settings up exchange email on my Iphone 5S, and the problem i found was to go to settings, icloud, then log into icloud with your apple id first (before setting up the exchange email). Once i logged into my icloud account on my Phone 5S, the exchange server email starting working and synching right away.
to confirm this worked, i even deleted my email account and deleted my Icloud accounts both from my iphone was able to simulated the same exact problem (exchange server would not sync with my Iphone 5S) until i logged back into my Icloud account on my 5S.
Again once i logged into Icloud, the exchange server issues went completely away.
Just wanted to post this so anyone else having the issue could see. -
Problems with a shared calendar using Outlook 2007 and Exchange 2010
Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support
Maybe you are looking for
-
I have two iPads under the one user ID. Mine and my 4 year olds. When making purchases for the App Store, the purchase goes to both IPads. How do I stop content going to both? Any help would be great.
-
When I installed jms (j2ee1.3) my lookups doesn't work anymore...
Hi. I was using j2se 1.3 and performed some lookups on objects from an Oracle 8.1.7. Then, in order to use jms, I installed j2ee 1.3 and j2se 1.3.1. Now my lookups doesn't work anymore, but my lookups on jms objects (por example Queue or QueueConnect
-
Can a servlet start it's own threads ?
Is there any problems with having a servlet start multiple threads to access different databases. In this way the database calls to not have to be synchronous. I'm concerned about starting additional threads from the servlet, while running under iPla
-
We have a salary statement designed in PE51. This has been desgined to be mass printed as a pay stub. When this same form is plugged in ESS , the form alignment is not correct - which is obvious becuase this was created keeping in mind that it will
-
Adobe PDF (Low on memory)- E61
I can't view video clips not documents. Can Someone in Nokia let us know if this device can be used as a PDA or we're bound to have only a large phone? Is there a way to free up memory on this device? Moderator's note: This message has been edited in