Cloud and Datacenter Management Blog

Microsoft Hybrid Cloud blogsite about Management


Leave a comment

Hybrid IT Connect computers and devices to #MSOMS using the OMS Gateway #Winserv #Linux

oms-agents

Instead of each individual agent sending data directly to OMS and requiring a direct Internet connection, all agent data is instead sent through a single computer that has an Internet connection. That computer is where you install and use the gateway. In this scenario, you can install agents on any computers where you want to collect data. The gateway then transfers data from the agents to OMS directly.

Here you can start with downloading the software for Microsoft OMS Gateway

oms-gateway-installer

oms-gateway-install-1

oms-gateway-install-2

oms-gateway-install-3

I used the default port 8080 for the Gateway.

oms-gateway-install-4

oms-gateway-install-5

oms-gateway-install-6

Now the Microsoft OMS Gateway Services is installedoms-gateway-running

Now Microsoft Operations Management Suite Gateway is installed, you can use some Microsoft Powershell Commands :

oms-gateway-powershell-1

oms-gateway-powershell-3

After the installation of the OMS Gateway, I installed the OMS Agent :

oms-connection

Download your OMS Agent here

oms-agent-1

oms-agent-2

oms-agent-3

oms-agent-4

oms-agent-5

Copy => Paste your OMS Workspace ID and Key.

oms-agent-6a

oms-agent-7

oms-agent-8

oms-agent-control

Here you can see the OMS Agent Connection settings.

oms-agent-9

When you wait for a few minutes you will see the connection in the Portal of OMS.

oms-connection

After this I installed the OMS Agent on One of my Domain Controllers with OMS Gateway settings //HyperV2016.hybridcloud4you.nl:8080.

This is what you will see in the Event Viewer of the OMS Gateway Server :

oms-gateway-events-next

Domain Controller 192.168.2.100 is going via the OMS Gateway

oms-agents-in-the-portal

OMS Agent via the Microsoft OMS Gateway

oms-portal

From here you can start with your OMS Solutions 😉

It is also possible to connect your System Center Operations Manager (SCOM) on-premises to the OMS Gateway.
Then you don’t have to connect your SCOM Management Server directly to the internet to OMS.

scom-oms-gateway

SCUG Banner


Leave a comment

How to recover a gateway that was deployed through VMM and is running Windows Server 2012 R2 #SCVMM #Winserv #sysctr #HybridCloud

SCVMM Gateway

This article contains information about gateways that are running Windows Server 2012 R2 and were deployed through Virtual Machine Manager (VMM). The VMM server must be running Microsoft System Center 2012 R2.

Here you find all the information you need about Windows Server 2012 R2 Gateway and how to recover


2 Comments

Making a NVGRE Gateway with System Center 2012 R2 Virtual Machine Manager #SCVMM #sysctr

We made in our TestLAB ICTCUMULUS (Means CLOUDS) a NVGRE (Network Virtualization using Generic Routing Encapsulation) Gateway with System Center 2012 R2 Virtual Machine Manager.

Before you make the Microsoft NVGRE Gateway see these blogposts here :

From Microsoft Private #Cloud to Hybrid Cloud Services Part 2 of 5 #SCVMM 2012 R2

NVGRE 1

NVGRE 2

NVGRE 3

NVGRE 4

NVGRE 5

NVGRE 6

NVGRE 7

NVGRE 8

NVGRE 9

The Microsoft Windows Server Gateway is active.

NVGRE 10Here we set the right settings for Front and backend Connection.

NVGRE 11

Now we create VM Network with isolation called Tenant Blue.

NVGRE 12

NVGRE 13

NVGRE 14

NVGRE 15

NVGRE 16

NVGRE 17

NVGRE 18

NVGRE 19

We create an IP Pool for the Blue Tenant network.

NVGRE 20

NVGRE 20 NVGRE 21

NVGRE 22

NVGRE 23

We now create a Hyper-V Port Profile for the VM’s in Tenant Blue

NVGRE 24

NVGRE 25

NVGRE 26

NVGRE 27

NVGRE 28

NVGRE 29

Now we deploy a Virtual Machine

NVGRE 30

NVGRE 31

NVGRE 32

NVGRE 33

NVGRE 34

NVGRE 35

We Create a Virtual Machine in the isolated Blue Tenant.

NVGRE 36

NVGRE 37

VM is automatically configured with an IP-adress from the IP-Pool (192.168.99.2):

NVGRE 38

VM communicates via the NVGRE (via NAT) with the internet:

NVGRE 39

Our virtualization gateway host is using a Provider Address (192.168.98.2) used for network virtualization:

NVGRE 40

We created two more VM in the blue tenant to see some more results in the next step:

NVGRE 41

We can see our three created VMs with Customer address mapped to Provider Address if we run the powershell command Get-NetVirtualizationLookupRecord on the gateway host (ras01):

NVGRE 42