Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine] - SCCM 2012 client push fail to start

Recently i faced an issue with SCCM 2012 R2 server and client push installation. (From my research it can be relevant to SCCM 2012 SP1 too).
Environment:

• SCCM 2012 R2
• SQL installed separately on cluster environment

Issue:
When configuring client push installation to servers and workstations as in the picture below, an error in CCM.Log stared and client fail to start installation on server type objects.

CCM.Log errors:
SQL Server Native Client 11.0][SQL Server]Invalid length parameter passed to the LEFT or SUBSTRING function. : sp_CP_CheckNewAssignedMachine

AND

Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine]

In SMS_CLIENT_CONFIG_MANAGER under Monitoring -> System Status -> Component Status i got the error:

Microsoft SQL Server reported SQL message 537, severity 16: [42000][537][Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid length parameter passed to the LEFT or SUBSTRING function. : sp_CP_CheckNewAssignedMachine

I tried to manually push the client from SCCM console to test server, opened up CCM.log on the SCCM server and watch for push installation process.
The installation started immediately and the client was installed successfully. that eliminated permission issue with Client Push Installation Account.

I decided to start from scratch and watch client push process from the beginning, so i deleted the test server from SCCM console, add another new Windows 2012 server to the domain and initiated System Discovery to discover the 2 server.
When System Discovery finished, i saw the 2 new servers in the console with the correct site code, suggested that boundary and boundary group was configured correctly (i check that anyway just in case).
As the SCCM client push installation was configured to automatically push client to servers and workstations, i expected that installation will start immediately, but once again, installation didn't start and CCM.log showed no attempt to push client to the new servers.

After long research, i discover that there is an SQL store procedure issue with this kind of configuration (SQL installed on cluster environment) and the only way to overcome this situation is to select all system types on Client Push Installation Properties:

I faced that issue on 2 separate environments, each with SQL cluster hosting SCCM database, never saw that with stand alone SQL. I hope a fix will be release soon.

Because this situation led to add the option to push client to all system types include Configuration Manager site system servers, i was needed to do some exclusions so client will not be installed on cluster nodes and other servers.
More on that in other post - Exclude computers from automatically client install.