Sharepoint 2010 Compatibility Matrix
Carlito Austin
PTC recieves a fair amount of questions about providing an integration to Office365 lately. I'm curious if there's folks out there using Office365 now and what type of connectivity you'd like to have with Windchill?
To me, the main difference is the option to use the Microsoft Office Web Applications instead of the locally installed Office applications and the content has a high probability of residing in the O365 cloud, OneDrive or an on-premise SharePoint implementation. The Office Web Apps are only supported on SharePoint and cannot be directly integrated into a non-SharePoint solution.
The main concern for us is not to compound this issue by adding compatibility of MS office into the mix. For us this means O365 support across a broad range of Windchill versions is much more important than broader O365 functionality supported on limited Windchill releases.
I am for less systems the better and since Sharepoint can't handle CAD files, and Windchill can handle the files as Sharepoint does. My view is Sharepoint should be migrated to Windchill and sharepoint closed or kept for general blabla discussion which does not add value into the company knowledge work.
Our IT department is looking at implementing this. In my discussion with them, they think that it will not have any affect on Windchill. If this is not the case, could you please let me know so I can talk with them. They steamrolled Office 2013 through and are already talking about steamrolling Office 2016 through, which isn't even out.
No our Windchill and SharePoint are not integrated. We use SharePoint for our corporate intranet. We do put documents out there but more from a sharing standpoint. We do have documents that we put in Windchill, but those have one of two purposes. 1. We have a workflow for approval signatures or 2. we are directly relating them to a workflow document or an end item/part. There are a couple of instances where we have overlap because not everyone has access to Windchill.
PTC fully supports Office365 as long as you have purchased a license that includes the local Office applications. If you have MS Office on your local machine, you can work with Windchill documents with or without Windchill Desktop Integration. If you only have access to the cloud version of the Office apps, you will not be able to work with Windchill as easily since these apps are geared at working with content in the Office365 vault.
You'll need to verify their licensing model. Many companies are going to Office365, but buying the license that includes local Office applications vs. cloud only. As long as you have access to local Office applications, you have full access to Windchill Desktop Integration and Windchill. Once the content files are uploaded and stored in the Office365 (SharePoint) cloud, the only Windchill integration is a URL Link Document. Not sure why everyone thinks Office365 and SharePoint are different from traditional ECM or DM solutions; once you've vaulted your files in another system, that is the system of record.
Dave, that is the $$ question. For me, its whatever system you put it in. If your document is located in Office365 (OneDrive), Windchill has no knowledge of it, no access to it and therefore no way to control it. As a customer, you would be forced to use the workflow and approval controls in Office365. The opposite is true if we turn the tables. If the document is located in Windchill, Office365 will have no knowledge of it, no access to it and therefore no way to control it.
To add to that, as I know you will no doubt see the FireFox support in there, this is just adding level two support into the browser compatibility matrix for SharePoint, this still means that not everything will work as good as it does in IE, however, they are providing better support. IE8 is, of course, going to be in the level one support browser compatibility matrix.
And with governance in mind, you may want to think about locking down your installation to control the usage of SharePoint Designer. Here is a great post from the SharePoint Designer Team Blog that talks about how to lock down SharePoint Designer within your SharePoint environment: -down-sharepoint-designer.aspx
Important: We only test the latest maintenance releases of BIG-IP and update their corresponding compatibility matrices. To find the latest maintenance release of BIG-IP, refer to the article. You should then refer to the latest compatibility matrix of that version for an updated list of supported software.
F5 Networks supports the functionality of BIG-IP Access Policy Manager on the most-used platforms and ensures support with the commonly used operating systems (OS) and browsers. Both IPv4 and IPv4+IPv6 deployments are supported, except as noted below.
F5 Networks supports the listed operating systems and browser releases, with the latest service pack or service pack equivalent, for up to 3 years from the time of initial release, as long as the listed operating systems and browsers are still supported by the vendor.
If an operating system or browser vendor ends mainstream support before the end of that 3 year period for a release or service pack, F5 Networks will also end support at the same time. Once an operating system or browser has surpassed the 3-year date from release, F5 Networks will continue to monitor the user base of this operating system or browser release. When a release reaches a usage level that can no longer justify development, test, and support resources, we will issue an EoL (End of Life) Solution at least three months prior to the planned EoDS (End of Development Support).
Once a release has passed two years from the release date, F5 Networks will monitor the user base of this release. When a release reaches a usage level that can no longer justify development, test, and support resources, we will issue an EoL (End of Life) Solution at least three months prior to the planned EoDS (End of Development Support).
F5 Networks supports 32-bit and 64-bit versions of Windows 10 running Microsoft Edge, Firefox, or Chrome. Other browsers using F5 Helper Applications can support 32-bit and 64-bit versions to provide Network Access and Endpoint Check functionality.
Note: F5 does not support the Microsoft Internet Explorer 11 desktop application as it went out of support. For more information, refer to the Lifecycle policy for Internet Explorer and Microsoft Edge.
Note: For Network Access support, install F5 Access (previously known as BIG-IP Edge Client) from Google Play. Only the latest version of F5 Access is available on Google Play Store. The BIG-IP Edge Portal app, which previously provided secure mobile access to enterprise web applications, is no longer provided for download.
Application tunnels and MS RDP Terminal Services are not supported on these platforms. Windows RT supports Network Access through Inbox F5 VPN Client. Network Access is supported on Windows Phone 8.1 using BIG-IP Edge Client for Windows Phone 8.1 that is available from the Windows Phone Store.
Java SE 7 and Java SE 8 have been fully qualified by F5. Java-related features can't be utilized using Google Chrome on OS X and Linux because Google Chrome doesn't support Java plugin on OS X and Linux.
* APM supports BLAST and BLAST Extreme protocol over TCP and UDP and also supports the Blast Extreme Adaptive Transport (BEAT) for Windows and Linux desktops and applications. APM supports VMware True SSO with Horizon.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
c80f0f1006