Setting up SCCM Environment
All, I'm in the middle of setting up a new SCCM environment. Here's what has been done so far. - Installed WIN2K3_x64 on a brand new server. Installed and configured. Tied into AD, etc etc. - Installed SQL2K5, configured. Not too much since this will be a dedicated SQL server for SCCM. - Installed IIS 6.0, BITS, enabled WEBDAV, ASP. - Installed SCCM. Everything ran fine during the predeployment checks. So everything seemed to work fine. - Attempting to set up all the server roles, MP, SLP, etc etc, pretty much all of them since this will be the main and only SCCM server, central site, etc. - Looked at the system status, errors everywhere. I looked at the event viewer, and pretty much every role that the SCCM is supposed to be doing, each of the system role installations failed out. MP, SLP, etc. All the installations failed with 80020009 errors. When I was in the ConfigMgr console, and tried to go through the System/Service Manager, I queried each component, and they all came back with "Failed to communicate with component". I read all the logs concerning with each of the role installations, and they all show the same 80020009 error message. I tried to copy and paste the command line, errored out. I tried to run the command by itself, errored out. Try to run the command from the SCCM DVD, failed. Thoughts??
April 1st, 2010 6:19am

Hi, You should not run the msi files directly from the DVD, I don't think that will help you. Do you have any errors in the sitecomp.log file?Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2010 9:04am

anything specific i should be checking for? i know specifically, each of the *.msi files all fail with that specific error code. but i think that may be a general error? Could you please let us know what the error code is?
April 2nd, 2010 5:55am

Any reasons for this?
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2010 5:01am

Error 401 = unauthorized. So double check the IIS logs to get an idea where exactly it is failing.
April 6th, 2010 10:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics