Our Blog

Today we had a funny situation when trying to set up a new desktop for a client using Windows Deployment Services from their Windows 2008 R2 server. The client PC wouldn't boot the Windows install files from the server, just hung waiting for a TFTP offer.

After a quick search found that this is due to having DNS server on the same machine as WDS (Windows Deployment Services). DNS uses up all available ports the TFTP service needs and stops issuing WDS responses when clients ask to boot off PXE.

In order to fix this situation, we simply did the following:

Windows Server 2008 R2 fix

run regedit

go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\WDSServer\Parameters

Right-click UdpPortPolicy, and then click Modify.
In the Value data box, type 0, and then click OK.
On the File menu, click Exit to exit Registry Editor.
Restart the Windows Deployment Services service.

Windows Server 2008 R1 fix

Click Start, click Administrative Tools, and then click Windows Deployment Services. If there is no server that is listed under the Servers node, right-click the Servers node, and then click Add Server to add the local computer.
In the navigation pane of the Windows Deployment Services MMC snap-in, expand the list of servers.
Right-click the server for Windows Deployment Services, and then click Properties.
Under Network, increase the UDP Port range. For example, if the current port range is 3,000 ports, increase the port range to 4,000 ports

This afternoon we're undertaking an upgrade of one of our iMac workstations and moving it from OSX Mavericks to OSX Yosemite. We'll post the results once the upgrade is completed.

This evening we've changed the default font to Open Sans. We hope you'll appreciate the easy viewing.

Updated Services Pages today and included a responsive slider to outline some of the services that we provide. We'll keep refining this over time.