open the SCCM administrator console and expand the site Management/site name/site settings, then select the Client Agents as below:
Double click on hardware Inventory client Agent on the right side and verify that it is enabled. Set the inventory schedule to 1 day (This is a LAB after all, in production you might want to use something less intensive, the default is 7 days). Click ok to close.
For the Software Inventory agent, verify the schedule is set to 7 days.
Click on the inventory collection tab, and delete the default scan listed.
Click on the yellow star and add files of type *.exe
then click on Set beside location, select Variable or Path name and enter %ProgramFiles%\ as the program path location so that it only scans that area for EXE files, Make sure to remove the tick from the windows directory
Next you can enable the Advertised programs client agent , and under the General tab, verify that Enable software distribution to clients is enabled and select New Program notification icon opens Add or Remove Programs as per below screenshot.
Note: In the R2 release of ConfigMgr you will have an additional choice called Allow virtual application package advertisement
Now click on the notification tab and set it accordingly
Next we will configure the Computer Client Agent properties,
Failure to configure this correctly or failure to configure it will lead to a failure in Operating system deployment with problems such as this one
for Network Access Account we need to enter an account to be used by Configuration Manager 2007 client computers to communicate with network resources. We can use the SMSread account we created earlier (in Step 3 of this guide).
Note: Be careful about what account you use as the Network Access Account, you should specify an account that has the minimum rights required, typically just enough to connect to your distribution point shares. It should never have domain admin rights. To see why, read this post.
fill in the text you want displayed to your users in the Customization tab
leave the reminders tab as it is and then set our BITS settings like this, if you don't want any BITS throttling enabled, then select Not Configured. Also worth checking if you have any BITS Group Policies enabled as Group Policies will override any throttling settings you define here. Check with your AD Network Team responsible for GPO's.
click apply and ok.
Set our Desired Configuration Management Agent schedule to 1 day
Let's leave Mobile device client agent settings as they are for now, and for Remote Tools client agent, set it as follows
add some permitted viewers (blank by default)
set your remote assistance settings to full control for both solicited and unsolicited remote assistance
We will leave Network Access Protection, Software Metering and Software updates Client agent as they are for now.
This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1 you must then do the additional configuration outlined in Part 2.
Step 1. Configure Client Agents
open the SCCM administrator console and expand the site Management/site name/site settings, then select the Client Agents as below:
Double click on hardware Inventory client Agent on the right side and verify that it is enabled. Set the inventory schedule to 1 day (This is a LAB after all, in production you might want to use something less intensive, the default is 7 days). Click ok to close.
For the Software Inventory agent, verify the schedule is set to 7 days.
Click on the inventory collection tab, and delete the default scan listed.
Click on the yellow star and add files of type *.exe
then click on Set beside location, select Variable or Path name and enter %ProgramFiles%\ as the program path location so that it only scans that area for EXE files, Make sure to remove the tick from the windows directory
Next you can enable the Advertised programs client agent , and under the General tab, verify that Enable software distribution to clients is enabled and select New Program notification icon opens Add or Remove Programs as per below screenshot.
Note: In the R2 release of ConfigMgr you will have an additional choice called Allow virtual application package advertisement
Now click on the notification tab and set it accordingly
Next we will configure the Computer Client Agent properties,
Failure to configure this correctly or failure to configure it will lead to a failure in Operating system deployment with problems such as this one
for Network Access Account we need to enter an account to be used by Configuration Manager 2007 client computers to communicate with network resources. We can use the SMSread account we created earlier (in Step 3 of this guide).
Note: Be careful about what account you use as the Network Access Account, you should specify an account that has the minimum rights required, typically just enough to connect to your distribution point shares. It should never have domain admin rights. To see why, read this post.
fill in the text you want displayed to your users in the Customization tab
leave the reminders tab as it is and then set our BITS settings like this, if you don't want any BITS throttling enabled, then select Not Configured. Also worth checking if you have any BITS Group Policies enabled as Group Policies will override any throttling settings you define here. Check with your AD Network Team responsible for GPO's.
click apply and ok.
Set our Desired Configuration Management Agent schedule to 1 day
Let's leave Mobile device client agent settings as they are for now, and for Remote Tools client agent, set it as follows
add some permitted viewers (blank by default)
set your remote assistance settings to full control for both solicited and unsolicited remote assistance
We will leave Network Access Protection, Software Metering and Software updates Client agent as they are for now.
Share this post
Link to post
Share on other sites