Trying to give something back to the Community...
One of my Packages is not installing via my Task Sequence. If I look in "execmgr.log" I see the following line:
TS Step required to run in user context, targeted to user or requiring user input. Rejecting.
ANSWER:
If you look at the line above the one you've posted it will show you the Program Name and Package ID for example:
Creating mandatory request for advert SMS10000, program <program_name>, package <package_ID>
Right-click on the Program in the ConfigMgr Console and select "Properties".
Click the "Environment" tab where you'll probably find the "Run mode" is set to "Run with user rights" rather than "Run with administrative rights". Also make sure you change "Program can run:" from "Only when a user is logged on" to "Whether or not a user is logged on".
Click "OK" to save the changes.
Some of you may find my "[SMS 2003] Query for Count of Machines by Model Type/ Manufacturer", query a bit unwieldy in big environments. So what if you want to run the same Query but only for a specific Site?
Well you simply insert the line:
Where Name0 Like '<site_code>%'
where '<site_code>' is the Site Code you want to query against. So for example if my Site Code is 'FAQ' then the Query I'd run is:
Select
Manufacturer00 Manufacturer,
Model0 Model,
Count (Model0) Counts
From Computer_System_Data
Where Name0 Like 'FAQ%'
Group By Model0, Manufacturer00
Order By Manufacturer00
Does anyone have a query that will show me what makes and models of machines I have in my environment and how many there are of each one?
ANSWER
Yes try this:
which will give you something like this:
NOTE: If when you run the query you get the following message:
Msg 208, Level 16, State 1, Line 1
Invalid object name 'Computer_System_Data'.
Make sure you are running the Query against your SMS database and NOT Master (which it defaults to).
Microsoft have just updated the following KB and I've updated the List of ConfigMgr KB Articles on FAQShop accordingly:
http://support.microsoft.com/kb/2019648/en-us?sd=rss&spid=12769
Error message "MMC could not create the snap-in" when opening the System Center Configuration Manager 2007 console installed on a localized version of Windows XP Service Pack 3
If you're seeing this error it could be down to the fact the machine doesn't have network connectivity or doesn't have a valid NIC driver... [Goto article]
http://support.microsoft.com/kb/2591848/en-us?sd=rss&spid=12769
How To Deploy the Zune Desktop Client using Microsoft System Center Configuration Manager 2007
If your Task Sequence fails with this error it could be down to an issue with the Install Software Updates Task timing out... [goto article]
http://support.microsoft.com/kb/938947/en-us?sd=rss&spid=12769
A WSUS client that is connected to a WSUS or Configuration Manager 2007 SUP server takes longer than expected to finish an update scan
It's important to understand the differences between Updating and Refreshing a DP as you'll potentially need to use both at some point depending on the situation. So let me explain the differences here …
http://support.microsoft.com/kb/967506/en-us?sd=rss&spid=12769
Client push fails when the System Center Configuration Manager 2007 Management Point is installed in Windows Server 2008
There are certain "rules" when it comes to which version of the Client can be assigned to which version of the product as detailed here...
One of my applications defined in my MDT Database refuses to install when the Task Sequence runs. I’ve checked the Package ID and Program are set correctly in the MDT database and match those in ConfigMgr.
However, when I build a machine the application doesn’t install. If I look in the “C:\WINDOWS\System32\CCM\Logs\BDD.log” I can see the relevant line for the Package in the form “Property PACKAGESxxx is now = <package><program>”. I also see the correct entry appearing in the “smsts.log”.
However, when I look in “execmgr.log” I don’t see the Policy arriving for the application despite the Policies arriving for applications either side of the problem app.
The most probably cause is that the Program isn’t enabled to be installed from your Task Sequence. To check:
The other thing to check is that the Program name in the MDT database matches the Program name in ConfigMgr EXACTLY including the case.
In this example the Program name in ConfigMgr was defined as “Install” whereas in MDT it was defined as “INSTALL”.
Looking in "BDD.log" it showed the line:
Property PACKAGES031 is now = FAQ00291:INSTALL
However, there was no trace of the Client receiving the Policy and running the Package in "execmgr.log"
Changing the Program name in the MDT database to match the Program name in ConfigMgr and rebuilding the machine resulted in the Client receiving the Policy and installing the Package.
TIP: When entering Program names in MDT I always right-click on the Program and select “Properties”. Then I copy and paste the Program name from ConfigMgr into the MDT database to avoid issues with typos, case, etc.
Open the "BDD.log" and do a search for “distribution share” which should display a line similar to:
SMS distribution Share = <fqdn_of_dp>
for example:
SMS distribution Share = CM072NDARY.FAQShop.COM
Other useful lines in this part of the log (just above) are:
After months of planning I'm delighted to tell you all that our very good friend Wally Mead is coming back to the UK on the 4th November when he'll be spending the day with us giving us the lowdown on ConfigMgr 2012.
So sign up for this free event which we're expecting to fill up fast.
To register goto here.
The Agenda for the day is:
9.30 - Registration
10.00 - Configuration Manager 2012 Overview and What’s new since beta 2
Configuration Manager 2012 is close to being released as a product. This session will describe (and demonstrate) some of the new features from Configuration Manager 2007, as well as some of the changes implemented from the beta 2 version you may have played with.
12.00 - Lunch
13.00 - Migration to Configuration Manager 2012
With the impending release of Configuration Manager 2012, you need to know how to move from your current Configuration Manager 2007 environment to the new Configuration Manager 2012 product. This session will demonstrate the migration process and what you can do to prepare for your own migration.
14.00 - Overview of the Configuration Manager 2012 Application model
Configuration Manager 2012 software distribution takes a large leap in functionality with the new application model. This session will discuss the benefits of application management over software distribution packages, and how to use the new application model for application management.
15.00 - Break
15.30 - Endpoint Protection in Configuration Manager 2012
Microsoft Forefront Endpoint Protection is now integrated into Configuration Manager 2012. This session will show you how to implement FEP 2012 into Configuration Manager 2012.
16.30 - Q&A
17.00 - End
I’m trying to build a machine. I insert my boot media. The machine boots and into PE and the Task Sequence Wizard runs. I click “Next >” on the “Welcome to the Task Sequence Wizard” screen.
However, on the “Select a Task Sequence” screen I’m only seeing one Task Sequence as being available despite there being several that should be available.
Check that the Task Sequence is Advertised to the relevant Collections. As well as Advertising your Task Sequence to the “All Unknown Computers” Collection you may want to Advertise Task Sequences to other Collections.
For example the first time you build a machine that isn’t in the ConfigMgr database you’ll see all of the Task Sequences advertised to the “All Unknown Computers” Collection on the “Select a Task Sequence” screen.
If you then try to rebuild the machine without deleting it from the relevant OS Collection that relates to the OS on the machine (for example “All Windows XP Systems”), first, you will only see the Task Sequences advertised to the relvant OS Collection already on the machine (in this case the “All Windows XP Systems” Collection), on the “Select a Task Sequence” screen.
In this case as a result of different Task Sequences being advertised to the “All Windows XP Systems” Collection than the “All Unknown Computers” Collection, only those Advertised to the “All Windows XP Systems” Collection were displayed as the machine had been built as XP.