How to successfully implement an SMS 2003 setup

To Implement an SMS 2003 architecture successfully in windows environment
we have to make sure we follow below steps

1. we have to satisfy all the prerequisite for Implementation of SMS 2003 server

2.Make sure we have separate user accounts for all the SMS agent for easy maintenance

3.should have sufficient hardware and network requirement to implement SMS 2003

we will see one by one all the steps required to implement SMS 2003 in other post.

Comments

Post a Comment

Popular posts from this blog

ConfigMgr 2012+ Version Numbers

Release Version Build Baseline D/L Link Our Guides SCCM 2012 RTM 5.00.7711.0000 7711 N/A N/A N/A SCCM 2012 RTM - CU1 5.00.7711.0200 7711 N/A KB2717295 N/A SCCM 2012 RTM - CU2 5.00.7711.0301 7711 N/A KB2780664 N/A SCCM 2012 SP1 5.00.7804.1000 7804 N/A N/A N/A SCCM 2012 SP1 - CU1 5.00.7804.1202 7804 N/A KB2817245 N/A SCCM 2012 SP1 - CU2 5.00.7804.1300 7804 N/A KB2854009 N/A SCCM 2012 SP1 - CU3 5.00.7804.1400 7804 N/A KB2882125 N/A SCCM 2012 SP1 - CU4 5.00.7804.1500 7804 N/A KB2922875 N/A SCCM 2012 SP1 - CU5 5.00.7804.1600 7804 N/A KB2978017 N/A SCCM 2012 R2 5.00.7958.1000 7958 N/A N/A Installation guide SCCM 2012 R2 - CU1 5.00.7958.1203 7958 N/A KB2938441 N/A SCCM 2012 R2 - CU2 5.00.7958.1303 7958 N/A KB2970177 Upgrade guide SCCM 2012 R2 - CU3 5.00.7958.1401 7958 N/A KB2994331 Upgrade guide SCCM 2012 R2 - CU4 5.00.7958.1501 7958 N/A KB3026739 Upgrade guide SCCM 2012 R2 - CU5 5.00.7958.1604 7958 N/A KB3054451 Upgrade guide SCCM 2012 R2 SP1 5.00.8239.1000 8239 N/A N/A Up
Read more

Steps to recreate WMI and Repair Corrupt WMI Services

WMI Error messages in execmgr.log file on SCCM clients   ·          Failed to open to WMI namespace '\.rootccmPolicyMachine' (8007045b) ·          Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace ·          Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy ·          Failed to connect to machine policy name space. 0x8007045b ·          Failed to connect to user policy name space ·          CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace ·          Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a ·          Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a ·          Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a ·          Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A
Read more

SCCM Software updates error WUAHandler.log errors

If you find errors in the WUAHandler.log as below "OnSearchComplete - Failed to end Search job. Error = 0x80072efd Scan failed with error = 0x80072efd" Error 0x80072efd means: 'The attempt to connect to the server failed. Can you check the following logs for more information "%Windir%\WindowsUpdate.log and ScanAgent.log Server not being able to talk to the WSUS server because port 8530 might be blocked lack of  communication  between the client and the SCCM sup if you are working with custom WSUS ports. Do not forget to open the used ports in the Windows Firewall Create a rule for inbound TCP (WSUS ports). In my case it was for 8530 and 8531. 
Read more