Code: Preparing a Windows® Powered NAS Server Appliance Master Operating System Image for Manufacturing If you are preparing your Network Attached Storage (NAS) appliance for manufacturing, you will be most interested in the original equipment manufacturer (OEM) Pre-install Kit sections of the help documentation. The following instructions lead you through the preparations for manufacturing NAS. Prerequisites Hardware platform that is identical to what will be manufactured Windows 2000 Server, Advanced Server, or Windows® Powered CD Most recent Windows 2000 service pack CD Windows 2000 OEM pre-install kit CD OEM-specific Product Identification (ID) Server Appliance Kit 2.0 CD Microsoft® Services for UNIX CD Microsoft® Service for Netware CD (optional) To prepare a Windows Powered NAS master operating system image for manufacturing: Install Microsoft Windows 2000 on the boot drive and partition of server appliance hardware platform. Install a version of Microsoft® Windows® 2000. Use the table on page 8 to determine what components should be enabled or disabled. Install Services for UNIX. Services for UNIX must be installed separately, before installing the Server Appliance Kit components. The following Services for UNIX components must be installed and enabled: Server for NFS User name mapping Server for NFS authentication If you are installing using the Services for UNIX wizard, you must select the Customized Installation and select the User Name Mapping component under Authentication Tools for NFS. You should clear Client for NFS, Shell and Unix Utilities, and Telnet Client. When prompted, set the User Name Mapping server to localhost. Accept the default install location. NFS logging should be enabled and use the default log file. If you are installing from the command shell use the following command: msiexec /i "sfusetup.msi" ADDLOCAL="NFSServer,NFSServerAuth,Mapsvc" SFUDIR="C:\SFU" /qb Optional: Install Services for Netware. Microsoft Services for NetWare are optional, and may be installed after installing the Server Appliance Kit components. The following Services for NetWare components must be installed and enabled: Internetwork Packet Exchange (IPX) NetWare client File and Print Services for NetWare (FPNW) Microsoft Directory Service Synchronization (MSDSS) To install Services for NetWare Install the IPX protocol. Choose Start, and then point to Settings, and then choose Network and Dial-up Connections. Select a network adapter and right-click the NIC name, and choose Properties, and then point to Install, and then point to Protocol, and choose Add. Select NWLink IPX and choose OK. Repeat steps 2-3 for each NIC card. To install FPNW from the Services for NetWare distribution CD Click Start and then select Settings, and then Network and Dial-up Connections, and select a network adapter. Right-click the NIC name of the chosen network adapter. Choose Properties, and then choose Install. Choose Service, and then point to Add, and choose Have Disk. Type the path for the FPNW subdirectory on the Services for NetWare CD. Open the FPNW subdirectory and choose File, and then choose Print Services for NetWare. Open the FPNW subdirectory and choose File, and then choose Print Services for NetWare. Install the latest service pack for Windows 2000. Install any quick fix engineering (QFE) updates. Configure the administrator account. Secure the configuration. Install the Server Appliance Kit. From the Setup Wizard, select NAS as the type of server appliance you would like to create, and accept the default components. To install the Server Appliance Kit components: Run SaSetup.exe from the root directory of the Server Appliance Kit CD. Select the type of appliance, for example NAS, Web, or custom appliance. Select the components you want to install based on the type of server appliance you are creating. The table on page 9 shows which components are selected by default for each type of server appliance. The features selected during setup can only be installed locally. Installing on first use and Installing from network are not supported. If you have installed the Web user interface (UI) framework, you can access it by opening a browser on the target appliance and typing http:\\localhost in the address field. The Web UI can also be accessed remotely by opening a browser on a client computer and typing the host name of the Windows Powered server appliance in the address field. Install the language resource files for the Server Appliance Kit 2.0. Optional: Add custom or third-party add-ins according to developer’s instructions. Optional: Install custom branding. Optional: Install OEMConfigDll. Run SaPrep. Run Sysprep. Optional: If you have added failover capability to your appliance, install the failover operating system by repeating steps 1-12 on the failover partition of the boot drive. If the primary operating system (OS) fails to boot, you can use a failover algorithm to make the Microsoft Windows Powered server appliance failover to another OS in a variety of ways. The algorithm must detect a boot failure, and then boot the server appliance from another partition/volume. See page 11 for details. Shut down appliance and remove boot hard drive, which will now serve as the master image. Note: Never boot from the master disk directly. Only boot using copies of the master. Copy the master image onto your test units. Test units thoroughly. Once your Windows Powered NAS server appliance master operating system image and hardware have been validated, you are ready to begin manufacturing the server appliance in quantity. Preparing a Windows Powered Web Server Appliance Master Operating System Image for Manufacturing If you are preparing your Web appliance for manufacturing, you will be most interested in the OEM Pre-install Kit sections of this Help documentation. The following instructions lead you through the preparations for manufacturing a Web appliance. Prerequisites Hardware platform that is identical to what will be manufactured Windows 2000 Server, Advanced Server, or Windows Powered CD Most recent Windows 2000 service pack CD Windows 2000 OEM Pre-Install Kit CD OEM-specific Product ID Server Appliance Kit 2.0 CD To prepare a Windows Powered Web server appliance master operating system image for manufacturing: Install Microsoft Windows 2000 on the boot drive and partition of server appliance hardware platform. (See table on page 6 for details). Install the latest service pack for Windows 2000. Install any quick fix engineering (QFE) updates. Configure the administrator account. Secure the configuration. Install the Server Appliance Kit. From the Setup Wizard, select Web Blade as the type of server appliance you would like to create, and accept the default components. (See table on page 8 for details). Install the language resource files for the Server Appliance Kit 2.0. Optional: Add custom or third-party add-ins according to developer’s instructions. Optional: Install custom branding. Optional: Install OEMConfigDll. Run SaPrep. Run Sysprep. Optional: If you have added failover capability to your appliance, install the failover operating system by repeating steps 1-12 on the failover partition of the boot drive. Shut down appliance and remove boot hard drive, which will now serve as the master image. Note: Never boot from the master disk directly. Only boot using copies of the master disk. Copy the master image onto your test units. Test units thoroughly. Once your Windows Powered Web server appliance master operating system image and hardware have been validated, you are ready to begin manufacturing the server appliance in quantity. Obviously, according to this unclear description in Microsoft's official documentation, this version cannot be built. According to documents from Dell, HP, and IBM, the minimum requirement for Powered is to run on SP2. It is not the specific SP3 version that the public thinks. It can be used on SP2-SP4. Perhaps because of my short-sightedness, I have never seen the results of using a "real" Powered key to install the system, so today is a small test to confirm one thing. You have no doubt about the correctness of the key, and I will not publish it. This is an item I got on a Spanish shopping platform. Because it comes with the original machine, there is no doubt about its accuracy.
Code: +SAK_V1 11.8 MB 1 |+oemtools 411.0 KB 2 | |+misc 56.9 KB 3 | | | hisecweb.inf 7.7 KB 4 | | | netset.exe 49.2 KB 5 | |+nullvga 324.0 KB 6 | | | drvprep.dll 13.1 KB 7 | | | ntldr 241.0 KB 8 | | | nullvga.cat 7.2 KB 9 | | | nullvga.cdf 233 Byte 10 | | | nullvga.inf 2.3 KB 11 | | | nullvga.sys 5.2 KB 12 | | | nullvgad.dll 10.1 KB 13 | | | saprep.exe 8.4 KB 14 | | | srvprep.dll 36.7 KB 15 | |+SaConfig 29.2 KB 16 | | +bin 27.5 KB 17 | | | oemconfigdll.dll 10.6 KB 18 | | | saconfig.exe 17.0 KB 19 | | +inf 843 Byte 20 | | | saconfig.inf 843 Byte 21 | | +reg 864 Byte 22 | | saconfigsample.reg 864 Byte 23 | autorun.inf 25 Byte 24 | LangSetup.exe 3.4 MB 25 | quickstart.txt 1.7 KB 26 | releasenotes.htm 25.3 KB 27 | SA_Hardware_Reference_Spec.htm 85.8 KB 28 | sahelp.chm 808.0 KB 29 | SASetup.exe 6.9 MB 30 | setup.exe 234.0 KB 31 Code: +SAK_V2 12.1 MB 32 +oemtools 411.0 KB 33 |+misc 56.9 KB 34 | | hisecweb.inf 7.7 KB 35 | | netset.exe 49.2 KB 36 |+nullvga 324.0 KB 37 | | drvprep.dll 13.1 KB 38 | | ntldr 241.0 KB 39 | | nullvga.cat 7.2 KB 40 | | nullvga.cdf 233 Byte 41 | | nullvga.inf 2.3 KB 42 | | nullvga.sys 5.2 KB 43 | | nullvgad.dll 10.1 KB 44 | | saprep.exe 8.4 KB 45 | | srvprep.dll 36.7 KB 46 |+SaConfig 29.2 KB 47 | +bin 27.5 KB 48 | | oemconfigdll.dll 10.6 KB 49 | | saconfig.exe 17.0 KB 50 | +inf 843 Byte 51 | | saconfig.inf 843 Byte 52 | +reg 864 Byte 53 | saconfigsample.reg 864 Byte 54 autorun.inf 25 Byte 55 LangSetup.exe 3.8 MB 56 quickstart.txt 1.7 KB 57 releasenotes.htm 26.9 KB 58 SA_Hardware_Reference_Spec.htm 85.8 KB 59 sahelp.chm 808.0 KB 60 SASetup.exe 6.9 MB 61 setup.exe 227.0 KB 62 As for SAK, there are two versions. One was released in May 2001 and the other was in June. The version number has not changed. What has changed is that support for several more languages has been added. *The MVS subscription provides the June version
dec4daa7bc8bcee952ca868dc16a25bd96da0afa *en_server_appliance_kit_2.0_aop.exe include Q313698 Code: Server Appliance Kit 2.0 Hot Fix Q313698 ======================================== This software update package for the Microsoft Server Appliance Kit 2.0 and 2.01 contains files that correct the elevated priviledge security issue as described in the Knowledge Base article Q313698. ..... en_server_appliance_kit_2.0_aop.exe\readme.txt Code: *********************************************************** Microsoft Server Appliance Kit 2.0 Add-on Pack Read Me File *********************************************************** December 2001 (c) 2001 Microsoft Corporation. All rights reserved. This is an add-on to the Server Appliance Kit version 2.01. To install and use you must already have a valid license for Windows 2000 Server, Advanced Server or Windows Power, and a valid license for the Server Appliance Kit. To install, you must be running Windows 2000 Server, Advanced Server or Windows Powered, each with Service Pack 2 or higher. The Role-based UI and Controller components also require that Server Appliance Kit 2.01 is installed. The Agent component does not require the Server Appliance Kit to be installed, but without it alerts will not be collected on the controller. ----------------------------------------------------------- 166ab5ddedf47bfad154b95d93b137d88ac69d4e *en_server_appliance_kit_2.01.exe <- your SAK_V2 12.1 MB quickstart.txt Code: The target server appliance system calls for the following requirements: * Microsoft(r) Windows(r) 2000 Server or Advanced Server, Service Pack 2 (SP2), installed on an NTFS file system partition * 50 megabytes (MB) of free disk space on the boot partition NODE: step1: install en_server_appliance_kit_2.01 step2: install en_server_appliance_kit_2.0_aop (as always Microsoft can't count LOL - 2.01 then comming 2.0)
I think that no matter how you operate it, the startup interface of the "Powered" image, including the titles of each window, is different.
from en_server_appliance_kit_2.0_aop.exe Setting up and uninstalling The Microsoft® Server Appliance Kit 2.0 Add-on Pack is designed to be installed after the Microsoft® Server Appliance Kit 2.01 has been installed. Before you uninstall the Microsoft Server Appliance Kit 2.01, you must uninstall the Server Appliance Kit 2.0 Add-on Pack. Changing features in Microsoft Server Appliance Kit 2.01 through sasetup.exe after the Server Appliance Kit 2.0 Add-on Pack is installed can adversely affect the functionality of the Server Appliance Kit 2.0 Add-on Pack and might require a reinstallation of the Server Appliance Kit 2.0 Add-on Pack features.