SCCM Solve child site replicaton problems

If you look at the replication logs I posted yesterday but still can’t understand why child site is not accepting packages from Central site.

If you get Errorcodes and errors about cetificates not valid for some packages etc but you have solved the public keys and done everything by the book then you have one more thing to try.

Disconnect Child site from Central parent site  and wait a weekend then reconnect it and re-replicate all packages. This solved a corrupted replication for me a couple of times.

Repair broken or corrupt WMI

When SMS or SCCM agents fails to install it’s often due to broken or corrupt WMI database. Recreating WMI database is not a good way to solve it since other applications might have stored configuration and values there.

So, I have written together a set of commands which fixes WMI problems in most cases without need of rebuilding whole WMI.

Open an administrative CMD Window and run these commands.

msiexec /unregister
msiexec /regserver

rundll32 wbemupgd, RepairWMISetup
Restart the “Windows Management Instrumentation service”

Change directory to %windir%\System32\WBEM
(\SysWOW64\WBEM on x64)

Then run these FOR loops:
FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
Net stop /y winmgmt
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Net start winmgmt

Now, try to install the SMS or SCCM agent again.
If it still fails, reboot and try agent installation once more.

Technorati-taggar: ,,,,,

SCCM Investigate package replication problems

Connect with RDP or Console to Parent and Child site servers.

Install Trace32.exe from SMS2003 toolkit (Installation is easy, copy it into %Windir% and start it). With Trace32 you can look at the log’s without locking them and they also update on the screen when there are changes in them. Excellent tool which you must have as SCCM specialist.

Open all below log files and put them up so you see them all on both child and parent RDP window.

Parent: Sender.log, Replmgr.log, Objreplmgr.log
Child: Despool.log, Replmgr.log, Objreplmgr.log, Distmgr.log

In console, update the distribution point that is not updating, look for errors in the logs..

SCCM Child site out of sync

Use below command from Central SCCM site server to force a full sync of  child site that is having problems.

<SCCM folder>\i386\00000409\preinst.exe /syncchild <child sitecode>

If child keeps getting out of sync, start investigating replication logs, see separate post.

SCCM sites in different AD Forrest, public keys!

If you have added the correct sender accounts in our hirarchy and you still can’t get the replication to work between sites? Public keys can make a mess when site servers try to communicate between forests since they do not share the same AD objects but I have found a solution!

1. Use “preinst.exe” to fix this problem.
2. Export the keys in both child and parent.
3. Copy the exported files according to the help text.
4. Restart Hierarchy Manager
5. Check hman.log

Prenumerera på: Inlägg (Atom)