New Secondary site Not reflecting in Primary Site

Issue

New Secondary site not replicated to Primary Console. The site has not been shown after an extended wait.

Resolution
(Note: – Please use the below solution after all the prerequisite check)
Log on your Secondary SCCM Site server,
Copy the file \inboxes\sitectrl.box\SiteCtrl.ct0 file to a temp location,
Rename it to 00000000.ct2 and
Copy the renamed file to Primary SCCM Site Server \inboxes\hman.box\

Wait for couple of hours and check.

Posted in Troubleshooting | Tagged , , | Leave a comment

Daily, weekly and monthly maintenance task for SCCM server

Daily Maintenance Tasks

Performing daily maintenance is important to ensure proper site operations.

 A daily maintenance log should be maintained to document dates that maintenance was conducted,

 By whom, and any maintenance-related comments about the task conducted.

Common Daily Maintenance Tasks

·   Verify that predefined maintenance tasks scheduled to run daily are running successfully. 

 ·         Check Configuration Manager 2007 site database status.

 ·         Check site server status.

 ·         Check Configuration Manager 2007 site system inboxes for backlogs.

 ·         Check site systems status.

 ·         Check client status.

·         Check the operating system event logs on site systems.

 ·         Check the SQL Server error log.

 ·         Check system performance.

Weekly Maintenance Tasks  

Performing weekly maintenance is important to ensure proper site operations. A weekly maintenance log should be maintained to document dates that maintenance was conducted, by whom, and any maintenance related comments about the task conducted.

 

Common Weekly Maintenance Tasks

  ·     Verify that predefined maintenance tasks scheduled to run weekly are running successfully.

 ·      Delete unnecessary files from site systems.

·       Produce and distribute end-user reports if required.

·       Back up application, security, and system event logs and clear them.

·       Check the site database size and verify that there is enough available disk space on the site database server to allow the site database to grow.

 ·     Perform SQL Server database maintenance on the site database according to your SQL Server maintenance plan.

 ·    Check available disk space on all site systems.

 ·    Run disk defragmentation tools on all site systems.

 Periodic Maintenance Tasks   

Performing periodic maintenance is important to ensure proper site operations. Some tasks do not need to be performed during daily or weekly maintenance, but are important to ensure overall site health and security and disaster recovery plans are up to date. A periodic maintenance log should be maintained to document dates that maintenance was conducted, by whom, and any maintenance related comments about the task conducted.

 Common Periodic Maintenance Tasks

·    Review the security plan for any needed changes.

 ·  Change accounts and passwords if necessary according to your security plan.

 ·   Review the maintenance plan to verify that scheduled maintenance tasks are scheduled properly and effectively depending on configured site settings.

 ·  Review the Configuration Manager 2007 hierarchy design for any needed changes.

 ·   Check network performance to ensure changes have not been made that affect site operations.

 ·     Verify Active Directory settings affecting site operations have not changed. For example, you should ensure that subnets assigned to Active Directory sites used as boundaries for a Configuration Manager 2007 site have not changed.

 ·   Review the disaster recovery plan for any needed changes.

·   Perform a site recovery according to the disaster recovery plan in a test lab using a backup copy of the most recent backup snapshot created by the Backup ConfigMgr Site Server maintenance task.

 ·   Check hardware for any errors or hardware updates available.

·  Check overall health of site.

 REF : http://technet.microsoft.com/en-us/library/bb632564.aspx

REF: http://prakaash2109.wordpress.com/2012/08/17/dailyweekly-montly-maintenence-tasks-in-sccm-server

 

 

Posted in Uncategorized | Tagged | Leave a comment

Patches getting reoffered from SCCM

Patches getting reoffered from SCCM and Windows update even after they are successfully installed.

Issue:

.NET Framework Security updates like kb2418241 and KB2656352 get reoffered on distribution tools like SCCM and Windows Update even after they are installed successfully. In this scenario the files which are targeted by the security updates are updated to the intended version and the security update is populated in the Add/Remove programs.

Cause:

This is due to an orphan registry key “HKLM\Wow6432Node\Microsoft\Update\Microsoft .NET Framework 2.0\SP2\kb960043”. KB960043 determines if the patch servicing for .NET Framework is following a LDR or GDR line of patching (Refer the KB for more information http://support.microsoft.com/kb/960043). The above mentioned orphan registry key would be left over due to a previous unclean uninstallation of .NET Framework or KB960043.

As per the security update detection methodology SCCM or Windows update would check for the file versions after the security updates are installed and then confirm if patch has been successfully installed or not. In this scenario KB960043 is not installed on the machine and the security update has updated the files to GDR version. SCCM detects that “HKLM\Wow6432Node\Microsoft\Update\Microsoft .NET Framework 2.0\SP2\kb960043” on the machine and assumes LDR line of patching is being followed on the machine. It would verify if the LDR version of files are installed on the machine but actually GDR version are installed on the machine. This version mismatch misleads SCCM and it would reoffer the patch again showing the status as failed.

Resolution:

We have to delete the orphan registry key “HKLM\Wow6432Node\Microsoft\Update\Microsoft .NET Framework 2.0\SP2\kb960043-V3” and try reinstalling the security update. After this it wouldn’t be reoffered.

PS: This registry path is for 64 bit machines. For 32 bit machines the path would be “HKLM\Microsoft\Update\Microsoft .NET Framework 2.0\SP2\kb960043-V3”

 

taken from :- http://blogs.msdn.com/b/vsnetsetup/archive/2012/10/07/installation-of-vc-2005-2008-fail-with-0x80070005-assembly-error-access-is-denied-issue.aspx

Posted in Troubleshooting | Tagged , | Leave a comment

preinst.exe /syncchild ABC Not a known site

Sometimes, when you try to sync your child site using preinst command you may get a message ABC not a known site.  This will happen due to improper removal of the site.

Follow the below steps to resolve the same. most of the cases it works. (Modify the SQL tables on your own risk, have a correct back up of DB before any changes to DB)

Delete the site associated tables using the below query

delete from sysreslist where sitecode = ‘ABC’
delete from siteboundaryadsite where sitecode = ‘ABC’
delete from siteboundaryipsubnet where sitecode = ‘ABC’
delete from sitecontrol where sitecode = ‘ABC’
delete from sitecontrolnotification where sitecode = ‘ABC’
delete from sites where sitecode = ‘ABC’
delete from sites_data where sitecode = ‘ABC’
delete from sitework where sitecode = ‘ABC’
delete from pkgservers where sitecode = ‘ABC’
delete from pkgstatus where sitecode = ‘ABC’
delete from contentdpmap where sitecode = ‘ABC’
go

After executing the above query, copy the sitectrl.ct0  from child to parent server desktop and rename the same to sitectrl.ct2 and past it in Hman box of parent. this will add the chid site back. keep a watch on Hman.log at parent for any errors.

Posted in Troubleshooting | Leave a comment

Package showing install Pending in Primary

(Don’t implement this solution without knowledge of SQL)

ISSUE

Package state displayed as installed in Central and install pending in Primary site. [This issue can randomly occur in larger SCCM environments with large packages and slow WAN links]

Solution

Login to Central Servers and execute the below commands.

Fist command to identiy the packages

select*from PkgStatus

where ID like‘Package ID’

Modify the PackageID, Site code, and server name and execute below command (use the first command output to fill the above details)

update pkgstatus setstatus= 0

where id =‘PackageID’

and sitecode =‘SiteCode’

and Pkgserver =‘ServerName’

Modify the PackageID, Site code, and server name and execute below command (use the first command output to fill the above details)

update pkgstatus set SourceVersion = 0

where id =‘PackageID’

and sitecode =‘SiteCode’

and Pkgserver =‘ServerName’

Now the source version has been changed to 0, so that in the next refresh cycle all the Package version will be deployed to this server.

 Go to central console and refresh the Package for this DP, and observer the log (approximate time for package process required is at least 1 hour)

 

Posted in Troubleshooting | Leave a comment

SQL Query to check when collection were updated

Hi

Use the below Query to check, when the collections were updated in SCCM 2007

Select

 CC.CollectionID,

CN.CollectionName,

Convert (VarChar(10), CC.TimeUpdated, 101)‘Last Updated’

From

Collection_MemberChg_Notif CC

Join Collections CN on CC.CollectionID = CN.SiteID

Order By [Last Updated] DESC

Posted in SMS Query | 2 Comments