00_Index_CP_R75_Management_Essentials_Part1_v01
windows7配置MariaDB（zip免安装）的手动安装与使用
windows7配置MariaDB（zip免安装）的手动安装与使用介绍MariaDB数据库管理系统是MySQL的一个分支，主要由开源社区在维护，采用GPL授权许可。
开发这个分支的原因之一是：甲骨文公司收购了MySQL后，有将MySQL闭源的潜在风险，因此社区采用分支的方式来避开这个风险。
MariaDB的目的是完全兼容MySQL，包括API和命令行，使之能轻松成为MySQL的代替品。
在存储引擎方面，10.0.9版起使用XtraDB（名称代号为Aria）来代替MySQL的InnoDB。
MariaDB由MySQL的创始人麦克尔·维德纽斯主导开发，他早前曾以10亿美元的价格，将自己创建的公司MySQL AB卖给了SUN，此后，随着SUN被甲骨文收购，MySQL的所有权也落入Oracle的手中。
MariaDB名称来自麦克尔·维德纽斯的女儿玛丽亚（英语：Maria）的名字。
MariaDB直到5.5版本，均依照MySQL的版本。
因此，使用MariaDB5.5的人会从MySQL 5.5中了解到MariaDB的所有功能。
从2012年11月12日起释出的10.0.0版开始，不再依照MySQL 的版号。
10.0.x版以5.5版为基础，加上移植自MySQL 5.6版的功能和自行开发的新功能。
Linux、维基媒体基金会等机构都已经加入到支持 MariaDB 的阵营。
以上信息来自维基百科 /zh-hans/MariaDB下载MariaDB https://downloads.MariaDB 10.4.7, 10.3.17, 10.2.26, 10.1.41 and 5.5.65 now available如果不想安装，可以下载 mariadb-10.2.10-winx64.zip 免安装版，如果下载 MSI 版以下内容可以忽略。
解压到磁盘 D:\mariadb\10.2.10安装服务创建一个批处理 install.bat 用于将 MariaDB 安装为服务1.::指定创建服务的程序2.@setmysql_service="d:\mariadb\10.2.10\bin\mysqld.exe"3.::设置服务名4.@set service_name="MariaDB.10"5.6.::开始安装Mariadb服务7.%mysql_service% --install %service_name% --defaults-file="d:\mariadb\10.2.10\my-medium.ini"8.9.pause顺便再创建一个移除服务的批处理 uninstall.bat1.@set mysql_service="d:\mariadb\10.2.10\bin\mysqld"2.@set service_name="MariaDB.10"3.4.:: 卸载服务5.%mysql_service% --remove %service_name%6.7.paused:\mariadb\10.2.10 目录内有几个ini 文件，这里使用 my-medium.ini 作为服务端的配置，根据需求的不同，还可以选择 my-small.ini 轻量化配置，或者 my-large.ini 以强化性能。
1075从属服务不存在或已经标记...
Windows错误代码大全332640000 操作已成功完成。
0001 错误的函数。
0002 系统找不到指定的文件。
0003 系统找不到指定的路径。
0004 系统无法打开文件。
0005 拒绝访问。
0006 句柄无效。
0007 存储区控制块已损坏。
0008 可用的存储区不足，无法执行该命令。
0009 存储区控制块地址无效。
0010 环境错误。
0011 试图使用不正确的格式加载程序。
0012 访问代码无效。
0013 数据无效。
0014 可用的存储区不足，无法完成该操作。
0015 系统找不到指定的驱动器。
0016 无法删除该目录。
0017 系统无法将文件移到其他磁盘驱动器上。
0018 没有其他文件。
0019 媒体写保护。
0020 系统找不到指定的设备。
0021 设备尚未准备好。
0022 设备无法识别该命令。
0023 数据错误（循环冗余检查）。
0024 程序发出命令，但是该命令的长度错误。
0025 驱动器在磁盘上无法定位指定的区域或磁道。
0026 无法访问指定的磁盘或软盘。
0027 驱动器找不到所请求的扇区。
0028 打印机缺纸。
0029 系统无法写入指定的设备。
0030 系统无法读取指定的设备。
0031 与系统连接的设备不能正常运转。
0032 其他进程正使用该文件，因此现在无法访问。
0033 另一进程已锁定该文件的某一部分，因此现在无法访问。
0034 驱动器中的软盘不正确。
请将 %2 （卷标序列号: %3）插入驱动器 %1。
0036 打开共享的文件太多。
0038 已到达文件结尾。
0039 磁盘已满。
0050 不支持此网络请求。
0051 远程计算机无法使用。
0052 网络中存在重名。
0053 找不到网络路径。
0054 网络正忙。
0055 指定的网络资源或设备已不可用。
0056 已经达到网络命令的极限。
0057 网络适配器出现错误。
0058 指定的服务器无法执行所请求的操作。
0059 网络出现意外错误。
0060 远程适配器不兼容。
centos7安装mysql5.5的方法
centos7安装mysql5.5的⽅法⾸先centos7 已经不⽀持mysql，因为收费了你懂得，所以内部集成了mariadb，⽽安装mysql的话会和mariadb的⽂件冲突，所以需要先卸载掉mariadb，以下为卸载mariadb，安装mysql的步骤。
#列出所有被安装的rpm packagerpm -qa | grep mariadb#卸载rpm -e mariadb-libs-5.5.37-1.el7_0.x86_64错误：依赖检测失败：libmysqlclient.so.18()(64bit) 被 (已安裝) postfix-2:2.10.1-6.el7.x86_64 需要libmysqlclient.so.18(libmysqlclient_18)(64bit) 被 (已安裝) postfix-2:2.10.1-6.el7.x86_64 需要#强制卸载，因为没有--nodepsrpm -e --nodeps mariadb-libs-5.5.37-1.el7_0.x86_64#安装mysql依赖yum install vim libaio net-tools#安装mysql5.5.39的rpm包rpm -ivh /home/liwei/MySQL-server-5.5.39-2.el6.x86_64.rpm rpm -ivh /home/liwei/MySQL-client-5.5.39-2.el6.x86_64.rpm #拷贝配置⽂件cp /usr/share/mysql/f /etc/f，改名为f作为mysql配置⽂件。
#修改响应的配置⽂件vim /etc/f#把mysql的data拷贝到制定的⽬录mv /var/lib/mysql /home/mysql/data/还要注意⽬录的属主和权限。
MYSQL启动后报：ERROR! The server quit without updating PID file错误的问题解决 MYSQL⽇志：Can't find file:'./mysql/plugin.frm' (errno: 13 - Permission denied)1、权限不够：chown -R mysql:mysql /home/mysql/data” “chmod -R 755 /home/mysql/data2、centos7的selinux问题：打开/etc/selinux/config，把SELINUX=enforcing改为SELINUX=disabled后存盘退出重启机器。
Ghost所有运行错误代码
Ghost所有运行错误代码Ghot所有运行错误代码完全大揭秘使用Ghot时，发生错误，Ghot会返回一个错误代码给用户，很多人并不知道代码的意思。
现在把它们一一列出，供大家在使用中参考，以做到对症下药，排除故障。
错误代码:10000原因或对策:不正确的路径/文件语法。
请确保路径及文件名是否正确，同时确定如果你正在网络上建立映像文件你是否有写权限。
错误代码:10001原因或对策:使用者放弃了操作。
错误代码:10060错误代码:10082原因或对策:Ghot的共享版本已过期，必须购买才能够使用。
错误代码:10170原因或对策:拒绝检查映像文件或磁盘。
请使用更新的版本以解决此问题。
错误代码:10180原因或对策:硬盘没有响应。
请检查电缆线、电源连接、跳线及基本输出入单元(BIOS)设置。
确定你的系统已经由FDISK给硬盘正确分了区。
错误代码:10210原因或对策:无效的扩充分区信息，可能你的硬盘分区已经被硬盘压缩软件压缩。
如果它们是由此类型的驱动器所控制，Ghot无法完全将硬盘定位。
请先把分区解压缩，再执行Ghot程序。
错误代码:10220原因或对策:返回这个错误代码，是因为你正在Window的Do窗口下执行Ghot程序。
请试着在纯DOS下使用Ghot，最好用DOS盘启动机器，然后再执行Ghot程序。
错误代码:10600原因或对策:Ghot无法适当地继续由于缺乏内存，请参阅下面15040错误代码。
错误代码:11000原因或对策:无效的备份映像文件，请重新指定备份映像文件。
错误代码:12080原因或对策:一般是企图在网络之上克隆磁盘对磁盘所致。
Ghot仅仅能够通过NetBIOS协议在网络上进行磁盘对磁盘克隆操作。
错误代码:12090原因或对策:读取或写入硬盘发生错误，请尝试先扫描硬盘，并修复操作再执行Ghot。
错误代码:14030原因或对策:未注册的Ghot版本遭遇文件的日期超过它的终止日期，请购买新的Ghot版本。
CentOS 7 安装配置SAMBA服务器及权限配置
Samba服务器是我们常用文件资源共享服务器，Samba服务器配置多种多样，可以根据不同用户或用户组访问不同目录进行配置。
下面开始讲解配置流程1、安装Samba服务器# yum -y install samba samba-client samba-common//或者使用rpm安装#rpm -ivh samba-4.1.1-37.el7_0.src.rpm2、创建共享目录#mkdir /smb3、配置内核参数# ulimit -n 16384# vi /etc/security/limits.conf#在最后加入以下内容* - nofile 16384Tip: 这主要是避免在启动Samba时出现以下警告信息：rlimit_max: increasing rlimit_max (1024) tominimum Windows limit (16384) 4、配置Samba参数#cd /etc/samba#mv smb.conf smb.conf.bf#touch smb.conf#vi smb.conf将下面内容复制进去[global]workgroup=WORKGROUPnetbios name=Amapleserver string=Samba Server#security=sharesecurity=usermap to guest = Bad User[share]path = /smbpublic = nowritable = yeswrite list = @sambavalidusers = @samba如果需要根据不同用户进入不同目录用share参数修改为[Share]path = /smb/%upublic = nowritable = yeswrite list = @sambavalidusers = @samba如果需要开启公共区域可以在share后面追加，根据需要开启[Public]path=/smb/docsreadonly=yesbrowseable=yesguest ok=yes5、创建用户组# groupadd samba6、创建用户# useradd -g samba amapleuseradd -g samba samba7、创建SAMBA用户# smbpasswd -a amaple8、赋值目录权限# chown samba:samba /smb# chmod 770 /smb9、启动samba服务器sysctltem start samaba然后在windows测试下如果不行关闭下防火墙和selinux 如果选择的是根据不同用户进入不同目录用share参数修改为10、创建用户目录mkdir /smb/amaple# chown amaple:samba /smb# chmod 755 /smb/amaple如果会setfacl建议用该它进行设置权限更加妥当，还有可以搭配mount目录挂载使用更加方便。
V5R2M0 Electronic Service Agent for iSeries 常见问题解答
Frequently Asked Questions forV5R2M0 Electronic Service Agent for iSeriesQ1: Where can I get media for the Electronic Service Agent product (5798-RZG)?A1: New systems leaving IBM from manufacturing will have Electronic Service Agent preloaded on the iSeries system. OS/400 upgrades will have the product included with theOS/400 software order on the B29XX_07 standard set products CD-ROM where XX is the language id.For systems where the product is not preloaded and the install media is not readily accessible, a separate Electronic Service Agent V5R2M0 CD-ROM will be available at V5R2 GA. IBM Service Representatives (SSRs) can order this CD-ROM (SK3T-4116-01) through IBM Publications.Q2: Are there any migration instructions if I am upgrading my iSeries system from V4R5 orV5R1 to V5R2?A2: Yes. If you SLIP install V5R2, the Service Agent inventory collection task created within Management Central will exist along with the QYSDDIAL TCP/IP connection profile, so you will not have to recreate them. However, you will need to accept the license agreement for inventory collection via the Extreme Support wizard. For hardware problem reporting, you will need to obtain an activation password from your IBM Service Representative (SSR) and accept the license agreement.Q3: Why does LODRUN fail when I try to install Service Agent?A3: The methods to install Service Agent from CD-ROM are the Restore Licensed Program command (RSTLICPGM) or Install Licensed Programs (GO LICPGM option 11).Message CPF3717 is generated if LODRUN is attempted.Q4: Why do I need to use a user profile for Inventory setup that has a *SECOFR user class but not the actual QSECOFR user profile?A4: The operating system has a submit job restriction that does not allow batch jobs to be submitted in the name of system supplied user profiles, such as QSECOFR. However, for Management Central purposes, the QSECOFR user profile must be enabled.If a collection task is created by QSECOFR, the inventory collection task will be started by the QSECOFR user profile and the data will be collected normally. After collection, Management Central will attempt to submit a QYIVRIPS job to be run in the QSVCDRCTR subsystem to send the inventory data. The operating system will not allow the QYIVRIPS job to be submitted because of the submit job restriction. Message CPD1617 (‘Value specified for USER parameter not correct.’) will be generated.Q5: How do I activate Service Agent functions?A5: For existing Service Agent customers, hardware problem reporting is activated by entering GO SERVICE on a command line. You will need an activation password from your IBM ServiceRepresentative (SSR). System inventory collection and transmission is activated using iSeries Navigator and the Extreme Support Wizard under Management Central.Q6: In prior releases of Service Agent, I needed to set up a locale object to make sure the time information for the scheduled task and history panel was correct. Is that still necessary for Service Agent?A6: Although the use of an OS/400 locale object is no longer necessary for Service Agent, we recommend you make sure the system value for time (QTIME) and the system value QUTCOFFSET are set correctly for your time zone. Changes may need to be made during the calendar year for the beginning and ending of Daylight Savings Time to ensure continuity of the task operations and history panel information.Q7: In V5R2 iSeries Navigator, what additional options are available to the Electronic Service Agent object under Management Central’s Extreme Support?A7: The additional V5R2 options are listed below. To view all of the options, expand Extreme Support and click Agents. Right click on the Electronic Service Agent object.!Using the “Configure Electronic Services” option you can register existing IBM ids to the Service Agent Information site to view your system’s inventory information. If you do not!!The history panel can be refreshed using F5 or from a drop-down option from the history panel.!You can start and stop job logging of all jobs that are run by user id QSVCDRCTR.Q8: Are there new or updated inventory selections for Service Agent?A8: Yes. V5R2 Service Agent sends Group PTF information (part of the PTF inventory) as well as Software Audit information (part of Software Inventory). Service Agent can also send the System Registration information. The System Registration wizard is located in the Configuration and Service section of iSeries Navigator. Sending this information and registering your iSeries system with IBM will help make future service calls to IBM faster and more productive.Q9: Does Service Agent send all of my system inventory to IBM each time it transmits?A9: No. After the first transmission of all of your selected inventories, Service Agent will only transmit system inventory if any part of that inventory has changed since the last time Service Agent transmitted. In V5R2, for PTF inventory and Software Resource inventory, Service Agent will only transmit the specific changes, and not the entire inventory.Q10: When I tried to do Inventory -> Collect, I did not get the option to send the Service Agent information. Has there been a change?QQ11: How can I set up Service Agent to report problems from a central system to IBM for other iSeries systems or secondary partitions in my network?A11: For hardware problem reporting, the products needed for this function are Electronic Service Agent (5798RZG) and System Manager for iSeries (57xxSM1) which is fee based software.System Manager for iSeries gives your central system or main partition the ability to report hardware failures on behalf of the iSeries systems or other partitions in your network.The link below to an IBM Software Knowledge Base document provides the information toQ12: How can I set up Service Agent to send inventory information from a central system to IBM for other iSeries systems or secondary partitions in my network?A12: For inventory transmission, Management Central allows collection from other iSeries systems or secondary partitions and transmission from the central system. You must have Service Agent installed on the secondary partitions or iSeries systems. The OS/400 release running on the central system determines the types of inventory to be sent since new collection capabilities have been added over the past two OS/400 releases.Q13: During Service Agent setup, I am having problems starting the Management Central server jobs and connecting to Management Central. What should I do?A13: We recommend this excerpt from the Management Central FAQs.You will need to perform some troubleshooting. The problem is most likely a TCP/IP configuration problem on the host. The following TCP/IP related questions should be answered.• Has TCP/IP been configured (CFGTCP) on your iSeries systems in the network?• Has TCP/IP been started (STRTCP) on your iSeries systems in the network?• Can you 'ping' the host from the client or another iSeries?• Can you 'ping' the client from the iSeries?• Can you 'ping' other iSeries systems in your network from the client and from the iSeries?• If you are using a Domain Name Server (DNS), both short and long names for the system in your network must be there and entered correctly.• If you are not using a DNS, the host table for both short and long name(CFGTCP, option 10) must be there and entered correctly. For example, a commonpractice is to define a long name that conveys the networkorganization and to also define a short name such as SYS1 that is easier to remember.!Is the domain information listed in CFGTCP, option 12 specified correctly?Host name (ex: SYS1) and domain name (ex: )• Is there a port conflict? Management Central uses port 5555 (NETSTAT, option 3.) You can also view the Service Entry Table (CFGTCP, opt 21, opt 1) to identify portassignments. Management Central has three port numbers assigned to it. Non-SSLservice as-mgtctrl is port 5555, SSL service as-mgtctrl-cs is port 5577 and SSL serviceas-mgtctrl-ss is port 5566. If these are not defined in the service table, add them.The protocol is TCP.• Starting in V5R1, Management Central added a java server job (QYPSJSVR) to support java function on the GUI. In order for this java server to run, the QSECOFR user profile must NOT be disabled.If the above troubleshooting steps do not solve the problem, contact your IBM Software Support Center.Q14: Are there problem determination steps for Service Agent inventory problems?A14: Yes. The following diagram steps through a general problem determination process.Q15: When I take option 19 to Display Service Agent audit log using the Service Agent Main Menu (GO SERVICE), my screen does not automatically go to the bottom of the file for the most recent entries as in past releases. Has there been a change?A15: Yes. The audit log file has been changed for easier code page translation and is displayed using SQL. On the ‘Position to line’ field, you can enter the letter B to get to the bottom of the file for the most recent audit log entries.Q16: When I look at the job schedule entries (WRKJOBSCDE) on my system, there is a QSDAUTOTST job schedule entry. What is that entry used for?A16: QSDAUTOTST is the Service Agent automated operational test which is an integral part of V5R2. This scheduled job will send a test to the service provider every 91 days for verification purposes. Day of the week and time settings can be modified using option 1 ‘Change Service Agent Settings’ from the Service Agent Main Menu (GO SERVICE).Q17: The V5R2 AUTOPTF function has been requesting a different informational APAR than in prior releases. Has there been a change?A17: Yes. The new informational APAR used for AUTOPTF at V5R2 is II12806.Q18: Why is there a new JV1 requirement for V5R2 systems running Service Agent Inventory Collection and Transmission?A18: The V5R2 IBM Developer Kit for Java has been updated. To comply with licensing requirements and to ensure V5R2 Service Agent will function, the update must be applied to user systems.The OS/400 product 5722JV1 (IBM Developer Kit for Java) and its option 5 (Java Developer Kit 1.3) need to be restored from the operating system CD B29XX_08, where XX is the two digit language identifier. No IPL or activation of Java code is necessary.This change affects new and existing V5R2 Electronic Service Agent inventory configurations.。
win2003安装sqlserver2005的方法-电脑资料
win2003安装sqlserver2005的方法-电脑资料复制代码代码如下:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows \\CurrentVersion]"ProductId"="69713-640-9722366-45198"[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion]"CurrentBuild"="1.511.1 () (Obsolete data - do not use)""InstallDate"=dword:3f6c976d"ProductName"="Microsoft Windows Server 2003""RegDone"="""SoftwareType"="SYSTEM""CurrentVersion"="5.2""CurrentBuildNumber"="3790""BuildLab"="3790.srv03_rtm.030324-2048""CurrentType"="Uniprocessor Free""ProductId"="69713-640-9722366-45198""DigitalProductId"=hex:a4,00,00,00,03,00,00,00,36,39,37,31, 33,2d,36,34,30,2d,\\39,37,32,32,33,36,36,2d,34,35,31,39,38,00,5a,00,00,00,41,32, 32,2d,30,30,30,\\30,31,00,00,00,00,00,00,00,00,e5,3f,e9,6a,2c,ed,25,35,12,ec,1 1,c9,8d,01,00,\\00,00,00,00,37,03,6d,3f,44,22,06,00,00,00,00,00,00,00,00,00,0 0,00,00,00,00,\\00,00,00,00,00,00,00,00,00,00,00,31,32,32,32,30,00,00,00,00, 00,00,00,dc,0f,\\00,00,bf,4a,94,6c,80,00,00,00,15,18,00,00,00,00,00,00,00,00,0 0,00,00,00,00,\\00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,34,79,ca, d7"LicenseInfo"=hex:71,84,c7,56,a0,d6,10,6e,70,b4,9f,e9,10,1a, 1e,7a,01,a4,41,09,\\25,20,0e,80,83,80,1f,31,27,86,64,1f,31,dc,22,af,f7,7d,aa,e4,2a, b9,e5,e3,6c,\\e2,01,69,85,70,91,be,a7,9f,95,e5QQ空间搜狐微博人人网开心网百度搜藏更多Tags：win2003 sqlserver 2005复制链接收藏本文打印本文关闭本文返回首页上一篇：sql 版本详解让你认识跟sql2000的区别下一篇：SQL SERVER 2000通讯管道后复用劫持相关文章2013-04-04sql server多行数据拼接的实例方法2007-11-11用SQL语句实现随机查询数据并不显示错误数据的方法2013-03-03sql语句中单引号,双引号的处理方法2013-01-01SQL Server误区30日谈第25天有关填充因子的误区2013-07-07在SQL Server的try...catch语句中获取错误消息代码的的语句2012-11-11H2 数据库导入CSV文件实现原理简析2008-12-12批量执行sql语句的方法2013-11-11SQLSERVER数据库升级脚本图文步骤2013-01-01SQL Server简单模式下误删除堆表记录恢复方法(绕过页眉校验)2007-03-03使用SQL Server数据库嵌套子查询的方法文章评论最近更新sql实现修改表字段名的方法详解还原sql server数据库的处理方法mssql 建立索引SQL Transcation的一些总结分享SQLSERVER 本地查询更新操作远程数据库的SQLServer 数据库变成单个用户后无法访问sqlserver 触发器教程SQLserver中用convert函数转换日期格式的简化SQL Server备份与还原到云工作原理及将Reporting services的RDL文件拷贝到另外热点排行SQL Server 2008图文安装教程SQL Server 2012 安装图解教程(附sqlserver中distinct的用法(不重SQL Server导入、导出、备份数据SQL语句去掉重复记录，获取重复记SQL Server数据库入门学习总结SQL Server错误代码大全及解释（sql convert函数使用小结sql 时间函数整理的比较全了用SQL语句添加删除修改字段、一些。
Windows NT 错误代码(一)
88L ERROR_NET_WRITE_FAULT 在网络上出现写错误。
89L ERROR_NO_PROC_SLOTS 此时，系统无法启动另一个进程。
100L ERROR_TOO_MANY_SEMAPHORES 无法创建另一个系统信号灯。
21L ERROR_NOT_READY 驱动器没有准备好。
22L ERROR_BAD_COMMAND 设备不识别命令。
23L ERROR_CRC 数据错误（循环冗余检查）。
24L ERROR_BAD_LENGTH 程序提供了一个命令，但命令长度不正确。
39L ERROR_HANDLE_DISK_FULL 磁盘已满。
50L ERROR_NOT_SUPPORTED 网络请求不受支持。
51L ERROR_REM_NOT_LIST 远程计算机无法使用。
52L ERROR_DUP_NAME 在网络上存在重复名称。
53L ERROR_BAD_NETPATH 无法找到网络路径。
54L ERROR_NETWORK_BUSY 网络忙。
55L ERROR_DEV_NOT_EXIST 指定网络资源不再可用。
56L ERROR_TOO_MANY_CMDS 已到达网络 BIOS 命令的限制。
25L ERROR_SEEK 驱动器无法在磁盘上找到
指定区域或磁道。
26L ERROR_NOT_DOS_DISK 无法访问指定磁盘。
27L ERROR_SECTOR_NOT_FOUND 驱动器无法找到请求的扇区。
-2 LZERROR_BADOUTHANDLE 输出句柄无效。
-1 LZERROR_BADINHANDLE 输入句柄无效。
HP Smart Update Manager
2011 年 9 月
版本： 5
保密的计算机软件。需要有 HP 颁发的有效 许可证才能拥有、使用或复制。按照 FAR 12.211 和 12.212 的规定，可以根据供应商 的标准商业许可证授权美国政府使用商用计 算机软件、计算机软件文档以及商业项目的 技术数据。
Microsoft®、Windows®、Windows Vista® 和 Windows Server® 是 Microsoft Corporation 在美国的注册商标。
ZHCN
iii
编辑目标 ............................................................................................................................ 21 删除目标 ............................................................................................................................ 21 管理组 ................................................................................................................................ 21 安装更新 ............................................................................................................................................. 22 安装更新 ............................................................................................................................ 23 关于安装 ............................................................................................................................ 23 查看发生故障的依赖项 ....................................................................................................... 23 选择软件包 ......................................................................................................................... 23 选择组件 ............................................................................................................................ 24 查看固件不匹配情况的详细信息 ........................................................................................ 24 选择设备 ............................................................................................................................ 24 安装选项 ............................................................................................................................ 24 重新引导选项 ..................................................................................................................... 25 安排更新 ............................................................................................................................................. 25 生成和查看报告 .................................................................................................................................. 26 生成报告 ............................................................................................................................ 26 查看报告 ............................................................................................................................ 26
NPort 管理套件 для Windows 7、Server 2008 R2 或更高版本的 rel
NPort Administration Suite for Windows 7, Server 2008 R2 or laterRelease NotesSupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Fixed driver signature failure on Windows 7.• For IP Serial library, unable to reopen a Grouped-COM port.• Fixed BSOD when a Grouped-COM port is opened.• Encrypted configuration file can't be imported via web console.EnhancementsWindows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012,Windows Server 2012 R2, Windows Server 2016, Windows Server 2019NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series,NPort 5600 Series, NPort 5600-8-DT Series, NPort 5600-8-DTL Series, NPort IA5000 Series, NPort P5150A• Supports Windows Server 2019.• Supports Moxa Security Guideline.New Features• Separate driver versions are now used to support different Windows versions; driver v2.0 supports Windows 95/98/ME/NT/XP/Visa and Windows Server 2003/2008, driver v3.0 supports Windows 7/8/8.1/10 and Windows Server 2008 R2/2012/2012 R2/2016/2019.N/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsWindows 10, Windows 2000, Windows 7, Windows 8, Windows 8.1, Windows 95, Windows 98,Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2,Windows Server 2012, Windows Server 2012 R2, Windows Vista, Windows XPNPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series,NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series, Industrial Device Servers • Supports encrypted configuration.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Device search failure when the host has more than 16 IP addresses.• NPort Administration Suite could not be run on Windows 2000.EnhancementsWindows 10, Windows 2000, Windows 7, Windows 8, Windows 8.1, Windows 95, Windows 98,Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2,Windows Server 2012, Windows Server 2012 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports Windows 10.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Updated IPSerial.dll to fix thread handle always existing.• Utility could not monitor devices with "auto save device" setting when restarting the utility.• Utility could not monitor devices with "manual" setting before executing search function.• Ports mapped by the NPort Administration Suite v1.18 or earlier would disappear when using a version of Administration Suite later than v1.18.• Searching by 802.11 WLAN would fail on Windows 7 or later.• The timeout of IPSerial nsio_checkalive function would not work on Windows 7 Ultimate.• Popup error message "The network component is not ready" when searching for an NPort on Windows 8.• Ports could not be sorted by COM number order when clicking the COM number field in the monitor page.• The ports mapped by NPort Administration Suite v1.19 or earlier could not be opened by using a version of Administration Suite later than v1.19.17.EnhancementsWindows 2000, Windows 7, Windows 8, Windows 8.1, Windows 95, Windows 98, Windows ME,Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • IPSerial.dll upgraded to version 1.7.3.• IPSerial added example code for VB2010.• Updated NPort.dll to support NPort P5150A.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsWindows 2000, Windows 7, Windows 8, Windows 95, Windows 98, Windows ME, Windows NT,Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012,Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports Windows 8 and Windows Server 2012.• Supports "Always Accept Open Request" for Windows 2000 and newer.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Driver caused a BSOD when opening and closing repeatedly in Windows 2008 R2.• Driver caused a BSOD when applications open grouped COM ports which contain one or more disabled ports.• In the COM Grouping function, sometimes HyperTerminal may not read the received data immediately.EnhancementsWindows 2000, Windows 7, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports NPort 5150AI-M12, 5250AI-M12, 5450AI-M12.• Supports LLDP configuration.• Supports Windows publish.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Application will not work properly when logging as a standard user in Windows Vista/7environments. This version will prompt the user change to an account with administrative rights.• Windows 2008 64-bit driver would cause a BSOD when accessing an invalid memory path.• Modified the Georgetown time zone to GMT-04:00, Caracas to GMT-04:30, and Sofia to GMT +02:00.• The "nsio_RTS" function was not able to control RTS signals.EnhancementsWindows 2000, Windows 7, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports NPort P5150A.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• System BSOD when setting and enabling COM grouping functions in Windows 2008 R2.EnhancementsWindows 2000, Windows 7, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports NPort 5600-8-DTL Series.• Supports NPort A Series products in NPort.dll library.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Reduced handle counts when application called nsio_init() from IPSerial library.• When closing COM port and applying change to other COM numbers simultaneously, the NPort administrator utility will cause a hang up.• If the nsio_close() function is called several times and then the nsio_open() function is called, it will fail and return an undefined error code.EnhancementsWindows 2000, Windows 7, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports Multi-connection by IPSerial library.• Supports Windows 7.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Shortened opening time for COM Grouping.• Shortened setting time for COM Grouping.• Write operation would stop transmitting.• Monitor and port monitor would stop after removing target.EnhancementsWindows 2000, Windows 7, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003, Windows Server 2008, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports COM Grouping function for Windows NT.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• Set IP filter netmask error on Windows x64 platforms.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows Server 2008, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports NPort 5110A, 5130A, 5150A, IA5450A, IA5450AI, IA5150A, IA5150AI, IA5250A, IA5250AI,5210A, 5230A, 5250A.• Supports COM Grouping function (does not support Windows 95/98/ME/NT).New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• "Import COM Mapping" function would throw an "invalid pointer opertion" message.• Monitor function would cause a memory leak.• Adjusted the IRP completion order for multi-processor environments.• Fixed the buffer protection mechanism for issues while inserting special characters in the serial RX buffer.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows Server 2008, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports NPort IA-5250I.New FeaturesN/A• This version also applies to models NPort IA-5250ISupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Upgraded package: IPSerial Library.• Application crash problem with IP serial library when binding more than 8 IPs(alias) for PC.• Loading driver failed in Windows Vista x64.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows Server 2008, Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series N/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• SERIAL_PURGE_TXABORT did not reset the WriteCharsQueued counter.• SIO outqueue count was inaccurate under classic mode.• The port number was incorrect in the "UDP Mode Settings: Destination" list.• Startup of Monitor and Port Monitor may fail.• Removal of Monitor and Port Monitor may fail.• The search function would have issues on a Windows 2003 host with dual LAN cards.• Adding COM port would fail if "SERIALCOMM" registry key was absent.• Invalid argument for time encode.• Access violation problem in "IP Address Report List".• Search function supports 16 IP addresses for local host.• "Alive" status in Monitor and Port Monitor may be incorrect.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series N/ANew FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows Vista, Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports Windows Vista.• Supports 5610-8-DT, 5610-8-DT-J, 5650-8-DT, 5650-8-DT-J and 5650I-8-DT.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Improved IoctlGetCommstatus() to report live out queue count.• Improved utility user interface.• Improved COM setting functions. If the selected ports are in use, no change can be made to them.These settings include: COM number, Tx mode, FIFO, and Fast Flush.• Improved COM setting functions. If the users do not have administrative privileges, they cannot add or delete COM ports. However, they can still view the COM settings and open the COM ports.• Improved utility user interface.• Modem dial out caused system halt on multi-processor platforms.• Driver read operations caused double completion (BSOD) on multi-processor platforms.• GetCommStatus caused a BSOD on multi-processor platforms.• ioctl of setting Xon/Xoff character failed.• Fixed bugs detected by Static Driver Verifier, which include a double completion problem and completion of IRP without releasing the cancel spinlock.• FastFlush setting error when COM port number exceeds 127.• COM Mapping problem when a disabled port is opened.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Added "Network Timeout" function for COM settings.• Added auto message log function.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/A• IOCTL_SERIAL_IMMEDIATE_CHAR bug causing a BSOD.• IOCTL_SERIAL_XOFF_COUNTER bug causing system halt.• Accessible IPs export and import configurations did not match.• IOCTL_SERIAL_IMMEDIATE_CHAR bug causing a BSOD.• IPSerial nsio_write and mutli-port connection problems.• Administrator could not remove serial port settings when uninstalling the NPort Administration Suite.• COM Mapping could not import files exported by Administrator v1.2.• Disconnecting an NPort will crash the application while calling nsio_close.EnhancementsWindows 2000, Windows 95, Windows 98, Windows ME, Windows NT, Windows Server 2003,Windows XPIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports PPP Mode and Real COM Mode (RFC2217) operating mode for NPort 56xx.• Supports 64-bit Windows.• Moved nprcmisic.dll to nport.dll to cover all NPort models.• Supports NPort 5130, 5150, 5650, 5650-S-SC, 5650-M-SC.• Supports SERIAL_LSRMST_ESCAPE and SERIAL_LSRMST_MST event types of IOCTL_SERIAL_LSRMST_INSERT requests. SERIAL_LSRMST_LSR_NODATA and SERIAL_LSRMST_LSR_DATA event types are not supported due to driver limitations.New FeaturesN/AN/ASupported Operating SystemsNotesChangesApplicable ProductsBugs Fixed• Improved Windows 2000/XP/2003 driver "Fast Flush" performance.• Improved disconnection process to prevent application blocking.• Improved NT/2000/XP/2003 driver Ioctl performance (parity, baud, modem...).• High CPU loading with Hyper Threading systems.• COM Mapping rescan prevents some models from being able to be configured.• Port Monitor: When NPort is reconnecting, Administrator increases CPU load to 100%.• Event log lost problem.• IOCTL_SERIAL_SET_WAIT_MASK (npser+114c) BSOD RQL_NOT_LESS_OR_EQUAL problem.• (npser+5c13) BSOD KERNEL_MODE_EXCEPTION_NOT_HANDLED problem.• Verifier testing problem.• Classic mode oqueue length was not correct.• Tx does not stop on network disconnection.• Write blocked after reconnecting.EnhancementsN/AIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • Supports new functions of firmware 2.0.• Added new NPort IA model.• Added Web console toolbar.• Supports IOCTL_SERIAL_XOFF_COUNTER command (Windows 2000/XP/2003), which is used by some 16-bit programs.New Features• Registered COM number usage (Windows 2000/XP/2003). This will avoid other COM device from using the same COM number occupied by this driver.N/ASupported Operating SystemsNotesChangesApplicable ProductsBugs FixedN/AN/AEnhancementsN/AIndustrial Device Servers, NPort 5100 Series, NPort 5100A Series, NPort 5200 Series, NPort 5200A Series, NPort 5400 Series, NPort 5600 Series, NPort 5600-DT Series, NPort 5600-DTL Series • First release.New FeaturesN/AN/A。
EnterpriseManager配置失败解决方法
EnterpriseManager配置失败解决方法sqlplus /nologconn / as sysdbaselect instance_name from v$instance;查到sid然后在cmd下设置set ORACLE_SID=sid名称然后emctl stop dbconsoleemctl start dbconsoledrop user sysman cascade;重启机器，并断开网络，关闭杀毒软件、防火墙，并删除失败记录，run -cmd-> emca -deconfig dbcontrol db -repos drop,一路输入密码后，显示成功删除。
重新配置emca -config dbcontrol db -repos create，EM配置成功了！◆1：开始－＞程序->oracle->Configuration and MigrationTools->Enterprise Manager Configuration Assistant◆2:配置本地oracleManagementServer－＞下一步->创建一个新的资料档案库->下一步->在现有的数据库中创建->输入用户名:sys，密码：服务：计算机名:1521:数据库名->下一步->资料档案库登录信息:输入想创建的用户名和密码->是◆3:进入“选择资料档案库用户表空间"->下一步－＞完成◆4:控制面板->服务->查看”OracleEnterpr ise Manager是否启动:如没启动则启动默认用户名和密码为：sysman 密码：oem_temp----------------------//////////////////////--------------------------------今天安装Oracle数据库时显示Enterprise Manager配置失败，实例化EM配置文件时出错，查询log后，发现报错：Service creation failed. Aborting...解决方案如下：需要deconfig em后，再重新config emC:\>emca -deconfig dbcontrol db -repos dropEMCA 开始于 2009-6-24 15:05:49EM Configuration Assistant 10.2.0.1.0 正式版版权所有 (c) 2003, 2005, Oracle。
Dell Wyse Management Suite 1.4 部署指南说明书
Dell Wyse Management Suite 版本 1.4 部署指南注、小心和警告注: “注”表示帮助您更好地使用该产品的重要信息。
小心: “小心”表示可能会损坏硬件或导致数据丢失，并说明如何避免此类问题。
警告: “警告”表示可能会造成财产损失、人身伤害甚至死亡。
© 2019 Dell Inc. 或其子公司。
保留所有权利。
Dell、EMC 和其他商标是 Dell Inc. 或其附属机构的商标。
其他商标可能是其各自所有者的商标。
2019 - 05Rev. A001 简介 (4)2 硬件要求 (5)3 Wyse Management Suite 部署架构 (6)4 部署详细信息 (7)在单个服务器上部署以支持 50,000 个瘦客户端设备 (7)在单个服务器上部署以支持 120,000 个瘦客户端设备 (7)支持 T eradici 设备的部署详细信息在单个服务器上部署以支持 5000 个 Teradici 设备部署以支持 5000多个 T eradici 设备 (8)单独数据库服务器上的 Wyse Management Suite (11)5 自定义端口配置 (13)更改 T omcat 服务端口 (13)更改 MQTT 端口 (14)更改 MariaDB 端口 (14)更改 MongoDB 数据库端口 (14)远程存储库 (15)管理 Wyse Management Suite 存储库服务 (21)6 将 Wyse Management Suite 版本 1.3 升级到 1.4 (22)7 维护 (26)数据库备份 (26)数据库还原 (26)目录3简介Dell Wyse Management Suite 是新一代管理解决方案，允许您集中配置、监控、管理和优化 Dell Wyse Thin Client。
新版 Suite 提供出色的功能、性能以及易用性，让您可以更轻松地部署和管理 Thin Client。
opengauss5.0企业版主备安装
opengauss5.0企业版主备安装作者:JQKA知乎：月亮岛岛主1、基础环境硬件配置：cpu：2c 2uMem：4GVM workstation 虚拟化8g 4c 2台数据库：openGauss-5.0.0-CentOS-64bit-all.tar.gz操作系统：CentOS-7-x86_64-DVD-1810.isoNode1：192.168.92.161Node2：192.168.92.1622、系统环境设置关闭防火墙systemctl stop firewalld.service #关闭防火墙systemctl disable firewalld.service安装前检查软件环境如果是最小化安装centos7.6，需要安装额外的软件yum install net-tools.x86_64 -y # 没有ifconfig命令需要安装该软件yum install -y epel-release # 安装当yum显示没有可用软件包的时候，代表在linux系统yum 源中已经没有对应的安装包了，这时，我们需要安装EPEL。
EPEL（Extra Packages for Enterprise Linux），企业版Linux额外包，RHEL分布非标准包的社区类库。
yum updateyum install -y bzip2 # 安装bzip2用于后面的解压openGauss安装包安装python3.6python -V结果是python2安装python3yum install -y python3验证python版本[root@node1 ~]# python -VPython 2.7.5[root@node1 ~]# python3 -VPython 3.6.8软件依赖要求yum list libaio-develyum list flexyum list bisonyum list ncurses-develyum list glibc-develyum list patchyum list redhat-lsb-coreyum list readline-devel所需软件建议版本libaio-devel建议版本：0.3.109-13flex要求版本：2.5.31 以上bison建议版本：2.7-4ncurses-devel建议版本：5.9-13.20130511 glibc-devel建议版本：2.17-111patch建议版本：2.7.1-10 redhat-lsb-core建议版本：4.1readline-devel建议版本：7.0-13libnsl（openEuler+x86环境中）建议版本：2.28-36关闭SELINUX，将值改成disabled[root@node1 ~]# vi /etc/selinux/config[root@node1 ~]# cat /etc/selinux/config# This file controls the state of SELinux on the system.# SELINUX= can take one of these three values:# enforcing - SELinux security policy is enforced.# permissive - SELinux prints warnings instead of enforcing.# disabled - No SELinux policy is loaded.SELINUX=disabled# SELINUXTYPE= can take one of three values:# targeted - Targeted processes are protected,# minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection.SELINUXTYPE=targeted设置时区和时间cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime如果出现情况，说明时区正常，可跳过设置字符集参数[root@node1 ~]# cat /etc/locale.confLANG="en_US.UTF-8"其他小配置（可选）修改mtu值[root@node1 ~]# ifconfig ens33 mtu 8192此命令只能临时修改，永久修改如下# vi /etc/sysconfig/network-scripts/ifcfg-ens33#增加如下内容MTU="8192"[root@node1 ~]# ifconfigens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 8192inet 192.168.92.137 netmask 255.255.255.0 broadcast 192.168.92.255inet6 fe80::68e7:6a06:fcd1:6efa prefixlen 64 scopeid 0x20<link>ether 00:0c:29:ec:c3:36 txqueuelen 1000 (Ethernet)RX packets 1587 bytes 126990 (124.0 KiB)RX errors 0 dropped 0 overruns 0 frame 0TX packets 1032 bytes 173388 (169.3 KiB)TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0# vi /etc/sysconfig/network-scripts/ifcfg-eth0#增加如下内容MTU="8192"允许root用户远程登陆：vim /etc/ssh/sshd_config将“PermitRootLogin yes”前面的#号去掉让配置生效修改Banner配置cat >>/etc/ssh/sshd_config<<EOFBanner noneEOF# 检查cat /etc/ssh/sshd_config | grep Banner# 重启生效systemctl restart sshd.service创建dbgrp组和用户ommgroupadd dbgrpuseradd -g dbgrp omm # 可后面安装时创建passwd omm #设置密码为Gauss_1234（注意大小写）chown -R omm:dbgrp /opengauss修改/etc/hostsvi /etc/hosts192.168.92.161 node1 192.168.92.162 node2手工建立互信# root配置互信ssh-keygen -t rsassh-copy-id node1ssh-copy-id node2#omm配置互信su - ommssh-keygen -t rsa ssh-copy-id node1 ssh-copy-id node2重启操作系统3、安装openGauss上传安装包文件至/opengauss 并解压mkdir -p /opengausscd /opengauss/tar -zxvf openGauss-5.0.0-CentOS-64bit-all.tar.gztar -zxvf openGauss-5.0.0-CentOS-64bit-om.tar.gz .xml配置安装openGauss前需要创建cluster_config.xml文件。
错误1075：依存服务不存在，或已标记为删除的解决方法
错误1075：依存服务不存在，或已标记为删除的解决⽅法[现象]在"开始->设置->控制⾯板->管理⼯具->服务"中⼿动开启某种服务时，出现"错误1075：依存服务不存在，或已标记为删除"，如果系统是英⽂版，则是"Error 1075: The dependency service does not exist or has been marked for deletion."。
[解决⽅法]1、双击想要开启的服务，在弹出的⾯板中，选择“依存关系”标签，查看该服务所依赖的服务。
然后将所依赖的服务都开启，再⼿动重启该服务。
2、如果实施步骤1之后，还是遇到"错误1075：依存服务不存在，或已标记为删除"，那么说明尚有依赖服务没有启动。
因为，步骤1中所列举的依赖服务，仅仅是系统公认的，是最基本的。
要查看某个服务（假设名称为xxx）所依赖的完整的服务列表，可这样操作：开始->运⾏，打上regedit（推荐regedit32，如果该命令可⽤的话），回车，找到HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet xx，双击xxx的DependOnService项就可以看到所依赖的服务列表。
3、有2种处理⽅法：3.1) 如步骤1⼀样，将所依赖的服务都启动（不推荐）3.2) 删除DependOnService中多余的依赖服务列表，仅保留最基本的依赖服务。
要注意，服务列表的最后⾯应该是空格，或者是空⾏。
也可以在"开始->运⾏"中运⾏sc config xxx depend= yyy来设定服务xxx的依赖服务yyy。
同样要注意，"depend="后⾯要加空格。
[例⼦][现象]电脑中毒，杀毒之后，打印机消失。
添加打印机时，直接提⽰"错误！⽆法添加"。
CentOS5.5(终结版)
一、常用命令分类命令cd目录操作命令进入目录：cd 目录名返回根目录：cd返回上一目录：cd ..帮助命令命令--help如adduser –help复制文件命令cp –p 源文件目标文件设置目录权限chown 用户名目录软链接命令ln –s 源文件目标文件查找文件find . -name '*.*'创建文件夹mkdir 文件夹（文件夹名称）创建文件touch 文件夹/ 文件（斜杠两边不需要空格）删除文件夹rmdir 文件目录删除文件rm -rf 文件夹或文件/ （该命令强制删除文件夹下所有文件）VIM删除行ddVIM中复制行方法1：鼠标选中，再将鼠标移动目标位置，并单击右键。
方法2：在非编辑模式输入命令：：起始行号，结束行号copy 目标行号如：5,12 copy 15 //将5至12行复制到15行显示目录下的文件LL 目录//如ll /etc重启计算机reboot打开开机设置界面Setup将服务设置为开机自动启动chkconfig 服务名on 如：chkconfig vsftpd onLinux 界面切换Ctrl+Alt+Fn //其中Fn 代表功能键F1,F2,F3,F4,F5,F6中的一个IP地址跳转斜杠加IP地址，如：/127.0.0.1查看网络配置ifconfig关机重启关机：shutdown/halt/init 0重启：reboot/shutdown -r now锁定用户LOCK usermod -L 用户名##解锁用户USE usermod -U 用户名##禁止其他用户使用SU命令usermod -G wheel 用户名（将允许使用SU命令添加到组即可）修改web端口号按ESC输入：:134，将80修改成需要修改的端口。
二、 用户和组管理分类 命令添加用户 useradd –u 用户UID 号 -g 所属组名 -d 家目录 用户名 修改用户密码 passwd 用户名 删除用户 userdel 用户名修改用户 usermod –u 用户UID 号 -g 所属组名 -d 家目录 用户名 添加组 groupadd –g 组ID 号 组名 删除组 groupdel 组名修改组 groupmod –g 组ID 号 组名 显示用户信息id 用户名三、 网络配置分类命令网卡IP 配置命令 vim /etc/sysconfig/network-scripts/ifcfg-eth0 网卡DNS 配置命令 vim /etc/resolv.conf 启动网络服务 service network restart 查看网卡配置 ifconfig同一网卡配置多个IP 地址cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0:0 vim /etc/sysconfig/network-scripts/ifcfg-eth0:0然后修改IP 地址，并将Device=eth0改为Device=eth0:0 将BOOTPROTO 由none 值改为static四、 WEB 服务器配置分类 命令启动apache 服务 #service httpd start修改网站目录 vim /etc/httpd/conf/httpd.conf 修改281行的DocumentRoot 值，修改后保存并重启httpd 服务才能生效修改网站首页vim /etc/httpd/conf/httpd.conf修改391行的DirectoryIndex 的值，修改后保存并重启httpd 服务才能生效mysql 数据库操作 修改数据库root 账号的密码（初始密码为空） #mysqladmin -u root password Aa1234567 登录mysql 数据库 #mysql -u root -p 查看数据库 Mysql>show databases; 创建数据库 create database 数据库名称; 删除数据库 drop database 数据库名称; 进入数据库 use 数据库名称; 查看数据库中的表 show tables;新建表create table 表名 (字段名1 字段类型(宽度),字段名2 字段类型(宽度),...);常见字段类型有：int,char(10),varchar(20),date 主键的设置方法：字段名 类型 primary key 删除表 drop table 表名;添加记录 insert into 表名 values (字段1的值,字段2的值,...); 删除记录delete from 表名 where 条件;从文本文件导入数据 Load data infile “文件路径” into table 表名; 显示记录 select * from 表名;显示表结构Show fields from 表名;查看用户： vim /etc/shadow 查看用户组： Vim /etc/group 查看账户： Vim /etc/passwd (具体解释请看Linux 应用基础教程第115页第七章内容)退出mysql quit或exit五、DHCP服务器的配置：cp /usr/share/doc/dhcp-9.3.6/dhcpd.conf.sample /etc/dhcpd.conf vim /etc/dhcpd.conf修改IP地址service dhcpd restartchkconfig dhcpd on分类命令网络地址Subnet子网掩码Netmask网关Option routersDNS Opton domain-name-servers地址范围Range dynamic-bootp地址租期Default-lease-time最长的地址租期Max-lease-time六、samba服务器分类命令匿名只读访问# mkdir /test //创建目录# chown nobody /test //设置匿名用户对文件夹的权限#vim /etc/samba/smb.conf // samba配置文件security=share //允许匿名访问[test] //配置共享名称comment=test //注释path=/test //配置路径writable =yes //只读属性#service smb restart //重启动samba服务匿名可读写访问# mkdir /test //创建目录# chown nobody /test //设置匿名用户对文件夹的权限#vim /etc/samba/smb.conf // samba配置文件security=share //允许匿名访问[test] //配置共享名称comment=testpath=/test //配置路径writable=no //可修改属性#service smb restart 允许匿名：guest ok =yes修改：101行修改安全权限：可改成（share [共享] or user [匿名]）282行到288行首先删除注释，然后在径行修改[path]文件目录路径，以及修改comment共享名最后重启整个服务。
CentOS使用yum安装MySQL5.7报检索密钥错误解决方法
CentOS使⽤yum安装MySQL5.7报检索密钥错误解决⽅法在CentOS上使⽤yum安装MySQL时检索密钥错误的解决⽅法使⽤yum安装MySQL时报错yum -y install mysql mysql-serveryum -y install mysql-community-server报错内容如下warning: /var/cache/yum/x86_64/7/mysql57-community/packages/mysql-community-libs-compat-5.7.37-1.el7.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 3a79bd29: NOKEY 从 file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql 检索密钥源 "MySQL 5.7 Community Server" 的 GPG 密钥已安装，但是不适⽤于此软件包。
请检查源的公钥 URL 是否配置正确。
失败的软件包是：mysql-community-libs-compat-5.7.37-1.el7.x86_64GPG 密钥配置为：file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql处理⽅式有两种1. 到mysql官⽹下载校验⽂件2. 修改配置跳过校验本⽂记录第⼆种⽅式编辑⽂件/etc/yum.repos.d/mysql-community.repo修改对应安装版本的gpgcheck=0即可,默认值为1[mysql57-community]name=MySQL 5.7 Community Serverbaseurl=/yum/mysql-5.7-community/el/7/$basearch/enabled=1gpgcheck=0gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql再次安装即可。
Win10_11使用VMware等启动虚拟机蓝屏报错等一些列问题解决方案
Win10_11使⽤VMware等启动虚拟机蓝屏报错等⼀些列问题解决⽅案前⾔新买的联想Thinkbook 14P电脑，趁着新鲜劲，赶紧把各个环境配置搞搞。
结果搭建Liunx虚拟机系统时，遇到了各式各样的问题，这⾥拿出来分享⼀下，给⼤伙避避坑。
⾸先，进⾏的是⼤家都常⽤的VMware进⾏操作，我⽤的是VMware-pro15VMware安装及部署Linux系统安装VMware⼀路下⼀步，都正常进⾏。
然后配置虚拟系统进⾏启动Linux虚拟机时，电脑出现蓝屏报错SYSTEM_SERVICE_EXCEPTION⽹上⼀顿搜索之后，查到的解决⽅案有以下两种：⽅案⼀：更新版本，更新⾄16.1.0及以上版本。
⽅案⼆（修改windows功能）：⾸先我们先打开"控制⾯板"。
按Win+X键可以快速调出系统应⽤菜单，然后选择控制⾯板。
打开的控制⾯板中依次点击程序→启⽤或关闭Windows功能，之后在打开的对话框中把Hyper-V选项给勾去掉点击确定重启。
想最简便的⽅式修改，所以选择了第⼆种⽅案1. 因为windows 10/11默认没有Hyper-V配置项，所以我们得先让它展⽰出来才能关掉。
新建txt⽂件，将下⾯代码复制粘贴过去。
pushd "%~dp0"dir /b %SystemRoot%\servicing\Packages\*Hyper-V*.mum >hyper-v.txtfor /f %%i in ('findstr /i . hyper-v.txt 2^>nul') do dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\%%i"del hyper-v.txtDism /online /enable-feature /featurename:Microsoft-Hyper-V-All /LimitAccess /ALL然后再把⽂件名+扩展名⼀起改成"Hyper-V.bat"2. ⽤管理员⾝份执⾏⽂件。
Double-Take_Availability_Windows_FullServerProtect_Guide_V5_3
3.4.1. 3.4.2. 3.4.3. 3.4.4. 3.4.5. 3.4.6. 3.5. 3.6.
切换作业说明(Failover) ................................................................................................. 14 回切作业说明(Failback)................................................................................................. 16 硬件故障切换接管后的恢复作业（单张网卡） ...................................................... 16 硬件故障切换接管后的恢复作业（多张网卡） ...................................................... 17 系统崩溃后回切作业说明....................................................................................... 18
3.6.1. 3.6.2. 3.6.3. 4.
故障排除 ................................................................................................................................ 19
Domain DNS Double-Take Group Administrator Admin 域控管理员 DNS 管理员 Admin Monitor option No Yes
架构单机神泣
首先安装数据库下载好SQLPERSONAL.rar后先解压出来这边我已经解压好了这边我解压的路径是 D:\SQLPERSONAL\SQLPERSONAL玩家自己可以随意解压到一个地方，但注意路径中不能有中文，有中文的话安装会出错，这个要检查下。
开始安装，看我操作这里的公司和姓名随意，默认就可以了，每个电脑都不一样的，不需要去改动它这里的安装路径不要去改动它，默认安装这里选择“使用本地系统帐户”选择“混合模式”密码填 youyou007@cy注意密码前后不要有空格好了下一步安装需要些时间，玩家可以跟我同步操作就行动画教程有暂停的功能好了点“完成”按照好后到开始菜单——程序，里面找到它找到这个服务管理器点击运行它点“开始/继续”运行好后桌面右小角会出现小三角绿色数据库图标小三角绿色图标才表示运行成功！！好了到开始菜单——程序，里面找到“企业管理器”就在刚才的服务管理器下面把它运行出来点左边的数据库成功运行这个数据库就可以点出来这样就全部设置安装好了玩家有出现问题，检查下步骤就可以了！！玩游戏前推荐关闭360保护等安全软件，有些杀毒或保护软件会限制程序的运行。
程序安全保证，放心使用。
在安装单机版程序前，先安装数据库，安装好后才能进行下面的步骤释放ShaiyaServer压缩包里的文件压缩包 -- 右键 -- 解压到当前文件夹强调下,路径必须为 D:\如若放到其他磁盘,或是其他文件夹内,会导致服务启动不起来。
解压好就是这样的，玩家检查下D:\ShaiyaServer这个路径下面就是这些文件，必须是这个路径。
安装扩展存储过程看动画来操作选中数据库底下的 master工具菜单——SQL查询分析器exec master..sp_addextendedproc 'xp_crypt', 'D:\ShaiyaServer\master\xp_crypt.dll' 复制上面这一行到里面鼠标右键粘贴点上面的勾后再点绿色三角我已经安装过了,会提示已存在,刚安装完会提示命令已成功完成。
服务器端程序不能运行,如何设设DEP项目
服务器端程序不能运行,如何设置DEP项目
如果您使用的是Windows xp sp2 或者Windows2003操作系统，那么您需要对系统的DEP即数据执行保护项目进行修改。
修改步骤如下：
方法一：
在桌面上“我的电脑”图标点击鼠标右键，在弹出的快捷菜单中选择“属性”功能打开系统属性对话框：
在对话框中选择“高级”选项卡，点击“性能”框中的“设置”按钮弹出如下对话框：
选择“数据执行保护（即DEP）”选项卡。
在此对话框中如果选择：只为关键Windws程序和服务启用数据执行保护的话直接点击确定按钮即可。
如果选择：除所选之外，为所有程序和服务启用数据执行保护的话，在窗口下方点击“添加”按钮弹出程序选择窗口：
选择天润档案服务器端的安装文件夹中TRDAserver.exe和TRDAtray.exe两个文件。
将此两个文件均添加到列表中点击“确定”按钮即可。
如果服务器上同时安装了客户端的话同样需要把客户端程序：档案管理系统.exe添加到上面列表中。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Module 1 - Networks & Firewalls ................................................................. 3
1 Securing Networks .........................................................................................5 1.1 All Firewalls are Not Equal .............................................................................5 1.1.1 Primary Organization Network .........................................................5 1.1.2 Hosted Services Network.................................................................6 1.1.3 Remote Office Networks ..................................................................7 1.2 Basic Protocols ..............................................................................................7 1.2.1 IP Protocol .......................................................................................7 1.2.2 TCP Protocol ...................................................................................8 1.2.3 UDP Protocol ...................................................................................9 1.2.4 ICMP Protocol................................................................................10 1.3 Protection Using Simple Packet Filters ........................................................10 1.3.1 Packet Filter Protection ..................................................................10 1.4 Protection Using Application Proxies ...........................................................10 1.4.1 Application Proxy Protection ..........................................................11 1.5 Protection Using Hybrids – Stateful Inpsection ............................................11 1.5.1 Stateful Inspection Protection ........................................................11 1.5.2 Building State Tables .....................................................................12 1.5.3 Check Point Filtering Modules .......................................................14 1.5.4 Check Point State Tables ..............................................................14 Basic Network Packet Analysis .......................................................................16 2.1 Sniffing Packets ...........................................................................................16 2.1.1 tcpdump .........................................................................................16 2.1.2 Wireshark.......................................................................................16