Windows Deployment Services and Surface Pro 2

The issue I am seeing is when trying load the Windows Boot Manager, before selecting a boot image. The boot manager is loading in the lower 1/4 of the screen. It will not move past this loading screen and seeing how it is not displaying correctly, I cannot
see if there is an error. I am guessing this is a WDS server setting, we are running 2008 R2. However, I don't know what step this would be. It is before the boot image is loaded and I do not think this is a part of Windows PE.
(see below)
Thanks.

check here: http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server
you will probably need to use these:
Sub-menu: /ip dhcp-server network
next-server (this may need to be set to the ip address of your WDS, so that your RouterBoard performs a referral to your WDS)
[this may be the only thing you need, if all your computers are on the same subnetwork]
otherwise you might need to explore these:
boot-file-name (not sure about this one)
dhcp-option (the usual options needed are option 66 and option 67)
EDIT: this may help you:
http://forum.mikrotik.com/viewtopic.php?f=2&t=18203
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

Windows Deployment Services and Mikrotik

I Have an active Directory setup within my office, and I wish to take advantage of Windows Deployment Services to deploy office workstations for our employees.
I have 1 requirement.
The DHCP server is an Mikrotik RouterBoard.
I need to know what options I need to set to allow our clients to PXE boot into WDS.
No one really seems to know what needs to be done.
Since there are options for using a 3rd party DHCP server software, I cant see why this will not work.

check here: http://wiki.mikrotik.com/wiki/Manual:IP/DHCP_Server
you will probably need to use these:
Sub-menu: /ip dhcp-server network
next-server (this may need to be set to the ip address of your WDS, so that your RouterBoard performs a referral to your WDS)
[this may be the only thing you need, if all your computers are on the same subnetwork]
otherwise you might need to explore these:
boot-file-name (not sure about this one)
dhcp-option (the usual options needed are option 66 and option 67)
EDIT: this may help you:
http://forum.mikrotik.com/viewtopic.php?f=2&t=18203
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Mouse and Touchpad settings Windows 8.1 and Surface Pro 3

I have a Surface Pro 3 running Windows 8.1. I noticed that I can no longer use the right or left clicks when using the touch pad on the Surface Pro 3 keyboard.
When I go to PC Settings - PC and devices - Mouse and Touchpad I only see the section for the Mouse, touchpad does not display.
This is occurs with a domain user account. If I log in as a domain admin (different account) the touchpad settings now appear. Does anyone have any thoughts?
If I make the original user and admin or domain admin the results don't change, the touchpad settings still do not display.

Hi,
It's hard to troubleshoot since I have no specific Surface pro to do a test.
Based on your description, when you add the promblematic user account to domain administrator group, the touchpad setting still not appear.
I suggest you recreate a new local user either admin or standard to check if it could get the correct setting.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows Deployment Services and Windows 8.1 Tablet Autorotation Issue

Hi,
I have been trying to deploy a vanilla Windows 8.1 image to Fujitsu Stylistic Q702 Hybrid Tablet using WDS, however this appears to prevent the automatic screen rotation functionality.
When installed from the Windows DVD, automatic rotation is available without any additional driver installation.
Are there any components that need to be added to the unattend files to allow this feature to work?
Regards,
So-Crates

Hi,
WDS provides PXE boot to install windows, it has nothing to do with windows component. I don’t think WDS is the culprit here.
I recommend you ask in manufacture forum, they may give you more effective suggestions.
Thanks for understanding.

WDS and Surface Pro 2

I have a Windows Deployment Server and I am using Windows ADK to load essential drivers onto my boot/install images.
I downloaded the latest Surface Pro 2 driver pack and used DISM to load drivers on to an offline boot image from a Windows 8.1 ISO. I then un-mount the image and load it onto my WDS server.
My problem is the Surface Pro 2 won't pxe boot into my Windows Deployment Server. When I PXE boot, it displays media present and then waits for user input to start PXE over IPv4. I press enter but it times out and then prompts for IPv6 (no error given) when
that times out it boots the machine into windows.
I had been successfully imaging Surface Pro tablets from this deployment server using the same methods, but we recently got in the Surface Pro 2 and I haven't been able to get it working.
I have the latest version of MDT installed but I'm not that familiar with it. When we first started deploying tablets I had attempted to create boot wims with MDT but I never got it working and decided just to use the WADK and DISM.
Any ideas on what I could try next?

I am running WDS on Windows server 2008 R2.
I am using a Type Cover 2 from Microsoft.
I am using the Microsoft Surface Ethernet Adapter. I loaded the drivers for the adapter into the boot image as well as the other drivers from the February driver pack.
Thank you for your response.

Windows Deployment Services 2012 - Driver Group filter by Model value not working - Drivers are not installed!

Hi,
I'm using Windows Deployment Services 2012 to deploy Windows 7 Pro x64 driverless images to different hardware models (drivers are injected using WDS). I already have organized the drivers in driver groups per
hardware model. I'm experiencing driver conflicts so I decided to start using driver group filters to make sure that the driver groups are available only available for the corresponding hardware model.
To get the correct values for the filters i have used the following method: (as described in this article: http:// technet.microsoft.com/en-us/library/dd759191.aspx)
so I checked msinfo32.exe
(System Manufacturer: Dell Inc. System Model: OptiPlex 790)
and set these values in the driver group filter:
Then fired up WDS using PXE booting on my OptiPlex but when finished: No drivers are installed! I investigated further and found on forums to use the following commands (which return the same values btw):
wmic bios get manufacturer
(returns: Dell Inc.)
wmic computersystem get manufacturer
(returns: Dell Inc.)
wmic computersystem get model
(returns: OptiPlex 790)
Values are the same so no problem there.
Then I checked the output of the following commands:
wmic bios get model (returned: error, invalid query)
wmic bios get /all (returned: all kind of information but no model value)
When I remove the value "OptiPlex 790" from the filter list the drivers are installed correctly. So this has to be some problem with the Model value.
Could someone please help me?
As a workaround I now disable all the driver groups exept the one that I need for the hardware. But as more new hardware models are added this is a lot of work to do everytime.
Extra info:
I'm using a WINPE 4.0 image (windows 7 media boot.wim file). 6.1.7.601
Windows Server version: Windows Server 2012 - version 6.2 (Build 9200) - All Windows updates are installed
Windows Deployment Services version 6.2.9200.16384
Having this problem on multiple systems
Questions:
- Does WDS/WinPE uses only the Bios values for determining system info? (then this problem could be with Dell in this example, because no model value is available)
- Is this the correct way to set up driver group filters? (then this is a problem with MS. Does anyone have solution??)
Thank you for your answers & help!

Hi Microsoft,
I still have no answer to my Questions.
Thank you for your answers & help!

Windows could not start the windows deployment services server Error 1067: The Process terminated unexpectedly - Please help

Hello All
I am trying to set up a PXE service point on my DP in SCCM 2012 R2
1) I have enabled the role on the DP
2) rebooted and verified WDS installed as a role.( I let SCCM enable this role as instructed)
3) When I tried to start the role from services I get the error below:
Note: I also followed the troubleshooting steps in this technet article but still it stops at the half way point
http://support.microsoft.com/kb/2009647/en-us
Phil Balderos

Hi,
Here is a similar post for your reference.
Windows Deployment Service
http://www.windows-noob.com/forums/index.php?/topic/3938-windows-deployment-service/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Deployment Services will not start

After advertising a image to my remote client computer I receive this error:
PXE-T01: the specified file was not found
PXE-E3B: TFTP error - file not found
PXE-M0F: Exiting Broadcom PXE ROM
I logged into the server and noticed the "windows deployment service" is not running. I tried to start the service and it failed to start. I then checked the "Site System Status" log and noticed there was a "Critical" message for the PXE service point role,
and a "warning" message for the management point role.
On 8/16/10 for the PXE service point role I see this critical error: PXE Control Manager detected PXE service point is not responding to pxe requests. The error is 16389. Possible cause: pxe service point is not started or not responding.
I would greatly appreciate any assistance.
Thank you

Thank you everyone for your patience and assistance. I have resolved the issue after double, and tripple checking everything. The problem was that the boot images (x64, and x86) were not pointed to SMSPXEIMAGES$ distribution which is the server share. I
pointed it to the Server only. After pointing to both the share, and the server all works fine.
So the initial issue with the deployment service not starting was to uninstall WDS, and the PXE option in SCCM. During the troubleshooting I accidently deleted the SMSPXEIMAGES$ distribution point from the boot image which caused another issue after resolving
the windows deployment problem.
Hope this helps the next person that has this issue.
The solution exists already in the link that I gave you, see the point N°5 :)
http://blogs.technet.com/b/smsandmom/archive/2008/09/17/configmgr-2007-troubleshooting-pxe-service-point-issues-and-wds-service-not-starting.aspx

Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

Hi
I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
Cheers

Hi Joel,
This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, 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.
The related KB:
PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
http://support.microsoft.com/kb/259670
The similar thread:
PXE-E53: No boot filename received
http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
WDSServer (Windows Deployment Server) Fails to Start
http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Deployment Services Issues

i have a Windows deployment Services server running , and at the same server i am running dhcp as well as dns server. the network series is 10.241.0.1 to 10.241.0.105 , questions:
Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1.
Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group , the first
os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.

Hi,
According to your description, I list your questions and the suggestions for each question as bellow:
Q: if i want the dhcp server to offer ip address in the network of 10.241.1.1 is it possible or i need to take the dhcp server in the network series of 1.
If there are 2 network, 10.241.0.1/24 and 10.241.1.1/24, and you want the DHCP server (which is belong to network 10.241.0.1/24 ) to provide DHCP service to clients on network 10.241.1.1/24. You may configure a DHCP relay agent on network 10.241.1.1/24, in
order to forwarder DHCP messages between clients (which are on network 10.241.1.1/24) and DHCP server. Detailed information about how to configure DHCP relay agent you may reference the link:
http://technet.microsoft.com/en-us/library/dd469685.aspx
Q: sometimes there is a problem in wds , the client pc says no dhcp proxies were offered, how do i resolve that ?
On the client which says no DHCP proxies were offered, open CMD, type “ipconfig /all” and hit Enter, check to see if it obtains the correct parameters. If not, type “ipconfig /release“ and “ipconfig /renew” to renew IP address.
Q:While entering the scope in the dhcp server, the dhcp server says the IP is overlapped or invalid ip address, any solutions ?
On a DHCP server, you can create only on scope for a subnet. If you have created a scope from 10.241.0.1 to 10.241.0.105, with subnet mask 255.255.255.0, then a scope with network ID 10.241.0.0 can’t be created. You may use
Exclusions to resolve this problem. If the problem still exit, please provide the scope and relate parameters you want to add, and the exiting scope you have already added on the DHCP server.
Q: i have multiple operating systems to deploys via network, so how is that possible , should i create a new image group or can i add the images in the same images and will it ask during the startup ? i tried by adding the other os to the group ,
the first os gets booted and installed but when i select the second operating system says, wdsclient error, no dhcp offered , , , , and so.
You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing. Make sure that your DHCP implement is working and let us resolve the above 3 problems first. Besides,
you may reference the link for detailed information about Windows Deployment Services Getting Started Guide:
http://technet.microsoft.com/en-us/library/cc771670(v=WS.10).aspx
Best Regards,
Eve Wang

Windows Deployment Services - Windows 8.1 Deployment Failure (Required Driver could not be Installed)

Hello everyone,
Give you a little background on the hardware/software which we are running to do a Windows 8.1 Deployment, we have an VM of Windows Server 2008 R2 with Windows Deployment Services installed and configured correctly. For the boot image it's a Windows 8.1
WIM and as for the Install Image we have a base image of Win 8.1 with all drivers installed for an HP EliteBook 8540w , we Syspreped and then capture the image using the W2K capture on PXE to capture and upload the image to the server. This is where we first
ran into the problem of connecting to the server and had to inject the lan drivers to have network connectivity. After the image was uploaded to the server, we thought to try and run a deployment of that image on an identical laptop. PXE boot into that Image,
it asks for domain credentials which are accepted it begins the installation process and fails at "Windows installation cannot continue because a required driver could not be installed"?
We just set up client logging on the server and it is useless it just says that the driver is missing, but what driver is missing? There are thousands, which one?
Another forum has this issue: http://social.technet.microsoft.com/Forums/windows/en-US/4cf0b378-09d0-4e0b-bc6e-3d898b668f98/during-deployment-windows-installation-cannot-continue-because-a-required-driver-could-not-be?forum=w8itproinstall

Hi,
Please first check the solution here:
Error: Windows installation cannot continue because a required driver could not be installed
http://support.brainwaregroup.com/kb/article/AA-00702/0/Error%3A-Windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed.html
Also, please try to find out Setup logs from the client computer, and we can see the details in the Setup log:
If the failure occurs in Windows PE before the disk configuration page of the WDS client is completed, you can find the logs at the
X:\Windows\Panther folder. Use Shift+F10 to open a command prompt, and then change the directory to the location.
If the failure occurs in Windows PE after the disk configuration page of the WDS client is completed, you can find the logs on the local disk volume at the
$Windows.~BT\Sources\Panther folder. The local disk volume is usually the drive
C. Use Shift+F10 to open a command prompt, and then change the directory to the location.
Kate Li
TechNet Community Support

Can I install Windows 7 on Microsoft Surface Pro 3?

Hi,
I want to install Windows 7 on my Microsoft Surface 3 Pro, I want to know that can I install Windows 7 on MS Surface Pro 3 or if I will install Windows 7 on Surface then what features will not be available in Windows 7 Pro ? What will the issues I will face
after that? Please advise.
Regards.
Kashif

http://windowsitpro.com/microsoft-surface/can-i-install-windows-7-surface-pro
I'm glad your page mentioned the Hyper-V alternative but wish it would elaborate on the potential deficiencies or necessary workarounds. E.g. regarding mouse pointer or Pen, I have W10TP installed as a Hyper-V guest in my Surface Pro 2 and a silly
thing with it is I need to use Mouse Sonar (e.g. press a Ctrl- key) to find out where the pointer is before clicking. After that it works fine. Heh. Right now I'm not having that problem symptom but I can't get on fully to test this recollection
because I have forgotten its password. ; }
Robert Aldwinckle

Windows Deployment Service. Network Profile Radio Buttons greyed out with R2

Hi All
I have downloaded and setup Server 2008 R2 (not yet activated). I have added the following roles "DHCP Server", "DNS Server", "Active Directory Domain Services" and "Windows Deployment Services". I can PXE boot a test client machine and (using the boot.win from windows 7 dvd) multicast a XP Image to it. This setup is connected via a 100 Mb switch and is an isolated network.
Under windows deployment services - if I right click my server - select properties - network tab "Network Profile is greyed out". I have tried running wdsutil /Set-TransportServer /Server:big /Profile:100Mbps but get the following error message: "Windows Deployment Services Management Utility Version 6.1.7600.16385. Error code 0xC110011F This WDS transport server does not support network profiles.
I have tried this on two hardware setups:
An Intel D915GUX 3GHz 2GB RAM and Marvel Yukon 88E8050 ethernet controller.
An Intel D965 Core2Duo 1.86GHz 2GB RAM and Intel 82566DM Network controller.
Incidently I have done the same setup with Server 2008 (not R2) on the D965 and the Network Profile radio buttons are not greyed out. If I upgrade the same test machine to server 2008 R2 the Network Profile radio buttons are greyed out. Is this a design change, does Server 2008 R2 no longer support network profiles as I am now unable to select 10 100 or 1000 Mbs ?
If more information is required or if anything needs further detail please let me know.
Thanks for any help.
Liam.D

Is there any way at all to manually set or control the network profile? In my environment, a SCCM\WDS multicast stream is bottoming out on speed and network utilization when the stream crosses a Nexus 7009 router. Speeds go from 200 Mbps to 20 mbps. I have
a theory that this "new" automatic configuration is placing the clients in a slow network profile that are on the opposite side of the router and I have been unable to find a way to speed of the transmission. I have also ruled out the "master
client" slowing down the stream buy using different clients only connecting to a stream 1 at a time. I have also ruled out the router as the source of the problem by having a VLC client listen to the multicast stream on the same side of the router as
the slow clients. The VLC client (unknown to SCCM\WDS) was able to receive the transmissions at 20 % utilization / 200 Mbps.
-Tony

Windows Deployment Services "the specified image file is either invalid or corrupted"

I'm trying to add images to a virtual server running WS08 R2 but the only type of images that get accepted are the vista x86, nothing else works,
I tried the following image files:
windows server 2008 R2
windows server 2008 x64
windows 7 x64
windows 7 x86
windows vista x64
and always the same error: "the specified image file is either invalid or corrupted"
the machine configuration is as follows:
Virtual machine on Hyper-V 2 (host is WS08 R2 Enterprise)
2048 MB RAM
25 GB free diskspace
running these roles:
AD
DNS
DHCP
WDS
hope someone can help

Was a solution for this ever found? I am experiencing the same issue with the following setup:
I am having an issue with a virtualized Windows Server 2008 R2 Enterprise blue-screening any time I try and add an install image through the Windows Deployment Services mode.
Server:
Lenovo TD200x – 3822-43U
Dual Intel Xeon E5530 CPU’s
Installed Memory: 28.0 GB
Two raid arrays.
                Array 1 – 500 GB Mirror – hosting Windows 2008
R2 Enterprise running Hyper-V
                Array 2 – 1 TB RAID 10 – hosting Virtual Machines
and Virtual Hard Disks
We have the latest firmware update installed on this physical machine
Our physical server is the Lenovo TD200x machine. On it, we are running Windows Server 2008 R2 Enterprise
Within Hyper-V, I am running a Windows Server 2008 R2 Enterprise domain.
Virtual Server 1 is a domain controller running Windows Server 2008 R2. It is configured with roles of: Active Directory Domain Services, DNS,
and DHCP.
Virtual Server 2 is a member server running Windows Server 2008 R2. It is configured with the role of: Windows Deployment Services.
The error is occurring on Virtual Server 2. After everything is installed on this server, and it is setup as a domain member and has the Windows
Deployment services role added, I go through and ad a Windows 7 boot image within Windows Deployment Services with no problem. When I go through and try to add a Windows 7 install image, however, during the creation of that install image, the Virtual
Server 2 pops up an error that reads:
Error occurred while trying to execute command.
Error Code: 0x80070002
After this, the system will immediately blue-screen and reboot with a STOP 0x000000F4 Error
I have tried using various Windows 7 DVD’s and even using the Windows 7 ISO file, mounting it as a drive. All with the same results.
I have erased the virtual server and recreated it with the same results. I have removed the entire domain and recreated both servers with the same results.
I have setup the physical box as a Windows Server 2008 R2 domain controller and added the Windows Deployment Services role and did NOT have any problems
going about it in that manner. Therefore, the issue lies within running this in a Virtualized server within Hyper-V.

Can't start "Windows Deployment Services" Service

I have a Windows 2003 Server that has WDS SP1 installed. The Windows
Deployment Services Server Service isn't started and when I try to
start it I get a message that says:
Windows could not start the Widows Deployment Services Server on Local
Computer. For more information, review the System Event Log. If this
is a non-Microsoft service, contact the service vendor, and refer to
server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to start the Windows Deployment Services
server.
Error Information: 0x906
When I go to the actual WDS application, my server isn't listed. If
I try and add it, I get a message that says "The Windows Deployment
Services configuration is corrupt. Would you like to add it anyway?"
If I say yes, the server is added, but it has a red x through it.
I thought about removing WDS and then re-installing it, but it listed a
number of programs that might fail if I did that.
What should I do?

Thanks, my problem was exactly that:
..................The error you are receiving generally indicates that you have a networking configuration problem on your server that
is causing the domain to be unreachable...............
They exchanged the Firewall and forgot to unlock the doors. After review and release back to work.
Thank you.________________
Moura

Windows Deployment Services and Surface Pro 2

Similar Messages

Maybe you are looking for