wells2050

I have a question regarding the Remote Control function of SCCM 2007. We are starting to notice that during a remote control session, the screen tears as the mouse moves across the screen. I have checked video drivers and they are all current. I have not tried downgrading the drivers. Any ideas?

So, I have followed the instruction on how to pre-stage computers, and yet WDS is still generating a random machine name. I have even gone in and used the syntax for WDSUTIL, and yet, WDS still generates a random Machine Name. Any help would be appreciated. UPDATE: So I set this up on my test lab at home, and it worked with no problems. The only difference is the fact that I am running a Novell DHCP server instead of a windows DHCP server and the WDS server is sitting in a different subnet than the machine that I want to image. My guess is that it has something to do with the Novell DHCP server and WDS can not authorize to a Novell DHCP server. If anyone has any knowledge of this, please let me know.

I have been looking for this for a while, and since I had a positive experience here last time, I decided to post again. Here is what I am looking to accomplish: When the PC PXE boots, I do not want the user to see the prompt for hitting F12. I would like it to be silent, so they will not know about it. (I work for a school district and if I give the kids an opportunity to press F12, they will). If F12 is not pressed, the PC boots as it should. If F12 is pressed, the PC PXE boots. I have tried replacing my PXEBOOT.COM file with the .n12 version, but all that does is boot the PC directly to the imaging server every time. Any ideas?

So here is what fixed the issue: Remove all dhcp options, 60, 66, and 67. Make sure that Novell's PDHCP is not running. In IManager, DHCP, set the bootp address and the boot file. Started right up. Now all that we need to do is keep the message to press F12 to come up, and start uplaoding our custom images. Thanks for your help.

Thanks. I have read that. That post was actually the reason I decided to post here. I do have the WDS configured. I went home and configured WDS on my home server and it works with the same basic config. There are differences though, Home-2003, Office-2008. At home, I am running microsoft dhcp and dns on the same server where at the office, DNS and DHCP are running on a Novell virtual machine and the WDS server is running on a different virtual machine. There is a managed switch that both of these servers connect through. There should not be any port filtering since they are on the same subnet and not going through a router. One thing I noticed on my 2008 install, If I check the "Do not listen on port 67" box, apply changes and click ok. When I go back, the check box is missing. Why? I wonder if that is the issue...

Update, I was able to install a tftp client and download the wdsnbp.com file, so I would say that the tftp services are running on the WDS. I venture to say it is something to do with the DHCP server or the dhcp options. Again, any help is appreciated.

Let me start by saying that I am new to WDS. We currently have a Novell Zenworks Imaging Server, but want to move over to the Microsoft Windows Deployment Services. Here is what I have done so far: Installed and configured WDS on a new server 2008 box. We are ruuning a novell DHCP server on a different server but in the same subnet. I have configured options 66 and 67 on the dhcp server. When booting the client pc, I get a PXE DHCP address, but recieve a PXE-E32: TFTP Open Timeout. I understand that this is an error with the server responding to the client, but can not figure out what I need to do to fix it. Any ideas?