I was recently troubleshooting a problem with the Orchestrator 2012 Beta web service, and got the error message “Value does not fall within the expected range” when trying to start the web service IIS website from the IIS console.
Recently, someone posted a PowerShell script, which is intended as a replacement for the SendSched.vbs included in the Microsoft System Center Configuration Manager 2007 Toolkit v2.
I took the liberty of cleaning the code up a little bit, and simplifying it to be more PowerShell friendly. Enjoy.
# # Script Name: SendSched_PowerShell_Version.ps1 # Purpose: Serves as a replacement for the sendsched.vbs script included in the Microsoft System Center # Configuration Manager 2007 toolkit -- asynchronously invokes SCCM client tasks # # Created By Kaido Jarvemets Http://Depsharee.blogspot.com # Configuration Manager MVP # 25.07.2011 # Updated by: Trevor Sullivan # Email: pcgeek86@gmail.com # Blog: http://trevorsullivan.net # Date: 2011-07-25 # # Changelog: # * Replaced Get-ScheduleID function with a hashtable # * Removed custom ping function in favor of using Test-Connection # * Replaced default computer name with a period, which represents localhost function Invoke-SCCMSchedule { [CmdletBinding()] Param( [String]$ComputerName = ".", [Parameter(Mandatory = $true)] [string]$ScheduleID ) $ScheduleIds = @{ HardwareInventory = "{00000000-0000-0000-0000-000000000001}"; # Hardware Inventory Collection Task SoftwareInventory = "{00000000-0000-0000-0000-000000000002}"; # Software Inventory Collection Task HeartbeatDiscovery = "{00000000-0000-0000-0000-000000000003}"; # Heartbeat Discovery Cycle SoftwareInventoryFileCollection = "{00000000-0000-0000-0000-000000000010}"; # Software Inventory File Collection Task RequestMachinePolicy = "{00000000-0000-0000-0000-000000000021}"; # Request Machine Policy Assignments EvaluateMachinePolicy = "{00000000-0000-0000-0000-000000000022}"; # Evaluate Machine Policy Assignments RefreshDefaultMp = "{00000000-0000-0000-0000-000000000023}"; # Refresh Default MP Task RefreshLocationServices = "{00000000-0000-0000-0000-000000000024}"; # Refresh Location Services Task LocationServicesCleanup = "{00000000-0000-0000-0000-000000000025}"; # Location Services Cleanup Task SoftwareMeteringReport = "{00000000-0000-0000-0000-000000000031}"; # Software Metering Report Cycle SourceUpdate = "{00000000-0000-0000-0000-000000000032}"; # Source Update Manage Update Cycle PolicyAgentCleanup = "{00000000-0000-0000-0000-000000000040}"; # Policy Agent Cleanup Cycle RequestMachinePolicy2 = "{00000000-0000-0000-0000-000000000042}"; # Request Machine Policy Assignments CertificateMaintenance = "{00000000-0000-0000-0000-000000000051}"; # Certificate Maintenance Cycle PeerDistributionPointStatus = "{00000000-0000-0000-0000-000000000061}"; # Peer Distribution Point Status Task PeerDistributionPointProvisioning = "{00000000-0000-0000-0000-000000000062}"; # Peer Distribution Point Provisioning Status Task ComplianceIntervalEnforcement = "{00000000-0000-0000-0000-000000000071}"; # Compliance Interval Enforcement SoftwareUpdatesAgentAssignmentEvaluation = "{00000000-0000-0000-0000-000000000108}"; # Software Updates Agent Assignment Evaluation Cycle UploadStateMessage = "{00000000-0000-0000-0000-000000000111}"; # Send Unsent State Messages StateMessageManager = "{00000000-0000-0000-0000-000000000112}"; # State Message Manager Task SoftwareUpdatesScan = "{00000000-0000-0000-0000-000000000113}"; # Force Update Scan AMTProvisionCycle = "{00000000-0000-0000-0000-000000000120}"; # AMT Provision Cycle } if(Test-Connection -Computer $ComputerName) { Try { $SmsClient = [wmiclass]"\\$ComputerName\root\ccm`:SMS_Client" $SmsClient.TriggerSchedule($ScheduleIds.$ScheduleID) } Catch { Write-Host "Trigger Schedule Method failed" -ForegroundColor RED } } else { Write-Host "Computer may be offline or please check Windows Firewall settings" -ForegroundColor Red } }# End of Function Invoke-SCCMSchedule
If you’ve worked with Configuration Manager 2007 for very long, you probably know that clients pending reboots can cause you quite a headache. Determining whether or not a client needs a reboot can be a challenging task, and most folks used desired configuration management rules to detect it.
Well, I’m happy to announce that there’s a new method of figuring out whether or not a SCCM client requires a reboot! There’s a new WMI namespace called rootccmClientSDK, and within it is a WMI class called CCM_ClientUtilities, which has a static method called DetermineIfRebootPending() – the method does not take any input parameters, however it spits out several [out] parameters when it is called.
Update: I have resolved the problem by using msizap.exe (a utility included in the Windows SDK) to kill the Orchestrator Management Service from the MSI database, and then reinstalled just that component (by running microsoft.systemcenter.orchestrator.managementserver.msi)
I’ve been repeatedly having trouble installing System Center Orchestrator 2012 on a Windows Server 2008 R2 SP1 VMware guest. My installation log is below. It seems that it is having a problem starting the service named: OpalisActionService.
Updated on 2011-08-03
Here are some links to interesting blogs, software, and other random tidbits!
When you use the New-WebServiceProxy class, you probably have noticed that PowerShell dynamically generates some really ugly type names. For example, if we get a reference to the Bing web service (you’ll need to get an API key first):
$BingSearch = New-WebServiceProxy -Class BingSearch -Uri "http://api.search.live.net/search.wsdl?AppID=$ApiKey"
… and examine the types contained within it:
$BingSearch.GetType().Assembly.GetExportedTypes() | select FullName
… you’ll notice some ridiculously long type names based on your API key, such as:
Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxyXXXXXXXXXXXXXXXXXXXXXXXXXXX.SearchRequest
Advertisements aren’t quite what you think they are. At least, that’s probably the case if you’re talking in context of Microsoft System Center Configuration Manager (SCCM / ConfigMgr). At first glance you might see “deleting advertisements” and exclaim: “YES! Please do!” The difference here is that advertisements in SCCM are not product or service advertisements, but rather proclamations of the availability of software to a computer system. If you’re reading this, you most likely already knew that, but if not, then … now you do.
Back in the days of the SCCM 2007 console, there was a single Software Distribution –> Advertisements node which contained advertisements for both standard software distribution and operating system deployment (OSD) task sequences. This worked pretty well, but it was a little confusing since the operating system deployment node was entirely separate from software distribution. Hierarchically, it just didn’t make sense.
In previous versions of Microsoft System Center Configuration Manager (ConfigMgr / SCCM), a common task for administrators, engineers, and consultants, was to extend the hardware inventory configuration. These inventory extensions were written in Managed Object Format (MOF) and allowed the SCCM client agents to report back a wider array of information to the central site database for reporting purposes, collection building, and other management tasks. Making changes to the configuration could be a tedious task, as MOF is not very forgiving, and rather quite strict, in its syntax.
In Microsoft Systems Management Server 2003 (SMS 2003), each time a configuration change was made, it was necessary to deploy the updated MOF file to the SMS clients — this made ensuring hardware inventory consistency across all clients a challenging task. In SCCM, Microsoft included changes to these MOF files (SMS_DEF.mof and Configuration.mof) as part of the machine policy refresh task, which is a client-side polling mechanism for configuration changes.
In SCCM 2012 Beta 2, Microsoft is taking it a step further and has eliminated the SMS_DEF.mof altogether, left the configuration.mof behind by itself, and stuck the WMI inventory configuration in … WMI. What is WMI? WMI stands for Windows Management Instrumentation, a service built into the Windows Operating System since Windows XP (and Windows 2000 Service Pack 4, I think). It provides a standard method of exposing hardware and software level system information to applications, such as storage, processor, memory, running processes, installed software, and other application configuration data. SCCM is built on top of this technology, and often makes developing software and scripts around the product much easier than it otherwise might be.
For the remainder of this article, we’re going to look at specifically how to extend hardware inventory in SCCM 2012 programmatically using Windows PowerShell with the SCCM WMI provider.
If you’re using System Center Configuration Manager (SCCM / ConfigMgr) 2007, you may want to discover how many SCCM sites you have from Active Directory. Of course, this assumes that you have Active Directory publishing enabled on your primary sites. When enabled, SCCM automatically places site information underneath the CN=System Management,CN=System,DN=mydomain,DC=com container.