AD schema is not extended or SLP is not present. Cannot continue site assignment

You may received the error - "AD schema is not extended or SLP is not present. Cannot continue site assignment." log in LocationServices.log when the SCCM client is successfully installed on the machine, but the SCCM client failed to discover primary site.

If the above entry is log, there are few things you may need to look into before you proceed with further action:

1. Is the Management Point publish in Active Directory?
   
2. Is the Management Point publish in DNS?
3. If you are using WINS for name resolution, you may need SLP registered in WINS.

How if the above components are already in-place but the SCCM client is still failed to discover primary site?

Another simple trick, try to verify your network DNS & WINS settings, the SCCM client may failed to assign to primary site due to incorrect assignment of DNS & WINS address.

SCCM Client Push Installation failed

I believed most of you guys may facing this problem when try to push SCCM client to the workstations using Client Push Installation. When you failed to push the client from SCCM server, first thing come to your mind maybe is Windows Firewall blocking that. But somehow, after you enable necessary ports for SCCM Client Push Installation at Windows Firewall, it still doesnt work. After that you might try to stop the Windows Firewall service at the workstation, but still no luck...

Recently during we work on one large SCCM deployment, we found one interesting stuff. Here begin the story, we suspected one of the workstation is infected by virus, because the users is complaining the machine is slow and very difficult for the user to perform daily work. Unfortunately, that machine haven't installed with SCCM client yet. Therefore, we went down to the machine and perform a virus scan, we also tried to extract the local machine antivirus program logs file to understand the machine condition. After we gather all the necessary logs files, we found few interesting entries from the log:

C:\Windows\system32\ccmsetup.exe
Prevent remote creation/modification/deletion of anything in the Windows folder and subfolders. Action: Blocked

C:\Windows\SMSClientInstall
Prevent remote creation/modification/deletion of anything in the Windows folder and subfolders. Action: Blocked

I hope the above information can give you guys a hint when you hit such a problem in the future. Do share this with your customer if you facing this problem.

Windows Firewall exceptions for SCCM Client Push Installation

After you had enable Client Push Installation in SCCM, you found all the client machines failed to receive and install the SCCM agent. After you verify the log files, you may found out the Windows Firewall in client machine is blocking the Client Push Installation. Due to company policy, it is impossible for you to turn off the Windows Firewall on client machines...

Here we provide one good solution for IT Administrators to encounter issue above.

In order to successfully use SCCM Client Push Installation, you must add the following as exceptions to the Windows Firewall on every client machines:

• File & Printer Sharing
• Windows Management Instrumentation (WMI)

After all things is done, lets rocks with SCCM Client Push Installation!

How to Remove SMS Advanced Client using Msiexec /x

We had meet one scenario from one of the customer, we are trying to remove SMS Advanced Client from one of the Windows XP machine using Ccmclean tool (Ccmclean tool can be found in SMS toolkit). But unfortunately, it failed to remove the client by using Ccmclean.

There is another method to remove the SMS Advanced Client from the machine which is msiexec /x command.

Before executing that command, you must know what is the GUID for the SMS Advanced Client, the GUID value can be found inside the Registry editor under following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
\CurrentVersion\Uninstall

The correct GUID has SMS Advanced Client as the Display Name value.

After you get the SMS Advanced Client GUID value, execute the msiexec /x command at command prompt.

Msiexec /x {D8EF2D11-47CF-45E5-B423-47B29706DE12}
(the value behind Msiexec /x indicate the GUID of SMS Advanced Client)

After you execute the Msiexec /x on the machine, you may need to manually remove the VPCache folder for SMS Advanced Client. Below is the step by step how to complete the task:

1. Locate the following registry key in registry editor:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\VPCache

2. The Path value for VPCache is the location of the VPCache folder on the system drive. For example, %Windir%\System32\VPCache.

3. Locate the VPCache folder and then delete it from the hard drive.

4. Lastly, delete VPCache registry key from the registry editor.

Although this method need to spend more time to complete it, but it is a alternative for you to remove the SMS Advanced Client from the machine, no harm to have a try. :)


P/S: Please use Registry Editor with extra careful, or else it may crash your system. :)