josharldt

The preferred method of sending a report to a manager is to save the report as either a PDF or Excel file, then email it to them. If your managers want the report regularly though, this can be a pain... I don't personally find that providing a link that runs a report is too difficult if you use the following steps: 1. Browse to your Report Manager URL in Internet Explorer. 2. On the Report Manager site, browse to the folder with the report you are wanting. 3. Click on the arrow to the right of the report and then click on Manage. 4. Click on Parameters to the left side of the page. 5. Make note of all of the variable names on the Parameters page. 6. Get the URL for the report and tack on each variable name to the end of the URL in the following format: &<Variable Name Here>=<Value Here> 7. Email the URL to your managers. They will now be able to run the report with the values that you preset whenever they click on the link.

I just realized that you are using IP Subnets as your boundaries. This is more than likely causing the problem that you are experiencing and definitely explains why it works when you set the AD Site as a boundary. It is recommended to use IP address ranges as boundaries in production environments...

By default, ConfigMgr 2007 runs an AD system discovery every 1 days at 12 AM. To see what schedule your site is set to, or to change the schedule, open the ConfigMgr console and go to Site Management\<Your Site>\Site Settings\Discovery Methods and double-click on Active Directory System Discovery and then click on the Polling Schedule tab. To change the polling schedule, click on the Schedule button. If the client is installed on systems that still reports Client=No and Approved=No, then the client is most likely unhealthy. Most client health problems are caused by WMI problems.

Like Niall said, it's different for every company... I have found that, for my organization, the following works well: 1. Create a Software Update Group for the updates that you will be deploying this month along with a Deployment Package. The naming convention should have the month and year so it's easy to keep track of. 2. Create a Software Update Group named All Software Updates and a Deployment Package with the same name. 3. Deploy the Software Update Group for the current month as a WOL enabled required deployment. 4. Once the current months updates have been successfully deployed. Move the current months patches to the All Software Updates group. 5. Delete the current months Software Update Group and Deployment package. 6. Deploy the All Software Updates group to All Systems as Available with WOL disabled. So, basically what we do is deploy the current months updates, then roll them up into another Software Update Group that is always set to Available just in case some machines missed the deployment. This way the users that missed the deployments can install them on their own leisure due to politics... I hope this gives you some ideas so that you can come up with a process that works well for your organization.

Do you have the Server Locator point installed? Once you have a Server Locator point, call the SMSSLP=<Server with Server Locator point here> switch when running ccmsetup.exe on the new clients.

Leave the key blank in the task sequence and add a step to your task sequence after OS Install that runs the following command line: SLMGR.VBS -ipk <Your MAK Here>

Check out this link: http://systemcentervnext.com/blogs/mmr/archive/2011/12/04/vbscript-to-create-a-sccm-advertisment-group-ad-quot-install-uninstall-quot-collections-quot-install-uninstall-quot-packages-programs-quot-install-uninstall-quot-with-depentprogram-deployment-in-dp-advertisements.aspx You might be able to modify that to do what you want it to.

1. Create a new collection. 2. On the Membership Rules page, enable "Update this collection on a schedule" and configure your schedule, and then enable "Dynamically add new resource" (if the option is available) 3. Click on the new Query Rule button and give the query a name, choose User Resource as the resource class, and then click on Edit Query Statement. 4. Click on the Criteria tab and then click on the Show Query Language button. 5. Type the following query into the Query Statement field: select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User where SMS_R_User.UserOUName = "<YOUR DOMAIN>/<YOUR OU>" Make sure to replace <YOUR DOMAIN> with the NetBIOS name of your domain and <YOUR OU> with the name of your OU. If that doesn't work, verify the name of the OU by right-clicking on the user in SCCM and looking at the value of the User Container Name[0] property. The value of User Container Name[0] should take the place of <YOUR DOMAIN>/<YOUR OU> in the query. Also, keep in mind that the Active Directory User Discovery plays a part in how often this collection will be updated, not just the collection update schedule.