A quick glance at this page here Formal Reading for AAG is always a good start. This post would cover some of the more technical aspects involved. To begin with setting up the Windows Failover Cluster would be the initial task to be completed. (more…)
So the scenario is that I have an instance of Windows Server 2012 (Windows Server 8 Beta) running on VMware Workstation 8 on my laptop.
Adding Hyper V role to the server
The other error that has been recorded:
Shutdown the Windows Server 2012
Browse to your VM location and open the vmx file and append at the end the following two lines
hypervisor.cpuid.v0 = "FALSE"
Save and power up your VM
Let’s try that again
Now you should be able to go on and configure your Hyper- V role on the server.
Windows 2008 R2 Core SP1 – Domain joined, updated.
Denali RC0 ISO File attached to VM.
Preparing Windows 2008 R2 Core for Installation
- Run the following Command File to pre prep the server.
DISM /Online /Enable-Feature /FeatureName:ServerCore-WOW64
DISM /Online /Enable-Feature /FeatureName:NetFx2-ServerCore
DISM /Online /Enable-Feature /FeatureName:NetFx2-ServerCore-WOW64
DISM /Online /Enable-Feature /FeatureName:NetFx3-ServerCore
DISM /Online /Enable-Feature /FeatureName:NetFx3-ServerCore-WOW64
DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShell
Start /w ocsetup ServerCore-WOW64
Start /w ocsetup NetFx2-ServerCore
Start /w ocsetup NetFx2-ServerCore-WOW64
- Download a special .net 4 package for Windows 2008 R2 Core from this location here.
- Run the .net 4 package and have it installed.
- Run sconfig.cmd and choose option 6 to install any further updates.
- Reboot the server
After this process, the Windows 2008 R2 SP1 Core is ready to be installed with Denali.
- Denali can only be installed on command line prompt at this stage. But as far as testing goes, with some special modifications you can modify the installation experience to involve the GUI mode as well.
- The process described here involves , my favourite way of installing SQL, using a configuration file.
;SQL Server "2012" RC0 Configuration File
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
; Detailed help for command line argument ENU has not been defined yet.
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
; Setup will not display any user interface.
; Setup will display progress only, without any user interaction.
; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components.
; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services.
; Displays the command line parameters usage
; Specifies that the detailed Setup log should be piped to the console.
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.
INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.
INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
; Specify the installation directory.
INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
; Agent account name
; Auto-start service after installation.
; CM brick TCP communication port
; How matrix will use private networks
; How inter brick communication will be protected
; TCP port used by the CM brick
; Startup type for the SQL Server service.
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
; Set to "1" to enable RANU for SQL Server Express.
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
; Account for SQL Server service: Domain\User or system account.
; Windows account(s) to provision as SQL Server system administrators.
; Provision current user as a Database Engine system administrator for SQL Server 2012 RC0 Express.
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
; Startup type for Browser Service.
Description for the configuration file
- Install mode to install a fresh install of Denali
- Installs only the Database engine and the Replication Service for SQL
- No Management Studio and Tools
- Uses default location for Data, Log , TempDB, TempLog and Backup File Location
- Domain_Name to be replaced with the domain name
- SQL_SERVICE_ACCOUNT to be replaced with the SQL Service account that you would use to run the SQL Services for Database , SSRS etc
- SERVICE_ACCOUNT_PASSWORD – password for all the service accounts
- SQL_ADMIN__ACCOUNT1 and 2 is for the SQL Admin Account.
Command Line file to kick start the Denali Installation using the above mentioned Config File
D:\Setup.exe /CONFIGURATIONFILE="C:\Scripts\SQL\DenaliConfig.ini" /INDICATEPROGRESS /SkipRules=NoReboot
Description for the command line file
- D:\Setup.exe – location of your Denali ISO or Media
- “C:\Scripts\SQL\DenaliConfig.ini” – location of this command line and config file on the Core SP1 server.
- /SkipRules=NoReboot – Issue with Core installation involving Denali – need this parameter for it to work. Reboot the system after installation is completed J
To have a view of all the parameters and installations available using configuration file here over here.
Tips and Tricks I picked up during this process
- To get to making folders and copying files (.net 4 installer , scripts etc.) over to the server core , try browsing from another domain joined machine to the core machine using \\NAME_CORE_SERVER\C$
Spend some time on sconfig.cmd especially Configure Remote Management Features of server core
- Use Remote Computer Management from “MMC” console of a domain joined machine to manage your server core.
So one of my SharePoint projects that I am working on requires Federated Stuff and hence for all my testing I require two AD networks. As I have only one single ESXI server with one nic card, I was wondering how best to create a sort of NAT between two Virtual Switches. But since one Virtual Switch is already connected to the LAN and running live servers , I didn’t want to break anything. So I need some kind of firewall between both the different networks. My search led to Zentyal . They have a Virtual Machine appliance which is available here .
My Original network was pretty straightforward. I had a router connected to my ISP which leads onto a switch and wireless router that served all my devices and an Esxi Host with One network card that kept all my Domain Controllers, Exchange, SharePoint and Database servers.
I The issue was that this weekend I had to prepare for Demo purposes , Federated Domains with ADRMS and SharePoint , Exchange , Lync and Database servers all existing on another demo domain. No issues building new VM’s and stuff but my problem was that I had only one Interface card on my Esxi host. I was trying to figure out how best can I split my Vmware Network as two different networks but all using the same Router to get to the Internet. I needed a new firewall in front of the New VM farm that I was building. So while all the VM’s were getting provisioned out I had some downtime while I waited.
So this is what I came up on paper. The steps involved where
- On my Esxi host, I created a new Virtual Switch and gave it a really meaningful name : Demo Network J
- Then Imported the Zyntal VM and gave the VM two virtual network cards. I connected Network Card 1 to the my LAN Virtual Switch, and the other network card to the new Virtual Switch that I created on Step 1
- Powered up the VM. The VM got an IP from my LAN DHCP on its Network Card 1 and so I was able to browse to the Firewall through that IP.
- Then it was pretty much setting up Gateway properties , Static Routes, a few Firewall rules so that I can RDP to all the servers on the Demo network and share Files and Internet and walla , a completely new network , a new domain with its own firewall and Domain network. Now I just hope my esxi host doesn’t die with all the over congestion.
It comes with a Windows style GUI and approach even though its built on linux