asked on Microsoft Office 365 and it Exchange Model there in!
Public Folders and public folder shared calendar are basically failing in Office 365 exchange. I have a case with Microsoft underway, but there second level support hasn't given me a definitive answer, and if there isn't any fix for the overall issue then an audit feature would work, and this audit feature appears to be native when using Outlook 2015 for the MAC, and in no other version.
I had asked this question in a prior effort to resolve my ongoing issue, but a lot more data points have come in. I had been perplexed with the configuration of the PCs as all the computers were showing a yellow exclamation over top of the internet icon, and DNS was statically set 127.0.0.1. every time I would try and change this, well, it would revert back. I was at a loss. Then I discovered what the monitoring company was trying to do. They were using, or are using the Open DNS. Its all part of cisco's secure global configuration, and yet the client has a sonic wall firewall. I would have at least expected a brand new meraki device, but I believe most if not all of this has been red hearings. My real problem with the slowing public folders is this; is this how it is designed? As an example, a 7, 8, or 12 meg file can take 40 seconds, 60 second and then even longer for the 12 meg file. The users are doing this movement several times a day. Then I have a lot of users within teams who need to be able to perform bulk transfers where they may take 20-30 sets of emails with attachments and attempt to move them into the public folders. This will often lead to complete failure on the part of Outlook 2016 or 2013, or essentially outlook remains unresponsive through out the entirety.
With the DNS client concerns I have read that the autodiscover records, of which the public folder relies upon, will typically be out of sorts within the cisco secure global configuration model. Is this true? is this just another red herring? Are we exceeding the design specifications of outlook with the Microsoft hosted solution? Has anyone run a similar scenario with their users, and if so was there any resolution to the utilization of this hosted Microsoft solution. The company with this problem had always been an SBS user and they were left without any true alternative when Microsoft scuttled SBS, and they were told that the way to go was just to migrate to the new 365 cloud.
I am working with Microsoft Engineering, but they are not leaving me a great amount of confidence. Its been several days and I have been taking their calls as they have asked follow up questions, and they have sent me down some other rabbit holes as well.
I have a second major component to this that needs handled, and this comes in the form of a true Company wide Calendar. Right now the company, public calendar is hosted within the Public folders. Trouble with this is that its only accessible through the Office Outlook Client, and not on small devices like a IPhone, or a Droid. when I spoke to Microsoft about this they told me to use the Outlook application from the play store, or from apple. Ive tried this, and then I learn that the public folders are not part and parcel to this application. The only way to solve this is through OWA. This is not a good solution. Is this the correct concept? The Outlook apps for the phone will not provide a public accessible calendar? Is there any solution to both of my current problems with this Brave new Microsoft World, or am I grasping at straws? Further, would the only true solution with Exchange be to move back to the true Exchange Model and Co-collocate my own solution? Is this really the maturity level of the office 365 solution with Exchange?
My last question contends with a feature noted within the MAC edition of Outlook. I have one user using this currently at this location. The user has shown me an artifact that remains after he deletes the attachment. This artifact shows the name of the file and when deleted. I will post the exact description of this artifact in the near future. Having this artifact appear in all versions of Outlook would solve so much of my problem, but thus far I have not been able to locate any good information on this .
In conclusion, I have three problems. 1. Slow Public folders, 2. Small device access to the publicly accessible calendar, and the MAC artifact of a deleted attachment. Any help in these matters would be awesome!
I had asked this question in a prior effort to resolve my ongoing issue, but a lot more data points have come in. I had been perplexed with the configuration of the PCs as all the computers were showing a yellow exclamation over top of the internet icon, and DNS was statically set 127.0.0.1. every time I would try and change this, well, it would revert back. I was at a loss. Then I discovered what the monitoring company was trying to do. They were using, or are using the Open DNS. Its all part of cisco's secure global configuration, and yet the client has a sonic wall firewall. I would have at least expected a brand new meraki device, but I believe most if not all of this has been red hearings. My real problem with the slowing public folders is this; is this how it is designed? As an example, a 7, 8, or 12 meg file can take 40 seconds, 60 second and then even longer for the 12 meg file. The users are doing this movement several times a day. Then I have a lot of users within teams who need to be able to perform bulk transfers where they may take 20-30 sets of emails with attachments and attempt to move them into the public folders. This will often lead to complete failure on the part of Outlook 2016 or 2013, or essentially outlook remains unresponsive through out the entirety.
With the DNS client concerns I have read that the autodiscover records, of which the public folder relies upon, will typically be out of sorts within the cisco secure global configuration model. Is this true? is this just another red herring? Are we exceeding the design specifications of outlook with the Microsoft hosted solution? Has anyone run a similar scenario with their users, and if so was there any resolution to the utilization of this hosted Microsoft solution. The company with this problem had always been an SBS user and they were left without any true alternative when Microsoft scuttled SBS, and they were told that the way to go was just to migrate to the new 365 cloud.
I am working with Microsoft Engineering, but they are not leaving me a great amount of confidence. Its been several days and I have been taking their calls as they have asked follow up questions, and they have sent me down some other rabbit holes as well.
I have a second major component to this that needs handled, and this comes in the form of a true Company wide Calendar. Right now the company, public calendar is hosted within the Public folders. Trouble with this is that its only accessible through the Office Outlook Client, and not on small devices like a IPhone, or a Droid. when I spoke to Microsoft about this they told me to use the Outlook application from the play store, or from apple. Ive tried this, and then I learn that the public folders are not part and parcel to this application. The only way to solve this is through OWA. This is not a good solution. Is this the correct concept? The Outlook apps for the phone will not provide a public accessible calendar? Is there any solution to both of my current problems with this Brave new Microsoft World, or am I grasping at straws? Further, would the only true solution with Exchange be to move back to the true Exchange Model and Co-collocate my own solution? Is this really the maturity level of the office 365 solution with Exchange?
My last question contends with a feature noted within the MAC edition of Outlook. I have one user using this currently at this location. The user has shown me an artifact that remains after he deletes the attachment. This artifact shows the name of the file and when deleted. I will post the exact description of this artifact in the near future. Having this artifact appear in all versions of Outlook would solve so much of my problem, but thus far I have not been able to locate any good information on this .
In conclusion, I have three problems. 1. Slow Public folders, 2. Small device access to the publicly accessible calendar, and the MAC artifact of a deleted attachment. Any help in these matters would be awesome!
Microsoft OfficeExchangeMicrosoft 365
Last Comment
Johnny
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Blue Street Tech,
Thanks for the info. My effort with this network and user based solutions is limited to just resolving the issue with the Public Folders. The monitoring company provides boots on the ground as well as the remote grey matter to diagnose proactively issues and troubles with the Network. At least, this is the bill of goods sold to the client.
As I have headed through the process of resolving their dilemma I have come very close to accepting that the Public folders are simply working the way thy are designed. Are there problems with the clients network, and does the IT monitoring company contribute to the shortfall? The answer to that has become very self evident over the past week or so. Some very irregular, and perplexing events have plagued my client, and have further occluded the process I am under.
However, I have taken most of my testing of the public folders off site. I run my testing from a known good network. This has made it clear that the problem persists. Hence, everything on the clients network has been little more than red herrings as it relates to the public folders.
Microsoft has always indicated that the public folder were never designed to be a filing system. My client is using them as an ERP. They have exceeded the design of their intended usage. I thank you for your time!
Thanks for the info. My effort with this network and user based solutions is limited to just resolving the issue with the Public Folders. The monitoring company provides boots on the ground as well as the remote grey matter to diagnose proactively issues and troubles with the Network. At least, this is the bill of goods sold to the client.
As I have headed through the process of resolving their dilemma I have come very close to accepting that the Public folders are simply working the way thy are designed. Are there problems with the clients network, and does the IT monitoring company contribute to the shortfall? The answer to that has become very self evident over the past week or so. Some very irregular, and perplexing events have plagued my client, and have further occluded the process I am under.
However, I have taken most of my testing of the public folders off site. I run my testing from a known good network. This has made it clear that the problem persists. Hence, everything on the clients network has been little more than red herrings as it relates to the public folders.
Microsoft has always indicated that the public folder were never designed to be a filing system. My client is using them as an ERP. They have exceeded the design of their intended usage. I thank you for your time!
My client is using them as an ERP. They have exceeded the design of their intended usage.You hit the nail on the head...They need an ERP system...this is a poor design process, which will lead to other poor decisions and efficiencies.
ASKER
Thank you and sorry been offline for a while.
Yes, Public Folders are pretty much deprecated from a dev standpoint. You should consider moving to Office 365 Groups. They auto populate into the users who have access via AutoMapping and are a much more comprehensive way to collaborate.
If the networking is not an issue I won't address it but I will say OpenDNS has nothing to do with Cisco or SonicWALL. If your management company was/is using them (OpenDNS) 127.0.0.1 is not the correct DNS address for their service and you should never have triangles over your network icons unless there is a severe misconfiguration.
I'm a bit confused if you have a SonicWALL or Cisco firewall, but it sounds like you have the network portion wrapped up. Please let me know if you don't and we can discuss further.