Changes in Functionality from Windows Server 2003 with sp1 to Windows Server 2008
Do I need to change any existing code?
Download 1.83 Mb.
|
- Navigate this page:
- What does Windows PowerShell Do
- Who will be interested in this feature
- Are there any special considerations
- What new functionality does this feature provide
- Windows Reliability and Performance Monitor
- What does Windows Reliability and Performance Monitor do
- Wizards and templates for creating logs
- Unified property configuration for all data collection, including scheduling
- User-friendly diagnosis reports
- Do I need to change any existing code
- What does the troubleshooting documentation do
- Event Log Online Help link in Event Viewer
- Online browsing of server role troubleshooting knowledge
Do I need to change any existing code?If you create software that is designed to be installed on with Windows Vista or Windows Server 2008, then you must make sure that your installation tool correctly configures the firewall by creating or enabling rules that allow your program's network traffic to pass through the firewall. Your program should recognize the different network location types recognized by Windows, domain, private, and public, and correctly respond to a change in network location type. Be aware that a change in the network location type can result in different firewall rules being in effect on the computer. For example, if you want your application to only run in a secured environment, such as a domain or private network, then the firewall rules must prevent your application from sending network traffic when the computer is on a public network. If the network location type changes unexpectedly while your application is running, it must handle the change gracefully. Additional referencesThe following resources provide additional information about Windows Firewall with Advanced Security and IPsec: For more information about Windows Firewall with Advanced Security, see Windows Firewall (http://go.microsoft.com/fwlink/?LinkID=84639). For more information about IPsec, see IPsec (http://go.microsoft.com/fwlink/?LinkID=84638). For more information about server and domain isolation scenarios for IPsec, see Server and Domain Isolation (http://go.microsoft.com/fwlink/?LinkID=79430). For more information about Network Access Protection, see Network Access Protection (http://go.microsoft.com/fwlink/?LinkID=84637). For more information about how to write applications that are aware of network location types, see Network Awareness on Windows Vista (http://go.microsoft.com/fwlink/?LinkId=85491), and Network Location Awareness Service Provider (NLA) (http://go.microsoft.com/fwlink/?LinkId=85492). Windows PowerShellWindows PowerShell™ is a new task-based command-line shell and scripting language designed especially for system administration. Built on the Microsoft .NET Framework, Windows PowerShell helps IT professionals and power users control and automate the administration of the Windows operating system and applications that run on Windows. What does Windows PowerShell Do?Built-in Windows PowerShell commands, called cmdlets, let you manage the computers in your enterprise from the command line. Windows PowerShell providers let you access data stores, such as the registry and certificate store, as easily as you access the file system. In addition, Windows PowerShell has a rich expression parser and a fully-developed scripting language. Windows PowerShell 1.0 includes the following features: 129 standard cmdlets that perform common system administration tasks, such as managing the registry, services, processes, and event logs, and using Windows Management Instrumentation. A task-based scripting language and support for existing scripts and command-line tools. Consistent design. Because Windows PowerShell cmdlets and system data stores use common syntax and naming conventions, data can be shared easily and the output from one cmdlet can be used as the input to another cmdlet without reformatting or manipulation. Simplified, command-based navigation of the operating system, which lets users navigate the registry and other data stores by using the same techniques that they use to navigate the file system. Powerful object manipulation capabilities. Objects can be directly manipulated or sent to other tools or databases. Extensible interface. Independent software vendors and enterprise developers can build custom tools and utilities to administer their software. Who will be interested in this feature?Windows PowerShell is useful to anyone who wants to manage Windows from the command line, especially system administrators who are writing automated task solutions, and developers who want to write their own Windows PowerShell cmdlets, providers, and hosting applications. Are there any special considerations?Windows PowerShell is an object-based environment, so users need to understand how to manipulate data using object properties and methods. Most existing shells are text-based, which means that scripts must parse through text-based data to find interesting data. In the Windows PowerShell object-based environment, a script needs only to access the appropriate object property to find the interesting data. What new functionality does this feature provide?Windows PowerShell provides the ability to manipulate objects rather than just text. It provides a powerful scripting language based on the .NET Framework. It provides a consistent way of traversing data stores, such as the registry, through the concept of providers. Additional referencesIn addition to the Help available at the command line, the following resources provide more information: Windows PowerShell Help Online (http://go.microsoft.com/fwlink/?LinkID=107116). Provides updated help for Windows PowerShell cmdlets, providers, and concepts. Windows PowerShell SDK (http://go.microsoft.com/fwlink/?LinkID=89595). Provides reference content used to develop cmdlets, providers, and hosting applications. Windows PowerShell Programmer's Guide (http://go.microsoft.com/fwlink/?LinkID=89596). Provides tutorials for creating cmdlets, providers, and hosting applications. Also contains information about fundamental Windows PowerShell concepts. Windows PowerShell Team Blog (http://go.microsoft.com/fwlink/?LinkID=83147). This is the best resource for learning from and collaborating with other Windows PowerShell users. Read the Windows PowerShell Team blog and join the Windows PowerShell User Forum (microsoft.public.windows.powershell). Then, as you develop your expertise, please freely contribute your ideas.
In some pre-release versions of Windows, this feature was named "Windows Performance Diagnostic Console". What does Windows Reliability and Performance Monitor do?Windows Reliability and Performance Monitor is a Microsoft Management Console (MMC) snap-in that combines the functionality of previous stand-alone tools including Performance Logs and Alerts, Server Performance Advisor, and System Monitor. It provides a graphical interface for customizing performance data collection and Event Trace Sessions. It also includes Reliability Monitor, an MMC snap-in that tracks changes to the system and compares them to changes in system stability, providing a graphical view of their relationship. Who will be interested in this feature? IT professionals who need to review the performance and reliability of individual systems on their network End users interested in the impact of applications and maintenance on their system performance and reliability Are there any special considerations?Windows Reliability and Performance Monitor is a tool intended for use by IT Professionals or computer administrators. To view real-time status in Resource View, the console must run as a member of the Administrators group. To create Data Collector Sets, configure logs, or view reports, the console must run as a member of the Administrators group or the Performance Log Users Group. What new functionality does this feature provide?Features of Windows Reliability and Performance Monitor new to Windows Server 2008 include the following. Data Collector SetsAn important new feature in Windows Reliability and Performance Monitor is the Data Collector Set, which groups data collectors into reusable elements for use with different performance monitoring scenarios. Once a group of data collectors are stored as a Data Collector Set, operations such as scheduling can be applied to the entire set through a single property change. Windows Reliability and Performance Monitor also includes default Data Collector Set templates to help system administrators begin collecting performance data specific to a Server Role or monitoring scenario immediately. Wizards and templates for creating logsAdding counters to log files and scheduling their start, stop, and duration can now be performed through a Wizard interface. In addition, saving this configuration as a template allows system administrators to collect the same log on subsequent computers without repeating the data collector selection and scheduling processes. Performance Logs and Alerts features have been incorporated into the Windows Reliability and Performance Monitor for use with any Data Collector Set. Resource ViewThe home page of Windows Reliability and Performance Monitor is the new Resource View screen, which provides a real-time graphical overview of CPU, disk, network, and memory usage. By expanding each of these monitored elements, system administrators can identify which processes are using which resources. In previous versions of Windows, this real-time process-specific data was only available in limited form in Task Manager. Reliability MonitorReliability Monitor calculates a System Stability Index that reflects whether unexpected problems reduced the reliability of the system. A graph of the Stability Index over time quickly identifies dates when problems began to occur. The accompanying System Stability Report provides details to help troubleshoot the root cause of reduced reliability. By viewing changes to the system (installation or removal of applications, updates to the operating system, or addition or modification of drivers) side by side with failures (application failures, operating system crashes, or hardware failures), a strategy for addressing the issues can be developed quickly. Unified property configuration for all data collection, including schedulingWhether creating a Data Collector Set for one time use or to log activity on an ongoing basis, the interface for creation, scheduling, and modification is the same. If a Data Collector Set proves to be useful for future performance monitoring, it does not need to be re-created. It can be reconfigured or copied as a template. User-friendly diagnosis reportsUsers of Server Performance Advisor in Windows Server 2003 can now find the same kinds of diagnosis reports in Windows Reliability and Performance Monitor in Windows Server 2008. Report generation time is improved and reports can be created from data collected by using any Data Collector Set. This allows system administrators to repeat reports and assess how changes have affected performance or the report's recommendations. Do I need to change any existing code?Previous performance counters, event trace providers, and other performance-related code elements do not need to change to work with the new Windows Reliability and Performance Monitor or its features. Windows Server Troubleshooting DocumentationThe troubleshooting content available with the Windows Server® 2008 operating system represents a new type of online documentation. Derived from knowledge captured when modeling the health of Windows Server 2008 server roles, the documentation provides prescriptive steps that can be taken to recover from error conditions reported by an event. Because you can access the documentation from Event Viewer, you can find out, from just one place, what an event means, how to fix the error condition reported by the event, and how to verify that the issue is resolved. What does the troubleshooting documentation do?The documentation offers prescriptive guidance so that you can: Resolve an error condition reported by a specific event. Determine if an error condition reported by an event is no longer present. Diagnose the underlying cause of an event when the source of the error condition is unclear. The documentation related to these troubleshooting activities complements the information available with the Windows Server events logged on your computer. This documentation also offers a view of server roles in Windows Server 2008, from the manageability perspective. Who will be interested in this feature? IT professionals who are troubleshooting error conditions on computers running Windows Server 2008. IT professionals who want to understand server roles in Windows Server 2008 from a manageability perspective. What new functionality is provided?Event Log Online Help link in Event ViewerEvent Viewer in Windows Server 2008 includes an Event Log Online Help link that, when clicked, directs you to this troubleshooting documentation. 
If the computer is connected to the Internet, a page will open in your Web browser, with troubleshooting information that applies to the selected event. Online browsing of server role troubleshooting knowledgeThe troubleshooting documentation is part of the online documentation for Windows Server 2008. To browse this documentation, see http://go.microsoft.com/fwlink/?LinkId=76538. Organized by server roles, the information is divided according to the logical areas of interest to an administrator or operator when monitoring and troubleshooting the server role. Within each logical area of manageability, you will find reference and troubleshooting information relevant to each event logged by services or applications that are part of the server role. Directory: uploads uploads -> 587 Return function, r i(X) r i(0) r i(1) r i(2) r i(3) 1 0 2 4 6 Thermal Station, I 2 0 1 5 6 3 0 3 5 6 10 uploads -> Department of science and humanities department of mathematics part-a questions and answers uploads -> The Case Against the nypd’s Quota-Driven ‘Broken Windows’ Policing What Is It? uploads -> For want of a nail uploads -> Ownership Models There are two different types of ownership models uploads -> Police Militarization uploads -> City of rising star regular meting thursday, july 14, 2016 uploads -> Township of winfield uploads -> Stop Militarizing Law Enforcement Act of 2014 uploads -> The Black Panther Party’s Ten-Point Program What We Want Now! Download 1.83 Mb. Share with your friends:
|
Note