nry

Thanks all, I did ADK 10 after the SP2 install...which I now regret as the boot images won't import into SCCM, I'll check the error I get and post it up as nothing I've tried from answers I've found get it going. I can't PXE boot from the original images either...

Hi all, Following your guides on here a few years ago we got SCCM 2012 up and running and last year upgraded it to SP1. I recall at the time having to re-do some of the boot images etc. We've just upgraded to SP2 which all went fine, however we can no longer PXE boot - we have installed/upgraded to MDT 2013 and moved to the Windows 10 ADK...the point of the upgrade was to allow us to look at Windows 10 deployment which I believe needed these two additional steps. I assume(s) we can also still roll out Windows 7 which we were successfully doing before. What are the expected next steps I should be doing to ensure the Win7 PXE boot still works? At the moment no boot image is being sent out when I try a PXE boot on a networked computer, but all the boot images still exist in the SCCM console as before. Hopefully I can get this bit sorted as at the moment it all looks fine within the console but I'm guessing I've missed a step Thanks, Chris

Is it possible that a deployed app which fails to install is triggering this?

The pop-up is coming from 'Software Center', I now have a screen shot. There is the countdown timer and the 'Hide' button is greyed out, they cannot choose to Hide the pop-up. There appears to be a route to block this via Software Restrictions as identified by Microsoft - if I do this, does it also disable the restart?

I have just found that the Windows Update 'Configure Automatic Updates' GPO was set to 'Not Configured' - I have now set this to 'Disabled' which appears to be best practice advice. Vaguely possible Windows Update Services has been over-riding the SCCM settings, I will know soon enough. I have requested screen shots etc. from any staff who see these messages and will post these ASAP.

Cheers - I will try to get a screen shot of the message. Just done a little more reading around on this one - in Client Settings > Computer Agent > Additional software manages the deployment of applications and updates, should this be set to Yes or No when using SCCM to manage these things? This page: http://technet.microsoft.com/en-us/library/gg682067.aspx#BKMK_ComputerAgentDeviceSettings Is slightly confusing, to me it suggests I should choose 'Yes' but at present I have 'No' chosen as I thought this meant that as SCCM does this for me, I am not using additional software? Chris

Hi all, We have been running SCCM 2012 in our school now for just over 12 months - it has worked fantastically well but the one thing I have not managed to get sorted is ensuring no computers automatically reboot during school teaching hours. I have a suitable maintenance window set, but even so, prompts pop-up forcing a reboot in x-minutes. All our applications and Windows Update packages through SCCM are set to not reboot and not install outside of maintenance hours, so I am bit stuck on how to get this one last thing sorted out! Advice is welcome, there seem to many places to check on this type of behaviour, I don't know if I've perhaps missed a critical tick box, or have done something else 'wrong' for our desired use! Cheers, Chris

Sussed it! For whatever reason, even though the 'Deploy this boot image from the PXE-enabled distribution point' was ticked, the problem I had with WDS I presume was not picking up this setting once re-installed. I un-ticked, applied, then re-ticked this option and voila, all working again! Superb, thanks for the help on this one, seems I'm back on track again

Yep it is starting OK, and the SMSPXE log shows it finds the standard x86 and x64 images, but it doesn't find the other two I created with MDT (one before SP1 and one post SP1). I will try updating the DP again for these two MDT images, if this doesn't work I'll try re-creating them.

Ok, the error from the log at present is: could not find boot image HCC000EF Within the SCCM console I have updated the distribution point for this image and it listed as successful once the process completed, any advice on where to look next?

Added WDS back in as a role, presuming this was 'OK', no idea why it wasn't installed any more? PXE is now quazi-working, issue with the SMSPXE log stating no boot image found so I'll go from there!

Which is curious...as that service is not listed...

Nope, I was looking at that file, it hasn't been updated since 23/7/2013 even though I've tried PXE boot numerous times since Love it when things go wrong, something to do!

Ahh, I shall now go hide in a corner for my stupidity, and look at the correct log file on the way!

The log file is not getting updated, I turned off then on again PXE for the distribution point after checking the guide again, and still no joy...any thoughts? I have SP1 and CU2 for SP1 now installed.

I'll confirm the error messages in the SMSPXE.log ASAP, I did follow the guide to the letter

Still seems to be complaining about missing fonts and not being able to copy files...still no PXE

Didn't help re-creating the standard boot images, as I'm using the MDT Boot Image, so I'll re-create this and see if it helps!

Thanks, the errors I get match the link exactly, missing font files, so I'll give it a go!

That looks rather exact We use an MDT deployment image, I'm guessing I have to follow the same steps as I originally did when I first created this?

Great set of instructions as always, our SCCM 2012 instance is now at SP1 Saying that, our PXE boot is no longer working - the interface seen on the clients looks a little different and they get no 'Press F12 to PXE boot' anymore, they simply connect and try to download policy - nothing happens and they move to the next boot device (e.g. hard disk). Do we need to do anything with pre-SP1 PXE boot images etc.? I can't find anything so far looking around Google.

We're only small to be fair - 440 or so pupils, 50 or so staff, myself full time (and I'm not 100% IT) and one p/t technician 2 days a week. Workload is generally low for the most part and our admin team isn't much bigger

SCCM 'Right Click Tools' let you do this easily with an existing computer - if you deploy the OS with SCCM, the settings don't apply for the cache size so for the moment we're using this: http://www.nryonline.co.uk/sccm-2012-setting-the-client-cache-size-for-os-deployment/

Curious view on users - for the most part we have one bulk user creation process before the start of each new school year. There are maybe a dozen pupils/staff added during each year. The bulk add is done with a small free program (Active User Manager) which sets all the user properties. Single users are just 'copied' and given a suitable login name/password. I see no reason why IT shouldn't handle this, it is an IT role and we have no skills or staffing structure in place for anybody else to be doing this type of work.

This may be of interest to people on this forum - it's a work in progress User Guide on how vanilla/SCCM 2012 is managed in our school environment and currently covers: Abbreviations used in this document User Management Creating a new single user Importing multiple/bulk users Setting up a new computer Setting up a computer with Windows pre-installed Join the computer to the HCC domain Update the group membership of the computer to ensure the correct GPO’s are applied Move a new computer to the correct AD location Checking System Center Configuration Manager 2012 has picked up the new computer Setting up a computer using PXE boot Update the group membership of the computer to ensure the correct GPO’s are applied Adding a PXE boot network card driver Identifying a correct PXE network card driver Adding the PXE driver to SCCM Adding the PXE driver to the boot image Adding hardware drivers to SCCM for use during OS deployment Managing applications and deployment within SCCM 2012 Creating an application in SCCM using an existing MSI Creating an application from an executable Finding the uninstall information for an application Distributing an application ready for deployment to computers Deploying an application to computers Uninstalling a deployed application from client computers Creating an MSI for distribution via SCCM Testing software deployment and removal It does not cover how we setup SCCM but is growing to cover all the ways we use it, I'll try to keep this thread updated as I add more to the document. You can find the PDF link here: http://www.nryonline.co.uk/system-center-configuration-manager-2012-user-guide/