Windows 10: Deployment of Windows RE issues

hello!!! I created a 600MB partition with drive letter H. I used Reagentc /setreimage /path H:\Recovery\WindowsRE and found a problem. After reagentc /enable started winre, Winre.wim ReAgent.xml boot.sdi files appeared in C:\Recovery\WindowsRE instead of /setreimage /path H:\Recovery\WindowsRE. When I shut down winre with reagentc /disable, Winre.wim related files were moved to H:\Recovery\WindowsRE. Why is this the case? Is the command Reagentc /setreimage /path used to set the location of winre when it is working, or does it just shut down the location where Winre.wim image and related fil

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

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

 

Need Help in BitLocker deployment Step by Step

Dear All,

We are planning to deploy to deploy Windows 10 BitLocker in our organization. Could you please anyone help me with step by step deployment from the scratch.

1. What are the requirement?
2. How to setup BitLocker management server?
3. What are the per-cautions and best practices?

Thanks in well advance for brief guide.

Best Regards

Faisal