While there were not really any sessions today, it was by no means slow. I had lunch with Russ and Todd (from the myITforum.com community), attended a few Hands-On Labs (HOL) this afternoon, and then the Welcome Reception this evening in the Expo hall.
Both of the HOLs I attended were presented by Wally Mead, SMS Program Manager. The first was Implementing Maintenance Windows for Software Distribution in System Center Configuration Manager 2007. A great new feature that allows you to set on a per-collection basis time frames in which advertisements can run. In other words, if you define a maintenance window on a collection any advertisement that is assigned to a member of that collection will only run inside of that time period. This just simplifies the common IT practice by defining the business policy so that your SMS-initiated changes are only applied during required times.
A few tidbits on maintenance windows:
Other random bits:
The next HOL was Implementing Branch Distribution Points in Configuration Manager 2007. Brand Distribution Points (BDP) were intended to allow a remote XP workstation (for example) to be made into a basic DP so that a managed server does not have to be deployed at a remote branch office. Since no code is installed on a BDP (unlike a standard DP) the site server does not need administrative rights on the target system. BITS must be enabled on the standard DP as the BDP downloads content from it using BITS. A site setting on the new Computer Client Agent allows you to tweak BITS throttling, which by default is enabled between 9AM and 5PM.
SCCM clients locate a DP via the following methods:
Methods #1 and #2 are flipped from how SMS 2003 clients function.
The following status messages appear for the Peer DP Agent component:- 11350 "content download started"- 11351 "content download succeeded"- 11369 "Package provisioned on share C:\SMSPKGC$\[pkgname]"
Typically "Run from distribution point" uses SMB and "Download and run" uses BITS, except with a BDP, which only does SMB because it does not use IIS.
BDP on XP does not extend the OS restriction on network connections; only 10 clients can connect simultaneously. Clients 11+ will show the package content as unavailable, go into a wait state, and retry per the normal process.