SHimmer45

being Dell's the method described will work without any mucking about didnt mean the reply to come across as being sharp apologies

that only works if the OEM actually populates that information, i found that out when trying to use it for our Stone / Novatech pc's as they dont add this information so WMIC can pick it up. i ended up doing something similar using other WMIC query fields but i am still not 100% happy that the selection works as it should, (have had a funky issue with an intel gfx / sound driver not being injected when adding more control to the driver injection, even though it is the correct driver in the folder...)

im sure there is an option in GPO for controlling what is on the CTRL ALT DELETE menu perhaps user config admin templates system rings a bell

use the vmat tool its what it is designed for (i havent really used it) as others have said KMS is pretty much a one time setup and forget task and in the long run makes it sooo much easier to manage licensing & keys

Install a KMS Host and change the keys on the clients. VMAT V2.0 i think is the version for W7. although you dont need it for KMS activation

both driver versions for 64 and 32 bit need to match otherwise it will grumble when trying to install the printer.

i built an image for the older linx 10 on windows 8, doing essentially what @ReBoot has done but i have just used DISM to capture the sysprepped image to a USB stick. 1010 iirc need to be booted from a EFI source (so the mem stick needs to be FAT32). i would love to deploy using MDT like the desktops but as they are wireless only getting MDT is apparently a massive pita but it isnt something i have attempted. On face value it should be an issue but i am not 100% winpe/MDT have the support for the extra bits needed for wireless to work, even if it was possible would you even want to pull a reasonable image over a wireless network would be the next question.

can some one post the update KB number so i can pull the original 1607 update from the windows cat, as all i can find / attempted to apply are updates for 1607 not 1607 itself

i reread the thread and then deleted the post

cool things in 2016?

Hesk would fit this.

if reading the manual correctly just having a 1 lit on the front panel says "no memory modules detected" which if its on and working cant be right, might be a more generic message to say that a DIMM has failed. id put the service tag into dells support site and look at the manual page 23, we have an older 410 which just has the number readout on the front not a full LCD display. u can have openmanage on an ESXI box you need have the omsa agent and then the console on another or use the web interface if it installs in for ESXI

Does the 10 driver have an option for WoL in device manager as it might be present but is set to disabled

for your "flat" file storage the 7200 drives should be up to it to a point, for Virtual machines no SSD or faster SAS Drives are going to be your options

The NIC is going to auto sense so shouldnt need tweaking. a couple of 7200RPM disk are not going to compete with an 15k SCSI array unless there are alot more of the 7200's which you dont have

yeah this is true i assume you could nest / chain the add user and group creation together, i still use net share cacls for the folder creation also as it still works nicely

powershell add user with a CSV works nicely

photoresizer is what we use to resize MASSIVE images down to more sensible sizes, run a search and then drag the results in the program and off it goes.

logon speeds appear to be better in the 1511 / anniversary edition, so LTSB users just need to wait those those to be put into the next ltsb release. i would totally agree that 7 login times are better than 10 which is a little frustrating but thats progress...

this should prove helpful https://support.microsoft.com/en-gb/kb/2852521 slightly tricking thing is to make sure you are changing settings for WIndows or office (like updating keys) as if you dont specify the correct activation ID the default is to the Windows licensing.

KMS key for 10 should activate older versions BUT it has to be the correct type to install on your server the exact name escapes me but it has windows 10 and server 2012 in the name. You need to install this Key and W10 will activate (if its a new server you will still need the usual min number of license requests to activate the server and then the clients) I have a 2008r2 server activating W7 & W10 clients here (with the required patches) also doing office as well but only using 2010, i havent used VMAT for license management on the clients, once it was setup and activated it has just worked.

when i 1st started using this i referred to a old guide on MSDN which stated that authenticated computers/domain computers needed to be added to the share permissions different guides have different views on this (usually read permissions only) GPO software deployment is nice but without SCCM you cant easily tell if the software has made it to the machine

might be the heater roller which i expect you can buy on its own (changed a few on older FS2000 & FS3920's) works out about £40.00 for the roller.

+1 on the fuser or the developer unit isnt working properly

wouldnt mind betting that the vista driver will function on 7