Content not Downloading to Distribution Point in SCCM 2012 R2

Content not Downloading to Distribution Point in SCCM 2012 R2

• SCCM is a very complex system.
• It hard to troubleshoot even with such exhaustive logging
• Reason is that the Mutiple issues on system can cause a side effect 
• So one of the frequent issue i face in my envionment is that the Content is not avaialble in Distribution Point.
• To resolve this the only effective solution i found is to reboot the server.
• So dont waste time investigating logs, as it will give 1000 varities of error
• As first step reboot the Distribution point server. 
• If you still have issues then you can troubleshoot with logs

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.

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2

Exchange 2010 MP not raising alerts after upgrading from SCOM 2007 to SCOM 2012 R2

• Recently we upgraded from SCOM 2007 to SCOM 2012, after upgrade we also migrated the MP's.
• Everything seems to work fine and after couple of days we got a call from Exchange team that they are not receiving Exchange 2010 related alerts.
• Exchange 2010 raises alerts based on correlation engine. So Correlation Engine decides when to raise an alert.
• So we immediately went and check on the RMS emulator server where the correlation engine was installed.
• We checked the "Application Logs" and there is lot of  Event ID 717 logged.
• When further investigated we found that the Exchange Correlation Auto alert resolution feature is failing because of which you see this Event ID 717.
• Looks like Exchange 2010 Correlation Engine is no longer compatible with SCOM 2012.
• To resolve this 
• We uninstalled the Exchange Correlation engine from Management Server (RMS emulator).
• We Installed Exchange Correlation engine on normal system which is not a Management Server.
• Then Stopped the Microsoft Exchange Monitoring Correlation service and Copied SCOM 2007 R2 SDK binaries into the Correlation Engine install directory %\Program Files\Microsoft\Exchange Server\v14\Bin. 
• Microsoft.EnterpriseManagement.OperationsManager.Common.dll
• Microsoft.EnterpriseManagement.OperationsManager.dll
• MomBidLdr.dll
• Start the Microsoft Exchange Monitoring Correlation and the alerts started flowing again.

SCOM 2012 R2 giving error Operations Manager Database Grooming not compelted Succesfully

SCOM 2012 R2 giving error Operations Manager Database Grooming not compelted Succesfully:

 

• You might get this error in your SCOM console and not sure what to do, lets understand what this alert means and work from there fixing this.
• So when you get this alert, first go and check your grooming settings to see how old alerts can be in SCOM operatoins Database, default is 7 days.
• Then create a view to filter alerts more than 7 days in closed state
• If you see more than 10000 alerts then your grooming is not working.
• Ok now how to fix it.Lets login to to the Operations Manager Database
• Open the query Window and run SELECT * FROM interaljobhistory order by interaljobhistoryid DESC.
• You can see 4 jobs with daily date updated, it will have a 0 or 1 net to it. If its 1 then its success.If its 0 then its failed.
• Now if the failed are more than1 then open the query windows and the run the Grooming Job manually EXEC p_groomingandPartitioning
• It will take long time some time close to 8 hours. If it succeeds then run the SELECT * FROM interaljobhistory order by interaljobhistoryid DESC and see if it succeded.
• If it fails the erro will tell you what the issue is. If its transaction log full error, then take a backup of your transaction logs and then run the above job.
• If the error is temb db full , then increase the space in temp db and try running the query again.
• If the error is LOCK error, then stop all the SCOM services on the managment server and then run the query and wait till it successeds.
• You also try changing the grooming settings .increase the number of days from 7 to 30 for all config in grooming settings and then run the job. If it succeds, the start reducing the days 1 day at a time and keep doing till it reaches optimum level.
• Another technique is to run just the failed jobs that you seel when you run the select query and see if it succeds. 

SCOM Agent is not installed but still showing in Pending State in SCOM 2012 r2-Resolved

SCOM Agent is not installed but still showing in Pending State in SCOM 2012 r2-steps to resolve

• We recently had a issue where there is no SCOM agent on the server.But When we try to Install SCOM agent from Console its says there is already agent pending to be managed and doesn't allow to install.
• Then when we check the pending agent state it shows up there ,but if i go and check the server there is no SCOM agent.
• So we where puzzled how its coming in pending management. Then we reject in pending management it goes from there.But if i try to install agent again it comes in pending management.
• So its stuck in pending management,So this time i rejected it and its gone from there.
• Then i Ran the Command shell command

               GET-SCOMPendingManagement | where {$_.AgentName -eq "FQDNServername"

• And the server was showing pending in command shell but not in console.
• To fix it you need to login to Operations Manager database server and run the below store procedue on query window on the operations manager database

               p_AgentPendingActionDeletebyAgentName 'FQDNServername'

SCOM Agent Uninstall error : The patch Package could not be opened

SCOM Agent Uninstall error : The patch Package could not be opened

• SCOM agent uninstall was always a piece of Cake. Jut right click and select uninstall from console

• But recently i was migrating from SCOM 2007 to SCOM 2012 and i have to uninstall SCOM 2007 R2 agents.Most went wellBut few failed with error

"The patch Package could not be opened. Verify that the patch package exists and that you can access it.Or contact the application support."

• First reaction was shocked. Haven't seen this error.I have access and all the msi to uninstall.

• Later i found out that issue is because of fact that the agent creates a reg entry of while installing with unique patch number.And if this conflicts or if there multiple of them then it will fail.

So to fix It follow the below steps,

• Click Start
• In Search type Regedit
• Click on HKEY_CLASSES_ROOT\Installer\Products\07779052F1B26F94BAD9C107B8
• Then double click on "Patches"
• Delete all the Values in it and Close it.
• Now go and try to uninstall it and it will work fine.

Get-GPO:How to Get list of Group POlicy in your EnviRornment using Powershell

Get-GPO:How to Get list of Group Policy in your Environment using Powershell

GET-GPO is a very powerfull Command.It gets list of all GPO in your Domain.

To get a list of all GPO, thep

GET-GPO

You will get the below error

PS C:\Users\foxsha> GET-GPO

The term 'GET-GPO' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spe

lling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:8

+ GET-GPO <<<<

    + CategoryInfo          : ObjectNotFound: (GET-GPO:String) [], CommandNotFoundException

    + FullyQualifiedErrorId : CommandNotFoundException

The reason for this error is that there is no Module Available for Active Directory

So first Import the Module using Command

Import-Module "grouppolicy"

You will see the below error

PS C:\Users\foxsha> Import-Module "grouppolicy"

Import-Module : The specified module 'grouppolicy' was not loaded because no valid module file was found in any module

directory.

At line:1 char:14

+ Import-Module <<<<  "grouppolicy"

    + CategoryInfo          : ResourceUnavailable: (grouppolicy:String) [Import-Module], FileNotFoundException

    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

The resaon for this error is that there is no Group policy Feature installed so first we need to install the group policy features

If you are on your desktop and not on Server,you need to go to below location and download and install it

http://www.microsoft.com/en-us/download/details.aspx?id=7887

Then go to Programs and Features in Control Panned .Click "Turn Windows Feature On or OFF " and select "Group policy management"

Now try " Import-Module "grouppolicy" and then GET-GPO and it will run sucesfully