O/S Deployment Thread, PXE-E79: nbp is too big to fit in free base memory in Technical; Creating a LTI using MDT / WDS . Currently I am trying to deploy Windows 7 onto a referance PC. ...
-
20th August 2012, 06:57 PM #1
- Rep Power
- 0
PXE-E79: nbp is too big to fit in free base memory
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!
-
-
IDG Tech News
-
22nd August 2012, 02:58 PM #2
- Rep Power
- 11
Wow - what have you got in that WIM? Ours, for x86 Pe, are only about 180MB.
-
-
22nd August 2012, 03:12 PM #3
- Rep Power
- 0
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!
-
-
22nd August 2012, 03:30 PM #4 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.
-
-
22nd August 2012, 03:53 PM #5
- Rep Power
- 0
WDS Drivers and NIC.PNG
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.
-
-
23rd August 2012, 10:50 AM #6
- Rep Power
- 11
You're not exceeding the scratch space size, are you?
-
-
23rd August 2012, 01:09 PM #7
- Rep Power
- 0
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!
-
SHARE: 
Similar Threads
-
By morganw in forum AV and Multimedia Related
Replies: 9
Last Post: 26th October 2009, 09:07 AM
-
By Dos_Box in forum General Chat
Replies: 17
Last Post: 5th February 2008, 10:31 AM
-
By ITWombat in forum School ICT Policies
Replies: 30
Last Post: 18th June 2007, 12:11 PM
-
By ChrisH in forum Windows
Replies: 6
Last Post: 29th March 2006, 08:16 AM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules