" Distribution Manager failed to install distribution point "
Now , the issue would be due to a number of things . Let us start to troubleshoot it from the start . You first step is to have a look at the distmgr.log file . Below is the snapshot of the distmgr.log file .
The screenshot clearly states that Dp files have not been installed . Now if you check the asset Message , you will see the below error :
It says that "Distribution Manager failed to install distribution point" . If we can try and drill down further go to the Application Log onto the server and you will see something like the below ( atleast in my case , this may vary ) :
As you may see that the application log gives us a more specific error as to User Rights . It is normally a good practice that you add the account that is being used for Distribution Point Installation on to the Local Admin group on the Distribution Machine . This would solve the issue for you in this case .
However , If this does not solve the issue and you are creating the Distribution Point on a windows 7 Machine , check for the below things :
IIS 6 WMI compatibility Feature
IIS 6 Management compatibility feature
Technet also , gives its specification/ pre Requisites for Distribution Point Installtion :
You can use the default IIS configuration, or a custom configuration.
To use a custom IIS configuration, you must enable the following options for IIS:
- Application Development:
- ISAPI Extensions
- Security:
- Windows Authentication
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
When you use a custom IIS configuration, you can remove options that are not required, such as the following:
- Common HTTP Features:IIS Management Scripts and Tools
- HTTP Redirection
I have been getting a lot of queries over Email from the readers . I would appreciate if you can post your queries directly on the blog . This would help me a lot as my Mailbox is almost full :-)
Thanks in advance
As we All Know that SCCM has Various Methods of Discovering Users , systems , Groups , Forest ( Something new in SCCM 2012 ) . Today we will take up SCCM User Discovery .
An In depth Insight :
___________________________________________________________________________________________
Let us have a look at the SCCM User Collections . Clearly in Fig 1 , we can see that there is No user in the User Collection .
At the same time if we have a look at the logs Folder , We may see that there is No log which corresponds to User Discovery in SCCM . Fig 2
As we move onto the Discovery Methods we find out that User Discovery has been Disabled in SCCM . Fig 3
Now , Just Double Click the User Discovery Method and Enable it , Giving the Proper Container for it as shown in Fig 4 and Fig 5
Once this is done Click on Ok.
Right Click on the User Discovery and Click Run Full Discovery . Fig 6
Click yes .
Now , Go to the Logs folder and you will see Adusrdis log being shown up there . Fig 7
Now , Open this log with the help of CM Trace Tool ( In case you have not installed it , Go to the SCCM Install Directory > Tools > CMTrace ) . The very First thing that you will see is User Discovery Component Setting was set to Active in the SCCM Control File . This is very Important thing to note . For any discovery to work it has to be active in the Control file . Fig 8
Once you see this , SCCM keeps on discovering Users and keeps creating DDR's for them . Fig 9 and Fig 10
Finally , You can see the user Information being populated in the SCCM Console :
Those who are looking to change job in SCCM may send resumes to sccmabheek@gmail.com
Those who wish to Learn this wonderful tool may use the below Links to MS Free vIrtual Labs :
Ask any SCCM Designer / Architect !! How Many Distribution Points you need in this Environment and he would bend his head and do zillion odd Calculations :-)
With this Post I intend to share a Table which shows how much time is required over a specific WAN link for a set of PC's :
The Below Table Shows the Approximate results for 1 Single Machine over WAN and LAN . From the results it is very clear that for Distribution Point the results are better
* Note : The figures mentioned above are approximate . Actual s may vary a little .
Now , Let us see the results for 50 Machines at a Local Branch with Different Bandwidth Options . Clearly you would see that if we are not going to use a Local Distribution Point then deployments like Operating system would choke the network and would a lot of time .
As you can see from the above Image , if we have a 2 MBPS line between the Primary server and the Local branch and there is No distribution Point ( Local ) , them for a set of 50 machines at such a location would take 200 hours for getting the OSD files . However , if we have a Local Distribution Point at the Branch Location , Machines would pick the Image over a LAN and it would just take 3 Hours of time . That's the power of a Local Distribution Point .
** The Calculations above are based on the assumption that all the bandwidth is available to SCCM .
It is also important to understand that the Traffic between Primary and Distribution Point can be scheduled and Throttled .
Those Interested for SCCM Training can send in the details at sccmtrainings@gmail.com
In this Post , You will learn on how to Migrate SCCM 2007 to SCCM 2012 . Although the Actual Environment would be a more Complex Scenario but the Underlying steps remain the same .
Before we Migrate , I will give you a brief about the Environment in which this Migration has been Performed ( It is Based on MS Virtual Lab ) with One SCCM 2007 Primary Site Being Migrated to SCCM 2012 Central , There is One Primary Site and One Client which is Finally Upgraded to SCCM 2012 From SCCM 2007 .
It Should be Noted that there is no Direct Method of Migration but the only way to perform Migration is a Side by Side Migration , Which Involves Specifying Source Hierarchy , Migrating Collections , Packages , OS Images , Etc .
Very First step is to Specify the Source Hierarchy on the SCCM 2012 Central Site . For this you Need Access to Account which has read Access to Objects in SCCM 2007 Environment and Server .
After the Account has been Specified , Check the test Connection .
Keep Checking IF SCCM Set up is running on Client Machine . After some time you will see Configuration Manager and find that all information is gone and New information is Populated .
Posts
All Comments
© 2013 Learn IT " The Easy Way " . All rights resevered. Designed by Templateism
