Failed to resolve 'SMS_SLP' to IP address from WINS. LSGetAssignedSiteFromSLP : Unable to get the list of SLPs

When you try to assign SCCM Site Code using Discovery button on SCCM Client there are errors in LocationService.log

Failed to resolve 'SMS_SLP' to IP address from WINS.
LSGetAssignedSiteFromSLP : Unable to get the list of SLPs

In order to resolve these errors on domain controller WINS Server should be installed and WINS SLP parameters configured.
Here is the procedure for manually configuring WINS SLP parameters:

On DC where WINS Server already was configured in CMD run netsh.

Type wins and press Enter.

Connect to the WINS server using: server \\ip address where ip address is ip adress of WINS server.

Type add name Name=SMS_SLP endchar=1A rectype=0 ip={ server locator point IP address }
where server locator point IP address is SCCM server's IP address.

To verify that you entered correct data for SLP in your WINS Server type this command:
show name Name=SMS_SLP endchar=1A

Next step is to configure WINS server in your network card TCP/IP properties or if there is DHCP in the network to configure WINS parameter in DHCP server.

Now if you try to add Internet SCCM based client to SCCM site code specifying DNS Sufix and click Discover in few seconds SMS Site Code will be discovered successfully. Same scenario is for workgroup computers belonging to different AD forest and managing by SCCM in other forest. 

Remove SCCM Child Primary Site

MTS - Primary Central Site
SEC - Secondary Site
MT1 - Child Primary Site

Pictures below show on SCCM Child Primary console that Computer Collections and Native SCCM Central Site Software Deployment Packages and Advertisements are locked out.

Here is the  procedure how to remove MT1 SCCM Child Primary Site from its MTS SCCM Parent Site.
First step is to delete MT1 child site address from MTS Parent Site via SCCM console.

Next step is to execute Preinst.exe which is located in C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\00000409 folder:

Executing Preinst /dump shows SCCM sites in SCCM Parent Central Site. The target is to remove MT1 Child Primary Site.

 

Delete jobs for MT1 site: Preinst /deljob MT1

Delete MT1 site: Preinst /delSITE MT1 MTS

Execute again Preinst /deljob MT1 to delete any job in meantime

Executing again Preinst /dump comand shows that MT1 Child Primary Site has been removed from SCCM Parent site.

On SCCM Child Primary Server Console remove settings from Report to parent site to Central site

 

Finaly you can see that all locked out items have been removed. All Software deployments packages, Advertisments, OS deployment packages, and Task Sequences have been inherited form SCCM Parent site into SCCM Child Site and can be modified.

Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)

When you try to install SCCM Client in ccmsetup.log file on local machine you are getting the following error:

Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)
A Fallback Status Point has not been specified.  Message with STATEID='308' will not be sent.

To resolve the issue WebDav on SCCM's IIS WebDav should be configured.
Here is the way how to configure Web DAV settings:

Change the settings as is shown on the picture, Click Apply and after click on WebDAV Authoring Rule.

Configure Authoring Rule as is shown on the picture and click OK.

If you have still the same issue then remove Management Point and install it again.

The instruction at 0x769a7a1f referenced memory at 0x00000028. The memory could not be written. Click on ok to terminate the program.

You get this error message when you want to deploy unattended Windows XP SP3 installation using SCCM 2007 R3 to VMware machine hosted on VMWare ESX Server 3i, 3.5.0.

The instruction at 0x769a7a1f referenced memory at 0x00000028. The memory could not be written. Click on ok to terminate the program.

The reason of this issue is missing mass storage drivers for VMWare image.

To resolve this issue VMWare SCSI Cotrollers drivers should be imported into SCCM and applied  to boot images and Drivers package distribution package.
Drivers for VMWare ESX machine you can find on already existed VMWare Windows XP machine in C:\Program Files\VMware\VMware Tools\Drivers\, copy to the SCCM Server and import it. To successfully install Windows XP SP3

First create a Driver Package in SCCM;

After that import the VMWare drivers into the Driver section:

Make sure that during Driver creation wizard, to update boot images and distribution points of Driver package.

..

 Add Apply Driver Package into the Task Sequence, choose previosly created VMWare driver package and check: "Select the mass storage driver within the package that needs to be installed before setup on Pre-Vista operating systems"

SCCM 2007 and Microsoft Deployment Toolkit - Video

SCCM 2007 and Microsoft Deployment Toolkit - Video presentation by Richard Smith a Senior Consultant with Microsoft Services, UK which includes:

• Setup the server environment for SCCM 2007 OS deployment
• Configure the SCCM 2007 Site Settings
• Configure the SCCM 2007 Computer Management Settings
• Configure the SCCM 2007 Operating System Deployment Settings
• Setup and use MDT integration with SCCM 2007
• Add a reference machine object to SCCM 2007
• Create a build and capture reference image for mass deployment using SCCM 2007

 SCCM 2007 and Microsoft Deployment Toolkit - Video

Forcing full synchronization from SCCM Parent site

Forcing synchronization from SCCM Parent site to the child site can be done using the following way:

Logon to SCCM Primary site using account with full SCCM admin privileges and to run preinst command from: 

C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\0000040

using the following switch:

preinst.exe /syncchild XXX

where XXX is a child SCCM code.

in my case MT1 is my primary child SCCM Server.

Check the following log files after launching preinst command:


Despool.log, Replmgr.log, Sender.log

Configuring SCCM 2007 Secondary site issue

After installing the secondary site on SCCM secondary server in SCCM console this site has not been shown or still is pending.
Here is the solution:
Log on your Secondary SCCM Site server, copy the file \inboxes\sitectrl.box\SiteCtrl.ct0 file to a temp location, rename it to 00000000.ct2 and copy the renamed file to Primary SCCM Site Server \inboxes\hman.box\
In few seconds on SCCM Console you can see the Second SCCM Site Server.

Instaled version of WAIK - SCCM SP2 upgrade error

During the upgrade from SCCM 2007 SP1 to SCCM 2007 SP2, Installation Prerequisite Check gives the following error:

OS Deployment in Configuration Manager 2007 SP2 requires the WAIK 2.0 (version 6.1.7600).

To resolve this issue current WAIK 1.1 installation from SCCM 2007 SP1 has to be removed and WAIK 2.0 version from SCCM 2007 SP2 has to be installed.

Remove WAIK 1.1 from SCCM 2007 SP1.

 

Install WAIK 2.0 from SCCM 2007 SP2 install DVD source.

Checking C:\Program Files\Windows AIK\Tools\x86\ImageX.exe Details property on ConfigMgr Server shows that the right version of WAIK 2.0 has been installed.

Run Application as a Windows Service

To allow an application to run as Windows Service under Windows 2008 you can use SrvAny.exe which is part of Windows 2003 Resource Kit.

1. Download Windows 2003 Resource Kit from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
and extract it.
2. Copy SrvAny.exe into C:\Windows\System32
3. Create a service using SC command which start srvany.exe.
ex: create MyService binPath= C:\Windows\System32\srvany.exe DisplayName= "My Service"
4. Using the previous action MyService registy key has been created in Registry.
Open Registry using regedit and in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyService create a Parameters key.
5. In Parameters create an String Value Application and enter the full path of the application.

Here is the example of making flcd4.exe to work as a service.
flcd4.exe is a daemon service from Floating License feature from 3D-Equalizer http://www.sci-d-vis.com/

Create  3D-Equalizer service using SC command:
SC create 3D-Equalizer binPath= C:\Windows\System32\srvany.exe DisplayName= "3D-Equalizer"

Go to services and change the Startup type to Automatic.

Open Registry using regedit and in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\3D-Equalizer create a Parameters key. Here create a String Value Application and enter the full path of the application: C:\3DEqualizer\3DE4_win32_r1b11\bin\flcd4.exe. Close the registry.

Go to services and start 3D-Equalizer.

and Voilà it works!!

Desired Configuration Management: Software Distribution to Dynamic Computer Collection based on Compliant Status - Part 3

This article continues from Part 2  http://tompopov.blogspot.com/2011/05/desired-configuration-management_24.html 


Next Step to finish our Software distribution Scenario for Computers which are Non-Compliant based on DCM status is to apply SCCM ForeFront Client Software Package on previously created Dynamic Computer Collection:  System: DCM Dynamic Computer Collection.

Using this SCCM configuration ForeFront Client will be installed on those computers.

When next refresh interval for DCM Configuration Baseline will check the status of those computers it will show that the status now is Compliant.

That automatically means that these computers will automatically disappeared from Dynamic Computer Collection:  System: DCM Dynamic Computer Collection and no more any SCCM Software Package will be applied.

This is a good way using Desired Configuration Management feature from SCCM to keep up-to-date installed software on domain computers .  

Desired Configuration Management: Software Distribution to Dynamic Computer Collection based on Compliant Status - Part 2

This article continues from Part 1 http://tompopov.blogspot.com/2011/05/desired-configuration-management.html

To apply Configuration Baseline to Computer Collection right click on target collection and click on Assign Configuration Baseline:

Choose the Configuration Baseline, in this case FCS Installed Baseline, click OK, Next and Close.

When the Configuration Baseline is applied to the target computer, go on SCCM Configuration Manager client, click on Evaluation of selected FCS Installed Baseline configuration baseline and clicking on View Report you will get that the status is Non-Compliant:

Next step is to create Dynamic Computer collection based on the status of the DCM.

Right click on Collections and choose New Collection. Write the name, in this case is: System: DCM Dynamic Computer Collection

Click on query button, write the name of the query (in this case FCS Compliant Status), click on Radio buton Limit to collection to choose the collection (System: DCS tests was the Computer Collection where DCM Configuration baseline was applied) and click on Edit Query Statement.  

Click on Criteria tab, click on yellow star, choose Select on Criteria properties window, in Select Atribute window on Attribute class choose Configuration Item Compliance state and on Attribute choose Compliance State Name.

Click on Value button and choose Non-Compliant in Values window.

Click Ok to close Criterion Properties window and to save the criateria.

Click on the yellow start to create another criteria. Click Select on Criterion properties window, in Select Attribute window on Attribute class choose Configuration Item Compliance state and on Attribute choose Localized Display Name. Click OK to close Select Attribute window.

Choose FCS Installed Baseline from the list and click OK to close Values window.

Click OK to close the second Criteria.

To check the SQL statement click on Show Query Language button.

select *  from  SMS_R_System inner join SMS_G_System_CI_ComplianceState on SMS_G_System_CI_ComplianceState.ResourceId = SMS_R_System.ResourceId where SMS_G_System_CI_ComplianceState.ComplianceStateName = "Non-Compliant" and SMS_G_System_CI_ComplianceState.LocalizedDisplayName = "FCS Installed Baseline"

Click OK to close the Query and click Next and Close to save Dynamic Computer Collection.

After Updating and refreshing this Dynamic Computer Collection on right pane you will get the computers with Non-Compliant Status or the computers which do not have FCS ForeFront installed.

 

Continue on Part 3: http://tompopov.blogspot.com/2011/05/desired-configuration-management_25.html