All about Systems Management / ConfigMgr

Friday, May 14, 2010

Scripts to query installed Service Packs, Patches/updates and Hotfixes

There are many known scripts which use WMI class Win32_QuickFixEngineering to enumerate hotfixes installed on a computer. These scripts can give you a list of installed updates like;

This Script reports installed updates that are installed with Windows Update (v5) technology and the result will be written to %temp%\UpdateHistory.txt and then launched in Notepad.

USAGE: Cscript //nologo WUhistory.vbs

The output will look like;

Report run at 4/23/2006 2:42:14 PM
------------------------------------------------------------------
Title: Security Update for Windows XP (KB908531)
Description: A security issue has been identified in Windows Explorer that could allow an attacker to compromise your Windows-based system and gain control over it. You can help protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer.
Date/Time in GMT: 4/18/2006 7:47:14 AM
Install mechanism: AutomaticUpdates
Install status: Succeeded
------------------------------------------------------------------

'--------------------8<----------------------
' Script that reports installed updates that are
' installed with Windows Update v5 technology
'
' Result will be written to %temp%\UpdateHistory.txt
' and then launched in Notepad
'
' Author: Torgeir Bakken
' Date 2004-08-12
'
Option Explicit

Const OverwriteIfExist = -1
Const OpenAsASCII = 0

Dim oWU, iTHCount, colUpdate, oUpdate, sStatus, iTotal
Dim iSuccess, iFailed, iAborted, iUnknown, sErrorCode
Dim oFSO, oShell, sFile, f

On Error Resume Next
Set oWU = CreateObject("Microsoft.Update.Searcher")

If Err.Number <> 0 Then
   MsgBox "WU5 programming interface does not exist.", _
          vbInformation + vbSystemModal, "Update history"
   WScript.Quit
End If
On Error Goto 0

iTHCount = oWU.GetTotalHistoryCount
If iTHCount > 0 Then

   Set oFSO = CreateObject("Scripting.FileSystemObject")
   Set oShell = CreateObject("Wscript.Shell")
   sFile = oShell.ExpandEnvironmentStrings("%TEMP%") & "\UpdateHistory.txt"
   Set f = oFSO.CreateTextFile(sFile, _
                      OverwriteIfExist, OpenAsASCII)

   iTotal = 0
   iSuccess = 0
   iFailed = 0
   iAborted = 0
   iUnknown = 0

   f.WriteLine "Report run at " & Now
     f.WriteLine "---------------------------------" _
           & "---------------------------------"

Set colUpdate = oWU.QueryHistory(0, iTHCount)

   For Each oUpdate In colUpdate
     f.WriteLine "Title:" & vbTab & vbTab & vbTab & oUpdate.Title
     f.WriteLine "Description:" & vbTab & vbTab & oUpdate.Description
     f.WriteLine "Date/Time in GMT:" & vbTab & oUpdate.Date
     f.WriteLine "Install mechanism:" & vbTab & oUpdate.ClientApplicationID

     sErrorCode = ""
     Select Case oUpdate.ResultCode
       Case 2
         sStatus = "Succeeded"
         iSuccess = iSuccess + 1
       Case 4
         sStatus = "Failed"
         iFailed = iFailed + 1
         sErrorCode = oUpdate.UnmappedResultCode
       Case 5
         sStatus = "Aborted"
         iAborted = iAborted + 1
       Case Else
         sStatus = "Unknown"
         iUnknown = iUnknown + 1
     End Select

     If sStatus = "Failed" Then
       f.WriteLine "Install error:" & vbTab & vbTab & sErrorCode
     End If

     f.WriteLine "Install status:" & vbTab & vbTab & sStatus
     f.WriteLine "---------------------------------" _
           & "---------------------------------"

iTotal = iTotal + 1
Next

   f.WriteLine
   f.WriteLine "Total number of updates found: " & iTotal
   f.WriteLine "Number of updates succeeded: " & iSuccess
   f.WriteLine "Number of updates failed: " & iFailed
   f.WriteLine "Number of updates aborted: " & iAborted

f.Close
oShell.Run "notepad.exe " & """" & sFile & """", 1, False
Else

MsgBox "No entries found in Update History.", _
vbInformation + vbSystemModal, "Update history"

End If
'--------------------8<----------------------

This script enumerate hotfixes installed on a computer and outputs some computer information.

USAGE: Cscript //nologo HotfixHistory.vbs > HotfixHistory.txt

The output will look like;

Hotfix report date: 4/23/2006 2:45:19 PM

OS version: Microsoft Windows XP Professional
SP version: Service Pack 2
OS language: English

HotFixID: KB873339
Description: Windows XP Hotfix - KB873339
InstalledBy: Administrator
InstallDate: 12/11/2005

'
' Description: Script that outputs some computer information
' and lists all installed hotfixes including installation date
'
' Author: Torgeir Bakken
' Date: 2004-10-19
'

Wscript.Echo "Hotfix report date: " & Now & vbCrLf

strComputer = "." ' use "." for local computer

Const HKLM = &H80000002

'On Error Resume Next
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colSettings = objWMIService.ExecQuery _
("Select * from Win32_OperatingSystem")

' get general info about the OS

' Caption value for different OS:
' Microsoft Windows 2000 ...
' Microsoft Windows XP ...
' Microsoft(R) Windows(R) Server 2003, ..... Edition
For Each objOperatingSystem in colSettings
    strOSCaption = objOperatingSystem.Caption
    Select Case True
      Case InStr(1, strOSCaption, "windows 2000", vbTextCompare) > 0
        strOS = "Windows 2000"
      Case InStr(1, strOSCaption, "windows xp", vbTextCompare) > 0
        strOS = "Windows XP"
      Case InStr(1, strOSCaption, "windows(r) server 2003", vbTextCompare) > 0
        strOS = "Windows Server 2003"
    End Select

    intOSLang = objOperatingSystem.OSLanguage
    strOSLangHex = Right("000" & Hex(intOSLang), 4)
    strOSServicePack = objOperatingSystem.CSDVersion
Next

Set objReg = GetObject("WinMgmts:{impersonationLevel=impersonate}!//" _
& strComputer & "/root/default:StdRegProv")

strOSLanguage = "Unknown" ' Init value
strKeyPath = "SOFTWARE\Classes\MIME\Database\Rfc1766"
strValueName = strOSLangHex
objReg.GetStringValue HKLM, strKeyPath, strValueName, strOSLanguage

' remove unnecessary stuff
arrOSLanguage = Split(strOSLanguage, ";")
strOSLanguage = arrOSLanguage(UBound(arrOSLanguage))
If Instr(strOSLanguage, "(") > 0 Then
arrOSLanguage = Split(strOSLanguage, "(")
strOSLanguage = Trim(arrOSLanguage(0))
End If

Wscript.Echo "OS version: " & strOSCaption
Wscript.Echo "SP version: " & strOSServicePack
Wscript.Echo "OS language: " & strOSLanguage

' start enumeration of hotfixes

Wscript.Echo vbCrLf & "Hotfixes Identified:"

strRegBaseUpdate = "SOFTWARE\Microsoft\Updates\" & strOS

Set colItems = objWMIService.ExecQuery _
("Select * from Win32_QuickFixEngineering",,48)

For Each objItem in colItems
    If objItem.HotFixID <> "File 1" Then
       Wscript.Echo "HotFixID: " & objItem.HotFixID
       Wscript.Echo "Description: " & objItem.Description
       Wscript.Echo "InstalledBy: " & objItem.InstalledBy
       strInstallDate = Null ' init value
       If objItem.ServicePackInEffect <> "" Then
          strRegKey = strRegBaseUpdate & "\" & objItem.ServicePackInEffect _
                 & "\" & objItem.HotFixID
          objReg.GetStringValue HKLM, strRegKey, _
               "InstalledDate", strInstallDate
       End If

       If IsNull(strInstallDate) Then
          strInstallDate = "(none found)"
       End If
       Wscript.Echo "InstallDate: " & strInstallDate
       Wscript.Echo   ' blank line
    End If
Next
'--------------------8<----------------------

I found this script in the community. Worth a try!

'--------------------8<----------------------

strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
    & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colQuickFixes = objWMIService.ExecQuery _
    ("Select * from Win32_QuickFixEngineering")
For Each objQuickFix in colQuickFixes
    Wscript.Echo "Computer: " & objQuickFix.CSName
    Wscript.Echo "Description: " & objQuickFix.Description
    Wscript.Echo "Hot Fix ID: " & objQuickFix.HotFixID
    Wscript.Echo "Installation Date: " & objQuickFix.InstallDate
    Wscript.Echo "Installed By: " & objQuickFix.InstalledBy
Next

'--------------------8<----------------------

Very recently, I found this GUI utility by name WinUpdatesList.

WinUpdatesList displays the list of all Windows updates (Service Packs and Hotfixes) installed on your local computer.
For hotfix updates, this utility also displays the list of files updated with these hotfixes.
In addition, it allows you to instantly open the Web link in Microsoft Web site that provides more information about the selected update, uninstall an update, copy the update information to the clipboard, or save it to text/HTML/XML file.

You can also query list of updates /hotfixes installed by this simple command (one line). Replace 'server-name' with your server or your machine name;

wmic /node:'server-name' qfe GET description,FixComments,hotfixid,installedby,installedon,servicepackineffect

You can also output the result to a text / csv file;

wmic /node:'server-name' qfe GET description,FixComments,hotfixid,installedby,installedon,servicepackineffect > QFElist.txt

Saturday, May 8, 2010

create 1000 users

' Create 1000 Sample User Accounts

Set objRootDSE = GetObject("LDAP://rootDSE")

Set objContainer = GetObject("LDAP://cn=Users," & _
objRootDSE.Get("defaultNamingContext"))

For i = 1 To 1000
Set objLeaf = objContainer.Create("User", "cn=UserNo" & i)
objLeaf.Put "sAMAccountName", "UserNo" & i
objLeaf.SetInfo
Next

WScript.Echo "1000 Users created."

'Below script to create number of computers in AD--for testing

'Below script to create number of computers in AD--for testing

'==============================================================================
'
' Description: This script creates multiple sequential computer accounts
' in an AD OU. It appends a 3 digit number to the base name starting with
' the number entered at the prompt.
' ==============================================================================
Option Explicit
'Define Constants
Const ADS_SCOPE_ONELEVEL = 1
'Declare Variables
Dim DQ
Dim strAdmin
Dim intRecord
Dim objShell
Dim objNetwork
Dim intWarn
Dim objRootDSE
Dim strADsPath
Dim objConnection
Dim objCommand
Dim strOUPath
Dim objRecordSet
Dim strBaseName
Dim intRecordMax
Dim bEnabled
Dim objOU
Dim strNewComputerName
Dim objNewComputer
Dim strDomainDN
Dim strDomainFQDN
Dim intOULevel
Dim strSearchADsPath
Dim intStartNumber
'Set variables
DQ = Chr(34)
'Create Objects
Set objShell = CreateObject("Wscript.Shell")
Set objNetwork = CreateObject("WScript.NetWork")
'Verifies script was run using Cscript, and if not relauches it using Cscript
If Not WScript.FullName = WScript.Path & "\cscript.exe" Then

objShell.Popup "Relaunching script with Cscript in 5 seconds...", 5, _
"Script Host Message", 48

objShell.Run "cmd.exe /k " & WScript.Path & "\cscript.exe //NOLOGO " & _
DQ & WScript.scriptFullName & DQ, 1, False

Script.Quit 0
End If

'Warn User
intWarn = MsgBox("This will make changes to AD." & VbCr & _
"Are you sure you want to do this?", 308, "ID 10 T Check")
'308 = Yes/No (4) + 'Exclaimation (48) + Default Button 2 (256)
If intWarn = vbNo Then

WScript.Quit 0
End If
'Construct an ADsPath to the Current Domain with rootDSE
Set objRootDSE = GetObject("LDAP://rootDSE")
strADsPath = "LDAP://" & objRootDSE.Get("defaultNamingContext")
'Convert domain Distinguished Name to FQDN format
strDomainDN = objRootDSE.Get("defaultNamingContext")
strDomainFQDN = Replace(Replace(strDomainDN, "DC=", ""), ",", ".")
'Connect to Active Directory
Set objConnection = CreateObject("ADODB.Connection")
Set objCommand = CreateObject("ADODB.Command")
objConnection.Provider = "ADsDSOObject"
objConnection.Open "Active Directory Provider"
Set objCommand.ActiveConnection = objConnection
objCommand.Properties("Page Size") = 1000
objCommand.Properties("Searchscope") = ADS_SCOPE_ONELEVEL
'Prompt for Path to OU
Do

strOUPath = _
InputBox("Please enter the path to the OU where the computer accounts " & _
" will be created - Seperate OUs With a \", "OU Path Input", "TopOU\SubOU")
If strOUPath = False Then
WScript.Quit

End If
Loop Until strOUPath <> ""

'Split OU path by OU
strOUPath = UCase(strOUPath)
strOUPath = Split(strOUPath, "\")

'Prepare variables for search
intOULevel = 0
strSearchADsPath = strADsPath

'Search through each OU level in path provided
For intOULevel = 0 To UBound(strOUPath)

objCommand.CommandText = "SELECT ADsPath FROM '" & strSearchADsPath & _
"'" & " WHERE objectCategory='organizationalUnit' AND Name = '" & _
strOUPath(intOULevel) & "'"

Set objRecordSet = objCommand.Execute

'Verify OU was found

If objRecordSet.EOF Then

WScript.echo "OU named " & strOUPath(intOULevel) & _
" not found, Exiting script."

WScript.quit

Else

objRecordSet.MoveFirst
Do Until objRecordSet.EOF
strSearchADsPath = objRecordSet.Fields("ADsPath").Value
objRecordSet.MoveNext
Loop
End If
Next
'Get current username to use in description field
strAdmin = objNetwork.UserName
'Prompt for the base computer name
Do
strBaseName = _
InputBox("Please enter the base computer name to use for new accounts:", _
"Base Computer Name", "TestPC")
If strBaseName = False Then
WScript.Quit
End If
Loop Until strBaseName <> ""
strBaseName = UCase(strBaseName)
'Prompt for starting computer number
Do

intStartNumber = _
InputBox("Please enter the beginning number to use in computer names:", _
"Starting Computer Number", "001")
If intStartNumber = False Then

WScript.Quit

End If
Loop Until intStartNumber <> ""
intStartNumber = CInt(intStartNumber)
intRecord = intStartNumber
'Prompt for number of accounts to be created
Do

intRecordMax = _
InputBox("Please enter the number of accounts to be created", _
"Count Input", "10")
If intRecordMax = False Then

WScript.Quit

End If
Loop Until intRecordMax <> ""
intRecordMax = CInt(intRecordMax)

'Bind to OU that computers will be created in
Set objOU = GetObject(strSearchADsPath)

'Create the user accounts
Do Until intRecord = intRecordMax + intStartNumber
intRecord = Right("000" & intRecord, 3)
strNewComputerName = strBaseName & intRecord
WScript.Echo "Creating " & strNewComputerName
Set objNewComputer = objOU.Create("Computer", "cn= " & strNewComputerName)
objNewComputer.Put "samAccountName", strNewComputerName & "$"
objNewComputer.Put "userAccountControl", 4096
objNewComputer.Put "description", "Account created: " & Date() & " by: " _
& strAdmin
objNewComputer.SetInfo 'Writes settings to AD
intRecord = intRecord + 1
Loop

WScript.Echo
WScript.echo "Finished creating computer accounts."

Tuesday, May 4, 2010

Dell PowerEdge R510 server

Specifications

Processor: Up to two Intel Xeon 5500 and 5600 processors, up to six cores per socket, up to 12 sockets per server.
RAM: Up to 64 GB, 128 GB, or 192 GB DDR3 RAM, depending on which Dell resource you use. (See “RAM options are inconsistent” in the What’s wrong section below for more information.)
RAID: Wide variety of RAID controller options to support internal and external storage.
Drive bays: Chassis options include 4, 8, or 12 drive bays.
Drive options: Up to 12 disks at 2 TB each. Supports 2.5″ and 3.5″ SATA and DAS disks and includes a solid state disk option. The 12 disk chassis also has space for two more internal drives.
Network: 2 x 1 Gb Ethernet ports on board (Broadcom 5716).
Power: Redundant power supply available.
Additional information: Product Web site
Photos of the Dell PowerEdge R510

The target market

The Dell PowerEdge R510 server is aimed squarely at space-constrained data centers or small and medium-size organizations. I see these primary use cases:

Common platform: Organizations that want significant server use flexibility and also want a common platform to administrative ease. The Dell PowerEdge R510’s versatility makes it a natural fit for many applications.
Smaller is better: Organizations that need to pack more servers into a data center and that don’t want to move to blades to gain density. The Dell PowerEdge R510’s 26″ depth makes it possible to support this need.
Mega storage needed: Small and medium organizations that need a server with massive internal storage and that may not want to invest in a SAN.

What problem does it solve

Many organizations have a desire to standardize on a single server platform in order to make it easier to support the server environment and to keep spare parts on hand in the event of a failure; however, those organizations often have a wide variety of computing needs, each requiring different computing resources. A VMware host, for example, will need RAM and processing power and will generally be connected to a SAN. Exchange, on the other hand, needs RAM, processing power, and raw disk space. SQL Server has similar needs. With its flexible chassis options, dual quad-core processing capability, and support for triple digit GBs of RAM, the 2U Dell PowerEdge R510 can meet the needs for all but the most processor intensive applications. IT can deploy a wide array of services on this single computing platform without sacrificing in any area of the computing spectrum.

The Dell PowerEdge R510 is also a short server, measuring only 26″ deep. This makes it an ideal choice for smaller organizations that have small data centers and need to eke out as much space as possible without sacrifice.

Standout features

In addition to offering very flexible computing options and having a short depth, the Dell PowerEdge R510 offers an optional LCD display that allows administrators to quickly determine chassis status and choose boot options. The availability of the display is dependent on which chassis option is selected. For example, as you will see in the photo gallery, getting a display on the 12 chassis model would be tough.

What’s wrong

Processor density
This is not a specific product issue, but rather a gap in Dell’s line. Ideally, I’d love to see the company release a version of the Dell PowerEdge R510 with support for up to four processors. Obviously, with a short depth, support for a lot of RAM and 12 disks crammed in the existing chassis, this four-socket dream might be difficult to produce in this form factor.

RAM options are inconsistent
Another negative element of this server is not necessarily a knock on the server itself — instead, it’s directed at Dell’s marketing folks. I got frustrated when I looked at various views of the Dell PowerEdge R510 on Dell’s site. Depending on the page being viewed, the site lists the server’s maximum RAM at three values:

64 GB (the Dell PowerEdge R510 dedicated page’s Tech Specs tab)
128 GB (the Dell PowerEdge R510 PDF specs) (I suspect that this is the true limit with the availability of 16 GB memory modules.)
192 GB (the PowerEdge server overview page)

In purchasing a server, the maximum RAM configuration available at present is 128 GB.

In the Dell PowerEdge R510’s complete technical guide, there is mention that the chassis selected also impacts the availability of certain RAM configurations. The 4 drive chassis is listed as accepting 1, 2, and 4 GB memory modules; the 8 drive chassis is shown as accepting 1, 2, 4, 8, and 16 GB modules.

My recommendation: Work with your sales rep to make sure your system has the memory options you expect and need.

Competitive products

Bottom line for business

The Dell PowerEdge R510 server is a very welcome addition to Dell’s server lineup and certainly fills an important niche by providing a single-platform solution to organizations that have a wide variety of needs.

Monday, May 3, 2010

ConfigMgr 2007 Tool Kit v2

http://www.microsoft.com/downloads/details.aspx?FamilyID=5a47b972-95d2-46b1-ab14-5d0cbce54eb8&displaylang=en

direct http://download.microsoft.com/download/5/5/0/55078AC4-3D15-407B-948E-CEB72A0A5A50/ConfigMgrTools.msi

The following list provides specific information about each tool in the toolkit.

Client Spy - A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on Configuration Manager 2007 clients.
Delete Group Class Tool - A tool used to remove inventory group definitions along with history data, tables, views and stored procedures for the group.
Desired Configuration Management Migration Tool - A tool used to migrate from the DCM Solution for SMS 2003 to DCM in ConfigMgr 2007.
Desired Configuration Management Model Verification Tool - A tool used by desired configuration management content administrators for the validation and testing of configuration items and baselines authored externally from the Configuration Manager console.
Desired Configuration Management Substitution Variable Tool - A tool used by desired configuration management content administrators for authoring desired configuration management configuration items that use chained setting and object discovery.
Management Point Troubleshooter Tool - A tool that checks a computer system before and after a management point installation to ensure that the installation meets the requirements for management points.
Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on Configuration Manager 2007 clients.
Preload Package Tool - A tool used to manually install compressed copies of package source files on Configuration Manager 2007 sites.
Security Configuration Wizard Template for Configuration Manager 2007 - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required. The Configuration Manager 2007 Service Pack 2 Security Configuration Wizard template supports new site system definitions and enables the required services and ports.
Send Schedule Tool - A tool used to trigger a schedule on a Client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.
Trace32 - A log viewer that provides a way to easily view and monitor log files created and updated by Configuration Manager 2007 clients and servers.

Thursday, April 29, 2010

APP V

App-V 4.6 is only supported on Configuration Manager SP2 with R2. App-V 4.6 and SCCM SP2 add support for 64-bit client operating systems.

Note: App-V 4.5 is supported on Configuration Manager SP2 with R2, but no support is available for 64-bit clients in this configuration.

Yep I want to make it Zero as APPV does

Do you hate ConfigMgr / SCCM on below situation??? I hate them

PKI and the DMZ
Locating and repairing broken clients (SCCM and WSUS)
Wouldn't it be nice if the 'copy package to new distribution point' wizard could alphabetize the distribution points?
The AI reports (License 14A for example) don't work very well with some license keys. Bugs from MS, wont be fixed until Windows 8.
OSD/TS process isn't documented very well from MS
when you have the potential to lose log files and not see what went wrong when.
Slow console!!
App-V Integration in SCCM
Migration Tools-
There is no Microsoft supported migration tool to export packages from SMS to SCCM.
Unable to fix broken Config Manager clients (most of the time) via the SCCM Console
SCCM Client cache (C:\Windows\System32\ccm\cache) does not get cleared automatically after a client reaches its cache limit (5GB)
WQL/SQL...
OSD....not reliably PXE booting into OSD every time ...Then after clearing advertisement and reboot, will boot into OSD just fine
Lacking the ability to create collections using SQL.
usmt, usb hard discs not being supported, pxe boot slow
Windows Embedded Systems Management
3rd Party patching
Anything involving Native-mode and PKI.
Client Health

software updates

The ability to postpone the reboot after the installation of updates(SUP).
The WSUS categories are not granular enough => You select Windows XP and you receive updates for Internet explorer.

Updates : Superseding and Superseded Updates : Complete Story

Superseding and Superseded Updates

Typically, an update that supersedes other updates does one or more of the following:

Enhances, improves, or adds to the fix provided by one or more previously released updates.
Improves the efficiency of its update file package, which is installed on client computers if the update is approved for installation. For example, the superseded update might contain files that are no longer relevant to the fix or to the operating systems now supported by the new update, so those files are not included in the superseding update's file package.
Updates newer versions of a product, or in other words, is no longer applicable to older versions or configurations of a product. Updates can also supersede other updates if modifications have been made to expand language support. For example, a later revision of a product update for Microsoft Office might remove support for an older operating system, but add additional support for new languages in the initial update release.

Conversely, an update that is superseded by another update does the following:

Fixes a similar vulnerability in the update that supersedes it. However, the update that supersedes it might enhance the fix or modify the applicability to client computers that the superseded update provides.
Updates earlier versions or configurations of products.

On the WSUS console, the WSUS update page clearly indicates those updates that have a superseded or superseding relationship with an earlier version. The Details tab also includes "Superseded by" and "Supersedes" status information for updates, in addition to KB links containing more information about each update.

WSUS does not automatically decline superseded updates, and it is recommended that you do not assume that superseded updates should be declined in favor of the new, superseding update. Before declining a superseded update, make sure that it is no longer needed by any of your client computers. These are three possible scenarios in which you might need to install a superseded update:

If a superseding update supports only newer versions of an operating system, and some of your client computers run earlier versions of the operating system.
If a superseding update has more restricted applicability than the update it supersedes, which would make it inappropriate for some client computers.
If an update no longer supersedes a previously released update because of new changes. It is possible that, through changes at each release, an update no longer supersedes an update it previously superseded in an earlier version.

Expired Updates

An expired update is an update that has been invalidated by Microsoft. An expired update can also be an update that has been superseded by the release of another update (new or revised) that fixes or enhances functionality or applicability offered by the expiring update. In this case, the superseding update should be approved in place of the expired update. An update that is expired can no longer be approved for detection or installation.

Some of the sample such updates

MS10-006 superseded by KB980232
MS10-009 superseded by KB978338
MS10-015 superseded by KB979683

Wednesday, April 28, 2010

I want to download these movies

Monsters, Inc. (Two-Disc Collector's Edition) DVD ~ Billy Crystal
The Jungle Book (Limited Issue) DVD
Pinocchio (Disney Gold Classic Collection

The 7 Habits of Highly Effective People Book

http://rapidshare.com/files/143957910/Stephen_R_Covey_-_The_7_Habits_of_Highly_Effective_People.pdf

the above is the book location you can download it

Tuesday, April 27, 2010

Complete Application Virtualization

Simple Steps

Enable BITS on DP

Enable Checkbox for

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems, and then click the name of the server.

To open the ConfigMgr Distribution Point Properties, in the results pane, right-click ConfigMgr distribution point, and then click Properties. On the General tab ensure Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and Internet-based clients). has been selected. Configuration Manager 2007 client computers that connect to a branch distribution point will run virtual application packages using SMB.
Notes :--Important
You must select Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and internet based clients). or Enable virtual application streaming option on the Virtual Applications tab will not be available.

On the Virtual Applications tab, select Enable virtual application streaming.

To close the distribution point properties, click OK.

Create package “” Install the Virtual Application Virtualization Desktop Client software

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution.
If necessary, expand the Software Distribution node and select Packages. To open the Create Package from Definition Wizard, right-click Packages, and then click New / Package From Definition.
On the welcome page, click Next.
On the Package Definition page, to specify the publisher and definition for the new package, click Browse. Locate and select the AppVirtMgmtClient.sms file. The default location for the AppVirtMgmtClient.sms file is <ConfigMgrInstallationPath>\ Tools \ VirtualApp \ AppVirtMgmtClient.sms. The Name, Version, and Language associated with the specified .sms file are displayed in the Package definition pane. Click Next.
On the Source Files page, select Always obtain files from a source directory to help ensure the latest version of the client software will be available, and then click Next.
On the Source Directory page, specify the directory that contains the source files for the package. This is the directory that contains the Microsoft Application Virtualization Desktop Client or the Microsoft Application Virtualization for Terminal Services installation file depending on the version of the client you are planning to install. Specify the source location by providing the UNC path. Alternatively, click Browse to specify the location that contains the setup files for the type of client you want to install. Click Next.
On the Summary page, review the Details for the package definition file. To create the package definition file and close the wizard, click Finish. To access the new package select the Packages node and the package will be available in the results pane.
If you installed the Microsoft Application Virtualization for Terminal Services client, after the package has been created, you should select the Packages node, right-click the package in the in the Results pane and select Properties. On the General tab, update the Name of the package so that it reflects that it is the terminal services version of the client.

Enable Client Agent Settings:-

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Client Agents.
Right-click Advertised Programs Client Agent, and then select Properties.
On the General tab, to enable the client agent for running virtual applications, click Allow virtual application package advertisement.
Click OK to exit the properties dialog box.

To work with clients you need below two software's requirements

The Microsoft Application Virtualization Desktop Client requires the following prerequisites be installed on the Configuration Manager 2007 client computer:

Microsoft Application Error Reporting – The install program for this software is included in the Support folder in the self-extracting archive file.
Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) – For more information about installing Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) http://go.microsoft.com/fwlink/?LinkId=116683

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) Silent install
This option will suppress all UI during installation.

Vcredist_x86.exe /q:a /c:"msiexec /i vcredist.msi /qn /l*v %temp%\vcredist_x86.log"

You need to import the (.xml) virtual package then you can create package and advertisement

my mistakes

I missed out Dynamic IT and Dynamic Systems in year 2003 and cry...............................I want to stop now... I will try my best

MMS 2010 Live @

http://www.studiosevent.com/newscenter/?id=mms

do you love mms then check it out here

Seven Habits of Highly Effective People

HABIT ONE: BE PROACTIVE®

HABIT TWO: BEGIN WITH THE END IN MIND®

HABIT THREE: PUT FIRST THINGS FIRST®

HABIT FOUR: THINK WIN – WIN ®

HABIT FIVE: SEEK FIRST TO UNDERSTAND THEN TO BE UNDERSTOOD®

HABIT SIX – SYNERGISE®

HABIT SEVEN: SHARPEN THE SAW®

Sunday, April 25, 2010

To test the SCCM Console Connectivity with the WMI

Console connectivity test WMI
Start à Run
2.       Type “wbemtest” and hit Enter
3.       Hit the Connect button
4.       In the namespace box, type “root\sms\site_XXX” (where XXX is your site code)
5.       Click Connect

Friday, April 23, 2010

This is a test post

Thursday, April 22, 2010

What's New in Configuration Manager 2007 R3

Source :- Microsoft Website

What's New in ConfigMgr07 R3

What's New in Configuration Manager 2007 R3

The following features are new and apply only to Configuration Manager 2007 R3:

· Power Management. Provides a set of tools to allow the site administrator to configure standard Windows power settings across computers

· Operating System Deployment Enhancements. Prestaged Media is a way to integrate with OEM factory imaging in order to leverage imaging at the OEM to speed up new hardware deployments

· Dynamic Collection Evaluation. Allows you to more rapidly evaluate a collection membership by adding only newly discovered resources.

· Delta Discovery. Performs an intermediate discovery cycle adding only new resources to the Configuration Manager 2007 database.

· Collections. Allows you to search for and add resources to the specified collection.

· Desired Configuration Management. Allows you to easily create collection of compliant or noncompliant computers in desired configuration management.

· Supported Clients Per Hierarchy: Configuration Manager 2007 R3 supports up to 300,000 clients per hierarchy when using 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.

About Dynamic Collection Evaluation in Configuration Manager 2007 R3

Query-based collections in Configuration Manager 2007 are periodically evaluated, based on a schedule you specify to update their membership from the site database. Even if there are no changes in the collection being evaluated, the entire collection is still processed. The default period between collection evaluations is 1 day. You can decrease this period, but evaluating collections with many members might cause a high load on your site database.

Dynamic collection evaluation in Configuration Manager 2007 R3 allows you to evaluate only resources that have been newly added to a collection. Because this improves the speed at which you can evaluate collections and lessens the processing load on the site database, you can increase the frequency by which you evaluate collections and therefore keep the data shown in the administrator console more up to date.

Important: Dynamic collection evaluation does not replace the existing method of collection evaluation; it only evaluates newly added resources

The following resources can be evaluated by dynamic collection evaluation:

· Resources that have been initially discovered.

· Resources that have been provisioned with operating system deployment.

· Resources that have been scanned for initial hardware inventory.

· Resources that have been upgraded to a newer version of the Configuration Manager 2007 client.

About Delta Discovery in Configuration Manager 2007 R3

Delta Discovery in Configuration Manager 2007 R3 enhances the discovery capabilities of the product by discovering only new or changed resources in Active Directory instead of performing a full discovery cycle. The interval by which delta discovery searches for new resources can be configured by the user to a short interval as discovering new resources only does not affect the performance of the site server as much as a full cycle. Delta discovery can detect the following new resource types:

· Computer objects

· User objects

· Security group objects

· System group objects

Important: Delta discovery is not a replacement for other Configuration Manager 2007 discovery methods. Because it only finds new or modified resources in Active Directory, it must be used in conjunction with a discovery method that performs a full synchronization with Active Directory

Note: Delta discovery only reads Active Directory attribute changes which are replicated. Non-replicated attributes which are changed such as the memberof attribute are not collected by delta discovery unless a change to a replicated attribute is made at the same time. Delta discovery is not enabled by default in Configuration Manager 2007 R3. When enabled, it will run, by default every 5 minutes

About Prestaged Media in Configuration Manager 2007 R3

Prestaged media for Configuration Manager 2007 R3 operating system deployment contains bootable media and image files that are copied to the hard drive of a computer. Prestaged media works in conjunction with your existing task sequences to provide a complete operating system deployment. The media can be accessed locally by a task sequence to install a new operating system instead of downloading them across the network. This allows operating system deployment where the computer cannot otherwise be provisioned completely. It can also reduce network traffic when deploying operating systems while still taking advantage of task sequences.

Prestaged media is generally copied to the hard drive of a new computer as a part of the computer manufacturing process or at an enterprise staging center before the computer is sent to the end user. The prestaged media consists of a .wim file that can be prestaged on a “bare metal” computer. When the computer boots for the first time after the prestaged media has been loaded, the computer will boot to WinPE and connect to the site management point to check for available task sequences.

When creating prestaged media, ensure the boot image you are using has the appropriate network and mass storage drivers need for the system to complete the provisioning process.

About Simplified Resource Management

Allows Administrators to search for and add resources to the specified collection using right click tool.

About Power Management in Configuration Manager 2007 R3

The Microsoft System Center Configuration Manager 2007 R3 power management feature provides a set of tools and resources that can help apply power settings to client computers in the enterprise and monitor the power usage of computers. Click the associated link in the following section for detailed information about planning, configuring, managing, monitoring and troubleshooting power management.

Overview of Power Management

Power Management in Microsoft System Center Configuration Manager 2007 R3 addresses the need that many organizations have to monitor and reduce the power consumption of their computers. The feature leverages the power management features built in to Windows to apply relevant and consistent settings to computers in the organization. Different power settings can be applied during and outside of working hours. For example, it might be acceptable to apply a more restrictive power plan during non-peak hours. In cases where computers must always remain switched on, you can prevent power management settings from being applied.

There are three major components to power management in Configuration Manager 2007 R3:

1. Monitoring and Planning: Power Management extends the hardware inventory of Configuration Manager 2007 to collect information about computer usage and power settings for computers in the site. A number of reports are provided to allow you to analyze this data and determine optimal power management settings for computers.

2. Enforcement: Power management allows you to create power plans which can be applied to collections of computers in your site. These power plans configure Windows power management settings on computers. You can use the built in Windows power plans, Balanced, High Performance and Power Saver or you can configure your own custom power plans. Different power plans can be configured for peak and non-peak working hours.

3. Compliance: After applying power plans to computers in your organization, you can run reports to validate that power settings were correctly applied and to calculate power savings across collections of computers.

About Reports for Power Management

Power management in Configuration Manager 2007 R3 contains a number of reports to help you to analyze power consumption and computer power settings in your organization. These reports require SQL Reporting Services which was introduced in Configuration Manager 2007 R2.

Power Management Plan Settings for Power Management

Power plans in Configuration Manager 2007 R3 contain Windows power management settings which can be configured and applied to collections of computers in your Configuration Manager 2007 R3 site.

Important: Depending on the version of Windows you are using, some settings might not be configurable on the destination client computer. For more information about the settings supported by your version of Windows, see your Windows documentation

Prerequisites for Power Management

Power management in Configuration Manager 2007 R3 has both external dependencies and dependencies within the product.

Configuration Manager 2007 Dependencies

The following table describes the dependencies within Configuration Manager 2007 for using power management.

Dependency

More Information

The site server must be running Configuration Manager 2007 R3.

Power management requires Configuration Manager 2007 R3.

Client computers in your site must be running the Configuration Manager 2007 R3 client software.

For information about upgrading the Configuration Manager 2007 client software, see Planning and Deploying Clients for Configuration Manager 2007.

The Configuration Manager 2007 hardware inventory client agent must be enabled for the site in which you are using power management.

Power management in Configuration Manager 2007 R3 uses information collected by hardware inventory. To use power management, you must first enable hardware inventory for the site.

The site must be enabled for power management.

Before you can use power management in Configuration Manager 2007 R3, you must enable the power management client agent.

SQL Reporting Services integration must be installed and configured.

The provided reports for power management require SQL Reporting Services to run. SQL reporting services integration was introduced in Configuration Manager 2007 R2 and is also included with Configuration Manager 2007 R3. For information about installing and configuring SQL Reporting Services, see SQL Reporting Services in Configuration Manager 2007 R2.

Dependencies External to Configuration Manager 2007

The following table describes the dependencies within Configuration Manager 2007 for using power management.

Dependency

More Information

The site must have access to an installation of Microsoft SQL Reporting Services.

Power management in Configuration Manager 2007 R3 uses SQL Reporting Services to display reports. SQL reporting services must be installed and configured for Configuration Manager 2007 before you can display these reports. For more information, see SQL Reporting Services in Configuration Manager 2007 R2.

How to Enable or Disable the Power Management Client Agent

Enabling the power management client agent in Configuration Manager 2007 R3 makes it possible for client computers in this site to apply power management plans configured in the Configuration Manager console.

The power management client agent is not enabled by default when you install Configuration Manager 2007 R3.

Important: The power management feature in Configuration Manager 2007 R3 uses data from hardware inventory on client computers to work, therefore, enabling the power management client agent will also enable the hardware inventory client agent on computers in your site. If you disable the hardware inventory client agent for your site, the power management client agent will also be disabled. Disabling the power management client agent prevents computers in your site from applying power plans created in the Configuration Manager console.

Note: The content in this document is subject to change at any time.

What's New in Configuration Manager 2007 R3

Just released

What's New in ConfigMgr07 R3