Is System Center Operations Manager still relevant in the Cloud?

EXCLUSIVE Whitepaper: Is OpsMgr still relevant in the Cloud by MVP Cameron Fuller

ImageProxy

The addition of the Cloud has truly changed how we monitor in Microsoft solutions. In this whitepaper, Microsoft MVP Cameron Fuller tackles the elephant in the room and answers the question of the relevance of Operations Manager. Find out whether Operations Manager is still relevant in the world of the Cloud

Installing Hyper-V role on Windows 2016 Server TP2 MinShell version

As you probably are aware of, Windows 2016 Server TP2, comes with 2 installation options. You also probably have noticed as well that the graphical user interface (GUI) is no longer an option in a default install on the Technical Preview 2.NOt even Start Menu.
install-1

  • Windows Server Technical Preview 2 option, will install the server with MinShell (Minimal Shell no GUI). Assuming that you will manage the host remotely you won’t need graphical interface at all and from a security point of view, it is the better option.

install-4

  • Windows Server Technical Preview 2 (with local admin tools) option, will install the server again with MinShell, but includes Server Manager and the other GUI administration tools, although no desktop experience (traditional desktop), nor start menu.

install-3

To install Hyper-V role in the Windows Server Technical Preview 2 (with local admin tools) option, in the Server Manager console, click on Add roles and features and select Hyper-V.

To install Hyper-V role in the Windows Server Technical Preview 2 option :

in the command prompt, type:

PowerShell

PS: > InstallWindowsFeature Hyper-V

Note: If the installation fails due to “The source files could not be found” error, assuming the Windows Server Technical Preview 2 ISO image connected to the DVD drive (D:), type:

PS: > InstallWindowsFeature Hyper-VRestart Source wim:D:\sources\install.wim:4

install-2

Simple as that!

Solved: Wireless not connecting after installing Windows Server TP2

Issue:

Wireless network does not connect on Windows Server TP2 after enabling Wireless Services and installing Wireless Drivers

Solution:

Add the Native WiFi Filter SERVICE in the properties of the wireless adapter

To be more specific:

  1. In the Network and Sharing Center, click on Change Adapter Settings and then on the network connections, select the Wireless Network, right click and select Properties.

1
2. In the Properties on the Wireless Adapter, click on Install
2
3. Select Service and click on Add
3
4. Select Native WiFi Filter and click on OK 4
5. Done. You will be able to connect to a WiFi connection now.

Make your voice heard and improve Windows Server 2016

The public download for Windows Server 2016 Technical Preview 2 (TP2) is here: http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview

win2016

 Now it is your time to give your feedback to the Microsoft Product team and help them improve Windows Server 2016

What’s new in Windows Server 2016 Technical Preview 2: (Please note that this is pre-released software; features and functionality may differ in the final release, that’s why YOUR FEEDBACK IS VERY IMPORTANT)

Compute and Virtualization: Simplified upgrades, new installment options, and increased resilience, helping you ensure the stability of the infrastructure without limiting agility.

Networking: Continued investment to make networking as flexible and cost-effective as possible while ensuring high performance.

Storage: Expanding capabilities in software-defined storage with an emphasis on resilience, reduced cost, and increased control.

Security and Assurance: Protecting against today’s threats with a “zero-trust” approach to security that is rooted in the hardware.

Management: Ongoing advances to simplify server management and increase consistency in approach.

  1. PowerShell Desired State Configuration (DSC) for easier, consistent and faster deployment and updates.
  2. PowerShell Package Manager  for unified package management and deployment
  3. Windows Management Framework 5.0 April Preview and DSC Resource Kit  (available online simultaneously with TP2)

VMM 2012 R2: Unified (almost) on premise and Azure management through the VMM console

Although it is only simple actions (i.e such as restart, refresh, and view) you can use Virtual machine Manager 2012R2 to manage both on premises and Azure Virtual Machines, by adding Azure subscription to VMM.

Let’s hope the VMM team extend those tasks beyond that.

To Download: KB3050317Update Rollup 6 for System Center 2012 R2 Virtual Machine Manager (https://support.microsoft.com/en-us/kb/3050317/)

 

for more information on new features on VMM 2012 R2 UR6 check http://blogs.technet.com/b/scvmm/archive/2015/04/29/an-overview-of-the-new-features-in-vmm-2012-r2-update-rollup-6.aspx

Unified management through the VMM console

With VMM 2012 R2 UR6, Virtual Machine Manager offers a very simple way for a VMM Fabric administrator to add a Microsoft Azure subscription to VMM. After users have added the Microsoft Azure subscription to VMM, they can get a view of their Azure instances directly from the VMM console, and they can perform some simple actions on these instances.

Although in the long term Microsoft vision is to establish WAP as the console of choice for on-premises and Azure workload management, we still see this feature as a value-add to a large set of users who don’t yet use WAP or who don’t want to incur the overhead of WAP. This option of performing simple VM management tasks such as restart, refresh, and view on Azure VMs through VMM consoles gives Fabric administrators the flexibility to manage both on-premises and Azure public cloud VMs from within a single VMM management console

 

Virtual Machine Manager 2012R2 UR6 : pack more VMs per replica, beyond 100% capacity

With Update Rollup 6 for System Center 2012 R2 Virtual Machine Manager, you can now overcommit clouds and host groups in your VMM environment.

This brings significant savings for the cloud and host group resources and helps you manage your datacenter in a more economical way.

After applying Update Rollup 6, to enable overcommit of replica VMs to a cloud or host group you simply need to configure the following registry key on the VMM Server:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Placement

Name: IgnoreMemoryForStoppedReplicaVM

Type: DWORD

Value: 1

Note: If the Placement key doesn’t exist you will need to create it.

Later, if you need to disable overcommit simply change the Registry Value for IgnoreMemoryForStoppedReplicaVM to 0

VMM Replica Overcommit

 

You can read more here: http://blogs.technet.com/b/scvmm/archive/2015/04/29/vmm-2012-r2-ur6-now-offers-the-option-to-overcommit-cloud-and-host-group-capacity-for-replica-vms.aspx

 

Categories: Cloud

Hyper-V quick Survey. Give your feedback to the hyper-v team

The Hyper-V team is conducting a survey and they want to hear from you!

https://www.instant.ly/s/G5bPn?s=bb

In this survey they:

  • Ask for some basic information about how you are using virtualization
  • Ask for feedback on Hyper-V in Windows Server 2012 R2
  • Give you the option to participate in future Hyper-V surveys
Categories: Cloud Tags: , , ,
Follow

Get every new post delivered to your Inbox.

Join 1,137 other followers