This solution accelerator will help you learn about new updates, processes, and technology that assist customers to more effectively assess their environments to identify Microsoft® Systems Management Server (SMS) 2003 managed and unmanaged Microsoft Virtual Server 2005 and Microsoft Virtual PC 2004 installations, Microsoft SQL Server™ installations, and instances and component-level details for Microsoft Office. It addresses the reduction of risk through identification of machines in the SMS-unmanaged space by providing sample automation scripts and reporting that will assist administrators in the four phases—Assess, Identify, Evaluate and Plan, and Deploy—of the patch management process in preparation for patch deployment with SMS 2003. This solution accelerator is based on Microsoft Operations Framework (MOF) and is built for use with SMS 2003. It provides customers with best practice guidance and automation to assist with establishing a patch management process for assessing, identifying, planning, and deploying patches to the Microsoft platform. It includes mechanisms for reducing risk and increasing reach through assessment and identification of machines in the unmanaged space (those outside of the SMS site boundaries) using sample Microsoft Visual Basic® VBscripts. These scripts provide detailed reports that identify the number of unmanaged machines running Microsoft SQL Server, Virtual Server, and Virtual PC within their environment. This information can assist information technology (IT) and security administrators to build plans for moving these machines into a managed software update and patch infrastructure and thus reduce risk to their environment. In addition, the solution also enables them to more effectively plan and prepare for patching SQL Server, Virtual Server and Virtual PC, and Microsoft Office with SMS 2003. On This PageThe TechnologiesSpecific technologies assessed through sample scripts provided in this solution include: | • | Virtual Server 2005 and Virtual PC 2004 installations to include host and guest operating system type, Virtual Server 2005 guest state (Saved, Stopped, Running), Undoable mode (Enable/Disabled), and combination reporting that joins host and guest sessions into a single view that enables the administrator to prepare for end-to-end patching of virtual computers. | | • | Microsoft SQL Server 2000 installations running on server and desktop operating systems, SQL Server instance names, and installed operating system version. | | • | Microsoft Office component-level details to include Suite (XP, 2000, 2003), ProductID, Install source paths, installation dates, and language versions. This is done by providing automation and guidance to customers on how to extend SMS Hardware Inventory or using SMS Software Inventory, thus complementing and extending existing SMS capabilities. | | • | Patching products not supported by MBSA using SMS 2003 Software Inventory. |
Additional BenefitsIn addition to the automation and best practice guidance, the solution also provides: | • | Three technical appendices that address best practices for patching Microsoft SQL Server 2000, Microsoft Virtual Server 2005 and Microsoft Virtual PC 2004, and Microsoft Office 2000/XP/2003 environments. | | • | More than 48 custom .mof files that can be imported into SMS 2003 for creation of custom collections for improved targeting of Office components. | | • | More than 48 custom .mof files that can be imported into SMS 2003 for creation of custom reports for improved reporting of Office components. | | • | Vulnerability Assessment reports for computers running SQL Server 2000, Virtual Server 2005, and Virtual PC 2004 not managed by SMS. (Vulnerability Assessment reports are generated by using MBSA 1.2.1 and MBSA sample reporting scripts.) |
FeedbackWe always appreciate feedback. Please send your comments or questions regarding this technical guidance to msmfeed@microsoft.com.
| |
