Monday, October 27, 2014

Agent Installation Error (Error Code : 80072971)

At times,we might experience another frequently seen error as below, where the agent management task status displays something like “….failed to acquire lock to remote computer….”

image 

This is due to when SCOM agent is pushed from the SCOM Management Server, the MS will first copy the install (& the patches) to the target machine at c:\windows\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2 folder, and if you managed to browse to the folder,there should be a file named LockTimeFile. This file is to determine which SCOM MS is attending the target server at the moment.

By default, once the installation is completed, the folder will be automatically deleted when the installation completes, however there is changes that the folder / files are not successfully removed.

image

In order to resolve this, one of the way is to delete the LockTimeFile and the SCOM agent was successfully installed

Wednesday, October 8, 2014

SCOM SharePoint 2010 MP troubleshooting

Encountered the following error message in SCOM event viewer for one of the SharePoint 2010 servers. Searching around the net, found 2 links with valuable information on resolving it.

http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/

http://thoughtsonopsmgr.blogspot.com.au/2013/04/troubleshooting-sharepoint-server-2013.html

Basically it seemed might have to do with PowerShell 3.0 (for Sharepoint 2010), and one of the solution was to uninstall the PowerShell 3.0, but before doing so, you might want to verify it further by granting the SCOM SharePoint MP account to have SP farm admin rights, to see if it is able to launch the SP cmdlets.

Hope this helps :)

Friday, September 19, 2014

Failed to capture windows 8 reference image via SCCM 2012 R2 capture media

Had recently started to play around with SCCM 2012 R2 and wanted to explore more on OSD and task sequencing. Tried to capture a Windows 8 image after i had set it up with latest updates, it failed when the capture media was inserted and TSMBAutorun.exe was executed.

As expected, once the sysprep commands are completed, the machine will be rebooted the capturing should start. In this case, it didn’t and went into “sysprep” mode whereby i was asked to personalize the windows 8 again.

Tried asking around and this seemed to have to do with the RAM allocated (mine was a VM, running on dynamic RAM 512 – 1024).

What i did next, shut down the VM, set the RAM to be static 2GB and run the capture media again, and voila…. it works. :)

many thanks to my fellow MVP for this similar blog post here

Monday, August 25, 2014

Agent Installation Error (Error Code :80004005)

Faced a problem recently when trying to upgrade the version of the SCOM agent to the latest 2012 R2.
Error message is similar to the below
The Operations Manager Server could not execute WMI Query "Select * from Win32_Environment where NAME='PROCESSOR_ARCHITECTURE'"
Operation: Agent Install
Install account: <SCOM runAs>
Error Code: 80004005
Error Description: Unspecified error
This is due the 'PROCESSOR_ARCHITECTURE' variable, does not return a value, which causes agent push to failed. (the manual installation seemed to work though) Checking on the web and it does not seemed to have a permanent solution, however, there is a workaround which should help to complete the agent installation via push method. Many thanks to stefanroth.net for such sharing