Keslaa

How and where did you do this? I am trying to resolve a very similar issue in my lab

I am now tasked with something similar. Did you ever get this figured out?

Because that's the way we've always done it? But seriously, do you think that running all of this on one box would suffice, including the WSUS? I believe the roles were separated out for the sake of disk space (SCCM 2007 was installed before I got here).

We are finally getting around to moving to SCCM 2012. Would the following configuration work? Looking at three separate servers: Primary site server with SQL 2012 DP SUP/WSUS We have about 5000 clients on our current SCCM 2007 environment all in one location. Thank you!

Has anyone experienced this situation? I have a long task sequence and it will not go back into the sequence following a reboot. The report Status of a specific task sequence advertisement for a specific computer shows the step for the reboot and then terminates. What can I look for? How can I restart a TS where it left off?

I've been looking but can't find a solution to my issue. I have a .CMD that resides locally on the hard drive and I want to simply kick it off. I have entered the command like this: C:\<Folder>\<Sub-Folder>\<Name>.CMD This is rebooted to the installed operating system. The CMD file isn't running. If I want to run a .CMD through a command line, is there any special verbiage I need? Do I need to declare the starting directory in both the command line and the Start In Folder box? Should I be using a Task Sequence variable and, if so, which one? This command runs through many configurations and can only take place AFTER a bunch of applications have been installed so when I need to test a change in this, it usually is about 90 minutes between takes. I have run into this before but my work-around was to create and compile a script and then deploy via packages. Thank you for your time.

Hello, I am trying to add the latest heartbeat discovery date to a report that is already in SCCM. I cloned the report (Compliance 8 - Computers in a specific compliance state for an update list <secondary>) and am having difficulty adding what I need. Any help out there? Thank you for your time. Eric

Hello, For the past few months, we've been getting errors while trying to deploy patches through our Software Update Point. Eventually, we were able to trace the problem back to the hard drive on the server running out of free space. It turns out that the folder C:\Windows\Temp has been filling up with files that start with "CAB_". We delete the files and they come back again and again. Does anyone know what these are and what I can do to control their proliferation? Thanks for your time. Eric

I don't know if this would be helpful, but I wrote a powershell script that sets the machine name based on the subnet the computer is sitting on during the imaging process. We have distinct sites and subnets, so this works well. Basically, based on subnet, the first three characters will be the site code (LAV for Las Vegas, NYC for New York City, etc.); the fourth and fifth characters are WW for Windows Workstation; the sixth character will be D for Desktop, N for Notebook or W for Workstation (based on a WMI query); the final seven characters will be the asset tag set in the BIOS (also based on a WMI query). I can post if someone would be interested.

I have a machine that I am trying to re-image. I removed from SCCM (search on MAC and delete - has always worked before) and PXE booted. Normally, after a log in screen, it prompts me to choose one of three flavors of task sequences that are advertised to UNKNOWN machines. This one, however, was pulling down a PE boot image that is not associated with any of the TS's used for the UNKNOWN machines. I would get the prompt for the password and then get a message stating that there are no advertised tasks for this machine. There were three other task sequences that were using this particular PE boot image and I have removed all three advertisements, even though they were all pointing to specific collections and NOT to All Unknown Computers. I then started receiving the 'abortpxe.com' error message before going to the next boot device. Finally, I did a Computer Association, adding the computer to a specific collection and advertised an imaging task sequence to that collection and am still getting the 'abortpxe.com' error. It seems as if this machine is still showing up - somehow - in the works and is looking for a specific task sequence, even though I am telling it to receive a different task sequence. Is there another way to make sure the machine is completely removed the database? Thanks for any help. UPDATE: I just figured out that this was originally our reference machine for our Win 7 image build. The errant PE boot image that the machine kept trying to run was used during that process. I don't know how that would make a difference, but I just thought I'd throw that out there.

Update: The problem just sort of went away, which is somewhat scarier than having the problem in the first place. The spot where the task sequence was ending is where I am executing a script to join the machine to the domain into a specific OU. After joining the domain, the machine should reboot and continue on with the remaining steps of the TS. It doesn't. It was rebooting after the domain join and acted as if there were no more steps. Anyway, hopefully this won't pop up again.

Hello all, I am working with a task sequence that has been used many times already, but now will not run to the end. It has been stopping at various places and there is no obvious error statement to go along with it. The TS just ends. Which logs can I be looking at to figure this out? Is there a log that shows each step of the task sequence as it is being executed? I have gone through the smsts.log already but see no error, just the line "Execution engine result code:2" right before the final reboot and near the very bottom of the log. Also, it shows the initial statements "Parsing ..." for each line of the task sequence, but doesn't show them being executed. Any help? Anything I can throw your way to help troubleshoot?

Thanks for the update. That is what was done. However, there is nothing within that tab that shows the source and that is what I needed to find.

Does anyone know how to determine which drivers were inserted into the boot images? I am trying to troubleshoot an issue and can't see an easy way to determine which drivers should be there and which shouldn't. Figured it out: Went through every driver folder in SCCM and located the matching NIC drivers, clicked on each and selected the Usage tab on the bottom of the screen. Definitely the long way to go about it, but successful.

Turns out it was the BIOS version. I updated to A10 and that made the issue go away. Thanks!