SharePoint 2019 Standard vs. Enterprise, Updates / Release / Patch / Versions and the SharePoint Framework Releases

We have an SP2019 test farm running SharePoint Server 2019 Standard, version 16.0.10351.20000 (October 2019). I have a few questions regarding compatibility between SPFX development and SP2019 on-premise:

  1. Is it important to keep the SP2019 environment updated with the latest monthly release in order to ensure compatibility with the latest version of the SharePoint Framework?

  2. Is there any guidance regarding development targeting SP2019 standard edition vs. enterprise (article, blog post)?

  3. Some on-line posts state that SPFX should be kept at version 1.4.1 for SP2019. Is this still true?

  4. Does anyone have any experience regarding possible deployment issues when development is performed on SharePoint Online? Development environment is O365.

Thanks in advance!

SharePoint 2010 Foundation vs Enterprise Security Vulnerability Patch

We have a little confusion here as to which security patches we should be applying to our SharePoint 2010 Enterprise farm. The following states there is a patch for Foundation Server, but nothing for Enterprise 2010 Server. Why is this? Is the security patch covered elsewhere? Where?


How do I install a specific patch number version of Python?

This question here tells me how to install a specific version i.e. x.y.

I would like to install a specific version of Python x.y.z – eg 3.6.3 – while the default in Ubuntu 18.04 is Python 3.6.8.

Is there a way to install the specific patch number of the version of Python?

I tried the selected answer in the related question and I cannot install properly.

sudo apt install python3.6.3 Reading package lists... Done Building dependency tree        Reading state information... Done E: Unable to locate package python3.6.3 E: Couldn't find any package by glob 'python3.6.3' E: Couldn't find any package by regex 'python3.6.3' 

I am able to install a particular version, just not a patch number

sudo apt install python3.5 Reading package lists... Done Building dependency tree        Reading state information... Done The following additional packages will be installed:   libpython3.5-minimal libpython3.5-stdlib python3.5-minimal Suggested packages:   python3.5-venv python3.5-doc binfmt-support The following NEW packages will be installed:   libpython3.5-minimal libpython3.5-stdlib python3.5 python3.5-minimal 0 upgraded, 4 newly installed, 0 to remove and 501 not upgraded. Need to get 4,113 kB of archives. After this operation, 22.5 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. 
sudo apt install python3.5.2 Reading package lists... Done Building dependency tree        Reading state information... Done E: Unable to locate package python3.5.2 E: Couldn't find any package by glob 'python3.5.2' E: Couldn't find any package by regex 'python3.5.2' 

Patch Advisory Board – feasibility of implementation

I’m working for a public sector organisation (around 6000 staff) with a mixed IT skill set. We’re looking at setting up a patch advisory board to assist in server patching.

The plan is to have a team from different areas of the business (Apps, DBs, infrastructure, etc) to review each patch and then approve whether they’re installed on any of our 1100 servers. Typically the patches reviewed will be from below.

My questions are:

  1. How feasible is this approach given the work, effort and time involved to regularly understand dozens of patches and then decide whether to apply them?

  2. Given that we don’t fully understand our own servers and the patches, reviewing each patch doesn’t guarantee success.

  3. How many of you use a patch advisory board in your current work place?

As opposed to just applying critical and security patches on dev and test before moving to production


SharePoint Migration – Product / patch installation or server upgrade required

I migrated SharePoint from 2013 to 2016 and then 2019. I used the database prefix SP_Intranet.

After migration to 2016, I removed SP_Intranet_Config and SP_Intranet_CentralAdmin + non-migrable databases.

This was followed by the installation of SharePoint 2019 with the latest patches. The farm consisted of four servers, the migration was successful. SharePoint server 2016 was still running but without databases. After two days in “Review problems and solutions” I got an error message: Product / patch installation or server upgrade required. .. Can you please tell me how to fix this error message?

In my opinion, since SharePoint server 2016 contained a database with the same name and continued to run, it joined the databases that were already created for SharePoint 2019.

I tried:

  1. Run the Get-SpProduct -Local after that run the Config wizard. I would use this psconfig -cmd upgrade -inplace b2b -force

  2. Clear the Config Cache on All server in Farm then run the psconfig wizard.

enter image description here

SharePoint June Patch for enterprise edition

Quick question to clarify patching SharePoint 2013 enterprise.

Do I only need to patch my enterprise farm servers with the enterprise version of the patch?

Or do I need to install the foundation version, then standard version, then enterprise version before running psconfig?

Side question, Would this also cover project server since it fixes cross site scripting for the farm?

Error after applying patch to module

I have applied patch from MD5 to SHA-512 to Magento 2 direct post module, when i tried to test purchasing with a credit card i got this error on exception.log file

main.CRITICAL: Warning: pack(): Type H: illegal hex digit : in /public_html/vendor/magento/module-authorizenet/Model/Directpost/Response.php on line 111  

this is the code line 111

return strtoupper(hash_hmac('sha512', $  message, pack('H*', $  signatureKey))); 

How can i fix this error?

Security Patch SUPEE-11155 – Possible issues?

Magento has released a new security patch for M1, and updates for M1 and M2.

What common issues do you have to watch out for when applying this patch/upgrade?

Magento 1

Magento 2

This should be the last release in the 2.1 series which reaches its EOL at the end of this month.