Search the Community

Hi everyone, I wonder if someone could help me. In my corporate environment, we have collections setup for deployments that our Service Desk use to build machines. The idea is that machines are created or added into that Collection, and the Task Sequence is also deployed to the Collection. We have upgraded to SCCM 1702 in recent times and ntoiced that we cannot always import machines to the collection - we get an error code, like 2152205056. I just looked at: So will test that out tomorrow when I am back in the office. The other issue I am having is; when we have existing machines that are in SCCM and show at Active with a tick etc, we cannot always rebuild them. Sometimes we can just start off the boot media and then either proceed or clean the disk first and then reboot/start the Task Sequence. Other times I get the "There are no task sequences available for this computer" message. What are we doing wrong?

Hi, if you are using UDI wizard to deploy your OS and If you want to have drivers installed for same laptop/machine but different OS you need to add a condition for both packages: 1. First you configure the operating systems in UDI wizard, then their name (Image Name, NOT display Name!) is what counts. 2. Then you implement OS into UDI task sequence, and for that to work you also use OSDImageName variable. For example Windows 7 x64 Enterprise you Add condition->TS variable->OSDImageName equals "Windows 7 x64 Enterprise", I got that name from UDI wizard. For Windows 8 x64 the same, just make another step including Install Operating system Windows 8 and change the variable according to the name. 3. Then create install driver steps both for different OS and also add the condition like bellow: You have to specify both conditions in order to work, otherwise it will install both driver packages. Thanks,

I am getting error when deploying W7 from SCCM. The error from sms log said "Failed to run the last action: apply operating system. Execution of task sequence failed. Element not found. (Error: 80070490; Source: windows). So I went to check the operating system object's image properties and trying to change it from 1-1 to 2-2 under Select image you want to view dropdown box but I am unable to change it. I am able to update the OS image to 2-2 on task sequence. I deleted the OS from sccm and reloaded it but i still can't Apply the change to 2-2 in image properties. The actual windows is on 2-2. Any advice? Thanks

Hei all, I am having a truly strange experience with our SCCM2012 server and a OSD to some desktops. Now, if I had just started with them I would have thought that I had the incorrect driver, but thats not the case here. About a month back I started to configure replacement client desktops for the students. These machines would be going to the library, an intense environment for data. So to make things simple for myself, I took some old HP dx2250 Athlon pc's, installed a new PCI Wifi card and imaged them from SCCM with Win7 x32. I have completed all of them, no problem. I then decided to expand on the usable machines and place several more in the common areas. First batch went well. But the second batch hit a hitch. When they were loading the WinPE environment, they repeatedly rebooted when the network drivers were been loaded. The machines are IDENTICAL in every way to the ones that had been imaged before. I tried booting them on different vlans, but the same issue happened on all. Finally I took one of them over to my work office to troubleshoot it and low and behold - it worked. I did no changes, just booted it from a different physical location. The vlans here are the same as in their previous location. And now things go really weird. I brought over the last 3 and two of them did the same as the first. But not the last. No matter what I try, I cannot get the WinPE environment to load past the network driver load. As mentioned before, the machine is identical to all the others that have been successful. Are there any logs that I can check to follow up or do any of you have any tips for me? Cheers & thanks in advance! Anthony

Is anyone having issues building and capturing an OS with RC2? I was redoing lab 7 and RC2 will not create the .wim file for some reason. I recall doing lab 7 for RC1 and it worked fine. I recall from RC1, that the TS step in lab 7 took a couple of minutes to comlete, but in RC2 it takes just seconds and when I check the path specified for saving the .wim file...the folder's empty. Any suggestions?

Hi, I am having a very strange error crop up while testing the deploy and capture of a boot OS via a task sequence. The error occurs on x86 or x64, on VM's or physical clients. SCCM 2012 is installed per the fantastic tutorial here and this error is appearing on part 7. When deploying the boot image to the target pc, the PE environment loads and immediately resets the client pc with this error: Failed to run task sequence - An error occurred while retrieving policy for this computer (0x80004005) After some searching around I found and tried these: Link 1: Permissions & Link 2: Certificates Unfortunately, neither helped. I have granted sufficient permissions to client systems to access the boot.wim image and the only certificate available is loaded into SCCM and is unblocked. Its difficult to be 100% sure re the certificates issue, as that link is to a 2007 SCCM structure and I think that Admin.\Security\Certificates would be the corresponding location in 2012. At this point I have reinstalled the distribution point, setup new boot images for both x86 & x64, created new tasks and sent them out to the clients and still ... nothing. Clients are still restarting immediately after the PE loads. I have tried to look at the smsts.log on the clients, but they are listed as empty, so cannot. The smspxe.log file reports business as usual with no unusual\error based behaviour. Any ideas anyone or anyWeb? At this point I am at my wits end, but need to continue regardless... Cheers & Thanks

Scenario - I've updating our O/S WIM image and want to push it out to all the DPs to replace the older WIM file, but have limited space on some of the DPs. I can't fit an extra WIM file on those servers and need to completely replace the older WIM with the new one. My initial thought - was to just delete the original image package from the parent server which should remove all the large WIM files from all the DPs, and then create a new image package and deploy that; plus update all my task sequences with the new image. My Question: If I just change the "Data Source" on the existing package to point to the new WIM, and then "update all DPs with a new package source version" will that cause a second cache instance of the .PKG file under \SMSPKG and use double the space? Or will it replace the other package cache file and not take anymore space up; meaning it replaces the older image? Thanks in advance - RickT

Hi everyone. I'm trying install windows 7, but witout succsess. SMSPXE.log: reply has no message header marker SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) reply has no message header marker SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) Failed to send status message (80004005) SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) Failed to send the status message SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE::DB_ReportStatus failed; 0x80004005 SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 20.06.2012 17:14:50 3880 (0x0F28) I was trying do like here but it didn't help me.

At some point I'd like to automate this but for now I need to capture a machine that currently has all of our applications installed. Which route would be the best to take? I tried just using a capture section in the task sequence but am getting an 0x800070490 error. Thanks!

Question, so during my RC1 and RC2 labs I created a captured WIM file and I was wondering if I could copy that file (from my lab) and import it into my production SCCM server. Will this be viable option or is it better to start fresh?