Burkard Josh

Senior System Engineer working for one of europes largest construction companies. i will write about Windows, System Center, Network and other interesting Technologies.

how to get the correct Virtual Disk for a VMware vm

Burkard Josh 8. March 2017 0

Some times I have the problem, I need to resize or delete a VMware virtual disk, but I only know the guest’s drive letter. In vm’s where there are only one virtual disk, or where each virtual disk has a different size, this isn’t a problem. but if you have a vm with multiple virtual disk with exactly the same size, you can’t compare it between the guest Disk Manager and the virtual disk sizes. if your vm has more than one SCSI controller, the problem will increase.

Windows Disk Manager	VMware VM settings

I searched long time to solve this problem, but I couldn’t find an easy solution for this. so I wrote this PowerShell script:

<#
.SYNOPSIS
    This script will return informations about virtual disks and windows disk allocation

.DESCRIPTION
    This script will return informations about virtual disks and windows disk allocation

.PARAMETER vCenterName
    defines the fqdn of the vCenter

.PARAMETER vmName
    defines the name of the vm (like naming in vCenter, not the fqdn / dns name)

.PARAMETER vmCred
    enter credentials to connect to the guest vm

.EXAMPLE
    $vmCred = New-Object System.Management.Automation.PSCredential ('domain\username', ( ConvertTo-SecureString 'YourSecretPassword' -AsPlainText -Force ) )
    .\ALL-OPR-get-VMDiskInfos.ps1 -vCenterName 'vcenter.domain.local' -vmName 'VMName' -vmcred $vmCred 

.NOTES
    -Author:		Josh Burkard
    -Email :		josh@burkard.it
    -CreationDate:	07.03.2018
    -LastModifiedDate: 
    -Version:		1.0.0.0
    -History:
        07.03.2018	1.0.0.0	Josh Burkard	InitalVersion

.LINK

#>
Param 
(
    # Parameter help description
    [Parameter(Mandatory=$true)][string]$vCenterName,
    [Parameter(Mandatory=$true)][string]$vmName,
    [System.Management.Automation.PSCredential][Parameter(Mandatory=$true)]$vmCred
)

#region Decalarations
#endregion Decalarations

#region Functions
#endregion Functions

#region Execution
    #region verify Params
        if ( [string]::IsNullOrEmpty( $vCenterName ) )
        {
            Write-Host  "parameter vCenterName was  not definied" -ForegroundColor Red
        } elseif ( [string]::IsNullOrEmpty( $vmName ) )
        {
            Write-Host  "parameter vmName was  not definied" -ForegroundColor Red
        } elseif ( [string]::IsNullOrEmpty( $vmCred ) )
        {
            $vmCred = Get-Credential
        } else {
            Write-Verbose "all needed parameters set"
        }
    #endregion verify Params


    #region load VMware Snapins
        Write-Verbose "load VMware Snappins"
        foreach ($comp in "VMware.VimAutomation.Core", "VMware.ImageBuilder") {
            if (Get-Module -ListAvailable -Name $comp -ErrorAction:SilentlyContinue) {
                if (!(Get-Module -Name $comp -ErrorAction:SilentlyContinue)) {
                    if (!(Import-Module -PassThru -Name $comp -ErrorAction:SilentlyContinue)) {
                        Write-Host "FATAL ERROR: Failed to import the $comp module!" -ForegroundColor Red
                        # Exit
                    }
                }
            } else {
                if (Get-PSSnapin -Registered -Name $comp -ErrorAction:SilentlyContinue) {
                    if (!(Get-PSSnapin -Name $comp -ErrorAction:SilentlyContinue)) {
                        if (!(Add-PSSnapin -PassThru -Name $comp -ErrorAction:SilentlyContinue)) {
                            Write-Host "FATAL ERROR: Failed to add the $comp snapin!" -ForegroundColor Red
                            # Exit
                        }
                    }
                } else {
                    Write-Host "FATAL ERROR: $comp is not available as a module or snapin! It looks like there is no compatible version of PowerCLI installed!" -ForegroundColor Red
                    # Exit
                }
            }
        }
    #endregion load VMware Snapins

    #region connect to vCenter
        Write-Verbose "connecting to vCenter $vCenterName"
        try 
        {
            Connect-VIServer -Server $vCenterName -WarningAction SilentlyContinue | Out-Null
            Write-Verbose "connected to vCenter $vCenterName"
        } catch {
            $ErrorMessage = $_.Exception.Message
            # $FailedItem = $_.Exception.ItemName
            Write-Host "couldn't connect to vCenter '$vCenter'" -ForegroundColor Red
            Write-Host $ErrorMessage -ForegroundColor Red
            # Exit
        }
    #endregion connect to vCenter
    
    #region get VM
        $vm = Get-VM -Name $vmName
        if ( [string]::IsNullOrEmpty( $vm ) )
        {
            Write-Host  "VM not found" -ForegroundColor Red
            # exit
        } else {
            Write-Verbose "vm $vmName found" 
        }
    #endregion get VM
    
    #region get VM View for SCSI Controller
        $vmview = Get-View -ViewType VirtualMachine -Filter @{"Name" = $vmName}
        if ( !( [string]::IsNullOrEmpty( $vmview ) ) )
        {
            Write-Verbose "vmView $vmName found" 
            $vmDisks = @()
            $VirtualSCSIControllers = $vmview.Config.Hardware.Device | Where-Object {$_.DeviceInfo.Label -match "SCSI"}
            $VirtualSCSIController = $VirtualSCSIControllers[0]
            foreach ($VirtualSCSIController in $VirtualSCSIControllers ) 
            {
                $VirtualDiskDevices = $vmview.Config.Hardware.Device | Where-Object { $_.ControllerKey -eq $VirtualSCSIController.Key }
                foreach ($VirtualDiskDevice in $VirtualDiskDevices ) 
                {
                    $vmDisks += New-Object -TypeName PSObject -Property @{
                        VirtualDeviceNode    = "SCSI ($( $VirtualSCSIController.BusNumber ):$( $VirtualDiskDevice.UnitNumber )) $( $VirtualDiskDevice.DeviceInfo.Label )"
                        PciSlotNumber        = $VirtualSCSIController.SlotInfo.PciSlotNumber
                        DataStore            = $VirtualDiskDevice.Backing.DataStore
                        FileName             = $VirtualDiskDevice.Backing.FileName
                        ControllerKey        = $VirtualSCSIController.Key
                        DiskKey              = $VirtualDiskDevice.Key
                        ControllerBus        = $VirtualSCSIController.BusNumber
                        ControllerUnitNumber = $VirtualSCSIController.UnitNumber
                        DiskUnitNumber       = $VirtualDiskDevice.UnitNumber
                    }
                }
            }
        } else {
            Write-Host  "VMView not found" -ForegroundColor Red
            # exit
        }
    #endregion get VM View for SCSI Controller
    
    #region get Disk and volumes from guest system
        $scripttext = @"
[Int64]$('$')HKLM = "2147483650"
[String]$('$')value = "UINumber"
$('$')Reg_Query = Get-WmiObject -List "StdRegProv" -Namespace root\cimv2 
$('$')PhysicalDisks = Get-WmiObject -Class "Win32_DiskDrive" -Namespace "root\CIMV2"    
# $('$')PhysicalDisks
$('$')DiskDrives = Get-WmiObject Win32_DiskDrive
$('$')DiskInfos = Get-WmiObject Win32_DiskDrive | ForEach-Object {
    $('$')DiskDrive = $('$')_
    $('$')PNPDeviceID = $('$')DiskDrive.PNPDeviceID.split('\')
    $('$')key = "SYSTEM\CurrentControlSet\Enum\$('$')($('$')PNPDeviceID[0])\$('$')($('$')PNPDeviceID[1])\$('$')($('$')PNPDeviceID[2])"
    $('$')PciSlotNumber = ($('$')Reg_Query.GetDWORDValue($('$')HKLM,$('$')key,$('$')value)).uvalue

    $('$')UniqueId = ( ( $('$')PhysicalDisks | Where-Object { $('$')DiskDrive.DeviceID -eq "\\.\PHYSICALDRIVE$('$')( $('$')_.DeviceId )" } ).UniqueId )
    If ( [string]::IsNullOrEmpty( $('$')UniqueId ) )
    {
        $('$')UniqueId = ( $('$')PhysicalDisks | Where-Object { $('$')DiskDrive.DeviceID -eq $('$')_.Name } ).SerialNumber
    }
    $('$')DiskDriveToDiskPartitions = Get-WmiObject -Query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID='$('$')($('$')DiskDrive.DeviceID)'} WHERE AssocClass = Win32_DiskDriveToDiskPartition"
    $('$')DiskDriveToDiskPartitions | ForEach-Object {
        $('$')partition = $('$')_
        
        $('$')LogicalDiskToPartitions = Get-WmiObject -Query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID='$('$')($('$')partition.DeviceID)'} WHERE AssocClass = Win32_LogicalDiskToPartition" 
        $('$')LogicalDiskToPartitions | ForEach-Object {
            New-Object -Type PSCustomObject -Property @{
                DiskSize        = $('$')DiskDrive.Size
                DiskModel       = $('$')DiskDrive.Model
                SCSIBus         = $('$')DiskDrive.SCSIBus
                SCSILogicalUnit = $('$')DiskDrive.SCSILogicalUnit
                SCSIPort        = $('$')DiskDrive.SCSIPort
                SCSITargetId    = $('$')DiskDrive.SCSITargetId
                PNPDeviceID     = $('$')DiskDrive.PNPDeviceID
                PciSlotNumber   = $('$')PciSlotNumber
                UniqueId        = $('$')UniqueId
                Partition       = $('$')partition.Name
                RawSize         = $('$')partition.Size
                DiskID          = $('$')partition.DiskIndex
                StartingOffset  = $('$')partition.StartingOffset
                DriveLetter     = $('$')_.DeviceID
                VolumeName      = $('$')_.VolumeName
                Size            = $('$')_.Size
                FreeSpace       = $('$')_.FreeSpace
            }
        }
    }
}
$('$')DiskInfos = $('$')DiskInfos | Where-Object { ( ! ( [string]::IsNullOrEmpty( $('$')_.UniqueId ) ) ) }
# $('$')DiskInfos | Sort-Object DriveLetter, DiskID | Select-Object -Unique UniqueId, DiskID, DriveLetter, SCSIBus, SCSILogicalUnit, SCSIPort, SCSITargetId, PNPDeviceID, PciSlotNumber | Format-Table
$('$')DiskInfos | convertTo-CSV
"@
        try {
            $WinDisks = Invoke-VMScript -VM $vm -ScriptText $scripttext -GuestCredential $vmCred -ErrorAction stop | convertfrom-csv    
        }
        catch {
            $ErrorMessage = $_.Exception.Message
            # $FailedItem = $_.Exception.ItemName
            Write-Host "couldn't connect to VM guest" -ForegroundColor Red
            Write-Host $ErrorMessage -ForegroundColor Red
            exit
        }
        
    #endregion get Disk and volumes from guest system
    
    #region merge WinDisk and VMware Disk Infos
        $DiskInfos = @()
        # $WinDisk = $WinDisks[1] 
        foreach ( $WinDisk in $WinDisks )
        {
            $vmDisk = $vmDisks | Where-Object { $_.PciSlotNumber -eq $WinDisk.PciSlotNumber -and $_.DiskUnitNumber -eq $WinDisk.SCSITargetId }
            $DiskInfos += New-Object -TypeName PSOBject -Property @{
                WinDiskID              = $WinDisk.DiskID
                PCISlotNumber          = $WinDisk.PciSlotNumber
                WinVolumeName          = $WinDisk.VolumeName
                WinDiskSCSITargetId    = $WinDisk.SCSITargetId
                DriveLetter            = $WinDisk.DriveLetter
                VMControllerBusNumber  = $vmDisk.ControllerBus
                VirtualDeviceNode      = $vmDisk.VirtualDeviceNode
                FileName               = $vmDisk.FileName
                DataStore              = $vmDisk.DataStore
            }
        }
        $DiskInfos 
    #endregion merge WinDisk and VMware Disk Infos
#endregion Execution

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

.SYNOPSIS

This script will return informations about virtual disks and windows disk allocation

.DESCRIPTION

This script will return informations about virtual disks and windows disk allocation

.PARAMETER vCenterName

defines the fqdn of the vCenter

.PARAMETER vmName

defines the name of the vm (like naming in vCenter, not the fqdn / dns name)

.PARAMETER vmCred

enter credentials to connect to the guest vm

.EXAMPLE

$vmCred = New-Object System.Management.Automation.PSCredential ('domain\username', ( ConvertTo-SecureString 'YourSecretPassword' -AsPlainText -Force ) )

.\ALL-OPR-get-VMDiskInfos.ps1 -vCenterName 'vcenter.domain.local' -vmName 'VMName' -vmcred $vmCred

.NOTES

-Author: Josh Burkard

-Email : josh@burkard.it

-CreationDate: 07.03.2018

-LastModifiedDate:

-Version: 1.0.0.0

-History:

07.03.2018 1.0.0.0 Josh Burkard InitalVersion

.LINK

Param

(

# Parameter help description

[Parameter(Mandatory=$true)][string]$vCenterName,

[Parameter(Mandatory=$true)][string]$vmName,

[System.Management.Automation.PSCredential][Parameter(Mandatory=$true)]$vmCred

)

#region Decalarations

#endregion Decalarations

#region Functions

#endregion Functions

#region Execution

#region verify Params

if ( [string]::IsNullOrEmpty( $vCenterName ) )

{

Write-Host "parameter vCenterName was not definied" -ForegroundColor Red

} elseif ( [string]::IsNullOrEmpty( $vmName ) )

{

Write-Host "parameter vmName was not definied" -ForegroundColor Red

} elseif ( [string]::IsNullOrEmpty( $vmCred ) )

{

$vmCred = Get-Credential

} else {

Write-Verbose "all needed parameters set"

}

#endregion verify Params

#region load VMware Snapins

Write-Verbose "load VMware Snappins"

foreach ($comp in "VMware.VimAutomation.Core", "VMware.ImageBuilder") {

if (Get-Module -ListAvailable -Name $comp -ErrorAction:SilentlyContinue) {

if (!(Get-Module -Name $comp -ErrorAction:SilentlyContinue)) {

if (!(Import-Module -PassThru -Name $comp -ErrorAction:SilentlyContinue)) {

Write-Host "FATAL ERROR: Failed to import the $comp module!" -ForegroundColor Red

# Exit

}

} else {

if (Get-PSSnapin -Registered -Name $comp -ErrorAction:SilentlyContinue) {

if (!(Get-PSSnapin -Name $comp -ErrorAction:SilentlyContinue)) {

if (!(Add-PSSnapin -PassThru -Name $comp -ErrorAction:SilentlyContinue)) {

Write-Host "FATAL ERROR: Failed to add the $comp snapin!" -ForegroundColor Red

# Exit

}

} else {

Write-Host "FATAL ERROR: $comp is not available as a module or snapin! It looks like there is no compatible version of PowerCLI installed!" -ForegroundColor Red

# Exit

}

#endregion load VMware Snapins

#region connect to vCenter

Write-Verbose "connecting to vCenter $vCenterName"

try

{

Connect-VIServer -Server $vCenterName -WarningAction SilentlyContinue | Out-Null

Write-Verbose "connected to vCenter $vCenterName"

} catch {

$ErrorMessage = $_.Exception.Message

# $FailedItem = $_.Exception.ItemName

Write-Host "couldn't connect to vCenter '$vCenter'" -ForegroundColor Red

Write-Host $ErrorMessage -ForegroundColor Red

# Exit

}

#endregion connect to vCenter

#region get VM

$vm = Get-VM -Name $vmName

if ( [string]::IsNullOrEmpty( $vm ) )

{

Write-Host "VM not found" -ForegroundColor Red

# exit

} else {

Write-Verbose "vm $vmName found"

}

#endregion get VM

#region get VM View for SCSI Controller

$vmview = Get-View -ViewType VirtualMachine -Filter @{"Name" = $vmName}

if ( !( [string]::IsNullOrEmpty( $vmview ) ) )

{

Write-Verbose "vmView $vmName found"

$vmDisks = @()

$VirtualSCSIControllers = $vmview.Config.Hardware.Device | Where-Object {$_.DeviceInfo.Label -match "SCSI"}

$VirtualSCSIController = $VirtualSCSIControllers[0]

foreach ($VirtualSCSIController in $VirtualSCSIControllers )

{

$VirtualDiskDevices = $vmview.Config.Hardware.Device | Where-Object { $_.ControllerKey -eq $VirtualSCSIController.Key }

foreach ($VirtualDiskDevice in $VirtualDiskDevices )

{

$vmDisks += New-Object -TypeName PSObject -Property @{

VirtualDeviceNode = "SCSI ($( $VirtualSCSIController.BusNumber ):$( $VirtualDiskDevice.UnitNumber )) $( $VirtualDiskDevice.DeviceInfo.Label )"

PciSlotNumber = $VirtualSCSIController.SlotInfo.PciSlotNumber

DataStore = $VirtualDiskDevice.Backing.DataStore

FileName = $VirtualDiskDevice.Backing.FileName

ControllerKey = $VirtualSCSIController.Key

DiskKey = $VirtualDiskDevice.Key

ControllerBus = $VirtualSCSIController.BusNumber

ControllerUnitNumber = $VirtualSCSIController.UnitNumber

DiskUnitNumber = $VirtualDiskDevice.UnitNumber

}

} else {

Write-Host "VMView not found" -ForegroundColor Red

# exit

}

#endregion get VM View for SCSI Controller

#region get Disk and volumes from guest system

$scripttext = @"

[Int64]$('$')HKLM = "2147483650"

[String]$('$')value = "UINumber"

$('$')Reg_Query = Get-WmiObject -List "StdRegProv" -Namespace root\cimv2

$('$')PhysicalDisks = Get-WmiObject -Class "Win32_DiskDrive" -Namespace "root\CIMV2"

# $('$')PhysicalDisks

$('$')DiskDrives = Get-WmiObject Win32_DiskDrive

$('$')DiskInfos = Get-WmiObject Win32_DiskDrive | ForEach-Object {

$('$')DiskDrive = $('$')_

$('$')PNPDeviceID = $('$')DiskDrive.PNPDeviceID.split('\')

$('$')key = "SYSTEM\CurrentControlSet\Enum\$('$')($('$')PNPDeviceID[0])\$('$')($('$')PNPDeviceID[1])\$('$')($('$')PNPDeviceID[2])"

$('$')PciSlotNumber = ($('$')Reg_Query.GetDWORDValue($('$')HKLM,$('$')key,$('$')value)).uvalue

$('$')UniqueId = ( ( $('$')PhysicalDisks | Where-Object { $('$')DiskDrive.DeviceID -eq "\\.\PHYSICALDRIVE$('$')( $('$')_.DeviceId )" } ).UniqueId )

If ( [string]::IsNullOrEmpty( $('$')UniqueId ) )

{

$('$')UniqueId = ( $('$')PhysicalDisks | Where-Object { $('$')DiskDrive.DeviceID -eq $('$')_.Name } ).SerialNumber

}

$('$')DiskDriveToDiskPartitions = Get-WmiObject -Query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID='$('$')($('$')DiskDrive.DeviceID)'} WHERE AssocClass = Win32_DiskDriveToDiskPartition"

$('$')DiskDriveToDiskPartitions | ForEach-Object {

$('$')partition = $('$')_

$('$')LogicalDiskToPartitions = Get-WmiObject -Query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID='$('$')($('$')partition.DeviceID)'} WHERE AssocClass = Win32_LogicalDiskToPartition"

$('$')LogicalDiskToPartitions | ForEach-Object {

New-Object -Type PSCustomObject -Property @{

DiskSize = $('$')DiskDrive.Size

DiskModel = $('$')DiskDrive.Model

SCSIBus = $('$')DiskDrive.SCSIBus

SCSILogicalUnit = $('$')DiskDrive.SCSILogicalUnit

SCSIPort = $('$')DiskDrive.SCSIPort

SCSITargetId = $('$')DiskDrive.SCSITargetId

PNPDeviceID = $('$')DiskDrive.PNPDeviceID

PciSlotNumber = $('$')PciSlotNumber

UniqueId = $('$')UniqueId

Partition = $('$')partition.Name

RawSize = $('$')partition.Size

DiskID = $('$')partition.DiskIndex

StartingOffset = $('$')partition.StartingOffset

DriveLetter = $('$')_.DeviceID

VolumeName = $('$')_.VolumeName

Size = $('$')_.Size

FreeSpace = $('$')_.FreeSpace

}

$('$')DiskInfos = $('$')DiskInfos | Where-Object { ( ! ( [string]::IsNullOrEmpty( $('$')_.UniqueId ) ) ) }

# $('$')DiskInfos | Sort-Object DriveLetter, DiskID | Select-Object -Unique UniqueId, DiskID, DriveLetter, SCSIBus, SCSILogicalUnit, SCSIPort, SCSITargetId, PNPDeviceID, PciSlotNumber | Format-Table

$('$')DiskInfos | convertTo-CSV

try {

$WinDisks = Invoke-VMScript -VM $vm -ScriptText $scripttext -GuestCredential $vmCred -ErrorAction stop | convertfrom-csv

}

catch {

$ErrorMessage = $_.Exception.Message

# $FailedItem = $_.Exception.ItemName

Write-Host "couldn't connect to VM guest" -ForegroundColor Red

Write-Host $ErrorMessage -ForegroundColor Red

exit

}

#endregion get Disk and volumes from guest system

#region merge WinDisk and VMware Disk Infos

$DiskInfos = @()

# $WinDisk = $WinDisks[1]

foreach ( $WinDisk in $WinDisks )

{

$vmDisk = $vmDisks | Where-Object { $_.PciSlotNumber -eq $WinDisk.PciSlotNumber -and $_.DiskUnitNumber -eq $WinDisk.SCSITargetId }

$DiskInfos += New-Object -TypeName PSOBject -Property @{

WinDiskID = $WinDisk.DiskID

PCISlotNumber = $WinDisk.PciSlotNumber

WinVolumeName = $WinDisk.VolumeName

WinDiskSCSITargetId = $WinDisk.SCSITargetId

DriveLetter = $WinDisk.DriveLetter

VMControllerBusNumber = $vmDisk.ControllerBus

VirtualDeviceNode = $vmDisk.VirtualDeviceNode

FileName = $vmDisk.FileName

DataStore = $vmDisk.DataStore

}

$DiskInfos

#endregion merge WinDisk and VMware Disk Infos

#endregion Execution

when you run the script, it will ask you for credentials and then shows you the informations about booth of your virtual disk and Windows drive : read more

Azure Automation Hybrid Worker behind a Firewall / Proxy

Burkard Josh 24. March 2016 0

One nice feature of Azure Automation is the Hybrid Worker. With the Hybrid Worker you can execute Runbooks inside your onPremise infrastructure. according to the official documentation or at John Hennen’s post, you have to open your FireWall for outbound traffic to *.cloudapp.net for this ports 443,9354,30000-30199.

When i told this requirement to our security-team, they weren’t very enthusiastic about the wildcard rule for *.cloudapp.net. So i have to search another solution.

To configure the Microsoft Monitoring Agent to use your proxy services, go to the Control Panel → System and Security → Microsoft Monitoring Agent and then go to the Proxy Settings tab: read more

daily Backup Report for SC DPM

Burkard Josh 2. November 2015 0

i like System Center Dataprotection Manager, especially for the backup possibilites of remote Windows servers and the Online backup to Azure. But in my past, i lost the overview about succeded and failed backup jobs. The included reporting doesn’t helped me enough, and the alert notification was like spam. I needed a daily reportÂ with one view of all Jobs, Disks, Agents and other states. To reach this goal, i wrote my own PowerShell script, which i want toÂ share here.

the report, sent by mail will look like this: read more

document your SCOM 2012 environment

Burkard Josh 11. April 2014

This is quite huge for me, because I’ve been working on this script for the last two months and finally decided, to release the script to public, although I know that it’s still far from complete.

Document your Operations Manager 2012 environment

You should know your environment and what happens in it and you should be able to show people what exactly has been configured in your environment. This is quite important for consultants, but also for admins. Consultants need to create a documentation after implementing Operations Manager 2012 at a costumer’s site and admins should be able to know how their environment looks like at any given time. read more

demoted Domain Controller still present in SCOM

Burkard Josh 24. February 2014 0

If you demote a Domain Controller, SCOM will generate a lot of alerts. By design, there is no automatically undiscovery for the Rules and Monitores for the Active Directory Roles.

Solution 1

This solution will remove all disabled Class instances from an existing object. it will not change any other properties of the object.

Open the Operations Management Shell
type in this command:

Remove-SCOMDisabledClassInstance -ComputerName <Demoted Server>

1	Remove-SCOMDisabledClassInstance -ComputerName <Demoted Server>

Stop the System Center Management service
Delete the folder C:\Program Files\System Center Operations Manager\Agent\Health Service State
Start the System Center Management service

Solution 2

This solution will clear only the agent cache. Sometime this will be sufficient, if the server discovery / undiscovery was already done well:

Stop the System Center Management service
Delete the folder C:\Program Files\System Center Operations Manager\Agent\Health Service State
Start the System Center Management service

Solution 3

This solution will remove the entire object and then recreate the object with it’s discovery. The new object wouldn’t be discovered as Domain Controller. The new object will have an new guid and any overwrites to the old object will be lost. read more

extend the Active Directory Users class for SCSM

Burkard Josh 17. February 2014 0

Today I needed some additional fields for the Active Directory User class for an SCSM Service Offering. For example, I need the PrimarySmtpAddress, which exists in the AD as mail, but not in the SCSM class. in this post, I will describe, how I did it:

We will need:

System Center Service Manager 2012 SP1
System Center Orchestrator 2012 SP 1
Service Manager Authoring Tool
Strong name key file

Open the Service Manager Authoring Tool and click to the menu File New, to create a new Management Pack. Define a unique name for your management packs file name, in this Example: Josh.Test.Library.xml (Library mean’s that we will extend a library class) read more

delete orphaned computers from SCOM

Burkard Josh 21. January 2014 0

after renaming a Active Directory computer, the computer was automatically detected in SCOM with the correct new name. but after short time, I detected, that the originally agent was already there, but not reachable. so I deleted the old computer under Device Management – Agent Managed.

normally after maximum 3 days, the agent isn’t visible in the computer view. the delay of 3 days is by design. so don’t delete the computer manually to early.

If you still see the Computer showing up – even after 3 days – then in most cases, there is still a discovery associated with it. To find the discovery, use this query:

SELECT BME.FullName, DS.DiscoveryRuleID, D.DiscoveryName FROM typedmanagedentity TME 
JOIN BaseManagedEntity BME ON TME.BaseManagedEntityId = BME.BaseManagedEntityId 
JOIN DiscoverySourceToTypedManagedEntity DSTME ON TME.TypedManagedEntityID = DSTME.TypedManagedEntityID 
JOIN DiscoverySource DS ON DS.DiscoverySourceID = DSTME.DiscoverySourceID 
JOIN Discovery D ON DS.DiscoveryRuleID=D.DiscoveryID 
WHERE BME.Fullname LIKE '%ComputerName%'

SELECT BME.FullName, DS.DiscoveryRuleID, D.DiscoveryName FROM typedmanagedentity TME

JOIN BaseManagedEntity BME ON TME.BaseManagedEntityId = BME.BaseManagedEntityId

JOIN DiscoverySourceToTypedManagedEntity DSTME ON TME.TypedManagedEntityID = DSTME.TypedManagedEntityID

JOIN DiscoverySource DS ON DS.DiscoverySourceID = DSTME.DiscoverySourceID

JOIN Discovery D ON DS.DiscoveryRuleID=D.DiscoveryID

WHERE BME.Fullname LIKE '%ComputerName%'

in my case, I didn’t found any discovery for this computer and it was still available in the Windows Computer view one week after deletion of the agent. read more

Create SCOM Dashboard for SharePoint in Visio

Burkard Josh 15. January 2014 0

This week I created a DashBoard for SCOM in Visio to present it on a SharePoint site. Normally you could use the Visio 2010 Addin for SystemCenter – Operations Manager. But this addin has some special prerequisites for the presentation on the SharePoint site, like installing SCOM components and special configurations on the SharePoint Farm. Also it has the limitation, that it can only present monitor states, and can’t present rule values (for example: disk usage).

So I created my own solution, which I will describe here. An overview to the steps: read more

website rebranding

Burkard Josh 14. January 2014 0

Hello

my website was over years reachable under josh-burkard.ch, which was a long url. I was on search for a new and shorter domain name for this website. now I have found one, which is shorter and which describes what i’m doing and writing about: Information Technology (IT). So, my new web address is burkard.IT

of course, the old address will be available, but I would like the new shorter one.

SCOM 2012 agent communication issue

Burkard Josh 6. January 2014 0

This days, I had a very special problem with some new SCOM agents. I installed some new servers and installed the SCOM 2012 agent on it. But after some time, they appeared in the Agent Managed view, still as not monitored.

first I looked up the event logs on the new servers and found this errors:

According to this errors, I found a lot of blogs about network and certificate issues, like this one: http://geertbaeten.wordpress.com/2013/07/08/scom-agent-or-gateway-certificate-issue/

but I don’t have a Certificate authority and I also assumed not have a network problem. read more

Josh's IT-Blog

Information Technology, and other interesting things ...

Burkard Josh

how to get the correct Virtual Disk for a VMware vm

Azure Automation Hybrid Worker behind a Firewall / Proxy

daily Backup Report for SC DPM

document your SCOM 2012 environment

Document your Operations Manager 2012 environment

demoted Domain Controller still present in SCOM

Solution 1

Solution 2

Solution 3

extend the Active Directory Users class for SCSM

delete orphaned computers from SCOM

Create SCOM Dashboard for SharePoint in Visio

website rebranding

SCOM 2012 agent communication issue

Burkard Josh

Share this:

Share this:

Share this:

Document your Operations Manager 2012 environment

Share this:

Solution 1

Solution 2

Solution 3

Share this:

Share this:

Share this:

Share this:

Share this:

Share this: