Yes we had to do this for our environment. The setting we used is 4096,
anything higher broke it.
From: [email protected]
To: [email protected]
Subject: [mssms] Re: RamDiskTFTPBlockSize setting after applying 2012 R2 CU2
Date: Sun, 27 Jul 2014 22:16:32 +0000
Hi Everyone,
Has anyone else noticed that when you apply 2012 R2 CU2, PXE breaks if you have
a custom RamDiskTFTBlockSize value of 8192 or higher? It gets stuck downloading
the Boot.sdi file and eventually errors out.
If you drop it back to 4096 and restart WDS, then it starts working again.
I’ve seen this now in two different client environments.
Cheers
Damon
CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by
legal professional privilege, and is intended only for the person or persons to
whom it is addressed. If you are not such a person, you are warned that any
disclosure, copying or dissemination
of the information is unauthorised. If you have received the transmission in
error, please immediately contact this office by telephone, fax or email, to
inform us of the error and to enable arrangements to be made for the
destruction of the transmission,
or its return at our cost. No liability is accepted for any unauthorised use
of the information contained in this transmission.
