SHimmer45

yeah i forgot to mention you need to extract the cab (this works for 2010 and 2013 so assume 2016 is the same as the /admin option still functions and generates an MSP for controlling the installer)

you can download the office updates and just put them into the updates folder of the office install source when the install runs it applied what is in the updates folder.

an update might have missed a dependency good you got it sort out

if you manually run 2018-06 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4284833) does it complete? also make sure you are not injecting the delta version of the update as they do require the previous update to be installed as they dont have all the requirements prepackaged which keeps it smaller DISM log suggest anything? C:\Windows\Logs\DISM\

Something called WebPI supports the later PHP versions

very much this, we have HESK running on IIS using MySql and PHP took a little fiddling to work (adding IIS_IUSR to be able to read and or write to certain folders for the helpdesk setup) but from where u are now you should just be ale to install the Mysql server (make a note of the DB name and the user and password for accessing it which is set at the time of install) PHP on IIS can be installed directly with a nice tool from Microsoft which can also install and configure IIS at the same time

Ah i see, then i just lift the updates from an updated machine and inject using DISM

i use WSUSoffline updater for the initial update of a build

yes thats all i do, i take a backup of the WIM before mounting it and making any changes

you shouldnt need to reimport it if you have added anything to the WIM i dont when i have made changes and it works ok

seeing as i have started using this for other things i will drop in and have a look

if they dont give you the money to replace the drive they are bonkers regardless if a new server is on its way a drive at most will be a couple of hundred and is well spent to avoid down time and the aggro of having to rebuild a setup. install omsa on core/hyper-v server is documented on the Dell site and is pretty straight forward and is soo useful. If a supplier like upgrade options want stupid money for a drive amazon is worth a look for dell branded kit or ebay or just get the Seagate Model number without the dell branding and you should be ok. (OMSA will moan about being a none dell drive) if your going down the none dell drive route just make sure the controller isnt going to reject a none dell drive (unlikely) If it goes tits up so to speak you will be blamed and the finger pointing will start and they will forget they have restricted you from spending money.

approved firmware and drives which they have tested and tested to make sure they work properly and make it onto the qualified vendor lists that they can then slap a premium on

airserver essentially replaced apple TV's here. shame the miracast support isnt as straight forward (believe it needs a wifi card in the target machine?)

put money on the clients are taking and age to contact the DHCP and get a response back

ports are open and being shown as accessible no from a client. when you say one worked when this morning did you leave it overnight and when you came in it was was on the MDT screen?. both the MDT and WDS servers can ping each other & can you ping them from the client that you are trying to PXE boot from.

"The following UDP ports need to be open for WDS to work across a firewall: 67, 69, and 4011 for DHCP and TFTP; 64001 through 65000 (random ports from this range are used by TFTP and for multicasting); and 68 if DHCP authorization is required on the server" microsoft do a small util (portqry) which you run from a machine and point it at your server to see if ports are open worth checking this

even if the firewall is turned off if a rule is not set to allow it will open the port it will be denied iirc

have you used something like wireshark to see if the machines you are trying to boot WDS from are actually able to reach the server. would there be a way to boot a client so that the DHCP server and the WDS & MDT are all on the same Switch / VLAN

+1 to what @sted says about DHCP options as both DHCP and WDS listen on the same port numbers so the options change what WDS listens on.

arent the feature updates downloadable from the windows catalog site or you have WSUS Offline app which works well i use it for "gold" images. you can also create a scheduled task on your machine to call the silent updater part of the program

theres not an underlying issue with the array that your attempting to copy to? (id check the disk & if it passes nuke the current partition) i think if you have previously used it as a replica location it leaves machine ID folders behind which cause it to grumble

there is a "learn powershell" in a month of lunches which is supposed to be good. i wouldnt say i "code" in powershell but made a bit of time to learn how to use some of the cmdlets to automate certain things

malwarebytes on a DC. not something i would have thought was a good idea

An update hasnt turn on or made changed to your firewall settings on the DC or made changes to what version of RDP client can connect to the DC can you connect out other machines on from the DC?