Hilfe
Neues Thema
Antworten
Zitat
Microsoft posts beta of new installer software
Microsoft Corp. Friday shipped the first beta of a software installer that is one key piece in a forthcoming overhaul of the company’s patch management architecture.
Microsoft Installer (MSI) 3.0, now available to users in the beta program, will become one of two installer technologies that will replace the jumble of eight installers Microsoft has today for installing patches.
MSI 3.0 will be used for most applications, while Update.exe will be the installer for the operating system.
In June, Microsoft admitted that its patch management architecture was broken and vowed to fix it, reducing the number of installer technologies and creating one comprehensive site where users could find patches for all Microsoft products.
A mish-mash of patch resources has fueled complaints for years that Microsoft’s patch management system is tainted by inconsistencies in how to find, deploy and verify a patch was installed.
Scott Culp, senior security strategist for the Trustworthy Computing team at Microsoft, said MSI 3.0 will be compatible with Windows Server 2003, Windows XP and Windows 2000 with Service Pack 3 and higher. Once users add MSI 3.0 to those platforms, Culp says they will be able to take advantage of changes Microsoft is making to its patch management infrastructure.
MSI 3.0, which includes improvements in authoring, creating, distributing and managing updates to applications, is expected to ship by mid-2004. It is designed to reduce the number of reboots needed when installing patches and other software, eliminate the calamity of file versions overwriting one another and improve the rollback of installations. MSI 3.0 also will allow the installation or removal of more than one patch at a time, but allows patches installed as part of a batch process to be uninstalled individually.
By the end of 2004, Microsoft expects to converge all products onto MSI 3.0 and Update.exe.
The installer technologies will be baked into Microsoft products starting with the Longhorn wave of software, according to Microsoft. The wave is expected to begin with a new desktop OS in 2005 or 2006.
Today, Windows Update only supplies patches for Windows, and users must go to other sites to find patches for other products. To add to the confusion, other products - such as SQL Server, Exchange and Office - all have their own unique technologies for installing patches.
Microsoft hopes that cutting the number of installers is one step in reducing the burden of patch management.
Microsoft Corp. Friday shipped the first beta of a software installer that is one key piece in a forthcoming overhaul of the company’s patch management architecture.
Microsoft Installer (MSI) 3.0, now available to users in the beta program, will become one of two installer technologies that will replace the jumble of eight installers Microsoft has today for installing patches.
MSI 3.0 will be used for most applications, while Update.exe will be the installer for the operating system.
In June, Microsoft admitted that its patch management architecture was broken and vowed to fix it, reducing the number of installer technologies and creating one comprehensive site where users could find patches for all Microsoft products.
A mish-mash of patch resources has fueled complaints for years that Microsoft’s patch management system is tainted by inconsistencies in how to find, deploy and verify a patch was installed.
Scott Culp, senior security strategist for the Trustworthy Computing team at Microsoft, said MSI 3.0 will be compatible with Windows Server 2003, Windows XP and Windows 2000 with Service Pack 3 and higher. Once users add MSI 3.0 to those platforms, Culp says they will be able to take advantage of changes Microsoft is making to its patch management infrastructure.
MSI 3.0, which includes improvements in authoring, creating, distributing and managing updates to applications, is expected to ship by mid-2004. It is designed to reduce the number of reboots needed when installing patches and other software, eliminate the calamity of file versions overwriting one another and improve the rollback of installations. MSI 3.0 also will allow the installation or removal of more than one patch at a time, but allows patches installed as part of a batch process to be uninstalled individually.
By the end of 2004, Microsoft expects to converge all products onto MSI 3.0 and Update.exe.
The installer technologies will be baked into Microsoft products starting with the Longhorn wave of software, according to Microsoft. The wave is expected to begin with a new desktop OS in 2005 or 2006.
Today, Windows Update only supplies patches for Windows, and users must go to other sites to find patches for other products. To add to the confusion, other products - such as SQL Server, Exchange and Office - all have their own unique technologies for installing patches.
Microsoft hopes that cutting the number of installers is one step in reducing the burden of patch management.
einige der neuen Features (von neowin.net
Zitat
Compatibility
- Packages and patches authored for MSI 2.0 are fully supported on the MSI 3.0 engine. By just installing MSI 3.0 users will be able to benefit from its many servicing improvements. MSI 3.0 patches have additional data tables which are necessary to completely exploit the new features. It is important to note that MSI3.0 patches can be installed by MSI 2.0 – the engine will just ignore the new tables and the associated functionality.
Patch Removal
– MSI 3.0 provides native support to remove small and minor updates (patches). Any patch installed by the MSI 3.0 engine is eligible for removal. The removal of a patch is the functional equivalent of never installing the patch. The state (files, regkeys, etc…) of the product when a patch (or patches) is installed and removed is identical to its state where the patch (or patches) was never installed. Patches can be removed in any order. Patches are removed using the command line or the calling the MsiRemovePatches API.
Sequencing
– The new MSI 3.0 patch sequence table enables authors to provide explicit instructions for the order in which updates should be applied on target machines. Updates will be applied to target products in a consistent and predictable order regardless of the order in which they are physically provided to the target machine. By adding the patch sequence table authors can reliably update un-versioned files. Patches without the sequence table will be applied in the order in which they are provided to the engine.
Performance
– Patches installed with the MSI 3.0 engine will take substantially less time to apply as compared to previous versions. Patching no longer implies a full product reinstall, so the engine does not have to examine all product files during patching operations. MSI 3.0 makes a distinction between product repair and patching and will use a lighter weight reinstall mechanism that only updates the files affected by a patch. MSI 3.0 also reduces needless file copies during patch application to further speed up patching.
Source List API
– MSI 3.0 provides significant enhancements for system administrators to manage the list of sources for products and patches. New APIs will enable full static management of the product sources including network, URL and Media sources and enable access to read, edit and replace the MSI source lists from an external process.
Multiple Patching - MSI 3.0 allows more than one patch to be installed (or removed) in a single installation transaction with integrated progress, rollback, and reboot behavior. Patches installed together in a single transaction can still be uninstalled individually. If one patch in the set obsoletes, supersedes, or touches the same files as other patches in the set, MSI will take this into account. MSI 2.0 patches are fully supported, and there are no additional authoring requirements to enable this functionality.
Inventory APIs
– MSI3.0 supports rich product, feature, component and patch inventory queries. Privileged accounts can use the new inventory APIs to enumerate across user and install contexts.
- Packages and patches authored for MSI 2.0 are fully supported on the MSI 3.0 engine. By just installing MSI 3.0 users will be able to benefit from its many servicing improvements. MSI 3.0 patches have additional data tables which are necessary to completely exploit the new features. It is important to note that MSI3.0 patches can be installed by MSI 2.0 – the engine will just ignore the new tables and the associated functionality.
Patch Removal
– MSI 3.0 provides native support to remove small and minor updates (patches). Any patch installed by the MSI 3.0 engine is eligible for removal. The removal of a patch is the functional equivalent of never installing the patch. The state (files, regkeys, etc…) of the product when a patch (or patches) is installed and removed is identical to its state where the patch (or patches) was never installed. Patches can be removed in any order. Patches are removed using the command line or the calling the MsiRemovePatches API.
Sequencing
– The new MSI 3.0 patch sequence table enables authors to provide explicit instructions for the order in which updates should be applied on target machines. Updates will be applied to target products in a consistent and predictable order regardless of the order in which they are physically provided to the target machine. By adding the patch sequence table authors can reliably update un-versioned files. Patches without the sequence table will be applied in the order in which they are provided to the engine.
Performance
– Patches installed with the MSI 3.0 engine will take substantially less time to apply as compared to previous versions. Patching no longer implies a full product reinstall, so the engine does not have to examine all product files during patching operations. MSI 3.0 makes a distinction between product repair and patching and will use a lighter weight reinstall mechanism that only updates the files affected by a patch. MSI 3.0 also reduces needless file copies during patch application to further speed up patching.
Source List API
– MSI 3.0 provides significant enhancements for system administrators to manage the list of sources for products and patches. New APIs will enable full static management of the product sources including network, URL and Media sources and enable access to read, edit and replace the MSI source lists from an external process.
Multiple Patching - MSI 3.0 allows more than one patch to be installed (or removed) in a single installation transaction with integrated progress, rollback, and reboot behavior. Patches installed together in a single transaction can still be uninstalled individually. If one patch in the set obsoletes, supersedes, or touches the same files as other patches in the set, MSI will take this into account. MSI 2.0 patches are fully supported, and there are no additional authoring requirements to enable this functionality.
Inventory APIs
– MSI3.0 supports rich product, feature, component and patch inventory queries. Privileged accounts can use the new inventory APIs to enumerate across user and install contexts.
angeblich soll man schon in die Newsgroups reinkommen. bei mir zeigt es keine neuen NGs an
. wie ist es bei euch?
Nach oben
