An update for Windows Server 2008 Server Manager (KB940518) has been released to integrate Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1). This update to Server Manager enables full integration of WSUS 3.0 SP1 into Server Manager, allowing installation, configuration, and management of WSUS 3.0 SP1 using the Server Manager console and wizards.
How to determine whether the service pack is installed
Look for Update for Windows (KB940518) in the View installed updates item or in the Programs and Features item in Control Panel. If Update for Windows (KB940518) does not appear, the update is not installed.
To avoid restarting the computer, verify that the Initial Configuration Tasks, Server Manager, and the Servermanagercmd.exe process are not running during the installation process. You must also log on to the computer as an administrator to install this update.
1. On a computer that is running Windows Server 2008, download the update package from the Microsoft Web site that is listed in the “Update information” section.
2. Double-click the download package to start the Setup wizard. Follow the instructions in the wizard to complete the installation.
3. Use one of the following methods to open Server Manager:
• Click Start, right-click Computer, and then click Manage.
• Click Start, point to Administrative Tools, and then click Server Manager.
• Click the Quick Launch bar, and then click Server Manager.
Note If WSUS 3.0 SP1 is already installed on your computer, you do not have to complete the remaining steps.
4. On the Server Manager home page, click Add Roles in the Roles Summary section.
5. On the Select Roles page of the Add Roles Wizard, click to select Windows Server Update Services from the list of available roles.
6. Follow the instructions in the Add Roles Wizard to complete installation.
As more companies deploy Windows 2008 and Vista, it is crucial, or in my opinion, critical that this hotfix be applied to all Windows 2003 servers that may communicate with these operating systems. One of the main reasons is a new feature called TCP auto-tuning which makes use of RSS to expand and shrink the sizes of your TCP window to increase/decrease throughput based on current network load. This feature greatly increases throughput on your network, but if there is an underlying problem with the network card driver or any of these features between disparate systems, you may experience slower than normal network performance. The good news is that the Chimney feature is disabled by default in Vista/Windows 2008.
More and more organizations are choosing VMware Infrastructure to virtualize their mission‐critical applications (Active Directory, Exchange, SharePoint, SQL Server) to create a flexible, easily administered virtual infrastructure. Virtual machines (VMs) and any applications they contain must be protected against failure. Typically, in the virtual world, this is done by performing an image‐level backup of the whole machine (for instance, using VMware Consolidated Backup). This method results in what is known as a crash‐consistent image. Restoring a crash‐consistent image is essentially equivalent to rebooting a server after a hard reset. For operating systems, this has not been an issue, since they can easily handle this type of activity. For database applications as well as for applications featuring replication, however, such a restore will often result in lost data, data corruption, or application failure. To illustrate this concept, let’s review the consequences of using different VM disaster recovery methods for one of the most common mission‐critical applications: a Microsoft Active Directory domain controller (DC). Depending on the solution used, the following results will be achieved:
Network Access Protection (NAP) is one of the most desired and highly anticipated features of Windows Server 2008. NAP is a new platform and solution that controls access to network resources based on a client computer’s identity and compliance with corporate governance policy. NAP allows network administrators to define granular levels of network access based on who a client is, the groups to which the client belongs, and the degree to which that client is compliant with corporate governance policy. If a client is not compliant, NAP provides a mechanism to automatically bring the client back into compliance and then dynamically increase its level of network access.
NAP includes an application programming interface (API) for developers and vendors to create complete solutions for health state validation, limitation of network access or communication, and ongoing compliance. This paper describes the scenarios for NAP, the components of NAP, and how NAP works for the different enforcement methods included with Windows Server 2008, Windows Vista, and Windows XP Service Pack 3.
Network Access Protection (NAP) is a new platform and solution that controls access to network resources based on a client computer’s identity and compliance with corporate governance policy. NAP allows third-party software vendors and system integrators to create complete solutions for validating and enforcing system health requirements for network access or communication.
This white paper describes the architecture of the NAP platform and the details of how NAP works for enforcement methods that are provided with Windows Server 2008, Windows Vista, and Windows XP Service Pack 3.
If you have a Windows 2008 guest that you wish to customize, it is fairly easy to do in VirtualCenter.
The sysprep.xml file is automatically generated by VirtualCenter, and does not require any additional tools from Microsoft, as they got smart, and included it in the base build of Windows Vista/2008.
Unfortunately, VC won’t customize a Windows 2008 guest… But it will customize a Windows Vista guest. Because they are a similar architecture (if not almost identical), changing the guest type to Vista, will allow you to customize a Windows 2008 guest.
All you have to do, is change the guest you wish to clone, or the template, to be configured as a Windows Vista guest.
You can then customize the guest (2008) the same way you would Windows Vista. When you are done deploying the guest, before you power it on, change it to be configured as a Windows 2008 guest.
Converteer je Windows 2008 template weer terug naar een VM en stel de VM daarna in op Microsoft Windows Vista als Guest Operation System Version.
Daarna converteer je de VM weer terug naar een templat. Vanaf nu kun je de Windows 2008 template ook customizen.
Microsoft has created a new FTP service that has been completely rewritten for Windows Server 2008. This new FTP service incorporates many new features that enable web authors to publish content better than before, and offers web administrators more security and deployment options. This new FTP service supports a wide range of features and improvements, and the following list contains several of the improvements in this version:
Integration with IIS 7.0: IIS 7.0 has a brand-new administration interface and configuration store, and the new FTP service is tightly integrated with this new design. The old IIS 6 metabase is gone, and a new configuration store that is based on the .NET XML-based *.config format has taken its place. In addition, IIS 7.0 has a new administration tool, and the new FTP server plugs seamlessly into that paradigm.
Support for new Internet standards: One of the most significant features in the new FTP server is support for FTP over SSL. The new FTP server also supports other Internet improvements such as UTF8, IPv6, and adaptive networking bandwidth usage.
Shared hosting improvements: By fully integrating into IIS 7.0, the new FTP server makes it possible to host FTP and Web content from the same site by simply adding an FTP binding to an existing Web site. In addition, the FTP server now has virtual host name support, making it possible to host multiple FTP sites on the same IP address. The new FTP server also has improved user isolation, now making it possible to isolate users through per-user virtual directories.
Extensibility and custom authentication: The new FTP server supports developer extensibility, making it possible for software vendors to write custom providers for FTP authentication. Microsoft is using this extensibility feature to implement two new methods for using non-Windows accounts for FTP authentication for IIS Managers and .NET Membership.
Improved logging support: FTP logging has been enhanced to include all FTP-related traffic, unique tracking for FTP sessions, FTP sub-statuses, additional detail fields in FTP logs, and much more.
New supportability features: IIS 7.0 has a new option to display detailed error messages for local users, and the FTP server supports this by providing detailed error responses when logging on locally to an FTP server. The FTP server also logs detailed information using Event Tracing for Windows (ETW), which provides additional detailed information for troubleshooting.