Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MMC 1
- Thread starter vonniago
- Start date
-
1
- #2
butchrecon
MIS
Microsoft Management Console. I hope this FAQ can help. Its kinda long but should do the trick. ;-)
Microsoft Management Console (MMC): Frequently Asked Questions
Microsoft Corporation
What's MMC?
Microsoft Management Console (MMC) is an ISV-extensible, common console framework for management applications. MMC is part of Windows NT and runs on NT 4.0 and later versions or Windows 9x. MMC enables developers to create of a set of integrated tools, each of which perform a specific task. Taken by itself, MMC is only a container, often referred to as the tool host. MMC doesn't provide any management behavior, but it does provide a common environment for snap-ins, which can be provided by Microsoft, ISVs, and in-house developers. Snap-ins, which are extensions to the tool host, add the actual management functionality.
The MMC environment is the common link between snap-ins and it provides for integration between snap-ins--even those developed by different vendors. By selecting specific snap-ins and combining them, you can create consoles exactly tailored to your management needs. You can then save the tools you've created for later use or for sharing with other administrators. As a further benefit, the groups of snap-ins that you save as a tool can be forwarded to others delegated to perform specific tasks. Any time you re-open a tool you've created, it will be in the state that you last saved it.
MMC is a core part of Microsoft's management strategy. In the NT 4.0 Option Pack, MMC snap-ins are provided for Internet Information Server, Microsoft Transaction Server, Microsoft Index Server, Simple Mail Transport Protocol (SMTP), and Network News Transport Protocol (NNTP). Two snap-ins are included with SNA Server. Microsoft has over 80 snap-ins currently under development, some of which will ship with the release of Windows 2000.
Snap-ins come in two flavors: stand-alone and extension. A stand-alone snap-in provides functionality even if it's loaded alone in a console that contains no other snap-ins. An extension snap-in, on the other hand, provides functionality only when invoked by a parent snap-in. An extension snap-in can add nodes to the namespace or just extend existing nodes with new menus, toolbars, property pages, wizards, or Help screens.
Positioning
What is the benefit of MMC for a customer?
MMC will deliver a highly flexible and well-integrated management console to administrators. The purpose of MMC is to create a set of integrated tools that each perform a specific task. On its own MMC is only a "container" (known as the "tools host"
. Snap-Ins are extensions to the host that add management functionality. By using Snap-Ins together customers can create administration consoles exactly tailored to their needs. Given that these grouping of snap-ins tools can be saved into a tool, they can also be forwarded to others delegated to perform a specific task. At any time a tool is reopened, it will be in exactly the state as when it was last saved.
Will the existing Windows NT® tools become part of MMC?
Yes. All Windows NT administration tools are being redeveloped as MMC Snap-Ins.
Does MMC replace System Management Server?
No. MMC complements System Management Server. MMC only provides a point from which administration can take place, it does not provide alternative functionality to System Management Server. The System Management Server Admin Console user interface is being redeveloped as a series of MMC Snap-Ins. (Note: The core functionality of System Management Server is provided by services that have no console components. These are unaffected by integration of System Management Server Admin into the MMC and will continue to exist as they do today.)
MMC and ISVs
Do ISVs and management partners have to use MMC?
No. There is great value in using the MMC as an integration point, but there is no requirement.
What is the benefit of MMC for an ISV?
MMC makes it easy for ISVs to create well-integrated management tools. It also offers ISVs the ability to integrate seamlessly with other MMC Snap-Ins (including those provided by Microsoft).
Why should ISVs write Snap-Ins?
On the Windows® operating system, this will become the way to build management applications. Using the console paradigm will not only make components easier to manage, it will also permit tool integration with the products from other vendors.
Can MMC support any protocol?
Yes. This is because it is the Snap-Ins, not the MMC, that are responsible for supporting whatever protocols they need. The MMC is totally protocol independent. The MMC will support any combination of Snap-Ins, using any combination of protocols. This was a key design goal in the development of MMC.
Will my current Win32® calls work?
Absolutely. The MMC is protocol independent. Think of MMC as a collection of functions that assist management applications in displaying their views and in integrating with each other.
Will MMC integration be a requirement for BackOffice® Logo approval in the future?
No plans at this time.
MMC and Enterprise Platforms
Does Microsoft see MMC as a replacement for enterprise platforms such as HP OpenView and CA Unicenter?
No. MMC complements enterprise platforms by providing well-integrated, task-based management functions that have the potential to be integrated into the platform in exactly the way management applications are integrated today.
Could MMC become a key component within future enterprise platforms?
Yes. MMC has the potential to make a great integration point for the UI components of future enterprise platforms.
Does Microsoft have plans to make an enterprise management platform?
No. Microsoft is committed to making the components that make it easy for partners to use Windows to host enterprise management solutions. It is also committed to providing best of breed management of the Windows environment.
Can I write an application for an enterprise platform such as HP OpenView that will fit into the MMC?
Yes. You will need to write your product as a Snap-In for MMC, but there is no reason why this should not be linked so that it is launched from HP OpenView for Windows® or Windows NT® operating systems. You could also create a Snap-In that is launched by HP OpenView.
MMC and Web Technologies
Why doesn't Microsoft just build all its management functions to work from a Web browser?
Microsoft is designing its admin tools to be web accessible. However, using the right tools for the right job is our prime goal. Our customers demand the best possible admin tools. Web browsers today cannot provide the level of functionality offered by the Windows environment and we will not compromise our customers' needs for the sake of only producing "hot" Web-based tools. On a Windows platform, using Windows technology is the best way to build a tool. Our MMC tool offering will complement our current Web-based Windows NT administration offering.
Can Web-administrable tools/devices be accessed by MMC?
Yes. MMC hosts Microsoft Internet Explorer.
Can MMC be accessed from a Web Browser?
No, but Snaps-Ins can be designed to function in Web browsers as well as the MMC. In doing this, it should be noted that browser technology is not sufficiently advanced to provide the richness of functionality available when a Snap-In is run from within an MMC. However, running a Snap-In as a browser control does allow an operator to manage the system from a browser hosted in a non-Windows environment.
Does the Web-Based Enterprise Management (WBEM) complement the MMC?
Yes. MMC and WBEM have very complementary functions. MMC provides an integrated task-based view of management to an administrator. WBEM defines mechanisms to model the managed systems.
Though MMC is not dependent on WBEM, WBEM will provide a consistent single way for MMC Snap-Ins to access the components and understand the relationship the components have with each other. Where MMC is a Windows-specific technology, WBEM is environment independent. WBEM is therefore able to model the whole system, end-to-end, including networks, hosts, and non-Windows OSes and applications.
Why isn't MMC Java™ Based?
MMC is based on Windows technology to allow us to maximize performance, flexibility, and ease of use. Although MMC itself is not built using Java, when released, MMC will support Snap-Ins developed in Java.
Can Sun's Solstice Java Management API be used with MMC?
Yes. A Snap-In could include JMAPI components.
James Collins
Field Service Engineer
A+, MCP
email: butchrecon@skyenet.net
Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
Microsoft Management Console (MMC): Frequently Asked Questions
Microsoft Corporation
What's MMC?
Microsoft Management Console (MMC) is an ISV-extensible, common console framework for management applications. MMC is part of Windows NT and runs on NT 4.0 and later versions or Windows 9x. MMC enables developers to create of a set of integrated tools, each of which perform a specific task. Taken by itself, MMC is only a container, often referred to as the tool host. MMC doesn't provide any management behavior, but it does provide a common environment for snap-ins, which can be provided by Microsoft, ISVs, and in-house developers. Snap-ins, which are extensions to the tool host, add the actual management functionality.
The MMC environment is the common link between snap-ins and it provides for integration between snap-ins--even those developed by different vendors. By selecting specific snap-ins and combining them, you can create consoles exactly tailored to your management needs. You can then save the tools you've created for later use or for sharing with other administrators. As a further benefit, the groups of snap-ins that you save as a tool can be forwarded to others delegated to perform specific tasks. Any time you re-open a tool you've created, it will be in the state that you last saved it.
MMC is a core part of Microsoft's management strategy. In the NT 4.0 Option Pack, MMC snap-ins are provided for Internet Information Server, Microsoft Transaction Server, Microsoft Index Server, Simple Mail Transport Protocol (SMTP), and Network News Transport Protocol (NNTP). Two snap-ins are included with SNA Server. Microsoft has over 80 snap-ins currently under development, some of which will ship with the release of Windows 2000.
Snap-ins come in two flavors: stand-alone and extension. A stand-alone snap-in provides functionality even if it's loaded alone in a console that contains no other snap-ins. An extension snap-in, on the other hand, provides functionality only when invoked by a parent snap-in. An extension snap-in can add nodes to the namespace or just extend existing nodes with new menus, toolbars, property pages, wizards, or Help screens.
Positioning
What is the benefit of MMC for a customer?
MMC will deliver a highly flexible and well-integrated management console to administrators. The purpose of MMC is to create a set of integrated tools that each perform a specific task. On its own MMC is only a "container" (known as the "tools host"
. Snap-Ins are extensions to the host that add management functionality. By using Snap-Ins together customers can create administration consoles exactly tailored to their needs. Given that these grouping of snap-ins tools can be saved into a tool, they can also be forwarded to others delegated to perform a specific task. At any time a tool is reopened, it will be in exactly the state as when it was last saved. Will the existing Windows NT® tools become part of MMC?
Yes. All Windows NT administration tools are being redeveloped as MMC Snap-Ins.
Does MMC replace System Management Server?
No. MMC complements System Management Server. MMC only provides a point from which administration can take place, it does not provide alternative functionality to System Management Server. The System Management Server Admin Console user interface is being redeveloped as a series of MMC Snap-Ins. (Note: The core functionality of System Management Server is provided by services that have no console components. These are unaffected by integration of System Management Server Admin into the MMC and will continue to exist as they do today.)
MMC and ISVs
Do ISVs and management partners have to use MMC?
No. There is great value in using the MMC as an integration point, but there is no requirement.
What is the benefit of MMC for an ISV?
MMC makes it easy for ISVs to create well-integrated management tools. It also offers ISVs the ability to integrate seamlessly with other MMC Snap-Ins (including those provided by Microsoft).
Why should ISVs write Snap-Ins?
On the Windows® operating system, this will become the way to build management applications. Using the console paradigm will not only make components easier to manage, it will also permit tool integration with the products from other vendors.
Can MMC support any protocol?
Yes. This is because it is the Snap-Ins, not the MMC, that are responsible for supporting whatever protocols they need. The MMC is totally protocol independent. The MMC will support any combination of Snap-Ins, using any combination of protocols. This was a key design goal in the development of MMC.
Will my current Win32® calls work?
Absolutely. The MMC is protocol independent. Think of MMC as a collection of functions that assist management applications in displaying their views and in integrating with each other.
Will MMC integration be a requirement for BackOffice® Logo approval in the future?
No plans at this time.
MMC and Enterprise Platforms
Does Microsoft see MMC as a replacement for enterprise platforms such as HP OpenView and CA Unicenter?
No. MMC complements enterprise platforms by providing well-integrated, task-based management functions that have the potential to be integrated into the platform in exactly the way management applications are integrated today.
Could MMC become a key component within future enterprise platforms?
Yes. MMC has the potential to make a great integration point for the UI components of future enterprise platforms.
Does Microsoft have plans to make an enterprise management platform?
No. Microsoft is committed to making the components that make it easy for partners to use Windows to host enterprise management solutions. It is also committed to providing best of breed management of the Windows environment.
Can I write an application for an enterprise platform such as HP OpenView that will fit into the MMC?
Yes. You will need to write your product as a Snap-In for MMC, but there is no reason why this should not be linked so that it is launched from HP OpenView for Windows® or Windows NT® operating systems. You could also create a Snap-In that is launched by HP OpenView.
MMC and Web Technologies
Why doesn't Microsoft just build all its management functions to work from a Web browser?
Microsoft is designing its admin tools to be web accessible. However, using the right tools for the right job is our prime goal. Our customers demand the best possible admin tools. Web browsers today cannot provide the level of functionality offered by the Windows environment and we will not compromise our customers' needs for the sake of only producing "hot" Web-based tools. On a Windows platform, using Windows technology is the best way to build a tool. Our MMC tool offering will complement our current Web-based Windows NT administration offering.
Can Web-administrable tools/devices be accessed by MMC?
Yes. MMC hosts Microsoft Internet Explorer.
Can MMC be accessed from a Web Browser?
No, but Snaps-Ins can be designed to function in Web browsers as well as the MMC. In doing this, it should be noted that browser technology is not sufficiently advanced to provide the richness of functionality available when a Snap-In is run from within an MMC. However, running a Snap-In as a browser control does allow an operator to manage the system from a browser hosted in a non-Windows environment.
Does the Web-Based Enterprise Management (WBEM) complement the MMC?
Yes. MMC and WBEM have very complementary functions. MMC provides an integrated task-based view of management to an administrator. WBEM defines mechanisms to model the managed systems.
Though MMC is not dependent on WBEM, WBEM will provide a consistent single way for MMC Snap-Ins to access the components and understand the relationship the components have with each other. Where MMC is a Windows-specific technology, WBEM is environment independent. WBEM is therefore able to model the whole system, end-to-end, including networks, hosts, and non-Windows OSes and applications.
Why isn't MMC Java™ Based?
MMC is based on Windows technology to allow us to maximize performance, flexibility, and ease of use. Although MMC itself is not built using Java, when released, MMC will support Snap-Ins developed in Java.
Can Sun's Solstice Java Management API be used with MMC?
Yes. A Snap-In could include JMAPI components.
James Collins
Field Service Engineer
A+, MCP
email: butchrecon@skyenet.net
Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
Simple version: MMC is the one-stop-shop where you can put all your most commonly used admin tools. You log in as Administrator, go to MMC to add your tools, save the console and then you only have to go to one place, instead of remembering about 5 or 6 different paths, to admin your machine.
Use the help files to show you how to work it.
@=)
Catadmin - New to Server Admin, but willing to learn... All help is appreciated.
Use the help files to show you how to work it.
@=)
Catadmin - New to Server Admin, but willing to learn... All help is appreciated.
- Status
Similar threads
- Locked
- Question
- Locked
- Question