SELECT sys.Name0 'Name', v_R_System.Operating_System_Name_and0 'Operating System'FROM v_ServiceWindow AS swINNER JOIN v_FullCollectionMembership AS fcm ON sw.CollectionID = fcm.CollectionIDRIGHT JOIN v_R_System AS sys ON fcm.ResourceID = sys.ResourceIDWHERE sw.Name is NULL AND sys.Client0 = 1ORDER BY sys.Name0
How to find clients with no Maintenance Window defined
Use the following query in ConfigMgr Report to find the list of clients that do not have any Maintenance Window defined.
SMS_SITE_BACKUP thread don't get restarted after successful backup
If you notice an intermittent issue whereby the component threads don't get restarted after a backup, in service manager they show as starting.
Resolution: Apply the hotfix: http://support.microsoft.com/kb/982399
Resolution: Apply the hotfix: http://support.microsoft.com/kb/982399
Where can Site Repair Wizard log be found.
When the Site Repair Wizard is run, check your repairwizard.log, it logs site repair information, which is written to the RepairWizard.log log file. This file is created in the <Configuration Manager 2007 program files>\AdminUI\AdminUILog directory when the Site Repair Wizard is started.
Hardware Inventory not being processed by SMS/ConfigMgr servers | Hardware Inventory not working
I noticed some systems mostly Windows 2000 Servers hardware inventory did not report back to SMS and their hardware inventory MIF files were being moved to \inboxes\dataldr.box\BADMIFS\ directory. This problem seem to get resolved by uninstalling and re-installing the SMS/ConfigMgr client, but this will reappear again after few days.
In the DataLDR.log the following error will be report for the effected clients.
File size exceeds defined maximum.
SMS creates a BadMifs directory only if a bad IDMIF or NOIDMIF is detected at your site server by the Inventory data loader. By default, the MIF file size is set to 5,000,000 bytes (4.7MB) that SMS collects from a client during its normal hardware inventory. If a MIF file exceeds the limit the MIF is rejected and placed into BADMIFs folder.
You can increase the maximum MIF file size value from the registry on your SMS/ConfigMgr Site Server by modifying the following registry key:
On a 32-bit server:
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size
On a 64-bit server:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS_INVENTORY_DATA_LOADER\Max MIF Size
However if you increase this value your disk space on the site server may grow considerably because of the larger the MIF file size and your resources may diminish because it takes longer for the Inventory Data Loader to parse and process them.
In the DataLDR.log the following error will be report for the effected clients.
File size exceeds defined maximum.
SMS creates a BadMifs directory only if a bad IDMIF or NOIDMIF is detected at your site server by the Inventory data loader. By default, the MIF file size is set to 5,000,000 bytes (4.7MB) that SMS collects from a client during its normal hardware inventory. If a MIF file exceeds the limit the MIF is rejected and placed into BADMIFs folder.
You can increase the maximum MIF file size value from the registry on your SMS/ConfigMgr Site Server by modifying the following registry key:
On a 32-bit server:
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size
On a 64-bit server:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS_INVENTORY_DATA_LOADER\Max MIF Size
However if you increase this value your disk space on the site server may grow considerably because of the larger the MIF file size and your resources may diminish because it takes longer for the Inventory Data Loader to parse and process them.
http://support.microsoft.com/kb/319167
http://support.microsoft.com/kb/198766
http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/fc9f5405-a476-4ee4-af71-4e74717c5fdd
"Approved" and "Targeted" in SCCM Reports
Today, I noticed an interesting thing in SCCM reports. If you use 'Targeted' column name in any SCCM report it always be displayed as 'Approved'.
If you run the follwoing report, insted of displaying the 'Targeted' column name it displays the column name as "Approved"
Select Name0 as Targeted from v_r_system.
If you run the follwoing report, insted of displaying the 'Targeted' column name it displays the column name as "Approved"
Select Name0 as Targeted from v_r_system.
How to run a program under Local System account
If you using sms/sccm then you may require to test a program under the LocalSystem accounts. Here is an easy procedure to run a program under Local System account.
How to run a program under LocalSystem account:
How to run a program under LocalSystem account:
- Download PSTools from here: http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
- open the command prompt using the following command using the psexec.exe
PSExec.exe -i -s -d cmd.exe
- In the command prompt window start any program that you want to run under Local System account.
Where can we find SCCM/SMS client logs
Client logs location:
- On 32-bit system, the client logs are located in the %WINDIR%\System32\CCM\Logs folder.
- On 64-bit system, the client logs are located in the %WINDIR%\SysWOW64\CCM\Logs
- On SMS/SCCM servers the client logs are located in the <INSTALLDRIVE>\SMS_CCM , here <INSTALLDRIVE> is the drive where sms/sccm servers is installed.
- On 32-bit system, the client installation log(ccmsetup.log,client.msi.log etc) are located in the %WINDIR%\System32\ccmsetup\ folder.
- On 64-bit system, the client installation logs(ccmsetup.log,client.msi.log etc) are located in the %WINDIR%