Loading...

Follow Waqas Sarwar SharePoint Blog on Feedspot

Continue with Google
Continue with Facebook
or

Valid

In this article, we will list complete detail about the July 2019 CU for SharePoint Server 2019. Same CU method adopted for SharePoint 2019 as to SharePoint 2016, I mean we will see 2 files each month ( some time one), One for SharePoint fixes and 2nd for Language dependent. These updates also include the security updates as it does in SharePoint Server 2016.

This Month MSFT released one patch for SharePoint server 2019; Security updates also part of the packages.

This month no patch for language depend so if you did not install the most recent language dependent package then use the April 2019 CU language dependent (KB4462221)

Note: In order to patch the SharePoint servers properly, we have to install both packages (language independents as well as language dependents) followed by PSconfig wizard on all servers in farm. We need to install language dependent patch even we don’t have any other language pack installed in the environment.

Improvements, fixes and Security Updates

Here is the list of fixes published by MSFT.

SharePoint Server 2019:

This security update contains improvements and fixes for the following non-security issues:

  • Adds support for the new Japanese era name to the Chinese word breaker to make sure that the name will be broken correctly.
  • Adds the ProjectIdMinDigitProjectIdSeedProjectIdPostfix and ProjectIdPrefix properties in the EnterpriseProjectTypeCreationInformation class. You can now use these properties to update the Project Identifier information of an enterprise project type (EPT) through the client-side object model (CSOM).
  • Adds the ProjectQueuePublishSummary method for the ProjectCollection class in the client-side object model (CSOM) so that project-level fields on a project can be published independently from the entire project. For example, if you use a workflow in your project creation process, you can use this new method to publish the stage summaries.
  • Reduces the severity of certain upgrade sequence messages from WARNING to INFO. These messages indicate that the upgrade action doesn’t have to make any changes because its database extension is not currently enabled in the database. For example, upgrade messages such as the following will no longer be labeled as warnings:

    “Ignoring upgrade sequence: Microsoft.SharePoint.BusinessData.Upgrade.BdcDatabaseExtensionUpgradeSequence because related content database extension Microsoft.SharePoint.BusinessData.SharedService.BdcDatabaseExtension is not enabled.”

  • Updating a fixed duration task assignment from a timesheet may unexpectedly change the assignment’s finish date to an earlier date.
  • Fixes an issue in which resetting the role inheritance by using the SPWeb.ResetRoleInheritancemethod does not work on copied sites that are created by using the Copy-SPSite cmdlet.
  • In some cases, existing files are overwritten even if users don’t explicitly overwrite the files.
  • Fixes an issue in which an Office file that contains the number sign (#) in the file name is downloaded by a user who doesn’t have sufficient permissions on the file.
  • Fixes an issue that prevents the BLOB cache feature from working unless the SharePoint application pool account is a member of the local Administrators group. If you add your SharePoint application pool account to the local Administrators group to work around this issue, we recommend that you remove that account from the local Administrators group after this update is installed. Removing the application pool account from the local Administrators group reduces potential security risks in your SharePoint farm.
  • Fixes an issue that causes an incorrect MIME type to be used for certain types of files that are stored in SharePoint, such as Cascading Style Sheet (.css) files. This may cause web browsers to incorrectly render webpages that depend on those files. To work around this issue, install the following Web Server Role (IIS) feature:

IIS 6 Metabase Compatibility (Web-Metabase)

  • This workaround is no longer necessary after this update is installed. Therefore, you can safely remove the IIS 6 Metabase Compatibility feature from SharePoint servers.
Project Server 2019:
  • No fix released this month
Security Fix:
  • An authentication bypass vulnerability exists in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF), allowing signing of SAML tokens with arbitrary symmetric keys. This vulnerability allows an attacker to impersonate another user, which can lead to elevation of privileges. The vulnerability exists in WCF, WIF 3.5 and above in .NET Framework, WIF 1.0 component in Windows, WIF Nuget package, and WIF implementation in SharePoint.

    An unauthenticated attacker can exploit this by signing a SAML token with any arbitrary symmetric key.

    This security update addresses the issue by ensuring all versions of WCF and WIF validate the key used to sign SAML tokens correctly.

  • A cross-site-scripting (XSS) vulnerability exists when Microsoft SharePoint Server does not properly sanitize a specially crafted web request to an affected SharePoint server. An authenticated attacker could exploit the vulnerability by sending a specially crafted request to an affected SharePoint server.

    The attacker who successfully exploited the vulnerability could then perform cross-site scripting attacks on affected systems and run script in the security context of the current user. The attacks could allow the attacker to read content that the attacker is not authorized to read, use the victim’s identity to take actions on the SharePoint site on behalf of the user, such as change permissions and delete content, and inject malicious content in the browser of the user.

    The security update addresses the vulnerability by helping to ensure that SharePoint Server properly sanitizes web requests.

Language-Dependent Fix:
  • No fix released this month.
Installation

As we know, this Month MSFT Release Only 1 update.

  • Please download the ‘sts2019-kb4475529-fullfile-x64-glb.exe’
    the files and install it on all SharePoint servers.

  • Please run the PSconfig wizard on all server in the farm one by one.
Article Number (KB) Download

Please download the November CU from the below link:

Prerequisite
  • To apply this update, you must have Microsoft SharePoint Server 2019 installed.
Restart information
  • If during the Installation of the Updates Certain Component of the SharePoint is running, then it will ask you for the Restart the server. So its depend upon your server.
Schema Change
  • This update updates the database schema so that the mean schema and Patch Version will change. You will see the same Patch number and Build Number.
Patch Number
  • 16.0.10348.12104 for Language Independent file
Known Issue with CU
  • No known issue with this CU.
Reference See Also

Please check this Wiki for the SharePoint 2016 Build Numbers

  • SharePoint 2019: Build Numbers
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Another day of Office 365 Admin’s life, today one of the customer having the issue with Microsoft 365 learning pathways site.

Problem:

Global admin successfully provisioned the learning site and hand over to the customer. But when users browse the site, home page loading without any issue but when they click on any other link i.e., they get the error: “Something went wrong”

And here is the detailed error.

Error:

Something went wrong

If the problem persists, contact the site administrator and give them the information in Technical Details.

Technical Details

[SPLoaderError.loadComponentError]:
***Failed to load component “141d4ab7-b6ca-4bf4-ac59-25b7bf93642d” (CustomLearningWebPart). Original error: ***Failed to load URL ‘https://publiccdn.sharepointonline.com/krosfarm.sharepoint.com/sites/appcatalog/ClientSideAssets/26c9cd9f-db62-49b1-b102-7f0dad281ea0/v2-customlearningwebpartstrings_en-us_550d233e4c4642a78860ff6ed0424b18.js’ for resource ‘CustomLearningWebPartStrings’ in component ‘141d4ab7-b6ca-4bf4-ac59-25b7bf93642d’ (CustomLearningWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.

***INNERERROR:
***Failed to load URL ‘https://publiccdn.sharepointonline.com/krosfarm.sharepoint.com/sites/appcatalog/ClientSideAssets/26c9cd9f-db62-49b1-b102-7f0dad281ea0/v2-customlearningwebpartstrings_en-us_550d233e4c4642a78860ff6ed0424b18.js’ for resource ‘CustomLearningWebPartStrings’ in component ‘141d4ab7-b6ca-4bf4-ac59-25b7bf93642d’ (CustomLearningWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***CALLSTACK:
Error
at t._generateErrorStackForIE (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:870:16404)
at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:870:15940)
at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:1493:21274)
at e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:1493:16198)
at e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:1493:12223)
at Anonymous function (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:1493:61761)
at L (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:8:2116)
at T (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:8:2232)
at O (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:8:2026)
at g (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-06-14.010/sp-pages-assembly_en-us_6b7c467dac13b54cb9ff078c773aa7b5.js:8:1608)

Troubleshooting:

It is hard to decide from where to start, so I pick from the error detailes.

As per the error, learning site downloading the CDN assets from the url “Failed to load URL ‘https://publiccdn.sharepointonline.com/krosfarm.sharepoint.com/sites/appcatalog/ClientSideAssets/26c9cd9f-db62-49b1-b102-7f0dad281ea0/v2-customlearningwebpartstrings_en-us_550d233e4c4642a78860ff6ed0424b18.js” but encountering the certificate issue “There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.“. I checked couple of things to make sure there is no issue.

  1. Make sure there is no proxy blocking this download
  2. Also make sure no firewall blocking for the URL.
  3. As per Office 365 URLs and IP address ranges, I make sure the all the urls & ports are open. Check # 37 under SharePoint and OnDrive.

There is nothing, I find which can be causing this issue. So I move one step back. And checked for the Provisioning requirements.

Here are the pre-requisite for provisioning the learning site.

  1. User provisioning the learning site should be a Global Tenant Admin.
  2. An app catalog must be provisioned and configured
  3. User who provisioning the pathways site should be Site collection of the App catalog site.

After closely checking the pre-requisite, I found that my account is global admin but not the site collection admin of the App Catalog. This is cause of the error as during the provisioning process, due to lack of permission, it failed to register the app in the app catalog. Error is kind of misleading.

Resolution:

To resolve the issue, I have perform the below steps:

  • Delete the current Learning Pathways site collection from SharePoint Tenant administration site.
  • Remove it from the Admin recycle bin as well.
  • Wait for 10 to 20 mins before moving to next step.
  • Re-provision the Microsoft Leaning Pathways Site but make sure this
    • User must be Global Tenant Admin
    • App Catalog configured
    • User also be Site collection admin of the App catalog.

Boom, after provisioning again, Site is working as expected:

Thank you guys for reading it, till next enjoying and keep SharePoint’ing.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Another day in the SharePoint world as an Admin. Today I will talking about the common issue which we all face that for some features you have to go to Modern Admin center and for few we have to go back to classic admin center.

Finally this compliant heard by Microsoft, created a new page inside the New Admin Center called “Classic Features”. On that page all the remaining features (Term Store, User profiles, Search, Apps etc.) will be listed.

Following announcement covered this update. Featured ID: 32864

You will see it in your tenant (depending upon your tenant target release options) as Microsoft rolling out these recently. My tenant is on early target release so I get it early.

As I mentioned above that, MSFT create a new page in the Modern admin center and made other changes which accommodate the functionality. On this new page, you will see all the features in classic version not modern. Following features will be available under that.

  • Term Store
  • User Profile
  • Search
  • Apps
  • BCS
  • Secure Store
  • Records Management
  • InfoPath
  • Hybrid Picker
  • Classic Site collections page


Now, you noticed that they all looks classic and not converted into the Modern yet. I think they want bring everything to modern admin center and it is taking time to convert. But there is huge pressure on them that admin don’t want to go back & fort between classic and modern admin center, so they decide to bring everything in modern admin center. At least every one can access everything from one location.

Let’s browse to the classic features page.

Exploring the Classic features

Classic features page will allow the SharePoint Online Admin to access the classic features which are still in old admin center.

  • Login to SharePoint Admin center (https://admin.microsoft.com) and login with SharePoint Tenant Admin credentials.
  • In the left hand Pane (quick launch) Select the Admin center > SharePoint
  • Click on the Classic features Button.
  • On the Classic Features page, you will see all the features:
  • Now, click on the Open button bottom of the feature, every features has its own open button. i.e. Click Open for Term Store:
  • Now you will see, Term store will open in the new window, it has same option what we have seen in Old admin center.
  • If you click Open for User Profiles
  • User Profile page will open in new window as well.
  • You can do same for all other option if you want to access it.
More Features:
  • On the default page, you will notice only 1st four features available, do not worry that other are not there. Remaining are hiding under the More Classic features.
  • If you click on More Classic features you will see all others:

I am sure, it will bring some smile on your face as you will get everything on same location.

Keep tuning as Microsoft keep adding more features inside the Modern admin center.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Another day in the SharePoint world as an Admin. Today I will talking about the new set of bulk edit features in Modern SharePoint admin center.

In March 2019, Microsoft release 1st set of the Bulk action feature (Bulk share) and in May they released 2nd set.

You will see it in your tenant (depending upon your tenant target release options) as Microsoft rolling out these recently. My tenant is on early target release so I get it early.

There are two more optioned added into the Bulk Edit features on the Active Sites page.

  1. Bulk delete of sites
  2. Bulk hub site association

In this article we will talk about the Bulk Delete of sites collections.

Bulk delete of Sites

Bulk delete feature will allow the SharePoint Online Admin to delete multiple sites in one go. This is really good feature which were request tons of time from Microsoft.

  • Login to SharePoint Admin center (https://admin.microsoft.com) and login with SharePoint Tenant Admin credentials.
  • In the left hand Pane (quick launch) Select the Admin center > SharePoint
  • Click on the Active Sites Button.
  • On the Active Sites page, you will not see the Bulk Edit option. Reason, we haven’t select the any site collection.
  • Now Select Multiple site collections (if you select only One site then Bulk edit will not appear, minimum 2 site collection should be selected.) & you will see the Bulk Edit Action option.
  • Click Edit drop down:
  • A new Delete Sites message box will pop up. Check the “Delete group-connected team sites and all their resources” box and hit Delete button.
  • You will see the status result on
  • Finally you will see the deleted message
  • Now, we successfully delete the site collections using the bulk operations.

Now you have to test what is the max number of site collections you can delete in this bulk delete, I think we can delete all sites collections.

Troubleshooting

There are 2 type of site collections which we cannot delete as per the SharePoint Online policy

  • Hub site collection
  • Root site collection.
Delete the Hub Site collection

If we try to delete a hub site collection then it will throw the error and asked to unregister that site from as a hub then delete it.

  • You select multiple site collection, which include one of the Hub Site collection and hit the delete the button from Bulk Edit. Now, we get the following error.
  • Now click on the View Details and get the information. You will see the message “to delete this site, unregister it as a hub site first.”

  • If we click the delete button after check the box, it will delete all the site collection except the Hub site.

Clearly, if you select a Hub site collection during the bulk delete operation it will not work, as we can’t delete a hub site unless we unregister it.

Delete the Root Site collection

If you trying to delete a root site collection, the operation also throw the error as we cannot delete the Root site collection in any given situation.

  • You select multiple site collection, which include one of the root Site collection and hit the delete the button from Bulk Edit. Now, we get the following error.
  • Now click on the View Details and get the information. You will see the message “This site can’t be deleted because it’s the root site for your organization.”

  • If we click the delete button, it will delete all the site collection except the Root site collection.

Clearly, if you select a Root site collection during the bulk delete operation it will not work, as we can’t delete a Root site.

Keep tunning as Microsoft keep adding more features inside the Modern admin center.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Today’s article is exploring another option in the Modern SharePoint Admin Center experience for SharePoint admin in office 365. In this article, we will go through the options / choices available in Deleted Sites Option. So as we know Modern Admin center is still in Preview mode ( as it is not build 100%), so if you already configure to use the Modern admin center then you get it or you can click on the banner and try New SharePoint Admin center.

Note: As SharePoint admin center is gradually releasing to around the globe, features / options you are seeing in the admin center depend upon the Office 365 Tenant Release options settings. This means that you may not yet see some features or they may be look different.
Note: This article is published on 04/26/2019, Product team is still pushing the more stuff into the New Admin center and may be when you are reading this article, more options already available.

So today is topic is Deleted Sites, In new SharePoint Admin center we are seeing a new options under the Sites link in left quick launch.

Deleted sites option is also called SharePoint Admin Recycle-Bin, there are couple of facts about it:

  • All deleted site collections will stay here for 93 days OOTB unless someone manually delete it.
  • Once Site collection is deleted then everything will be gone permanently including all content, list, libraries, sub-sites etc
  • This recycle-bin only keep the site collection not sub-sites
  • Delete a site collection from recycle-bin only available in New Admin center
  • Restored Site collection will be restored on the previous location (same url).
  • If site collection is in Admin Recycle-Bin then you can create new site collection on same url.

A site collection can be deleted by various method

  • Site collection admin delete it via Site option
  • A tenant admin delete site collection from SharePoint admin center
  • Or a tenant admin delete it via SPO powershell.

Let’s walk through inside the Deleted Site option:

Reach to Deleted Sites Page:
  • Login to SharePoint Admin center (https://admin.microsoft.com) and login with SharePoint Tenant Admin credentials.
  • In the left hand Pane (quick launch) Select the Admin center > SharePoint
  • If you already configured New Admin center as default then it will open New Admin center.Or if not then you will get this page. Click on Try it now in banner.
  • Click on Deleted Sites on Left Pane.
  • On this page you will see all the Deleted Site collections.
Views of Deleted Sites Page:

We have the same sorting and filtering options over here as we have seen on the Active Sites page. There are 13 columns available for Sorting & Filtering.

Sorting:

We can sort the any column ascending or Descending or lowest to larger depending upon the Column type. To sort a column please follow the below steps:

  • Click on the Drop-Down arrow and Select the required sorting options. (If there are other filtering options available then you will get that choice there.)
  • I.e. when Click on Site Name Column’s Dorp-Down,
    • It give below sorting options and you can pick one as per your requirement.
      • A to Z
      • Z to A
    • It also give the Customize columns options as well. If you want customize the column in the view then click on it.
  • Click On A to Z
  • Now you can see, all the list is sorted by Site Name Column (A to Z Pattern)
  • If you Click on Z to A
  • Then it will sort the list again with Site Name Column (Z to A pattern)
  • If you want to clear the Sorting, Simply refresh the page and it will clear all sorting.

You can do the same steps on any column but sorting option may be different depending upon each column type. See the Table below for the complete list of Columns.

Filtering:

We can also filter the columns as per the given options. Not all columns have filtering option (see below chart for the filtering Options).

  • Create a filter
    • Click on Drop-Down next to Template column
    • Click on Filter by Template > now you will see all the available templates (these are from the sites who are deleted sites list).
    • Click on Communication Site and you will see all the Sites with communication template will be displayed.
    • Now you will see all the Sites which are using the Communication Site Template:
  • To clear the filter options
    • Click on the Drop-Down next to Template Column
    • Click on the Clear filter.
    • Now you will see all Deleted sites is back to all item view:

Table: List of all currently available columns in the Deleted Sites view with Sorting & Filter Options (if any).

Column Name

Sort Option

Filter options

Site Name

  • A to Z
  • Z to A

No Option

URL

  • A to Z
  • Z to A

No Option

Storage Used (GB)

  • Smaller to larger
  • Larger to smaller

No Option

Primary Admin

  • A to Z
  • Z to A

Filter by Primary Admin

i.e. name of admins

Template

  • A to Z
  • Z to A

Filter by Template

i.e. Team Site or Team Site ( Classic Experience) or Communication Site etc.

Created On

  • Older to newer
  • Newer to older

No Option

Time Deleted

  • Older to newer
  • Newer to older

No Option

External Sharing

  • A to Z
  • Z to A

Filter by External Sharing

i.e. Off or On

Office 365 Group

  • A to Z
  • Z to A

Filter by Office 365 Groups

I.e. No or Yes

Files viewed or edited

  • Smaller to larger
  • Larger to smaller

No Option

Page views

  • Smaller to larger
  • Larger to smaller

No Option

Files

  • Smaller to larger
  • Larger to smaller

No Option

Hub Site Association

 

Filter by Hub Site Association

I.e. Empty or name of hub site (s)

Customize Column:

There are total 13 columns available for the Deleted Sites list, in default view it shows only 7 columns. But we have option to add / remove the columns in views, we can also change the order of the column. Let start with to customize the views.

  • We can get the customize columns by couple of way:
    • Click on Drop-Down of any Column name and click Customize Column option
    • Click on “…” at the end of the columns and click on Customize Columns.
    • On Customize Columns option dialogue,
    • We can select or un-select the required column.
    • We also change the order of the column as well
      • Highlight the column and click on UP or down arrow as per the requirement.
      • You can repeat it until you reached to your desired order.
    • Click Apply
  • Now you will see that view with required changes.
Restore Deleted Sites:

If we want to restore a deleted sites collection, we have to follow the below steps.

  • Click on the Required Deleted Sites collection (i.e. /Sites/PM1), Make sure it is highlighted otherwise restore button will be grayed-out in ribbon.
  • In the ribbon click on the Restore button.
  • If it is Group-Enabled Site then it will warn about the other group’s related resources’ restore. Click on restore.
  • You will see working wheel before Search while its restoring site (its depend how big the site is and if it is group-enabled or not).
  • If you click on the Progress wheel you will get same information (site Restoring).
  • Once it completely resorted then it will display this message and complete the task.

You can Run Restore only one site collection, if you select multiple Site collection then Restore Button will be grayed. If you want to delete multiple site collections, you have to do it one by one (don’t need to wait for deletion of 1st site) or use the PowerShell.

Delete the Deleted Sites

There are situation where we want to delete a deleted site collection from recycle-bin as well. To delete a deleted site collection, please follow the below steps.

  • Click on the Required Deleted Sites collection (i.e. /Sites/PM1), Make sure it is highlighted.
  • Click on the Deleted from Ribbon.
  • Click on Delete on the warning pop-up.
  • Now Progress wheel will indicate the progress.
  • Once deleted it will notify that site deleted successfully.
  • Now this Site is permanently deleted from the Tenant and cant be recover.

Again: We cant not perform bulk delete operations from New Admin Center, We have to select one by one. For bulk use the SharePoint Online PowerShell.

Search the Deleted Sites

We can search the within the deleted sites list, as your usage of tenant grow, you can see tons of site in deleted sites list. There are 4 columns which has indexing on it (Site name, Url, Primary Admin, Template).

To perform a search operation, please follow the below steps:

  • Type you search term in the search box (on top right) and hit Enter. I.e. Waqas
  • You will see it bring all the sites which containing the Waqas in Site Name or URL or Primary Admin or Template columns.
  • Let’s perform another search, Type Communication and Hit Enter
  • Now you will it bring all the sites which are using communication site template or that keyword is part of their URL or site name.
  • If you want clear the filter then click the X in front of Search box.
  • Now it clear the filter and now see all the deleted sites.

OMG, that’s conclude the today’s article, I tried to cover Deleted Sites in detail...

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In this article, we will list complete detail about the March 2019 CU for SharePoint Server 2019. Same CU method adopted for SharePoint 2019 as to SharePoint 2016, I mean we will see 2 files each month ( some time one), One for SharePoint fixes and 2nd for Language dependent. These updates also include the security updates as it does in SharePoint Server 2016.

This Month MSFT released one patch for SharePoint server 2019; Security updates also part of the packages.

This month no patch for language depend so if you did not install the most recent language dependent package then use the February 2019 CU language dependent (KB4462170)

Improvements, fixes and Security Updates

Here is the list of fixes published by MSFT.

SharePoint Server 2019:
  • Adds support for the new Japan era in SharePoint Server 2019.
  • Editing a project-level custom field while on a project detail page (PDP) cuases lost task-level calculated custom field values if the field formula includes the task’s Unique ID.
  • When you upload content to a document library, selecting a destination folder doesn’t work. This issue occurs when you open the SharePoint site by using the Microsoft Edge browser.
Project Server 2019:
  • No fix released this month
Security Fix:
  • This security update resolves a remote code execution vulnerability that exists in Microsoft SharePoint if the software does not check the source markup of an application package.

    A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the SharePoint application pool and the SharePoint server farm account.
    Exploitation of this vulnerability requires that a user uploads a specially crafted SharePoint application package to an affected versions of SharePoint.
    The security update addresses the vulnerability by correcting how SharePoint checks the source markup of application packages.

Language-Dependent Fix:
  • No fix released this month.
Installation

As we know, this Month MSFT Release Only 1 update.

  • Please download the sts2019-kb4462199-fullfile-x64-glb.exe
    the files and install it on all SharePoint servers.

  • Please run the PSconfig wizard on all server in the farm one by one.
Article Number (KB)

  • KB 4462199  
Download

Please download the November CU from the below link:

Prerequisite
  • To apply this update, you must have Microsoft SharePoint Server 2019 installed.
Restart information
  • If during the Installation of the Updates Certain Component of the SharePoint is running then it will ask you for the Restart the server. So its depend upon your server.
Schema Change
  • This update updates the database schema so that the mean schema and Patch Version will change. You will see the same Patch number and Build Number.
Patch Number
  • 16.0.10342.12113 for Language Independent file
Known Issue with CU
  • No known issue with this CU.
Reference See Also

Please check this Wiki for the SharePoint 2016 Build Numbers

  • SharePoint 2019: Build Numbers
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Couple of day’s back I noticed one interesting thing, I open the SharePoint admin center and found an emoji inside the Site name. It is kind of surprise for me as I never seen this before. I thought it is my browser who is causing this issue, so I close the browser & reopen it but result is same. I browse the site collections and I saw the same emoji’s on their home page as part of Site Name. I decide to deep dive in this issue and quickly I come to know, we can use the emoji’s as part of site collection name either on prem or SharePoint Online. All type of site collection supported this i.e. Teams site, Communication Site, Modern Team site, classic sites etc. You can update the existing site collection name and include the emoji inside it.

This is what I have seen in the New Admin center:

Let’s do together and use the emoji’s inside the site collection name while creating new as well as updating the existing. I used the emoji’s in following way

  • Create new Microsoft Teams from admin center
  • Create a classic team site from Admin center
  • Update existing Modern Communication Site Collection’s site name using the Site Information option
  • Update existing Classic Team Site Collection’s site name using the Site settings > Title option
Create new Microsoft Teams from admin center

Let’s start it with Microsoft team’s site.

  • Login on the SharePoint admin center with SharePoint admin credentials
  • Open the New SharePoint Admin center, it’s easy to create Modern Teams or Communication site collections.
  • Click Active Sites on Quick launch
  • Click Create button on the Active Sites page
  • Click on Team Site (group connected)
  • On this page, enter the
    • Site Name: Over here please enter the Site name and include the emoji in it. To enter the emoji, please use the emoji panel in Windows 10 or on screen keyboard of windows.
    • Group Owner
    • Select Language.
    • Click next
  • Click finish
  • Now if you go back to the New Admin center Actives Sites page, you will see your site name with emoji. Wow.

  • Let’s browse the site and you will see it on the homepage on Site Name location
    .
Create a classic team site from Admin center
  • Login on the SharePoint admin center with SharePoint admin credentials
  • Open the New SharePoint Admin center, it’s easy to create Modern Teams or Communication site collections.
  • Click Active Sites on Quick launch
  • Click Create button on the Active Sites page
  • Now enter the emoji in the Site Name text field.

  • Click Finish.
  • Now back to Active Sites and you noticed that

  • Now let’s browse the Site collection and you will noticed that in the Site collection name.
Update existing Modern Communication Site Collection’s site name using the Site Information option

Let’s edit a Modern Communication Site collection name from the Site Information page.

  • Browse the site collection in browser
  • Click Settings
    > Click Site information

  • On this page, Please enter the emoji inside the Site name (you can enter inside the Site description).

  • Click Save.
  • Now go back to New Admin Center > go to Active sites page. You will see the Site name with Emoji ( in rare case it may take little bit time to sync.)

  • If you browse the site, you will notice it on the home page as well.

Update existing Classic Team Site Collection’s site name using the Site settings > Title option

Let’s edit a Modern Communication Site collection name from the Site Information page.

  • Browse the site collection in browser
  • Click Settings
    > Site settings
  • Now
    Click “Title, description and logo” under look and feel.
  • On this page, Please enter the emoji inside the Site name (you can enter inside the Site description).
  • Click Ok.
  • Now you can see this in Site name on home page
  • Now let’s go back to New Admin Center:
  • Now open the Site collection in browser and you will see it on homepage.

I am sure you like it and enjoy this. There are couple of things to note before I conclude this article.

  • You can use emoji in Site Name / Site description in SharePoint Online as well as SharePoint On prem
  • Use the Windows Emoji panel / on Screen Keyboard to input the emoji inside the site name
  • You can use PowerShell to insert the emoji ( PowerShell use Unicode)
  • Emoji will not be part of url, you have to pick the url.

I think emoji are good, if you want to group the site collections based of their team then assign an emoji to it. It is more fun. Till next enjoy and have a great SharePointing.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Another day in the SharePoint world as an Admin. Today I will talking about the new set of bulk edit features in Modern SharePoint admin center.

In March 2019, Microsoft release 1st set of the Bulk action feature (Bulk share) and in May they released 2nd set.

You will see it in your tenant (depending upon your tenant target release options) as Microsoft rolling out these recently. My tenant is on early target release so I get it early.

There are two more optioned added into the Bulk Edit features on the Active Sites page.

  1. Bulk delete of sites
  2. Bulk hub site association

In this article we will talk about the Bulk Hub Site Association of sites collections. Please check the article for explanation of the Bulk Delete of Sites.

There are couple of operations can be performed.

  1. Associates multiple site collections to a hub sites
  2. Change the Hub site association
  3. Un-associates sites from a hub site.

Note: you cannot associate a hub site to another hub site

Bulk Hub Site Association

Bulk hub site association feature will allow the SharePoint Online Admin to associate multiple sites in one go. This is really good feature which were request tons of time from Microsoft.

  • Login to SharePoint Admin center (https://admin.microsoft.com) and login with SharePoint Tenant Admin credentials.
  • In the left hand Pane (quick launch) Select the Admin center > SharePoint
  • Click on the Active Sites Button.
  • On the Active Sites page, you will not see the Bulk Edit option. Reason, we haven’t select the any site collection.
  • Now Select Multiple site collections (if you select only One site then Bulk edit will not appear, minimum 2 site collection should be selected.) & you will see the Bulk Edit Action option.
  • Click Edit drop down:
  • A new Hub Site Association box will pop up.
  • Click on the Select a hub Site drop down and select the required Hub Site.
  • You will see the status message on active site page.
  • Finally you will see the sucessfully Updated message.
  • You will see all 3 sites collections associates with Test2 hub site.
  • Now, we successfully associates the multiple site collections to a hub site in a go.
Unregistered Site collections from Hub Site collection

We can also change the association of sites collections from a Hub site or totally remove its associations from the Hub site

  • You select multiple site collection and hit the Hub site association button from Bulk Edit. Now, Select the None
  • Now click Save
  • Now, you will see the status message on active site page.
  • Finally you will see the sucessfully Updated message.
  • Now we can see the no hub site associates with these site collections.

We can change the association of the site collection from one hub to other hub site using the same method.

Try to associate Hub site another Hub site.

If you select Hub site and try to change its association, it is not possible. In this case, you will get the error.

  • Select the multiple site collection (including the one Hub Site as well)
  • When click the Hub Site Association, you will see this error message. “1 site you selected can’t be associated with a hub.”
  • If you click the view details.

  • This message is self-explanatory, we cannot associate a Hub site to another Hub site. If we want to change the hub association of hub site then we have to unregister that site as hub site 1st then change the associations.

In this article, we learn about the new option available under the Bulk edit, Hub site association. It is easy to use and really handy tool.

Keep tuning as Microsoft keep adding more features inside the Modern admin center.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Another day in SharePoint world and another problem in it. As we familiar that Office 365 include two options for the enterprise social feature in SharePoint. 1- Newsfeed and 2-Yammer.com.

Problem:

I was configuring tenant for one of my customer, he has separation of duties for many work streams (Less Global Admin, Dedicate SharePoint admin / Exchange admin / Microsoft Teams Admin / Azure AD / Yammer admin etc). I was working with a SharePoint Admin (who has SharePoint admin, Service Admin and report readers’ role). Customer want to use Yammer.com service for the enterprise social collaboration. When tried to enable that setting from Settings page ( using the classic Admin center, as this option yet not moved into modern admin center), it throws the following error:

“We’re having trouble updating this setting. Please try again in a few minutes.”

Investigation:

We tried different stuff to resolve it,

  1. Go back to the Microsoft documentation and make sure nothing special mentioned here.
  2. We waited for 1 hour but no luck.
  3. Sign-out and close the browser, try again
  4. Clear the browser cache and again tried
  5. Tried with different browser.
  6. Make sure yammer.com service is enabled and user able to login on the yammer.com.

After trying all above method, we collect the correlation id and contact with Support team.

Resolution:

Microsoft team told us that correlation ID basically throwing Not Authorized error for the user. This is weird for us but this thing told us that we should try with higher level permission, we asked Global admin to configure this settings for us.

WOW, when global admin login and configure the Yammer.com services for enterprise social collaboration, and it’s worked this.

Conclusion:

If you want to configure yammer.com for the enterprise social then you need global admin rights in the tenant.

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Today’s article on the Modern SharePoint Admin Center experience for SharePoint admin in office 365. In this article, we will go through the options / choices available in Active Sites under Sites Option. So as we know Modern Admin center is still in Preview mode ( as it is not build 100%), so if you already configure to use the Modern admin center then you get it or you can click on the banner and try New SharePoint Admin center.

Note: As SharePoint admin center is gradually releasing to around the globe, features / options you are seeing in the admin center depend upon the Office 365 Tenant Release options settings. This means that you may not yet see some features or they may be look different.

Note: This article is published on 04/24/2019, Product team is still pushing the more stuff into the New Admin center and may be when you are reading this article, more options already available.

SharePoint product team is working on the Modern admin center and they will add more options in it on later days.

So today is topic is Active Sites, Active Sites page is central place to get the information about the Site collections (including Modern Teams, Communication and Office 365 group connected sites). On this page following activity can be done easily.

Note: this page will only list information about the Site collection level and Sub-sites are not included here.

Create Team Site (Modern)
  • On Create a Site page, Select the desired options
    • Team Site (modern team site connected to Office 365 groups)
    • Communication Site ( modern communication site)
    • Other options ( for all other available templates)
      • Team Site
      • Document Center
      • Enterprise Wiki
      • Publishing Portal

Note: Options for Modern Team Sites and Communications will be same.

  • Click on Team Site
  • On Create Team site page, enter the following details

Site name
Group email address
(Only available, if the Office 365 Groups are enabled in SharePoint Online. This option will be available as soon as you type something in Site Name field.)

Group Owner

Select Language
Advance Settings

(If you the click on the Advance settings then below additional configurable option will available.)

How Sensitive is your data

(Only available if it is enabled by tenant admin at the Azure AD level.)

Privacy Settings
  • Pubic : Anyone in the organization can access this site
  • Private – Only Members can access this site

Time Zone
Site description
Storage limit
(Only available if Tenant configuration is Manual Site Quota Management but If Automatic Site Quota management is enabled then this option will not available.)
Click “Next”
  • On Next Page, If you have additional owners or members which you want o add the user in it then use this page:

Note: SharePoint at this time start creating the sites while you deciding about your extra members.

Add additional owners
Add members
  • Once the site collection created, Click Finish
  • On the Active Site page, you will get this message.
  • Now you can see the site in the list

Now this site will appear all the related locations i.e. sites following. It is time to use this site.

Create Communication Site

Creation of the Communication site’s process is same as for Team site except Choice of Design option.

In Choose Design Page following Options available:

  • Topic – Use this design if you have a lot of information to share such as news, events, and other content.
  • Showcase – Use this design to showcase a product, team, or event using photos or images.
  • Blank – Start with a blank site and make your design come to life quickly and easily.

We can create the site using the classic templates from the same create site options, following templates are available for classic experience:

  • Team Site:
    A site for a team of people to share content when they work together. This option does not create an Office 365 group, shared Outlook inbox, shared calendar, OneNote notebook, or Planner plan.
  • Document Center: A classic site designed for centralized document management.
  • Enterprise Wiki: A classic site for sharing knowledge across the organization. Page authoring is simple, and users can comment on and rate pages.
  • Publishing Portal: A classic site for building an intranet portal. It includes a Search Center.
Create Team Site (Classic)
  • On Create a Site page, Select the desired options ( Other Options)

  • On the Other Options Page, Select the correct template ( Team, Document Center, Enterprise Wiki or Publishing Portal)
  • Now enter the detailed
Site Name
Site Address
Primary Administrator
Select a Language
Advance Settings
Time Zone
Storage Limit
(Only available if Tenant configuration is Manual Site Quota Management but If Automatic Site Quota management is enabled then this option will not available.)
Finish
  • Click Finish and it create the New Site Collection.
  • After creating, it will go back to Active Sites Page.
  • That’s it, we successfully created the classic team site.

If you want to create another classic site collection with different type of template then follow the above steps.

Hope you enjoy this article, Till next please keep SharePoint’ing and Enjoy!

Read for later

Articles marked as Favorite are saved for later viewing.
close
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Separate tags by commas
To access this feature, please upgrade your account.
Start your free month
Free Preview