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
software updates
Typically, an update that supersedes other updates does one or more of the following:
Conversely, an update that is superseded by another update does the following:
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:
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
Monsters, Inc. (Two-Disc Collector's Edition) DVD ~ Billy Crystal
The Jungle Book (Limited Issue) DVD
Pinocchio (Disney Gold Classic Collection
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
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 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
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®
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
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.
Just released
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.
=IF(ISNA(VLOOKUP(A:A,B:B:$B$97,2,0)),"No server IS In MY List","Yes server IS In MY List")
New Source Eenadu.net on April 19th 2010
Office 2007 Dump Looks Like this….
Go to command prompt and change the working directory to office dump folder and type "setup.exe" /admin 
then you will see similar to below wizard
enter the values or choose the option that you want to customized then click on file and save now it will save as a FILE.MSP
Now lets try out our saved .MSP file and see if it works correctly before proceeding further
Now let's open CMD.
browse to your install and enter the following switch: "setup.exe" /adminfile file.msp
If this works create an Package and advertisement and push to the systems
Sometimes things just happen, sometimes you accidentally delete the All Systems collection because you were trying to do too many things at once. I’ll fess up, I did it.
Here’s how to restore the collection with the appropriate ID. This solution was given to me by Microsoft Support.
Here is the VBS script that will do the restore:
####begin script
strSMSServer = "."
strParentCollID = "COLLROOT"
'This example creates the collection in the collection root.
'Replace COLLROOT with the CollectionID of an existing collection to make the new collection a child.
strCollectionName = "All Systems"
strCollectionComment = "This is the All Systems Collection."
Set objLoc = CreateObject("WbemScripting.SWbemLocator")
Set objSMS = objloc.ConnectServer(strSMSServer, "root\sms")
Set Results = objSMS.ExecQuery ("SELECT * From SMS_ProviderLocation WHERE ProviderForLocalSite = true")
For each Loc in Results
If Loc.ProviderForLocalSite = True Then
Set objSMS = objLoc.ConnectServer(Loc.Machine, "root\sms\site_" & Loc.SiteCode)
End if
Next
Set newCollection = objSMS.Get("SMS_Collection").SpawnInstance_()
'Create new "All Systems" collection
newCollection.Name = "All Systems"
newCollection.OwnedByThisSite = True
newCollection.Comment = strCollectionComment
newCollection.CollectionID = "SMS00001"
path = newCollection.Put_
'Set the Relationship
Set newCollectionRelation = objSMS.Get("SMS_CollectToSubCollect").SpawnInstance_()
newCollectionRelation.parentCollectionID = strParentCollID
newCollectionRelation.subCollectionID = ("SMS00001")
newCollectionRelation.Put_
####end script
Once you’ve recreated the collection with the appropriate ID, then you’ll have to import the All Systems query for your membership rules.
The Preload Package Tool (PreloadPkgOnSite.exe) is used to manually install compressed copies of software distribution package source files on Configuration Manager 2007 sites. After package source files are installed, a status message is sent up the site hierarchy indicating the presence of the new package source files. This avoids sites higher in the hierarchy from copying package source files over the network when distribution points at child site are selected to host software distribution package content that has already been preloaded on them.
The following feature enhancements have been made to the tool since it was released in the SMS 2003 Toolkit:
To check if a Management Point is up and running we have the mplist and mpcert http URLs that we can open in Internet Explorer. We don’t have such URLs to test if a Distribution Point (DP) is up. Management Point and Distribution Point servers are very different roles. The Management Point is a conduit for the clients to get information from the SQL database i.e. their cert, their machine policy, etc. That is why there is a way to use an http link to get that information from SQL through the MP. A DP is nothing but a server share. To use BITS for downloads, we expose that share through a virtual IIS directory.
There is no http link with a cert on a DP that we can query on, but you can create a package just to test the DP health. Here is how:
1. Create a text file and write in it whatever you want to see when you use the http URL to test the DP.
2. Rename that file and change the txt extension to html.
3. Create a package that only contains that file and add your distribution points to the package.
4. Get the package ID and then go to the IIS Manager console and find the name of the DP virtual directory and make sure there is a folder for your DP health package.
5. Use IE and type the URL for the server, the virtual IIS directory, the package ID folder, and then your html file. In my case it looks like this:
http://sccm/sms_dp_smspkge$/zzz0002e/dphealth.html
6. You should get back the content of the text file you created on step one:
If you get the content of your html file back, your BITS enabled DP is up.
Our helpdesk asked me to make a task sequence that can be used on computers with more than one partition. In this case, I had to make sure that the operating system will install only on first partition and will not touch the data on other partitions.
To achieve this, I copied another TS and modified the following 2 steps:
This way, when TS runs, it automatically wipes partition 1 from disk 0 and will not touch any other partition or disk.
=============================================================================================
In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences. Suppose you already created or imported a new Microsoft Deployment Task Sequence. If not, do it now.
Select the desired Task Sequence and click Edit in the Actions pane
In the <Name> Task Sequence Editor window, in the left pane select Format and Partition Disk
Now you’ll see this volume in the task sequence editor.
To add another partition click the yellow star again and fill in the following details:
In the Partition name type the name of your partition, this will be you disk D:
Under Partition options, select the Partition type as Primary
To use all the remaining disk space, select “Use a percentage of remaining free space” and set the Size(%) to 100
Under Formatting options, choose the file system you want and check the Quick format checkbox (optional)
Under Advanced options write a Variable name
Click OK when you’re done making your changes
Now you’ll see both volumes in your task sequence editor window. Next time you will deploy an operating system, the hard disk will format and create 2 partitions (C: and D:) and your computer will boot from the first partition (C:).
How does SCCM know that it needs to apply the OS image on the first partition and not the second? Well, it doesn’t, we will set this up in the “Apply Operating System Image” task.
In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences.
Select the desired Task Sequence and click Edit in the Actions pane
In the <Name> Task Sequence Editor window, in the left pane select Apply Operating System Image
If you are installing the OS using the source media, then choose “Apply operating system from an original installation source” option using Browse choose one of the installation packages you have created when making the task sequence
If you have captured and OS image previously as a .wim file, you can select “Apply operating system from a captured image” option and select the image you want
Check to use a sysprep answer file and select the package using the Browse button
Now is the time to tell SCCM where you want your image to be applied.
- To apply the image on a specific partition, under Destination select “Specific disk and partition”. Under Disk select 0 (zero) and under Partition select 1 (first partition). This is the option I use every time
- To apply the image on the C: partition, under Destination select “Specific logical drive letter”. Under Disk letter select C:
This is it about these two tasks. Of course these tasks can be further customized using the Option tab of each task.
SELECT TOP (100) PERCENT ReportID, Name, Category, DrillThroughReportID
FROM dbo.v_Report
WHERE (NOT (DrillThroughReportID IS NULL))
ORDER BY ReportID
SELECT TOP (100) PERCENT Client_Version0 AS [ConfigMgr client version], COUNT(Client_Version0) AS Total
FROM dbo.v_R_System GROUP BY Client_Version0, Client0 HAVING (Client0 = 1)
ORDER BY Total DESC, [ConfigMgr client version]
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 SMS_R_System.ClientVersion != "4.00.6487.2000"
This way, system resources with older client version will be members of this collection.
CCMSETUP.EXE /noservice SMSSITECODE=CFM SMSCACHESIZE=1024 SMSSLP=CFM.DOMAIN.COM SMSMP=CFM.DOMAIN.COM RESETKEYINFORMATION=TRUE
Now, as system resources with older client version are members of this collection they will receive the advertisement and will silently install the latest ConfigMgr client.
When the collection will have no system resources, I will know that all clients are upgraded. Also, I can check this by opening the same report from any browser on any computer.
Method one:- With SCCM build and capture
Method two : WDS capture Wizard
method three: details steps are below
Depending on what you need the .wim file for, you can create it manually or automatically.
- To manually create a .wim file (capture image) you need a bootable CD with Windows PE (with ImageX.exe included) that you can create using Windows Automated Installation Kit.
The basics steps are:
Where: C: is the partition to be captured; D:\CapturedImage.wim is the place of the captured file; “My captured image” is the name of the file.
More switches can be found on the ImageX Command-Line Options page.
If you need the image for deployment, do not forget to run sysprep before capturing the image!
- To automatically create a .wim file you can use a capture media created using Configuration Manager.
If you want to capture a Windows XP OS, copy sysprep files to C:\sysprep. Newer operating systems have sysprep files installed by default.
To use capture media:
As Microsoft recently released Service Pack 2 for Office 2007 suite, it is a good idea to add the update files to the package so it it can be deploy during the installation.
So, first of all we have to download the SP2 executable file from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en (see additional information bellow).
Then, using a command prompt window, extract the content of the package to a folder you can browse to.
Accept EULA and click Continue.
Select a folder to extract the files to.
When the extraction is complete, you should have the following files:
At this point, you can delete the office2007sp2-kb953195-fullfile-en-us.exe file. Copy the other 9 files to “Updates” folder from your Office 2007 source folder.
Now you only have to update the distribution point/s and the next time Office 2007 will install, it will apply the SP2 update during Office 2007 installation.
The same steps are valid for Visio and Project 2007.
Microsoft Office Visio 2007 Service Pack 2 (SP2) can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?familyid=78E36742-8BDA-471E-88E6-9B561BB06258&displaylang=en.
Microsoft Office Project 2007 Service Pack 2 (SP2) can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c126fa4a-b43f-4f7e-a9d4-522e92a6cfee.
When using task sequence, you might want to install different driver packages for different computer models. This can be accomplished by using a WMI query.
First of all you need to have driver packages for all your computer models and know the exact model name for every computer.
To find this, open a command prompt and type WMIC ComputerSystem GET Model (use this command on every computer to find it’s model).
Then, Edit your task sequence. Add how many steps you need with “Apply Driver Package”. Select the driver package you have created for a certain computer model (HP dc5700 in my case).
In the Options tab, click Add Condition and select Query WMI. In the WMI Query Properties window, make you sure you have root\cimv2 as WMI Namespace and write the following query in the WMI Query input box:
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%dc5700%” for HP Compaq dc5700 computer models.
Now, for every driver package, replace the model name with the computer model name the driver package is for. This way, the task sequence will install the correct drivers on every computer that will match the model specified in the query and will skip other steps sending the following status message: “The task sequence execution engine skipped the action (HP Compaq dc5700) in the group (Apply driver packages) because the condition was evaluated to be false”.
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_R_System.OperatingSystemNameandVersion not like "%Server%" and SMS_G_System_COMPUTER_SYSTEM.Name not in (select distinct SMS_G_System_COMPUTER_SYSTEM.Name from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Adobe Reader 9%")
The TS Looks like this… to install software using a TS, is to have only Install Software steps. This way, you can install multiple software products using one advertisement instead of advertising every package. I use this only when I have an OS installed and I want to install software on it.
This is how such a TS looks like: 
The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives you full control over the installation process, allowing you to set:
The usual form of the msiexec command line is this:
msiexec.exe <install_option> <path_to_package> [package_parameters]
When launching an installation package, you can set the install type through these options:
Chicago
![Wiping volume C:\](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_saXk3jB9Ok5DxahqAiZKUZYX5jHp1chhCM2jNQfM1SbBuQfJQCPsaF8sijXGbaxy9FmcnS43TFmqRGyX_ILCaaT-yiK0LHTztUKeOPk2BotyRi6t-qBhcwJNM2J81UDYZmTY_Wh94-aq9aAJ30EFwgVsnVqWn65FV_EIA=s0-d "Wiping volume C:\")
msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>Sample command line:
msiexec.exe /i "C:\Example.msi"
The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:
msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]Sample command line:
msiexec.exe /i "C:\Example.msi" /qn
Sometimes an installation overwrites files which are in use or it needs to reboot the machine in order to finish. The reboot policy used by the installation can be set through these options:
msiexec.exe /i <path_to_package> [/norestart][/promptrestart][/forcerestart]
Sample command line:
msiexec.exe /i "C:\Example.msi" /norestart
When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:
msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>Sample command line:
msiexec.exe /i "C:\Example.msi" /L*V "C:\package.log"
The Windows Installer command line can apply or remove updates (patches for example) through these options:
msiexec.exe [/update][/uninstall[/package<product_code_of_package>]] <path_to_package>
Sample command lines:
msiexec.exe /update "C:\MyPatch.msp"
msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318} /package {AAD3D77A-7476-469F-ADF4-04424124E91D}
Tip
If you have an installed package, you can use the Windows Installer command line for repairing it:
msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>Sample command line:
msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}
The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY="value".
Sample command line:
msiexec.exe /i "C:\Example.msi" MY_PROP="myValue"
Correct syntax:
msiexec /i A:\Example.msi PROPERTY=VALUE
Incorrect syntax:
msiexec /i PROPERTY=VALUE A:\Example.msi
Property values that are literal strings must be enclosed in quotation marks. Include any white spaces in the string between the marks.
msiexec /i A:\Example.msi PROPERTY="Embedded White Space"
To clear a public property by using the command line, set its value to an empty string.
msiexec /i A:\Example.msi PROPERTY=""
For sections of text set apart by literal quotation marks, enclose the section with a second pair of quotation marks.
msiexec /i A:\Example.msi PROPERTY="Embedded ""Quotes"" White Space"
The following example shows a complicated command line.
msiexec /i testdb.msi INSTALLLEVEL=3 /l* msi.log COMPANYNAME="Acme ""Widgets"" and ""Gizmos."""
The following example shows advertisement options. Note that switches are not case-sensitive.
msiexec /JM msisample.msi /T transform.mst /LIME logfile.txt
The following example shows you how to install a new instance of a product to be advertised. This product is authored to support multiple instance transforms.
msiexec /JM msisample.msi /T :instance1.mst;customization.mst /c /LIME logfile.txt
The following example shows how to patch an instance of a product that is installed using multiple instance transforms.
msiexec /p msipatch.msp;msipatch2.msp /n {00000001-0002-0000-0000-624474736554} /qb
When you apply patches to a specific product, the /i and /p options cannot be specified together in a command line. In this case, you can apply patches to a product as follows.
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb
Some Sample Commands for EXE files:--
MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL
psexec \\computer_name MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL
cmd='msiexec /qn /i %SOFTWARE%\adobereader93\AdbeRdr930_en_US.msi TRANSFORMS=%SOFTWARE%\adobereader93\AdbeRdr930_en_US.mst'
'msiexec /qn /update %SOFTWARE%\AdobeReader93\AdbeRdrUpd932_all_incr.msp'
'MsiExec.exe /x{AC76BA86-7AD7-1033-7B44-A80000000002} /qn '
msiexec /qn /x{AC76BA86-7AD7-1033-7B44-A93000000001}
msiexec.exe /qn /update "%SOFTWARE%\AdobeReader93\AdbeRdrUpd932_all_incr.msp"'
'msiexec /qb /uninstall "%SOFTWARE%\adobe-reader\AcroRead.msi'
siexec /i "UNCPath\filename.msi" /qn
msiexec /i "UNCPath\filename.msi" /qn PIDKEY="Key value without dashes
jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1
jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /v"/qn ADDLOCAL=ALL IEXPLORER=1 INSTALLDIR=D:\java\jre"
start /w jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0n1n2n3n4n50}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0151020}
Creating a Log File
If you want to create a log file describing the installation/uninstallation, append /L C:\<path>setup.log to the install/uninstall command. The following is an example for installation:
Installation Example
jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /L C:\<path>setup.log
The following is an example for uninstalling:
Uninstalling Example
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000} /L C:\<path>setup.log
Below is available WINZIP MSI File http://download.winzip.com/ov/winzip100.msi
ymsgrie.exe /s /v/passive - install Yahoo! Messenger silent, with progress bar
The /S switch for silent install of TEAMVIEWER WORKS!
but you must do the following :
download the program (preferably the latest version) ..or ..if you have it on your hard drive , open it... (AND LET IT OPEN! DO NOT CLOSE OR INSTALL THE APLICATION. JUST DUBLE-CLICK IT!!)
Then , go to C:\Documents and Settings\Administrator\Local Settings\Temp. There you'll see a folder called TeamViewer. Open that folder. Inside you'll have 2 files. Teamviewer.exe and tvinfo.ini
Copy the Teamviewer from that folder and paste wherever you want. After this you can close the other application.
With the new teamviewer.exew which you copyed from the temp folder , u can run it sillently. Use the /S Switch. Works with WPI also.
If you find MSiexec has problem then you can run below two commands
msiexec /unregister ---> for unregistering the windows installer
msiexec /regserver---> for registering the windows installer
Released Versions of Windows Installer
The table in this topic identifies the released versions of the Windows Installer.
Release
Version
Description
Windows Installer 2.0
2.0.2600.0
Released with Windows XP.
Windows Installer 2.0
2.0.2600.1
Released with Windows 2000 Server with Service Pack 3 (SP3).
Windows Installer 2.0
2.0.2600.1183
Released with Windows 2000 Server with Service Pack 4 (SP4).
Windows Installer 2.0
2.0.2600.2
Released as a redistributable.
Windows Installer 2.0
2.0.2600.1106
Released with Windows XP with Service Pack 1 (SP1).
Windows Installer 2.0
2.0.3790.0
Released with Windows Server 2003.
Windows Installer 3.0
3.0.3790.2180
Released with Windows XP with Service Pack 2 (SP2). Released as a redistributable.
Windows Installer 3.1
3.1.4000.1823
Released as a redistributable. This version is has the same functionality as version 3.1.4000.2435.
Windows Installer 3.1
3.1.4000.1830
Released with Windows Server 2003 with Service Pack 1 (SP1) and Windows XP Professional x64 Edition. Update this version to version 3.1.4000.2435 to address the issue discussed in KB898628.
Windows Installer 3.1
3.1.4000.3959
Released with Windows Server 2003 with Service Pack 2 (SP2).
Windows Installer 3.1
3.1.4000.2435
Released with a fix to address the issue discussed in KB898628. This is the latest version of Windows Installer 3.1.
Windows Installer 3.1
3.1.4001.5512
Released with Windows XP with Service Pack 3 (SP3).
Windows Installer 4.0
4.0.6000.16386
Released with Windows Vista.
Windows Installer 4.0
4.0.6001.18000
Released with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008.
Windows Installer 4.5
4.5.6002.18005
Released with Windows Vista with Service Pack 2 (SP2) and Windows Server 2008 with Service Pack (SP2.)
Windows Installer 4.5
4.5.6000.20817
Released as a redistributable for Windows Vista.
Windows Installer 4.5
4.5.6001.22162
Released as a redistributable for Windows Server 2008 and Windows Vista with SP1.
Windows Installer 4.5
4.5.6001.22159
Released as a redistributable for Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with SP1 and later.
Windows Installer 5.0 is released with Windows Server 2008 R2 and Windows 7.
To create exe file by using winrar for silent installation / Self Extractor
create SFX archive”. Change the archive name if you like but it must have the .exe extension.
Switch to the Advanced tab and select “SFX options” to open Advanced SFX options window.
On the General tab in the “Path to extract” box type the path you want to extract the installer to. Make sure it is the same path you have in the antivir.cmd file. Then in the “Run after extraction” box type in the path to the antivir.cmd file.
Change to the Modes tab and select the “hide all” and “overwrite existing files” radio buttons.
Close the “Advanced SFX Options” window by clicking OK, then click OK on the “Archive name and parameters” window to start creating the installer. The finished installer is created in the antivirpec folder.
Also you can do with 7zip where you will have more options compare to winrar or winzipself extractor.
So here is his tip on how to create a customized MSP file with OCT:
Further more, with OCT you can customize almost everything regarding how your Word/Excel etc. applications will run. What I liked most is the possibility to create the default profile in Outlook if you are using an Exchange server in your organization.
Don’t forget to save the MSP file and to put the file in Updates folder or to use /adminfile <path to MST file> switch .
Hope I will try to post when i get some time
Always read the Release Notes for the patch you are about to install. The Release Notes usually contain information on known issues with the patch and specific procedures on how to install them.
Online hosted virtual machines : http://www.microsoft.com/systemcenter/configurationmanager/en/us/virtual-labs.aspx
Downloadable VHD of with sccm 2007 R2 installed. http://www.microsoft.com/downloads/details.aspx?familyid=E0FADAB7-0620-481D-A8B6-070001727C56&displaylang=en
Success:
0
Reboot:
1604
1641
3010
3011
Retry*:
4
5
8
13
14
39
51
53
54
55
59
64
65
67
70
71
85
86
87
112
128
170
267
999
1003
1203
1219
1220
1222
1231
1232
1238
1265
1311
1323
1326
1330
1618
1622
2250*) A retry exit code will force SMS/SCCM to rerun the advertisement after a timeout of 10 minutes.
The Microsoft Assessment and Planning (MAP) Toolkit is an agentless toolkit that finds computers on a network and performs a detailed inventory of the computers using Windows Management Instrumentation (WMI) and the Remote Registry Service. The data and analysis provided by this toolkit can significantly simplify the planning process for migrating to Windows® 7, Windows Vista®, Microsoft Office 2007, Windows Server® 2008 R2, Windows Server 2008, Hyper-V, Microsoft Application Virtualization, Microsoft SQL Server 2008, and Forefront® Client Security and Network Access Protection. Assessments for Windows Server 2008 R2, Windows Server 2008, Windows 7, and Windows Vista include device driver availability as well as recommendations for hardware upgrades.
Note MAP supports x86 and x64 versions of operating systems.
Download Location
SQL Server 2008 Express Edition is a fantastic option for those seeking the power of a full-featured relational database but with low performance requirements. It replaces the Microsoft Data Engine (MSDE) as the free version of SQL Server for application development and lightweight use. It remains free and retains the limitations of MSDE with respect to client connections and performance. It’s a great tool for developing and testing applications and extremely small implementations, but that’s about as far as you can run with it.
SQL Server 2008 Express has the following features and limitations:
Ohh.. my systems dead slow after joins here… they given me T61 with 1 GB.. Where my system taking more than 1 Gb almost every time I am working my Page file….
I checked this utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.
Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system. Also included in the download package is a command-line equivalent that can output in CSV format, Autorunsc.
You'll probably be surprised at how many executables are launched automatically!
Here is the link to download http://live.sysinternals.com/autoruns.exe
