Valuable for Windows professionals atall skill levels, this book will be especially indispensablefor intermediate-to-advanced level professionals seeking expert,in-depth solutions. Every chapter contains tips, tricks, bestpractices, and lessons learned from actual deployments: practicalinformation for using Windows Server 2012 to solve real businessproblems.
The OpsMgr Unleashed team is pleased to publish an additional simple management pack to cover Cloud Backup. Now you can further extend OpsMgr to watch the health of your file servers protected by Windows Server Backup to Azure. Both sealed and unsealed versions of the management pack are contained in a single ZIP file. You can download the management pack ZIP file from this link: -content/uploads/2014/05/CloudBackupManagementPack.zip.
Add an entry to the local c:\windows\system32\drivers\etc\hosts file for each OpsMgr management server in the resource pool that will be managing UNIX/Linux hosts for the IP address and proper DNS name of the UNIX/Linux server
The setup GUI for Windows Server 2012 is very similar to the installation process for Windows Server 2008 and Windows Server 2008 R2. After the installation software loads into memory, the configuration setup pages have a consistent look and feel. Each step outlined in the following sections also has integrated links to relevant Help topics. Many of the choices and options that were historically part of the pre-installation setup process in Windows 2000/2003 are now relegated to post-install configuration after the base OS installation has completed. Therefore, the steps required during initial installation are minimized, allowing for a faster installation and more streamlined initial process, consolidating operations pertaining to settings specific to the final role of the server to the post-installation phase.
The first element when installing Windows Server 2012 is to choose the language to install on the server. Usually, the language selected is English; however, the language selections vary based on a region. Examples of languages include English, Arabic, French, Dutch, Spanish, and many more. The next element to be specified is the time and currency format. This setting dictates how the server will handle currencies, dates, and times, including daylight savings. The final element is the keyboard or input method. Specify the country code, such as US, Canada, or China, and click Next to begin the installation.
The next page in the installation process is Select the Operating System You Want to Install. One of the first items that needs to be addressed on every new installation of Windows Server 2012 is which edition and type of operating system will be installed. The options include a Full installation or a Server Core installation. A Full installation is a traditional installation of Windows and includes all the user interfaces and supports all the server roles. As mentioned earlier, a Server Core installation is a scaled-down installation of Windows Server 2012 with the intent to reduce the attack surface and management.
In addition to the server type, the operating system edition must also be selected. Here, again, Windows Server 2012 simplifies the choices with two editions: Standard and Datacenter. There are no longer any feature differences between the editions, only a difference in hardware and virtual systems supported.
On the Which Type of Installation Do You Want page, you can either select to upgrade an existing Windows server or install a clean copy of Windows. Because this is a clean installation and a legacy operating system does not exist, the upgrade selection will present a message to this effect and prevent the installation from proceeding. Therefore, in this scenario, select Custom: Install Windows Only (Advanced) to perform a clean installation of Windows Server 2012. Click Next to continue, as shown in Figure 3.1.
After the Windows Server 2012 Install Windows Wizard collects the information and installs the Windows operating system, the system restarts. The administrator must set a password before logging on to complete the installation process. When logged on, Server Manager is automatically invoked and presents the Dashboard view, which provides a quick-start series of steps to getting started with the server. By selecting the first link, Configure This Local Server, the Local Server view is activated and presents basic information about the server as well as links to common core configuration tasks, as shown in Figure 3.3. These tasks are commonly used to initially configure the server:
The first configuration task to perform after installing Windows Server 2012 is to set an administrator password. This must be done before you can log on the first time. The installation process automatically creates the default administrator account called, surprisingly enough, Administrator. This account has local administrative privileges and enables you to manage all local configuration settings for the server. For security reasons, it is a good idea to rename the account after the installation.
Even though you might have selected the option in the previous steps to automatically configure server updates, it is still possible to download and install updates manually by clicking the links next to Last Installed Updates and Last Checked for Updated. When these are clicked, the server connects to the Microsoft Windows Update site. Before configuring roles or features or making your server available to users on the network, it is a best practice to install the latest updates and patches from Microsoft. If your environment uses an automated tool such as WSUS, tested and approved patches might already be installed by your update and patching infrastructure if the system was joined to the domain and is configured to do so.
Unless you configure exceptions to the firewall, users cannot access resources or services on the server. Exceptions to this are roles and features installed using Server Manager or PowerShell. Many roles and features automatically create the required exceptions for their own workload, enabling you to leave the firewall on while allowing access to specific functions on the server, if desired. With Windows Server 2012, it is possible to configure incoming and outgoing firewall rules on each network connection using the Windows Firewall with Advanced Security console available from the tools menu in Server Manager.
Windows Server 2012 introduces network interface card (NIC) teaming as part of the operating system. Click the Network Adapter Teaming link to open the NIC Teaming configuration dialog, from where you can create and manage teams on local and remote servers.
The latest version of System Center Configuration Manager (SCCM) is a dramatic update of its predecessor Configuration Manager 2007, and this book offers intermediate-to-advanced coverage of how the new SCCM boasts a simplified hierarchy, role-based security, a new console, flexible application deployment, and mobile management. You'll explore planning and installation, migrating from SCCM 2007, deploying software and operating systems, security, monitoring and troubleshooting, and automating and customizing SCCM 2012 with scripts. 2b1af7f3a8