SCCM: Setting wizard error: There are no task sequences available for this computer.

I was trying OS deployment on a server multiple times, it refused find assigned task sequences. I double checked target server’s SMBIOS id and MAC address in assigned server. It keep failing with this error:

There are no task sequences available for this computer.

If you look in the SMSTS.log you may also see the following error:

No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.

It turned out to be there is a duplicate SMBIOS id exists in SCCM database. Of course I am trying to rebuilding a existing server…..God Dammit!!! Don’t they tell in plain English there is a duplicate BIOS id exists in the error messages. Another Microsoft error wasted my time.

I have deleted the previous server name from SCCM computer collection and retried with great success.

Reference information: OSD Task Sequence fails with "There are no task sequences available for this computer" if multiple machines have the same SMBIOS GUID

SCCM Reporting: "An error occurred on the server when processing the URL. Please contact the system administrator."

I installed Windows Update Services feature on my SCCM R2 server. WSUS site certainly screwed the reporting site settings. If you get the following messages, you are in right place.

"An error occurred on the server when processing the URL. Please contact the system administrator."

“You do not have permission to view this directory or page.”

It meant (on my case) is the site is not using NTLM authentication which is required for SCCM reporting.

Follow the steps below to fix this authentication issue. I am assuming you are running SCCM on Windows 2008 R2 server.

  1. Log on to SCCM server as administrator.
  2. Open “Internet Information Services (IIS) Manager” console in Administrative Tools.
  3. Expand the Websites to SMSReporting-<sitecode>
  4. Double click on Authentication icon on the middle pane. image
  5. Click on Windows Authentication and Choose Providers… under Actions pane.
  6. Add NTLM if it not listed already and move it to the top.
  7. Click OK to close the dialog box.
  8. Run IISReset to restart the IIS services in Command prompt (elevated mode).

Voila!! Check it now. Smile

SCCM: How to verify “Distribution Point” available or not?

How would you check if software or OS deployment distribution point is available or not?  May be you encountered distribution point errors during software or OS deployment.

Follow the steps below: (this to check OSD distribution point)

  1. Open Configuration Manager Console
  2. Expand to System Center Configuration Manager / Site Database / Computer Management / Operating System Deployment / Operating Systems Images / OS Image Name / Package Status / Package Status / Site Name
  3. On Results Pane, check the Path and verify the path in Windows Explorer.

This will verify you don’t run into any permission issues or availability issues. Hopefully you resolve the issue with this.


SCCM: Agent Install fails

I am sure this blog will help lot of you with same setup as mine.

SCCM R3 running on Windows 2008 R2 in NATIVE mode. SQL database is placed at remote SQL 2008 Cluster.

Installation went fine. My computers were discovered successfully and listed in collections. BUT, SCCM Agent is failing to install, either Automatic or Manual.

If you read the CCMSetup.log (located at C:\Windows\CCMSetup in Windows 2008/Windows 7, C:\Windows\System32\CCMSetup in Windows 2003/XP), you will find this error message in the end.

“Call to HttpSendRequestSync failed for port 443 with an error code.”

I checked the following items and all looking good.

Thumbs upCorrect Web Server Cert in SCCM server
Thumbs upClient auto enrollment GPO and client machines are getting certs
Thumbs downConfMgr Management Point is in Red and stopped with errors in Site Status node

All my Internet search were wasted time and frustration. Even though Windows 2008 R2 OS is support for SCCM R3, I am suspecting something still wrong with locked down security in the OS.

I found the FIX myself accidentally. This might work for you too. The fix is,

  1. Log on to the SCCM server via Remote desktop
  2. Open Internet Information Services (IIS) Manager Console
  3. Expand Server Name –> Sites –> Default Web Site
  4. click on CCM_Client site. On right side pane, double click SSL Settings. Select Accept on Client Certificates: section.


5.  Click Apply on Action Pane.
6.  Repeat these steps 4 through 5 again for CCM_Incoming, CCM_Outgoing, CCM_System and SMS_MP sites.
7.  That’s It. You may want to run IISReset, just in case. Now automatic client install (or Manual) should be working.

Now I hear you asking “Is this setting makes less secure in Native mode? After all Native Mode is all about secure setup”.  I know..believe me I know. 

If you restart the server, the above settings will revert back to “Require” automatically. My objective was to kick off the client automatic install. Winking smile