关于：打开AD组策略提示项目太长被截断的解释和解决方法
[ 2005/03/08 15:20 | by gOxiA ]
症状
当试图在运行 Microsoft Windows Server 2003、带 Service Pack 1 (SP1) 的 Microsoft Windows XP Professional 或 Microsoft Windows 2000 的计算机上修改或查看组策略对象 (GPO) 时，可能会收到类似以下内容的错误信息：
The following entry in the [strings] section is too long and has been truncated.（下列在 [strings] 节中的项目太长，被截断。）
此错误信息后面可能会显示某些文本，这些文本在不同情况下会有所不同。另外，如果在错误信息窗口中单击“确定”，则可能会重复出现类似的错误信息。每条重复的错误信息后面都会显示不同的文本。
原因
发生此问题的原因是：组策略编辑器的较早版本无法解释某些包含多于 255 个字符的字符串类型。这些字符串类型包含在将被“IF VERSION”构造排除的 .adm 文件中。
通常，当您试图查看或修改已由其他工作站查看的 GPO，而该工作站包含使用“IF VERSION >=5”构造的 .adm 文件时，会发生此问题。当管理工作站查看 GPO 时，该工作站会自动使用最新版本的 .adm 文件更新该 GPO。如果工作站的 .adm 文件比域 GPO 的 \Adm 文件夹中包含的文件新，则更新模板文件。如果模板文件包含“IF VERSION >=5”构造，当管理工作站试图修改或查看 GPO 且该工作站未安装此修复程序时，将出现错误。
注意：Microsoft Windows XP Service Pack 2 (SP2) 中包含使用“IF VERSION >=5”构造的管理模板 (.adm) 文件。当使用较早版本的组策略编辑器修改某些组策略设置时，此构造可以防止这些设置中的意外行为。
Windows2000 SP3或更高版本：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=ba478b46-3af7-4eaf-9ce6-e34ea2c74faf
WindowsXP SP1：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=3c599574-0f8d-4c2c-b3be-ebf3fb041214
Windows2003：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=532a4cd0-f2ce-4fa7-92ab-ac336ad18409
原文地址：http://support.microsoft.com/default.aspx?scid=kb;zh-cn;842933
当试图在运行 Microsoft Windows Server 2003、带 Service Pack 1 (SP1) 的 Microsoft Windows XP Professional 或 Microsoft Windows 2000 的计算机上修改或查看组策略对象 (GPO) 时，可能会收到类似以下内容的错误信息：
The following entry in the [strings] section is too long and has been truncated.（下列在 [strings] 节中的项目太长，被截断。）
此错误信息后面可能会显示某些文本，这些文本在不同情况下会有所不同。另外，如果在错误信息窗口中单击“确定”，则可能会重复出现类似的错误信息。每条重复的错误信息后面都会显示不同的文本。
原因
发生此问题的原因是：组策略编辑器的较早版本无法解释某些包含多于 255 个字符的字符串类型。这些字符串类型包含在将被“IF VERSION”构造排除的 .adm 文件中。
通常，当您试图查看或修改已由其他工作站查看的 GPO，而该工作站包含使用“IF VERSION >=5”构造的 .adm 文件时，会发生此问题。当管理工作站查看 GPO 时，该工作站会自动使用最新版本的 .adm 文件更新该 GPO。如果工作站的 .adm 文件比域 GPO 的 \Adm 文件夹中包含的文件新，则更新模板文件。如果模板文件包含“IF VERSION >=5”构造，当管理工作站试图修改或查看 GPO 且该工作站未安装此修复程序时，将出现错误。
注意：Microsoft Windows XP Service Pack 2 (SP2) 中包含使用“IF VERSION >=5”构造的管理模板 (.adm) 文件。当使用较早版本的组策略编辑器修改某些组策略设置时，此构造可以防止这些设置中的意外行为。
Windows2000 SP3或更高版本：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=ba478b46-3af7-4eaf-9ce6-e34ea2c74faf
WindowsXP SP1：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=3c599574-0f8d-4c2c-b3be-ebf3fb041214
Windows2003：
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=532a4cd0-f2ce-4fa7-92ab-ac336ad18409
原文地址：http://support.microsoft.com/default.aspx?scid=kb;zh-cn;842933
Vmware官方关于群集中共享磁盘的设置方法及说明
[ 2005/03/08 14:44 | by gOxiA ]
Enabling SCSI Reservation
SCSI reservation must be enabled in a virtual machine before you can share its disks. To enable it, make sure the virtual machine is powered off. Open the configuration file (.vmx file on Windows hosts, .cfg file on Linux hosts) in a text editor and add the line scsi[n].sharedBus = "virtual" anywhere in the file, where [n] is the SCSI bus being shared.
VMware recommends you set up the shared disks on their own SCSI bus, which is a different bus than the one the guest operating system uses. For example, if your guest operating system is on scsi0:0, you should set up disks to share on scsi1 bus.
For example, to enable SCSI reservation for devices on the scsi1 bus, add the following line to the virtual machine's configuration file:
scsi1.sharedBus = "virtual"
This gives the whole bus the ability to be shared. However, if you would rather not share the whole bus, you can selectively enable SCSI reservation for a specific SCSI disk on the shared bus. This prevents the locking of this specific disk. Add the following line to the configuration file:
scsi1:1.shared = "true"
If SCSI reservation is enabled (that is, scsi1.sharedBus is set to "virtual"), then this setting is ignored.
In addition to enabling SCSI reservation on the bus, you need to allow virtual machines to access the shared disk concurrently. Add the following line to the virtual machine's configuration file:
disk.locking = "false"
This setting permits multiple virtual machines to access a disk concurrently. Be careful though; if any virtual machine not configured for SCSI reservation tries to access this disk concurrently, then the shared disk is vulnerable to corruption or data loss.
When SCSI reservation is enabled, a reservation lock file that contains the shared state of the reservation for the given disk is created. The name of this file consists of the filename of the SCSI disk appended with .RESLCK.
For example, if the disk scsi1:0.filename is defined in the configuration file as
scsi1:0.fileName = "/
then the reservation lock file for this disk is given the default name
"/
However, you can provide your own lock file name. Add a definition for scsi1:0.reslckname to the configuration file. For example, if
scsi1:0.reslckname = "/tmp/scsi1-0.reslock"
is added to the configuration file, it overrides the default lock file name.
Selecting the Disk
Once SCSI reservation is enabled for a disk — that is, the scsi[n].sharedBus = "virtual" and disk.locking = "false" settings are added to the configuration file for each virtual machine wanting to share this disk, you need to point to this disk for each virtual machine that wants to access it.
Sharing a Disk on the scsi0 Bus
VMware does not recommend sharing a disk on SCSI bus 0.
SCSI reservation must be enabled in a virtual machine before you can share its disks. To enable it, make sure the virtual machine is powered off. Open the configuration file (.vmx file on Windows hosts, .cfg file on Linux hosts) in a text editor and add the line scsi[n].sharedBus = "virtual" anywhere in the file, where [n] is the SCSI bus being shared.
VMware recommends you set up the shared disks on their own SCSI bus, which is a different bus than the one the guest operating system uses. For example, if your guest operating system is on scsi0:0, you should set up disks to share on scsi1 bus.
For example, to enable SCSI reservation for devices on the scsi1 bus, add the following line to the virtual machine's configuration file:
scsi1.sharedBus = "virtual"
This gives the whole bus the ability to be shared. However, if you would rather not share the whole bus, you can selectively enable SCSI reservation for a specific SCSI disk on the shared bus. This prevents the locking of this specific disk. Add the following line to the configuration file:
scsi1:1.shared = "true"
If SCSI reservation is enabled (that is, scsi1.sharedBus is set to "virtual"), then this setting is ignored.
In addition to enabling SCSI reservation on the bus, you need to allow virtual machines to access the shared disk concurrently. Add the following line to the virtual machine's configuration file:
disk.locking = "false"
This setting permits multiple virtual machines to access a disk concurrently. Be careful though; if any virtual machine not configured for SCSI reservation tries to access this disk concurrently, then the shared disk is vulnerable to corruption or data loss.
When SCSI reservation is enabled, a reservation lock file that contains the shared state of the reservation for the given disk is created. The name of this file consists of the filename of the SCSI disk appended with .RESLCK.
For example, if the disk scsi1:0.filename is defined in the configuration file as
scsi1:0.fileName = "/
then the reservation lock file for this disk is given the default name
"/
However, you can provide your own lock file name. Add a definition for scsi1:0.reslckname to the configuration file. For example, if
scsi1:0.reslckname = "/tmp/scsi1-0.reslock"
is added to the configuration file, it overrides the default lock file name.
Selecting the Disk
Once SCSI reservation is enabled for a disk — that is, the scsi[n].sharedBus = "virtual" and disk.locking = "false" settings are added to the configuration file for each virtual machine wanting to share this disk, you need to point to this disk for each virtual machine that wants to access it.
Sharing a Disk on the scsi0 Bus
VMware does not recommend sharing a disk on SCSI bus 0.
Mysql在Windows平台下的群集实现
[ 2005/03/08 13:59 | by gOxiA ]
自打Windows2003群集经历波折最终成功建立后，IIS的群集建立几乎没有遇到什么阻碍。于是拟建立Mysql的群集，去了官方站点看了看发现都是Linux下建立群集的资料，于是在QQ群组上咨询了朋友，才得知Mysql在Windows下建立群集是可行的。唯一需要特别设置的是要采用“通用服务”建立Mysql的群集资源。
首先，建立一个群集组，命名为Mysql Cluster；之后建立一个地址：192.168.80.155；之后建立一个网络名称：Mysql；最后建立通用服务：建立Mysql服务和Mysql启动命令。
呵呵，回想一下真的很简单。不过有几点很关键：
1、Mysql-4.1.10-Win32如果使用手工安装方式真的很复杂，所以我下载了集成版，发现mysql的安装已经非常人性化，设置也方便的多了，我选择将数据库放在磁盘阵中，名称为Mysql datafiles。
2、自动安装后，mysql是以服务运行的，而且是自动运行，所以需要将启动方式改为手工，这样做是为了方式节点同时打开后有一个节点会出现mysql启动失败的警告，并且这样做也是讲mysql的启动权交给了群集服务来管理，当哪个节点优先就会开启这个节点的Mysql服务。
这样，mysql的群集就做好了，关键是帐号部分的数据如何实现群集，也就是说当建立一个帐号的时候，他被默认存储在mysql的安装盘中而非磁盘阵里。这个问题还需要再想想找找解决方案。
首先，建立一个群集组，命名为Mysql Cluster；之后建立一个地址：192.168.80.155；之后建立一个网络名称：Mysql；最后建立通用服务：建立Mysql服务和Mysql启动命令。
呵呵，回想一下真的很简单。不过有几点很关键：
1、Mysql-4.1.10-Win32如果使用手工安装方式真的很复杂，所以我下载了集成版，发现mysql的安装已经非常人性化，设置也方便的多了，我选择将数据库放在磁盘阵中，名称为Mysql datafiles。
2、自动安装后，mysql是以服务运行的，而且是自动运行，所以需要将启动方式改为手工，这样做是为了方式节点同时打开后有一个节点会出现mysql启动失败的警告，并且这样做也是讲mysql的启动权交给了群集服务来管理，当哪个节点优先就会开启这个节点的Mysql服务。
这样，mysql的群集就做好了，关键是帐号部分的数据如何实现群集，也就是说当建立一个帐号的时候，他被默认存储在mysql的安装盘中而非磁盘阵里。这个问题还需要再想想找找解决方案。
