Fdsfdsfdsf

Windows 8 Enterprise
OPERATING SYSTEM

Windows Server 2008 is built from the same code base as Windows Vista; therefore, it shares much of the same architecture and functionality. The new server OS, code named Longhorn, shares the same kernel with Windows Vista and incorporates many additions compared to its predecessor.

2013
USER
HOME
3/25/2013

Microsoft will release Windows 2008 Server as the direct successor to Windows 2003 Server in the spring of next year. The new server OS, code named Longhorn, shares the same kernel with Windows Vista and incorporates many additions compared to its predecessor.
When using the completely revamped server-management console, configuration and administration of the new server become much simpler. The new Internet Information Server 7 also sports a new user interface. With virtualization technology integrated directly into the operating system, third-party tools or solutions are no longer necessary when using virtual machines and the like. Lastly, administrators are as up-to-date as it gets, since Windows 2008 Server includes all of the components slated for inclusion in Service Pack 1 for Windows Vista.
Tom’s Guide took a look at the first release candidate, version RC0. Generally speaking, release candidates are very close to the final product and are distributed to testers primarily in order to find bugs. New features are not to be expected in the later release candidates, though. What we see here today is most definitely what users will get in the final version. Thus, a look at RC0 should allow us to draw conclusions about the final release.
Although the Server 2008 may have the Vista kernel under its hood, that does not mean that administrators will be greeted with colorful windows using the Aero interface. Understandably, Microsoft’s focus lay on the server-related issues in implementing improvements, and so the management aspect took precedence over design.
Nonetheless, even if the primary purpose of a server OS is not to look good, Windows Server 2008 still offers the option of installing the new, colorful design. Thus, even jaded system administrators can get a little bit of that Vista feeling and see if the "Wow" really does start now.
Features
Windows Server 2008 is built from the same code base as Windows Vista; therefore, it shares much of the same architecture and functionality. Since the code base is common, it automatically comes with most of the technical, security, management and administrative features new to Windows Vista such as the rewritten networking stack (native IPv6, native wireless, speed and security improvements); improved image-based installation, deployment and recovery; improved diagnostics, monitoring, event logging and reporting tools; new security features such as Bit Locker and ASLR (address space layout randomization); improved Windows Firewall with secure default configuration; .NET Framework 3.0 technologies, specifically Windows Communication Foundation, Microsoft Message Queuing and Windows Workflow Foundation; and the core kernel, memory and file system improvements. Processors and memory devices are modeled as Plug and Play devices, to allow hot-plugging of these devices. This allows the system resources to be partitioned dynamically using Dynamic Hardware Partitioning; each partition has its own memory, processor and I/O host bridge devices independent of other partitions.
Server Manager
Server Manager is a new roles-based management tool for Windows Server 2008. It is a combination of Manage Your Server and Security Configuration Wizard SCW from Windows Server 2003. Server Manager is an improvement of the Configure my server dialog that launches by default on Windows Server 2003 machines. 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., and provides a consolidated, portal-like view about the status of each role.

Benefits of Windows Server 2008
Windows Server 2008 delivers benefits in four primary areas:
Web
Windows Server 2008 gives you the ability to deliver rich web-based experiences efficiently and effectively, with improved administration and diagnostics, development and application tools, and lower infrastructure costs. * Simplified Web server management with Internet Information Services 7.0, which is a powerful Web platform for applications and services. This modular platform provides a simplified, task-based management interface, greater cross-site control, security enhancements, and integrated health management for Web services. * Task based interface simplifies common management Web server tasks. * Cross-site copy allows you to easily copy Web site settings across multiple Web servers without additional configuration. * Delegated administration of applications and sites so you can give control to different parts of the Web server to those who need it. * Deliver flexible and comprehensive applications that connect users to each other and their data, enabling them to visualize, share, and act on information.
Virtualization
With its built-in server virtualization technology, Windows Server 2008 enables you to reduce costs, increase hardware utilization, optimize your infrastructure, and improve server availability. * Built-in virtualization to virtualize multiple operating systems--Windows, Linux and others--on a single server. With virtualization built into the operating system and with simpler, more flexible licensing policies, it's now easier than ever to take advantage of all the benefits and cost savings of virtualization. * Centralized application access and seamless integration of remotely published applications. Improvements also add the ability to connect to remote applications across firewalls and without the use of a VPN, so you can quickly respond to the needs of your users, regardless of their location. * New deployments options to provide the most suitable method for your environment. * Interoperability with your existing environment. * Robust and vibrant technical community to provide a rich experience throughout the product life cycle.

Security
Windows Server 2008 is the most secure Windows Server ever. Its hardened operating system and security innovations, including Network Access Protection, Federated Rights Management, and Read-Only Domain Controller, provide unprecedented levels of protection for your network, your data, and your business. * Protection of your server with security innovations that reduce attack surface area of the kernel, resulting in a more robust and secure server environment. * Protection of your network access with Network Access Protection that gives you the power to isolate computers that don't comply with security policies you set. The ability to enforce security requirements is a powerful means of protecting your network. * Enhanced solutions for intelligent rules and policies creation to increase control and protection over networking functions, allowing you to have a policy-driven network. * Protection of your data to ensure it can only be accessed by users with the correct security context, and to make it available when hardware failures occur. * Protection against malicious software with User Account Control with a new authentication architecture. * Increased control over your user settings with Expanded Group Policy.

Solid Foundation for Business Workloads
Windows Server 2008 is the most flexible and robust Windows Server operating system to date. With new technologies and features such as Server Core, PowerShell, Windows Deployment Services, and enhanced networking and clustering technologies, Windows Server 2008 provides you the most versatile and reliable Windows platform for all of your workload and application requirements. * Increased dependability with advanced reliability enhancements to reduce loss of access, work, time, data, and control. * Simplified management of your IT infrastructure by using new tools that provide a one-stop interface for server configuration and monitoring, as well as the ability to automate routine tasks. * Streamlined installation and management of Windows Server 2008 by installing only the roles and features you need. The customization of the server configuration simplifies ongoing maintenance by minimizing the attack surface area and reducing the need for software updates. * Effectively pinpointing and resolving trouble spots with powerful diagnostic tools that give you ongoing visibility into your server environment, both physical and virtual. * Increased control over servers located in remote locations, such as the branch office. With optimized server administration and data replication, you can provide users with better service while reducing management headaches.
Windows Server 2008 Technologies
Web
Windows Server 2008 gives you the ability to deliver rich Web-based experiences efficiently and effectively, with improved administration and diagnostics, development and application tools, and lower infrastructure costs.
Internet Information Services 7.0: Windows Server 2008 delivers a unified platform for Web publishing that integrates Internet Information Services (IIS) 7.0, ASP.NET, Windows Communication Foundation, Windows Workflow Foundation, and Windows SharePoint Services 3.0. IIS 7.0 is a major enhancement to the existing Windows Web server and plays a central role in integrating Web platform technologies. IIS 7.0 helps developers and administrators alike maximize their control over network/Internet interfaces through key functionality pillars that include delegated administration, enhanced security and a reduced attack surface area, integrated application and health management for Web services, and improved administration tools.
Virtualization
With its built-in server virtualization technology, Windows Server 2008 enables you to reduce costs, increase hardware utilization, optimize your infrastructure, and improve server availability.
Terminal Services: Windows Server 2008 introduces new functionality in Terminal Services to connect to remote computers and applications. Terminal Services Remote App completely integrates applications running on a terminal server with users' desktops such that they behave as if they were running on an individual user's local computer; users can run programs from a remote location side-by-side with their local programs. Terminal Services Web Access permits this same flexibility of remote application access via Web browser, granting an even wider variety of ways user can access and use programs executing on a terminal server. These features in conjunction with Terminal Services Gateway allow users to access remote desktops and remote applications via HTTPS in a firewall-friendly manner.
Security
Windows Server 2008 is the most secure Windows Server ever. Its hardened operating system and security innovations, including Network Access Protection, Federated Rights Management, and Read-Only Domain Controller, provide unprecedented levels of protection for your network, your data, and your business.
Network Access Protection (NAP): A new framework that allows an IT administrator to define health requirements for the network and to restrict computers that do not meet these requirements from communicating with the network. NAP enforces administrator-defined policies that describe the health requirements for the given organization. For example, health requirements may be defined to include all updates to the operating system be installed, or having antivirus or antispyware software installed and updated. In this way, network administrators can define the baseline level of protection all computers carry when connecting to the network.
Microsoft Bit Locker provides additional security for your data through full volume encryption on multiple drives, even when the system is in unauthorized hands or running a different operating system time, data, and control.
Read-Only Domain Controller (RODC): A new type of domain controller configuration in the Windows Server 2008 operating system that makes it possible for organizations to easily deploy a domain controller in locations where the physical security of a domain controller cannot be guaranteed. An RODC hosts a read-only replica of the Active Directory services database for a given domain. Prior to this release, users who had to authenticate with a domain controller, but were in a branch office that could not provide adequate physical security for a domain controller, had to authenticate over a wide area network (WAN). In many cases, this was not an efficient solution. By placing a read-only Active Directory database replica closer to branch users, these users can benefit from faster logon times and more efficient access to authentication resources on the network, even in environments with inadequate physical security to deploy a traditional domain controller.
Failover Clustering: Improvements are aimed to makes it easier to configure server clusters while providing protection and availability of your data and applications. By using the new Validate Tool in failover clusters, you can perform tests to determine whether your system, storage, and network configuration is suitable for a cluster. With failover clusters in Windows Server 2008, administrators can carry out setup and migration tasks, as well as management and operations tasks more easily. Improvements to the cluster infrastructure help administrators maximize availability of the services they provide to users, achieve better storage and network
Solid Foundation for Business Workloads
Windows Server 2008 is the most flexible and robust Windows Server operating system to date. With new technologies and features such as Server Core, PowerShell, Windows Deployment Services, and enhanced networking and clustering technologies, Windows Server 2008 provides you the most versatile and reliable Windows platform for all of your workload and application requirements.
Server Core: Beginning with the Beta 2 release of Windows Server 2008, administrators can choose to install Windows Server with only the services required to perform the DHCP, DNS, file server, or domain controller roles. This new installation option will not install non-essential services and applications and will provide base server functionality without any extra overhead. While the Server Core installation option is a fully functioning mode of the operating system supporting one of the designate roles, it does not include the server graphic user interface (GUI). Because Server Core installations include only what is required for the designated roles, a Server Core installation will typically require less maintenance and fewer updates as there are fewer components to manage. In other words, since there are fewer programs and components installed and running on the server, there are fewer attack vectors exposed to the network, resulting in a reduced attack surface. If a security flaw or vulnerability is discovered in a component that is not installed, a patch is not required.
Windows Power Shell: A new command-line shell with over 130 tools and an integrated scripting language. It enables administrator to more easily control and securely automate routine system administration tasks, especially across multiple servers. Windows Power Shell does not require you to migrate your existing scripts, and it is ideally suited for automation of new Windows Server 2008 features. A new admin-focused scripting language, and consistent syntax and utilities, Windows Power Shell accelerates automation of system administration tasks--such as Active Directory, Terminal Server, and Internet Information Server (IIS) 7.0--and improves your organization's ability to address the unique system management problems of your environment.
Windows Power Shell is easy to adopt, learn, and use, because it does not require a background in programming, and it works with your existing IT infrastructure, existing scripts, and existing command-line tools.
Server Manager: A new feature that is included in Windows Server 2008. It is a "one-stop-shop" designed to guide Information Technology administrators through the end-to-end process of installing, configuring, and managing server roles and features that are part of Windows Server 2008. Server Manager replaces and consolidates a number of features from Microsoft Windows Server 2003 such as Manage Your Server, Configure Your Server, and Add or Remove Windows Components. You can use Server Manager to configure various "roles" and "features" on your machine.
Windows Deployment Services (WDS): An updated and redesigned Windows Server 2008 version of Remote Installation Services (RIS), WDS assists with the rapid adoption and deployment of image-based Windows operating systems. WDS allows network-based installation of Windows Vista and Windows Server 2008 to "bare metal" computers (no operating system installed), and even supports mixed environments including Microsoft Windows XP and Microsoft Windows Server 2003. Windows Deployment Services thus provides an end-to-end solution for deployment of Windows operating systems to client and server computers and reduces the total cost of ownership (TCO) and complexity of Windows Server 2008 and Windows Vista deployments.

Processor | Minimum | 1GHz (x86 processor) or 1.4GHz (x64 processor) | Recommended | 2GHz or faster | Memory | Minimum | 512MB RAM | Recommended | 2GB RAM or greater | | Maximum (32-bit systems): 4GB (Standard) or 64GB | | (Enterprise and Datacenter) | | Maximum (64-bit systems): 32GB (Standard) or 2TB | | (Enterprise, Datacenter and Itanium-based Systems) | Available Disk Space | Minimum | 10GB | Recommended | 40GB or greater | Others | Drive | DVD-ROM drive | Display and Peripherals | Super VGA (800 x 600) or higher-resolution monitor; Keyboard | | Microsoft Mouse or compatible pointing device |

Setting Up an Additional Domain Controller With Windows Server 2008 | Published |
: |
February 17, 2008 | Last Updated | : | February 17, 2008 | | | | Introduction |

In a previous article, we have set up our first Active Directory Domain Services (AD DS) using Windows Server 2008. In this article, we are going to see how to set up an Additional Domain Controller for AD DS replication.

To set up an Additional Domain Controller, I will use the dcpromo.exe command. 1. To use the command, click on Start > Run > and then write dcpromo > Click OK

2. The system will start checking if Active Directory Domain Services ( AD DS) binaries are installed, then will start installing them. The binaries could be installed if you had run the dcpromo command previously and then canceled the operation after the binaries were installed.

3. The Active Directory Domain Services Installation Wizard will start, either enable the checkbox beside Use Advanced mode installation and Click Next , or keep it unselected and click on Next

Deployment configuration | Advanced mode installation wizard pages | New forest | Domain NetBIOS name | New domain in an existing forest | On the Choose a Deployment Configuration page, the option to create a new domain tree appears only in advanced mode installation. Domain NetBIOS name Source Domain Controller | Additional domain controller in an existing domain | Install from Media Source Domain Controller Specify Password Replication Policy (for RODC installation only) | Create an account for a read-only domain controller (RODC) installation | Specify Password Replication Policy | Attach a server to an account for an RODC installation | Install from Media Source Domain Controller |
The following table lists the additional wizard pages that appear for each deployment configuration when you select the Use advanced mode installation check box.

4. The Operating System Compatibility page will be displayed, take a moment to read it and click Next

5. On the Choose a Deployment Configuration page, click Existing forest, click Add a domain controller to an existing domain, and then click Next.

6. On the Network Credentials page, type your domain name, my domain name is elmajdal.net ( was set in the previous article ) , so I will type elmajdal.net.

7. To set up an Additional Domain Controller, you will need an account that must be either a member of the Enterprise Admins group or the Domain Admins group. We have two options: * My Current logged on credentials ( DomainName\Username or MachineName\Username) * Alternate credentials * If you have previously joined this server to the domain and you are currently logged in to it with an Enterprise Admin/Domain Admin user, then you can use the first option (My current logged on credentials) . As you can see this option is grayed here, and the reason for this is below it. It is because I'm currently logged in with a local user, the machine is not a domain member. I'm left out with the second option: Alternate credentials 8. To enter the Alternate credentials, click Set. In the Windows Security dialog box, enter the user name and password for an account that must be either a member of the Enterprise Admins group or the Domain Admins group > then click Next.

If you have entered a wrong username/password , you will receive the following error message

9. On the Select a Domain page, select the domain of the Additional Domain Controller, and then click Next, as I already have only one domain, then it will be selected by default.

10. On the Select a Site page, either enable the checkbox beside Use the site that corresponds to the IP address of this computer, this will install the domain controller in the site that corresponds to its IP address, or select a site from the list and then click Next. If you only have one domain controller and one site, then you will have the first option grayed and the site will be selected by default as shown in the following image

11. On the Additional Domain Controller Options page, By default, the DNS Server and Global Catalog checkboxes are selected. You can also select your additional domain controller to be a Read-only Domain Controller (RODC) by selecting the checkbox beside it.

My primary domain controller is a DNS Server is well, and this can be verified by reading the additional information written in the below image, that there is currently 1 DNS server that is registered as an authoritative name server for this domain. I do want my Additional DC to be a DNS server and a Global catalog, so I will keep the checkboxes selected. Click Next

12. If you select the option to install DNS server in the previous step, then you will receive a message that indicates a DNS delegation for the DNS server could not be created and that you should manually create a DNS delegation to the DNS server to ensure reliable name resolution. If you are installing an additional domain controller in either the forest root domain (or a tree root domain) , you do not need to create the DNS delegation. In this case, you can safely ignore the message and click Yes.

13. In the Install from Media page ( will be displayed if you have selected Use advanced mode installation on the Welcome page, if you didn't select it, then skip to step # 15), you can choose to either replicate data over the network from an existing domain controller, or specify the location of installation media to be used to create the domain controller and configure AD DS. I want to replicate data over the network, so I will choose the first option > click Next

14. On the Source Domain Controller page of the Active Directory Domain Services Installation Wizard, you can select which domain controller will be used as a source for data that must be replicated during installation, or you can have the wizard select which domain controller will be used as the source for this data. You have two options : * Let the wizard choose an appropriate domain controller * Use this specific domain controller

If you want to choose from the list, any domain controller can be the installation partner. However, the following restrictions apply to the domain controllers that can be used as an installation partner in other situations: * A read-only domain controller (RODC) can never be an installation partner. * If you are installing an RODC, only a writable domain controller that runs Windows Server 2008 can be an installation partner. * If you are installing an additional domain controller for an existing domain, only a domain controller for that domain can be an installation partner. 15. Now you will have to specify the location where the domain controller database, log files and SYSVOL are stored on the server.
The database stores information about the users, computers and other objects on the network. the log files record activities that are related to AD DS, such information about an object being updated. SYSVOL stores Group Policy objects and scripts. By default, SYSVOL is part of the operating system files in the Windows directory

Either type or browse to the volume and folder where you want to store each, or accept the defaults and click on Next

Note : Windows Server Backup backs up the directory service by volume. For backup and recovery efficiency, store these files on separate volumes that do not contain applications or other nondirectory files. 16. In the Directory Services Restore Mode Administrator Password (DSRM) page, write a password and confirm it. This password is used when the domain controller is started in Directory Services Restore Mode, which might be because Active Directory Domain Services is not running, or for tasks that must be performed offline.

Make sure the password meet the password complexity requirements of the password policy, that is a password that contains a combination of uppercase and lowercase letters, numbers, and symbols. else you will receive the following message :

17. Summary page will be displayed showing you all the setting that you have set . It gives you the option to export the setting you have setup into an answer file for use to automate subsequent AD DS operations, if you wish to have such file, click on the Export settings button and save the file. Then click Next to begin AD DS installation

18. Active Directory Domain Services installation will be completed, click Finish, then click on Restart Now to restart your server for the changes to take effect.

* Open Active Directory Users & Computers, and then click on the Domain Controllers Organizational Unit, and you will see your Additional Domain Controller along with your Primary Domain Controller.

Summary

Additional domain controllers improve the performance of authentication requests and global catalog server lookups. They also help Active Directory Domain Services (AD DS) overcome hardware, software, or administrator errors. When you add a domain controller, information is replicated over the network.

Grant DNSAdmins the Right to View DNS Event Log Entries Remotely on Windows Server 2008 R2
-------------------------------------------------
Overview
This is an issue we’ve struggled with in the past day or so. An organization running Windows Server 2008 R2 is delegating control of their DNS servers to specific people, and in order to do so, they added these users to the DNSAdmins built-in group in Active Directory. However, since these users are not members of any administrative groups, while they can view the DNS Event Logs and manage them locally, on the DNS server(s), they cannot do so remotely from another Windows Server 2008 R2 or Windows 7 management workstation.

-------------------------------------------------
The Problem: Access Denied when Viewing Event Logs Remotely
To demonstrate this in our lab environment, we created a user called DNSManager, and added him to the DNSAdmins group. Once the user logs on to their management workstation and opens Event Viewer, they connect to a remote computer.

‘
Figure 1: Connecting to a Remote Computer

In the “Another Computer” area, they type the name of the remote machine. In this case, it’s a remote Domain Controller that is called DC1, which also hosts the DNS service.

Figure 2: Select Computer to View Event Logs on
Once connected, they attempt to open one of the Event Logs, but get an “Access is Denied (5)” message:

Figure 3: Access Denied Error Message when Viewing Event Logs Remotely
-------------------------------------------------
The Solution: Granting DNSAdmins to the Event Log Readers Group
This can be easily fixed by adding these users (or group of users) to the “Event Log Readers” built-in group on the servers that you need to have remote access to.

Figure 4: Adding DNSAdmins to the Event Log Readers Group
Now, if the DNSManager user logs off and logs back on to the remote management machine, he can view the relevant event logs.

Figure 5: Access Granted to DNSAdmins
-------------------------------------------------
The Problem: Access Denied to DNS Event Logs
However, while this trick works for most Event Logs, it does NOT work for the DNS Event Log, as can be seen from this screenshot below.

Figure 6: Access Denied error when Viewing DNS Event Logs
This problem persists even if the user opens up the DNS management console, while they CAN manage the DNS properties, zones and records, as shown below.

Figure 7: DNS Management Console works find
Yet when they attempt to view the remote DNS Event Log, they still get the “Access is denied” error.

Figure 8: Unable to Access DNS Event Logs -------------------------------------------------
The Solution: Granting Remote Access to DNS Event Logs
The fix lies in a somewhat complex Microsoft knowledgebase: How to set event log security locally or by using Group Policy in Windows Server 2003
And also in this great blog post: Giving Non Administrators permission to read Event Logs Windows 2003 and Windows 2008 - Jane Lewis's Weblog
But the trick is that in Windows Server 2008 R2, the procedure is a lot simpler. Here are the steps: 1. Open Command Prompt with elevated permissions (Run as Administrator), and run the following command: wevtutil gl "DNS Server" > C:\Temp\DNS_Server.txt Note: Change the path to fit your needs.
By the way, if you need to perform the same trick on other custom or application logs, you can find out the name of the log by running the following command and examining the resulting text file for the exact name syntax: wevtutil el > C:\Temp\All_Logs.txt 2. Next open the text file from the above path, and look for the channelAccess: entry. Figure 9: ChannelAccess entry

3. Now we need to find the SID of the DNSAdmins group. To do so, if the logged on user is a member of that group, you can find the SID by typing the following command (assuming this is Windows Server 2008 R2 or Windows 7): whoami /groups | find /i "dnsadmins"
The result should look something like this:
PETRI-LAB\DnsAdmins Alias S-1-5-21-3903327414-3371247034-3746192915-1102 Mandatory group, Enabled by default, Enabled group
Naturally, the domain name and SID will differ, but you get the point…
You can also use other tools such as PSGetsid from Sysinternals.
Copy the SID, we’ll need it in a moment. 4. Going back to the text file, append the following text string to that long line:
(A;;0x1;;;XXX)
Where XXX is the SID you’ve copied from above.
In this case, I will append the following line:
(A;;0x1;;;S-1-5-21-3903327414-3371247034-3746192915-1102)

Figure 10: Adding Your SID

5. Next, copy the entire text from the O:BAG… part till the end of the line (including your recent addition):
O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x5;;;SO)(A;;0x1;;;IU)(A;;0x1;;;SU)(A;;0x1;;;S-1-5-3)(A;;0x2;;;LS)(A;;0x2;;;NS)(A;;0x2;;;S-1-5-33)(A;;0x1;;;S-1-5-21-3903327414-3371247034-3746192915-1102)
6. And finally, run the following command in the Command Prompt, pasting the above string just after the /ca: parameter: wevtutil sl "DNS Server" /ca:O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x5;;;SO)(A;;0x1;;;IU)(A;;0x1;;;SU)(A;;0x1;;;S-1-5-3)(A;;0x2;;;LS)(A;;0x2;;;NS)(A;;0x2;;;S-1-5-33)(A;;0x1;;;S-1-5-21-3903327414-3371247034-3746192915-1102)

Figure 11: Run the command
You can now close the text file, we don’t need it anymore. No need to save it.
Going back to the management workstation, open Event Viewer or open DNS management console as the DNSManager user, and behold, you can now view the DNS Event Logs:

Figure 12: Problem solved, the DNS Event Logs show up

Figure 13: Problem solved, the DNS Event Logs show up