Showing posts with label System Center Configuration. Show all posts
Showing posts with label System Center Configuration. Show all posts

Monday, November 16, 2015

Failed to sync update fc5e8c16-7b3b-409f-8e42-5ffb3c1cf09d WSUS Synchronization failed with SCCM.

Today I faced a problem with WSUS Synchronization the update on SCCM.
This problem was annoying me. I can sync my WSUS db from Microsoft ok. But for some reason I am getting this error in SCCM.
Failed to sync update fc5e8c16-7b3b-409f-8e42-5ffb3c1cf09d. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted
It prevents my scheduled sync from passing and then it attempts to re-sync every 60 mins.
That above issue is known for MS and it’s often.
To resolve that issue you should have to run the following command on the WSUS server.
At the command line %drive%\Program Files\Update Services\Tools>, type:
Wsusut reset

Once you run the above command after that start the synchronization once again and you will see the synchronization.

Friday, January 3, 2014

Improve the performance of PXE boot


To improve the PXE boot we have to enable/add a registry value in DP where PXE is enabled,

From the distribution point (where you enabled PXE) complete the following

1.        Open regedit and locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

2.        Add a QWORD value and call it RamDiskTFTPBlockSize

3.        Give it a Hexadecimal value of “4000″

Friday, November 8, 2013

Installation Prerequisite Check for ConfigMgr 2012

One day I was installing SCCM 2012 secondary site, I had installed SQL express on local machine because from CM12 primary site it install on C drive,
Error when doing the Prerequisite installation checks Likewise “Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.”
And “The logon account for the SQL Server service cannot be a local user account or LOCAL SERVICE. You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM;”
 
 
Both errors were normal but I was sure I have configured correct domain account for local service, and installation account was configured as the sysadmin server roles in SQL.
After that I did, went to services and again I have reconfigured the same domain account and did stop the service and start the service of SQL server,
And SQL Agent service was by default disabled, I made this enable and automatic.
Then again I did the Prerequisite installation checks and now this time all went pass.

Saturday, October 26, 2013

Deploy list is not synching with child site

I faced an issue could of month back, deploy list is not synching with child site,
 
here is the solution how to resync and update the deploy list.
 
 
1-Failed to insert Object 6298a02f-0a6a-4f34-b832-08059b682b63 from replication file d:\Microsoft Configuration Manager\inboxes\objmgr.box\INCOMING\RetryGL_48796.CID.
On to the resolution, I found that running the following 6 SQL queries on the effected child sites resolved the issue:

Delete from CI_ConfigurationItems Where CIType_ID in (1, 6, 8);
Update CI_SDMPackages set IsDeleted = 1 where SourceSite = 'CEN';
Delete from CI_ComplianceHistory where isdetected = 1
Delete from CI_Compliancehistory where isdetected = 0
Delete from CI_SDMPackages where is deleted =1 and sourecesite = 'CEN'
Exec sp_DeleteOldSDMPackageData 0;

* Note: replace CEN with the site code of your central site (or the active SUP which is the furthest upstream’)
Running the above queries will purge Software Updates data from the effected child site.
You should then wait about 30 minutes and then restart the following services on the effected child site:
SMS_EXECUTIVE
SMS_COMPONENT_MANAGER
The final step is to initiate a full site replication, this can be done using the hierarchy maintenance tool (syncchild option) or by place a file called .SHA * in the objmgr.box on the parent site.
* .SHA – replace with the 3 digit site code of the desired child site you wish to replicate.
Allow up to 24 hours for the site replication to complete, when it finishes you should have a fully matching compliment of updates on the central site and child primary site.
 
 
2-If above method is not working then no problem, you would have to follow following steps as well as you followed first steps,
 
1.    In child site, delete all files inside objmgr.box, objmgr.box\INCOMING, objmgr.box\INCOMING\retry & objmgr.box\INCOMING\retry\Bad.
2.    Run below SQL query to clean the updates information from child site DB.
 
We need to run a clean-up process using the below SQL query.
================================
BEGIN TRANSACTION
 
DECLARE @SiteCode varchar(8)
DECLARE @RowCount int, @Err int, @TotalRowCount int
SELECT @SiteCode=ThisSiteCode from SMSData
 
PRINT N'Step 1 - Deleting the update sources'
 
delete from CI_UpdateSources where UpdateSourceName = 'WSUS Enterprise Server'
 
PRINT N'Step 2 - Deleting rows of type 1 and 6'
 
delete CIR from CI_ConfigurationItemRelations CIR
left join CI_ConfigurationItems cci on cci.CI_ID = CIR.FromCI_ID
where cci.CIType_ID in (1, 8)
 
delete CIR from CI_ConfigurationItemRelations CIR
left join CI_ConfigurationItems cci on cci.CI_ID = CIR.ToCI_ID
where cci.CIType_ID in (1, 8)
 
set rowcount 1000
 
delete from CI_ConfigurationItems Where CIType_ID in (1) and SourceSite <>
@SiteCode
SET @TotalRowCount=@@RowCount
 
IF @@ERROR!=0 GOTO exiterror
 
while (1=1)
begin
Delete from CI_ConfigurationItems Where CIType_ID in (1) and SourceSite <>
@SiteCode
SELECT @RowCount=@@ROWCOUNT, @Err=@@ERROR
SET @TotalRowCount=@TotalRowCount + @RowCount
 
IF @Err!=0 GOTO exiterror
IF @RowCount = 0 break
 
PRINT N'Looping... Rows deleted so far:'
PRINT @TotalRowCount
end
 
PRINT N'Step 3 - Deleting rows of type 8'
 
set rowcount 1000
 
delete from CI_ConfigurationItems Where CIType_ID = 8
SET @TotalRowCount=@@RowCount
 
IF @@ERROR!=0 GOTO exiterror
 
while (1=1)
begin
Delete from CI_ConfigurationItems Where CIType_ID = 8
SELECT @RowCount=@@ROWCOUNT, @Err=@@ERROR
SET @TotalRowCount=@TotalRowCount + @RowCount
 
IF @Err!=0 GOTO exiterror
IF @RowCount = 0 break
 
PRINT N'Looping... Rows deleted so far:'
PRINT @TotalRowCount
end
 
PRINT N'Step 4 - Running the SP...'
 
set rowcount 0
update CI_SDMPackages set IsDeleted = 1
where SourceSite is not NULL and SDMPackageName not like 'ScopeID%' and
SDMPackageName not like '%GLOBAL%'
IF @Err!=0 GOTO exiterror
 
exec sp_DeleteOldSDMPackageData 0
IF @Err!=0 GOTO exiterror
 
GOTO exitok
 
exiterror:
 
PRINT N'Error:'
PRINT @@ERROR
 
exitok:
set rowcount 0
 
if @@ERROR = 0 COMMIT TRANSACTION else ROLLBACK TRANSACTION
================================
.
1.    Stop SMS Executive and Site component manager service on Child site.
2.    On the child site navigate to <SCCM installation drive\location>\Bin\i386 rename the DLL -> objreplmgr.dll to objreplmgr.dll.old
3.    Start the Site component manager service on Child site, SMS Executive service will be started automatically by site comp service.
 
4.    Force a resync of the updates data objects by dropping a <childsitecode>.sha file into the Central site's
5.    Once the SHA file disappear, wait for 1 – 2 hour and proceed with next step.
6.    Stop SMS Executive and Site component manager service on Child site.
7.    On the child site navigate to <SCCM installation drive\location>\Bin\i386 rename the DLL -> objreplmgr.dll.old to objreplmgr.dll
8.    Start the Site component manager service on Child site, SMS Executive service will be started automatically by site comp service
 
 
 

Tuesday, October 8, 2013

Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager

Today Microsoft released a new KB targeting problems with the Install Software Updates hanging when you use the Install Software Updates step in a Task Sequence. This issue has been around since Configuration Manager 2007 and is still an issue in Configuration Manager 2012 with some updates.
Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager“ 
The KB article is applicable both to Configuration Manager 2007 and 2012. Keep an eye on the KB above as it will be updated with more updates as they are reported, that will save a lot of troubleshooting time!
Symptoms:
“If a Configuration Manager Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, the task sequence can fail to complete successfully.”
Cause:
The first reboot initiated by the software update is properly controlled by the Task Sequence. However the second reboot request is initiated by a Windows component (typically Component-Based Servicing) and therefore not controlled by the Task Sequence.
Resolution:
“To resolve this issue, it is recommended that any updates that require dual reboots be applied using the normal Software Updates feature of Configuration Manager instead of Task Sequences. The following software updates have been reported as requiring multiple reboots. This KB will be updated as more updates are reported.

Tuesday, November 27, 2012

Troubleshooting Software Updates Client Issues SCCM




1-Client Scan Fails with Error 0x80040693

In the Microsoft System Center Configuration Manager 2007 console, view any reports in the category Software Updates - Troubleshooting. If a Configuration Manager 2007 client reports the error code 0x80040693, it means the client is running the wrong version of Windows Update Agent (WUA). Configuration Manager 2007 clients require version 7.0.6000.374 or higher.


Possible Solution
If client computers are configured for Automatic Update, they should automatically update their Windows Update Agent from their Automatic Update source. If clients are not configured for Automatic Update, you can locate the WUA redistributable file wuredist.cab on MSDN and deploy it using Configuration Manager 2007 software distribution.


2-Software Update Installation Fails with Error 0x80091007

Before a Configuration Manager 2007 client can install software updates, it verifies the hash on the content containing the software update. If the hash does not match, the client fails to install the software update and logs error 0x80091007 to the updatesdeployment.log on the client. The error is also sent to the management point and is visible in the reports under the category Software Updates 
Troubleshooting.
This issue is often caused by having the wrong version of the package on the distribution point. Frequently this issue occurs when content has not been replicated to a child site or when the package version has changed but the client has not received new policy yet.


Possible Solution

In the Configuration Manager 2007 console, navigate to System Center Configuration Manager ,Site Database, Computer Management,  Software Updates, Deployment Packages, Package Status, Package Status, and look at the source version for the package. Verify that all distribution points are using the same source version, including any distribution points at the child site. You can also look at distmgr.log for any errors that reference the package ID.


3-Software Update Installation Fails with Error = 0x80004002

A client computer fails to install a software update with the 0x80004002 error message reported in the client log files, such as the following sample log entries:
UpdatesHandler.log
WSUS update installation result = 0x80004002, Reboot State = NoReboot
Update execution failed.
WUAHandler.log
Failed to get final installation result of updates. Error = 0x80004002.
Update 1 () finished installing (0x80004002).
Update 2 () finished installing (0x80004002).
Installation of updates completed.
WindowsUpdate.log
WARNING: client failed installing updates with error 0x80004002
The UpdatesHandler.log and WUAHandler.log files are located in Logs, and the Windows Update.log is located in windir.
Possible Solution
The WUA installation on the client might be missing files or be corrupt. Reinstall WUA 3.0 on the client computer. For more information about installing WUA 3.0, 

Thursday, July 8, 2010

How to install Microsoft System Center Configuration Manager 2007 for secondary site:

The best practice for Install configuration server, you should check perquisite site components are ok or not, if there is no error then you can go ahead.
Step-1: then click on Configuration Manager Console in Install section which is available middle when you click on SPLASH.HTA.
After that click on next, then tick on Install a configuration Manager Site server as figure no 1:

Then click next.after that choos sceondary site option then click next, the click choss the defaulter option for installation of Manager console
Again you have to click next.After that enter the 3 digit of site code (as figure 2) which you want to assign for Secondary site.
The site code will be used to uniquely identify this configuration Manager site in your hierarchy.

Then again click next.
Specify the setting for the confgMgr primary site that the secondary site will report to. Click next.In the next step setup will install the latest version of the perquisite if they are available, so tick on check for update and download.click next. Then in next step Type the alternate path where you want to download perquisite component.
After that setup will check installation problem, if installation problem will found then setup will display how to resolve this problem. And click begin install.

After clicking next installation will complete.After that installation will be finish. Then you have to install Administration console:

In next step enter the name of the server that you want to configur Manager Console to connect to when you first run this program.then click next.

In next step setup will check for potaincial installation problem, if installation problem are found setup will display, detail about how to resolve this problem.
Click next then accept the licence agreement, then click next, in the next step choos the no, I do not want to participate right now, again click next to install in the defaulter folder click next.
After that click on begin install then click next after that console will install in your sceondary server.

PXE Issue after SCCM CB 1806 upgrade

Recently i had upgraded my SCCM environment 1806 and after upgrade suddenly all PXE servers stopped working. While initiating the PXE ...