IBM Systems Director6.1都有哪些改进？
IBM Systems Director6.1都有哪些改进？
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
IBM Systems Director6.1都有哪些改进？
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（9）
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
这个不知道，不是专门做这个的
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.
这个不知道，不是专门做这个的
A Level-0 managed object is now referred to as an agentless-managed system. This is a system that does not have an agent installed, but can be discovered by IBM Systems Director using SSH, DCOM, or SNMP.
IBM Director Core Services is now referred to as Platform Agent. Platform Agent provides a lighter footprint and fewer management functions than the Common Agent. A system on which Platform Agent is installed is now known as a Platform-Agent managed system rather than a Level-1 managed object.
IBM Director Agent is now referred to as Common Agent. Common Agent provides a rich set of security, deployment, and management function. A system on which Common Agent is installed is now known as a Common Agent managed system rather than a Level-2 managed object.
Managed objects are now called systems, which are hardware endpoints that can be discovered and managed by IBM Systems Director. For example, storage devices, network devices, physical servers, virtual servers, and virtual farms are systems.
Extensions are now known as plug-ins, which are free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function.
:
Job activation is now referred to as job instance, which is a specific occurrence of a job that is running or has completed running.
:
Event action plans are now called Event Automation Plans. These are
user-defined policies that determine how IBM Systems Director automatically handles certain events. An event action plan comprises one or more event filters and one or more customized event actions.
Hardware control points are now known as platform managers. A platform manager is software that manages one or more host systems and their associated virtual servers and operating systems. Platform managers can be started from the IBM Systems Director Web interface. For example, BladeCenter Management Module, IBM Hardware Management Console (HMC), IBM Integrated Virtualization Manager (IVM), and VMware VirtualCenter are platform managers.
What was previously called a configuration profile is now called a configuration plan, which is a collection of templates used to configure hardware and operating systems.
:
Components are now referred to as templates. These are stored versions of definition parameters for the configuration of specific systems.
Remote session is now called the remote command line and still refers to initiating a command-line interface to a remote managed system.