Нас уже 2,838 своих. 🙂
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Апр 4 2017
UEFI PXE Boot Steps – WDS Server 2012 R2
https://social.technet.microsoft.com/Forums/en-US/cd7b3950-fe5a-4591-aeb1-e9c567f00540/uefi-pxe-boot-steps-wds-server-2012-r2?forum=mdt Sign in to vote In my own setup i use a W2012R2 DHCP server. (and W2012 R2 WDS) And with help of vendor classes and DHCP Policy’s I can redirect my clients to the appropiate WDS boot file. Vendorclass: PXEClient:Arch:00007 =UEFi PXE x64 Vendorclass: PXEClient:Arch:00006 =UEFI PXE x86 Venderclass: PXEClient:Arch:00000= BIOS Legacy […]
Читать дальше.
By serg • Boot, PXE, UEFI 0