PowerShell to install SCOM agent...

-
Well I have been busy!

Looking at all the PowerShell I've been pasting together from bits and pieces found around the web (Thanks Google!) it's no wonder that I've been AFK or more correctly AFB for a couple of months.

But now back with some PowerShell script-lets under my belt and here's one of them.

We have issues *cough* "firewall ports" accessing some of our servers in our remote data centres to push the SCOM agent.

We were unable to solve the *cough* "firewall ports" issue so we decided to go round the issue and manually install the agent on each server.

I wrote a PowerShell and VBS script to accomplish this.  Here there are.  Nothing fancy and I am sure that things could be done better however this is how we are acheiving bypassing our firewall....errr I mean resolved our issue.

The install is silent so you may want to adjust the MSI line and remove /quiet and /qn to help with troubleshooting this script in your environment.


PowerShell version:

# Powershell script to install and configure the Ops Manager Agent
# Ver. 1.0
# Use at your own risk!
$path_to_install = <your-path>

# Grab the machine name
$machine = get-content env:Computername
$FQDN = [system.net.dns]::GetHostEntry($Machine).HostName
# Get architecture
$os = get-wmiobject -class "Win32_OperatingSystem" -namespace "root\CIMV2"
if($os.OSArchitecture -eq "64-bit" -or $os.Caption -match "x64"){
 $path_to_install += "\amd64\MOMAgent.msi"
}
else{
 $path_to_install += "\x86\MOMAgent.msi"
}
# Setup Arguments
$args = "USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=MG-Europe MANAGEMENT_SERVER_DNS=<server name> SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"
$args = "/i " + $path_to_install + " /quiet /qn /promptrestart " + $args
# Install Ops Manager Agent
start-process -FilePath "msiexec.exe" -ArgumentList $args


VBScript: 
' VisualBasic script to install and configure the Ops Manager Agent
' Ver. 1.0
' Use at your own risk!
path_to_install = <your path>

' Grab the machine name
Set objWMI = GetObject( "winmgmts:\\.\root\cimv2")
Set colItems = objWMI.ExecQuery("Select * from Win32_ComputerSystem", ,48)
' Yes this is a collection so we have to ForEach it!
For Each objItem in colItems
 FQDN = objItem.Name & "." & objItem.Domain
 ' msgbox FQDN
Next
' Get architecture it is a collection AGAIN!
Set objProcs = objWMI.ExecQuery("Select * from Win32_Processor", ,48)
For Each objProc in objProcs
 If objProc.AddressWidth = "64" then
  path_to_install = path_to_install & "\amd64\MOMAgent.msi "
 Else
  path_to_install = path_to_install & "\x86\MOMAgent.msi "
 End If
Next
' Setup Arguments
args = " USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=MG-Europe MANAGEMENT_SERVER_DNS=<MS server name> SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1"
Set objShell = CreateObject("WScript.Shell")

' Install Ops Manager Agent
objShell.Run "msiexec.exe /i " & path_to_install & " /quiet /qn /promptrestart " & args

Enjoy

Comments

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine
Read more

Intune installation requires a wire...or does it?

-
If you are using Intune (great!) it assumes you have a wired connection (not great) - this is more of an issue as some machine now no longer have built in ethernet ports. It is possible to connect to your wireless - albeit in a slightly awkward way.....here's how During the OOBE hit SHIFT+F10 to get a command window and type either; start ms-settings: To get the settings window or start ms-availablenetworks: To see the network fly outs. Thanks to  Using a wireless network connection with Windows Autopilot white glove – Out of Office Hours (oofhours.com)
Read more

Security Policy 1001

-
We had an annoying warning showing every 5 minutes on our Read Only Domain Controllers.  This didn't affect service but meant we were losing our logs of important events (should the have occurred) "Security policy cannot be propagated. Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation." Source: SceCli Event: ID 101 We tracked this down to a GPO which was populating the local Administrators group. Obviously a Domain Controller has no local users or groups so this was causing the issue. Ensuring that the GPO did not apply to the Domain Controllers - yes the GPO was linked at the root! fixed the issue. It is strange that we did not see the warnings on our main Domain Controllers only on the Read Only DC's as this would have affected all DCs the same (I would have thought)
Read more