Armarn
winextreme team | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
взято из SMS 4.0 Technical Library
What's New in SMS 4.0
SMS 4.0 Beta 1 includes the addition of several new features, changes to other functionality, and the removal of some components.
SMS 4.0 Beta 1 is fully functional out of the box, and now includes simple setup improvements that quickly result in a fully functional SMS site. Device Management functionality is now integrated into SMS setup.
Introducing Network Access Protection
Network Access Protection is not designed to secure a network from malicious users. It is designed to help administrators maintain the health of the computers on the network, which in turns helps maintain the network’s overall integrity. For example, if a computer does not have the software updates you require, the computer is found to be noncompliant. SMS NAP enforcement then quarantines the system, allowing remediation using SMS software updates management. Once remediation has taken place and the client is deemed healthy, it is granted access to network resources.
Network Access Protection does not prevent an authorized user with a compliant computer from uploading a malicious program to the network or engaging in other inappropriate behavior.
Operating System Deployment
Operating System Deployment (OSD) provides the SMS administrator with a tool for creating images that can be deployed to computers managed by SMS 4.0, and to unmanaged computers using bootable media such as CD or DVD. The image, a Windows Image (WIM) format file, contains the desired version of a Microsoft Windows operating system and can also include any line-of-business applications that need to be installed on the computer. Operating System Deployment provides the following functionality:
Image capture
User state migration using the User State Migration Tool
Image deployment
Task sequences
Disconnected and Remote Deployment
You can deploy Windows via CD set or DVD with or without network connectivity. WinPE, boot image, and applications can all be stored on removable media.
Advanced Task Sequencing
OSD offers a new task sequence editor with many built-in features that provide flexible operating system deployment.
Changes in Security
Systems Management Server (SMS) 4.0 Beta 1 introduces very few security changes from SMS 2003.
If you are already familiar with SMS 2003 security from reading the Scenarios and Procedures for SMS 2003: Security guide, you need to read only one topic, SMS 4.0 Security
If you are unfamiliar with SMS 2003, read the SMS 4.0 Security Guide to understand the best security practices for SMS 4.0 Beta 1.
Changes in the SMS Administrator Console
SMS 4.0 provides a simplified and intuitive task-based interface. The SMS Administrator console is now multi-threaded, which allows administrators to perform multiple tasks simultaneously.
New Search Functionality in Results Pane
SMS 4.0 offers search and filter functionality in the results pane for appropriate nodes in the SMS Administrator console. You can now enter a term or phrase in the Look for: text box as well as select which columns to search, in the Search in: text box. Using this feature returns a filtered list matching your search parameters and makes managing lengthy SMS object lists easier.
Multiple Selection and Drag-and-Drop Functionality
Other improvements in the SMS Administrator console are multiple selection and drag-and-drop operations for specific new features in SMS 4.0.
Changes in Software Update Management
There are many improvements in SMS 4.0 related to Software Update Management. This What's New topic addresses some key changes, but you should refer to the Software Updates node under SMS Features in the main documentation to access a complete discussion of changes in this feature area.
Software Updates No Longer Uses Software Distribution Components
In SMS 4.0, Software Updates no longer use the software distribution components (packages, programs, and advertisements) to distribute software updates to clients. SMS 4.0 now creates software update deployments. New deployments are created in the Distribute Software Updates Wizard. When completing the wizard, the deployment object is created and a new deployment package object is created or an existing one is used.
A new machine policy informs targeted clients about the new deployment and during the client's next machine policy evaluation cycle, it processes the deployment.
Deployment Packages
Deployment packages download the software updates to a network share, compress them into a package file, and extract and copy the software update files to each distribution point, defined in the deployment package, where the source files are available for installation.
Custom Updates
SMS 4.0 implements an open schema for software update detection and installation metadata, which supports updating 3rd-party and Line-of-Business (LOB) applications.
Software Updates Client Agent
Like other client agents, the Software Updates client settings apply to the entire site. The Software Updates client agent is enabled by default during installation. The settings can be configured within the Software Updates Client Agent properties.
Selective Download
SMS 4.0 introduces the concept of selective download. Clients identify which targeted software updates are applicable, and only retrieve the files appropriate for installation from the package contents.
Changes in Software Distribution
SMS 4.0 improvements in the area of software distribution include a new server role, the branch distribution point, and the inclusion of a user-configurable service window.
Branch Distribution Points
A new SMS server role, the branch distribution point, allows small office locations to host SMS packages on workstation computers without requiring a SMS secondary site. Packages transfer to the branch distribution point according to bandwidth controlled settings using BITS (Background Intelligent Transfer Service).
Advertisements Not Replicated to Secondary Sites
In SMS 2003, Legacy Clients could be assigned directly to secondary sites so SMS sent all advertisement information to all secondary sites. In SMS 4.0, there are no Legacy Clients and the SMS 4.0 client can only be assigned to a primary site.
In SMS 4.0, SMS no longer replicates advertisement information to secondary sites, resulting in significant performance improvements and savings in network bandwidth
What's Out in SMS 4.0
This section discusses changes and removals in the SMS 4.0 release.
Legacy Client
In SMS 2003, you had a choice between the Legacy Client and the Advanced Client. Starting with SMS 2003 SP1, you could install the Legacy Client only on Windows 98 or Windows NT 4.0 clients. In SMS 4.0 Beta 1, there is just one client called simply the SMS client and it is the equivalent of the SMS 2003 Advanced Client. Before upgrading to SMS 4.0 Beta 1, you must remove all Legacy Clients in the site hierarchy. You can still have Advanced Clients reporting to SMS 2003 sites.
Standard Security
In SMS 2003 you had the option of standard security or advanced security and advanced security was recommended. In SMS 4.0 Beta 1, you have only one security mode and that mode is equivalent to SMS 2003 advanced security mode. In SMS 2003 some sites could not comply with the advanced security requirements that all sites systems belong to an Active Directory domain and use Microsoft SQL Server™ 2000 or later, but these are now requirements to run SMS 4.0 Beta 1.
Network Trace and Network Monitor
These components have been removed in SMS 4.0. This change was based on customer feedback and the availability of the MOM 2005 Management Pack for SMS to monitor, maintain, and troubleshoot your SMS 4.0 hierarchy.
Product Compliance Reporting
Product compliance reporting has been removed in SMS 4.0.
|
