Use Full SQL Tables / Views

UseFull SQL Tables/ Views	Description / Use
v_Add_Remove_Programs
v_Advertisement
v_AdvertisementInfo
v_ClientCollectionMembers
v_Collection
v_Collection
v_ConfigurationItems
v_DistributionPoint
v_DistributionPointGroup
v_GS_ADD_REMOVE_PROGRAMS
v_GS_ADD_REMOVE_PROGRAMS_64
v_GS_COMPUTER_SYSTEM
v_GS_DISK
v_GS_Memory_Details0
v_GS_OPERATING_SYSTEM
v_GS_PATCHSTATE
v_GS_SERVICE
v_GS_SoftwareProduct
v_GS_SYSTEM
v_GS_WORKSTATION_STATUS
v_GS_X86_PC_MEMORY
v_OS_Details
v_Package
v_PackageStatus
v_Program
v_Query
v_R_System
v_R_User
v_R_UserGroup
v_RA_System_IPAddresses
v_RA_System_IPSubnets
v_RA_System_IPXAddresses
v_RA_System_MACAddresses
v_RA_System_SMSAssignedSites
v_RA_System_SMSInstalledSites
v_RA_System_SystemContainerName
v_RA_System_SystemGroupName
v_RA_System_SystemOUName
v_RA_System_SystemRoles
v_Report
v_Site
v_SiteBoundary_ADSite
v_SiteBoundary_IPSubnet
v_StateNames
v_UpdateBundles
v_UpdateListStatus_Live
v_UpdatePrograms

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

 

Windows 2008 IIS Common Issue on MP : Make sure you need to meet this settings on your windows 2008 server

You must know these collections as handy : Collections End to End

1.Client all system collection

2.Non client systems

3.Inactive systems

4.Obsolete system

5.Duplicate client Yes or No

6. Last hardware inventory 14 days

7.Last software inventory 14 days

8.Last Data discovery cycle.

9. XYZ package, XYZ Advertisement success systems’ collection

10. XYZ package, XYZ Advertisement Failed systems’ collection

11.XYZ subnet collection system

12.Add XYZ system’s to a collection of Existing

13. All SMS server system collection

14. All windows server, workstation,DP,BDP collection

15. All system’s with AD site based

16. Collection limiting to sub collection, linking

17.System’s are in “A” collection But not in “B” Collection & Vice versa

18. In collection “XYZ” Software installed system

19. In collection “XYZ” File inventory(s\w inventory based) installed system

20. In collection “XYZ” file specific method(H\w inventory based) system

21.XYZ patch Installed & Not Installed system

22. All windows update Agent version 7.6 below

23.XYZ user/group collection

SCCM Index : End- End

SCCM Index from windows noob

 

http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/

Good Posting for Multicasting for OSD : End to End

you can find here http://tinyurl.com/289ho4y

Multicasting is a new feature of R2 in SCCM and is a welcome addition to the OSD feature.  Multicast allows for image deployment with a much reduced network load.  If, for example, you are deploying a 500 MB image to 20 workstations that have just arrived from the OEM then with normal OSD imaging you would see network traffic equal to around 10 Gig!  Using multicasting would result in a significant decrease in network utilization.  Depending on the configuration, as little as about 500 MB of traffic required to deploy to all 20 machines!  This is the same amount of network traffic you would consume deploying to just a single imaging system using typical OSD imaging before multicast!

How do you setup multicast?  Let's walk through the configuration that is required step by step.

First, we need to enable multicasting.  Multicast requires a distribution point and the 'transport server'  component of WDS installed on a Windows 2008 server.  From there select the properties of the distribution point site system role and make sure the option for BITS, HTTP and HTTPS transfer is selected as shown

Note the new multicast tab that is added when R2 is installed.  Select the multicast tab and enable multicasting.

There are two options when using multicast - autocast and scheduled multicast. 

To enable autocast just select to enable multicast.  In this configuration the multicast session starts as soon as the first machine powers up and requests the image.  As additional machines are also booted up for imaging they will 'join' the current multicast session already in progress and consume the remainder of the stream.  When the stream ends it will start again and the systems that joined late will consume the parts they missed.  While autocasting isn't as efficient as scheduled multicast it is still significantly more efficient that standard OSD image delivery.

Scheduled multicast allows for more control of the multicast session.  Here you choose either a time delay before starting the multicast session or a minimum number of clients that must join the session before it starts.  The multicast session will start whenever either of the two requirements are met.  The idea here is to allow the administrator time to get all of the systems started and ready and then all systems can load the image simultaneously - providing the best usage of network   resources. Scheduled multicast is enabled by selecting the 'enable scheduled multicast' check box.

There are other configuration options on this screen but no extra configuration is required unless by your network.  The 'out of the box' settings work fine for most environments.

In addition, while DHCP and Windows 2008 based WDS (transport component as noted earlier - the PXE boot piece does not need to be on the same server) are needed, there is no special configuration requirement for either to make use of multicasting.

The next step is to configure the image package to be deployed by multicast.  In properties of the imported image, select the 'distribution settings' tab as shown

Select the option to allow the package to be deployed by multicast and optionally select the other two options.  In my testing I tried to select to only allow the image to be transferred via multicast but this didn't seem to work.  When I disabled multicast the image would still deploy, even with this option set.

in addition to enabling multicast for the image, you can also enable multicast on any package that is part of the image deployment.  On each package select properties and then select the 'distribution settings' tab.  the same options are available here as were on the image package as shown

As shown on both the image and the package, multicast is something that takes place in Windows PE only.  So, setting these options per package will not result in the package being delivered via multicast through normal software distribution.

Finally, enable the task sequence advertisement to deliver the image via multicast.  On the properties of the advertisement select the 'distribution points' tab as shown.

To enable multicast MAKE SURE you have selected to 'download content locally when needed by running task sequence'.  This requirement isn't documented and I spent hours trying to understand why my multicast sessions weren't starting up before realizing this setting was required.

Thats it - we are now ready to go for delivering images via multicast.  Let's walk through a couple of scenarios using autocast and scheduled multicast.  In our scenarios we will use PXE booted systems but multicast also works fine when booting from media - the experience is just slightly different when in Windows PE.

Autocast - single machine
To test multicast generally you will use a single machine.  So, what is your indication that multicast is actually working?  When the image begins to deploy you will see that a multicast session is requested, the image is downloaded locally via multicast and then reassembled as shown in the following three screenshots.

Autocast - two machines
As mentioned, in autocast the first requesting machine will start the multicast as shown above.  Any subsequent machines that boot up during the existing multicast session will join in progress and then loop back to the start and request the initial bits again.  The screenshots below show two sysems - the one on the left was started ahead of the one on the right but both are downloading the same image.  The one on the right started mid-stream.

After downloading the image the one on the left proceeds to extract while the one on the right finishes up getting the image. 

Scheduled multicast works similarly except here the multicast session will not start until either time has expired or the minimum number of machines have joined the multicast session.  The screenshot below shows a system waiting for either more systems to join or the timeout to expire.

So, while this is all going on - what is happening in the background to make this all work?  The SMSTS log varies slightly in each scenario but the core details are the same.  The SMSTS log section below is from a machine participating in an autocast multicast session.

In the log snip below we see the imaging system flag the multicast enabled distribution point that it wants to use for the multicast session, construct details for the multicast session request and then send the request to the multicast point

Continuing in the log we see the request information submitted to the multicast point followed by a reply with information the imaging system needs to join the multicast session.  Once we get the proper information back from the multicast point we then request and establish the multicast session

Next we see the response from the multicast server, the session get setup and the download begin

Once downloaded we begin to reconstruct the wim file and start applying the image.

When initially setting up the multicast session we say reference to sending information to the multicast point.  If we look in the mcsisapi log we see the request received, processed and the resulting reply sent back to the imaging agent as shown

There is certainly more 'behind the scenes' detail that takes place but this give a good picture, end to end, of how to configure, use and understand the process of using multicasting in R2.

Good website for beginners on Windows Basics

http://www.comptechdoc.org/os/windows/win2k/index.html

People can go through with the left side list from 1 to 75

Installation & Configuration of SCCM2007 Secondary Site

1.     Add the Configuration Manager Secondary Site Server Computer account to the Group “SCCM-GROUP”. As mentioned in my previous article this group must be added on to the System Management Container Security tab with Full permissions in active directory users and computers snap in as shown below.

2.     Add the computer account of Configuration Manager Secondary site server to the Local Group “SMS_SiteToSiteConnection_INC” which is present on the primary Site server.

Procedure:

Logon to primary Site Server- Open Computer management drill down to Local Users and Groups, Select groups and in that we will find a Local Group named as “SMS_SiteToSiteConnection_INC” as shown below. Go to the properties page and add secondary site server computer account.

3.     Create a Sender Address with the Secondary Site Code and Primary Site Information.

Procedure:

Open SCCM2007 Primary Site Server management Console, drill down to Site Management-Site Code- Site Settings- Addresses.

Right Click on Addresses and create a new Standard Sender Address

On the new Standard Sender Address Wizard, enter the Destination Site Code that is the new site code which we will give at the time of Secondary Site server installation. In our case we will give INS.

Give the Site Server name that is the Secondary Site Server Name.

If you leave the Site address account empty, the sender will use Primary Site Computer account to establish communication between both the sites (Primary and Secondary). If you leave the default, Primary site computer account must have full permissions on the secondary site server.

We can also set a windows user account that is having full admin privileges on both the site servers.

In our case we will leave as it is to use the Primary site Computer account.

In our case we selected open from Sunday to Saturday and click next

Leave the defaults and click Finish, you can also modify these settings based on your organization needs.

Once done you will see the newly created connector as shown below.

4.     Check the remote installation permissions of the account with which we are installing SCCM2007.

As discussed previously, we are using the Site server system account to establish communication between 2 sites, make sure we add the SCCM-Group into the Local Administrators group on the Configuration Manager Secondary Site Server.

To verify these

Log onto the Secondary site server and add the SCCM-GROUP account in the Local Administrators group of SCCM2007 Secondary site server.

5.     The SCCM2007 Primary site server Computer account must have full admin privileges on the Secondary Site Server computer account.

6.     The Service account with which we are installing secondary site server must have local admin privileges on the Secondary Site Computer account.

7.     Install IIS 6.0 (IIS is used for Management Point and Fallback Status Point)

Installing secondary site is two methods one from SCCM Console and second one from direct media from secondary site. we will run with the second option.

 

On the installation Prerequisite Check windows select Secondary site and click ok

click OK

 

Click ok, and

Initiate the Configuration Manager 2007 installation

Click next on the available setup options page

 

 

Accept the License agreement and click next

 

 

On the site type windows select Secondary site and click next

 

Provide the installation directory for binary files and click next

On the Site Settings Windows Insert the site code which we entered at  the time of Sender creation and provide the site name

In our case site code is INS and Site Name is MacroALLY Secondary Site Server

 

On the Parent Site Settings window, enter the Primary site code, which are INC and the Parent Site Server Name. Click next to proceed

 

On the Update Prerequisite Components page leave the defaults and click next

On the Updated Prerequisites path, enter the path to the folder were SCCM will download the updates and put it. Click next

On the settings summary page review the settings, if any changes go back to modify or proceed further with installation by clicking next

Setup will evaluate your system and cross checks all the prerequisites once more, if the status is green proceed further by clicking Begin install.

Setup starts installing the Configuration Manager Secondary site server

Click Finish and restart the server

open the console  now after restart

And the Sender will be updated with the necessary information as shown below

 

Vise Versa in the Secondary site settings-Address, you will also see a sender address created for Primary server as shown below

Configuration Manager Secondary Site is installed Secondary Site Information is updated in the System management Container in AD which is shown below

How confirm that Secondary site is working /Primary to secondary communication is fine:

Verify the Log Files to find out weather Secondary site is communicating with primary server properly.

Log files to monitor

ConfigMgrSetup.Log : Located on the root of system drive (Secondary site server )

Sender.log: Located on the Secondary site server installation directory (c:\Program Files\Microsoft Configuration Manager\Logs\Sender. Log) used to track weather the site is sending site information to the primary parent site.

After ensuring there are no communication problems from the above 2 logs, go ahead to check the despoiler.log on the primary site server to ensure it has received the secondary site information and is processing the secondary site information.

Despoole.log: located on the Primary site server (c:\Program Files\Microsoft Configuration Manager\ Logs\Despool.log)

Hman.log: Logs actions related to the hierarchy structure of the sites, located on the primary server (c:\Program Files\Microsoft Configuration Manager\ Logs\HMan.log).

Sitecomp.log: Logs information related to secondary site information publishing to Active Directory along with the primary site information, Located on the primary Site Server (c:\Program Files\Microsoft Configuration Manager\ Logs\SiteComp.log)

With this you are done with Secondary site Server Installation.

 

Day to Day Operations SCCM / ConfigMgr 2007 Reports

I recommend below ConfigMgr Reports to be familiar and these might be useful in day to day operations

 

Asset Intelligence:-

License 03A - Count of licenses by license status
Hardware 07A - USB devices by manufacturer

Software 02C - Software by Category and Family

Software 01A - Summary of installed software in a specific collection

This report provides a summary of installed software ordered by the number of instances found from inventory.

Desired Configuration Management – Compliance

Summary compliance for a collection by computer

Hardware

Count physical disk configurations

Computers with low free disk space (less than specified MB free)

Computers with low free disk space (less than specified % free)

Count memory configurations

Computers with low memory (less than or equal to specified MB)

Computers with a specific amount of memory

Memory information for a specific computer

Network

Count IP addresses by subnet

IP - Information for a specific computer

NAP

List of NAP-capable and NAP-upgradable computers

List of Network Access Protection policies

Operating System

Windows Server computers

Computers with a specific operating system and service pack

Computers with a specific operating system

Count operating systems and service packs

Count operating system versions

Services - Computers running a specific service

SMS/SCCM Client

Count SMS client versions

Servers with no client Installed

Client Deployment Failure Report

Client Deployment Success Report

Client Deployment Status Details

Client Assignment Failure Details

Count clients assigned and installed for each site

Computers with a specific SMS client version

Count clients for each site

Computers with duplicate MAC addresses

Computers that may share the same SMS Unique ID

Clients that have not reported recently (Collection)

& Clients that have not reported recently (in a specified number of days)

Site TO Site Reports:

Sites by hierarchy with time of last site status update

Computers in a specific site
Status messages for a branch distribution point
Site system roles and servers for a specific site

Software Inventory

Software registered in Add Remove Programs for a specific collection
Computers with specific software registered in Add Remove Programs
Computers with a specific product
Count of all instances of software registered with Add or Remove Programs
Computers with a specific product name and version
Count computers with a specific filename

Software Distribution:-

Status of a specific advertisement
All advertisements for a specific collection
All advertisements
Distribution status of a specific package
All packages on a specific distribution point
All distribution points
All active package distributions

Patching:-

Compliance 1 - Overall Compliance
Compliance 4 - Deployment (per update)
Compliance 3 - Update list (per update)
Compliance 4 - Deployment (per update)
Management 1 - Updates required but not deployed
Management 2 - Updates in a deployment
States 1 - Enforcement states for a deployment
States 2 - Evaluation states for a deployment
Scan 1 - Last scan states by collection
Scan 2 - Last scan states by site

Auditing

All audit messages for a specific user
All Task Sequence Advertisements
Deployment status of all task sequence advertisements
Progress of a running task sequence
Progress of OS deployment task sequences
Status of all unknown computers
Computers for a specific user name
WOL

All sites that are enabled for Wake On LAN
All computers targeted for Wake On LAN activity
All objects pending wake-up activitiy

Customized reports:

All computers based on AD site:

SELECT DISTINCT SYS.Name0,SYS.AD_Site_Name0,

SYS.User_Domain0,SYS.User_Name0,

SYS.Operating_System_Name_and0

FROM v_R_System SYS

WHERE SYS.AD_Site_Name0 LIKE @variable

ORDER BY SYS.AD_Site_Name0, SYS.Name0

--Prompt Query

SELECT DISTINCT SYS.Name0,SYS.AD_Site_Name0,

SYS.User_Domain0,SYS.User_Name0,

SYS.Operating_System_Name_and0

FROM v_R_System SYS

WHERE SYS.AD_Site_Name0 LIKE @variable

ORDER BY SYS.AD_Site_Name0, SYS.Name0

Lins with reports =è Hardware - General - Computer information for a specific computer; below is the screenshot

Also I prefer one to have below custom reports

Compliance - Detailed list - specific collection

Computer Information - specific collection

Computer information for a collection of computers

Computers with specific software

Distribution Points in All DP Group

Missing Patches

Network settings

Network settings for a specific collection

Servers with SCCM Client version
All Workstation Patching compliance reports
All Desktops & Laptops model & make reports