Jump to content


Geekdevil

Established Members
  • Posts

    2
  • Joined

  • Last visited

  • Days Won

    2

Geekdevil last won the day on October 24 2013

Geekdevil had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Canada

Geekdevil's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Hi Niall, Under Client Push Installation properties General tab: Enabled automatic site-wide client push, unchecked. Installation Properties tab: SMSSITECODE=<my site> SMSCACHESIZE=20000 SMSMP=<my mp> FSP=<my fs> PATCH=<UNC path to SP1.msp> Under Hierarchy Settings Automatic Client upgrade tab: Upgrade client automatically, checked.. I don't remember turning this on because we use Deep Freeze for some machines, so this would be a waste of resrouces. When I ran the upgrade, everything was green. The first thing that I attempted was do to an OSD because WDS is usually the first thing to break. When I couldn't PXE boot, I reinstalled it twice but it was throwing a 80004005 trying to connect to the management point, I decided to look somewhere else. When I looked at my component status, I saw that SMS_MP_CONTROL_MANAGER was in error. I tried to restart it but it would error querying the component. This was when I attempted to reinstall the management point. While monitoring the mpsetup.log I saw that it was trying to install the client as a pre-req and that was failing, so I went to look at my ccmsetup.log and noticed the "PATCH=" mpsetup.log <10/23/13 10:54:49> Installing pre-req using command line "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp <10/23/13 10:54:49> Pre-req installer "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 1 <10/23/13 10:54:49> Failed to Install Pre Req CcmSetup. Return Code is 1 ccmsetup.log [LOG[Loaded command line: "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" "/runservice" "/mp:<my mp>" "SMSSITECODE=<my site code>" "SMSCACHESIZE=20000" "FSP=<my fsp>" "PATCH=<UNC to SP1 .msp&gt]
  2. Hi Topher, I was upgrading our server to R2 this morning and ran into the same issue where the management point stopped working. By chance do you have a "PATCH=" in your automatic client install because I think this is what killed me. I had put that there for SP1. When looking at the mpsetup and mpmsi logs I could see it failing. Like you, I saw the that management point needs the client, so I looked at the ccmsetup and client.msi logs and noticed that it was trying to install the patch for SP1. Long story short, to get the management point back up I did the following: 1. Removed the management point from my server. 2. Ran "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup SMSSITECODE=<mysite>" (with no other options. Change mysite to your actual site code). 4. Monitored my ccmsetup.log to make sure the client installs correctly. 3. Added the management point to my server. 5. Monitored mpsetup and saw that it got past the prereqs and actually installed mp.msi. Eventually I could see activity again in my mpcontrol.log I hope this helps, David
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.