Archive for the ‘Azure’ Tag

OMS Network Performance Monitor #MSOMS #NPM #Azure   Leave a comment

When Using OMS you can benefit of the Network Performance Monitor (NPM), that helps you perform near real-time monitoring of network performance parameters (such as packet loss and network latency) and localize network faults. It not only detects network performance issues, but it also localizes the source of the problem to a particular network segment or device to make it easy for you to locate and fix a network performance issue.

OMS Network Performance Monitor (NPM)

You can detect network issues with the solution dashboard which displays summarized information about your network including recent network health events, unhealthy network links, and subnetwork links that are facing high packet loss and latency. You can drill-down into a network link to view the current health status of subnetwork links as well as node-to-node links.

So what to do to get the full benefit of the NPM.

Deploying NPM involves four basic steps.
1. Enabling the solution on your OMS workspace
2. Installing the OMS agents
3. Configuring the OMS agents
4. Configuring the solution.

Diagram that shows how the solution works.

I Assume you already have the OMS Agent in place and connected and reporting to OMS,if not below are two screens on how to enable the NPM and installing the Agent. And a lot of cool new features are there.

imageimage

Installing the OMS agent Windows Or Linux.

 

OMS Network Performance Monitor (NPM)

Firewall ports are required to be opened on the servers so that the agents can connect to each other.

Run the script without any parameters in a power shell window with administrative privileges. This script creates few registry keys required by NPM and creates windows firewall rules to allow agents to create TCP connections with each other

The port opened by default would be 8084. You have the option of using a custom port by providing the parameter ‘portNumber’ to the script. However, the same port should be used on all the machines where the script is executed.

Note that the script will configure only windows firewall locally. If you have a network firewall you should make sure that it is allowing traffic destined for the TCP port being used by NPM

OMS Network Performance Monitor Agent Configuration Script

OMS Network Performance Monitor (NPM)

Now that the solution is enabled we can configure some networks. All the networks are discovered by the Agent and it will turn-up automatically.

 OMS Network Performance Monitor (NPM)

You can Add a new network ( read this as a Name ) as we give the IP subnet a name and link the subnet to the network

image

Give the network a name and link the subnet to It

image

And don’t forget to save the network. now that the networks have names it is easier to understand the networks.

When looking at the nodes you can easily see what networks the machine is using

image

The monitoring of the networks

image

If you don’t want to monitor Certain networks you can disable the monitoring of this network.

 

Set monitoring rules

Network Performance Monitor generates health events about the connectivity between a pair of nodes or subnetwork or network links when a threshold is breached. These thresholds can be learned automatically by the system or you can configure them custom alert rules.

The Default rule is created by the system and it creates a health event whenever loss or latency between any pair of networks or subnetwork links breaches the system-learned threshold. You can choose to disable the default rule and create custom monitoring rules

OMS Network Performance Monitor (NPM)

In the monitoring rules you can create a special rule set say for the SQL server , Webservers or DMZ / ISCSI networks with each a set of his own rules.

With all this in place and when things are running you may need to tweak the thresholds a bit.

image

There a great in depth overviews and you can adjust them to drip down.

image

Normally this is not the best view for a network but this is a test lab and machines are not always running.

Topology Dashboard

If you click the View topology map link, you will see the hop-by-hop topology of the routes between the source and destination nodes. The unhealthy routes or hops will be colored in red, which will help you to quickly localize the problem to a particular section of the network.

 

image

And if you want to get more detail about your network drill down and adjust the time setting from 7 days to 6 hours

image

to get a Daily overview with OMS Network Performance Monitor with the data based on 6 hours

image

Get a good view of the latency of your network between servers/ HOP’s

Log Analytics search

All data that is exposed graphically through the Network Performance Monitor dashboard and drill-down pages is also available natively in Log Analytics search. You can query the data using the search query language and create custom reports by exporting the data to Excel or PowerBI. The Common Queries blade in the dashboard has some useful queries that you can use as the starting point for creating your own queries and reports.

More and more new OMS features are coming so I guess the data Size is still Growing

 

image

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

Posted August 26, 2016 by Robert Smit [MVP] in Azure, MSOMS

Tagged with , ,

Azure Server management tools Manage your servers from anywhere #servermgmt #Azure #SMT   Leave a comment

Server management tools is an Azure service that offers a set of web-based GUI and command line tools to manage Windows Servers. This is especially useful when managing headless servers such as Nano Server and Server Core. These tools also provide rapid access to your on-premises infrastructure in a common dashboard alongside your Azure resources, thereby providing a consistent management experience across your infrastructure. Server management tools supports a set of basic server diagnostic tools.  The Tools are working on Windows Server 2012,Windows Server 2012R2,Windows Server 2016 and Nano Server

Server management tools requires a gateway which can be configured on any server in your environment. The gateway enables communication between the Microsoft Azure portal and your Windows Server machines, whether on-premises in your infrastructure, or hosted in a cloud provider.

A while a go I already created a blog post on this but as there are so many new features a fresh post is in place.

https://robertsmit.wordpress.com/2016/02/12/azure-server-management-tools-offers-a-set-of-web-gui-tools-to-manage-azurestack-servers-rsmt-asmt/

Even now that my wish on the Uservoice is added to the Service Management Tools #SMT the tools are getting better all the time.

How are things working below is a schematic overview.

server management tools

 

A Server management tools gateway is required to enable communication between the Microsoft Azure portal and your Windows Server 2016 machines. A gateway is typically deployed and configured on the same local network as the Windows Server machine(s) you wish to manage. The machine must have an internet connection.

Building the Connection go to Azure and look for Server Management Tools

server management tools

check the Server Management tools and a new right screen will open

server management tools

Just check Create.

imageserver management tools

A common mistake is give the computer name and the gateway the same name. but this will Fail!!

Important Item In the Computer name and the Gateway name can’t be the same name It can but you will not be able to manage this server remotely.

image

provide the NAME/IP/FQDN of the machine you want to connect to ( so not the GATEWAY SERVER )

If this is the first Server management tools connection you are creating, you will also need to choose to create a new Server management tools gateway and give it a name. You will be prompted to complete the gateway configuration after the Server management tools connection is created.

 

Configuring a new Server management tools Gateway

image

When creating the gateway you need to do little configuration on the Gateway server local

server management tools

I choose for automatic updates and you will need to generate a link with the gateway package

 

image

check the generate a package link and use this link to install the gateway

https://pdrsmtrppreviewneu.blob.core.windows.net/ce12af764058e42b8a603d3c2c77f1915/gateway.

image

 

  1. Use the generated link to download the gateway deployment package now, or copy the link URL to download the package later from the machine on which you intend to install the package.

  2. From the machine that you want to designate as the gateway, unzip the package and run GatewayService.MSI.

  3. Once the gateway installation completes, return to the Microsoft Azure portal and reopen your Server management tools connection.

  4. You should now be able to manage your Windows Server 2016 machine if the Microsoft Azure portal can reach it through the gateway.

server management tools

server management toolsserver management tools

now that the Gateway is installed you should see a OK status in the Azure console if not you need to do some extra settings.

After OK status

image

In case the Ok is not showing check your Firewall or past the rule below in the Firewall

NETSH advfirewall firewall add rule name="WinRM 5985" protocol=TCP dir=in localport=5985 action=allow

If you wish to connect using the local Administrator account, you will need to enable this policy on the target machine by running the following command in an administrator session on the target machine:

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1

And if the WinRM settings are not in place you will need to set the correct winrm settings as well,

winrm set winrm/config/client @{ TrustedHosts="10.255.255.59" }

Change the IP with your own server when you set this on the manage server the trusted host must be the gateway server.

Now that the Service Management Tools Gateway is in place and working the Service Management Tools Connections needs configuration and this is where all the magic happens.

server management tools

when opening the Service Management Tools Connections you will need to set the administrator credentials else you can’t connect and do stuff on your server.

 

image

You can save the Credentials or Fill the in every time you need the Service Management Tools Connections for you server. A new feature is Persist credentials

The ability to save the credentials used to manage the target machines. From the credential entry dialog, you can opt to store credentials securely. The credentials are first encrypted using standard AES 256 encryption and then securely stored within Azure. These credentials can only be decrypted using the certificate which is stored in the Server management tools gateway. When you go to manage an instance, the encrypted credentials are passed down to the Server management tools gateway for decryption, and are then used to process all management requests on the target machine. Even though the credentials are securely stored in Azure, the on-premises certificate provides an additional level of security because only your gateway can decrypt the stored credentials since only your gateway has the certificate used to encrypt them. The certificate used to encrypt the credentials is never passed to Azure and the Azure service will never have access to unencrypted user credentials.

 

image

A brief overview of the server you can customize the view but the more you put in the overview the slower the content is showing in the browser. Unless you need it.

A long list of options and server management tools are there and the list is getting longer, File Explorer,Firewall rules and PowerShell script saving and Certificate manager are all new to the Service Management Tools Connections.

image

 

PowerShell script editor enhancements

The script editor is now equipped with basic file browsing capabilities. You can browse through the files on the target machine and open an existing script. You can create a new script or modify an existing one and save it on the target machine.

Script editor is now also integrated with your Azure Blob storage. You can save your scripts in your blob and make them available across all your servers and to other members of the subscription.

image

image

As the script editor can save the scripts or open the scripts from a blob account so you don’t need to type everything for each server

imageimage

the one thing is missing here is creating a Storage Account. this would be handy if you could create one here.

 

image

On the Storage account you can create a container for you files or if you already have one place the files in this container.

imageimageimage

But when you don’t want to place the files in Azure and leaf them on your server this is also an option.

image image

the File Explorer is a great option to look and use files on the Server and when you look at the storage you will see all the drives and what a great feature it shows even unhealthy drives.

The Certificate manager is also new to the server management tools

It brings the much needed ability to remotely manage certificates on targeted computers. With capabilities such as viewing all or a specific set of certificates, along with relevant event log channels, it helps you to find the root cause of certificate related issues. You can also import, export and delete certificates.

As you can see I  play a lot with the Certificates on the Hyper-V server guess it is time to do some certificate cleaning.

image

 

 

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

Posted August 25, 2016 by Robert Smit [MVP] in Azure

Tagged with

System Center 2016 VMM Place template VM in Custom OU #sysctr #Cloud #Deploy #VM   2 comments

when using VMM and deploying templates you not always want to place them in the default OU computers

image

But instead you want the Template Server 2016 places in OU TP5 and Hyper-V server directly placed in the OU Hyper-v.

Default there is no Gui item in the VMM console to do this. Say on the domain join tab place this VM in the Hyper-V OU

 image

Instead of this you need to fill in the Value in Powershell. and Make a custom OU field.

image

You can Add Custom Properties as you like.

But first we are creating a Custom Guest OS profile this profile is the basis for the new build template and the Custom OU Placement.

image

Now that the Custom OS profile is in place we can check it there is a domain OU field

Get-SCGuestOSProfile

image

this shows us the field that we must fill in to get the right OU placement.

Get-SCGuestOSProfile |select Name

image

Get-SCGuestOSProfile -name "Guest OS 2016TP5"

Setting this in the OS profile

Get-SCGuestOSProfile -name "Guest OS 2016TP5" |Set-SCGuestOSProfile -DomainJoinOrganizationalUnit "OU=SCVMM16,DC=MVP,DC=local"

image

Now when I create a new template with this OS profile the VM is place in the SCVMM16 OU but it is not anywhere visible in the GUI.

and what if I have already build templates how to place them in Custom OU.

Yes you can do this. First I select all the templates to pick the right one

Get-SCVMTemplate |select name

image

 

$template = Get-SCVMTemplate | where {$_.Name -eq "ws2016G2"}
$template |select name

image

As I made the OU a variable :

$ou = "OU=SCVMM16,DC=MVP,DC=local"

Set-SCVMTemplate -VMTemplate $template -DomainJoinOrganizationalUnit $ou

 

image

So now the Template has a custom OU also.

But still there is no GUI property to show this. therefore go to the Template and create a Custom Property

image

go to the Manage custom Properties

image

Select Virtual Machine Template Properties give it a name “ custom OU “ and assign this to the template

image

Now that tis is assigned we can enable this in the GUI

imageimage

But before we get any value in this field we need match this with the PowerShell Value DomainJoinOrganizationalUnit

 

Get-SCVMTemplate | %{ Set-SCCustomPropertyValue -InputObject $_ -CustomProperty $(Get-SCCustomProperty -Name "Custom OU") -Value $_.DomainJoinOrganizationalUnit }

 

image

As you can see there is an error this is because one template has no value.

image image

 

Now With new deployments the VM’s will be places in the Custom OU

image

 

 

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

System Center 2016 VMM Current Updates installation | Cumulative Update 1 & 2   Leave a comment

When testing with Windows Server 2016 and system Center 2016 you need to install the CU1 and CU2 update to get the best results. there are several fixes in these updates.

 

 

 

Issue 1: As a Delegated Administrator (DA), when you try to configure the load balancer on the Network Controller Service, the service crashes with a NULL pointer exception.

Issue 2: When you try to configure VPN connections that are running on a Network Controller-managed gateway, VMM does not display the VPNServerAddress object on the VMM Console.

Issue 6: Creating Shielded VMs on Guarded Hosts on an untrusted network or on a perimeter network fails.

To get more info on all the fixes and solutions and read the KB you may need to change something in the Database! So no hit and run on the System Center  cumulative Updates. 

image

As you can see only 86 days left on this evaluation.

image

After the updates make sure the Hyper-v servers have the latest Agent version!

 

How to obtain and install CU1 for System Center 2016 VMM Technical Preview 5

Download information

Update packages for VMM are available by manual download.

Manual download of the update packages

Go to the following websites to manually download the update packages from the Microsoft Download Center:

Installation instructions
 
How to obtain and install Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5
 
Download information
Update packages for Virtual Machine Manager are available by manual download.
Manual download of the update packages
Go to the following websites to manually download the update packages from the Microsoft Download Center:

DownloadDownload the Server update package now.

Add your Azure Subscription v1 only to System Center Virtual Machine manager 2016 #SCVMM #Azure #MSCloud   4 comments

When you are testing Virtual Machine Manager (VMM) in System Center 2016 and you want to connect your Azure Subscription connected you need a Certificate and publish this is the admin portal. But as you thought he cool I can access all my resource groups VM’s and my old VM’s eh no VMM 2016 Preview can only manage  the old VM’s.

To do this go to the VMM Console and Add Subscription

image

Easy as it is fill in the blanks

The Display name is the name you want and has no pointer to Azure

the Subscription ID is directly linked to Azure this is where your VM’s are

image

The Certificate we need to make this by hand.

First the Subscription ID go to the Azure.com portal and in the Subscriptions there is the ID.

image

image

Next we need a Certificate for a selfsigned certificate we can use Makecert but what fun is that .

Makecert.exe

https://robertsmit.wordpress.com/2015/05/01/manage-azure-with-system-center-2012-r2-virtual-machine-manager-scvmm-2012-r2-ur6/

 

Create a new self-signed certificate

You can use any tool available to create a self-signed certificate as long as they adhere to these settings:

  • An X.509 certificate.
  • Contains a private key.
  • Created for key exchange (.pfx file).
  • Subject name must match the domain used to access the cloud service. > You cannot acquire an SSL certificate for the cloudapp.net (or for any Azure related) domain; the certificate’s subject name must match the custom domain name used to access your application. For example, contoso.net, not contoso.cloudapp.net.
  • Minimum of 2048-bit encryption.
  • Service Certificate Only: Client-side certificate must reside in the Personal certificate store.

There are two easy ways to create a certificate on Windows, with the makecert.exe utility, or IIS.

Makecert.exe

This utility has been deprecated and is no longer documented here. Please see this MSDN article for more information.

Create a Certificate with Powershell

there is a new command in powershell : New-SelfSignedCertificate

this is how we create a certificate quick and easy and I also exported the Certificate

#Create new Certificate
$cert = New-SelfSignedCertificate -Subject AzureVMM01 -FriendlyName AzureVMM01 -Type Custom -CertStoreLocation "Cert:\currentuser\My" -KeyExportPolicy ExportableEncrypted -KeyLength 2048 -KeySpec KeyExchange

#set password for PFX
$password = ConvertTo-SecureString -String "P@ssw0rd" -Force -AsPlainText

#Export Certificate
Export-PfxCertificate -Cert $cert -FilePath "c:\cert\scvmm16azure.pfx" -Password $password

# to use this certificate in the Azure management portal export it to a .cer file
Export-Certificate -Type CERT -Cert $cert -FilePath "c:\cert\scvmm16azure.cer"

 

image

Now that the Certificate is exported I can upload this in the Old Azure V1 portal

image

Go to Settings and Management Certificates at the bottom there is a upload link.

image

Select the fresh created Certificate with the right subscription ( must be the same as the ID picked earlier )

image

Now that the Azure Certificate is in place I check browse and see the local certificate also.

image

After these steps we see the subscription in the console

image

here you can manage the VM’s with out the Azure v1 Portal.

As the the Resource Group option is still unavailable you can Vote for this in the user https://systemcentervmm.uservoice.com

Add Azure Resource Manager Stack based Azure VMs to the subscription view

 

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

Microsoft Azure Active Directory and Office 365 Readiness Wizard integration with your on-premises AD #Office365   Leave a comment

In this blog post I connect my Office 365 with my on premise Active Directory Based on the Azure AD Connect

Before you start installing Azure AD Connect, make sure to download Azure AD Connect and complete the pre-requisite steps in Azure AD Connect: Hardware and prerequisites.

Azure AD Connect allows you to quickly onboard to Azure AD and Office 365

Integrating your on-premises directories with Azure AD makes your users more productive by providing a common identity for accessing both cloud and on-premises resources. With this integration users and organizations can take advantage of the following:

  • Organizations can provide users with a common hybrid identity across on-premises or cloud-based services leveraging Windows Server Active Directory and then connecting to Azure Active Directory.
  • Administrators can provide conditional access based on application resource, device and user identity, network location and multifactor authentication.
  • Users can leverage their common identity through accounts in Azure AD to Office 365, Intune, SaaS apps and third-party applications.
  • Developers can build applications that leverage the common identity model, integrating applications into Active Directory on-premises or Azure for cloud-based applications

Azure AD Connect makes this integration easy and simplifies the management of your on-premises and cloud identity infrastructure.

 

image image

As using the Office 365 domain the .Local are useless you can’t resolve them over the internet.

 

Installing Microsoft Azure Active Directory Connect

When Installing Microsoft Azure Active Directory Connect you will need the pre-requisite steps in Azure AD Connect: Hardware and prerequisites.

image image

In the next steps you can customize the installation

image

I change the Default install Location

I use a dedicated SQL server that holds my Sync DB and this can be a my sql express DB.

I pre Created a Service Account that has the right amount of rights else you will see an account like MSOL_46396c1d8b6e.

 

imageimage

I used my 356 account and the password and I use Password sync.

 

imageimage

Connect my local Active Directory with my own local Account. Filling in the blanks and use Add Directory

imageimage

In the next steps you can customize the sync properties and the OU that you want to sync. If you pick the whole AD then all objects are synced and Deletion in the Web is not real funny.

imageimage

After I picked the OU for filtering we are ready for the first sync.

image image

as you can choose sync right now or later

imageimage

as you can see there is a new sync user created in Office 365

image

and on the server where you installed Microsoft Azure Active Directory Connect there is a troubleshooting tool

it can be found : C:\Program Files\Microsoft Azure AD Sync\UIShell\miisclient.exe

 

image

 

This is the installation on premise but you can also use the Office 365 Wizard to sync your AD.

Logon as an Office 365 Global Administrator and in the Admin Center Settings there is an Azure AD option

But Remember : When you are using a Free or trail subscription the usage of the Azure AD Free Version will not work you will need to use the Azure AD instead.

image

imageimage

Connecting to the Dirsync wizard and starting the Readiness Wizard will guide you to 3 steps

image

Step 1 a new popup will do the checks

image

A little download will popup

image

The Tools are installed and will run. If not make sure you have admin rights on the machine that is running this assistant

imageimage

Now that the scan is ready and completed we can see some details about the scan

image

my demo Ad is not that big

image

it also scans my Domains  / UPC records and shows me what is suitable and what not

image

my domains in the O365 suite

image

image

After correcting the domain setup I can use the domains for O365.

 

image

A little clean up is needed in my AD

image

The next step is installing Azure AD Connect I already did this above and I’m running this on the same machine so no problem to go further.

 

image

the last step and the AD sync is working.

imageimage

So this is all a lot of steps but basically it is al very simple when you have the right info and the domains setup up then you are good to go.

And remember don’t sync the entire AD just as test.

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog

Posted July 13, 2016 by Robert Smit [MVP] in Azure

Tagged with

Install the OMS agent using GPO automation with Powershell OMS WorkSpace lookup #MSOMS #Azure   1 comment

Suppose you want to deploy the OMS ( Microsoft Operations Management Suite ) Agent but you don’t want to do this by hand. Well Supposed you could run a Powershell script that installs the Agent. But in this case it is about deployments and a lot of VM’s are getting deployed and removed and you don’t want to put the Agent in the Template VM. I recently had to build a poor man’s lightweight deployment solution. As there is noting yet in the Cloud I used the good Old Active Directory.

https://www.microsoft.com/en-us/cloud-platform/operations-management-suite

Microsoft Operations Management Suite

So Old Skool deployment by GPO as you could use this for any file or solution. and yes Powershell could also be handy but in this case the VM’s can be remote controlled as the remote Port is firewalled.

https://robertsmit.wordpress.com/

Create a GPO in my case “ Deploy-OMS”

Edit the GPO

image

and Go to the Computer Settings right Click on the folder choose New and folder 

image I use Update the folder Pick a name

Now the GPO Creates a folder on all targeted Machines I did place this GPO on top be carful with that!

 

image

Next same as on the Folder new file

image

In this new file I’ll use the Source and destination keep in mind the destination is on the machine where the agent needs to be.

imageimage

Do this for both files or if you have more then do this per file and If you want to limited this a bit there a a few options to do that.

the Apply once option and the Item-Level targeting based on your Query the GPO will Execute or Not. (this is not needed but it is optional )

image

As I used a CMD batch file you need to create one with your task

I used this one liner to install the OMS Agent use your own key and save this file as a CMD file

"c:\Package-deploy\MMASetup-AMD64.exe" /C:"setup.exe /qn ADD_OPINSIGHTS_WORKSPACE=1 OPINSIGHTS_WORKSPACE_ID=d69d8969-1111-4586-80f0-4a11bc111199c OPINSIGHTS_WORKSPACE_KEY=3zNTcggsfsfsdgjhkldsaOyQ0/dgMwsbdtrgQVPXqu== AcceptEndUserLicenseAgreement=1"

 

image image

In case you can’t find the Workspace ID check your portal and go to the settings Dashboard. and get your info.

image

But In case you want to do a little bit of Powershell.  OMS Powershell

First let me check if the Modules are installed if not Install the modules.

 

Find-Module AzureRM.OperationalInsights | Install-Module
Install-Module AzureRM.OperationalInsights -Scope CurrentUser
Get-Module AzureRm.OperationalInsights

https://robertsmit.wordpress.com/

Next we need to login to your Subscription

Login-AzureRmAccount
Get-AzureRmSubscription

If you have Multiple subscriptions pick the right one

Select-AzureRmSubscription –SubscriptionId

#Get your WorkSpace ID
Get-AzureRmOperationalInsightsWorkspace |select Name,ResourceGroupName,CustomerId

image

I use these two as variable

$ResourceGroupName = "OI-Default-East-US"
$WorkSpaceName = "clustermvp"

Now we get the key that we needed.

Get-AzureRmOperationalInsightsWorkspaceSharedKeys -ResourceGroupName $ResourceGroupName -Name $WorkSpaceName

image

See how easy Powershell is just take baby steps find the info and you will learn every day step by step.

 

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

  • Twitter

  • %d bloggers like this: