SM17

Hi, Have set up WSUS on my SCCM box. I have accidentally clicked Windows 8 in the Products to download updates for and now have 433 Updates for Win8. I don't have any Windows 8 machines though, just 8.1. How do i remove them in SCCM please? I'm only used to managing WSUS through the WSUS console - where id decline any updates i didn't want and then run the cleanup wizard. I don't see any option to lose them in SCCM though. Thanks

Problem solved xc3ss1v3 - see my thread for details.

PROBLEM SOLVED! If anybody else comes across this issue or any Task Sequence Deployment issue after upgrading to SP2/SP1 and lands at this thread looking for sanity the this is the problem..... There is a DST related bug in 2012 SP2/2012 R2 SP1 for Task Sequence Deployments that prevents deployments with an available time within the last hour (I think that's it) from working. The easy solution is to set your available time back 12 hours when creating it. credit to Jason Sandys and Torsten Meringer from the Technet forums for the above info! Create your task sequence - make the available time 12 hours (i did 24 hours to be sure) earlier and your Task Sequence Deployment will work straight away!

Not yet i havnt - although i think i have narrowed down the cause of the issue - just not sure yet why its doing it. (check previous link for the updates)

ANOTHER UPDATE Left my newly created task sequence (created approx 3.30pm yesterday) - not OSD'ing and rebooting on preparing Network Connections at 5.30pm last night. Come back to work this morning - re-fired up the same VM i was using yesterday - and guess what - it started to OSD fine!! So I definitely have some sort of time advertisement of any newly created task sequence issue i think. Anybody R2 SP1 manage to replicate this? Think might have to give the guys at MS a call.

UPDATE: To me it appears its something to do with Task Sequences and some sort of advertising delay. Basically i have done nothing since yesterday afternoon when i created my umpteenth task sequence - it failed again so i got the hump and give up on it! Went back this afternoon, tried 1 more VM and hey presto it loaded the OS just like it was pre SP1! - I mean WTF seriously. So i created a new task sequence, used exactly the same settings and boot image - created a brand new VM on the same HyperV Host with identical settings (bar the MAC address of course) - Imported it into my test Collection. Bang - reboots on Preparing Network Connections. Deleted the deployment from my "now working today" sequence - re-deployed again to my test collection. Booted the very same VM again after removing it from the console and re-importing it again, and bang - reboots on Preparing Network Connections. So the same VM managed to load the OS and then an hour later using a different Task Sequence but with all the same details as the one that worked an hour earlier fails to load, and the original that worked an hour later also now fails because its been re-deployed to my collection. Only thing that was different to yesterday and the first attempt today was 18 hours of time! I have a sore head - its been banged against my desk so many times this afternoon.

This is a very kind gesture. If you are happy to do so then id be most grateful. Thankyou

http://www.windows-noob.com/forums/index.php?/topic/12621-upgraded-to-sp1-and-now-cannot-osd-win10-to-a-hyperv-guest/

Correct on both counts Sir. (i upgraded mine Friday just gone - wish i hadn't now mind)

So i recreated both boot images as per this article http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/ Distributed them both successfully Still unable to OSD anything to HyperV - or even a physical machine. Always reboots on "Preparing Network Connections" I dont know enough about this beast to know where to turn next waaaahhhhhhhh

Cant even OSD a W7 machine to Hyper-V and i know i did this successfully pre SP1 upgrade. Think ill re-build the boot images and re-deploy them incase they got screwed during the upgrade

Still battling to learn OSD here! I upgraded my site server to R2 SP1 Friday last week for Win10 support. I have re-deployed the SP1 updated boot images to my DP after the upgrade. I'm trying to test a Build and Capture for Windows 10 build 10030. I have my target VM as a machine in a "Test" collection and have everything deployed and distributed. The Hyper V machine will PXE boot fine but reboot after "Preparing Network Connections" So i imagine that its having problems with the Network Card Drivers. Microsoft would not remove the driver for the Hyper-V Legacy Network Adapter from the SP1 boot image surely??? The smsts.log file tells me: There are no task sequences available to this computer. But i can assure you my Win 10 B+C Ref Task sequence is deployed to "Test" Collection and only that collection. I can confirm that the target vm is getting a valid IP address on the network within the same scope as the SCCM server and within the same boundary group thats assigned. Please help. TIA

I have 1 single DP so both should be distributed to it. I did notice though during the Task Sequence setup that the sysprep bit wasnt greyed out and i have to choose the config manager package. Its at this point its failing so is something up with the config manager package would you think?

Hey all, During my testing and first ever use of SCCM. Yesterday i set up, distributed and deployed a Build and Capture for Win 10 Preview 10030 with Office 2013 installed aswell. Created my task sequence and off i went to PXE boot a test machine. Everything goes well - it installs Windows - reboots - gets devices ready - then goes back into the SCCM screen where it starts to download the Configuration Manager Client Agent. However it gets to "Installing Configuration Manager Client Agent" , sits there for a minute or so without the progress bar moving and then just boots into Windows 10 "Getting things ready" When the desktop comes up there is no agent installed, no Office 2013 installed and no ccm directories to check any log files. Because it hant completed the build stage it doesnt even go to the capture stage so i dont get a WIM image created and saved to the specified directory on the SCCM box either. Ive checked the package for the Configuration Manager Client Package and its successfully been distributed. Under Packages is a folder called "Configuration Manager Updates" and in there are CU5 updates for server update, console update, x64 client upadate and x86 client update - all with a Content Status of Success. The site server was upgraded from 2012R2 release to the CU5 update if this makes any difference? Anybody help me work out whats going on here please? Thanks in advance

The password option though would presumably limit when the OSD could be done to just Office hours? Think ill go down the import route to a seperate collection as i manually distribute new machines to relevant DHCP IP pools anyway via MAC address so its just a little extra work to add it into SCCM too, but ill sleep easier knowing only devices i know about and have control over will/could/can PXE OSD boot!