All of our DP are on VMware ESXi 5.5 or 6.0 , is there anything specifics or known issue regarding PXE in this environment?
Thanks everyone for the great info & link, I've missed the Window Size but already did the block size a few years ago. -- Sébastien Chobeaux De : listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] De la part de Nash Pherson Envoyé : jeudi 11 mai 2017 10:17 À : mssms@lists.myitforum.com Objet : [CSDCCS Anti-spam: Courriel non-identifé] [mssms] RE: PXE boot slows down after the 3rd computer Changing the Block Size isn't near as effective/reliable as the Window Size, which is why the ConfigMgr team added support for tweaking it last year. See Jorgen's experiments with Window Size and Block Size, but realize both speed and reliability depend on the virtual host, network, and clients: http://ccmexec.com/2016/09/tweaking-pxe-boot-times-in-configuration-manager-1606/ I hope that helps, Nash Nash Pherson Microsoft MVP, Enterprise Client Management Senior Systems Consultant O: 651-796-1168 C: 507-304-0946 [Small Logo-PNG]<http://www.nowmicro.com/> 1645 Energy Park Drive Ste. 200 St. Paul, MN 55108 www.nowmicro.com<http://www.nowmicro.com/> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West Sent: Wednesday, May 10, 2017 3:17 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: PXE boot slows down after the 3rd computer Take a look at this Customize the RamDisk TFTP block size and window size on PXE-enabled distribution points<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsccm%2Fosd%2Fget-started%2Fprepare-site-system-roles-for-operating-system-deployments%23BKMK_RamDiskTFTP&data=02%7C01%7Cnashp%40nowmicro.com%7C97b6000cc2c34848afdd08d497e86a1d%7Cf8a9903e111f4bab99804ab7dc637d43%7C1%7C0%7C636300471853218815&sdata=RLo%2BO6LGs854l8Gp2Zi12VcWvcjTQ5MHRgOTaF8Hp1s%3D&reserved=0> We set ours to 16384 (Decimal) and found it drastically improved our PXE performance. P.S. Don't for get to restart the Windows Deployment Services Server (WDSServer) service after making the change. Dave From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Chobeaux, Sebastien Sent: 09 May 2017 17:15 To: mssms@lists.myITforum.com<mailto:mssms@lists.myITforum.com> Subject: [mssms] PXE boot slows down after the 3rd computer Hello, when using boot on PXE the first 2 / 3 first computers are able to load the boot image relatively quickly , but for the following ones the loading time is incredibly slows (and therefore PXE is unusable for larger deployment). I don't know how long but after a while it goes back to regular speed. I don't feel it something on the SCCM end (all the content is distributed, when booting on PXE it goes to the correct DP, can't see anything peculiar in the logs) and we can see this across all our 65 location / distribution point I'm looking for ideas or pointer I could share with the network team. (using SCCM 1610, with a mix 2008r2 /2012 r2 distribution points) Thanks a lot. -- Sébastien Chobeaux. ________________________________ AVIS IMPORTANT: Les renseignements contenus ou joints à ce courriel sont pour l'usage exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et peuvent contenir des renseignements privilégiés, confidentiels et exempts de divulgation conformément à la Loi sur l'accès à l'information municipale et la protection de la vie privée. Dans l'éventualité que le récepteur du présent courriel n'est pas le destinataire concerné ou la personne autorisée à acheminer le message au destinataire concerné, vous êtes, par la présente, avisé(e), que toute divulgation, diffusion, distribution ou reproduction de la présente communication est strictement interdite. Si vous recevez ce message par erreur, veuillez immédiatement en informer l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que toutes les pièces jointes qu'il comporte. Merci de votre collaboration. ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.plymouth.ac.uk%2Fworldclass&data=02%7C01%7Cnashp%40nowmicro.com%7C97b6000cc2c34848afdd08d497e86a1d%7Cf8a9903e111f4bab99804ab7dc637d43%7C1%7C0%7C636300471853218815&sdata=i%2FtOsO4gZKuUz3C3QiHfEpbR8td8RoBOlqNuTh1GGfs%3D&reserved=0> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form. ________________________________ AVIS IMPORTANT: Les renseignements contenus ou joints à ce courriel sont pour l'usage exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et peuvent contenir des renseignements privilégiés, confidentiels et exempts de divulgation conformément à la Loi sur l'accès à l'information municipale et la protection de la vie privée. Dans l'éventualité que le récepteur du présent courriel n'est pas le destinataire concerné ou la personne autorisée à acheminer le message au destinataire concerné, vous êtes, par la présente, avisé(e), que toute divulgation, diffusion, distribution ou reproduction de la présente communication est strictement interdite. Si vous recevez ce message par erreur, veuillez immédiatement en informer l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que toutes les pièces jointes qu'il comporte. Merci de votre collaboration.
