ZeZe

Do you have screenshots of the problem? Can you export to other format than PDF? Check the SRSRP.log... Did you install the role as described in this lab?! https://www.windows-noob.com/forums/topic/4550-using-sccm-2012-rc-in-a-lab-part-11-adding-the-reporting-services-point-role/

Yes - I guess that would be the best approach and not have to change your current configuration. Just setup one WSUS (not a role nor part your ConfigMgr environment), setup with the proper settings and you are done. Change your site settings to sync from the WSUS that is not part of your ConfigMgr configuration...

Give it some time. ConfigMgr is a little bit slow sometimes!

I had this, but I don't think this affects your reference image.

Screenshots or logs? That's pretty short information to help you at least from my side!

Does the script runs anything from the network? how did you create the script - with notepad++ or normal notepad?

Update: Initially this post was about the drivers in my boot image - maybe yes.. If you have ADK 10.0.10586.0 and if you try to refresh or build and capture an operating system, your task sequence will probably fail. After a lot of troubleshooting and with the help of Windows-noob administrator aka Anyweb, finally got it. I just had update to 1511 and my ADK was 10.0.10586.0. http://blogs.technet.com/b/configmgrteam/archive/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511.aspx=> Microsoft recommends that we don't use this ADK because it nasty, but I thought that this wasn't for me... After adding all needed drivers, the problem persisted and my smsts.log was showing something like this: http://ccmexec.com/2015/11/adk-10-0-10586-breaks-the-refresh-scenario-in-configmgr-2012-sp2-r2-sp1/#comment-20644 Resolution: Remove ADK 10.0.10586.0 Restart server Install ADK RTM (10.0.10240.16384) Restart server Add manually the new boot image to SCCM (Copy winpe.wim from ADK folder to \SMS_PR1\osd\boot\<x64> or <i386>\new_boot_image_wim (don't forget to add your drivers to this new boot image and distribute the content to your DP). Change your task sequence to use this TS instead. Thanks you anyweb!

You probably have duplicate objects. I had that once. Delete that object and add again.

I'm not sure that is possible! Even if you change the configuration in the WSUS, your ConfigMgr will override that configuration. If you have sites with specific configurations than you might need to rethink your environment. But you can always do this: Setup WSUS that sync with Microsoft Updates - you don't add this server to your ConfigMgr environment; Configure your site to download from your internal wsus; Only one server is going online to download updates. Could be this your solution?

Yes, I think this new SUP will have the same configuration. But isn't that the all idea? Edit: This is a component for your site. If you add more roles, the component is still the same. The configuration will propagate the same way for each server that runs that role.

Can you try to do this? Administration - Sites - select the site - Configure site Componentes and select Software Update Point; (you should the configuration from there)... Thanks

There you have it! I think it's the right answer

I guess not... What you can do is a script that will run from network location the installation of whatever you want, however I can't see any reason for that because if the content is not available the TS will fail... what is it that you want to accomplish?

When you have a package or application, I think the agent download the content and run its locally. If you are using a script that run programs that are on a shared folder, maybe (i don't know).. just maybe it causes issues with that switch (/SP).

smsts.log (x:\windows\temp\smstslog) ... press F8 when the error comes up and copy the file smsts.log to the network location or usb...

I'm having problems using VMware Fusion 8 Pro to build and capture windows 7. I can start the task sequence but when it should start capturing the operating system, because the boot image failed to use any of the drivers that are injected, the task sequence fail because it doens't have network. Does anyone has the drivers for nic e1000 ?!

I would recommend to download the content and run it locally. Did you try that?

Can anyone share a link for the network adapter e1000 ? Please?!? I'm using VMware fusion and the folder which everyone is talking about for the drivers is empty... PLEASEEEE.....

After reading moreover this, I think I actually need this, question is.. how and where? I'm using OSX !...

Hmmm... no? The adapter is the Intel 82574 L... I'll make some print screens and post it tomorrow! Maybe I should add that driver to the boot image... I honestly don't know anymore! I'm a little bit lost... never had this kind of issue... thank god this is my lab!

Hi all, I have my own lab in running on my Macbook Pro (mid 2015). I'm using vmware Fusion 8 pro and almost everything works fine. When I try to run a task sequence to build and capture it fails when the step is "capture" because the network driver is not loaded. Actually I added two network drivers to my boot image: from vmware and intel 82574L (which is the one that is not loading). Nevertheless, the computer restart and start loading the boot image to capture the windows, but fails immediately and I'm out of options. Does any one had this issue before? The driver is not digitally signed but was correctly injected to the boot image. note: the driver is correctly loaded when I'm booting from the network (pxe) and I can't copy the log because I don't have any driver loaded... no network nor copy paste basic functions... Any help will be much appreciated!!! Thanks in advanced!

Select the application, go to deployments types, open the installation type you want to change; go to the tab User Experience: Installation behavior: install for user, install for system or install for system if resource is device; install for user = i think it use user permissions to run the program; install for system it will use SYSTEM account to run the application; the third if the you are targeting devices it will automatically run as SYSTEM otherwise as user;

Actually I would suggest that you create a package using IEAK... just be sure to include the pre-requisites!

I'm not sure if this is the same problem I had in the past but when I was re-imaging a test machine, I notice that sometimes it failed to register the computer to the domain. The problem was that sometimes chooses different domain controllers and the computer already existed but it wasn't replicated from other DC's... does the computer exists in the AD? If so, try to removed it and make sure all DCs have the same information...

The software will be pushed on the date/time you made it available. It will run on the deadline you set. If you have a maintenance window define, the installation will be postponed; if you've checked the setting to install software when the deadline is reached, then it should run. Unless there is another variable that you didn't mention. Cheers!