SCCM Query find All Server count with OS Name

SCCM Query find All Server count with OS Name

• Recently I was asked to count of servers by OS
• It was quite Challenging as we need to understand the SCCM Structure very well to do the SQL Queries.
• Following are the Queries to fin the Server by OS Name and the count of Servers

SELECT VR.operatingSystem0,COUNT(VR.operatingSystem0) FROM v_R_System AS VR

WHERE VR.operatingSystem0 LIKE '%Windows Server%'

GROUP BY VR.operatingSystem0

Edge servers not discovered in Skype Management pack in SCOM 2012 R2

Edge servers not discovered  in Skype Management pack in SCOM 2012 R2

• Recetnly i was working for one of my customer and they have imported the Skype Management pack. All Skype roles are discovered except the Edge Server.
• They are showing as Agent management in the SCOM server, but still not appear in Skype Management pack.

Action taken:

• I directly felt that discovery script for Skype is failing on these server. As generally Edge servers are in DMZ, then are not in Domain.
• So i went to Agent Skype Edge server and Check the Operations manager event log for Error and found the following

Description: DiscoverMachine.ps1 : ——————————————————————————– -Script Name: Skype for Business Server 2015 MP Machine Topology Discovery -Run as account: nt authority\network service -Execution Policy: RemoteSigned ——————————————————————————– Value of Source Id is {5AAFA97E-833F-9AD1-2678-56AFD1E2214C}. Value of ManagedEntity Id is {C4F6E362-BE95-93C1-729D-3F7BD6FAAFD6}. Value of Target Computer is EDGESERVER01.group.domain.com. SkypeForBusiness Module is added Successfully initialize discovery data. An exception occurred during discovery script, Exception : Could not connect to SQL server : [Exception=System.Data.SqlClient.SqlException (0x80131904): Cannot open database “xds” requested by the login. The login failed. Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’. 

Solution:

• Add the “Network Service” to the following local groups on each Edge server.
• "RTC Component Local Group" and "
  RTC Local Administrators".
• Also enabe Proxy on the agent.
• Then restart the SCOM service on the agent and voila its show in Skype management pack in few minutes.

How to find which servers are allowed to do DNS Scavenging

How to find which servers are allowed to do DNS Scavenging

To see which servers are currently allowed to scavenge, run the command 

DNSCmd /ZoneInfo

• If there is a section “Scavenge Servers” at the bottom of the output, then those DNS servers whose IP addresses are listed are the only ones that can perform scavenging on the specified zone. 

• If there is no “Scavenge Servers” section present, then any DNS server otherwise permitted can perform scavenging on the zone.

Add new Disk on Virtual Servers in Windows Azure

Extend Disk on Virtual Servers in Windows Azure

• First Login to Windows Azure portal and your Virtual Mahcine and select "Attach an Empty Disk"

• Now enter the Disk Size you want and click Create

Install SCOM 2012 R2 agent on Servers Hosted in Microsoft Azure Cloud

Install SCOM agent on Servers Hosted in Microsoft Azure Cloud

• Microsot Azure is the Cloud Solution from Microsoft. You can Install SCOM agents and Monitor them using your Existing SCOM environment.
• To Install SCOM agent on Windows Serve hosted in Microsoft Azure Cloud
• Logon to Your Azure Portal
• Then Click on Operation Insight Tab on the left

• Then Click on the Workspace that you see 

• Now You will be taken to the Dashboard Page,Now Click on SERVERS Tab

Now Click on "Enable OP INSIGHTS"

• And Install SCOM agent on the Server. This will install SCOM agent on server automatically.

 

• Now Login to Your Server and Go to Control Panel and Open Microsoft Monitoring Agent. YOu can see that the agent ins installed.If you have In house SCOM server then configure you Management server and your SCOM management group. in Operations Manager Tab. By Default it Connects to Microsoft Operaions Manager

• You can see that after some time MP's get downloaded and Monitoring Start.

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps

HP latest Management Pack for Blade Systems and Proliant Servers - Step by Step Installation steps:

• HP has released the latest MP for monitoring the Blade and Proliant server
• Following are the list of MP:
• HP BladeSystem Management Pack (v 2.1)
• HP ProLiant Agentless Management Pack (v 3.1)
• HP ProLiant Linux Management Pack (v 3.1)
• HP ProLiant PRO Management Pack (v 2.1)
• HP ProLiant Server Management Pack (v 2.2)
• HP ProLiant VMware Management Pack (v 3.1) 
• You can download it from the here --> Click here

Following are the Components that are important in this MP:

• HP management packs
• HP Device Monitor Console (DMC)
• HP Device Monitor Service(DMS)
• HP Custom Data Manager(CDM)

HP management Packs:

              I suggest you install the HP Blade System Management Pack and the HP Proliant Server Management Pack. These should be enought to monitor all the Servers. Other are just some additional addon.

HP Device Monitor Console (DMC):

The HP Device Monitor Console (DMC) provides the user interface for connecting to the HP Device

Monitor Service (DMS) to add or remove devices supported by management packs that use the 

DMS. 

So you need to Install DMC first. You can install on any management server.
If you are already having older version called as HP enterprise manager, then Device Console replaces it.Just install the new DMC and it will automatically upgrade.

Then install the Above MP and everything will be discovered and start working.