Trevor Sullivan

It is possible that 12 end users have already installed the software update, and therefore the SCCM client agent is reporting back that the update is already installed. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

It sounds like what's happening is the .exe is popping up an interactive prompt for more information. Your best bet is to go into the Package --> Program settings and temporarily enabling "Allow users to interact with this program." Then, re-execute the deployment and see what happens. Once you're finished testing and resolving the issue, you can go back and uncheck the box. Also, as a best practice, make sure you use any logging options provided by the installer executable. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Have you tried updating your boot images to WinPE 3.1 using the Windows AIK Supplement? http://blogs.technet.com/b/mniehaus/archive/2011/02/17/windows-aik-for-windows-7-sp1-released.aspx Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Is the client system on the same subnet as the SCCM server / WDS service? If so, remove DHCP options 66/67 -- it will broadcast out and get these options from the PXE service. Did you go into the WDS console and configure WDS after installing the Windows role? If so, remove and re-install WDS, and do not configure it. Don't even open the WDS console. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

I don't see anything glaringly wrong either -- I'm a bit confused why we're not seeing the Apply Operating System failure in the smsts.log however. Where did you pull this smsts.log from? If you pulled it from the c:\ drive somewhere, I think we're missing some stuff. Look for the log in x:\windows\temp\smstslog -- see if that has the error in it. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

If you have a custom attribute in Active Directory that correlates a user to a computer, you could certainly add that to your discovery configuration and build a query off of that. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You have to create a query-based collection that includes only Windows 7 systems. You can use the Operating System.Caption property to build your collection query. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Actually, Trend isn't causing it to say that it's the wrong version of SCCM. The "Property" table in the MSI database is simply defining those errors in case it needs to display them. Those "Property(S)" lines you pasted are simply references to the error text, not actually generating the errors themselves. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You will need to troubleshoot why your Active Directory System Group discovery is not working. According to the Technet documentation, the appropriate log file to check out is the adsysgrp.log on the SCCM primary site. http://technet.microsoft.com/en-us/library/bb694071.aspx Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

In theory yes, it's possible, but you'll probably have to deploy a script + MOF edit in order to achieve this. The script deployed to client workstations would need to identify the appropriate registry key under: HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\System\<PackageID>\<GUID> ... and write it to WMI somewhere. Then, you'd need to add the WMI class to your SMS_DEF.mof for reporting purposes. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Here's an article I wrote about how to extend hardware inventory in SCCM 2012 Beta 2 using PowerShell. http://trevorsullivan.net/2011/07/05/extreme-powershell-configmgr-extending-hardware-inventory/'>http://trevorsullivan.net/2011/07/05/extreme-powershell-configmgr-extending-hardware-inventory/ Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

On a 64-bit Windows SCCM client, the ccmsetup folder will be in c:\windows. Can you retrieve the ccmsetup.log and see if we can figure out what's going on? Is the 64-bit client in the same IP subnet as the 32-bit client you were testing with? Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Go into the IIS configuration on your secondary site and check to make sure that "Allow Hidden Files to be Listed" is "True." This will be under Server --> Sites --> Default Website --> WebDAV Authoring Rules --> WebDAV Settings. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello there, First of all, just for the sake of clarification, nothing is supposed to be configured in WDS after you install the PXE Service Point SCCM role. If you sort your SCCM site server Logs folder by modified date/time, are any logs getting changed when you initiate the installation of the PXE service point? Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello jpboyce, I'd start out by checking your IIS logs on both the secondary site and the primary site. That may give you some indication as to what's failing. Are you using the FQDN or NetBIOS name of the secondary site in the sender address? http://technet.microsoft.com/en-us/library/bb680457.aspx FWIW, I haven't had any issues running a central & child primary site both on Windows Server 2008 R2 systems. I realize this is a bit different from your setup, but it's actually more complicated since there's two primary sites in play. Just thought I'd throw that experience out there. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

I think this particular request is going to take some customization (scripting, etc.). You mentioned using an INSERT trigger ... I don't know SQL Server very well, however this sounds like a good idea. If it helps, since SCCM is based on Windows Management Instrumentation (WMI), you can also use the built-in WMI eventing model to respond to these events. You could fire off a PowerShell script in response to an event. Back in November 2010, I wrote a PowerShell module that assists with building these event models. This solution would be similar to your SQL trigger idea, only using WMI's event model instead -- to be honest, it will probably perform slightly less optimally than the SQL solution, but I doubt there would be any major performance issues with implementing it this way either. http://powerevents.codeplex.com Let me know if you would like help using it -- there's plenty of documentation and examples in there to start you off. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You have to wait for the inventory information to come back from clients before the report will run. The SQL view you are trying to query indeed does not exist until the following happens: 1) Clients pickup change in SMS_DEF.mof 2) Clients run a hardware inventory cycle 3) Client sends inventory report to SCCM site server 4) Site server processes client MIF file and imports into database (creates tables / views automatically if necessary). Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello, You'll probably need to extend your SMS_DEF.mof to include inventory of the root\cimv2:Win32_PageFileUsage WMI class. If a system does not have a page file, it should not have an instance of Win32_PageFileUsage. In this case, you'd probably want to RIGHT OUTER JOIN the table that holds and then filter (WHERE clause) for null values (systems that don't have any instances of Win32_PageFileUsage). I'm not a great SQL guy, but with a little fiddling, I'm sure this would work correctly Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello, Thanks for your inquiry. First off, almost anything is possible For your particular question, it depends on what your definition of "installed software" is. If you want, you can write a report that sorts ALL the inventoried items (from hardware inventory) in Add/Remove Programs, and you can filter for items installed on a daily basis. The query is simple, and would look something like the below query. This query returns software that was installed on the 1st day of "this" month. select [sys].[AD_Site_Name0] , [sys].[Name0] , [arp].[Publisher0] , [arp].[DisplayName0] , [arp].[installDate0] from [v_R_System] [sys] join [v_GS_ADD_REMOVE_PROGRAMS] [arp] on [sys].[ResourceID] = [arp].[ResourceID] where [arp].[installDate0] is not null and LEN([arp].[installDate0]) = 8 and CONVERT(int, SUBSTRING([arp].[installDate0], 5, 2)) = DATEPART(m, GETDATE()) and CONVERT(int, SUBSTRING([arp].[installDate0], 1, 4)) = DATEPART(YYYY, GETDATE()) and CONVERT(int, SUBSTRING([arp].[installDate0], 7, 2)) = 1 order by [arp].[installDate0] desc Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello, I assume you're talking about SCCM rather than SCOM? SCOM is for systems monitoring. Anyway, SCCM OSD won't automatically attempt to reinstall applications -- you'll have to define your application packages and add app install task sequence items to your task sequence. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

That means that SCCM clients have not scanned against that update's metadata yet. Do you have the software updates agent enabled? Is there a GPO in place that's overriding your SCCM software updates client agent settings? (this is bad)

Just use the standard software distribution feature in ConfigMgr to deploy a batch script. md c:\test xcopy *.* c:\test /E /Y Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

What tool are you using to import the computers into the collection? Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

I'd recommend deleting the existing driver out of the console, as well as on the filesystem. Then, download the latest driver directly from Intel, import it, assign it to your WinPE boot image, and perform an update on your boot images. Post back if this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Quite easy to do using Windows PowerShell and the WMI provider for SCCM: # Populate these variables $SccmServer = 'MySccmServer' $SccmSiteCode = 'LAB' $PackageID = 'LAB00023' $MyPkg = Get-WmiObject -ComputerName $SccmServer -Namespace root\sms\site_$SccmSiteCode -Class SMS_Package -Filter "PackageID = '$PackageID'" $MyPkg.RefreshPkgSource() Now, schedule this to execute in the Windows task scheduler, using an account that has access to the SCCM Provider. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86