Skip to content

deploy captured 7 but custom

Featured Replies

Hi all

 

I've successfully captured my custom Windows 7 32Bit reference machine.

Now I'm trying to deploy it on a physical machine.

 

Is it going to deploy the partitions, Userprofiles etc as i captured it or do i have to redo this in MDT and SIM?

 

So i ipmorted the the captured image into MDT and created a TS. When i try to edit the Unattend.xml file i'ts unable to generate or locate the catalogue file. Unfortunately I'm talking about my CAPTURED image, which I can't move to the source folder of the OS-InstallPackage.

 

1: How can i edit my Captured .wim for mapping drives, configuring IE and so on...

2: PX:E53 Error (no Bootfile Name) when deploying the TS with the Captured Image to my machine. PXE Service Point is on SCCM, WDS is configured with check on DHC-Option "Do not listen on port 67" and my DHCP (which is not on the same machine as WDS and SCCM) has got no ScopeOptions concerning the Options 60, 66 or 67.

 

Any Ideas? or any .xml Files of zero touch installations i can have a look at?

 

thanks Anna

you can use wsim to edit windows 7 settings keep in mind that you can generate the unattend.xml on another machine which you have copied the win7 dvd to and extracted it. you do not need to use your newly captured wim to do the unattend.xml work with, just use the original source. you can use imagex/dism to mount the wim later and make other changes if needed, but its always best to do a build and capture when making changes to a master image, the captured image is the 'master' or 'gold' image.

 

2. configure the options on your dhcp server, set option 67 to “\boot\x86\wdsnbp.com” , restart the dhcp service and try again

  • Author

hi Anyweb

 

I'll do that. Thanks for your reply...

  • Author

- what does the \boot\x86\wdsnbp.com path mean¨? and to what File does it referr to?

I need to wright an exact documentation about this...

 

-Do I have to change the path for 64bit OS manually on the DHCP-Scope Options to deploy 64Bit?

ok read this

 

http://blogs.technet.com/adnanezzi/archive/2009/06/22/configmgr-2007-osd-how-to-allow-dhcp-broadcasts-across-vlan-s.aspx

 

specifically

 

How to allow a DHCP Server that is located in a different subnet to respond to a PXE client

 

 

 

So here is the answer:

 

 

 

If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the following:

 

 

 

· (recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts).

 

 

 

· Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to smsboot\x86\wdsnbp.com.

 

 

 

 

 

As suggested configure IP Helper tables to Allow all DHCP broadcasts on UDP port 67 to the SCCM PXE point

 

 

 

Or else

 

 

 

configure the Add DHCP options 66 and 67. Option 66 should be set to the SCCM PXE server, and option 67 should be set to smsboot\x86\wdsnbp.com.

 

 

 

Note: You can also configure IP Helper table along with DHCP option 66 & 67 together to allow redundancy.

 

 

 

interestingly i've seen \boot\x86\pxeboot.com and smsboot\x86\wdsnbp.com working, use what works for you ok ?

 

cheers

niall

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.