JackT

Anyone else getting this issue with 1511?

Ive had no packet loss that i know of. See attached screenshot.

That other reg change is for the initial downloading of the boot file only. Mind after looking at it and changing some more values it was downloading the image to the local drive at 950mbps before it started deploying so not sure why i was complaining now.

Do you have a link to that Mukz?

RIP. I've got it good then if its down to 16 minutes!

Windows 10 edu on an oold dual core desktop with a laptop hdd in it took 16 minutes. Image size was 35GB.

Currently on 1602 so it's not that. Maybe im just being inpatient, it's pulling down the image at anywhere between 50mbps and 150mbps. I've also changed the deployment method from downloading to the local disk first then deploying to installing it straight away. I've tried multicast once before in WDS and wasn't that keen on it. The fact that it waits for the slowest client is a pain. I can't remember where i had seen the option for 10,100,1000 mbps in sccm for deployment speeds, but if im getting 150mbps at times i'd assume ive went for the 1gbps option.

Does anyone know how to speed up the deployment of an image? I've done it once before in WDS where a client could pull the image down at 500+ mbps but in my role i've setup SCCM and can't seem to break past the 50mbps point. I've seen this page for speeding the initial pull down of boot file : System Center Configuration Manager: How to boost PXE TFTP Boot speed. I remember changing some packet sizes but can't remember which ones i changed, if anyone could point me in the right direction that would be grand. I've reimage 300+ machines during the summer and want it to go as fast as possible.

I had a mistake the first time i was trying to remove apps and that was to login with more than one account which provisioned a load of apps for that user aswell. Caused me to rebuild the image. To remove the apps locally from the user account you will need to fun the remove-Appxpackage command from my above post. The provisioned command will stop that app from installing for any other user that signs into the machine, so its best to run both commands to stop the apps from reinstalling and to remove the apps from the current user. Because sysprep is flakey with the apps it will only ever prompt you stating that there is an issue with one app at a time which is a MASSIVE pain.

First you need to run Get-AppXProvisionedPackage -Online | Select PackageName That should return a list of all packages. Next you need to copy the full package name from that list into the next command, in my example i am removing the 3D Builder program. This command will remove the app for all new users that are logging into the system remove-AppxProvisionedPackage -package Microsoft.3DBuilder_11.0.47.0_neutral_~_8wekyb3d8bbwe -online To remove it locally for your user you need to run remove-Appxpackage -package Microsoft.3DBuilder_11.0.47.0_neutral_~_8wekyb3d8bbwe Once you've ran both commands you should be able to sysprep the machine but you may find there are alot of apps to remove and sysprep will only inform you about one app at a time!

Are you loading the credits straight into azure or are you going through a reseller first? If you're loading it straight into Azure you need to remember that the pay as you go pricing are far higher than if you were to go through a reseller for the education pricing.

As others have mentioned the Care Takers forums would be the best bet.

Random question was the program written using wpf or the good old windows forms? If its winforms take a look at this https://github.com/jacobslusser/ScintillaNET it might be an easier option for giving more control to the word editing side of things.