Pages

Showing posts with label SCCM 2007. Show all posts
Showing posts with label SCCM 2007. Show all posts

On Windows 2008 R2 with SP1 you may face MP Fatal error 1603 Problem

This could happened because of not supported versions to fix this you need to apply a patch  KB2489044. (I ran into this problem today at a customer place and fix is below)

 

Ms Link http://support.microsoft.com/kb/2489044/en-us

Who is installed Software's ?

Collection for computers that failed to run an advertisement 

http://blog.coretech.dk/confmgr07/collection-for-computers-that-failed-to-run-an-advertisement/

 

Who is installed Software's ?

http://blog.coretech.dk/confmgr07/config-mgr-inventory-and-reporting/audit-software-installations/

Troubleshooting SCCM Software Updates

 

http://www.myitforum.com/myITToolbar/frame-click.asp?

http://blogs.technet.com/b/sudheesn/archive/2010/11/10/troubleshooting-sccm-part-iii-software-updates.aspx

 

VB Script to Clear SCCM Client Cache (C:\Windows\System32\CCM\Cache)



-------

on error resume next

dim oUIResManager
dim oCache
dim oCacheElement
dim oCacheElements

set oUIResManager = createobject(“UIResource.UIResourceMgr”)

if oUIResManager is nothing then
      wscript.echo “Couldn’t create Resource Manager – quitting”
      wscript.quit
end if

set oCache=oUIResManager.GetCacheInfo()

if oCache is nothing then
      set oUIResManager=nothing
      wscript.echo “Couldn’t get cache info – quitting”
      wscript.quit
end if

set oCacheElements=oCache.GetCacheElements

for each oCacheElement in oCacheElements
oCache.DeleteCacheElement(oCacheElement.CacheElementID)
next

set oCacheElements=nothing
set oUIResManager=nothing
set oCache=nothing

 

----------

 

Do you want to collect all clients LOG files to send it to some one ?

use this script below …

1. Create a folder and place the following batch files and txt file on it: Collect.bat, TestAll.bat, TestPC.bat, and Computers.txt. The codes for the batch files are given below. Place the name or ip address of the machines in computers.txt (one computer name/ip address per line)

2. Run TestAll.bat

3. A folder named “Result” will be created inside the folder where the batch files are located. This folder will contain the log files of the machines that you entered in computers.txt

A. Collect.bat

MD .\Result\%1
MD .\Result\%1\CCMLog
MD .\Result\%1\CCMSETUPLog
xcopy \\%1\admin$\system32\ccm\logs\*.* .\Result\%1\CCMLog /E /Y
xcopy \\%1\admin$\system32\ccmsetup\*.log .\Result\%1\CCMSETUPLog /E /Y

B. TestAll.bat

rd  /Q /S .\Result_OLD
Move /Y .\Result .\Result_OLD
rd  /Q /S .\Result
MD .\Result

del FailPing.txt
del FailConnect.txt
del Succeed.txt
for /f %%i in (computers.txt) do call TestPC %%i

C. TestPC.bat

@echo off
REM usage: TestPC PCName

if not %1. == . goto INSTALL
Echo Usage: TestPC PCName
goto END

:INSTALL
REM @echo on
Echo Now test %1

Echo Now try to ping %1
ping %1 -n 1 | find /i “ttl=” && Goto ONLINE
Goto OFFLINE

:ONLINE
Echo can ping %1
Echo Now try to connect to \\%1\Admin$
Dir \\%1\Admin$ >nul
If ERRORLEVEL=1 goto ConnectionFailed
Echo Connection test succeeded for %1. Can connect to \\%1\admin$.
Echo %1 >>.\result\Succeed.txt
Echo Now collecting data
call Collect.bat %1
goto END

:OFFLINE
echo cannot ping %1
Echo %1 >>.\result\FailPing.txt
goto Failed

:ConnectionFailed
Echo cannot connect to \\%1\admin$.
Echo %1 >>.\result\FailConnect.txt
goto Failed

:Failed
Echo Connection test failed for %1

:END
Echo.

D. Computers.txt

A consolidated Report for Patch Deployments

to get the consolidated Report for all your deployments / instead of depending on dashboard you can view this PVT Report

 

Source:- http://blog.coretech.dk/kea/status-report-for-software-update-deployments/

Select Deploymentname, Available, Deadline,

cast(cast(((cast([Compliant] as float) / (ISNULL([Compliant], 0) + ISNULL([Enforcement state unknown], 0) + ISNULL([Successfully installed update(s)], 0) + ISNULL([Failed to install update(s)], 0) + ISNULL([Installing update(s)], 0) + ISNULL([Waiting for another installation to complete], 0) + ISNULL([Pending system restart], 0) + ISNULL([Downloading update(s)], 0)))*100) as Numeric(10,2)) as varchar(256)) + '%' AS '%Compliant',

  [Compliant],

  [Enforcement state unknown],

  [Successfully installed update(s)],

  [Failed to install update(s)],

  [Installing update(s)],

  [Waiting for another installation to complete],

  [Pending system restart],

  [Downloading update(s)]

From

(select

a.AssignmentName as DeploymentName,

a.StartTime as Available,

a.EnforcementDeadline as Deadline,

sn.StateName as LastEnforcementState,

count(*) as NumberOfComputers

from v_CIAssignment a

join v_AssignmentState_Combined assc

on a.AssignmentID=assc.AssignmentID

join v_StateNames sn

on assc.StateType = sn.TopicType and sn.StateID=isnull(assc.StateID,0)

group by a.AssignmentName, a.StartTime, a.EnforcementDeadline,

      sn.StateName) as PivotData

PIVOT

(

SUM (NumberOfComputers)

FOR LastEnforcementState IN

( [Compliant],

  [Enforcement state unknown],

  [Successfully installed update(s)],

  [Failed to install update(s)],

  [Installing update(s)],

  [Waiting for another installation to complete],

  [Pending system restart],

  [Downloading update(s)])

) AS pvt

Good talking about Client Health common issues that we encounter in real world.

Good talking about Client Health common issues that we encounter in real world.

 

Take some time to focus on some common issues with client installation and communication issues, as well as a couple of tools that make troubleshooting infinitely easier.


SCCM Tools available

First up I want to list 3 of the primary tools I use for client side troubleshooting.

  1. Trace32 Log Reader
  2. SCCM Client Center
  3. JSandys CM Startup Script

Now the first item on that list, trace32 is by far the most valuable tool to the SCCM administrator outside of the console itself, perhaps even more so than the console. It allows filtering, highlighting, real time updates, and just generally makes the logs readable.

SCCM Client Center, this tool attaches to the cm WMI Namespace and allows for nearly full control of the client on the target machine. In terms of remediation, or even testing, there is no reason this tool shouldn’t be installed.

Config Manager Startup Script by Jason Sandys. This script is easily configured for implementation and has fairly rich logging power for a vbscript, it’s also lighter weight than some of the other health scripts. I highly recommend using this for maintaining client integrity, as well as offering an installer tool for the CM agent by secondary or third parties.


The Client

First, lets start with identifying the clients existence on the local machine.

Here’s where to look:

  • Control Panel > Configuration Manager (this is one of the quickest methods)
  • Task Manager (ctrl+shift+esc) > Processes > CcmExec.exe
  • Task Manager > Services > CcmExec
  • Control Panel > Admin Tools > Services > SMS Agent Host
  • c:\windows\system32\ccm (32bit)
  • c:\windows\syswow64\ccm (64bit)
  • HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\Product Version (32bit)
  • HKLM\SOFTWARE\Wow6432Node\Microsoft\SMS\Mobile Client\Product Version (64bit)

This is a list of the primary locations to check for the presence of the client, it’s also useful for finding methods to script around identifying them.

The Client’s Jobs

Now lets discuss what the client does. First lets recognize that the client is just a dictator for the most case, it tells multiple windows services what to do to complete specific tasks. Until we need to break down what services do things specifically lets just treat the client as the primary initiator.

  • Policy updates and application
  • Manage downloads
  • System scans
  • Inventory reports

The client and server relationship relies heavily on BITS, Admin shares, RPC (at least for installation), WMI, AD, and WUA.

The client will regularly talk to the server, telling it about any changes it’s had since it’s last conversation, by way of xml. It will also ask the server what it should be doing differently, to which the server sends the client it’s latest policy. The client will review that policy then act, or do nothing depending on if there are any actionable changes.

Actionable changes could be installation of software, OS, OS configuration changes, even changes in the frequency of their conversations. These exchanges of course are called policy updates, and I believe by default they are set to 90 minutes (no real reason to change it either).


Client Installation

There are multiple ways to install the SCCM client, and in a lot of ways, that method will vary depending on your environment. I will stick to the basics and explain the process if done by server initiated push. I will also discuss what is required.

First the server begins by initiating a PUSH, using local admin rights, it will copy down the CCMSETUP.EXE file to either c:\windows\ccmsetup or c:\windows\system32\ccmsetup

A service named CcmSetup is made and it begins transferring the client contents to the local machine and finalizing installation and cleanup of the directory.

A log of the transaction is left in the ccmsetup folder named ccmsetup.log

Once this process is complete, the client will perform it’s first policy update and make it’s active client existence known to it’s respective primary server.

So what if installation fails?

This isn’t a perfect world. If you are pushing into an existing environment, things may have accidentally found there way out of standards and or flat broken.

Lets discuss what is required on a local PC for a successful install:

  • Resolvable hostname (proper DNS entry)
  • Service account with local admin rights
  • RPC access to OS components (such as registry)
  • Admin$ shares
  • WUA (Windows Update Agent)

Instead of explaining exactly why for each of these, lets explain how to resolve potential problems with each. I also want to treat this as an all inclusive troubleshooting guide for the client, so I won’t limit things to just install failures. Truthfully, if any of these breaks after installation, the client will most likely not function as intended.

Improper DNS entry:

From the local machine there is little you can do to resolve this problem. Two methods that could resolve the problem are:

ipconfig /registerdns

This will attempt to update the DNS records for all adapters of the local machine.

ipconfig /flushdns

This will dump all resolver cache data on the local machine. (long shot, but I’ve seen this clear up client DNS conflicts from the push)

Any additional resolution would need to be done by the Domain Admin on the DNS server with the improper pointer references.

Service Account with local admin rights:

This is a very simple solution. Add the appropriate service account to the local admins group on the client PC. For Installation and operation, this account needs to be set for the client to perform it’s jobs.

RPC Access:

This one can have you scratching your head at times, but a majority of the times it’s tied to a firewall. Make sure that local firewalls have exceptions built in for the SCCM server. When in doubt, disable the firewall software to verify if it’s the culprit or not.

Also ensure that the RPC (RpcSs) and RPC Endpoint Mapper (RpcEptMapper) services are Started.

Some of these changes may require a restart before taking effect so be aware of that while troubleshooting RPC denials. It’s also worth mentioning there are a multitude of applications that could disrupt this functionality, so be sure to thoroughly investigate the machine for potential culprits.

Admin$ Shares:

First off, the service Workstation (LanManWorkstation) is responsible for these shares, as well as all SMB protocols on the local machine. If it’s disabled, you will not have these shares.

One of the most direct methods for enabling admin shares is in:

HKLM\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\AutoShareWks, 1

HKLM\SYSTEM\CurrentControlSet\Services\LanManServer\Parameters\AutoShareServer, 1

Then restart the PC.

Be aware this setting can be viewed as a security risk, and with that being said, some security software may actively disable them. So treat your evaluation similarly to your RPC troubleshooting.

WUA Disabled:

The Windows Update service being disabled is a fairly simple solution provided there isn’t a GPO forcing it. You can either enable and set the Windows Update service to Automatic (wuauserv). Inside the control panel under Windows Update or Automatic updates set it to automatic.

WUA is responsible for system scans, patching, software delivery, essentially a vast majority of the clients functionality. It is imperative that WUA is enabled.


Logs to Read, and Policy Updates

For the official list of log files, go here.

(http://technet.microsoft.com/en-us/library/bb693897.aspx)

I’m going to touch on the more immediate logs for troubleshooting the following issues.

  • Health
  • Policy
  • Connectivity
  • Licenses
  • Installs

Health:

CcmExec.Log, this log is one of the first stops for suspected bad installs.

ClientLocation.log, this log is a good place to verify that client has a healthy install with a site server.

StatusAgent.log, status messages for client components. Also useful for connectivity issues.

Policy:

PolicyAgent.log, this holds policy request information, very helpful when pulling policy.

PolicyEvaluator.log, this log lets us know know if we are having issues applying policies.

Connectivity:

InternetProxy.log, if you are using unprotected DPs, this is the log to check.

Mpcontrol.log, logs record the state of the management point

LocationServices.log, attempted connectivity to MPs and DPs

Licenses:

Hman.log, if clients aren’t registering this is worth looking into.

Installs:

Ccmsetup.log, client installation happenings are recorded in this log.

Client.msi.log, output from the installer.


That concludes the overview of SCCM client installation and troubleshooting. Happy problem solving. For additional information on the client and troubleshooting check MSDN:

http://technet.microsoft.com/en-us/library/bb693982.aspx

and be sure to get involved with

http://www.myitforum.com/absolutenm/PPLSearch.aspx

Source : -http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=23741&zoneid=89

SMS to SCCM Auto Migration Script

SMS to SCCM Auto Migration Script

 

Copy.bat

 

xcopy /y ccmsetup.exe c:\windows\temp\
xcopy /y ccmclean.exe c:\windows\temp\
xcopy /y install.bat c:\windows\temp\
schtasks /CREATE /SC MINUTE /mo 90 /TN Migration /TR "C:\windows\temp\install.bat" /RU SYSTEM
schtasks /CREATE /SC MINUTO /mo 90 /TN Migration /TR "C:\windows\temp\install.bat" /RU SYSTEM

 

 

Install.bat

 

C:\windows\temp\ccmclean.exe /client /q
C:\windows\temp\Ccmsetup.exe /mp:ServerName SMSSITECODE=Sitecode

SCHTASKS /delete /TN Migration /F

 

 

Advertise the Copy.bat then automatically clients will installing the sccm

Move SCCM Database to remote SQL server

Move SCCM Database to remote SQL server

 

    a. Back up the site database on the current site database server and restore it on the new site database server computer using the SQL Server Management Studio.

    b. Ensure the primary site server computer account has administrative privileges over the new site database server computer.

    c. Close any open Configuration Manager console connections to the site server.

    d. On the primary site server computer, use the hierarchy maintenance tool (Preinst.exe) to stop all site services with the following command: Preinst /stopsite.

    e. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup, or navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.

    f. Click Next on the Configuration Manager Setup Wizard Welcome page.

    g. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.

    h. Select Modify SQL Server configuration on the Configuration Manager Setup Wizard Site Maintenance page.

    i. Enter the appropriate SQL Server name and instance (if applicable) for the new site database server as well as the site database name on the Configuration Manager Setup Wizard SQL Server Configuration page.

    j. Configuration Manager Setup performs the SQL Server configuration process.

    k. Restart the primary site server computer, and verify the site is functioning normally.

OBT Info

Some use full links for OBT

http://www.google.com/search?q=out+of+band+management+sccm+2007&start=10&hl=en&sa=N&biw=1260&bih=620&prmd=ivnsfd&source=univ&tbm=vid&tbo=u&ei=QGbCTe7fO5SChQfdtpGyBQ&ved=0CDsQqwQ4Cg

http://communities.intel.com/community/openportit/vproexpert/microsoft-vpro/blog/2008/10/24/microsoft-sccm-2007-sp1-intel-vpro-training-videos-now-available

http://depsharee.blogspot.com/2011/03/my-configuration-manager-2007-out-of.html

www.vproexpert.com/playbook/vPro_SCCM_QuickStartGuide.pdf

http://64.4.11.252/en-us/library/cc161766.aspx

http://www.agileit.com/Blog/Lists/Posts/Post.aspx?Id=535

http://scug.be/blogs/sccm/archive/2010/05/06/step-by-step-guide-for-provisioning-intel-vpro-clients-in-sccm-2007-sp2-part-3.aspx

http://blogs.technet.com/b/configurationmgr/archive/2009/03/05/configmgr-2007-amt-vpro-useful-links-for-initial-planning-and-deployment.aspx

Powershell :- System Management Container

If you want to create Systems Management Server (SMS) 2003 or System Center Configuration Manager (ConfigMgr / SCCM) 2007, Container i.,e “System Management” with Power shell here it is the Cmdlts

 

 

# Get the distinguished name of the Active Directory domain
$DomainDn = ([adsi]"").distinguishedName
# Build distinguished name path of the System container
$SystemDn = "CN=System," + $DomainDn
# Retrieve a reference to the System container using the path we just built
$SysContainer = [adsi]"LDAP://$SystemDn"
# Create a new object inside the System container called System Management, of type "container"
$SysMgmtContainer = $SysContainer.Create("Container", "CN=System Management")
# Commit the new object to the Active Directory database
$SysMgmtContainer.SetInfo()

You’ll still have to set permissions appropriately, but if you’re looking to automate the entire process, here’s at least once piece!

image

SCCM / SMS Backup Report

To know what sites haven't backed up within a given date range (a day and a half since last backup), and those that have never backed up (never reported a backup).

Groovy stuff, not so easy to determine though, or so it would seem, unless you fall back entirely onto the Status Message sub-system.

When a SMS2003 or ConfigMgr backup completes, a Status Message is produced by the SMS_SITE_BACKUP component and processed by the Site server. As you probably know, Status Messages replicate up the hierarchy, so the Central Site server will know all Status Messages being "sent up".

I've had this code running for a few days, it seems to work a charm.

There is one thing that can get in the way though, customised Status Filter Rules. If you have them, you understand them (unless you've inherited in which case GIYF), and know that they can block Status Messages from being processed or delivered to the Parent Site server (drop all informational for example, as the last rule in the rule set, yes some folks do this!).

The T-SQL to bring back the Status Messages, and to render a list of machines that do not fit the logic (no backup reported, ever) is here:

SELECT vsite.ServerName AS Servername, vsite.SiteCode, MAX(stat.Time) AS LastTime

FROM vStatusMessages AS stat LEFT OUTER JOIN

StatusMessageInsStrs AS ins ON ins.RecordID = stat.RecordID LEFT OUTER JOIN

StatusMessageAttributes AS att1 ON att1.RecordID = stat.RecordID LEFT OUTER JOIN

v_Site AS vsite ON vsite.ServerName = stat.MachineName

WHERE (vsite.Type = 2) AND (stat.Component = 'SMS_SITE_BACKUP') AND (stat.MessageID = 5035)

GROUP BY vsite.ServerName, vsite.SiteCode

HAVING (MAX(stat.Time) < DATEADD(day, - 1.5 , GETDATE()))

ORDER BY LastTime

select 'Sites that have never reported a backup (Investigate any server that is listed)'

select servername from v_site where type = 2 and servername not in

(SELECT vsite.ServerName AS Servername

FROM vStatusMessages AS stat LEFT OUTER JOIN

StatusMessageInsStrs AS ins ON ins.RecordID = stat.RecordID LEFT OUTER JOIN

StatusMessageAttributes AS att1 ON att1.RecordID = stat.RecordID LEFT OUTER JOIN

v_Site AS vsite ON vsite.ServerName = stat.MachineName

WHERE (vsite.Type = 2) AND (stat.Component = 'SMS_SITE_BACKUP') AND (stat.MessageID = 5035)

GROUP BY vsite.ServerName, vsite.SiteCode

HAVING (MAX(stat.Time) >= DATEADD(day, - 1.5 , GETDATE())))

 

 

The Query itself is entirely harmless, in that it doesn't UPDATE or DELETE, but you should be aware it can put a load on your DB instance while running. Nothing to big to worry about, unless you are seriously underspec'd hardware-wise.

And finally, be aware that as long as Status Filter rules are not inhibiting the delivery of the Status Message from down-level sites up the hierarchy, and that Sites in your hierarchy are communicating with their Parent's correctly, then you should be OK to rely on this report. I would suggest having some more reports configured to check for any sites that haven't reported in within the last 24hrs (indicative of some kind of failure taking place) and also to look at using dedicated Monitoring tools such as OpMgr to monitor Site servers and Site systems health using the Management Pack.

Configuration Manager 2007 SuperFlows

The SuperFlow interactive content model provides a structured and interactive interface for viewing documentation. Each SuperFlow includes comprehensive information about a specific Configuration Manager 2007 dataflow, workflow, or process. Depending on the focus of the SuperFlow, you will find overview information, steps that include detailed information, procedures, sample log entries, best practices, real-world scenarios, troubleshooting information, security information, animations, and more. Each SuperFlow also includes links to relevant resources, such as Web sites or local files that are copied to your computer when you install the SuperFlow.

The following table lists the Configuration Manager 2007 SuperFlows that are available for download.

 

SuperFlow Name Description

Client Installation and Assignment SuperFlow (http://go.microsoft.com/fwlink/?LinkId=200706)

Provides detailed steps that you can use to prepare for and install the Configuration Manager 2007 client. This SuperFlow also provides you with the dataflow for background processes, additional resources related to client installation, and troubleshooting information for common issues.

Backup and Recovery SuperFlow for Configuration Manager 2007 (http://go.microsoft.com/fwlink/?LinkID=191983)

Provides detailed steps that help you to backup and recover a Configuration Manager 2007 site.

SuperFlow for Creating SQL Server Reporting Services Report Models in Configuration Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=182504)

Provides detailed steps that you can use to create a SQL Server Reporting Services report model in Configuration Manager 2007.

SuperFlow for Configuring Software Updates (http://go.microsoft.com/fwlink/?LinkId=182287)

Provides detailed steps that help you to plan for and configure software updates at a site. This SuperFlow also includes troubleshooting information and additional resources that you can use to learn more about configuring software updates in Configuration Manager 2007.

Software Update Deployment SuperFlow (http://go.microsoft.com/fwlink/?LinkId=182505)

Provides information that helps you to prepare for and deploy software updates after you configure the software updates infrastructure and synchronize software updates.

Software Updates Synchronization SuperFlow (http://go.microsoft.com/fwlink/?LinkId=182288)

Provides the detailed dataflow for the software updates synchronization process, additional resources related to software updates synchronization, and troubleshooting information.

SuperFlow for Operating System Deployment via PXE (http://go.microsoft.com/fwlink/?LinkId=190812)

Provides information about operating system deployment by using preboot execution environment (PXE) service points.

SCCM : Copy and Paste, context menu add-on

Source:--http://blogs.microsoft.co.il/blogs/doli/archive/2011/04/27/sccm-copy-and-paste-context-menu-add-on.aspx


SCCM : Copy and Paste, context menu add-on


I like SCCM (System Center Configuration Manager) and in my opinion it is a great management tool, but it's developers, apparently, forgot the small things that makes it better. One of the missing feathers is the copy & paste menu option ("Elementary my dear Watson"). When I first installed SCCM 2007, I was very excited to find the copy option, but till today I couldn't find his little sister, "paste", I suspect that they decided to release her in the next version.

Please help "Copy" find his little sister "Paste" in the following picture: סמיילי

image

There is a saying "If the mountain won't come to Muhammad, Muhammad must go to the mountain.", so I tried to write something of my own. Microsoft delivers a good SDK pack for SCCM, which helped me reach my goal.

My tool adds Copy and Paste options to the context menu of Collections (Queries), Packages, Programs and Advertisements.

Collections (Collection Queries)

Select the source collection (from the right or left pane) and choose "Copy Collection Query"

image

Select target collection (from the right or left pane) and choose "Paste Collection Query"

image

Choose a name for the new query

image

If you press cancel the specific query will not be copied (It will proceed to the next query)

The result:

נורת חשמל You first need to refresh the collection branch

image

At the end of the process you will be asked whether or not you want to delete the cashed settings

image

Packages

Select the source package and choose "Copy Package"

נורת חשמל Works only from the right pane

image

To paste the new package select any package on the right pane, and choose "Paste Package" from the Popup menu

Choose a name for the new package

Choose whether or not you want to delete the cached settings

נורת חשמל Don't forget to refresh the collection branch:

image

נורת חשמל Distribution Points,Access Accounts,Programs won't be copied

Programs

Select the source package and choose "Copy Program"

נורת חשמל Works only from the right pane

image

To paste the new program to the same package, right click the source program (on the right pane), and choose "Paste Program" from the menu

To paste the new program to another package, right click the target "Programs" (on the left pane), and choose "Paste Program" from the menu

Choose a name for the new program

Choose whether or not you want to delete the cached settings

נורת חשמל Don't forget to refresh the Programs' branch:

image

Advertisements

Select the source package and choose "Copy Advertisement"

נורת חשמל Works only from the right pane

image

To paste the new advertisement select any advertisement on the right pane, and choose "Paste Advertisement" from the menu

Choose a name for the new Advertisement

Choose whether or not you want to delete the cached settings

נורת חשמל If the source advertisement contains custom scheduler it won't be copied, instead the new advertisement will contain the following fixed date as shown below (Of course, after pasting, you can change it to any desired date):

image

The purpose of this behavior is to avoid automatic deployment after pasting the new advertisement.

נורת חשמל For this reason try to avoid copying advertisements which contains "AS Soon AS Possible"

The target mandatory assignments will have two assignments:

image


SETUP

image

During the setup you can choose which extension to install:

image

You can download the setup from HERE

MSG.Exe : To pass a input to the Batch file for a User inputs / Notification

 

 

msg.exe * /TIME:300 /v /w "Message From IT Administrator: Please Save and close your all office Applications and then click OK"

 

Time:300 seconds will wait for the user input if no input received it will execute it

 

 

Send a message to a user.

MSG {username | sessionname | sessionid | @filename | *}
    [/SERVER:servername] [/TIME:seconds] [/V] [/W] [message]

  username            Identifies the specified username.
  sessionname         The name of the session.
  sessionid           The ID of the session.
  @filename           Identifies a file containing a list of usernames,
                      sessionnames, and sessionids to send the message to.
  *                   Send message to all sessions on specified server.
  /SERVER:servername  server to contact (default is current).
  /TIME:seconds       Time delay to wait for receiver to acknowledge msg.
  /V                  Display information about actions being performed.
  /W                  Wait for response from user, useful with /V.
  message             Message to send.  If none specified, prompts for it
                      or reads from stdin.

SCCM Documentation Updated

Configuration Manager 2007 documentation library (http://technet.microsoft.com/en-us/library/bb680651.aspx) has been updated on the Web with updates for April. Topics that were updated have Updated: April 1, 2011 at the top of the topic.

 

Configuration Manager 2007 Quizzes also updated

 

Configuration Manager 2012 documentation library  Configuration Manager 2012 Documentation Library.

One other Good Website for SCCM

http://certcollection.org/forum/forum/88-sms-sccm-2007/

Single system required Patch’s report from SQL

---Single system required Patch’s report from SQL

 

SELECT DISTINCT

SYS.Name0

AS [Machine Name], UCS.Status AS [Patch Status Code],

CASE WHEN UCS.Status = '2' THEN 'Applicable' WHEN UCS.Status = '3' THEN 'Installed' ELSE '' END AS 'Patch Status', UI.BulletinID, UI.ArticleID,

UI.Title

FROM

v_R_System AS SYS LEFT OUTER

JOIN

v_Update_ComplianceStatusAll

AS UCS ON SYS.ResourceID = UCS.ResourceID INNER
JOIN

v_UpdateInfo

AS UI ON UCS.CI_ID = UI.CI_ID

WHERE

(UCS.Status IN ('3', '2')) AND (SYS.Name0 = 'ServerName'
)

state messages for some reason is not being updated correctly Causes Updates Compliance Report Issue

run the below script to get the actual system state. this will help to report back actual compliance of patch level to SCCM Server

 

Option Explicit
On Error Resume Next

Call RefreshServerComplianceState

' WScript.Echo "Finished"

Sub RefreshServerComplianceState()

    ' Initialize the UpdatesStore variable.
    dim newCCMUpdatesStore
    ' Create the COM object.
    set newCCMUpdatesStore = CreateObject ("Microsoft.CCM.UpdatesStore")

    ' Refresh the server compliance state by running the RefreshServerComplianceState method.
    newCCMUpdatesStore.RefreshServerComplianceState
    ' Output success message.
'    wscript.echo "Ran RefreshServerComplianceState."

End Sub

Advertisement status tracking

How to read the advertisement reports:-

Accepted – Software can be installed in few mins, as it will start downloading the software from remote /local system

No Status - Systems are not online or has issue with SMS Agent, or not received the policy, if the system is online then this status must change in one hour time (if the status not changed then you may

     Suspect the issue with SMS / SCCM agent )

Accepted - No Further Status – Back end installation may be running and need to wait for some time to get the actual status

Failed – Software installation failed, you need to re push once again this advertisement.

Succeeded – Software installed successfully without any issues

Package not downloading due to some IIS File filtering blocking issue

Check with these commands

 

 

BITSADMIN /LIST /ALLUSERS

 

C:\>BITSADMIN /geterror {7D46DE5B-3911-40B1-A72B-607737DB06F9}

BITSADMIN version 2.0 [ 6.6.3790.3959 ]
BITS administration utility.
(C) Copyright 2000-2004 Microsoft Corp.

ERROR FILE:    http://sccmserver.mydomain:80/SMS_DP_SMSPKGD$/SMSPKG/HCC00
05F/AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm -> C:\WINDOWS\system32\CCM\Cache\HCC0005F.1.System\AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm
ERROR CODE:    0x80190194 - The requested URL is not found on this server.
ERROR CONTEXT: 0x00000005 - When processing the remote file error has occurred

/LISTFILES job                     Lists the files in the job
/SUSPEND job                       Suspends the job
/RESUME job                        Resumes the job
/CANCEL job                        Cancels the job
/COMPLETE job                      Completes the job

 

BITSADMIN /INFO job [/VERBOSE]

BITSADMIN /geterror {B2826EF6-C78B-4D1C-A386-94D0D36DC107}

BITSADMIN /LIST /ALLUSERS

 

Where job =

{B2826EF6-C78B-4D1C-A386-94D0D36DC107}

SMS 2003 Major issues in MS PSS

 

image

image

image

image

image

image

image

image

image

 

image

image

image

image

image

image

image

image

image

image

image

image

image

image

image

image

image