Windows 10: Windows Deployment on tested device poses issues beyond available communicative...

Why a vendor-tested device requires attention in Windows installation which is hardly found in any online documentation? To mention first the safety risk that must be adressed right on with BCDEDIT and ndu in the winRegistry. And to mention secondly the stiffly irregular output of milliseconds as observed in media applications where normal playback must be remedied with slower playspeed and never actually matching the correct milliseconds because e.g. most media players offer a 0.75 slower playback which is missing 0.02 msecs to make the true rendering of the material. It can be guessed easily that all output is distorted in like terms video games, Windows UI, everything.

Any possible hints for one to get help in this issue leads to "a bug in the drivers", and that could be the DisplayDrivers or a Windows bug like one discussed in forums about a postprocessing group?.

It has been proved from impossible to irresponsible to expect technical assistance for such an issue from any official support: they simply cannot discuss expediently such an affair, neither be certain of the exact nature of the issue although some observers have appeared from distance very discerning, except not readily involved to contribute to just any ends of home computing.

So, please, can anyone tell me what this is really about? Is it perhaps a serious glitch to policy? Because in all support plans "restrictions apply" anyway!

In any case, here a computer is certainly given to an individual... but not exactly! What do you make of that?


Please Note: The issue mentioned here has been observed in various hardware configurations and poses a question whether it is not simply a tune-up affair, like for example the "adjusting of the paging file" that everybody was instructed to it outside of true technical contexts.

:)

 

Just released: Windows 10 Application Deployment tool

Source: Just released: Windows 10 Application Deployment tool | Building Apps for Windows

 

Futuremark Releases Powermark Battery Life Test for Windows 7 Devices

Futuremark, the world leader in performance benchmarking software and services, today expanded its product line with Powermark a new battery life and power consumption test for Windows 7 notebooks, laptops, tablets and other battery powered devices. Powermark is a professional grade benchmark designed for industrial testing of battery powered Windows 7 devices by OEMs, corporations and governments. It includes a convenient set of standard tests based on productivity and entertainment use-case scenarios, as well as allowing custom settings for bespoke testing requirements. Powermark Professional Edition commercial licenses start at $200 for 10 activations. For further details and to purchase Powermark please visit this page.

Jukka Mäkinen, CEO of Futuremark said, "Battery life is critical to delivering a positive user experience. Powermark helps PC industry OEMs and their suppliers strike a balance between performance and power consumption by providing a consistent, accurate and reliable testing and measurement tool created with Futuremark’s deep experience in quality benchmarking software."

Powermark - battery life test for Windows 7 devices from Futuremark:

• Accurately measure the battery life of Windows 7 devices.
• Choose convenient scenario tests or create your own custom settings.
• Designed for professional test lab environments.
• Licensed for commercial use.

Powermark is only available for business customers at this time.

 

Customised Windows 10 deployment on multiple desktops and laptops.

OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx