Jump to content


tymque

Established Members
  • Posts

    7
  • Joined

  • Last visited

About tymque

  • Birthday 03/13/1980

Profile Information

  • Gender
    Male

tymque's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. WAIT!!!! I take that back! Omg.. what a .... ugh, simple mistake that was. [smashing keyboard] I see that a few clients are starting to become assigned and automatically being approved! IT'S ALIVE! Well, thank you so much for helping me and pointing that out. I've gone over this so many times that I was assuming the problem was much larger and out of my realm. Should have remembered to look for something simpler. Thanks again! You guys are the greatest. Rebecca
  2. Ah.. Alright. [click, click, click] I've installed R2 and SP2. [slept a few hours] Same issue..
  3. I just verified the schema has been extended on the domain controller. http://technet.microsoft.com/en-us/library/bb693614.aspx
  4. Wow, what a nightmare I'm having with SCCM. Not with the program but with random other things on our network that are causing issues. I "think" my current issue may directly be related to a network issue such as DNS or something, hopefully someone will have some advice for me! Upgraded from SMS to SCCM deleted everything I could find relating to the old SMS server in AD. All of the new clients are able to discover the new SCCM server but can not register. I have to manually put in the new site code. They can ping the server, under DNS the server name is correct, when I type in the server name under a web browser I can get the cert and mplist. I've checked all of the log files on the SCCM server, MP has been installed successfully (MPsetup, mpMSI), I've checked all the components which are running correctly (stopped, restarted) Current Setup: ------------------ Server 2008 R2 (virtual) SCCM SP1 SQL 2005 II7 (Mixed Mode) (Firewall turned off) Schema has been extended on primary domain controller, do I need to extend it on all the domain controllers though? SLP is configured anyways SCCM is reporting back that everything was successful.. My current issue is that none of my clients are able to register with my SCCM server. On all of the client workstations I'm getting these error messages: (CcmExec.log) <![LOG[[CCMHTTP] HTTP ERROR: URL=http://DELGADO.AD.ENGR.WASHINGTON.EDU/ccm_system_windowsauth/request, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="22:39:01.999+480" date="03-11-2010" component="CCMEXEC" context="" type="1" thread="4256" file="ccmhttperror.cpp:264"> <![LOG[Raising event: instance of CCM_CcmHttp_Status { ClientID = "GUID:8B1BBEFC-8E56-462A-8168-5F2ACE3117CD"; DateTime = "20100312063902.124000+000"; HostName = "DELGADO.AD.ENGR.WASHINGTON.EDU"; HRESULT = "0x80072ee7"; ProcessID = 2772; StatusCode = 0; ThreadID = 4256; }; ]LOG]!><time="22:39:02.124+480" date="03-11-2010" component="CCMEXEC" context="" type="1" thread="4256" file="event.cpp:525"> <![LOG[HandleRemoteSyncSend failed (0x80040231).]LOG]!><time="22:39:02.140+480" date="03-11-2010" component="CCMEXEC" context="" type="3" thread="4256" file="forwarder_client.cpp:1308"> <![LOG[CForwarder_Sync::Send failed (0x80040231).]LOG]!><time="22:39:02.140+480" date="03-11-2010" component="CCMEXEC" context="" type="3" thread="4256" file="forwarder_client.cpp:1380"> <![LOG[CForwarder_Base::Send failed (0x80040231).]LOG]!><time="22:39:02.140+480" date="03-11-2010" component="CCMEXEC" context="" type="3" thread="4256" file="forwarder_base.cpp:393"> --------------------------------------------------------------- (ClientIDManagerStartup.log) <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="21:35:01.640+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="1" thread="4256" file="regtask.cpp:1434"> <![LOG[RegTask: Failed to send registration request message. Error: 0x80040231]LOG]!><time="21:35:01.656+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="3" thread="4256" file="regtask.cpp:1139"> <![LOG[RegTask: Failed to send registration request. Error: 0x80040231]LOG]!><time="21:35:01.656+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="3" thread="4256" file="regtask.cpp:1314"> <![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="22:39:01.702+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="1" thread="4256" file="regtask.cpp:1434"> <![LOG[RegTask: Failed to send registration request message. Error: 0x80040231]LOG]!><time="22:39:02.140+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="3" thread="4256" file="regtask.cpp:1139"> <![LOG[RegTask: Failed to send registration request. Error: 0x80040231]LOG]!><time="22:39:02.140+480" date="03-11-2010" component="ClientIDManagerStartup" context="" type="3" thread="4256" file="regtask.cpp:1314"> ClientLocation.log - sees the MP server, success LocationService.log ------------------------------- <![LOG[Refreshing client operational settings over AD]LOG]!><time="02:26:42.618+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:4768"> <![LOG[Refreshed security settings over AD]LOG]!><time="02:26:42.664+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:4797"> <![LOG[No security settings update detected.]LOG]!><time="02:26:42.743+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lssecurity.cpp:4350"> <![LOG[Attempting to retrieve default management point from AD]LOG]!><time="19:28:56.848+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:2537"> <![LOG[Retrieved Default Management Point from AD: DELGADO.AD.ENGR.WASHINGTON.EDU]LOG]!><time="19:28:57.863+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:2543"> <![LOG[Persisting the default management point in WMI]LOG]!><time="19:28:57.863+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:3850"> <![LOG[Persisted Default Management Point Location locally]LOG]!><time="19:28:57.879+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:3863"> <![LOG[Attempting to retrieve local MP from AD]LOG]!><time="19:28:58.035+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:3778"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="19:28:58.176+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:457"> <![LOG[Retrieved local Management Point from AD: DELGADO.AD.ENGR.WASHINGTON.EDU]LOG]!><time="19:28:58.176+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:3790"> <![LOG[The 'Certificate Store' is empty in the registry, using default store name 'MY'.]LOG]!><time="19:28:58.332+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="ccmcert.cpp:204"> <![LOG[Refreshing client operational settings over AD]LOG]!><time="19:28:58.348+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:4768"> <![LOG[Refreshed security settings over AD]LOG]!><time="19:28:58.394+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lsad.cpp:4797"> <![LOG[No security settings update detected.]LOG]!><time="19:28:58.644+480" date="03-11-2010" component="LocationServices" context="" type="1" thread="4256" file="lssecurity.cpp:4350"> CAS.log ------------------------- <![LOG[software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="10:03:18.864+480" date="03-05-2010" component="ContentAccess" context="" type="3" thread="2776" file="softdistpolicy.cpp:1312"> <![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="10:03:18.864+480" date="03-05-2010" component="ContentAccess" context="" type="3" thread="2776" file="cachemanager.cpp:1819"> <![LOG[software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="18:09:11.034+480" date="03-10-2010" component="ContentAccess" context="" type="3" thread="980" file="softdistpolicy.cpp:1312"> <![LOG[CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used]LOG]!><time="18:09:11.049+480" date="03-10-2010" component="ContentAccess" context="" type="3" thread="980" file="cachemanager.cpp:1819"> Everywhere I look they say it's a MP issue.. I've reinstalled so many times now I.. I don't think it's MP. Could this be DNS? I have one workstation that is registered to an IP address but the workstation name is different. In Server 2008 R2 are there any firewall ports that need to be opened or some rule installed, uninstalled? My boundaries are setup, workstations are found in SCCM but they can't be approved or anything they register as client NO, but then again the clients can't register. The server can ping the workstations, workstations can ping the server. I'm stumped on this one so any help would be really appreciated! Thanks, Rebecca
  5. Yes! I've triple checked, uninstalled, reinstalled, reconfigured more times then I'd want to.
  6. Here is the MPmsi log file: <11-24-2009 17:39:28> SMSMP Setup Started.... <11-24-2009 17:39:28> Parameters: C:\PROGRA~1\MICROS~3\bin\i386\ROLESE~1.EXE /install /siteserver:DELGADO SMSMP <11-24-2009 17:39:28> Installing Pre Reqs for SMSMP <11-24-2009 17:39:28> ======== Installing Pre Reqs for Role SMSMP ======== <11-24-2009 17:39:28> Found 1 Pre Reqs for Role SMSMP <11-24-2009 17:39:28> Pre Req MSXML60 found. <11-24-2009 17:39:28> No versions of MSXML60 are installed. Would install new MSXML60. <11-24-2009 17:39:28> Enabling MSI logging. msxml6.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6MSI.log <11-24-2009 17:39:28> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msi <11-24-2009 17:39:30> msxml6.msi exited with return code: 0 <11-24-2009 17:39:30> msxml6.msi Installation was successful. <11-24-2009 17:39:30> ======== Completed Installion of Pre Reqs for Role SMSMP ======== <11-24-2009 17:39:30> Installing the SMSMP <11-24-2009 17:39:30> Passed OS version check. <11-24-2009 17:39:30> IIS Service is installed. <11-24-2009 17:39:30> checking WebDAV configuraitons <11-24-2009 17:39:30> WebDAV is configured <11-24-2009 17:39:30> No versions of SMSMP are installed. Installing new SMSMP. <11-24-2009 17:39:30> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log <11-24-2009 17:39:30> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <11-24-2009 17:40:24> mp.msi exited with return code: 1603 <11-24-2009 17:40:24> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError <11-24-2009 17:40:24> Fatal MSI Error - mp.msi could not be installed.
  7. Hello - I'm hoping someone could help me with this problem. I've searched so many websites trying to resolve this issue and it seems no matter what I try I keep getting the same error message. I've followed the steps in setting up SCCM 07 from this web site which was very nicely done! I've also followed the directions on Microsofts Tech Net website on how to configure WebDav and IIS settings. I'm working on a Virtual Windows Server 2008 32-bit OS, SP2, SCCM 07 SP2, IIS7 Here is the message I get in the log files: ---------------------------------------------------------------------------------------------------------------------------- Message ID: 4963 Process ID: 4364 Thread ID: 7996 Componet: SMS_MP_CONTROL_MANAGER MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. ------------------------------------------------------------------------------------------------------------------------------- I could be completely wrong but I read somewhere that with the latest version of IIS doesn't install these user accounts. I checked to see if those accounts existed and they didn't. I've tried what this one website mentioned: http://myitforum.com/cs2/blogs/mlucero/archive/2007/05/16/sms-2003-troubleshooting-mp-control-manager-detected-mpsetup-has-failed-to-create-the-ccm-incoming-virtual-directory.aspx - Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete. - Uninstall the IIS component from the OS of the Site Server. - Reboot the Site Server. - Run ccmdelcert.exe from the SMS Toolkit. - Reinstall the IIS component (with BITS) on the OS of the Site Server. - Go into the IIS manager and allow WebDav. - Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly. These steps didn't seem to work, probably because it was for SMS 2003. Any advice would be greatly appricated! Thanks!
×
×
  • Create New...