Jump to content


wildcard78

Established Members
  • Posts

    4
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    New York

wildcard78's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. After all that, I went to Admin > Distribution Points and unchecked "Enable this Distribution Point for Prestaged Content" and all the packages started to flow, including the CM client package I needed. I guess that setting doesn't do what I thought it did, hence my confusion. But looks like I'm in finally in business with my task sequence!
  2. I have an interesting issue. I am implementing CM2012 with SP1 and decided to split out my distribution point separate from my primary server. I have my x86 and x64 boot images distributed, along with my Windows image for Win7x64-SP1. I created a task sequence and can successfully PXE boot into WinPE, but I stall immediately with an error that the task sequence cannot find the program files on the distribution point. The package ID it references is the "Configuration Manager Client Package". I checked distribution status for the CM client package and it keeps saying it's "in progress" and that it's waiting to be manually pre-staged. I looked at the properties for the package and they are all grayed out -- there is no way to change the prestage setting from its value of manual and everytime I run 'distribute' content, I notice (from the distmgr.log) that it says that the package and its properties have not changed, so nothing is to be done. How else can I get the CM client package to copy to my DPs? Without it, my task sequences are dead on arrival.
  3. I get that. I just wanted to make sure I wasn't missing out on something compared to the way you do it. But cool, thank you for that. Maybe I will blog one of these days. :-)
  4. I second this. I made some mistakes when I was creating these templates initially and I saw how these deployments were already created from previous attempts, so I just re-used them. Seems like it's a cleaner to create a deployment first, then an ADR, rather than having to go through the ADR wizard twice (albeit using a template the second time to save some steps) and then have a bunch of disabled ADRs in the console to scroll by. I also found I triggered a weird error where the console crashes (.NET runtime error) when I tried to select a template. But shouldn't creating a deployment then an ADR be just as good as doing ADR twice? Thanks in advance for your advice on this.
×
×
  • 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.