Thursday, April 29, 2010


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

  1. PKI and the DMZ
  2. Locating and repairing broken clients (SCCM and WSUS)
  3. Wouldn't it be nice if the 'copy package to new distribution point' wizard could alphabetize the distribution points?
  4. 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. 
  5. OSD/TS process isn't documented very well from MS
  6. when you have the potential to lose log files and not see what went wrong when.
  7. Slow console!!
  8. App-V Integration in SCCM
  9. Migration Tools-
  10. There is no Microsoft supported migration tool to export packages from SMS to SCCM.
  11. Unable to fix broken Config Manager clients (most of the time) via the SCCM Console
  12. SCCM Client cache (C:\Windows\System32\ccm\cache) does not get cleared automatically after a client reaches its cache limit (5GB) 
  13. WQL/SQL...
  14. OSD....not reliably PXE booting into OSD every time ...Then after clearing advertisement and reboot, will boot into OSD just fine
  15. Lacking the ability to create collections using SQL.
  16. usmt, usb hard discs not being supported, pxe boot slow
  17. Windows Embedded Systems Management
  18. 3rd Party patching
  19. Anything involving Native-mode and PKI.
  20. Client Health

software updates

  1. The ability to postpone the reboot after the installation of updates(SUP).
  2. 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


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

  1. 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.

  2. 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.

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

  4. To close the distribution point properties, click OK.

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

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

  2. 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.

  3. On the welcome page, click Next.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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:-

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

  2. Right-click Advertised Programs Client Agent, and then select Properties.

  3. On the General tab, to enable the client agent for running virtual applications, click Allow virtual application package advertisement.

  4. 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)

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 @


do you love mms then check it out here

Seven Habits of Highly Effective People








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