Content Download Issue : 'CTM Job Suspended' -- 'Calling back with empty distribution point list'

Issue:

Today I stuck for a while during the Application Deployment to an user collection. Used all the default settings for the deployment. It almost worked until I saw an error in the contenttransfermanager.log:

Checked the locationservices.log and found the following entry in the log:
    calling back with empty distribution points list

Probing:

It was kind of surprise as many other deployment in past have worked without any issue.
While probing came across this small setting that could have been missed while creating the Deployment Type:

Deployment Option was left with the highlighted settings and that led to the above errors in contenttransfermanager.log and locationservices.log.

Solution:

Click on the drop drown option and select 'Download content from distribution point and run locally' :

Went back on the client and re-initiated the deployment and everything went well and the required application got installed without any further problems.

SQL Server Error while installing SCCM 2012/Current Branch Site

Issue: 

When we run the setup for the installation of SCCM 2012/Current Branch, Primary/Central Site we get the following error message in the Configmgrsetup.log

Cause:

This happens because the name of the Windows Server with the SQL Server instance installed was renamed before starting the installation of SCCM Site Installation.

Solution:

Open the SQL Management Studio on the SQL Server and login with the required credentials.

Run the following stored procedures to check the current name of the server in sys.servers of the SQL Servers.

Exec SP_Helpservers;

Go

If you find the old server name as a result of the above query then run the following procedures to first delete it from sys.servers and then update it with the current name.

Exec sp_dropserver <Old name>; (For default instance)

Go

Exec sp_addserver <New Name> ; (For default instance)

Go

                                           OR

Exec sp_dropserver <old name\instance name>; (for Named Instance)

Go

Exec sp_addserver <New Name\Instance name>;  (for Named Instance)

Go

After renaming the server name in sys.servers of the SQL servers run the following query to check if the name is changed or not

Select @@ServerName;

It will return the current name of the Server.

 Now restart the Instance of the SQL from the SQL Configuration Manager and reboot the server.

Once the server is up and running after the reboot run the  configmgr setup. The setup will first run to uninstall the Site components that  got installed in the last failed attempt.

After the Uninstall setup is finished run the configmgr setup once again to start the Site installation. This time the same error should not come up during the setup SQL Database step of the Site installation process.