Win2K with the SAK. Win2K with the SAK provides the tools vendors need to create Win2K-powered server appliances. OEMs can use the SAK with Win2K Server and Win2K Advanced Server, so appliances can scale to up to 8-way Intel Profusion boxes. OEMs install the entire Win2K footprint, then use the SAK to choose which features and functionality to activate for their specific device. This selectivity optimizes reliability and performance in the device's area of functionality. Thus, Win2K on a Web or NAS appliance functions like an embedded OS but, strictly speaking, isn't an embedded OS because it has the full OS footprint. The SAK includes
- a local console or UI appropriate for monitor display.
- a browser-based framework for headless management of the server.
- a Device Driver Kit (DDK) with Microsoft certification of developed device drivers.
- a software development kit (SDK) that uses Microsoft languages. The SDK provides scripts that help OEMs build Web server and NAS appliances. Microsoft intends to provide scripts for other types of appliances in the future.
- a reliability framework that includes BIOS failover, automatic mirroring, watchdog timers, and an appliance-monitoring service.
- build documentation.
- exposed APIs for adding services.
The SAK interface, which is similar to Microsoft Small Business Server's (SBS's), is task oriented, with each button leading to a wizard. Figure 1 shows the interface page you use to work with network properties. This page was captured on a MaxAttach NAS 4100. The SAK interface is extensible (just as SBS's is); when a vendor adds functionality through a plugin such as an antivirus package or another add-on, that functionality can appear as either a new page in the interface or additional buttons and wizard steps.
Appliances that OEMs create with the SAK can take advantage of all the abilities inherent in Win2K, particularly enhanced reliability in the form of watchdog timers and failovers to redundant devices and services. Win2K appliances support Lightweight Directory Access Protocol (LDAP), the Kerberos security protocol, NFS (for UNIX and Linux clients) and Common Internet File System (CIFS), Novell NetWare and Apple Computer's AppleTalk, and Services for UNIX (SFU) and other network file-sharing services. Also, Win2K supports Fibre Channel, SCSI, and Ethernet, so Win2K NAS appliances that enable support for all three transport protocols can participate in networked storage regardless of the networking implementation you've chosen.
Microsoft is licensing key software products from other vendors to enhance the appliance offerings of its partners with a set of plugins. W. Quinn Associates has agreed to license its StorageCentral SRM software for inclusion in the SAK. StorageCentral SRM provides realtime quota monitoring and enforcement and "best practices" storage-utilization reporting, and it prevents unwanted file types such as MP3 files from being written to an appliance. Microsoft has also announced that it will add to the SAK Columbia Data Products' Persistent Storage Manager high-availability data-protection software for NAS appliances.
OEMs typically use SAK scripts to remove Active Directory (AD) management services from both Web server and NAS appliances because those appliances are special-purpose devices and thus won't be used as domain controllers (DCs—we might see DC appliances one day, but no vendors currently offer them). However, Win2K registers appliances in your domain's AD as servers because that's essentially what they are.
The SAK greatly reduces the number of steps a vendor must complete to create a Web or NAS appliance. The steps are
- Specify hardware design, peripheral devices, and associated device drivers.
- Install Win2K.
- Install the SAK and run the script that chooses the desired components.
- Add any OEM features.
- Test the appliance.
- Run Saprep to remove the keyboard, mouse, and monitor drivers, and install the Null VGA driver.
- Run Sysprep to add a unique SID to the appliance when it boots up.
- Add a cloned disk to each appliance.
OEMs can get Win2K with the SAK at no cost by sending a request to sak@microsoft.com or through Microsoft's standard distribution channels. When an OEM is ready to release a server appliance, the company must obtain a redistribution license from Microsoft.
