File:// Links not working on Chrome or Edge (Chromium)
We've recently encountered an issue with IE11, and are trying to move to a different browser solution on company Workstations. Our intranet is Sharepoing 2013 (On-Prem), and we have a large number of documents linked in "file://" format. I would like to avoid replacing every single document on our intranet with a different link format; does anyone know of a way for Chromium based browsers to open "file://" based links in file explorer. I am aware of the "file://" chrome extension that opens them in an index search, but we want the links to open in file explorer. Thanks for your time! ~JP
Using Sharepoint as Virtual Data Room (VDR)
I am very new to SharePoint and I have been tasked to set up a VDR using SharePoint. It is for sharing and collaborating with external partners. Important features of a VDR are, but not limited to: 1) User Management and Control (User login, Login auto expiry, Assigning access permission etc) 2) Data Management and Control (Access permission, watermarking, cannot download/save, cannot print, cannot edit etc) 3) User Activity Report (when did user login, frequency of login, which files, etc) I am not able to find much resources for this. I am wondering anyone here has any experience setting up a VDR via Sharepoint. And if you could share best practice or any advice, will be much appreciated. Many thanks in advance. Cheers, jwExchange Hybrid Configuration Wizard - Error 1603 - Connector registration failed
Did any of you encounter this error while installing hcw on an exchange server? Here is the event viewer error details: Connector registration failed: Make sure you are a Global Administrator of your Active Directory to register the Connector. Error: '"The registration request was denied. "'How to Troubleshoot EWS Connection Issues Using EWS Editor
How to Troubleshoot EWS Connection Issues Using EWS Editor Problem: You get errors when you use any application to connect to (or execute a specific action upon) a mailbox or public folder via the Exchange Web Services (EWS) protocol. Solution: To verify if an error is related to application or to your environment, you can use a tool called EWS Editor to connect to the mailbox or public folder that causes errors and check if the error appears. This can be very useful in scenarios when: An application cannot establish connection to a mailbox or upload/download required data An application cannot access public folders An application cannot impersonate a mailbox – Connecting to a mailbox via EWSEditor 1. Go to the https://github.com/dseph/EwsEditor/releases and download the bin package. 2. Copy the downloaded file to the machine where application is installed and extract it. 3. Open the program and click File > New Exchange Service (Fig. 1.). Fig. 1. Creating a new EWS connection to a mailbox in EWSEditor. 4. Use the Autodiscover Email option or manually provide the Service URL by using the FQDN of the machine you are connecting to (CAS server). If you use Office 365, click the 365 Default button (Fig. 2.). Note : The Service URL for EWS should be as follows: https: machine FQDN>/EWS/Exchange.asmx for example: https://exchange.example.com/EWS/Exchange.asmx Fig. 2. Configuring the EWS connection. 5. Configure the authentication options: o Direct access: If you want to access your mailbox directly, select Use the following credentials instead of the default Windows credentials and provide the user name and password for that mailbox account (Fig. 3.). o Mailbox impersonation: If you want to connect to another mailbox by using the admin’s credentials, click Use the following credentials instead of the default Windows credentials and provide the administrator’s credentials. After that, select the Check if using EWS Impersonation checkbox and provide the primary SMTP address of the mailbox you want to access. Fig. 4. Configuring a connection to a mailbox as an administrator, by using impersonation. 6. When the configuration is complete, click OK. If the connection is successful, you will see a confirmation in the program. If the connection is not successful, the software will throw an error. The appearance of any errors means that the mailbox connection problem is not related to your application and the problem relates to your environment. If you are getting Error 500, then probably your XML configuration file for web services (including EWS) is corrupted. Please consider reverting any recent changes made to that file. Browsing a mailbox Directly after you finish configuring the connection, you get a prompt asking if you want to add the mailbox root to the tree view. Please confirm by clicking Yes (Fig. 5.). Fig. 5. The prompt that allows you to browse the mailbox content in EWSEditor. After the addition is complete, you can browse the content of your mailbox under Root\Top of Information Store (Fig. 6.). If you are getting any errors while accessing any of the folders within that container, it means that the mailbox is corrupted. Fig. 6. Browsing the content of a mailbox. Browsing public folders To browse public folders of a mailbox account that you added to the EWSEditor’s tree view, right-click the name (email address) of the mailbox at the very top of the tree, and select Add Root Folder. After selecting Identify folder by well known name, choose PublicFoldersRoot (Fig. 7.) and click OK. Fig. 7. Adding public folders to the mailbox tree view. If you are getting any errors when accessing public folders, this might mean that public folders are not yet created or their creation is still pending. However, if you are getting trouble accessing some particular public folders, it means that you are missing some of the required permissions. Reference : http://jasparrow.info/2020/08/how-to-troubleshoot-ews-connection-by-using-ews-editor/ Regards JasonConfluence to SharePoint migration
https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® is an essential part of the efficient SharePoint®deployment strategy for organizations of any structure and size. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® dramatically reduces the effort and time for migration to SharePoint®, eliminates migration errors and ensures that the entire corporate digital archive is seamlessly moved to new digital platform. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/ supports Confluence on premise servers and Confluence online, SharePoint 2010, 2013, 2016 and SharePoint Online. It transfers text, images, tables, wiki pages, documents, files, videos etc. Despite evident advantages and improvements offered by SharePoint®, the decision for the actual deployment of the portal does not always come easy. It is complicated with concerns about large amounts of corporate documents spread across legacy storage sites, such as existing intranet sites, network accessible storage (NAS) and even local hard disks of user workstations. Associated expenses for content migration and potential disruptions of access during the transition can be significant arguments impeding the important management decision. https://caseagile.com/products/enterprise-bridge/confluence-to-sharepoint-migration/® resolves these concerns in a simple and elegant way by offering automated content migration scenarios enforced with elaborate transformation engine supporting conversion of data, meta-data, security and permissions. Migration of data from Confluence ® (cloud or on-premise) to SharePoint ® Online, 2016, 2013 or 2010. Migration of text, images, tables, wiki pages, documents, files, videos and other content to SharePoint ® . Spaces, when migrated to SharePoint ® are distinguished and identifiable. Pages and sub-pages, after migration, are in the same order as that of Confluence ® . Migration of most widely spread and popular Confluence ® macros. Maintains the source page formatting. Wiki pages migrated to SharePoint ® are in the same format as that of the Confluence ® in terms of text, images, links and more. Links to other Confluence ® pages and documents (Related Articles) remain intact when migrated to SharePoint ® . Created and modified dates of the spaces, pages and files remain the same after migration. Owners and contributors of the spaces, pages and files remain the same after migration, as well as permissions of users and groups as they existed on source server. Labels on each page come across when migrated to SharePoint ® . Destination SharePoint ® fields for this content are configurable through visual mapping. Support two-factor authentication and proxy. Full compliance to most rigid and contemporary corporate security standards.How to Properly Delete Custom Columns in SharePoint
SharePoint custom columns have been around for quite some time, but I’m finding that there’s still some confusion on how the various types are used, and more importantly how can you delete them. In this post, I’m hoping to shed some light on the topic. Custom columns form a part of your overall SharePoint Information Architecture. When properly set up, custom columns (or fields as sometimes referred to in SharePoint) are ideal for capturing metadata in a consistent way across various types of content. In SharePoint, you can create custom columns in one of two ways: Custom List Column Custom List columns are created directly within a list (or library). They can be accessed via the list and used to store information. Although quick to set up, one of the major drawbacks is that list columns are limited in scope to only the list in which you created them. You cannot leverage the site columns outside of the list. This reason alone can prevent such columns from being considered for scalable solutions where you would have to add the same columns to multiple lists or libraries throughout a SharePoint site. Custom Site Columns Custom Site columns, as their name suggests, are created at the site level. Unlike their List Column relatives, the Site columns are accessible throughout the entire site collection, where you can add them to any number of lists, libraries, and content types. When you change the Site column properties, you have the choice to propagate these changes to all instances where the Site column is in use. Deleting Custom Columns If you wish to remove a custom column, it’s important to understand your options and the ramification they have on your data as described below. Deleting a List Column As I’ve mentioned earlier, when you create a new column within a list or library (not selected from pre-existing site columns), the list owns the column, and the column is only accessible to the list. Therefore, you can easily delete it from the List Settings by selecting the column and then clicking the Delete button on the form. Keep in mind that once you delete the list column, you also lose any data associated with the column. Deleting a Site Column from a List A reference to the site column is added when you add a site column directly to a list. As mentioned above, whenever you change the site column, any instances that use it will change as well. In the example below, I’m showing a Date field that has been added directly to two lists. If you try and delete the Date site column, you will see a warning message similar to This site column will be removed and all list columns which were created from it will be permanently orphaned. Are you sure you want to delete this site column? What does orphaned mean? Well, think of the site column as being the parent that controls its children (the referencing site columns within the lists). They will behave as their parent does. When you delete the parent, then you are in essence converting the site columns within the lists into list columns that lose the relationship between them. In other words, each list will have its unique copy of the site column with all the same settings just before you deleted the site column. You cannot undo this change. Deleting a Site Column from a Content Type When you add a site column to a content type, you’re following better practices for your Information Architecture by encapsulating all required metadata into a reusable entity (content type) rather than dealing with the individual site columns in each list. On the flip side, deleting your site column now becomes a bit trickier. If you tried to remove a site column that is associated with a content type, you might have seen a message as Site columns which are included in content types cannot be deleted. Remove all references to this site column prior to deleting it. What you need to do in this case is remove the site column from each content type before removing it. But what do you do if you don’t know where it’s used? In this case, you can leverage PowerShell to help you get the answer you need. To find out what content types are using your site column, you first need to know the InternalName of your site column. You find it by going to the site column (Site Settings à Site Columns) and looking at the URL as depicted below. In my case, the field is called Date1. Now you can run the script below that is based on OfficeDev PnP to search all the content types in a site collection. The script lists all the content types that use the site column you wish to delete (NOTE: to run the code I’ve supplied below, you must install the OFficeDev PnP solution first from https://github.com/OfficeDev/PnP-PowerShell). Connect-Sponline -url "your_tenant_url" $fieldInternalName = "your_field" $web = Get-SPOWeb Write-Host "Searching for:" Write-Host "InternalName: $fieldInternalName" Write-Host Write-Host "Get Content Types" $cTypes = Get-SPOContentType | where {($_.Hidden -eq $False) -and ($_.Group -ne "_Hidden")} # Search through all the non-hidden content type and find which ones include the site column foreach($ct in $cTypes) { $fields = $ct.Fields $web.Context.Load($fields) $web.Context.ExecuteQuery() $field = ($fields | where {$_.InternalName -eq $fieldInternalName}) if ($field -ne $null) { Write-Host "Content Types: $($ct.Name)" Write-Host "Content Type ID: $($ct.ID)" } } The output will look something similar to the image below. Searching for: InternalName: Date1 Get Content Types Content Types: TestCT Content Type ID: 0x01010038A3F80D4105C845BDD6A523CB1CC969 Now you need to go to the Content Types (Site Settings à Site Content Types) and look for the content types by name. If you see any duplicates, compare the content type ID against the one listed in the URL. Just remember, removing the columns from the content type will delete the content of those columns. That’s it. Now you know what to look for when removing your custom columns. Good luck.
Understanding Groups vs Team Sites, need help
Hey everyone, I'm struggling to understand the differences between these two site types, as we are starting to roll out SPO through our organization. Just having a few questions before I write up our proposal to management Is there a difference between team sites and group sites going forward? Are groups just replacing teams? Is there a way to convert one to another? Is there a need to? Is there any method for creating Modern team sites or is there a difference between modern and "classic/2013 look and feel" sites? I found a number of articles about creating 'Modern' sites, but they are just creating group sites (like this using pnp powershell https://github.com/SharePoint/PnP-Guidance/blob/master/articles/modern-experience-customizations-provisioning-sites.md) This is what leaves me confused about the differences between the two. I'm hoping to use modern sites going forward, but don't want to roll out 2013 look/feel to users if something is going to change "soon", would rather just do it all at once. I'm feeling really confused and there is a lack of information that's easily available.
