Thursday, December 2, 2010

ALL Collections WQL and collection ID and Names in a Site

SELECT     TOP (100) PERCENT dbo.v_Collection.Name, dbo.v_Collection.CollectionID, dbo.v_CollectionRuleQuery.RuleName, dbo.v_CollectionRuleQuery.QueryID,
                      dbo.v_CollectionRuleQuery.LimitToCollectionID, dbo.v_CollectionRuleQuery.QueryExpression
FROM         dbo.v_Collection INNER JOIN
                      dbo.v_CollectionRuleQuery ON dbo.v_Collection.CollectionID = dbo.v_CollectionRuleQuery.CollectionID
ORDER BY dbo.v_Collection.Name, dbo.v_Collection.CollectionID

Tuesday, November 30, 2010

SMS 2003 Sourceforge Tools And Utilities

SMS/SCCM Peer2Peer AddOn
SMSTorrent is a Peer2Peer AddOn for SMS2003/SCCM2007 Clients. SMS/SCCM Clients are able to share the local Package cache with other Clients using the BitTorrent filesharing protocol.
SMS Site Settings tweak
SMSSettings provides a GUI to modify SMS2003 (Microsoft System Management Server 2003) Site Settings which are not accessible over the normal SMS Admin Interface.
Screen Lock
This Tool does lock the Screen, Mouse and Keyboard for a specified time.
SMS Client Center
Troubleshoot and manage SMS 2003 advanced clients
SMS 2003 Offline Hardware Inventory
Capture SMS2003 Hardware Inventory on Systems without Network connectivity or Systems without an SMS Agent installed. This Tool creates a DDR (DataDiscoveryRecord) and an IDMIF File for each scanned system.
Secure Autologon
Enable Windows Autologon without a cleartext password in the Registry. The password will be stored by the Local Security Authority (LSA).
SMS2003 Object Backup
Backup and restore a definable set of SMS 2003 Objects (Packages, Programs, Advertisements, Collections...). SMSObjBackup can also be used for Site Migration (Objects can be moved to another SMS Primary Site Server)
SMS 2003 Adv.Client local policy import
A command line tool to assign local software distribution policies to an SMS 2003 Advanced Client. The Software will be installed independent of collection memberships.
Manage the assigned Software Packages of a Microsoft SMS (SystemManagementServer) 2003 DistributionPoint
SMS 2003 Software Request Web Form
SMS 2003 Software Request Web Form with a simple Workflow (mail/web based).
SMS Collection Commander
Initiate SMS 2003 advanced client actions on a collection: Ping, WakeUp, HW/SW Inventory, ReRun Advertisements, Show logged on user, Download/Refresh Policy, Repair SMS Agents, Import Clients to the Collection...
SMS OSD Program Import
SMSOSDXML extends the SMS 2003 Admin Console to import OSD Program-Settings based on a XML File. SMS OSD automatically creates such XML Files (SMSDeploy.xml) for each OSD Program created in the Admin Console.
SMS Package Dependency Viewer
Show "Microsoft System Management Server 2003" Software Package dependencies in a TreeView.

Thursday, November 4, 2010

WMI delete

To delete a class

You can delete a class in the current namespace with Delete Class on the Windows Management Instrumentation Tester dialog box.

  1. Open the Windows Management Instrumentation Tester dialog box.
  2. In the Windows Management Instrumentation (WMI) Tester dialog box, click Connect.
  3. In the Namespace box, type the path to the namespace that you want to connect to.
    • To connect to the namespace where the Win32 provider classes reside, type:
  4. Click Connect.
  5. Click Delete Class.
  6. In the Get Class Name dialog box, type the name of the class you want to delete, and then click OK.
    A dialog box is displayed to warn you that the class might have derived classes or instances. This dialog box is displayed even if there are no derived classes or instances.
  7. If you are sure you want to delete the class, click Yes to delete the class.


  • Performing this task on the local computer does not require you to have administrative credentials. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.
  • Performing this task on a remote computer requires that you are a member of the Administrators group on the remote computer, or that you have been delegated the appropriate authority.
  • To open the Windows Management Instrumentation Tester dialog box, click Start, click Run, and then type WBEMTest.exe.

Wednesday, October 20, 2010

Tuesday, October 19, 2010

Use Full SQL Tables / Views

UseFull SQL Tables/ Views Description / Use

Monday, October 18, 2010

Download these next path ::


scom r2

service manager

Data Protection Manager


Saturday, October 16, 2010

SCCM R3 Provides

The following features are new to Configuration Manager 2007 R3.

  • Power Management: Provides a set of tools that enable the site administrator to configure standard Windows power settings across computers and monitor power consumption and computer activity.
  • Operating System Deployment Improvements: Provides pre-staging of boot images and Windows Imaging Format (.wim) files on new computers that enables the administrator to apply a task sequence to the device that can use the pre-staged media.
  • Dynamic Collection Evaluation: Enables you to rapidly evaluate a collection membership by adding only newly discovered resources.
  • Active Directory Delta Discovery: Performs an intermediate discovery cycle that adds only new resources to the Configuration Manager 2007 database.
  • Simplified Resource Management: Enables you to search for and add resources to a specified collection.
  • Desired Configuration Management: Enables you to create a collection of compliant or noncompliant computers in desired configuration management.
  • Higher Number of Supported Clients Per Hierarchy: Configuration Manager 2007 R3 supports up to 300,000 clients per hierarchy when it uses the default settings for all Configuration Manager 2007 features. This increase in supported clients is the result of improvements to the Active Directory synchronization and Collection Evaluation processes

Thursday, October 14, 2010

Test post

V.Next: Configuration Manager and Systems Management Server

Configuration Manager and Systems Management Server

You can find the labs all on the TechNet Virtual Lab page here.
Don’t forget, tomorrow the Community Evaluation Program for ConfigMgr v.Next starts.  More information on that is here.

R3 is RELEASED !!!!!!

Epo tutorials & documentation.

Below link has Epo tutorials & documentation.

Wednesday, October 13, 2010

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

Last hardware inventory 14 days

select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Name not in (select SMS_R_System.Name from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WORKSTATION_STATUS.LastHardwareScan >= DateAdd(dd,-14,GetDate()) )

Collections: query to check for obsolete clients



select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name,SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup,SMS_R_System.Client from SMS_R_System where obsolete = 1

Monday, October 11, 2010

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

Wednesday, October 6, 2010

“The network path was not found" error on Win XP sp3”

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)

  • On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
  • Scroll down to the Computer Browser service.
  • If it is Disabled or set to Manual, set it to Automatic.
  • Then start it. It may stop immediately again, but this is OK.
  • At this point try to connect to the target machine.
If it still doesn't work, you can try the following:
  • open up Network Connections, under Control Panel.
  • Right click on your network adapter and click on Properties.
  • Click on Internet Protocol (TCP/IP), then click on Properties.
  • Click on Advanced, and click on the WINS tab.
  • Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
  • Press OK on each screen until everything's closed.
  • Go back to the client machine and try again.
  • You should be able to connect!
If it still doesn't work:
  • Go back to the Services window and find the service named Routing and Remote Access.
  • Double-click on it, set it to Manual, and stop it.
  • Close Services and try to connect from your client machine again.

Tuesday, October 5, 2010

WSUS Wiki and troubleshooting WSUS

Read here on the WSUS Team Blog a nice article about troubleshooting WSUS. It references the site

This site was created to provide a place for the WSUS community to share information about WSUS, including troubleshooting steps and best practices. The advantages that this site provides over public news groups include:

  • Content on this site is edited and kept up-to-date. News group postings can get out of date, can contain incorrect information, and are often not corrected.
  • It is easier for readers to find information on this site than in the news group.
  • This site captures minor contribution from many users and both aggregates and persists them over time. This body of work grows and gets better over time whereas newsgroups just grow.
  • It is fun to edit pages and improve on contributions of others. You can not really do that with news groups.

It also references several troubleshooting tips for successful configuration of WSUS.

Check it out.

SQL Reporting Services: SRS

SQL Reporting services have some benefits over the current reporting solution:

  • Provide best in class reporting capability by integrating SQL Reporting Services, with the leading change and configuration management product: SCCM 2007
  • Enable Ad-hoc reporting - Make it easy for both SCCM administrators, and non administrators to find the information they need to make the right decisions for their business
  • Support alternative databases as the reporting database, such as a replicated or backup database
  • Allow custom report creation via a report authoring wizard.
  • Enable report browsing and viewing via the SRS Report Viewer.
  • Take advantage of rendering in all supported SRS formats, report caching, and subscriptions.

This article will explain setting up SRS with Configuration Manager based on SQL 2008. I’ve taken most of the steps from this article (many thanks to Michael Wiles). I’ve added some screenshots and applied it to SQL 2008, while the original article discusses SQL 2005. If you need more background info on SRS check out that link.

Install and configure SQL Reporting Services in SQL 2008


Be sure to check Reporting Services as part of your SQL installation


At step 21 of this part of this guide the setup provides you with three choices:

  • Native mode default configuration
  • SharePoint mode default configuration
  • Unconfigured Reporting Services installation

You should select Unconfigured Reporting Services installation at this point.

After the installation finishes you should configure SRS for the use with Configuration Manager 2007.

1. In the start menu select Microsoft SQL Server 2008 / Configuration Tools, then click Reporting Services Configuration Manager.

2. In the Reporting Services Configuration Connection select the Server Name and the Report Server Instance, then select Connect.


3. In the Report Server Status verify that the Service Status is set to Running. If it is not, click Start, and then click Apply.


4. Select Web Service URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default ReportServer). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.


5. Select Database, select Create a new report server database in the Report Server Database Configuration Wizard and click Next


6. Select the Database Server Name and Authentication Type that matches your SQL server and credentials.


7. Supply the Database Name and Language. Be sure to select Native Mode for Report Server Mode. Click Next.


8. Select the proper credentials from the drop list for Authentication Type


9. In the Summary screen review your settings and Click Next.


10. Review your database in the Report Server Database screen.


11. Select Report Manager URL and make sure you specify the name you want to call the virtual directory created by Reporting Services (or use the default Reports). Optionally you can select the IP-address you want to use, the port and SSL setting. When done click Apply.


12. Email settings are not mandatory to setup, but can be configured appropiately if necessary.

13. Execution Account is necessary to configure if you will be running unattended reports. Optionally apply credentials and Click Apply.

20. Click Exit to close Reporting Services Configuration Manager.

Configure Configuration Manager 2007

SQL Reporting Services need the configuration of a Reporting Services Point role.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code>-<site name> / Site Settings / Site Systems.

2. In this guide I will add the reporting services point site role to the existing site system. Right-click the site system name, and click New Roles. On the General page of the New Site Role Wizard, configure the general settings for this site system, then click Next.


3. On the System Role Selection page of the wizard, select Reporting Services point (don’t select Reporting Point by mistake, which is the traditional reporting functionality), then click Next.


5. On the Reporting Services Point page, specify the folder that will be created on the report server to contain the SQL Reporting Services reports used in Configuration Manager and then click Next.


6. Review the information shown on the Summary page, then click Next.

7. Click Close to exit the wizard.

8. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services, and expand the node.

9. Right-click the reporting services point server you want to configure, then click Properties.

10. On the Data Source Settings tab of the Report Server Properties dialog box, specify the Configuration Manager 2007 database server and database name (not the one create earlier for reporting!) to be used as the data source for SQL Reporting Services reports. Click the test button to verify that you have correct data entered.


11. On the Data Source Authentication tab of the Report Server Properties dialog box, specify the credentials used to access reports on the report server. I’ve use Windows Integrated Security here.


12. On the Data Source Security tab of the Report Server Properties dialog box, specify permissions for the users who have access to the data source specified in the Data Source Settings tab.


13. On the Security tab of the Report Server Properties dialog box, specify the users who have access to the selected report server.


14. Click OK to close the Report Server Properties dialog box.

Import standard reports in Reporting Services

The last step in configuring SRS for Configuration Manager 2007 is to convert the standard reports to Reporting Services reports.

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services

2. Right-click the Reporting Services server that the standard reports will be copied to, then click Copy Reports to Reporting Services.


3. On the Data Source Settings page of the Copy Reports Wizard, specify the Configuration Manager 2007 database server and database name from which to copy the reports. Click Next.


4. On the Data Source Authentication page of the Copy Reports Wizard, choose the authentication method required to run the copied reports on the reporting point server. Click Next.


5. On the Select Reports page of the Copy Reports Wizard, select the reports you want to copy to the reporting services point. Select Overwrite existing reports if you want to overwrite any reports that already exist on the reporting services point. Click Next.


6. On the Security page of the Copy Reports Wizard, specify which users can access the copied reports and the roles they must belong to. For more information about the options on this page, see Report Server Properties: Security Tab. Click Next


7. On the Summary page of the Copy Reports Wizard, review the reports that will be created, and then click Next.


8. After the reports are copied, click Next.


9. On the Confirmation page of the Copy Reports Wizard, review the information, and then click Close to exit the wizard.

Reports are now available Site Database / Computer Management / Reporting / Reporting Services / <Site Server> / All Reports


To run a particular report just Right Click the report and select Run.


Popular and useful tools for ConfigMgr 2007

  • SCCM Right Click Tools
  • SCCM Client Center
  • OSD++
  • SMSMap
  • SCCMAutoDoc
  • SCCM 2007 SDK
  • BitsAdmin
  • WMI Administrative Tools
  • WMI Diagnosis Utility!.aspx

Step by Step 4 part guide to Deploying Windows 7 Enterprise.

Deploy Windows 7 part 1.
Build and Capture
Part 1 is the longest part of the 4 part guide and covers the steps required to successfully Build and Capture Windows 7 RTM. It was tested successfully on both X86 and X64 Enterprise RTM releases.
Step 1. get the ISO
Step 2. Add Operating System Install Package
Step 3. Create Distribution Point for the Image
Step 4. Update Distribution Point
Step 5. Create the Build and Capture Task Sequence
Step 6. Advertise the Build and Capture Task Sequence
Step 7. Add a system to the Build and Capture 7 collection
Step 8. PXE boot the newly added Windows 7 client
Deploy Windows 7 part 2.
Add the captured WIM file
Step 1. Add the Captured Wim file as an Operating System Image
Step 2. Distribute the Captured WIM file
Deploy Windows 7 part 3.
Create a new Task Sequence
Step 1. Create a new Task Sequence
Deploy Windows 7 part 4.
Advertise the Task Sequence
Step 1. Advertise the Task Sequence
Step 2. Last Actions
enjoy !

SCCM Index : End- End

SCCM Index from windows noob

A legacy network adapter : Hyper - V

A legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network-based installations because it includes the ability to boot to the Pre-Boot Execution Environment (PXE). The legacy network adapter is not supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition."




then you can see as below



Hyper – V : Installing a Legacy Network Adapter

Installing a Legacy Network Adapter.
(Legacy Adapters aren't supported in Windows Server 2003 64-bit or Windows XP 64-bit)
1. Make sure your Virtual Machine is shutdown.
2. Right-click the Virtual Machine in Hyper-v select Settings.
3. Select Add Hardware.
4. On the Add Hardware page select Legacy Adapter.
5. Then click Add.

Monday, October 4, 2010

OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause:  This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.


Here, I'll share with you 9 tips to deal with negative people in your life:

1) Don't get into an argument
One of the most important things I learned is not to debate with a negative person.

A negative person likely has very staunch views and isn't going to change them because of what you say. Whatever you say, he can find 10 different reasons to back up his viewpoint. The discussion will just swirl into more negativity, and you pull yourself down in the process. You can give constructive comments, and if the person rebuts with no signs of backing down, don't engage further.

2) Empathize with them
Have you ever been annoyed by something before, then have someone tell you to "relax"? How did you feel? Did you relax as the person suggested or did you feel even more worked up?

From my experience, people who are negative (or upset for that matter) benefit more from an empathetic ear than suggestions/solutions on what he should do. By helping them to address their emotions, the solutions will automatically come to them (it's always been inside them anyway).

3) Lend a helping hand
Some people complain as a way of crying for help. They may not be conscious of it, though, so their comments come across as complaints rather than requests. Take the onus to lend a helping hand. Just a simple "Are you okay?" or "Is there anything I can do to help you?" can do wonders.

4) Stick to light topics
Some negative people are triggered by certain topics. Take for example: One of my friends sinks into a self-victimizing mode whenever we talk about his work. No matter what I say (or don't say) he'll keep complaining once we talk about work.

Our first instinct with negative people should be to help bring them to a more positive place (i.e. steps #2 and #3). But if it's apparent the person is stuck in his negativity, the unhappiness may be too deeply rooted to address in a one-off conversation, or for you to help him unravel it.

Bring in a new topic to lighten the mood. Simple things like new movies, daily occurrences, and common friends make for light conversation. Keep it to areas the person feels positive about.

5) Ignore the negative comments

One way to help the negative person "get it" is to ignore the negative comments. If he goes into a negative swirl, ignore or give a simple "I see" or "Ok" reply. On the other hand, when he is being positive, reply in affirmation and enthusiasm. Do this often and soon he will know that positivity pays off.

6) Praise the person for the positive things

Negative people aren't just negative to others; they're also negative to themselves. If you already feel negative around them, imagine how they must feel all the time.

What is the person good at? What do you like about the person? Recognize the positive things and praise him for it. He will be surprised at first and might reject the compliment, but on the inside he will feel positive about it. That's the first seed of positivity you're planting in him and it'll bloom in the long-term.

7) Hang out in 3's or more people

Having someone else in the conversation works wonders in easing the load. In a one-on-one communication, all the negativity will be directed towards you. With someone else in the conversation, you don't have to bear the full brunt of the negativity. This way you can focus more on doing steps #1 (Empathizing) and #2 (Helping the person).

8) Be responsible for your reaction

Whether the person is negative or not, ultimately you're the one
who is perceiving the negativity.

Take responsibility for your perceptions. You can interpret every personality trait of another person in a positive  or a negative manner. Learn to see the goodness of the person rather than the negative. It may be tough initially, but once you cultivate the skill,
it becomes second nature.

9) Reduce contact with them / Avoid them

If all else fails, reduce contact with them or avoid them altogether. If it's a good friend, let him know of the severity of the issue and work it out where possible. It's not healthy to spend too much time with people who drain you.

Your time is precious, so spend it with people who have positive effects on you

Friday, October 1, 2010

Systems Part of What Collections

--Systems Part of What Collections

SELECT v_R_System.Name0, v_Collection.Name FROM v_FullCollectionMembership INNER JOIN v_R_System ON v_FullCollectionMembership.ResourceID = v_R_System.ResourceID INNER JOIN v_Collection ON v_FullCollectionMembership.CollectionID = v_Collection.CollectionID WHERE (v_R_System.Name0 = 'Systemname')

Thursday, September 30, 2010

For finding the 90 days old computers in the AD



For finding the 90 days old computers in the AD

DSQUERY COMPUTER "DC=MydomainName,DC=COM" -STALEPWD 90 -LIMIT 5000 >> C:\output.csv

for finding the 90 days old computers in the AD & action to delete with the output


Wednesday, September 29, 2010

Good Posting for Multicasting for OSD : End to End

you can find here

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 Book for Good to Great Framework

Good to Great: by Jim Collins Page


like The 7 Habits of Highly Effective People

one more virtual software : SUN V BOX

one more virtual software



Thursday, August 26, 2010

Good website for beginners on Windows Basics

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

7575 questions to ask yourself : Questions are the answer.

1. Why not me?
2. Am I nice?
3. Am I doing what I really want to do?
4. What am I grateful for?
5. What’s missing in my life?
6. Am I honest?
7. Do I listen to others?
8. Do I work hard?
9. Do I help others?
10. What do I need to change about myself?
11. Have I hurt others?
12. Do I complain?
13. What’s next for me?
14. Do I have fun?
15. Have I seized opportunities?
16. Do I care about others?
17. Do I spend enough time with my family?
18. Am I open-minded?
19. Have I seen enough of the world?
20. Do I judge others?
21. Do I take risks?
22. What is my purpose?
23. What is my biggest fear?
24. How can I conquer that fear?
25. Do I thank people enough?
26. Am I successful?
27. What am I ashamed of?
28. Do I annoy others?
29. What are my dreams?
30. Am I positive?
31. Am I negative?
32. Is there an afterlife?
33. Does everything happen for a reason?
34. What can I do to change the world?
35. What is the most foolish thing I’ve ever done?
36. Am I cheap?
37. Am I greedy?
38. Who do I love?
39. Who do I want to meet?
40. Where do I want to go?
41. What am I most proud of?
42. Do I care what others think about me?
43. What are my talents?
44. Do I utilize those talents?
45. What makes me happy?
46. What makes me sad?
47. What makes me angry?
48. Am I satisfied with my appearance?
49. Am I healthy?
50. What was the toughest time in my life?
51. What was the easiest time in my life?
52. Am I selfish?
53. What was the craziest thing I did?
54. What is the craziest thing I want to do?
55. Do I procrastinate?
56. What is my greatest regret?
57. What has had the greatest impact on my life?
58. Who has had the greatest impact on my life?
59. Do I stand up for myself?
60. Have I settled for mediocrity?
61. Do I hold grudges?
62. Do I read enough?
63. Do I listen to my heart?
64. Do I donate enough to the less fortunate?
65. Do I pray only when I want something?
66. Do I constantly dwell on the past?
67. Do I let other people’s negativity affect me?
68. Do I forgive myself?
69. When I help someone do I think “What’s in it for me”?
70. Am I aware that someone always has it worse than me?
71. Do I smile more than I frown?
72. Do I surround myself with good people?
73. Do I take time out for myself?
74. Do I ask enough questions?
75. What other questions do I have?

Wednesday, August 25, 2010

Discovery Mystery

Discovery Methods

Six methods of discovery are available in Configuration Manager 2007:

  • Network Discovery
  • Heartbeat Discovery----------------------------------------------------this must enabled in all sites
  • Active Directory System Group Discovery
  • Active Directory Security Group Discovery
  • Active Directory System Discovery
  • Active Directory User Discovery


As Configuration Manager 2007 discovers resources, it creates records in the Configuration Manager database. This record is called a data discovery record (DDR) and the file generated has a .DDR extension. The specific information contained in each record varies depending on the resource "discovered," but it can include data such as the NetBIOS name of a computer, IP address and IP subnet of a computer or device, operating system, MAC address, and so on.

Depending on the discovery method used, resource DDRs are periodically regenerated to keep the discovery data up to date in the database and to verify that the resource is still a valid resource within the Configuration Manager 2007 site.


Now these methods what will discover?.. below are the discover use of each

Active Directory System Group Discovery

  • Organizational unit
  • Global groups
  • Universal groups
  • Nested groups
  • Nonsecurity groups
  • Active Directory System Discovery

    • Computer name
    • Operating system
    • Object class
    • DNS Host name
    • Domain

    Active Directory User Discovery

    • User name
    • DNS host name
    • Object class
    • Active Directory domain
    • Active Directory container name

    Network Discovery

    • NetBIOS name
    • IP addresses
    • Resource domain
    • System roles
    • SNMP community name
    • MAC addresses

    Heartbeat Discovery :- Heartbeat Discovery is active only on computers that have already been installed as Configuration Manager clients.

    It is important to ensure that any schedule you create causes the DDRs to be updated frequently enough so that the original DDR isn't viewed by Configuration Manager as obsolete or deleted from the database.Heartbeat Discovery updates existing DDRs rather than creating new ones. By default, it generates an updated DDR for each client every seven days, although this timing is configurable.

    Heartbeat Discovery runs on installed Configuration Manager clients according to the schedule you specify. With this method enabled, the Client Component Installation Manager (CCIM) on the client causes the Cliex32.dll to generate a DDR, which is then written to the management point. This file is the same size as a normal DDR (approximately 1 KB per client), and so it will generate approximately the same network traffic.


    Active Directory Security Group Discovery

    he Configuration Manager 2007 Active Directory Security Group Discovery method searches for security groups by polling the closest Active Directory domain controller. The Active Directory domain can be in mixed mode or native mode.


    Discovery Troubleshooting Flowcharts


    Log files related to discovery

    Adsysdis.log Active Directory System Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created and any "bogus" entries.

    Adsysgrp.log Active Directory System Group Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created.

    Adusrdis.log Active Directory User Discovery log file showing when the discovery method runs, and its results. Look for the number of DDRs created.




    If you deleted any system from SCCM / SMS console you can initiate the client discovery data cycle then client can be reappear in the console


    Third party Discovery Tools :- enhanced discovery tool


    The major discovery drop backs in SCCM is it will not do a delta discovery it will do from scratch.. that means it will not discover specific to the changes that has changed from last cycle.. to accomplish this you need to depend on Enhanced discovery tool 

    now with SCCM R3 you can do delta discovery

    SCCM Client Services and applets

    image If SMS/SCCM Client is installed we will get SMS Agent host (ccmexec.exe ) service will be installed all the related information log file is ccmexec.log file

    if client installed it will come in Control Panel



    if the client OS version is 32 bit then you can find the applets in the control panel directly, if it is 64 bit OS then you will get in 32-bit Control Panel items (The reason is sccm is a 32 bit application) also client will be installed in windows\ccmsetup for client installation

    and for client logs in 64 located in



    64 bit client log files location screenshot is below