How to Install Configuration Manager Clients Using Software Update Point Based Installation

Step:1

To configure an Active Directory Group Policy object to specify the software update point for client installation and software updates

1. Using an editor such as Windows Group Policy editor, open a new or existing Group Policy object.

2. In the Group Policy editor, navigate to Computer Configuration / Administrative Templates / Windows Components / Windows Update, and then open the properties of the setting Specify intranet Microsoft update service location.

3. Click Enabled.

4. In the Set the intranet update service for detecting updates: field, specify the name of the software update point server you want to use, and the port. These must match exactly with the server name format and the port being used by the software update point:

   • If the Configuration Manager site system is configured to use a fully qualified domain name (FQDN), specify the server name using FQDN format.
     
     
   • If the Configuration Manager site system is not configured to use a fully qualified domain name (FQDN), specify the server name using a short name format.
     
     
   • If the site is in mixed mode and software updates is using the default Web site, the port number is likely to be 80 unless it has been changed.
     
     

   If the site is in mixed mode and software updates is using a custom Web site, the port number is likely to be 8530 unless it has been changed.

    If your WSUS Setup configured on port 8530 then the below URL will be placed

   • Example: http://myactivewsusserver.mydomain.com:8530
     
     or  If your WSUS Setup configured on port 80 then the below URL will be placed
     
   • http://myactivewsusserver.mydomain.com:80
     
     

5. In the Set the intranet statistics server: field, specify the name of the intranet statistics server you want to use. There are no specific requirements for specifying this server. It does not have to be the same computer as the software update point server, and the format does not have to match if it is the same server.

6. Assign the Group Policy object to the computers on which you want to install the Configuration Manager client and receive software updates.

Step:2
To publish the Configuration Manager 2007 client to the software update point

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> – <site name> / Site Settings / Client Installation Methods.

2. Right-click Software Update Point Client Installation, and click Properties.

3. To enable client installation, select the Enable Software Update Point Client Installation check box.

4. If the client software on the Configuration Manager 2007 site server is a later version than the client version stored on the software update point, the Upgrade Client Package Version dialog box will open. Click Yes to publish the most recent version of the client software to the software update point.

    

5. To finish configuring the software update point client installation, click OK.

 

-------------------
Thanks,
http://sccm07.blogspot.com/

SCCM Client failes with Software Updates: WUAHandler.log Error = 0x80070002

SCCM Client failes with Software Updates:

 

 

Issue:- Software updates failes without installing when you check the WUAHandler.log file you will get below erro

OnSearchComplete - Failed to end search job. Error = 0x80070002. WUAHandler 1/28/2009 3:00:15 PM 3380 (0x0D34)
Scan failed with error = 0x80070002. WUAHandler 1/28/2009 3:00:15 PM 3380 (0x0D34)

 

Solution: Check will you able to connect wmi from remote system?

 

Rebuild the WMI

 

-------------------
Thanks,
http://sccm07.blogspot.com/

grave-accent character (`)

grave-accent character (`)

 

-------------------
Thanks,
http://sccm07.blogspot.com/

First command to start with Powershell is

First command to start with Powershell is

Get-Command
Get-Help

-------------------
Thanks,
http://sccm07.blogspot.com/

Power Shell Learning Commands

Power Shell Learning Commands:-

 

 

dir -RECURSE

`

Start-Transcript filename.txt

 

stop-Transcript

 

I will post to continue this article persistently

 

 

Paddy

 

SCCM 2007 / SMS 2003 SQL Package Related Query

-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->
-----------------------------------------------------------------------------------------------------------------------------------
To know the package Name and ID

SELECT     PackageID, Name
FROM         dbo.v_Package
-----------------------------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------------------------
SQL Query:-->

If you want to filter with the package ID then modify the Query to

SELECT     PackageID, Name
FROM         dbo.v_Package
WHERE     (PackageID = 'YourPKGID')

-----------------------------------------------------------------------------------------------------------------------------------
-------------------
Thanks,
http://sccm07.blogspot.com/

Failed to remove package from SMS / SCCM Retired/ Correpted distrubution point

Failed to remove package from a retired distrubution point

 

Select * from pkgservers where NALpath like '%\\retired DP path\DP$'
Select * from pkgstatus where pkgserver like '%\\retired DP path\DP$'

by runing above two commands verifiy that you have got the correct Correpted DP package ID or not. then if you find it you can safly run the below two commands to delete.

Next delete entries from any of the above tables to the invalid dp share.

Delete from pkgservers where NALpath like '%\\retired DP path\DP$'
Delete from pkgstatus where pkgserver like '%\\retired DP path\DP$'

This will be same for SMS 2003 and SCCM 2007
-------------------
Thanks,
http://sccm07.blogspot.com/