关于BXP帮助文件的一些重要部分

edww · November 26, 2004, 10:57am

翻译的BXP3.11帮助文档的原文，本想全贴出来，可太大了，先贴一些我认为比较关键的地方，随后将不断更新，若有需要其它细节部分的，也请在回帖中注明，我也将陆续贴出，谨以此向各位不吝于自己经验和技术的前辈致敬。

Tellurian DHCP服务器

Tellurian DHCPdNT(DHCP服务器)已经被捆绑在BXP产品中用以在没有现存的DHCP服务器的时候提供DHCP服务。
在安装BXP服务器的时候，Tellurian DHCP服务器是一个可选安装项，如果选择了安装Tellurian DHCP服务器，安装程序将在BXP的安装文件夹下创建一个名为“Tellurian”的文件夹(譬如C:\Program Files\Venturcom\BXP\Tellurian)，该文件夹里将包括Tellurian DHCP服务器和产品文档，在安装程序中选择Tellurian DHCP服务器并不会立即启用和设置好这项服务。
取得Tellurian DHCP服务器
(注意: 这一操作必须在安装BXP服务器时执行，关于安装BXP服务器方面的更多问题，请参考BXP安装手册。)

执行BXP产品安装
在安装类型中选择“Full Server”
在提示选择组件时，选择“Tellurian DHCP Server”.
按照BXP安装手册的提示完成安装。
安装Tellurian DHCP服务器
Tellurian DHCP服务器作为一项Windwos标准服务运行，它包括自己的基于ASCⅡ文本文件设置信息，并将客户端租约信息存储在另一个ASCⅡ文本文件中。

警告：如果Tellurian DHCP服务器和BXP服务器安装在同一个系统内，下列命令行将必须存在于Tellurian DHCP设置文件中，反之，则在Tellurian DHCP设置文件中将不允许存在如下命令行
option dhcp-class-identifier “PXEClient”;

创建一个DHCP设置文件
在安装Tellurian DHCP服务的时候，一个范例测试文件已经生成了，我们建议这个文件能被用作设置文件的蓝本，这一样板文件名为“dhcpd.conf”，你可以在BXP安装文件夹下的Tellurian文件夹里找到它(例如：C:\Program Files\Venturcom\BXP\Tellurian\dhcpd.conf)
关于如何修改范例设置文件，请参考Tellurian的相关文档。
安装Tellurian DHCP服务
Tellurian DHCP服务器通过如下命令行进行安装
打开一个命令行窗口(在“开始菜单”→“运行”栏里输入”CMD”).
将盘符更代到BXP的安装盘符(例如，输入“C:”)
进入Tellurian文件夹(例如：输入:“CD \Program Files\Venturcom\BXP\Tellurian”)
要安装Tellurian服务，键入“dhcpdnt.exe Cinstall”.
设置DHCP服务
Tellurian DHCP服务需要调整选项才能有效发挥效能，这也能通过命令行来完成，如下命令行选项都是可用的：
-l 响应完整的DHCP逻辑文件路径和文件名(默认为C:\dhcpdnt.log.)
-d 是0～9之间的一个数字，它用以标识具体事件在逻辑文件中的重要性，0表示不需要记录，并且也不创建逻辑文件。
2 产生简单的加载信息
6 第一级加强型逻辑控制服务环境
9 第六级加强型逻辑控制服务/传输环境
-c DHCP服务器设置文件(默认：C:\dhcpd.conf’)
-b 列出包含所有租约的文件(默认：C:\dhcpd.leases)
-p DHCP的UDP端口(默认为67)
-s 将当前命令行参数保存至注册表
-r 复位注册表信息到安装时的默认值
下面是一个在BXP安装中使用默认设置文件调试DHCP的范例
dhcpdnt.exe --install
dhcpdnt.exe -l “c:\Program Files\Venturcom\BXP\Tellurian\Log.txt” -d 2 -c “C:\Program Files\Venturcom\BXP\Tellurian\dhcpd.conf” -b “C:\Program Files\Venturcom\BXP\Tellurian\dhcpd.leases” -s
4.启动Tellurian DHCPdNT服务
和所有的服务一样，Tellurian DHCPdNT服务必须启动或被设置为在系统运行时自动启动以发挥效能。
可执行如下操作以启动Tellurian DHCPdNT服务：
在开始菜单里，单击选择“控制面板”
双击“管理工具”.
双击“服务”图标.
选择“dhcpdNT”服务
右击dhcpdNT并选择“属性”
单击“开始”以启动Tellurian DHCP服务
要调整Tellurian DHCP服务至在每次计算机启动时自动运行，将“启动类型”改变为“自动”
关闭服务控制台窗口
小窍门
・在安装完并设置好Tellurian DHCP服务之后，仍然可以通过修改注册表改变设置参数(就像改变设置文件一样)，相关注册表参数值可在如下子键下找到HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dhcpdNT\Parameters.
・通过Tellurian 服务生成的逻辑文件对于调试设置文件的错误非常有用，如果你无法启动Tellurian DHCP服务器，建议先检查一下逻辑文件以获取额外相关信息。

edww · November 26, 2004, 10:57am

BXP客户端域成员资格工具

简介
每一台需要登录域的计算机都需要域控制器提供一个计算机帐号，该帐号及其口令同时存放在域控制器和客户端的本地注册表上，如果这些信息不匹配，用户阿将无法从客户端计算机登录到主域，因此，一旦启用了BXP写过滤，且采用将单一映像提供给多台具有不同计算机名和帐号名的客户端计算机用作启动使用时，这种口令不匹配的现象将会发生。
为修正这一问题而专门编写了一个应用程序，通过在主域控制器上执行它，便可以创建和分配BXP客户端计算机帐号和默认密码“与帐号名相同”，在客户端，必须安装一个服务以便在网络登陆服务之前将计算机帐号设置在本地注册表内，该密码采用同样的加密规则(基于启动时BXP虚拟磁盘驱动所动态分配的计算机名)。
BXP设置计算机帐号应用(BNSetCA)
该工具运行在主域控制器上以创建BXP客户端计算机帐号并更改现存用户的口令分配，使用方法如下：
BNSetCA <计算机名>
<计算机名>是BXP数据库中需要BXP的客户端的名称，该应用程序需要Win2000 Server且必须管理员权限才能运行。
BXP客户端服务(BNClient)
BXP客户端服务必须动态调整包含在默认安装BXP客户端的本地计算机的帐户口令。
默认情况下，计算机帐号口令7天自动更改1次，默认设置必须要调整为允许BXP客户端登陆域，要变更这一设置，在BXP客户端计算机进行如下操作：

在开始菜单里，选择“设置”“→“控制面板”
如果运行WinXP，选择“性能与维护”分类，( Win2000不需要这一步)
选择“管理工具”并找到“本地安全策略”选项
当运行“本地安全策略”时，选择“安全设置“→“本地策略”→“安全选项”并在左面展开分支
在右面的列表中启用如下规则中的一个(取决于使用的操作系统)
・ WinXP：“域成员: 禁止计算机帐号口令变更”
・ Win2000：“防止计算机帐号密码的系统维护”
点击确认以存储变更并关闭窗口。

edww · November 26, 2004, 11:00am

设置BOOTP服务

如果你的网络使用BOOTP,按如下步骤为BXP设置BOOTP。
・注意: 3Com BOOTP服务和DHCP服务器不能安装在同一台计算机上，如果你选择安装在同一台计算机上，在安装BOOTP服务之前，你就必须移除、禁用或停止DHCP服务器。
在安装好BXP之后，默认情况下，一个范例BOOTPTAB文件就已经放在TFTPBOOT文件夹里了，默认情况下，这一文件夹的路径是C:\Program Files\Venturcom\BXP\TFTPBOOT)，在这个文件夹里同时还存在一个BOOTPTAP文件的备份文件，它的文件名是bootptab.bp.

在Windows的开始菜单里,选择“设置”，然后选择“控制面板”
在“控制面板”里，单击“3Com BOOTP”按键。
如果出现一个警告信息提示BOOTP服务没有运行，选择“Yes”.将出现BOOTP设置界面。
在“Options”页面，确认BOOTPTAB文件的路径和文件名正确，(除非特别指定，这里应该是C:\Program Files\Venturcom\BXP\TFTPBOOT)，如果这里没有显示，请按“Browse”键以查找它。
如果你需要启用多播回应，则选择“Broadcast Replies”，这样BootP回应请求将被同一网络或子网的每一台工作站收到，当该功能未被启用，则只按照单播回应(Unicast Replies)方式，这种情况下将只有请求回应的那台工作站会收到BOOTP回应。
如果服务器安装了超过1块网卡(NIC)，你就必须设置究竟哪些网卡绑定BOOTP服务，单击“Network Adapters”页面以选择想要使用的网卡，明确了吗？
在选择适当的网卡之后，选择“OK”以保存设置并推出BOOTP设置界面。
下一步是设置TFTP服务。

为BXP启用BootP
BXP设置向导在默认情况下会将PXE协议用作网络启动协议进行加载，如果要为BXP使用这个更老的、不够灵活的Bootp协议，标准设置项中的几个地方必须作调整，下面将详细说明这些差异性。
1)你必须在客户端使用Bootp兼容的网卡，不是所有的网卡都支持Bootp协议，3Com 905C是已知的在其ROMBIOS中提供具备已经能正常工作的Bootp协议的网卡。
2)你不能在BXP服务器上运行DHCP或PXE服务，如果你使用PXE设置向导来设置BXP服务器，请确认在安装向导运行完毕后已停止PXE服务和可能存在的BXP DHCP服务。
3)通过控制面板的“服务”选项在BXP服务器上启动BXP Bootp服务
4)用BXP Bootptab编辑器(BXP Bootptab Editor)编辑Bootptab文件，为每一台工作站添加MAC地址和IP地址，确认在“Edit”→“Preferences”对话框里将Bootptab编辑器设置到Bootp模式，你可以参看“使用Bootptab编辑器”一览以获取有关Bootptab编辑器的更多信息。
5)确认你在创建虚拟磁盘映像时为你的工作站设置了一个静态IP地址，如果你启用共享映像模式启动，BXP工作站驱动将从Bootp进程中获取并自动为每一台启动工作站更换为Bootptab中指定的IP地址，因此即使所有IP地址都已经分配为静态IP，在共享映像模式下仍然需要使用启用了Bootp的虚拟硬盘。

edww · November 26, 2004, 11:01am

BXP IO服务调整

可以通过调整两个注册表键值来调整BXP IO服务，这一更改允许你增加用于处理IO服务请求的线程数。
警告：修改注册表可能导致严重问题甚至可能导致你必须重装操作系统，因此请注意只修改下列指定的注册表键值，由此引起的一切风险由操作者自己承担。
要调试此键值，遵循如下步骤：

在BXP服务器上，运行regedit.exe.
找到下列键值：HKEY_LOCAL_MACHINE\Software\Venturcom\BXP\IOS.
在“编辑”窗口，选择“新建”→“双字节值”
创建一个键值并命名为“InvestigateThreads”，并指定其键值为1
在“编辑”窗口中，选择“新建”→“双字节值”
创建一个注册表键值并命名为“ThreadsPerSocket”，然后指定你想要为每一个连接分配的线程数，默认值为1.
在某些网络条件下，增加为每一个连接使用的线程数将改善IO服务效能。

edww · November 26, 2004, 11:03am

客户端启动模式选项

客户端系统的启动和分配虚拟硬盘的模式可以通过BXP Administrator 的Disk Properties对话框来进行调试，该动作将在BXP客户端下载和执行BXP Bootstrap之后进行，BXP允许为单一客户端系统分配多个硬盘映像，具体使用那个硬盘映像将取决于具体的启动行为。
・ Boot First Disk C 分配给客户端的第一个虚拟硬盘将被用作启动盘，其它分配给客户端的虚拟硬盘将被忽略，如果这一虚拟硬盘无法被访问(譬如IO服务器已关闭)，则客户端将在启动时产生错误信息
・ Boot First Available C 最多可以为一个客户端分配四个虚拟硬盘，当一台客户端PC被设置为“Boot First Available”，它将从列表中选择第一个在线且可以访问的虚拟硬盘作为启动盘，在存在多BXP IO服务器的BXP网络中，该选项通常用于实现“软冗余”。
・ Disk Menu C 当客户端被设置为使用“Disk Menu”模式，在启动时将出现一个可用的虚拟硬盘列表，用户可从中选择某一虚拟硬盘来启动，该菜单由分配给该客户端的所有虚拟硬盘组成，你可以在客户端属性中选择，最多可以允许四个虚拟硬盘。
・ IO Server Least Busy C 该动作备用来在多IO服务器提供相同的镜像给同一客户端的状况，当一个客户端采用这种启动动作，Login服务将根据负载量排列IO服务器队列并选择前几分钟内负载量最小的IO服务器，这有助于在大型的BXP网络中实现IO服务器的负载平衡。

edww · November 26, 2004, 11:04am

BXP客户端域成员资格工具

简介
每一台需要登录域的计算机都需要域控制器提供一个计算机帐号，该帐号及其口令同时存放在域控制器和客户端的本地注册表上，如果这些信息不匹配，用户阿将无法从客户端计算机登录到主域，因此，一旦启用了BXP写过滤，且采用将单一映像提供给多台具有不同计算机名和帐号名的客户端计算机用作启动使用时，这种口令不匹配的现象将会发生。
为修正这一问题而专门编写了一个应用程序，通过在主域控制器上执行它，便可以创建和分配BXP客户端计算机帐号和默认密码“与帐号名相同”，在客户端，必须安装一个服务以便在网络登陆服务之前将计算机帐号设置在本地注册表内，该密码采用同样的加密规则(基于启动时BXP虚拟磁盘驱动所动态分配的计算机名)。
BXP设置计算机帐号应用(BNSetCA)
该工具运行在主域控制器上以创建BXP客户端计算机帐号并更改现存用户的口令分配，使用方法如下：
BNSetCA <计算机名>
<计算机名>是BXP数据库中需要BXP的客户端的名称，该应用程序需要Win2000 Server且必须管理员权限才能运行。
BXP客户端服务(BNClient)
BXP客户端服务必须动态调整包含在默认安装BXP客户端的本地计算机的帐户口令。
默认情况下，计算机帐号口令7天自动更改1次，默认设置必须要调整为允许BXP客户端登陆域，要变更这一设置，在BXP客户端计算机进行如下操作：

在开始菜单里，选择“设置”“→“控制面板”
如果运行WinXP，选择“性能与维护”分类，( Win2000不需要这一步)
选择“管理工具”并找到“本地安全策略”选项
当运行“本地安全策略”时，选择“安全设置“→“本地策略”→“安全选项”并在左面展开分支
在右面的列表中启用如下规则中的一个(取决于使用的操作系统)
・ WinXP：“域成员: 禁止计算机帐号口令变更”
・ Win2000：“防止计算机帐号密码的系统维护”
点击确认以存储变更并关闭窗口。

edww · November 26, 2004, 11:04am

释放客户端硬盘锁定

一旦多客户端和服务器能够访问单一虚拟硬盘映像文件，就必须采取一些访问控制机制以防止映像损坏，一旦一个用户偶然地分配了一个个人映像文件给其它复数客户端并试图由此启动，便可能导致映像损坏，因此，BXP将根据设置锁定映像，而且，在某些情况下这种锁定将无法解除。
当一台客户端PC使用某一虚拟硬盘镜像启动且在启动过程中崩溃或断电，虚拟硬盘映像上的锁定将无法解除，如果该工作站再度启动，同样的锁定将被再次应用而不会导致任何不良后果，无论如何，如果管理员试图在这种情况下将该虚拟硬盘映射到BXP服务器上，由于先前崩溃的工作站的锁定仍然存在，因此服务器将拒绝映射此虚拟硬盘。BXP能够释放此类“死”锁定，如果一个虚拟硬盘被不适当地锁定了，在BXP Administrator中右击选定该虚拟硬盘并选择“Release Image Locks”，这将解除这一映像的所有锁定，执行这一操作前，请务必确保没有别的工作站和服务器正在使用这个映像文件。
如果一个工作站正在使用一个虚拟硬盘映像(待机客户端同样被认为正在使用映像文件)，则映像文件锁定将不会被解除，此时有另一个方法以解除锁定，在BXP Administrator中右击选定工作站,然后选择“Release Client Locks”，该操作将释放指定工作站所使用的任何映像文件的锁定，该操作将在工作站通电启动后的任何时候执行而不用考虑任何危险，当某一特定工作站死机且你只想解除这一特定工作站的锁定时，你可以采用这一操作。

edww · November 26, 2004, 11:08am

设置多播参数
设置多播参数工具允许你调整启动操作的多播部分以合理利用网络资源，在BXP Administrator窗口里高亮IO服务器并在“Tools”菜单里选择“Set Multicast Pacing”工具，这将为指定服务器设置多播参数。

下列相关参数可用：
Maximum Clients Per Session C 设置允许在一次多播进程中启动的客户端台数，如果通过交换机来实现多播，则还可能导致交换机自身的带宽溢出。如果此问题出现，将有大量的坏包(Drop Packet)和无效包(Missing Packet)在多播过程中产生，减少服务器单次多播过程中的工作站数量将减少交换机的多路复用负载并可以控制启动的工作站数量，额外的工作站将被停止直到下一次启动进程。
Packets Outstanding C 设置在每一台客户端得到ACK(正确应答)之前将被多播的包数量，通常传送的包数量是可变的并且能被设置到最大256，一旦自动流量控制(Automatic Flow Control)被关闭，Outstanding包将会是在服务器所等到ACK应答之前所传送的包的总量，如果你的交换机或网络因为多播而瘫痪，减少设置将减轻以客户端启动为代价的网络负载，如果自动流量控制开启,Outstanding包将被控制在流量控制法则指定的流量控制起始点并只造成轻微影响。
Automatic Flow Control C 测定BXP系统是否试图自动发现最优化的Outstanding包设置(当启用时)，或使用一个被Packets Outstanding定义的固定设置值(当禁用时)。

fuckaqxd · November 26, 2004, 12:39pm

很好的翻译，，多谢楼主无私奉献，，真的帮助了很多人，，非常感谢，虽然我也能看懂，，，呵呵，，不过没有楼主的翻译水平，，

moyy · November 26, 2004, 12:44pm

太好了！！！！！！！！！

weixun · November 26, 2004, 1:42pm

OK!好人！好文！谢就一个字！

upleader · November 26, 2004, 1:53pm

真是辛苦了兄弟，我也在翻译中，你的翻译给了我很好的参考，谢谢！
有可能的话能给我全文的翻译么？？谢谢了！
我的email是q12435536@163.com

华英雄 · November 26, 2004, 2:48pm

good,不过希望能翻译一些关键的地方啊,
比如:administrator\工具的使用,虚拟磁盘的类型.
我把一些重要的文档贴出来.希望有志之士
给我们翻译一下.

华英雄 · November 26, 2004, 2:53pm

Disk Properties Dialog

There are three types of disks that can be defined by BXP. The following describes each type.

Standard Virtual Disk - The disk is a standard BXP virtual disk with a virtual disk file residing on an IO server. This type of disk can be used to record an image of a hard drive (using the BNImage utility) and can then subsequently be used to remote boot the a PXE enabled client.

TFTP Chained Bootstrap Disk Template - This disk is a placeholder in the virtual disk assignments to a client workstation. When a client boots from this type of “disk” (usually in response to a disk menu selection) the BXP bootstrap program will load the 3rd party bootstrap program pointed to by this disk’s properties and execute it. In this way, for example, a Linux PXE bootstrap program can be chained to from the BXP bootstrap program. A client can therefore be set up to boot from Windows, Linux, or any other OS that supports PXE boot by simply assigning a TFTP Chained Bootstrap disk pointing to the 3rd party PXE boostrap for the OS you want to boot.

Local Fixed Disk Template - This disk is similar to the TFTP Chained Boostrap Disk Template except that it represents booting from the Local Physical Hard drive of the client. Normally this type of disk is assigned to the client as part of a disk menu. In this way the user can select booting from the local hard drive or from a virtual disk on the BXP server.

Standard Virtual Disk

This dialog box displays the properties of the selected virtual hard drive image file.

Information tab

Server
The name of the BXP IO Server on which the virtual hard drive image file resides.

Size

Active boot partition
Allows the user to set the virtual disk’s boot partition.

Like a regular hard drive, the client PC can only boot from an active boot partition.

Path
The virtual disk image file name and path to the virtual disk directory.

Description
A description of the virtual hard drive image file.

Long Description
A longer description of the virtual hard drive image file, up to 400 characters long.

Class
The class of the disk image. Used in Automatic Disk Image Update and Disk Provisioning to match new disk images and provision files to the client. Up to 40 characters long.

Type
The type of the disk image. Used in Automatic Disk Image Update to match the new image to the old image.

Enable Auto-Update
Enables the Automatic Disk Image Update process on this image file. If yes, the update process will try to find a match for this image on already existing clients and test for an automatic update. If no, this disk image will be ignored by the update process.

Update On
Checkbox to enable the update on date. If checked, the automatic image update process will ignore this image file unless the current system date is greater than or equal to the update on date.

Disk Mode tab

Access Mode
Allows the user to select how this image file will be used. Private Image, Shared Image, or RAM Disk are all supported.

Cache Type
Allows the user to select caching type for Shared Image as either, Client RAM or BXP Server.

Cache Size (MBs)
Allows the user to select cache size in megabytes for Client RAM based Shared Image caching.

Enable Multicast Boot
Allows the user to indicate that this image should be multicast to all clients using it.

Multicast Address
Sets the Multicast IP Address used to multicast this image.

Multicast Time To Live
Sets the Time To Live used in all Multicast Packets. This is normally 1, but should be raised if multicast is being performed through a router.

Invitation Type
Sets the invitation type to either fixed or variable, and invitation period in milliseconds to use when clients request a multicast boot of this image. Fixed invitations stop accepting boot requests in the timeout period from the last client request.

Identification tab

Version (Major, Minor, Build)
Version number for use by the user and also used by the Automatic Disk Image update feature and the Incremental Disk Update feature. With the Automatic Disk Image Update feature, if the new image version > old image version, the disk image will be replaced for matching Class/Type images. Precedence is Major then Minor then Build. With the Incremental Disk Update feature, the delta file version must match the version number of the virtual disk or the delta file will not be applied.

Serial #
Initially set to a random GUID. User can set as needed for their implementation. The Serial # is used in the incremental virtual disk update feature to ensure that a delta file is being applied to a virtual disk file correctly.

Date
For user’s informational use only. Initially set to a string representing the creation date of the image file.

Author
For user’s informational use only. Set as appropriate for your installation.

Title
For user’s informational use only. Set as appropriate for your installation.

Company
For user’s informational use only. Set as appropriate for your installation.

Internal Name
For user’s informational use only. Set as appropriate for your installation.

Original File
For user’s informational use only. Set as appropriate for your installation.

Hardware Target
For user’s informational use only. Set as appropriate for your installation.

TFTP Chained Bootstrap Disk Template

This dialog box allows you to modify the properties of a disk template to chain to a 3rd party bootstrap program.

Disk Name
Enter the name for the chained template disk. The disk name can be a maximum of 127 characters, and can have any extension.

Description
Enter a description for the chained template disk. The description can be a maximum of 50 characters.

Bootstrap Filename
Name of the file residing on the BXP TFTP server which can be used to download the new bootstrap program. For example “linux.0”. This file should be placed in the same folder as the normal BXP bootstrap program (vldrmi13.bin) on your primary BXP server. This folder defaults to “Program files\Venturcom\BXP\TFTPBOOT”

Local Fixed Disk Template

This dialog box allows you to modify the properties of a disk template used to boot from the local physical hard drive of the client.

Disk Name

Enter the name for the local fixed disk template. The disk name can be a maximum of 127 characters, and can have any extension.

Description

Enter a description for local fixed disk template. The description can be a maximum of 50 characters.

华英雄 · November 26, 2004, 2:54pm

Automatic Disk Update

The Automatic Disk Update feature of BXP allows groups of BXP Client machines to be automatically updated to one or more new disk images on a scheduled basis. The new images are usually newer versions of the current image, thereby allowing distribution of newer versions of disk images to one or more sites. The images can be marked to all be activated on a specific day which permits all of your client workstations to update to the new client image software on the same day regardless of when the new image file actually arrived at the site.

The automatic update process takes advantage of the BXP Client and Disk Image properties of Class and Type. A Class can be assigned to both Clients and Disk Images. Additionally, the Disk Image has the additional property, Type. In order for an automatic update to take place, the Class of both the Client and Disk Image must match. Additionally, for a newer disk image to replace an older disk image within a client configuration, the Disk Image Type of both images must match. Since multiple disks can be assigned to each client (in the case of Disk Menu, IO Server Least Busy and First Available boot behaviors), it is necessary to further qualify the old image that will be replaced by the new image. This is the reason for the Type property of the Disk Image. You should never assign more than one disk image from the same IO Server with the same Type to the same client if you want to use the Automatic Disk Image Update feature.

In order to take advantage of the Automatic Disk Update feature of BXP, follow the following procedure:

In the client configurations that will all use the same image file, set the client Class property to a unique class name that reflects the class of image that should be used for these clients. This must match the Image Class in order for a disk to automatically be assigned to these clients.
Set the Class for the initial image file to have the same Class as that assigned to the client(s). If more than one image file is assigned to the client(s), and the image files will reside on the same IO Server, set a different Type in each image file for each image that will be assigned to the same clients. If the same image file is to be used on multiple IO Servers (IO Server Least Busy, First Available) it is permissible to have identical Type properties for each of these image files (they can actually be a copy of the same image file without a problem). This is because the update process uses the Class, Type and IO Server to identify the image to be replaced by a new image.
Set the Disk Image Major Version, Minor Version and Build Number property on all Disk Images to your initial version.
Distribute the initial version and configure your clients normally.
On the BXP Login Server at all of your sites, run the BXP Administrator program. Schedule your automatic disk updates to be applied at the most convenient time of day using the menu selection Tools/Schedule Automatic Disk Updates. Enable the automatic updates using the supplied checkbox and set the time of day you want the update process to run. You can also force an update manually using this same tool by selecting the Check For Updates Now button. From that point on the login service will check for new disk images on all the IO servers configured in the BXP database at the scheduled time of day.
When a new version of the image is needed on your client workstations, create the new image using the standard image creation procedure. You must assign the new image file a name different from the initial image the new image is destined to replace. A version or sequence number appended to each image file would be ideal in this purpose. This new name is necessary because the two images must reside in the same windows virtual disk folder for an indeterminate amount of time. For example:

StandardPOSTerminal.001 ← Initial image file name for a client

StandardPOSTerminal.002 ← Update of image for the same clients

Set the Enable Auto-Update property of the new Image to Yes on the Disk Properties/Information tab. Optionally, check the Update On checkbox and provide a date on which the image should be activated on all clients. Also set the Class and Type of the image to match the Class and Type of the old image that this new image will replace. Set the Major Version, Minor Version, and Build Number to a value that is greater than the old image this new image is destined to replace.

Distribute the new image file to the Virtual Disks folder of the relevant IO Servers at your installations (in the same folders as the old image that the new image is destined to replace). When the automatic update process runs at the scheduled time, the update process will match the new image file to the old image file using the following criteria:

If the Update On property is enabled in the new image, the current local system date is >= the Update On date.

Both images reside on the same IO Server.

The new image Class matches the Class in both the current (old Image) and Client.

The new image Type matches the Type in the current (old Image).

The Version Numbers of the new image are greater than the Version Numbers in the old image. (Precedence of Major then Minor then Build numbers).

On each image match where all of the above criteria are met, the Client is marked to show that a new image file is ready for use by that client. When the client reboots and connects to the login server the next time, the new image file will replace the old image file in the same slot of the client disk configuration and the boot will proceed normally using the new image. Once all clients have been booted once, the old disk image configuration can be deleted if needed. It can also be saved so that the clients can “revert” to the old image in desired.

华英雄 · November 26, 2004, 2:55pm

Installing BXP on Multi-Homed Systems

If your BXP server has more than one network interface card (NIC), make sure that all BXP services are bound to the same NIC. See the table below. The BXP Configuration Wizard will set up all of these services except Bootp.

Configure the…
How…

BXP IO Service
Windows Start menu, Programs Files, Venturcom BXP, BXP IO Service Preferences

BXP Login Service
Windows Start menu, Programs Files, Venturcom BXP, BXP Login Service Preferences

3Com BOOTP Service
3Com BOOTP applet (Windows Control Panel)

3Com PXE Service
3Com PXE applet (Windows Control Panel)

BXP TFTP Service
BXP TFTP applet (Windows Control Panel)

华英雄 · November 26, 2004, 2:56pm

Reducing Network Utilization of Diskless Systems
Background
Windows 2000 and XP provide several features, some are listed below, that presume a large and fast hard disk.

Virtual Memory

Recycle Bin

Offline Folders

Event Logs

Windows XP provides the following new features that make the same presumption.

Hibernation

System Restore

Logical Prefetch

While many of these features can also be useful on a diskless system where the disk is actually on the network, their use decreases cache effectiveness and thereby increases network utilization. In an environment that is sensitive to network utilization, consider reducing the effect of these features by disabling them or adjusting their properties.

In particular, System Restore and Offline Folders are not useful on a diskless system but could be detrimental to the performance of Windows on a diskless system. BXP provides more deterministic, reliable, and simpler restore point than System Restore by simply rebooting the client. Offline Folders cache network files C a feature that is just not applicable to a system where all files are on the network.

All of these features are configurable via the client itself. The following features are configurable via Windows Group Policy.

Offline Folders

Event Logs

Configuring Windows Features on a Shared Virtual Disk via the Client
When configuring any of these features on a shared virtual disk via the client, be sure to use the following procedure.

Prepare a shared virtual disk for configuration.

Shutdown all BXP clients that use the shared virtual disk.

From the BXP Administrator, change the Disk Access Mode to Private Image.

Start one BXP client.

Configure one or more features.

Prepare the a shared virtual disk for Use.

Shutdown the BXP client used to configure the virtual disk.

From the BXP Administrator, change the Disk Access Mode to Shared Image.

Start one or more BXP clients.

Configuring Virtual Memory
On Windows 2000, minimize the virtual memory page size as follows.

Select Start > Settings > Control Panel.

Open System.

Select Advanced > Performance Options > Virtual Memory > Change.

Change the Initial Size to the value of Minimum allowed.

Change the Maximum Size to the value of Minimum allowed.

Press Set.

On Windows XP, disable or minimize the virtual memory page size as follows.

Select Start > Control Panel.

Open System.

Select Advanced > Performance > Settings.

Select Advanced > Virtual Memory > Change.

Choose one of the following.

Disable virtual memory.

Check No paging file.

Minimize virtual memory page size.

Change the Initial Size to the value of Minimum allowed.

Change the Maximum Size to the value of Minimum allowed.

Press Set.

Configuring Recycle Bin
Disabling the Recycle Bin deletes files immediately. Consequently, the file system reuses respective disk sectors and cache entries sooner.

From the desktop or Windows Explorer, right click on Recycle Bin.

Select Properties.

Select Global.

Select the following properties.

Use one setting for all drives

Do not move files to the Recycle Bin.

Remove files immediately when deleted.

Configuring Offline Folders (Strongly Recommended)
Disabling Offline Folders prevents Windows from caching network files on its local disk C a feature with no benefit to a diskless system. Configure this feature via the client or Windows Group Policy.

To configure via the client :
Open Windows Explorer.

Select Tools > Folder Options.

Select Offline Folders.

Uncheck Enable Offline Folders.

To configure via Windows Group Policy:
On the domain controller, use the Microsoft Management Console with the Group Policy snap-in to configure the domain policies for the objects shown in the following paragraphs.

Object
User Configuration \ Administrative Templates \ Network \ Offline Files

Policy
Disable user configuration of Offline Files

Setting
Enabled

Policy
Synchronize all offline files before logging off

Setting
Disabled

Policy
Prevent use of Offline Files folder

Setting
Enabled

Configuring Event Logs
Reduce the maximum size of the Application, Security, and System logs. Configure this feature via the client or Windows Group Policy.

To configure via the client :
Select Start > Settings > Control Panel.

Open Administrative Tools \ Event Viewer.

Open the properties for each log.

Set the Maximum log size to a relatively low value. Consider 512 kilobytes.

To configure via Windows Group Policy:
On the domain controller, use the Microsoft Management Console with the Group Policy snap-in to configure the domain policies for the objects shown in the following paragraphs.

Object
Computer Configuration \ Windows Settings \ Event Log \ Settings for Event Logs

Policy
Maximum Application Log Size

Setting
Relatively low value. Consider 512 kilobytes.

Policy
Maximum Security Log Size

Setting
Relatively low value. Consider 512 kilobytes.

Policy
Maximum System Log Size

Setting
Relatively low value. Consider 512 kilobytes.

Configuring Hibernation
Disabling Hibernation prevents Windows XP from storing memory state in a large disk file (e.g. hiberfil.sys).

On Windows XP, disable Hibernation as follows.

Select Start > Control Panel.

Open Power Options.

Select Hibernation.

Uncheck Enable hibernation.

Configuring System Restore (Strongly Recommended)
Disabling System Restore prevents Windows XP from storing any restore points that result in large disk files. BXP provides an inherent restore feature whenever the client reboots.

On Windows XP, disable System Restore as follows.

Select Start > Control Panel.

Open System.

Select System Restore.

Check Turn off System Restore.

Configuring Logical Prefetcher
Disabling Logical Prefetcher prevents Windows XP from caching additional files.

Set the following registry value to 0 (zero).

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters\EnablePrefetcher

华英雄 · November 26, 2004, 2:58pm

Batch Client Configuration

The Batch Client Configuration Tool is used to configure selected properties of multiple clients simultaneously. The Batch Client Configuration Tool is accessible in the BXP administrator via the Tools/Batch Client Configuration menu option. Using the Batch Client Configuration Tool you can assign disks to clients, remove disks from clients, and set boot behaviors and the client class on large numbers of clients easily.

The main window of the Batch Client Configuration Tool is used to manage batch disk assignments for clients. On the main window you can assign disks or delete disks from clients. The following controls are available:

Batch Mode
Used to select whether to assign a disk to clients or delete a disk from clients. Options are “Assign Disks to Clients” or “Delete Disks from Client”, select as appropriate.

Assign To
Used to modify the assignment behavior when assigning disks to clients. No affect when deleting disks. The following options are available through Assign To:

All Selected Clients C The selected disk is assigned to all clients selected in the Clients window. The Disk Slot control is used to select how the disk is assigned to all clients.

Matching Class and Type in Images of Selected Clients - The selected disk replaces all disks with a matching class and type (to the disk selected in the Disks selection box) in all selected clients. This selection can be used when updating a set of clients to a new version of a disk image. The new image replaces the old image in the client’s configuration.

Matching Class in Selected Clients C The selected disk is assigned to the selected clients if and only if the Class of the client also matches the Class of the image. This selection can be used to assign disks to clients in classes (or groups). The Disk Slot control is used to select how the disk is assigned to the clients once a match occurs.

Disk Slot
Used to select the way a disk is assigned to the client. No affect when deleting disks. No affect when deleting disks. The following options are available through Disk Slot:

Replace All Client Disks - The disk table for each client is cleared and the single selected disk is assigned to the first slot of each client.

Append To Client Disks C The selected disk is appended to the client disk table (if there is room in the table) for each client. Up to four disks can be assigned to each client. Multiple disks on a client can be used for IO Server Least Busy, Disk Menu, and Boot First Available boot behaviors.

Slot 1-4 C The selected disk is assigned to the specific slot in the client disk table. If the slot would be invalid (slot 4 on a client with only 2 disks already assigned) the disk is assigned to the next highest valid slot (slot 3 in the example).

Disks
Used to select the disk to assign or delete to/from the selected clients. Select the disk to assign/delete by clicking on the desired disk.

Clients
Used to select the clients to assign/delete the disk to/from. Multiple clients can be selected and assigned to or deleted from simultaneously. Note that you must always select a set of disks to work with. This set of disks can further be modified by the Assign To control when assigning disks only.

Select All/Clear All
Selects or Clears the selection of all clients in the Client List

Assign/Delete
Once the proper selections are made on the other controls in this window, use the Assign/Delete button to assign or delete the selected disk from the selected clients.

Properties
Used to bring up the Selected Client Properties dialog. This dialog allows you to change certain global (non-disk) properties on a group of clients.

Use this dialog to assign the selected properties to the clients selected in the Clients list box on the right. Only the checked properties will be modified in the selected clients. Additionally, only the clients that are actually selected in the Clients list will have their properties modified. Select he properties to modify and client “Set Properties” to set those properties in the selected clients. See the Client Properties Dialog for more information on the properties configurable with the Selected Client Properties dialog.

edww · November 27, 2004, 7:22am

硬盘属性对话框

在BXP上定义了三种硬盘类型，下面将逐一加以解释：
・ Standard Virtual Disk C 在IO服务器上表现为一个虚拟硬盘映像文件的标准BXP虚拟硬盘，这种虚拟硬盘能被用于记录物理硬盘驱动器的信息(使用BNImage工具)并能被用来远程启动基于PXE的客户端。
・ TFTP Chained Bootstrap Disk Template C 这种硬盘是一个向客户端工作站分配硬盘时的占位符，当客户端从这类“硬盘”引导时(通常用于实现硬盘引导菜单)，BXP Bootstrap程序将载入指向该硬盘属性的第三方Bootstrap程序并执行它，在这种情况下，举例而言，一个基于Linux PXE Bootstrap的程序将被链接到BXP Bootstrap程序上，客户端能被设置为可从Windows/Linux或其它支持PXE的操作系统引导，而这一切只需要简单地更改一下你分配给TFTP所链接的Bootstrap硬盘指向到指定的你想引导的第三方PXE Bootstrap即可。
・ Local Fixed Disk Template C 该硬盘与TFTP链接Bootstrap硬盘模板有些类似，但它指向客户端的本地物理硬盘，通常这种硬盘作为一个菜单项被分配给客户端，这种情况下用户可以选择通过本地硬盘或BXP服务器上的虚拟硬盘来实现引导。
Standard Virtual Disk
该对话框显示选定虚拟硬盘映像文件的属性：

Information页
Server 存放有虚拟硬盘映像文件的BXP IO服务器的名称
Size 大小
Active boot partition 允许用户设置虚拟硬盘引导分区正如一个物理硬盘一样，客户端PC只能从激活的分区进行引导。
Path 虚拟硬盘映像文件名和完整路径
Description 虚拟硬盘映像文件的描述
Long Description 关于虚拟硬盘映像文件的一个较长的描述，支持400个字符长度
Class 硬盘映像的“类”，用于自动映像更新、硬盘批量匹配化和为客户端提供文件使用，最大40个字符
Type 硬盘映像的类别，用于在自动硬盘映像更新时匹配新旧镜像
Enable Auto-Update 在此映像文件上启动硬盘映像自动更新处理，如果选“Yes”，更新处理将试图在已存在的客户端上查找并匹配现存映像文件并试图进行自动更新，如果选“No”，该硬盘映像在更新处理中将被忽略。
Update On 复选以启用根据日期的自动更新，如果该选项选定，除非当前系统日期比更新日期更大或相同，否则自动映像更新处理将忽略该映像文件。

Disk Mode页
Access Mode 允许用户选择如何使用该映像文件，支持私有模式、共享模式和RAM Disk模式
Cache Type 允许用户选择共享模式下的缓存类型，包括客户端RAM和BXP服务器模式
Cache Size (MBs) 在基于客户端RAM的映像缓存模式下允许用户选择缓存容量(以MB为单位)
Enable Multicast Boot 允许用户指出映像是否需要为所有客户端使用多播
Multicast Address 设置用于多播该映像的多播IP地址
Multicast Time To Live 设置所有多播包的生存期，通常为1，但在多播被设置为通过路由器实现时，该值需要被设大一点
Invitation Type 设置请求类型(Invitation Type)为固定(Fixed)或可变(Variable)，当客户端请求一个多播启动该映像时，其请求周期以毫秒为单位计算，固定请求模式下，在最后一台工作站请求的休息周期内停止接受启动请求

Identification页
Version (Major, Minor, Build) 用来给用户、自动硬盘更新特性以及增量硬盘更新特性所使用的版本号，在自动硬盘更新特性下，一旦新映像的版本号高于老版本映像，硬盘映像将被根据Class/Type被替换为新版本，其优先顺序为先Major然后是Minor最后是Build；在增量硬盘更新特性下，“Delta”文件版本号必须和虚拟硬盘相匹配，否则Delta文件将不被应用。
Serial # 起初设置为一个随机的GUID，用户能设置为自己的.Serial #被用于增量硬盘更新特性以确保Delta文件被虚拟硬盘映像文件正确地应用。
Date 仅用于用户信息，起初设置为一个字符串以描述映像文件的创建日期
Author 仅用于用户信息，根据你的安装过程而设置
Title 仅用于用户信息，根据你的安装过程而设置
Company 仅用于用户信息，根据你的安装过程而设置
Internal Name 仅用于用户信息，根据你的安装过程而设置
Original File 仅用于用户信息，根据你的安装过程而设置
Hardware Target 仅用于用户信息，根据你的安装过程而设置

TFTP Chained Bootstrap Disk Template
该对话框允许你调整用于链接到第三方Bootstrap程序的硬盘模板的属性

Disk Name 键入链接模板硬盘的名字，最大127个字符，支持扩展名
Description 键入链接硬盘模板的注释，最大50个字符
Bootstrap Filename 用于在BXP TFTP服务器上提供客户端下载新Bootstrap程序的文件名，譬如：linux.0，该文件必须和标准的BXP Bootstrap文件(vldrmi13.bin)放在同一个目录里，默认状况下该目录是BXP主服务器上的“Program files\Venturcom\BXP\TFTPBOOT”目录
Local Fixed Disk Template
该对话框允许你调整用于指定工作站从本地物理硬盘启动的硬盘模板的属性

Disk Name 键入本地修正硬盘模板的名称，最大127个字符并支持扩展名
Description 键入本地修正硬盘模板的注释，最大50个字符

danies · November 27, 2004, 7:55am

谢谢了楼主。^_^。