Windows Server R2 - Wikipedia.
Looking for:
- (PDF) Windows Server R2 e-book | carlos amador - |
Windows web server 2008 r2 active directory free -
By having fewer physical computers, you reduce your energy consumption, datacenter space requirements, and hardware support costs, while also reducing your carbon footprint, a not insignificant consideration these days. Licensing Windows Server R2 Hyper-V requires no additional licensing to use on those editions in which it is available.
There are no additional Client Access Licenses required, either. With Windows Server R2 Datacenter, you have an unlimited license to run virtualized instances of the Windows Server software. This can make the price of Windows Server R2 Datacenter a compelling bargain in heavily virtualized environments.
You can use Windows PowerShell cmdlets. It integrates into the Server Manager console or runs stand-alone as shown in Figure With the Hyper-V console, you can manage all aspects of a VM except clustering.
You can add or delete VMs, add networks, change the settings on a VM, export it, take a snapshot, and all the other things you need to do to a VM.
One key requirement is to leave one net- work interface card NIC exclusively for managing the server. In a production environment, unlike our test environment here, you should also plan on having at least one dedicated NIC for each VM on the server. As you can see, planning for virtualization means configuring your servers with multiple NICs. If you use the wizard to automatically create a new virtual hard disk VHD , it will create a dynamically expanding VHD file, which is nice for only using the space you really need, but imposes a performance penalty as it has to periodically expand the disk space.
A better option is to use the New Virtual Hard Disk Wizard, shown in Figure , to create the VHD file before you create the VM, allowing you to specify a fixed size or pass-through disk for optimal performance. NOTE One of the areas where Windows Server R2 improves on the performance of Windows Server is dynamically expanding disks, which have been optimized in R2 to reduce the performance penalty.
However, fixed-size VHDs are still recommended for production servers. Another consideration when using the New Virtual Machine Wizard is that it automatically assigns only a single processor and a single disk to the VM it creates. In the Settings dialog box, you can change the virtual hardware that is used by the VM, along with management settings for the VM. Only a limited subset of the virtual hardware of a VM can be modified while the VM is running or in a saved state.
These include changing the connection of a network adapter but not the number of network adapters , changing the DVD or Diskette Drive connections, and adding or removing a hard disk. This last feature is an important change in Windows Server R2 that allows you to dynamically manage the storage used by a VM.
The current release as of this writing is still version 1. Because this project was designed to work with Windows PowerShell 1. That will likely change with the next version of PSHyperV. You can migrate the storage within a host, or across hosts, with short downtimes—on the order of a couple of minutes, depending on the speed of the network and the speed of the storage.
Queuing of Live Migrations One limitation of live migration is that you can only do one at a time on a given host, either as source or target. SCVMM adds the ability to queue live migrations on a host by detect- ing that a migration fails because another one is in process, and relaunching the migration in the background after waiting.
The wait between tries increases after each failure, up to a maximum. This could be a slow process on a busy network with large VHDs. Host-Compatibility Checks In migrations between hosts, the CPU and other host hardware needs to be compatible for the migration to succeed. This enables users to check if a VM is compatible without having to do the migration, only to discover that the VM cannot start or run on the host. But an even better feature is that you can use the graphical console to help build a library of scripts that you can then modify for repeat use.
When you perform an action in the console, as the last step before you execute it, you have an option to click View Script, which opens a Notepad window with the Windows PowerShell script that will be executed. For example, Fig- ure shows the Summary page for adding a new filesystem share to the library, and Figure shows the Windows PowerShell code that was displayed with the View Script button.
In Windows Server , you were pretty limited in your options for storage, and even if you used failover clusters, you still had limited flexibility. R2 changes that dramatically with the addition of CSVs in Windows failover clustering.
Live migration has the following benefits: n Provides better agility Datacenters with multiple Hyper-V physical hosts can move running VMs to the best physical computer for performance, scaling, or optimal consolidation without affecting users. Live migration makes it possible to keep VMs online, even during maintenance, increasing productivity for users and server adminis- trators. Datacenters can now also reduce power consumption by dynamically increas- ing consolidation ratios and powering off unused physical hosts during lower demand times.
Live migration and Quick Migration both move running VMs from one Hyper-V physical computer to another, but with an important difference: Quick Migration saves, moves, and restores VMs, resulting in some downtime, whereas live migration uses a different mechanism for moving the running VM to the new physical computer.
Briefly, live migration uses the following process: 1. Any page modifications that occurred during step 1 are transferred to the destination physical computer. The destination VM is brought online on the destination Hyper-V server. A live migration results in significantly less downtime for the VM being migrated compared to a Quick Migration or a simple move, making it preferable when users need uninterrupted access to the migrating VM.
Because a live migration completes in less time than the Trans- mission Control Protocol TCP timeout for the migrating VM, users experience no outage for the migrating VM during steps 3 and 4 of the migration. There are no concerns about differences in hardware, and especially no concerns about different capabilities of the CPUs.
Because Hyper-V can take advantage of the processor capabilities in the newest Intel and AMD processors to improve the overall speed and efficiency of the VMs running on the physical host, the default is to use whatever processor features are available on the original host when the VM is created.
With identical processors, both live migration and Quick Migration work as expected. When a cluster includes nodes with different processors, the capabilities of the pro- cessors can be different. Because a migration occurs with a running machine, this can cause a failure when the VM tries to run after migrating to a different proces- sor.
Applications use the x86 CPUID processor instruction to determine processor type and processor features. Use the Processor Compatibility Mode only in cases where VMs will migrate from one Hyper-V-enabled processor type to another within the same vendor processor family. This includes unplanned failovers and manual VM moves between hosts. Failover clusters in Windows Server R2 can include nodes with different processors, and even processors from different manufacturers. Live migration, however, requires that the processors at least be from the same manufacturer.
Create a Failover Cluster Before you can do live migration or Quick Migration , you first have to configure two or more servers as a failover cluster.
The basic minimum hardware requirements for a two-node cluster are the following: n Two physical servers capable of running Windows Server R2.
Ideally, these should be identical or very similar servers. The minimum number of Gigabit NICs for a supported live migration scenario is three per node. The recommended configuration uses four Gigabit NICs. You should have already created at least two storage disks, one of which will be used for the witness disk. When you use iSCSI disks, they are initially offline and not initialized even after you have them assigned to a node. You need to use the Disk Management console or Diskpart.
Right-click the cluster in the tree pane, and select Enable Cluster Shared Volumes. Read it and understand what it means before you go any further. The steps for this will vary depending on your SAN hardware or software.
Click Refresh to show any new targets, as shown in Figure Select the target you want to add to the cluster and click Connect. Repeat steps 2 through 5 on the second node in the cluster. The iSCSI target must be connected to all nodes that will be using the disk. Open the Disk Management console Diskmgmt.
Right-click again and select Initialize Disk. Select Storage in the tree pane. Select the disk to add and click OK. The disk will be added to the cluster in the Storage node. In the tree pane, select Cluster Shared Volumes. The disk is now available for Hyper-V storage. The basic steps are as follows: n Create the VM. Use the following steps to create the new VM and make it available for live migration: 1.
Specify a CSV location, as shown in Figure Complete the rest of the New Virtual Machine Wizard. If not, click View Report to identify the problem and correct it.
Start the VM and install an operating system as you would normally. The VM is config- ured to support live migration. Once a VM is configured to support live migration, the process is simple. Specify the target node, and the migration pro- ceeds. Optimizing Virtual Machine Performance Windows Server R2 improves overall Hyper-V performance significantly compared to Windows Server , while reducing power consumption and allowing greater VM den- sity per physical host.
The two main areas of performance improvement are scalability and networking. Scalability Improvements in VM Performance Windows Server R2 supports up to 64 logical processors on the physical host com- puter.
This allows greater VM density per physical host, reducing costs and power consump- tion, and gives IT administrators greater flexibility in assigning CPU resources to VMs. This works the same as in a physical TCP Offload scenario; Hyper-V now simply extends this functionality into the virtual world.
This benefits both CPU and overall network throughput performance and is fully supported by live migration. This translates into better host system performance and a simultaneous boost to VM network throughput. Support for Jumbo Frames was introduced with Windows Server Jumbo Frames support in Hyper-V adds the same basic performance enhancements to virtual networking, including up to six-times-larger payloads per packet, which not only improves overall throughput but also reduces CPU utilization for large file transfers.
Each VM device buffer is assigned a VMQ, which avoids needless packet cop- ies and route lookups in the virtual switch. The major technological addition in R2 is full support for Virtual Desktop Infrastructure VDI and the ability to have applications and whole desktops virtualized. Windows Server introduced major changes in Terminal Services, especially the ability to integrate a remotely running application into your local desktop with TS RemoteApps. In Windows Server R2, RemoteApps is extended to provide a more nearly seamless experience, with the ability to have the full Windows Aero experience for remote applications.
For users who need a consistent but personal desktop, Windows Server R2 can provide a personal virtual desktop regardless of which computer you are using. It can also provide a standard corporate desktop from a pool of virtual desktops to users on demand. Remote applications can now take full advantage of multiple moni- tors, the Windows Aero look and feel, and a full audio experience, while also integrating more seamlessly into the Taskbar, Start menu, and system tray.
The RemoteApp and Desktop Connection can be customized to meet your needs, but defaults to a name of Enterprise Remote Access, as shown. Changes made here are directly reflected in the RemoteApp and Desktop Connection Control Panel for Windows 7 users, and in the applications and virtual desktops that users connecting from earlier versions of Windows see when they log in to the RD Web Access server, as shown in Figure For those new to Windows PowerShell, a brief explanation of providers is in order.
In Windows PowerShell, providers are a way to view and navigate information in a hierarchical way as if the providers were drives on the computer. In fact, the FileSystem is implemented as a provider. The dir command is an alias for Get-ChildItem. So, for example, if you want to know what the parameters are for creating a new RemoteApp using Windows PowerShell, you just ask Windows PowerShell to tell you, as shown in Figure Not only will they have more direct access to applications and desktops through the RemoteApp and Desktop Connection RAD link in the Control Panel, but the overall experi- ence is more natural and integrated.
RemoteApps are directly integrated into the Start menu, Taskbar, and system tray, so that many users will be unable to tell whether a program is run- ning locally or remotely. Applications will behave just like they do when running locally in multimon- itor configurations. Plus, once the initial connection is made, applications and desktops are automatically updated as the administrator configures the available applications and desktops, simplifying management and deployment.
This will also enable the Hyper-V role. This might require an updated BIOS. This will be imported onto the virtual machines VMs. Yes, this is fairly complicated, but most of these steps are performed one time only, or can be easily automated. Integrating Remote and Local Applications with RemoteApp RemoteApp for Windows Server R2 gives you the ability to provide your users with an integrated and transparent mixture of local and remote applications.
For applications that behave best when run locally, or that are used when not connected to the network, you can install the applications locally, while providing access to other applications using RemoteApp where appropriate. Applications running remotely can even control the file extensions on the client computer, providing a transparent experience for the user. To configure remote applications to take over the local file extensions, you need to create a Windows Installer.
Click Next and select the program or programs you want to add, as shown in Figure Click Next to open the Specify Package Settings page. Make any changes here that are appropriate for your environment. Also select the Desktop check box if you want the user to have a shortcut to this application on his or her desktop.
Click Next and then click Finish to create the. Users can connect to the resources of your RDS environment, including virtual desktops, from supported clients using direct RemoteApp and Desktop Connection, or over the Web using the Remote Desktop Gateway.
This enables users to have consistent access to corpo- rate resources without having to use a virtual private network VPN connection. RD Web Access can be configured to provide virtual desktops as well as RemoteApps, and also provides a gateway to allow users to connect to their own workstation if corporate policy allows it.
Licensing The Remote Desktop Services role and its role services are included as part of the standard Windows Server license and do not require any additional licenses.
Companies should carefully consider their users and the type of devices and access they need to RDS resources before purchasing CALs and deciding what mode RD Session Host servers will use. The RD Licensing Manager, shown in Figure , adds important new capabilities, including the ability to automatically migrate licenses and dynamically activate or deactivate license servers. In Windows Server , Terminal Servers used a discovery mechanism to find and con- nect to a license server.
This created problems if the license server was unavailable, or if the discovery process encountered problems, and it became the source of a significant number of support calls. In Windows Server R2, this is changed so that RD Session Hosts explicitly specify the RD License servers they will connect to, as shown in Figure , and when a spe- cific license server is unavailable, licenses are automatically migrated. When an RD Session Host is initially installed, it has a day grace period before a license server needs to be specified.
If no license server is specified and available at the end of that grace period, the RD Session Host will stop accepting connections.
Virtual Desktop Licensing Complete and correct licensing of a Microsoft VDI environment requires licensing of both the Windows client operating system running in a centralized location and the infrastructure and management components that enable an end-to-end VDI environment. These two suites combine the products for an optimum VDI experience in a value package. NET Framework 3. This requirement is to support the new Active Directory Web Services module.
However, although the Active Directory roles in Windows Server R2 appear to be the same as those in Windows Server , there are some substantial innova- tions beneath the surface, particularly in the area of Active Directory administration.
The R2 release includes a new set of tools for managing Active Directory from Windows PowerShell, a new graphical management utility that is based on those same Windows PowerShell cmdlets, and a long-requested mechanism for restoring Active Directory objects that administrators have inadvertently deleted. There is also a new facility for joining work- stations to an AD DS domain when they do not have access to a domain controller, and an Active Directory implementation of the Best Practices Analyzer BPA technology that should be familiar to administrators of Microsoft Exchange Server.
These are all improvements that administrators can avoid entirely, if they so desire. You can skip right over this chapter if you want to and continue to work with Active Directory the way you always have on your new Windows Server R2 servers, and everything will function just as it always has.
However, if you choose to persevere and examine these new features, you might find yourself approaching your Active Directory management tasks in a completely new and better way.
You might even learn to love the command prompt. For administrators not comfortable working from the com- mand prompt, Windows Server R2 also includes Active Directory Administrative Center ADAC , a new management console that provides a graphical interface to the functionality of the Windows PowerShell cmdlets.
A Windows PowerShell 2. You can also import the module manually from a standard Windows PowerShell prompt by using the following command: Import-Module ActiveDirectory Once you have imported the module, the Active Directory cmdlets it contains become available, but only within that Windows PowerShell session. If you open up another Windows PowerShell window without importing the module , the Active Directory cmdlets are not available in that session.
Of course, for any serious Windows PowerShell user, command-line parameters are only one way to specify attribute values when creating a new object with the New-ADUser cmdlet. Another possible method is to use an existing object as a template.
When you specify the name of the object you want to use as a template on the New-ADUser command line, using the —instance parameter, the system copies all of the attribute values from the template to the new object, except for those overridden by other parameters on the command line.
Yet another method, suitable for creating multiple Active Directory objects using a single command, is to create a comma-separated value CSV file containing a list of the objects you want to create and their attribute values. The preced- ing are some extremely basic examples of how, with a little study and a little practice, you can learn to enhance and streamline the processes by which you perform your regular Active Directory management tasks, using the tools provided in Windows Server R2. Active Directory Administrative Center: Better Interactive Administration Of course, there are some administrators who are simply not comfortable working from the command line.
Indeed, there are some who scarcely know it exists. However, the capabili- ties provided by the Active Directory Module for Windows PowerShell need not be lost on those who prefer a graphical interface. The console works by taking the selections you make and the information you supply in the ADAC graphical interface and translating them into the proper command-line syntax, using the cmdlets in the Active Direc- tory Module.
The program then executes the commands, receives the results, and displays the results in a graphical fashion. The Overview page provides access to the root of your domain, as well as basic functions, such as directory search and password reset. As with most pages in ADAC, you can customize the appearance of the page, in this case by clicking the Add Content link and specifying which tiles should appear in the details pane.
For anything else, you have to create the user first and then open its Prop- erties sheet to configure it, often switching between many different tabbed pages in the process. With ADAC, the Create User page, shown in Figure , contains a great many more configuration settings—in fact, more than can fit in this figure. NOTE Not coincidentally, the list of configuration settings on the Create User page closely resembles the list of parameters for the New-ADUser cmdlet discussed earlier in this chapter.
In addition to creating new Active Directory objects, ADAC also enables you to move, dis- able, rename, and delete objects, and configure their properties. Customizing the Interface ADAC includes a Tree View that you can use to browse your domain, in the style of Active Directory Users and Computers, but it also has a List View option, to which you can add your own navigation nodes, as shown in Figure Navigation nodes are essentially shortcuts that point to specific containers anywhere in your domain or in other domains.
Using the Add Navigation Nodes page, shown in Figure , you can browse your enterprise and select the containers you need to access on a regular basis. For AD DS installations that span multiple domains, or even multiple forests, administra- tors can manage objects in containers anywhere in the enterprise, as long as there are trusts in place between the domains or forests.
You can build complex queries by specifying the exact object criteria you want to search within, limiting the scope of the search to specific navigation nodes, and using the Lightweight Directory Access Protocol LDAP query syntax. Suppose, for example, you are managing a large, multidomain Active Directory installation, and you have to locate the user object of the vice president who just called to complain that he is locked out of his account.
You can then save the query for later reuse when the vice president locks himself out again. Introducing Active Directory Web Services ADAC might appear to be nothing more than a new management interface for Active Directory, but there is actually quite a bit that is new beneath the surface. ADWS requires Microsoft. This is true not just in remote management scenarios, but for activities confined to the local system as well. If the ADWS service stops or fails to start, or you disable it, you will not be able to use Windows PowerShell or ADAC to manage the directory service, even when working at the domain controller console.
In a remote management scenario, no matter how you install the Active Directory Module for Windows PowerShell, the system will not be able to import the module successfully unless it has access to Active Directory Web Services on a computer running Windows Server R2.
If the computer is not a member of a domain, or it is a member of a domain without a Windows Server R2 domain controller, you cannot use the Active Directory Module cmdlets to manage Active Directory.
NOTE Although there has been no official announcement as of yet, it is rumored that Microsoft will eventually release a version of Active Directory Web Services for comput- ers running Windows Server and possibly earlier versions as well.
In this book, we focus on the new features and refinements in R2. Where an R2 feature is a refinement of a feature that was new in Windows Server , we provide background on the Windows Server feature to provide context. This book is targeted primarily at Windows server administrators who are responsible for hands-on deployment and day-to-day management of Windows-based servers for large organizations. Praetorian Prefect. Archived from the original on October 12, CBS Interactive.
Retrieved February 14, June 24, Retrieved October 26, Retrieved August 11, Retrieved August 15, Archived from the original on February 11, Archived from the original on February 9, Archived from the original on 22 December Retrieved 2 April Microsoft Windows. Components History Timeline Criticism. Windows 1. Windows 95 Windows 98 Windows Me. Embedded Compact CE 5. Phone 7 Phone 8 Phone 8. Cairo Nashville Neptune Odyssey.
List of versions Comparison Category. Categories : Windows Server R2 software X operating systems. Hidden categories: Articles with short description Short description is different from Wikidata. Namespaces Article Talk. Views Read Edit View history. It is recommended to stick to the default settings.
Step 9 - Once the installation is complete, the server will be automatically rebooted to apply the configurations. Website Support Live Demo Forums. Knowledge Base. Active Directory Auditing Tool.
Windows web server 2008 r2 active directory free
You probably need to do a little more in order to resolve members and duplicate members in nested groups. Command not found on Win7 SP1. I'm guessing you need RSAT installed? Community Bot 1. But is there any way around the truncated group names? This is great! Worked a treat. Note that this isn't recursive and doesn't list groups that are in a group.
Not very helpful if you have nested or hierarchical groups. For some reason I am getting error "The group name could not be found. Show 2 more comments. The Quest tools do not require any additional changes to your DCs.
Ryan Fisher Ryan Fisher 2, 16 16 silver badges 13 13 bronze badges. I use the first query all the time — Jim B. Be aware that you have to run this command on the domain controler. Or download it from microsoft. See my answer above for details and links. The "net group" command searches only domain or domain tree where the computer is joined. Gordon Bell Gordon Bell 2 2 silver badges 12 12 bronze badges.
It looks like the AD tooling from Quest may now be defunct and the link currently redirects to oneidentity. Oh well, that sucks. It was good while it lasted. Here's an example query for getting group membership: AdFind. For display members of the UserGroup1 try: dsquery group -name UserGroup1 dsget group -members dsget user -display. Might want to point out what CLI utility you'd use this in.
This hotfix should not be applied to the Windows Server servers that are in the domain. The English United States version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias.
Additionally, the dates and the times may change when you perform certain operations on the files. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature. To work around this issue, reset the password of the problematic user account on the domain controller that is running Windows Server R2.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:. KDC has no support for encryption type while getting initial credentials. Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback?
The more you tell us the more we can help. Can you help us improve? Resolved my issue. However, rather than serve only as a starting point to configuring new roles, Server Manager gathers together all of the operations users would want to conduct on the server, such as, getting a remote deployment method set up, adding more server roles etc.
Support for the RTM version of Windows Server ended on July 12, , [3] [4] and users will not be able to receive further security updates for the operating system.
As a component of Windows Vista, Windows Server will continue to be supported with security updates, lasting until January 14, , the same respective end-of-life dates of Windows 7.
Microsoft planned to end support for Windows Server on January 12, However, in order to give customers more time to migrate to newer Windows versions, particularly in developing or emerging markets, Microsoft decided to extend support until January 14, Windows Server can be upgraded to Windows Server R2 on bit systems only. Most editions of Windows Server are available in x and IA variants.
As such, it is not optimized for use as a file server or media server. Windows Server is the last bit Windows server operating system. The Microsoft Imagine program, known as DreamSpark at the time, used to provide verified students with the bit variant of Windows Server Standard Edition, but the version has since then been removed.
However, they still provide the R2 release. Windows Server Foundation Released on May 21, Windows Server shares most of its updates with Windows Vista due to being based on that operating system's codebase.
A workaround was found that allowed the installation of updates for Windows Server on Windows Vista, [40] adding three years of security updates to that operating system Support for Windows Vista ended on April 11, , [41] while support for Windows Server ended on January 14, Due to the operating system being based on the same codebase as Windows Vista and being released on the same day as the initial release of Windows Vista Service Pack 1 , the RTM release of Windows Server already includes the updates and fixes of Service Pack 1.
Service Pack 2 was initially announced on October 24, [42] and released on May 26, Service Pack 2 added new features, such as Windows Search 4. Windows Server specifically received the final release of Hyper-V 1. Windows Vista and Windows Server share the same service pack update binary because the codebases of the two operating systems are unified - Windows Vista and Windows Server are the first Microsoft client and server operating systems to share the same codebase since the release of Windows Windows Server shipped with Internet Explorer 7 , the same version that shipped with Windows Vista.
Internet Explorer 9 was continually updated with cumulative monthly update rollups until support for Internet Explorer 9 on Windows Server ended on January 14, The latest supported version of the.
NET Framework officially is version 4. Starting in March , Microsoft began transitioning to exclusively signing Windows updates with the SHA-2 algorithm. As a result of this Microsoft released several updates throughout to add SHA-2 signing support to Windows Server In June , Microsoft announced that they would be moving Windows Server to a monthly update model beginning with updates released in September [51] - two years after Microsoft switched the rest of their supported operating systems to that model.
With the new update model, instead of updates being released as they became available, only two update packages were released on the second Tuesday of every month until Windows Server reached its end of life - one package containing security and quality updates, and a smaller package that contained only the security updates. Users could choose which package they wanted to install each month.
Later in the month, another package would be released which was a preview of the next month's security and quality update rollup. Installing the preview rollup package released for Windows Server on March 19, , or any later released rollup package, will update the operating system kernel's build number from version 6.
The last free security update rollup packages were released on January 14, Windows Server is eligible for the Extended Security Updates program. This program allows volume license customers to purchase, in yearly installments, security updates for the operating system until at most January 10, The licenses are paid for on a per-machine basis. If a user purchases an Extended Security Updates license in a later year of the program, they must pay for any previous years of Extended Security Updates as well.
Extended Security Updates are released only as they become available. A second release of Windows Server based on Windows 7, Windows Server R2 , was released to manufacturing on July 22, [55] and became generally available on October 22, It is the first server operating system by Microsoft to exclusively support bit processors, a move which was followed by the consumer-oriented Windows 11 in Windows Server supports the following maximum hardware specifications: [61] [62] [63].
From Wikipedia, the free encyclopedia. Server operating system by Microsoft released in Screenshot of Windows Server showing the Server Manager application which is automatically opened when an administrator logs on.
Closed-source Source-available through Shared Source Initiative. See also: Features new to Windows Vista. Main article: Microsoft Cluster Server. Main article: Hyper-V. Main article: Windows System Resource Manager. See also: Features removed from Windows Vista. Main article: Internet Explorer 9. Main article: Windows Server R2. Standard: 4 Enterprise: 8 Datacenter: IA : 32 x64 : News Center.
Redmond, WA : Microsoft. Retrieved
Comments
Post a Comment