Windows Deployment Services

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Windows Deployment Services

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS Feature Packs >> Windows Deployment Services

Page: [1]

Message

<< Older Topic Newer Topic >>

Windows Deployment Services - 5/14/2007 1:13:40 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

hi guys first of all hello to all of you i m new here !

My questions regarding windows deployment services are :

1. Im having trouble to connect to windows deployment services accross multiple VLAN's (different IP Subnets)

2. How can i upload the image of the whole hard disk to windows deployment server. Right now i m able to only capture the image of the C drive. What about capturing the whole hard disk at once to windows deployment server ???

Thanks in advance to the person who helps me out.

Post #: 1

RE: Windows Deployment Services - 5/14/2007 10:27:12 PM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

Try the following:
Configure DHCP scope with options 60 PXECLIENT
Configure the BOOTP Server and Boot rom file from your WDS server.
Configure IP Helper

(in reply to Chaudry)

Post #: 2

RE: Windows Deployment Services - 5/15/2007 5:04:59 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Configure the BOOTP Server and Boot rom file from your WDS server.
Configure IP Helper

can you please provide more help for these 2 steps. configuring DHCP scope with 60 PXECLIENT Is done. But i have no clue about the last 2 options which you have said. Please help me out i will appreciate it a lot thanks man for your reply !

(in reply to nguru)

Post #: 3

RE: Windows Deployment Services - 5/15/2007 12:09:16 PM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

The basic idea is that WDS, RIS, and ADS before that are all treated as DHCP servers in the network world. They use the same protocol as a DHCP client to get the TFTP server name and get the boot file image from it.

DHCP Option 60 tells the client about PXEClient availability on the network.
DHCP Options 066 and 067: Options 66 and 67 on DHCP will be needed. Configure 66 to be the host name and 67 to be the path to the boot file(s), which has the .com extension.

IP Helper is a command for configuring Cisco Devices, but it should work or have an equivilant on other managed network hardware. It simply tells your clients coming alive on the VLAN where to go for DHCP / BootP if the WDS server is another VLAN.

(in reply to Chaudry)

Post #: 4

RE: Windows Deployment Services - 5/17/2007 12:27:30 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Thanks Nguru for your quick response. You have given some very good tips to solve the VLAN problems for WDS. Thanks again i will try it out as i was busy in some other work for 2 days.

I have doubt regarding port 66 and 67. On the DHCP server if we go to server options and select port 66 or 67 then in the bottom it says String value. Any idea what should be the string value or we just need to enable the ports ?? The second thing is you said "67 to be the path to the boot file(s), which has the .com extension". Does this path has to be UNC path of the Windows deployment server ??

But my other question was how to capture the image of the whole Hard disk. Right now i m able to capture only C Partition ?

< Message edited by Chaudry -- 5/17/2007 3:52:54 AM >

(in reply to nguru)

Post #: 5

RE: Windows Deployment Services - 5/31/2007 3:50:48 PM 1 votes

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

Sorry I have been off site for a few days:
Option 60 the string is: PXEClient
Option 66: Just put the IP address of your RIS/WDS Server
option 67: The path to the .com file starting with your RIS/WDS file share name, for example: REMINST\boot\x86\pxeboot.com

Please score my answer if it helped you :)

(in reply to Chaudry)

Post #: 6

RE: Windows Deployment Services - 6/4/2007 1:21:33 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Nguru thanks for your solution it worked 100% fine ! (10/10 for 1st question)

My other question was that is there any way of capturing the whole image of the hard disk ?? Right now im able to capture on C drive image. What about D drive ??

(in reply to nguru)

Post #: 7

RE: Windows Deployment Services - 6/4/2007 9:16:10 AM 1 votes

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

Due to the nature of Imagex tool and the WIM file format (which is a file based not sector based tool/format), you can't capture the whole disk. For that you have to go with Symantec Ghost or other commercial imaging products and use them for your image instead of image.exe. Ghost for example has a Ghost32.exe (sometimes called GhostPE.exe) which has a command line similar to Imagex.exe. The cost of Ghost Suite 2.0 is around $16.50 per workstation for large purchases (500+ licenses).

PS: to score my answers, you could click on "Rate Post" below each answer :)

(in reply to Chaudry)

Post #: 8

RE: Windows Deployment Services - 6/5/2007 4:49:17 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Thanks Nguru for your quick response !

We are planning to create 4-5 winodws deployment servers in our college.Here is our secnerio :

J Block ( Windows Deployment Server) (J block has Vlans 20,21,25)

F Block ( Windows Deployment Server) (F Block has Vlans 12,13,14)

C Block ( Windows Deployment Server) (C Block has Vlans 30,31,32)

D Block ( Windows Deployment Server) (D Block has Vlans 7,8,9)

Now is it possible that when you boot the client from the network the client will be able to see list of all the 4 servers and then its upto the client to proceed from whichever server it wants ???

Second question is if the above case is not possible then in that case the client will connect to any of the 4 servers and we will never know which server is handling more load. Thats the reason we are creating 4 servers for each different blocks so that each client will connect to its respective server

(in reply to nguru)

Post #: 9

RE: Windows Deployment Services - 6/5/2007 9:30:46 AM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

This sounds like something you could manage from the DHCP scopes. The three DHCP options we discussed could be split as follows:
Option 60: This value will not change among individual DHCP scopes, so make it Global (server specific not scope specific)
Option 67: same thing too, unless the path to the boot file is NOT the same for your WDS servers.

Option 66: you have speicify to the boot server (WDS) for each VLAN's assigned DHCP scope at
Since each VLAN can have one or more subnets, the DHCP scopes for those VLANS should each have the value of the server assigned to their vlan like you stated.

(in reply to Chaudry)

Post #: 10

RE: Windows Deployment Services - 6/6/2007 3:30:50 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Thanks Nguru for your answer. As usual you are very quick. I will test it out and then let you know

There is one more question lolzzzzzzz due to which i m in alot of trouble !

Previously when i installed on windows deployment services it was on the same computer as DHCP server (My Local test Lab) . Due to your help i was able to sort out imaging problems accross VLAN's at that time

Now the problem which i m facing is (In real company enviroment) that both DHCP and Windows deployment server are installed in different computers. So due to that i m not able to configure option 60 for PXE client. Hence im not able to boot from the clients accross Vlan's RESULT NO IMAGING ! How to configure option 60,66 & 67 if the DHCP and WDS servers are residing on different computers.

(in reply to nguru)

Post #: 11

RE: Windows Deployment Services - 6/6/2007 10:18:59 AM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

You need to get me the error code from the boot screen. This is addressed in the WDS documentation in Windows 2003 by the way.
The WDS configuration Wizard ask you if you are running DHCP on the same box or not and makes the changes for you.

Option 60 has to be there regardless
Option 66 should be the FQDN or IP of your WDS server NOT the DHCP server
Option 67 is the path to the boot file image as we discussed before

The additional step you have to undertake: go to DHCP manager and Authorize the WDS server as a DHCP server in Active Directory. Otherwise, it will not talk to AD.
It is a network security feature in AD.

PS: If my last two posts helped you, please rate them

(in reply to Chaudry)

Post #: 12

RE: Windows Deployment Services - 6/11/2007 7:17:40 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

Nguru first of all thanks for your response. No reply form my side coz i was on holidays for 3 days

i will try the solutions provided by you and then i will rate your answer. Will do it within the next 1-2 days

(in reply to nguru)

Post #: 13

RE: Windows Deployment Services - 6/12/2007 2:44:13 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

While trying to boot the client over the network im getting the following error:

PXE-E55: Proxy DHCP service did not reply to request on port 4011

(in reply to Chaudry)

Post #: 14

RE: Windows Deployment Services - 6/12/2007 11:07:32 AM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

http://support.microsoft.com/kb/259670

Add the IP addresses of your WDS Servers to your routers "IP Helper" list :)

(in reply to Chaudry)

Post #: 15

RE: Windows Deployment Services - 6/13/2007 2:44:01 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

This issue can occur when the DHCP server has the following Dynamic Host Configuration Protocol (DHCP) options set:

•
#60 = Client Identifier (set to "PXEClient")

•
#66 = Boot Server Host Name

•
#67 = BootFile NameWhen the initial DHCP offer from the DHCP server contains these boot options, an attempt is made to connect to port 4011 on the DHCP server. This offer fails if the PXE server is on another computer.
Important: Microsoft does not support the use of these options on a DHCP server to redirect PXE clients

Back to the topTo resolve this issue, you must remove these options from the DHCP server and configure the routers IP helper table to contain the IP address of the RIS server.
if i remove these 3 options then how the WDS will work ??? How the client will know where the boot files are located on the WDS server ????

@ nguru

yup i went through that article in detail i m still facing the same problem. When WDS and DHCP are installed on the same machine it works fine. The problem comes only when WDS and DHCP are installed on seperate computers !

In Swtich IP helper address i have given the ip address of the WDS but i m still getting the same error : E55:Proxy DHCP did not reply to client request on port 4011

Where exactly on the switch or router do i need to make the changes. Please explain in detail. And which command i need to use ?? We are using foundary and HP Switches.

Nguru do i need to change anything on DHCP in option 60 ??? In its properties string its set to PXEClient

Option 60 : PXEClient

Option 66 properties string is : 10.20.20.10 (which is the ip address of the server )

Option 67 : 10.20.20.10\remote install\boot\x86

these are the options set on my DHCP server

am i doing something wrong ??

< Message edited by Chaudry -- 6/13/2007 3:16:22 AM >

(in reply to nguru)

Post #: 16

RE: Windows Deployment Services - 6/13/2007 3:41:41 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

OR if it is possible Nguru can u give me your hotmail ID so that i can add u and discuss this matter in voice chat.

I neeeeeeeeeeeeed urgent help coz my boss is bugging me all the time

there is one more thing which i would like to add and that is previously when my DHCP and WDS were installed on the same machine and it was not working accross VLAN's then i added this command at CMD prompt :

WDSUTIL /set-server /usedhcpports:no /DHCPoption60:yes

and it started working accross VLAN's

now since my DHCP and WDS are installed on seperate machines i can't add this command. Do my problem have some link with this issue

here is the screenshot of my DHCP server

WDS And DNS server IP address is 10.20.20.10

< Message edited by Chaudry -- 6/13/2007 6:53:55 AM >

(in reply to Chaudry)

Post #: 17

RE: Windows Deployment Services - 6/13/2007 8:38:30 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

The above Scenario which i have posted is scenario 1

The second Scenario is that i have moved DHCP server, windows deployment server and the client within the same VLAN but still it doesn't work ! I don't know why ????

If i move the WDS on the DHCP computer then it works fine within the vlan as well as accross the VLAN's. But if i install DHCP and WDS on seperate computers then it doesn't work even within the same VLAN WHY ???

(in reply to Chaudry)

Post #: 18

RE: Windows Deployment Services - 6/14/2007 2:03:07 PM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

Please verify that all the WDS servers are added to the DHCP Management Console and Authorized in Active Directory or they will not function, not even on the local subnet. This explains why WDS only works if you install it on the DHCP server (which I assume is already authorized).
You simply click add server and add the WDS server by name or IP address, even though it is not a DHCP server, then right click it and choose "authorize".

Moving forward:

I could tell you right away that:

The Bootfilename needs to be corrected. It does not need to include the IP address IMHO. You simply put the share name, which is REMINST.
So it should be in your case:
REMINST\boot\ etc etc..

Option 60 should be under "Server Options" so that it is valid for all scopes on the DHCP server
Option 67 could be under "Server Options" if it is the same path for all server. Please verify it first like I stated above.

Option 66 (boot server) should be scope-specific because you have different servers servicing different subnets, which are serviced by different scopes, so that PC's serviced by a certain scope get the right server for their VLAN or subnet.

Please try and let me know. Please rate my answer :)

(in reply to Chaudry)

Post #: 19

RE: Windows Deployment Services - 6/15/2007 3:02:28 PM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

@ nguru

can you plz post the screenshot of how to add WDS servers to the DHCP Management Console.

im totally dumb and new on the server side plz help me out

< Message edited by Chaudry -- 6/15/2007 3:03:01 PM >

(in reply to nguru)

Post #: 20

RE: Windows Deployment Services - 6/15/2007 7:39:12 PM 1 votes

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

You got it ..
Start the DHCP MMC
Right click "DHCP" and select "Add Server"
Enter the server DNS name or IP address.
Once the server shows up in the list, right click the server and select "Authorize"

Try that and let me know ..

(in reply to Chaudry)

Post #: 21

RE: Windows Deployment Services - 6/18/2007 3:04:21 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

My Windows Deployment Server has started working. Here is what i did :

1) i deleted the option 60,66,67 from the server options in DHCP
2) In scope options i configured only option 66 (which is IP address of my Server)
3) IP helper address in Switch for WDS server
4) Authorized WDS server in DHCP

for me the main problem was options 60,66,67 configured on DHCP server. Once i removed those 3 options it started working fine for me !

Thanks Nguru for replying all the time for mine queries !

(in reply to nguru)

Post #: 22

RE: Windows Deployment Services - 6/18/2007 9:28:41 AM

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

Glad it is working. I think the scope options were a bit off in the screen cap you posted. Authorization is always a step we all forget in RIS / WDS troubleshooting.

Good luck,
Nguru

(in reply to Chaudry)

Post #: 23

RE: Windows Deployment Services - 6/22/2007 1:57:46 PM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

WDS will work in Workgroup environment or NOT OR is it must to have a working Domain and AD in your setup ?

What is the best way to update the images on all the WDS server. Suppose i update image on 1 WDS server is there any way that this image automatically updates on other WDS servers as well ??

< Message edited by Chaudry -- 6/22/2007 1:59:08 PM >

(in reply to nguru)

Post #: 24

RE: Windows Deployment Services - 6/23/2007 1:29:35 PM 1 votes

nguru

Posts: 298
Score: 13
Joined: 2/7/2004
Status: offline

To my best knowledge, since it is a RIS Version 2.0, it got to have AD.
There are free PXE server software online that work on servers or workstations. They need more manual editing of boot files etc.. You get what you pay for.

The images have to be copied via script of manually. You could use DFS to replicate it over to the other sites but I would copy the images using a DVD drive or over the WAN if you have bandwidth. If you use SMS, you could replicate images as an SMS package. You will need to set maintenance time windows to make sure the image is not in use.

(in reply to Chaudry)

Post #: 25

RE: Windows Deployment Services - 6/25/2007 9:09:59 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

yup thats true i tried to make WDS work in Workgroup enivornment but it didin't worked !

here is what i want to understand :

can you plz explain in detail this option is used for which purpose ???

(in reply to nguru)

Post #: 26

RE: Windows Deployment Services - 7/2/2007 9:40:18 AM

Moha

Posts: 2
Score: 0
Joined: 7/2/2007
Status: offline

Hello all,

I have BDD 2007/SMS SP2 + OSD.

I have created a OSDCDinstall.
then created a ramdisk boot in WDS.

1-booting PXE from a new computer.
2-then winpe initialise
3-Initialise also network then I have the folowing issue.

4-OSdenv cmd windows launch hangs then black screen and reboot.

Advice

Moha

(in reply to Chaudry)

Post #: 27

RE: Windows Deployment Services - 7/4/2007 7:28:53 AM

Chaudry

Posts: 32
Score: 0
Joined: 5/14/2007
Status: offline

boot from the network and it successfully connects to the WDS network and then Windows loading files phase finishes & when the mini vista Setup starts it gives me the following error :

WDSClient: An error occured while obtaining the IP address from the DHCP. Please check to make sure that an operational DHCP server on this network segment.

This error comes only when i try to download the image from the WDS server. There is no problem whatsoever whenever i try to upload the image to the WDS server. Any idea why im getting this error ????

(in reply to Moha)

Post #: 28

RE: Windows Deployment Services - THANKS :) - 7/3/2008 5:02:26 AM

Obiit

Posts: 1
Score: 0
Joined: 7/3/2008
Status: offline

Thanks for the conversation Chaudry and nguru. It saved me after a server crash where we had to move DHCP off the WDS server and WDS failed. Without it i couldn't have got it working again!

Thanks again.

Obiit

(in reply to Chaudry)

Post #: 29

RE: Windows Deployment Services - 9/11/2008 11:01:32 PM

bishal

Posts: 1
Score: 0
Joined: 9/11/2008
Status: offline

Hi,
I did as you told in the form. but the problem is that we are using dell switch. In one subnet it work great it is very fast I can create image but with the other subnet I can boot through PXE but it is very slow. It takes 30 min to start up and when we type start.bat it take us to ghost I select to create It took 2 hours to complet 10% where as in other subnet it took only 5 min to create image.

Please help me

(in reply to Chaudry)

Post #: 30