Jump to content


slimslickncom

Established Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by slimslickncom

  1. Rocket Man - I had a package built out like that, but MS deleted it. I will try that again, and thanks, when this system stabilizes.
  2. Thanks Peter. Will check it out if it happens again. I am in the process of working with Microsoft on some other issues. Mainly, the clients are not registering. Rocket Man - I will try that again, as MS stated it was best to use the built in client package. I don't know if all this started when we applied SP1 CU2 but I don't think so.
  3. Everything is set up properly, boundaries and boundary groups. This is a brand new build of SCCM 2012. Trying to work out the kinks before adding more to it, such as dist points, pxe service points, etc... This is not the only thing we are experiencing, but I don't want to go into full detail here about it. The clients are not registering. This is an ongoing issue for us as well. One day it will work with no issues, and other days I have to manually re-distribute packages. I did find this in the ccmsetup.log file. <![LOG[Task 'Configuration Manager Client Upgrade Task' does not exist]LOG]!><time="08:55:51.207+240" date="08-29-2013" component="ccmsetup" context="" type="0" thread="2648" file="wintask.cpp:571"> <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="08:55:51.207+240" date="08-29-2013" component="ccmsetup" context="" type="1" thread="2648" file="ccmsetup.cpp:10540"> Everything is stopped after this, preventing it to run the rest of the task sequences. In which pointed me to this technet article. I didn't attempt to try this yet, but if it comes down to it, I will. Client auto-upgrade failing after client is installed via an OSD task sequencehttp://social.technet.microsoft.com/Forums/en-US/cf091a72-7a86-4e85-a2d3-b55094128364/client-autoupgrade-failing-after-client-is-installed-via-an-osd-task-sequence
  4. Thanks for getting back to me. I updated distribution points and did everything that was suggested.
  5. We have currently stood up an SCCM 2012 SP1 CU2 Stand-alone primary site with remote a remote sql db. Everything is working correctly, but when we go to PXE boot and image computers, it is failing when starting the ts. Receiving this error: "Failed to Run Task Sequence" - This task sequence cannot be run because the program files for <PKGID> (Config Mgr Client) cannot be located on a distribution point. Any help would be appreciative as this is blowing up and stopping our imaging process. Also, when we image machines it seems that the client isn't installing correctly, and showing up in devices as Unknown and not being assigned to the site.
×
×
  • 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.