obbnice Posted August 20, 2012 Posted August 20, 2012 Creating a LTI using MDT/WDS. Currently I am trying to deploy Windows 7 onto a referance PC. I cannot avoid getting this error message from every machine I try PXE booting from, "pxe-e79 nbp is too big to fit in free base memory." Has anyone seen this before? I am currently using MDT 2012. The client machine's have 4 - 8 GB's RAM. My LightTouchPE_64.WIM file is about 1001MB. Can someone please shine some light on what could possibly be happening here?? Also, I have rebuilt this 3 times on my Win 7 workstation and once on my VM Server '08 R2 all with same results...Any help would be GREATLY appreciated!
birchanger Posted August 22, 2012 Posted August 22, 2012 Wow - what have you got in that WIM? Ours, for x86 Pe, are only about 180MB.
obbnice Posted August 22, 2012 Author Posted August 22, 2012 Sorry.. In my shreak for help I forgot to say that from the MDT Workbench, it shows 1001MB. However, it is only 160MB on disc from the files properties. Since I have posted this, I now believe my issue is related to our network infrastructure. We are running several VLAN's and different subnets. I think the clients are trying to pull the boot image from the DHCP. Our network admin will be setting up our router to forward broadcasts today. Hopefully I'll have better luck!
SYNACK Posted August 22, 2012 Posted August 22, 2012 Its still a bit big, when you rebuild it are you doing an optimized build that rebuilds it from scratch and have you set it to only include the storage controller and NIC drivers.
obbnice Posted August 22, 2012 Author Posted August 22, 2012 I did have system class drivers checked also initially. It has now been changed and I'm giving it another try. However, I have tried creating a generic version with same results. I usually leave the default optimization setting when updating share, this time I am completely regenerating.
birchanger Posted August 23, 2012 Posted August 23, 2012 You're not exceeding the scratch space size, are you?
obbnice Posted August 23, 2012 Author Posted August 23, 2012 The issue was finally resolved. I needed to have our network admin configure IP Helper to point to my WDS server. After that my client machine's booted to network no problem. Thanks everyone for your help!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now