Venkat - I clearly address that in the above blog post. If you are using AD integration, you should not modify this setting. It will break AD integration.
It would be very nice, if the agent were able to download updates via the already opened standard ports, through the firewalls. Netbios is not an option, and now we have to make an sccm package.........
Hi Kevin,
Is this still the case for SCOM 2012?
Cheers,
Jarrad
Thanks Kevin.
Another question. Would you recommend this for internet based managed agents?
Hi Kevin,
I meant internet based just like in Config Manager, agents connecting via the internet. Don't worry this customer is using certs, gateway servers, firewalls, dedicated AD and Ops Mgr infrastructure isolated just for this, port redirects... etc. But I stupidly did not think about the UDP ports needed!!!
I'm a little confused by this, since we have a script that load balances the Agents between MS every month. Most of the Agents are manually installed, and some are pushed out from the console. According to this, we shouldn't be able to run the script successfully since the manual Agents should ignore it. We run R2 CU5 (now CU6) and it works fine.
So is this a case of "Console can't do it, but Powershell can" or is it the script is specifically written to circumvent the issue?
Param([array]$CSVServerList)
$arrServerObject = @()
$arrAgentObject = @()
foreach($Server in $CSVServerList)
{
$arrServerObject += Get-ManagementServer | where {$_.Name -eq $Server}
echo "Looking for $Server"
}
$ServerCount = $arrServerObject.Count
if ($ServerCount -gt 1)
{
echo "Found $ServerCount management servers"
} else {
echo "Found only 1 (or less) management servers. Aborting..."
Exit
}
echo "Getting agents..."
foreach ($Server in $arrServerObject)
{
$arrAgentObject += Get-Agent | where {$_.PrimaryManagementServerName -eq $Server.Name}
}
$AgentCount = $arrAgentObject.Count
if ($AgentCount -gt 1)
{
echo "Found $AgentCount agents"
Start-Sleep -m 200
} else {
echo "Found only 1 (or less) agents. Aborting..."
Exit
}
$i = 0
foreach ($Agent in $arrAgentObject)
{
if ($i -ge $ServerCount)
{
$i = 0
}
$arrTemp = @($arrServerObject | Where-Object {$_ -ne $arrServerObject[$i]})
# $FailoverServers = $arrTemp -join ","
Set-ManagementServer -AgentManagedComputer: $Agent -PrimaryManagementServer: $arrServerObject[$i] -FailoverServer: $arrTemp
$arrTemp = $null
$i++
}
Do these settings also apply to scom 2012?
Marius,
I just tried this on my scom 2012 infrastructure and works great. Took a minute for the console to update, so give it some time.
Thanks
I've just run this on SCOM 2007 and although the agent is now remotely manageable, the option to change primary management server is still not available.
Hi Kevin,
Now we are planning to do scom 2012 upgrade from scom 2007 r2 and enabled AD integration . therefore we need to move the agents to another MG server. In this case can you explain how to move the AD integrated agents to another management server
Thanks in Advance
I'm guessing this procedure is safe to use on SCOM 2012 if the QUERY returns a correct list of agents...but I can I get some confirmation that it is?
I can't see the GUID changing for 'BaseManagedTypeId' - but stranger things have happened.
Hi Kevin,
can i use this to break AD Integration? We don't won't to use AD Integration any longer. My idea is to run the script, remove Container in AD, apply CU4 to SCOM so that all Agents will be shown under pending management, update the Agents through the console. I think this should work, or not?
I think this is better than uninstall all Agents and then reinstall via console.
BR
Klaus