Joe13

Solved this by automating diskpart commands.

I did something now which made it work, not entirely sure how to correct this in the TS. When I booted F12, I used DiskPart to list disk, I cleaned it and created a partition. The deployment was successful after that. So it seems that the TS isn't partitioning the disk the way it should? What can I look at?

Here is the log file, I cannot think why it would be hardware, I take the exact same models and boot PXE, my test machine has no issues. smsts.log

Can someone shed some light on my new issue. I have 1 testing PC where everything works fine, any other PC fails with the same error, new or used PC. There are no more volumes available for use. ApplyOperatingSystem 2019-03-19 15:25:07 1780 (0x06F4) The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created The parameter is incorrect. (Error: 80070057; Source: Windows) ApplyOperatingSystem 2019-03-19 15:25:07 1780 (0x06F4) Failed to run the action: Apply Operating System. Unspecified error (Error: 80004005; Source: Windows) TSManager 2019-03-19 15:25:07 1656 (0x0678) Attached is the first step of my TS where it fails.

Back to square one! : device is in the database. SMSPXE 2019/03/15 9:32:19 AM 5180 (0x143C) : no advertisements found SMSPXE 2019/03/15 9:32:20 AM 5180 (0x143C) : No boot action. Aborted. SMSPXE 2019/03/15 9:32:20 AM 5180 (0x143C) I just used it, what now! Frustrated.

I found the following in the log file: Install application action failed: 'AppName'. Error Code 0x87d00269 It seems like it cannot contact the MP - I'm not joining the domain so it seems that it cannot resolve the MP Name. I added the following in my Cfgmgr step SMSMP=ServerFQDN. Your thoughts on this? Running the TS again, will report back tomorrow.

I have one running now with this options ticked, will post back

Going to pull my hair out. Blank OS with drivers will install. As soon as I add apps it fails. One day it will install the next day it will fail. Cannot find log files to troubleshoot. Frustrating.

See screenshot, when I add a step in TS to install software after the built in "Setup Windows and Configuration Manager" It proceeds past this step, by when it gets to install software on the bottom it shows Initializing SCCM client. Is this correct? I added restart commands between these steps. My software installs, when Windows is done the are no apps installed? It just wouldn't install, If I deploy the apps to a collection and install it from Software Center it works. Just not in the TS. Also added restart steps between app installs.

Thanks Niall, I'm using a standard TS as suggested. With the Windows 10 start layout mod, where would I apply it? In your guide you said it should be - "Scroll down to a section that occurs after Set Status 4" But this was with MDT and SCCM TS. Edit: I added a new section below setup operating system and linked the package from there. Will test and report back. The TS is stuck at "just a moment", I've read that adding unattend.xml to skip OOBE will skip this step. I did this and now the TS fails at the end.

This post forms part of option 3 and 6 of my OP. How can I make this TS lightweight, what steps can be disabled from screenshots attached? Do I use DISM to capture a custom image with drivers and software on it or how can I do this? Is it better to include the drivers with DISM or with this TS? Would it be possible to customize start menu tiles and shortcuts to my preference?

Hi all, Does anyone know how to create a SCOM alert for DHCP scope count - It should alert me when we are running out of available IPs. I've seen this in a deployment a few years back. TIA!

Hi there, How would I go about to free up some space on this SQL server?

Cannot believe no one has replied or resolved this. I have the same issue, but SCSM issues two notifications on SRs, cannot find where the one is coming from, I'm sure it is something OOB config somewhere.

@LeeF I did not change anything in the TS, what difference will this make? Could we discuss point 5 in OP. Do I deploy this to the Unknown collection in SCCM, will any new PC / NB be able to use this PXE? I would like to test the UEFI, It seems that ours will only deploy BIOS. I found an article about the boot file "wdsmgfw.efi" being missing on the \\WDSServer\REMINST\Boot\x64 (See screenshot) I placed it there for now and will test a newer PC with the DHCP scope options (See screenshot) Success - Boot from PXE and UEFI.