SCCM Bug: Push Client - ERROR: Unable to access target machine for request - Error 1003 - ccm.log

If you have error "Unable to access target machine for request" with error code "1003" in your "Microsoft Configuration Manager\Logs\ccm.log" on your secondary or your primary

...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE"  $$ <03-01-2018 18:27:05.821-480="">
Execute query exec [sp_IsMPAvailable] N'SEC'~  $$ <03-01-2018 18:27:05.822-480="">
---> ERROR: Unable to access target machine for request: "2097199533", machine name: "MYMACHINE",  access denied or invalid network path.  $$ <03-01-2018 18:27:05.823-480="">
Execute query exec [sp_CP_SetLastErrorCode] 2097199533, 1003~  $$ <03-01-2018 18:27:05.824-480="">
Stored request "2097199533", machine name ""MYMACHINE", in queue "Retry".  $$ <03-01-2018 18:27:05.827-480="">
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097199533, 2~  $$ <03-01-2018 18:27:05.831-480="">
Execute query exec [sp_CP_SetLatest] 2097199533, N'03/01/2018 10:27:05', 194~  $$ <03-01-2018 18:27:05.842-480="">
<======End request: "2097199533", machine name: ""MYMACHINE".  $$ <03-01-2018 18:27:05.851-480="">
....
<03-01-2018 18:27:05.824-480=""> <03-01-2018 18:27:05.827-480=""> <03-01-2018 18:27:05.831-480=""> <03-01-2018 18:27:05.842-480=""> <03-01-2018 18:27:05.851-480="">  
Instead of:

...
======>Begin Processing request: "2097199533", machine name: "MYMACHINE"  $$ <03-01-2018 18:51:25.981-480="">
Execute query exec [sp_IsMPAvailable] N'SEC'~  $$ <03-01-2018 18:51:25.987-480="">
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~  $$ <03-01-2018 18:51:25.988-480="">
---> Attempting to connect to administrative share '\\MYMACHINE.mydomain.net\admin$' using account 'MYDOMAIN\AdminAll'~  $$ <03-01-2018 18:51:25.988-480="">
...
Error 1003 normally is: "Cannot complete this function." but here it is a SCCM Bug (CB 1706 and 1710. Perhaps before and after)



Resolution: (Do it on your Primary SQL server, Secondary will do synchronization)

1st: get all client with 1003 error:
SELECT * FROM ClientPushMachine_G
WHERE 1=1
AND LastErrorCode = '1003'

(and save these informations to create a collection to re-push client)

2nd:delete all line with 1003 error : (WARNING: modify database directly is NOT permit by Microsoft - backup your database before any modifications)
DELETE FROM ClientPushMachine_G
WHERE 1=1
AND LastErrorCode = '1003'


3rd:re-push you clients
All should be OK now