[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 540
  • Last Modified:

Manually start Windows Deployment Services Client

Hello everybody.

after PXE-booting the original boot.wim from Vista/2008, a menu is shown where i can select the install-image that has to be installed.
I now want to find out, by which Application this menu is shown. On a Tech-Net page, I found the information that the "Windows Deployment Services Client" in fact is Vistas setup.exe. But that seems to be impossible, because there is no setup.exe in the boot.wim.

Why I want to know that? Well, I have to "get between". When the boot.wim is started, I first want to start a tool of my own to do some preparation stuff, after that I want to start the original Install-Image-Chooser-Menu.

The normal way an application is started in PE (Registry-Entry, unattend.xml, winpeshl.ini) doesn´t seem to be the way the Windows Deployment Services Client is started.

Does anybody have any ideas?
Thanks!
Tom
0
TheInterrozitor
Asked:
TheInterrozitor
  • 4
  • 2
1 Solution
 
lscapaCommented:
What exactly are you tryin got attempt in "getting between"? There has been some changes in how WDS processes.
0
 
TheInterrozitorAuthor Commented:
I want to start a Tool that creates the partitions in which the OS has to be installed. It is not possible to use the partitioning-tool integrated in the boot-image.
But in fact it is not interesting what i want to do there, my problem is how i can inhibit the start of the Windows Deployment Services Client, then do anything, and then start the Windows Deployment Services Client from my application..
0
 
lscapaCommented:
Unfortunatly WDS only starts when called by the PIX session from a NIC. What you are talking about doing needs to be done via MDT (Microsoft Desktop Deployment Toolkit) it is free and can be used to customize an OS install BEFORE installing. You can launch a windows app (some restrictions apply) to do anything you need then finish the OS install. Take a look and it's worth the reading it takes...
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
TheInterrozitorAuthor Commented:
So in other words, I can not modify the boot-Image but have to customize the install-image with MDT so that my application is started from the the install-image while installing?
0
 
lscapaCommented:
correct it falls into the LTI (Light Touch Installation) in Microsofts framework. There are some limitations but the docs provided in the MDT will explain them to you. This is also another excellent website for setting up LTI. It was written for the earlier version of MDT but will still give you a good overview.
http://www.myitforum.com/myITWiki/Default.aspx?Page=OSD&AspxAutoDetectCookieSupport=1
 
 
0
 
lscapaCommented:
In fact MDT will let you customize the partitions and all so it might even prove more usefull...
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now