SuperPlay

Hi Peter Looking at the software group it does indeed have almost 1000 items (997). I will split my Windows 7 ADR into two groups filtered by 'update classificaion' Thanks

Hi Folks I have the same error, however the only selection criteria I have on the Software Updates tab is product/windows7 Any ideas? Thanks in advance

Rocket Man you are a star. I had only selected the new image when I was creating my task media.

I am having total headaches today :-( Yesterday I upgraded SCCM to SP1, all went well. Today I have updated my 'Deployment Task Sequence' with a few settings to install windows updates. Then original issue I had following this was imaging task sequences failing on applying operating system (0x80070057). I had the idea that it may be because I had not updated the version of the console on my admin PC where I created the media. So I moved over to the server to create this (ISO). When I tried to create the ISO it kept failing (pointing to a log that did not exist on the server!), In the end I decided to re-create our x86 boot image (As I could create a task sequence media image based on x64) 1. I removed my existing custom boot image from the distribution point 2. Deleted it from SCCM 3. Deleted the corresponding file from \\servername\SMS_SSF\OSD\boot\i386\ 4 Copied an existing boot.wim to a new file (Think this is the stock one you get on installation) 5. Added the new image into SCCM with my NIC drivers etc Now I can create my boot ISO :-) However on boot I select one of our task sequences abd it fails with "This task sequence cannot be run because the program files for SSF0000A cannot be located on a distribution point............." Looking on our backup it looks like ID SSF0000A was the boot image that I deleted. Please help me, I have been on this solid for 5Hours.... all I want to do is image a machine ;-) Thanks

Hi GarthMJ Thank you for the quick reply. I am new to SCCM patching migrating from WSUS so I am still on the learing curve.

Hi Please can someone clarify what happens if a PC is being shut down while an update or application is being installed? For example: I have an ADR for Windows Updates and a few users have shutdown their PCs during installation. In the Deployment status I see errors similar to the following: 0X8024001E Operation did not complete because the service or system was being shutdown Will the updates be re-installed automatically? Thanks

I have managed to resolve this and it was unrelated to the domain level switch. The cause of the issue was that the BIOS date/time on the new PCs was set incorrectly. Although once imaged users could log-on using their domain accounts (with no errors logged in event viewer) SCCM did not want to know them. In the end I manually removed and re-added them into AD and now all is working as expected. I have also imaged a new PC (after ensuring the BIOS data/time was correct) and this has also been successful.

I have just realised that this issue has been apparent since we have changed our Domain Functional level from "2003" to "2008" is this root cause? Do I need to apply/re-apply any AD or schema settings? Thanks

Hi For some reason a few machines which I have imaged this afternoon are not showing in a query based Collection based on an OU. They are however showing in the default 'All Systems' collection. I have forced both a full 'group discovery' and a 'system discovery' and have performed the 'update membership' task on the collection but still nothing. A few systems that I deployed this morning that are in the same AD OU show in the collection just fine. In sccm if I check the properties of one of the missing machines the 'System OU' field is still blank Any ideas or log files etc. that I can look at? Thanks

Thank you for your prompt reply. I am new to SCCM and this has been very helpful

Hi Please can you help me with the following queries. Q1: If a collection does not have a maintenance window set, what is the resultant setting? Does the collection have a 24hour maintenance window or does it just not have one? Q2: If a PC is a member of say two collections for different purposes for example one for application deployment and one for software updates, each with different maintenance window times (not overlapping). Are both windows seen as game for either task or is the task restricted to its own respective collection time window? Any help/clarification on either of these would be appreciated.

Nice idea :-)

Hi Peter Thank you for your advice and quick replay.

Hi When I was looking in 'Assets and Compliance / Overview / Devices' today I noticed there are a number of computers listed as 'unknown' Checking the MAC addresses of these they look like they are PCs that have been deleted from SCCM and then re-imaged with a real/new name. Can I just delete these 'unknown computers'? Or will this cause problems as they also exist in SCCM with their real name. Thanks

First of all thank you for this and the other guides they have been extremely useful. I am also interested in knowing if this is possible. Currently I have my ADR(s) pointing to my Systems collection. As I would also like to deploy software updates as part of a PC image Deployment Task Sequence I need to be able to deploy this/these to the "Unknown Computers" collection. So pretty much the same questions as 'Rocket Man' Is there a way to do this or do I need create a duplicate ADR? If I have to create a duplicate ADR can I point this to the same share for package source? Thanks