Difference between revisions of "Active Directory/Documentation/WDS/Service Configuration"
m |
(→Servers: Server & DHCP template data update) |
||
| Line 8: | Line 8: | ||
===WDS-Centennial=== | ===WDS-Centennial=== | ||
==Servers== | ==Servers== | ||
| − | There are three servers currently: munin.wolftech.ad.ncsu.edu, hugin.wolftech.ad.ncsu.edu, and wt-wds-00.wolftech.ad.ncsu.edu | + | There are three servers currently: munin.wolftech.ad.ncsu.edu, hugin.wolftech.ad.ncsu.edu, and wt-wds-00.wolftech.ad.ncsu.edu. PXE-all and WDS-Main will connect users to wt-wds-00, and WDS-Centennial connects users to hugin. The third server, munin, is used as a WDS master server for all management changes to be applied to first, and replicated out to the other two servers. These servers are configured to be fully redundant, so all images, drivers, and other files placed in the Deployment DFS area will be mirrored between all servers. However, due to disk space limitations, the Staging directory hierarchy is only replicated between hugin and munin. |
==Imaging Settings== | ==Imaging Settings== | ||
Revision as of 14:14, 22 April 2010
This page documents the overall layout of centralized WDS services on campus, as well as specific configuration options on the servers and services running. This is intended as a quick reference guide, not a disaster recovery document.
Overview
DHCP
Three DHCP templates are used to connect users to the centralized WDS service. In addition, IT organizations on campus have the ability to integrate centralized WDS services into their own DHCP templates if they so choose.
PXE-all
WDS-Main
WDS-Centennial
Servers
There are three servers currently: munin.wolftech.ad.ncsu.edu, hugin.wolftech.ad.ncsu.edu, and wt-wds-00.wolftech.ad.ncsu.edu. PXE-all and WDS-Main will connect users to wt-wds-00, and WDS-Centennial connects users to hugin. The third server, munin, is used as a WDS master server for all management changes to be applied to first, and replicated out to the other two servers. These servers are configured to be fully redundant, so all images, drivers, and other files placed in the Deployment DFS area will be mirrored between all servers. However, due to disk space limitations, the Staging directory hierarchy is only replicated between hugin and munin.
Imaging Settings
DFS/Replication
A DFS area, \\wolftech.ad.ncsu.edu\deployment, has been created so that it is easy for all users to submit new images and drivers to the service. Additionally, DFS helps replicate the server assets and configuration between the various WDS servers.
Note: replication limitations are inactive until further notice - all replication is performed 24 hours per day at full bandwidth utilization
\deployment\Staging
This area is used for submission of all items (drivers, images, etc) to the service. It has been set up so that it replicates at up to 16Kbps during the hours of 9a-4p Monday through Friday. This is done so that if imaging is taking place, replication of staging data interferes only minimally with the imaging process. Outside of these hours, full bandwidth usage is allowed for replication.
\deployment\DriverRepository
This area contains the various drivers supported through the service. It has been set up so that it replicates at up to 16Kbps during the hours of 9a-4p Monday through Friday. This is done so that if imaging is taking place, replication of driver data interferes only minimally with the imaging process. Outside of these hours, full bandwidth usage is allowed for replication.
\deployment\RemoteInstall
This area contains the actual images and settings replicated between the WDS servers. There are no restrictions on the bandwidth allotted for data replication in this group.