Jun 27

Windows Server 2012 R2 (70-412) Configure Network Services – Study Guide

Prepare yourself for the Microsoft MCSA 70-412 exam. This course explores how to implement an advanced DHCP solution, implement an advanced DNS solution, and deploy and manage IP Address Management.

 

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and2012GregShieldscmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

All, or nearly all, sections include DEMOS so I’m not notating that separately.

 

  1. Implement an Advanced DHCP Solution
    1. Create and configure superscopes and multicast scopes
      1. superscopes – combine multiple DHCP scopes to have broader range of addresses
      2. initial subnet didn’t have enough addresses
      3. when you run out of addresses;
        1. define by geographical location; floor, building, city, etc.
        2. assign multiple network IPs to router (downside is network admin involvement)
        3. DHCP RELAY – we’ve been there…allows DHCP traffic to cross router
        4. DEMO
          1. In DHCP, create superscope, then add multiple scopes to it
          2. Multicast scope –
            1. create Multicast scope, pick start/end IP, set TTL
            2. unlikely would be allowed on most modern networks
            3. most common use is WDS or other desktop deployments
    2. Configure DHCP filters and policies
      1. nodes in DHCP mmc
        1. filters; allow or deny by MAC
        2. then have to “enable” by checkbox
        3. can set exemptions
        4. Policies; what options will the managed machines get
          1. vendor class
          2. MAC
          3. FQDN
        5. Then set what treatment those hosts that fit the policy actually get
    3. Implement DHCPv6
      1. Not a lot of real world use yet
      2. NOT very simple
      3. built into IPv6 can auto assign anyhow. Don’t believe it read this article…IPv6 address autoconfiguration
      4. This would be used for anything beyond what the protocol can do.
      5. CANNOT assign a default gateway
      6. CAN assign most other options
      7. NOT really needed for auto assignment, more used for address control
      8. DEMO
        1. click on IPv6, right click “new scope”
        2. etc. pretty much like IPv4
        3. beware of test questions about WHY you would use it.
    4. HA for DHCP – failover and split scopes
      1. split scopes (the old way)
        1. 80% / 20% is the most common (I’m sure I’ve seen test questions that said that was wrong though).  Well the 80/20 split scope is Microsoft best practice see here.
        2. Can be messy recovering from a server outage; the DHCP databases don’t know anything about what the other one is doing.
      2. DHCP Failover
        1. one DB
        2. can use 100% of scope
      3. DEMO
        1. split scopes (split scope configuration wizard)
        2. DHCP Failover
          1. per scope
          2. “Configure Failover”
          3. set load balance or hot standby and some other settings
          4. you can enable message authentication via shared secret
          5. Configure DNS registration, can discard as well
    5. DHCP Name Protection2012DHCPNameProtection
      1. mainly for non-windows computers (screenshot)
      2. prevents non-windows from registering a name that is already in use.
    6. DNS Registration
        1. Configure DNS registration, can discard as well
  2. Implement an Advanced DNS Solution
    1. Configure Security for DNS, including DNSSEC, DNS Socket Pool, and Cache Locking
      1. DNSSEC does not necessarily require certs.
      2. To enable you “sign” the zone.
      3. Key Master is the authoritative DNS server that generates and manages the key for the zone.
      4. when you create the new key, then you have all kinds of options
      5. Needs to be AD integrated zone
      6. KSK – Key Signing Key and ZSK – Zone Signing Key
      7. Trust Anchor (for authenticating non-authoritative server
      8. Then GP is used to tell clients to ask for the DNS key
      9. “name resolution policy”, checkbox for enable DNSSEC
      10. create rules to determine who it applies to
      11. DNS Socket Pool (in response to Kaminsky attack DNS vulnerability)
        1. randomizes the SOURCE PORT to not be using TCP/53 and UDP/53
        2. enabled by default, but you tweak settings like number of ports
        3. DnsCmd /config /socketpoolsize 100000
        4. DnsCme /info /socketpoolsize
      12. Cache Locking
        1. Locks cache after update in cache.
        2. cannot be overwritting by a percentage of TTL
        3. default is 100% of TTL
        4. DnsCmd /config /cachelockingpercent 50
    2. Configure DNS Logging
      1. two places it can be configured depending on what you want
      2. event logging (1)  goes into event logs
      3. debug logging (2) goes into file
    3. Configure Delegated Administration
      1. under “security” tab
      2. for you to delegate activities, you MUST have AD integrated zone (test question?)
    4. Configure recursion
      1. disabled by default
      2. servicing servers outside your network
      3. should be ON on external server to prevent DNS attacks
    5. Configure Netmask ordering
      1. common use – WSUS
      2. essentially allows DNS server give a client an address that corresponds to the subnet that they are in. For traveling users.
      3. First response goes to server with same subnet
    6. Configure Global Names Zone
      1. for needs that used to be handled by WINS
      2. short name resolution
      3. create a zone called “GlobalNames”
      4. will contain short names
      5. you have to explicitly enable on all DNS servers
      6. dnscmd servername /config /enableglobalnamessupport 1
    7. Analyze Zone level statistics
      1. Get-DNSServerStatistics -zonename company.local
      2. DNSLint
        1. graphical display of internal/external on .htm file
        2. dnslint 
  3. Deploy and Manage IP Address Management – IPAM
    1. Provision IPAM via manual or GP
    2. IMPORTANT NOTE: to change  the IPAM provisioning method (like from manual to automatic) you must UNINSTALL and REINSTALL!
      1. install FEATURE
      2. configure from Server Manager
      3. choose database (internal or SQL)
      4. GPO Name prefix (manual configuration of IPAM is tedious and not recommended)
      5. run PS command Invoke-IpamGpoProvisioning -Domain ….creates the Group Policies and links them.
      6. Run IPAM server discovery
      7. Choose the ones you want and set them to managed.
        1. managed servers need to show up in “security filtering’ box on the GPO
        2. machine has to receive and apply the GP before it shows as “unblocked” and “managed”
        3. IPAM is more of a “push” instead of pulling in existing IP use
        4. IP Address block
          1. 1 or more IP ranges
        5. Add address range (block of IPs or open range that IPAM can use)
        6. can add reservations and VIPs
        7. along with normal DNS, gateway and other information
    3. Configure server discovery
    4. create and manage IP blocks and ranges
    5. migrate to IPAM
      1. tasks / import IP addresses (imports from .csv). certain mandatory columns for IPAM imports – IPAddress,IPAddressState,AssignmentType,ManagedByService,ServiceInstance,AssetTag
    6. monitor utilization of IP address space
      1. lirrlw pie chart by each range, can be adjusted for the entire server
    7. delegate IPAM administration
      1. there is an “ACCESS CONTROL” link on the very bottom left to set up roles and access.
      2. several default roles but you can create your own customized roles and set the policy settings
    8. Manage IPAM collections
      1. request new addresses (fine and allocate) “find next”
      2. RECLAIM ip addresses that are no longer used, delete resource records and DHCP reservations if exist.
      3. EVENT CATALOG – log viewer of IPAM events
      4. ADDRESS RANGE GROUPS – group by custom fields you defined during IP creation
    9. configure IPAM database storage
      1. PS Move-IPAMDatabase (moved internal IPAM DB to SQL if you want)
      2. lots of IPAM powershell commands (automation possibilities)
Jun 24

How to create RDM mappings for SQL Clustering with MSCS on VMware 6.0

How to create RDM mappings for SQL Clustering with MSCS on VMware 6.0

Using vSphere 6.0

For the sake of this discussion, we’re building two VMs for use in a two node failover MSCS cluster for SQL 2012.  We’ll simply call them A and B.

We will be using the Web Client for this, since that’s the direction VMware is pushing. However, the Fat (C#) client is faster for this task as it takes fewer steps.  For example, on the fat client, when you create the first RDM mapping, it will automatically create a new, second SCSI controller. When on the web client, you have to manually create the SCSI controller first, then start building the RDM drives.

The documentation in the 6.0 documents is very sparse, and I don’t think it’s even complete or accurate so this took a bit of effort to figure out and get set up.

Add a new SCSI Controller (we had issues with other “types” and use VMware Paravirtual exclusively now)
mscs2mscs1

Add a new disk;
mscs3Select the target LUN by LUN ID;
mscs4

Choose your new SCSI controller 1 (not like picture) and pick an unused SCSI ID.
mscs5

 

This shows the proper SCSI controller and ID selection.
mscs6

After creating this, go to the Windows OS on A, bring disk online, initialize, format, name, label, etc.

Now go to server Node B and add a RDM pointing to that exact same file.
mscs7

You told it to store the VMDK pointer “with the server” so go to that datastore and fine the VMDK that was created by the new drive creation on A. When you create this drive in VMware on B, then you can go into the OS on the B node and the drive should show up there labeled and formatted and drive lettered.

If you keep track of it as you go, you can add several drives at once on A (2,3,4,5,6,7…) and it will create them all at once, then go over to B and add/create them all at once. But you have to keep your VMDK names and LUN IDs straight so you know which one is which. Doing one at a time is slower but less confusing.

 

How to tell (after it’s created) which VMDK file a new RDM is using on A, so you can find the correct VMDK when you create B;

Go to “Edit Settings” then at the top there is a “Manage other disks”
mscs8

Open that button, then drop down the details on the disk you’re looking at and it will show you the VMDK and datastore. This VMDK is just a “pointer” or “mapping” file to the LUN.
mscs9

mscs10

mscs11

Pick the SAME SCSI controller and port that you did on A;
mscs6
ISSUES ENCOUNTERED;

Set LUNS as “perennially reserved”.  If this is not set right, the ESX HOST will take HOURS to boot, depending on how many RDMs it has to scan. Ours took 2.75 to boot. When this was set right via esxcli, they would boot in about 6 minutes, counting the HP specific boot processes. This is addressed in this KB, scroll down to the “perennially reserved” section. ESXi/ESX hosts with visibility to RDM LUNs being used by MSCS nodes with RDMs may take a long time to start or during LUN rescan (1016106)

 

EXPANDING RDM sizes. 

PARAVIRTUAL driver

Jun 24

Windows Server 2012 R2 (70-412) Configure High Availability – Study Guide

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and2012GregShieldscmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

All, or nearly all, sections include DEMOS so I’m not notating that separately.

  1. Configure Network Load Balancing
    1. most commonly used with IIS
    2. stateless (doesn’t matter what node user connects with)
    3. Configure NLB Prerequisites
      1. install Feature
      2. Unicast, Multicast, IGMP Multicast
      3. Unicast
        1. always works
        2. 1:1
        3. requires a second NIC on each server
        4. causes subnet flooding; all traffic to all hosts goes to all hosts
      4. Multicast
        1. no second NIC
        2. network configurations
        3. does not solve subnet flooding
      5. IGMP Multicast – best practice
        1. no second nic
        2. network requirements
        3. solve subnet flooding problem
    4. Install NLB Nodes
    5. Configure Cluster Operation Mode
    6. Configure Port Rules and Affinity
    7. Upgrade an NLB Cluster
  2. Configure Failover Clustering (read prior post here)
    1. Cluster Storage
      1. shared storage is not built in Windows; it’s a foreign concept
      2. proper configuration of storage is critical
      3. iSCSI, FC, Storage Spaces (in our previous FS training)
      4. we’re using iSCSI here in this demo
    2. Configure Cluster networking
      1. best practice to separate cluster private network and storage network
      2. Failover Cluster Manager – console for cluster management
      3. Cluster Validation wizard (lots of experience with this 😉
      4. In this Demo, Cluster Private network, Storage network, and Management / Production
      5. Check the networks in Failover Cluster Manager
    3. Cluster Shared Volumes (CSV) used by Hyper-V virtual machines
      1. Quorum (chosen by smallest size)
      2. Available Storage LUNs (if containing a VM, they all would have to fail over at the same time (or each have dedicated LUN)
      3. CSV, each VM can fail over individually
      4. you can define a disk as a CSV, and you can revert also.
      5. More here on Using CSV for Failover Cluster
        1. CSV cache size configuration; (Get-Cluster).BlockCacheSize = 512 for Server 2012 R2, for more read the link above.
      6. Quorum configuration
        1. Quorum is only to identify if enough of a cluster remains to still operate as a quorum.
        2. Quorum Models (dependent on number of nodes)
          1. Node majority (used for ODD number of nodes)
          2. Node and Disk Majority (even number of nodes)
          3. “split brain” when cluster breaks into two separate groups of nodes who each think they are quorum
          4. No Majority Disk Only (old, not used any more)
          5. Node and File Server Majority (special considerations) even nodes, multi site. The separate vote goes to a disk file share somewhere.
        3. Configure quorum model in Failover Cluster Manager
          1. MS automatically manages cluster quorum setting now. “use default quorum configuration”
          2. Or, you can go to advanced features and dance with the complexity on your own.
      7. Clusters without network names (detached cluster) Deploy an Active Directory-Detached Cluster
        1. SQL server outside your firewall
        2. not supported for several additional roles
        3. no bitlocker
        4. no CAU (Cluster Aware Updating)
        5. read the link
        6. cannot use FOCM
        7. PS – (Get-Cluster).AdministrativeAccessPoint
          1. read the link for more
      8. CAU (Cluster Aware Updating)
        1. “update cluster” item in Server Manager
        2. allows cluster to manage resource movement to update nodes/hosts.
        3. configure self-updating options wizard
        4. add the ROLE on the cluster
        5. choose schedule (normal WSUS stuff)
        6. reboot timeouts, max retries, pre or post scripts, recommended / important
        7. All the above is for Windows updates, not WSUS
        8. “Analyze cluster updating readiness”
        9. PS
          1. Cluster-Aware Updating Cmdlets in Windows PowerShell
      9. Restoring single node of cluster
        1. Evict = kicking node out
        2. restore configuration from backup (make sure you have system state)
      10. Upgrading a cluster
        1. not recommended to directly upgrade a cluster
        2. this is a cut and move
        3. “copy cluster roles” from a wizard from the TARGET cluster, connect to OLD cluster to get configs.
  3. Manage Failover Clustering Roles
    1. remember MSCS is a “general purpose” clustering solution
    2. role-specific settings
      1. DFS, SHCP, DTC, FIle Server, iSCSI target, etc., etc..
      2. Generic application, script, or service
      3. DEMO – clustered NOTEPAD via Generic Application
      4. cluster is a SINGLE instance of the app that fails from node to node, moving the resources (including created drives) as needed
      5. Continuously available file server
        1. General Use, or SOFS (Scale Out File Server) (used for Hyper-V and SQL)
      6. Configure Virtual Machines
        1. do not put SOFS and VMs on same CSV
    3. fail-over and preferences
      1. ROLES (shared app, file server, VM, etc.)
      2. move, stop, change startup priority
      3. no autostart
      4. add resources or storage
      5. “show dependency” report
        1. graphical representation of dependencies
      6. “preferred owner” unchecked can be used, just not preferred
      7. failover max
      8. failback now/yes, set hours it can happen
      9. cluster handles DNS records for cluster required records
      10. you can manually add dependencies
    4. possible and preferred owners
      1. possible owners (cannot be on any node that is not checked)
      2. preferred owner (can use unchecked nodes, they’re just not preferred)
    5. guest clustering
      1. another layer of abstraction
      2. simply means clustering VMs that are on the MSCS cluster
      3. shared .VHDX2012EnableVirtualHardDiskSharing
      4. new feature (like RDMs) in VMware
      5. advanced features “enable virtual hard disk sharing”
  4. Manage VM Movement
    1. Migration – Live, Quick, Storage
      1. Quick
        1. the old fashioned, with a quick period of loss of service
      2. Live
        1. no loss of service
      3. Storage
        1. moving the .vhdx, the data
      4. Quick is technically faster, and uses less bandwidth than Live
      5. Live – procs need to be same manufacturer and similar family
      6. virtual switches needs to be named the same
      7. physical devices must be disconnected
      8. DEMO
        1. constrained delegation has to be configured to the hosts that you want to migrate to/from
        2. CredSSP alternative to Kerbos/constrained delegation but CredSSP requires you to log onto the machine to start the migration
    2. Import, Export, Copy
      1. have to export/import if you can’t do quick/live migration
    3. Configure VM Health Protection
      1. move to locations without proper networks, or something similar
      2. VMHP is under Network Adapter / advanced features
      3. it will move it back to prior location if it ends up isolated
      4. ENABLED by default
    4. Configure Drain on Shutdown
      1. drain a node on shutdown
      2. ENABLED by default
    5. Configure VM Monitoring
      1. “resources” tab on bottome of Failover Cluster Manager
      2. checkbox to enable automatic recovery for application health monitoring
      3. if/when enabled, you can select services via checkbox that you want to include for application monitoring.
Jun 16

Windows Server 2012 R2 (70-412) Configure Active Directory – Study Guide

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and2012GregShieldscmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

  1. Introduction
    1. Not about the basics, this is 412 training so the basics should be in place
    2. Multiple Forests, multiple domains
    3. Configure a Forest or Domain
    4. Configure Trusts
    5. Configure Sites (remember from an era when WAN connectivity and site replication was expensive)
    6. Manage Active Directory and SYSVOL Replication
      1. RODC
  1. Configure a Forest or Domain
    1. implement multi domain and multi forest AD, with interoperability with previous versions of AD.
    2. Upgrading existing domains and forests, including preparation and functional levels
    3. Configure multiple UPN suffixes
    4. Used to require contiguous namespace; contoso.com, denver.contoso.com, paris.contoso.com.
      1. now we can use DISJOINTED namespaces. can have a forest with the following domains;
        1. contoso.com
        2. denver.contoso.com
        3. widget.com
        4. This is called a TREE DOMAIN (as in “forest”, “trees” I suppose….) vs. the old
          2012TreeDomain

          TREE (disjointed) domain

          CHILD DOMAIN

    5. When would you want to use a multi domain structure (desired state now is to minimize)?
      1. habit essentially
      2. political or organizational
      3. Autonomy (separation)
      4. Data isolation
      5. Segregation for replication /authentication /authorization
      6. SECURITY is not one of the reasons as part of the same forest.
    6. Multi Forest structure
      1. when two forests merge (purchase a company, etc.)
      2. two forests connected by a TRUST of some sort.
      3. Trusts require MANUAL creation
      4. Different requirements for AD Schema can dictate multiple Forests
      5. Exchange Organizations (In Exchange, only allowed one, so if your Exchange needs require more, then you are multi forest)
    7. Permissions required for creation
      1. To build a new forest, Local Admin on first DC (there is no AD yet)
      2. To build a new domain tree or child domain, you must be Enterprise Admin
      3. To add additional DCs, you must be a Domain Admin
    8. Upgrade Process for Domain or Forest (know this process)
      1. get healthy (make sure everything is working right)
      2. extend the schema (essentially adding columns to AD database, or new characteristics or fields) (ADPREP)
      3. upgrade DCs to new OS (all DCs need to be upgraded prior to raising functional level). Hopefully you don’t have hundreds of DCs.
      4. relocate FMSO roles if needed
      5. raise domain/forest functional level
    9. DEMO – extend schema
      1. adprep (link above)2012_adprep_cmd
      2. uses the stack of .ldf files where adprep resides
      3. remember you can view these attributes in the ad database using ADSI Edit.
      4. adprep
        1. first use /forestprep
        2. then /domain prep
        3. optionally /gpprep, and /rodcprep
      5. now raise the functional level
        1. ad domains and trusts
        2. cannot go backwords, this is a one way road.
      6. What’s new in the functional levels
      7. Creating new UPN suffix
        1. AD Domains and Trusts, UPN suffixes
        2. add what you want in AD D and T
        3. then in ADUC you can use them in the user account tab
  2. Configure Trusts
    1. Configure External, Forest, Shortcut, Realm
    2. Configure trust authentication
      1. Forest wide, or “selective”
    3. Configure SID filtering
      1. Get-ADUser  -filter * | select SAMAccountName,sid (returns SIDS for users)
      2. SID filtering is on my default in external trusts.
      3. used in domain object migrations (from domain to another)
      4. has to be turned OFF to migrate (only time you would do this)
      5. SID history has to be ENABLED to migrate objects, which requires turning off SID filtering. Example; move a user to different domain, if you don’t do this properly a new SID is created and they lose access to printers they used prior. With SID history ENABLED, user object retains a history of both SIDs
      6. Detailed explanation and example of disabling SID filtering, enabling SID history here.
    4. Configure Name Suffix Routing
      1. determine what name suffixes get passed / routed to other side of trust
    5. Fundamentals
      1. trusts have direction – trusting, vs. trusted
      2. the direction is opposite of the direction of access
      3. remember by “wing it” is ‘eng -> ‘ed.   From trustING to trustED.
      4. most are bi-directional
      5. can be transitive (if A trusts B, and B trusts C, then A trusts C)
      6. different types
        1. External from one domain in one forest to domain in a different forest
        2. Shortcut – literally a shortcut to another domain in same complex forest. Not common as AD simplifies
        3. Forest – between two forest roots; everything in forest is trusted. Transitive. Most common type of trust. Acquisitions. Always transitive. Can configure rules of authentication.
          1. Need name resolution to set up. Can be done by consolidating nameservices. In larger environment, conditional forwarders.
          2. create from AD Domains and Trusts
          3. can create both halves of trust from one side (one server)
        4. Realm trust – to non-AD Kerberos realm / Linux
  3. Configure Sites
    1. Created for AD replication across geographical locations
    2. Associated with subnets (VYOS router for lab)
    3. KCC (knowledge consistency checker)
    4. Configure Sites and Subnets
      1. rename “Default-First-Site-Name”, use it and create additional as needed
      2. create subnets and associate to sites
    5. Create and Configure Site Links
      1. Inter-Site transports
      2. most of the time is IP, NOT SMTP
      3. all sites are added to IP default site link
      4. absolute value of the cost is meaningless, only the RELATIVE value (compared to other links) has meaning
      5. A lot of this had more meaning when network connectivity was expensive and low capacity
    6. Manage Site Coverage
      1. you need a DC in each site
      2. are the DCs Global Catalogs (old times was limited due to processing power, bandwidth)
      3. now best practices are simply make every DC a GC
      4. if multiple DCs in a site, define a preferred BridgeHead server. Or leave this alone and leave it to KCC.
      5. best practice is leave it to KCC
    7. Manage Registration of SRV Records
      1. determines what DC site computers use
      2. ipconfig -registerdns make the DC set srv records
    8. Move DCs Between Sites
  4. Manage AD Replication and SYSVOL replication
    1. Upgrade SYSVOL replication to DFS-R (Distributed File System Replication)
      1. If you have an old, upgraded, AD, you might not be on DFS-R and still on the old FRS (File Replication Service)
      2. upgrading to DFSR
        1. three steps after get healthy, migrate to prepared state, migrate to redirected state, migrate to eliminated state
        2.  dfsrmig /?  (powershell for DFSR migration)
        3. dfsrmig /getglobalstate
        4. results will be “prepared”, “redirected”, or “eliminated”
        5. only do one step at a time then WAIT
        6. Some health check commands
          1. gwmi – class win32_logicaldisk – ComputerName yourcomputername (shows drive space)
          2.   repadmin /syncall /force /aped (forces domain sync and ignore all schedules)
          3. update-DfsrConfigurationFromAD
    2. Configure replication to RODCs
      1. single use case; unsecure branch location. only contains passwords and content for that branch
      2. never log onto RODC with privileged  account
      3. delegated RODC administrator (the selected group can administer the RODC (“managed by” tab)
    3. Configure password policy replication for RODCs
      1. set policy for which PWs you want to cache on RODC (password replication TAB)
      2. you can see what users/computers are replicated to RODC on “advanced” tab.
    4. Monitor and manage replication
      1. sites and services – right click and “replicate now” from AD Sites and Services
      2. repadmin /replicate server1 server2
      3. repadmin /showrepl
      4. repadmin /kcc
      5. repadmin /prp view servername reveal (shows RODC replication)
      6. in GPMC, look at a domain, you can see replication status
      7. dfsdiag
      8. nltest (tests if you can locate a DC)
      9. AD Change Notification (replicates to all sites instantly)
        1. ADSI edit
        2. sites
        3. “options”, from blank to “1”, now replicates across sites at same replication as intrasite replication.

 

 

Jun 15

Windows Server 2012 R2 (70-412) MCSA and the 70-412 Exam – Study Guide Part 2 – build a lab

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and2012GregShieldscmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

As mentioned previously, the second section of this course seem like it was going to focus on how to build a lab in preparation for training, so I broke it into a separate post.

Windows Server 2012 R2 (70-412) MCSA and the 70-412 Exam

Building Your 70-412 R2 Environment

  1. VMware workstation
    1. please note; VM Workstation is a licensed product; you have to PAY for it. You can get a 30
      TG-LAB

      My physical lab 5 DL380 G5s (one not in picture) and two DL360 G5s. The G4s are being decomissioned.

      day trial of VM Workstation here. Also, if you have ever passed a VMware certification (like me) then you get a free license as one of your benefits. So, for example, I have a permanent license for Workstation 10, but cannot upgrade without buying a new license. I suppose you could do this lab on VBOX also if you have familiarity there. At the end of this I will also post some links to good sites about virtual labs.

  2. VM infrastructure and IP scheme
  3. Forest infrastructure
  4. Understanding the Network Infrastructure
  5. VyOs router for network routing
  6. Use of templates or clones. Discussion of Linked Clones to minimize disk use. Linked Clones are a VMware specific ability. VMware Linked Clones use the same virtual disks as the parent. So you could have 10 linked clones using one set of disks, with a very much improved storage use scenario especially in a lab.
  7. Reviewing lab IP scheme and host design;
    1. 4 Domain Controllers
    2. 1 File Server
    3. 2 NLB hosts
    4. 5 Failover Cluster hosts
    5. 1 Certificate server
    6. 1 RMS (Rights Management Server)
    7. 1 ADFS (Active Directory Federation Services)
    8. 1 desktop
    9. Total of 1,2,3 let’s see 16 machines looks like all in VM Workstation running on one PC
  8. Forest infrastructure
    1. company.whatever
    2. separate forest to test ADFS
    3. three different sites
    4. 4 subnets; VMware Workstation doesn’t support subnetting which is why we have VyOS
  9. Setting up VYOS
    1. default username and pw is “vyos”
    2. setting up multiple NICs to support the subnetting
    3. adding 4 more NICs
    4. Configured VYOS
    5. Configured internal home router for the appropriate vlans

Ok that’s about it. It does looks like a pretty good way to set up this all in a virtual lab. I’d like to see how it performs but probably pretty well since he put all the drives on a separate SSD.

Here are some of the other links I have gathered on building a lab. Some focus on low power (electricity costs), some focus on being quiet (don’t need the disturb the spouse) and some on different things. I’ve had the good fortune to be able to collect some HP G5 servers which I have been able to use, using iSCSI and / or VMware VSAN for storage. I used this lab to study for and pass my VCP-DCV5.1 test.

Links;

Labs in general

While this one could go under “low noise” or “low power” they’re not really stated goals so I’m putting it here, it’s one of the best; http://packetpushers.net/vmware-vcdx-lab-the-hardware/

Similar lab build; http://rickmur.com/home-lab-server/

A more expensive ($3,000.00) work office targeted option using HP / CDW parts; (can this run ILO?) https://virtualizationreview.com/blogs/virtual-mattox/2012/03/build-cheap-screaming-virtualization-lab-server.aspx

Another good follow along lab; http://ethancbanks.com/2014/03/15/my-home-lab-esxi-5-5-server-build-and-the-logic-behind-it-all/ but this guy had a couple of Cisco SG300-52 switches that are worth min $400.00 each so not really cheap.

 

Nested / Low Power / Low noise or some combination

“nested” generally simply means you have one hypervisor running on another, or one hypervisor running as a VM.

Nested lab on VMware Workstation; low cost; http://www.heathreynolds.com/2014/02/building-nested-esxi-lab-on-vmware.html

Nested lab on ONE DL380 G5; http://www.running-system.com/how-to-build-a-nested-lab-on-a-hp-dl380-g5-server-step-1/ You can sometimes get a G5 on Craigslist for cheap or free. I got a couple for free, and I got a couple for as little as $90.00. There are thousands of these G5s still in production and they are solid hardware. Anything older than G5 won’t have processors that will support virtualization.

First one I have seen specifically on VMware 6.0 which just came out a few months ago; http://www.vladan.fr/nested-esxi-6-in-a-lab/

This looks cool; Intel NUC, low power (15w with 5 running VMs) http://www.vclouds.nl/how-to-build-a-low-cost-low-power-and-fast-esxi-home-lab/

Around 30w; https://matthill.eu/projects/vmware-esxi-low-power-home-lab/

VBOX lab

http://pc-addicts.com/building-the-ultimate-virtualbox-lab-intro/

In my experience, Memory is going to be the first constraint on a lab system no matter which method you choose. After that, probably storage. On nested environments (like this Pluralsight training) SSD would be a great idea.

Jun 14

Windows Server 2012 R2 (70-412) MCSA and the 70-412 Exam – Study Guide

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and 2012GregShieldscmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Greg Shields @ConcentratdGreg, the trainer, contact info at the end.

After doing the Advanced Features training, I’m expanding into the rest on Pluralsight and will go through as many as I can before my test date. This content should also apply to the 70-417. The 417 is the one I’m taking is a combination of 410, 411, and 412 all in one. It breaks down the score for each section. You have to pass all three sections. I have passed two of them (410 and 411) but not the 412, so if you fail one of them, you fail the entire test.

  1. An Introduction to the MCSA’s Final Exam2012Exams
    1. bunch of stuff about exam, objectives, strategy
    2. 417 is a combination of 410, 411 and 412
    3. Intended audience; ok.
    4. Without taking a bunch of notes, let’s just say review the exam objectives, just scroll down on the appropriate page for the specific exam you’re looking at;
      1. https://www.microsoft.com/learning/en-us/exam-70-410.aspx
      2. https://www.microsoft.com/learning/en-us/exam-70-411.aspx
      3. https://www.microsoft.com/learning/en-us/exam-70-412.aspx
      4. https://www.microsoft.com/learning/en-us/exam-70-417.aspx
    5. R2 specific information has  been included since January 2014.  So, while I don’t think you’ll have a lot of questions about the differences from 2012 and Server 2012 R2, I WOULD expect to know the new Server 2012 R2 features.
    6. Link on what is NEW in Server 2012 R2
  2. The next section is titled Building Your 70-412 R2 Environment 
    1. I’m going to put the next section in a new post focused on how to build a lab.
Jun 14

Windows Server 2012 R2 New Features Study Guide

Windows Server 2012 R2 New Features (test 70-412 or 70-417)

These notes are my personal notes from the FREE training on Pluralsight. You can get your FREE signup through technet/MSDN or Dreamspark. The title of this course is exactly the title of this post. These notes are from this specific course only. I use these as a refresher Study Guide. POWERSHELL topics and cmdlets are in purple. I have a few notes with the “DEMO” each time the training included a DEMO just so you can see how many demos there were which were really helpful. Thanks to Orin Thomas, the trainer, contact info at the end.

  1. Web Application Proxy
    1. Replaces AD FS Proxy role
      1. AD FS offers CLAIMS BASED Authentication (based on other atributes from user or computer accounts). For example based on employee type, location, title, etc.
      2. AD FS can work between organizations with different OS (Windows / Linux)
      3. Allows SSO for premise and cloud (like Office 365)
      4. Reverse proxy for web apps (prior might have used TMG / Threat Management Gateway)
    2. Web Application Proxy prerequisites
      1. supports pass through authentication
      2. AD FS preauthentication
      3. requries certs;
        1. cert that includes federation service name
        2. specifics for Workplace Join
        3. Certs for each web app, or wildcard cert
  2. Guest Clustering with Shared Virtual Hard Disks
    1. I think is the same as using VMware RDMs to sup MSCS clusters on Windows Server VMs. I’ve done a bunch of these at work with vShere 6.0 and Server 2012 R2
    2. Nodes can be on different hosts; AKA “Cluster Across Boxes” as opposed to “Cluster in a Box” which is both nodes on one physical host.
    3. Shared Virtual Hard Disks allow shared storage WITHOUT SAN.  What?
    4. More simple than iSCSI
    5. Needs to be highly available via
      1. scale out file server
      2. cluster shared volume
    6. shared storage needs to be .vhdx
    7. Gen1 or Gen2
    8. Only with 2012 and 2012R2 for OS
    9. DEMO
      1. build out clustered SOFS
      2. configure cluster file server
      3. add csv
      4. set up new share on SOFS using SMB-Applications
      5. Hyper-V hosts need to be able to access this location
    10. Then use Hyper-V console to attach the VHD to a SCSI controller
      1. has to be .vhdx
      2. fixed or dynamic
      3. ENABLE VHD sharing
      4. attach to SCSI controller
      5. bring disk online, iitialize, format volume
      6. can create multiple drives on same volume
    11. DEMO
      1. create VHD and create VM cluster
      2. enalble vhd sharing

        2012EnableVHDSharing

        enable VHD sharing

      3. after each VM (node) can see the storage then you can add the failover clustering FEATURE.
      4. then build the cluster
  3. Improving VHD Performance
    1. resizing VHDs
      1. used to have to be shut down, now can be running
      2. must be using .vhdx format
      3. must be connected to a SCSI controller (Gen1, or Gen2)
        1. Gen1 machines boot from IDE, so…
      4. resizing allows to set smaller size upfront, knowing expansion is simple.
      5. use Hyper-V console or Resize-VHD Powershell command
      6. DEMO of above steps
    2. Storage QoS
      1. set max/min IOPS

        2012SetIOPSonVHD

        set IOPS limits

    3. Storage Tiering
      1. via storage pools
      2. automatic; turn in and it moves based on activity
      3. CAN  manual settings
  4. Windows Server 2012 Clustering Improvements
    1. VM Drain on shutdown
      1. If you put a VM in maintenace mode, then VMs are moved to another host.
      2. HOWEVER, in 2012, if you shut down host WITHOUT maintenance mode, there is a disruption of service as VMs go into a saved state, are moved, then started. While they are in a saved state, they are non-functional.
      3. In R2, even if you shut down (without maintenance mode) they move to another host AUTOMATICALLY. This is new in R2
    2. Dynamic Quorum / Dynamic Witness
      1. DQ – 2012 and 2012 R2 automatically recalculate quorum if a node is shut down gracefully.
      2. if multiple nodes fail, 1) checks if it has a quorum then 2) recalculates quorum
      3. you can also configure certain nodes to be NON voting node.
      4. Dynamic Witness
        1. configure a witness that will or will not be used based on quorum
        2. if there is an odd number, then dynamic witness doesn’t vote
        3. if there is an even number, then dynamic witness will be active
        4. PURPOSE is to reduce the chance of cluster failure if a witness goes down.
        5. basically insures an odd number of votes
      5. Force Quorum Resiliency
        1. to avoid “split brain” or “partitioned cluster”; nodes are not aware of each other, most often due to network issue. Generally resolved by restarting cluster. Essentially, each set of nodes think they have quorum. Think nodes in two separate datacenters (Sydney and Melbourne)
        2. Force Quorum Resiliency is that when network is restored, the cluster quorum is restored automatically.
      6. Tiebreaker 50-50 Node Split
        1. clusters dynamically adjust a nodes vote (deprecated vote) to ensure odd number.
        2. you have to configure it.
        3. works WITH dynamic witness
        4. works if dynamic witness fails
        5. in multi site clusters, admin can set which site retains quorum
  5. Enhanced Session Mode and Improved VM Export
    1. Virtual Machine Connection via Hyper V Console
      1. doesn’t allow cut/paste, scripting, redirect sound, basically only KB and mouse
      2. if you want those features, you usually have to use RDP
      3. Requirements
        1. host on 2012 R2
        2. VMs running R2 or Windows 8.1
        3. Enabled in Hyper V settings on host
        4. account is a member of RDP users or Admins on VM
        5. (do not have to log into VM and enable RDP
    2. DEMO of Enhanced Session Mode2012EnhancedSessionMode
      1. allows to set resolution
      2. allows redirect audio
      3. allows record remote audio
      4. redirect printers
      5. redirect clipboard (like RDP)
      6. click “More” to get to map drives, PnP, etc.
      7. Essentially this is like the same thing in RDP but appears pretty robust and solid.
    3. Virtual Machine Export IMPROVEMENTS
      1. 2012 or prior, had to shut down machine.
      2. R2 lets you export RUNNING machine.
      3. the exported machine, when you import it, it will be running as well (with certain requirements)
      4. Example; testing; you want to copy a bunch of machines to test a software install.
    4. DEMO of Virtual Machine Live Export
      1. create checkpoint (snapshot)
      2. can export checkpoint or live machine
      3. if you do the live machine, it creates temporary checkpoint, then a live update at the last instant to finalize
      4. WILL create a new vm id upon import, if you want. there are three choices; 1) Register in place (use existing unique ID), 2) restore the virtual machine (use existing unique ID), and 3) copy the virtual machine (create a new unique ID). Explanations of these three options here.
      5. Also note the VM unique ID, is a unique Hyper-V GUID, but this is NOT the same as a SID. A SID is used for Active Directory, this is simply for Hyper-V see explanation here.
      6. CAN do multiple imports, like a template. That would usually be option # 3 above.
  6. Generation 2 Virtual Machines – NEW in R2
    1. Gen 1 machines WILL run in 2012 R2 no problem.
    2. Gen 1 machines emulate older hardware, which creates performance impact
      1. lots of P2V, but now we do a lot of straight to VM
    3. Gen 2
      1. supports secure VM boot
      2. don’t need to run on particular older hypervisor
      3. don’t need to support Remote FX
      4. boot volumes bigger than 2.2 Tb (developers will love this; we want all the storage you have….)
      5. there is a new step in VM creation wizard; 1 or 2.  Default is still Gen1 (see screenshot)
      6. Can’t really change this later. There is an unsupported script on MSDN and perhaps other places example here.
    4. DEMO of Generation 2 VM on Server 2012 R22012Gen2MachineDefaultGen1
      1. It states in the wizard that this cannot be changed, see the warning at the bottom.
      2. next few steps are the same as you’re familiar with.
      3. Gen2 only support new .vhdx format.
      4. Another new feature; no default virtual DVD! This is ONLY created if you specify install by .iso. (see screenshot)

        If you don't select the .iso, there will be NO default DVD drive created.

        If you don’t select the .iso, there will be NO default DVD drive created.

    5. Generation 2 Boot Order
      1. for booting to .ISO etc.Just like changing boot order in BIOS more less.
      2. Enable secure boot (default is ENABLED)
      3. only supported by Windows OS
      4. VM has to be turned off to change setting.
      5. currently (as of this training)
    6. DEMO of Gen2 Boot Order
      1. contained in VM “settings/firmware”
    7. NO IDE controller. (older versions HAD to boot off IDE
      1. Gen2 ONLY boot from SCSI
      2. allows hot add storage, or expand storage while running (R2)
    8. DEMO of hot add storage and expand
      1. we went over this in the prior post VNEXT First Look
    9. Drawbacks to Gen2
      1. no remote FX (so be aware if you are a VDI shop)
      2. no .vhd support for OS drive.
      3. no linux support
      4. no iSCSI reboot
      5. cannot replicate to Azure
  7. SMB and DFS Improvements
    1. manage bandwidth based on traffic type; default/Live Migration/Virtual Machine Traffic
    2. by default, no limits
    3. Bandwidth Limit is a FEATURE, only enabled/configured by POWERSHELL (no GUI install). Installed from Server Manager, enabled by PS
    4. SMB manage bandwidth Managed by Powershell, see here.
    5. Clone of the DFS database; Use Case; setting it up in a branch office without WAN replication to get initial replication set up.
    6. Preserved File Restoration
      1. ConflictAndDeleted and PreExisting can be managed by Powershell;
        1. Get-DfsrPreservedFiles and Restore-DfsrPeservedFiles
        2. can choose to overwrite, or copy to new location
      2. This is a Server 2012 R2 capability.
    7. DEMO DFS Export
      1. Get-DfsrCloneState
  8. Remote Desktop Services Improvements
    1. Session shadowing, Dynamic Display, RestrictedAdmin Mode, Online Data Deduplication
    2. Session shadowing allows admin to connect to Server 2012 R2 session and view mode, or “control mode” so you can interact and control just like the user.
      1. Can be configured to “require permission”
    3. DEMO of session shadowing.
      1. similar to what a lot of third party tools have been able to do; Citrix, Webex, LogMeIn123, VNC,  etc.
    4. Dynamic Display – supports “device rotation” for landscape mode for tablets etc. Multiple monitors, projectors, etc. Supports touch devices.
    5. RemoteFX virtualized GPU support DX 11.1
    6. compression bandwidth compression – claims of 50% less bandwidth when playing video across Server 2012 R2 RDS WAN link.
    7. RestrictedAdmin mode
      1. allows interactive logon without sending credentials
      2. only Windows 8.1
      3. requires /restrictedadmin mode in MSTSC command
      4. more info on RestrictedAdmin mode here.
    8. Online Data Deduplication
      1. deduplicates VHD while running
      2. requires Server 2012 R2 with Feature enabled
      3. when deployed on tiered storage, deduped data moved to higher tier
  9. Windows Server 2012 R2 WDS Improvements
    1. WDS with Powershell and VHDX deployment
    2. lots of new powershell to automate. System Center Orchestrator can call these cmdlets.
      1. New Powershell cmdlets;
        1. New-WdsInstallImageGroup
        2. Import-WdsBootImage
        3. Import-WdsInstallImage
        4. Import-WdsDriverPackage
    3. DEMO of Powershell cmdlets via ISE
    4. VHDX files Import and Deployment
      1. now can use a GUI to manage.
      2. create in Hyper V, sysprep, then shut down.
      3. no need to capture
      4. import the .vhdx into WDS
      5. make reference machine smaller than 120 Gb or WDS will error thinking it’s larger than the default 120 Gb drive
    5. DEMO
      1. demo of sysprep, shut down, etc.
      2. Import to WDS
  10. DHCP and DNS Improvements
    1. Implementing DNSSEC, Zone Level Statistics, and DHCP Registration Options
    2. DNSSEC allows records to be digitally signed so clients can verify authenticity
    3. most Server 2012 R2 improvements related to replication
    4. When DNSSEC is enabled, each record gets a matching RRSIG (Record Resource SIGnature) record, and a DNSKEY record and a NSEC/NSEC3. More on DNSSEC here.
    5. DNSSEC keys
      1. trust anchor
      2. KSK Key Signing Key
        1. first server with DNSSEC has the KSK
      3. Zone Signing Key
      4. NRPT can be configured after DNSSEC is confitured.
        1. configured with Group Policy
        2. allows you to configure IPSEC
    6. DEMO of DNSSEC
    7. Zone Level Statistics (improved)
      1. query, transfer, updates
    8. Demo of Zone Level Statistics
      1. Get-DnsServerStatistics
    9. DHCP registration and Name Protection
      1. DEMO of DHCP registration and Name Protection
      2. site or server level
      3. “enable name protection” checkbox. Does not allow duplicate named hosts.
  11. Upgrading to Windows Server 2012
    1. upgrading domain controllers, migrating DHCP servers, migrating file servers
      1. DC not a true upgrade, can’t do x86 to x64 version
      2. only some OS can do an OS upgrade
      3. Recommendation is to introduce a Server 2012 R2 DC to your 2003 functional level domain
      4. promote Server 2012 R2 to DC
      5. transfer FISMO roles to Server 2012 R2 DC
      6. then demote the old DCs (dcpromo)
    2. DEMO of upgrading the DCs
      1. netdom query FISMO  (shows FISMO roles)
    3. Migrating DHCP
      1. back it up using DHCP concsole
      2. install ROLE on Server 2012 R2
      3. then restore the backup
        1. netsh to back up DHCP
        2. 2003 netsh DHCP server export c:\somefilename.txt all (exports the file)
        3. 2003 netsh DHCP server import c:\somefilename.txt all (imports to Server 2012 R2 server)
        4. 2008 use the Server Manager
    4. DEMO of transferring DHCP
    5. Migrating File Server
      1. biggest issues are permissions, share permissions, and quotas
      2. install migration tools Feature on Server 2012 R2
      3. creates a package to install on source machine
      4. basic steps are;
        1. INSTALL migration tools on Server 2012 R2 target machine
        2. CREATE package for donor/source machine
        3. INSTALL migration tools from package to donor/source machine
        4. START Receive-SmigServerData on target/destination
        5. START Send-SmigServerData on donor/source
        6. More on SmigServerData here.
    6. DEMO of moving file server role
      1. install Feature from server manager or PS
        1. DO NEED .net framework 4
        2. create package (just a folder of a bunch of files)
        3. run smigdeploy to start it on the donor/source

This concludes the Pluralsight Windows Server 2012 R2 New Features Course

Thanks to Orin Thomas;

http://www.pluralsight.com/author/orin-thomas

http://orinthomas.com/

@orinthomas

Jun 11

Windows Server vNext First Look

This is one of the FREE Pluralsight training classes.
Windows Server vNext First Look

UPDATE; I got some questions about VNEXT. I have not finished this Study Guide as I need to focus on my upcoming test. However, I did find a couple of additional posts on other sites that are helpful;

  1. 1) http://windowsitpro.com/windows-server/windows-server-vnext-giant-leap-rather-small-step
  2. 2) Tech Days Keynote by Jeffrey Snover and Rick Claus
  3. 3) there is a whole series of videos on MSDN CHANNEL 9
    1. There are two many to list right now but go to this URL; http://channel9.msdn.com/Events/Ignite/2015/
    2. Then, add search criteria on the right; 1) add “vnext” or “nano” to the search box (one at a time)
    3. AND also down the list a bit select “level 300” and you should be getting a list of vNEXT and NANO videos from Ignite.

My notes (did not complete this, had to focus back on 2012 R2 for upcoming tests)

  • The next (unamed OS). This is a PREView, not even to Beta yet.
  • Some features are not even in the preview
  • RTM sometime 2015
  • Hyper-V
    • can rolling upgrade from 2012 R2 to vNEXT AND BACK
    • so you can move a VM from one to another
    • once all nodes are vNext, then you can upgrade cluster, and after that all VMs are version 6 instead of 2012R2 v5
    • VM configuration file improvements. Less editable, more resilient. Binary, not XML
      • .VMCX and .VMRS files
    • Production checkpoints (snapshots in 2012r2) weren’t really supported. Now are fully supported in all production workloads.
    • Still can do standard checkpoints, or production checkpoints
    • Linux Secure Boot;
      • Generation2 Linux VM
      • protects boot environment from malware
      • have to use MS UEFI certificate authority
    • Hot Add Memory and Hot Add NICs
      • increase, decrease even with static settings, Gen 1, Gen2
      • NICs, only Gen 2
    • Hyper-V Manager
      • information about versions and memory utilization
      • can use alternate credentials
      • downlevel server management; 2012 R2, Windows 8, different versions.
      • additional features; integration services through windows updates, connected standby, add storage to VMs that are set to replicate (prior had to recreate)
    • Demo
      • hyper-v console
      • hot add memory (VMware could do for years)
      • hot add NIC (VMware could do for years)
    • What’s new in Remote Desktop Services
      • Remote FX improvements (Remote FX simulates a powerful graphics adapter, in VDI environments or Remote Desktop)

 

Jun 05

Links from HP Discover 2015

Water cooled server racks; APOLLO; http://www8.hp.com/us/en/products/servers/high-performance-computing/apollo/apollo8000-product-portfolio.html

Video explanation of the APOLLO water cooled system; this is the Peregrine system they talked about that is being used to heat the sidewalks with excess heat from the datacenter; https://youtu.be/9Ih3R84Corg

The MACHINE; the HP Labs folks running this section were real genius types;  http://www.hpl.hp.com/research/systems-research/themachine/

MEMRISTOR; http://www8.hp.com/hpnext/tags/memristor#.VXGmJc9VhBc

StoreVirtual VSA; virtual array storage and servers in single appliance; http://www8.hp.com/us/en/products/data-storage/storevirtual-vsa.html

VPV; http://www8.hp.com/us/en/software-solutions/vpv-server-virtualization-management/

SiteScope; http://www8.hp.com/us/en/software-solutions/sitescope-application-monitoring/

Operations Manager; http://www8.hp.com/us/en/software-solutions/operations-manager-infrastructure-monitoring/

 

HP Moonshot; lots of buzz, very flexible, and very dense; http://www8.hp.com/us/en/products/servers/moonshot/#products

HP Vertica; SQL on Hadoop; http://www.vertica.com/hp-vertica-products/sqlonhadoop/

Hadoop with Cloudera or Hortonworks; http://www8.hp.com/us/en/products/servers/high-performance-computing/hadoop.html

Helion; huge buzz about Helion the Cloud Infrastructure / Openstack offering; http://www8.hp.com/us/en/cloud/hphelion-openstack-overview.htmlhttps://docs.hpcloud.com/helion/openstack/1.1/. Supports Chef, Puppet, etc., etc., etc.

Internet Giants; this was running, just kind of interesting; http://pennystocks.la/battle-of-internet-giants/