Windows 10 Upgrade Failed with Error code 0x80200056 while deploying from SCCM 2012 R2

Windows 10 Upgrade Failed with Error code 0x80200056 while deploying from SCCM 2012 R2

• Windows 10 Upgrade Pushed from SCCM can fail because of various reasons.
• You need to read the error code and understand it to further troubleshoot.
• One of the frequest errors i see while upgrade is Error code "0x80200056"
• This error means that there was some interuption while u upgrade the OS.
• Reason couble be user has switched off the Laptop,Or it got restarted because of some power issues, or Network got disconnected.
• To fix this instruct the user not to turn off or disconnect the PC from network till the upgrade is compelete.This should resolve the issue

Windows 10 Upgrade failed with error 0x80073712 while deploying from SCCM 2012 R2

Windows 10 Upgrade failed with error 0x80073712 while deploying from SCCM 2012 R2

• Windows 10 Upgrade is giving lot of issues.
• There are also lot of complains. One error i see while Deployement fails is with error code "0x80073712"
• This error indicates that there is issue with the file which is needed is damaged or missing.
• Mostly your ISO that you created is missing some files or is damaged.
• So make a fresh copy of ISO from Install media and try again
• This time it succeded without any errors.

SCOM Management Server showing warning with Event ID 1825 - A security package specific error occurred

SCOM Management Server showing warning with "Event ID 1825 - A security package specific error occurred"

• Today when i checked the SCOM management Server it was in Warning state.
• When i open the health explorer i could see only "Failed to access event log" is selected and its in warning state with error in details "A security package specific error occurred".
• When i tried to access the event log from the SCOM management server it failed with the same error.
• so i decided to do a nslookup of the server and found that the reverse lookup is pointing to the alias of the server rather then the actual server name.
• Once it was resolved things got health again.
• So when you have this issue, its usually issue with the DNS entries which needs to be fixed

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 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.

SCOM 2012 R2 Fatal error 1603 while installing Management Server

SCOM 2012 R2 Fatal error 1603 while installing Management Server

• I was today trying to install SCOM 2012 R2 on Windows 2008 r2.
• Everything seems to be going well and Pre requisite passed with flying colors.
• But while installing Management Server in the middle it failed with Fatal error 1603 and all got rolled back and installation was aborted.It asked me to refer the scom install log while which just gave the error 1603 Fatal error.
• After investigating some time found that there is 1 pre requisite which Microsoft missed to do.Probably a bug.
• Microsoft.NET 3.5.1 is mandatory. If this is not install it won't say any errors while you run the pre requsite. But.But in middle install will fail.
• So before starting the installation of SCOM management Server Go to Add/remove programs and click "add roles" and select "Application Server"    and install.
• This time the MS installation went through without any errors.

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

How to check and repair disk errors

In order to check and repair disk error you need to run CHKDSK command

• Click on Start --> Run
• Type Cmd
• Run CHKDSK /R

This will fix and repair you disk errors