NBA_2011

Windows Server 2003域服务器的搭建中遇到的问题

在Windows2003 中搭建域服务器，推荐一个比较好的博客，写的很详细：http://hi.baidu.com/shangdawei421/blog/item/b0305060fbede1d38db10d37.html。

在安装的过程中，可能会遇到如下的错误：

This computer has no disk drives formatted for the NTFS file system. Because the SYSVOL folder is replicated among Active Directory domain controllers, that folder must be on a disk formatted with NTFS

(You can convert drives formatted with the FAT file system with the convert.exe command-line tool.)

解决方法是：
将安装盘（比如C:）的文件格式从 FAT32 转为 NTFS

Windows XP本身支持NTFS分区，使用NTFS分区的安全程度和磁盘管理比其他分区格式要好。在安装Windows XP时，系统会自动让你选择是否将现有分区转化为NTFS分区，如果当时没有选择，而现在又想将硬盘转为NTFS，除了使用Partition Magic等工具软件外，其实还有一个更为简单实用的方法。

  1.点“开始→程序→附件→命令”提示符(这是Windows XP内置的一个类似于DOS的界 
面，内部所有的指令语句和DOS下的基本相同)。

  2.打开窗口以后，在光标的提示符下输入“covert c:/FS:NTFS”，然后回车。注意在“covert”的后面有一个空格。

  3.接着系统会要求你输入C盘的卷标，然后回车。卷标在“我的电脑”中点C盘，然后看它的属性可以找到。

  这样就可简单地转换分区格式为NTFS了。这个方法只用于FAT32转为NTFS，不能将NTFS转为FAT32。

ＥＮＤ

TechNet

TechNet Library

Windows Server

Windows Server 2008 and Windows Ser...

Browse Windows Server Technologies

Active Directory Services

Active Directory Domain Services

Active Directory Domain Services fo...

Getting Started

AD DS Installation and Removal Step...

Known Issues for Installing and Rem...

Known Issues for Installing and Removing AD DS

Updated: January 10, 2011

Applies To: Windows Server 2008, Windows Server 2008 R2

Review the following known issues before you install Active Directory Domain Services (AD DS):

Adprep.exe issues
Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues
Disk space and component location issues
Other AD DS server role issues
Changes to performance counters

Adprep.exe issues

The location for Adprep.exe is different in Windows Server 2008 and Windows Server 2008 R2. You must run Adprep.exe before you can add a domain controller that runs Windows Server 2008 or Windows Server 2008 R2 to an existing Windows 2000 Server or Windows Server 2003 Active Directory environment. In Windows Server 2008, Adprep.exe is located in the /Sources/adprep folder of the operating system installation disk. In Windows Server 2008 R2, Adprep.exe is located in the /Support/adprep folder. Windows Server 2008 R2 includes a 32-bit and 64-bit version of Adprep.exe. The 64-bit version runs by default. If you want to run one of the Adprep.exe commands on a 32-bit computer, you must use the 32-bit version of Adprep.exe.
The adprep /rodcprep command can log an error if the infrastructure operations master for an application directory partition is not available when you run the command. The error indicates the name of the application directory partition whose infrastructure operations master role is not available. For more information about how to fix this issue, see article 949257 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=114419). This issue affects the adprep /rodcprep command in Windows Server 2008 and Windows Server 2008 R2. However, if you have already run the adprep /rodcprep command for Windows Server 2008, you do not have to run it again for Windows Server 2008 R2.
If you have not run the adprep /rodcprep command, Dcdiag.exe returns an error when it runs the NCSecDesc test. This test checks that the security descriptors on the naming context heads have appropriate permissions for replication. The error indicates that the Enterprise Domain Controllers group does not have Replicating Directory Changes In Filtered Set access rights for the DNS application directory partitions. If you do not plan to add an RODC to the forest, you can disregard this error. If you plan to add an RODC to the forest, you must run adprep /rodcprep. For adprep /rodcprep, you can run the version of Adprep.exe that appears in either Windows Server 2008 or Windows Server 2008 R2 because that parameter performs the same set of operations in each version. For more information about running adprep /rodcprep, see Prepare a Forest for a Read-Only Domain Controller.
When you run adprep /forestprep for Windows Server 2008 R2, Windows 2000 domain controllers that are configured as global catalog servers perform a full synchronization of their partial domain replicas. This occurs because the /forestprep operation modifies the global catalog's partial attribute set (PAS). A reduction in the performance of Windows 2000 domain controllers is possible during the rebuild process. This is expected behavior for Windows 2000 domain controllers only; later versions of Windows Server add the additional attributes incrementally. To avoid the full synchronization, upgrade the Windows 2000 domain controllers to Windows Server 2003. Demoting the Windows 2000 domain controllers is also possible, but this action requires sufficient planning to ensure that no service outages are experienced.
If you run Adprep.exe or Adprep32.exe on a non-English version of Windows, the status and progress information does not appear.

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

When you install a new Windows Server 2008 or Windows Server 2008 R2 domain controller with DNS server into a domain such as treyresearch5.net, you might encounter the following error:

A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain “treyresearch5.net”. Otherwise, no action is required.

If you are not concerned that people in other domains or on the Internet will not resolve DNS name queries for computer names in the local domain, you can disregard the message and click Yes.

The error occurs when:
- The Active Directory Domain Services Installation Wizard (Dcpromo.exe) has been configured to install the DNS server role.
  
  -and-
  
  Enough delegations do not already exist between DNS servers in the immediate parent DNS zone and the subdomain where you are installing the new domain controller.
  
  -and-
  
  The domain controller you are installing is unable to create a delegation to the DNS subdomain on a DNS server that is authoritative for the parent zone.
Dcpromo.exe tries to create the delegation to ensure that computers in other domains can resolve DNS queries for hosts, including domain controllers and member computers, in the DNS subdomain.

Dcpromo.exe can auto-create such delegations only on Microsoft DNS servers and will always fail if the parent DNS domain zone resides on third party DNS servers such as BIND.

You can see this error when you install domain controllers in forest root domains with two or three-part names (such as contoso.com or corp.contoso.com) that are immediately subordinate to top-level domains on the internet such as .COM, GOV, .BIZ, .EDU or two-letter country code domains such as .NZ and .AU.

If your Active Directory domain was to be registered on the Internet by the time it was promoted, the logging of this warning text may indicate that your ISP or DNS hosting provider has not yet created the necessary delegation to your Active Directory subdomain.

Administrators may also encounter this error when creating domain controllers in a forest root domain that is subordinate to an existing corporate intranet namespace. For example, if the internal domain contoso.com is owned by bind DNS Servers, this error will be encountered when Dcpromo.exe attempts to create the delegation from contoso.com to the Active Directory forest root domain corp.contoso.com subdomain.

In order for Dcpromo.exe to create the delegation on authoritative DNS servers in the parent domain:
1. The parent DNS server must run the Microsoft DNS Server service.
2. The Microsoft DNS server in the parent domain must be online and accessible over the network from the domain controller you are installing.
3. The user running Dcpromo.exe on the domain controller that you are installing must have Domain Admins, Enterprise Admins, or DNS Admin credentials in the parent DNS zone.
Given that many Active Directory domains are not registered with an Internet registrar, and that the DNS servers for top level domains (TLDs) run BIND, this error message can safely be ignored by clicking Yes to continue the promotion.

Where delegations should exist between the parent domain and the subdomain being promoted, they can be created and validated before or after the Dcpromo.exe promotion. There is no reason to delay the promotion of a new domain controller presenting this error.

To avoid this error message in future Dcpromo.exe promotions, either:
1. Pre-create the delegation on third-party DNS Servers in the immediate parent domain.
2. Make sure that domain controllers that are being promoted have network connectivity and the necessary administrative credentials to create delegations on Microsoft DNS servers that host the parent DNS zone.
Alternatively, specify the /CreateDNSDelegation:No argument in the Dcpromo.exe command line or answer file.

For more information about delegation, see Understanding Zone Delegation(http://go.microsoft.com/fwlink/?LinkId=164773). If zone delegation is not possible in your situation, you might consider other methods for providing name resolution from other domains to the hosts in your domain. For example, the DNS administrator of another domain could configure conditional forwarding, stub-zones, or secondary zones in order to resolve names in your domain. For more information, see the following topics:
- Understanding zone types (http://go.microsoft.com/fwlink/?LinkID=157399)
- Understanding stub zones (http://go.microsoft.com/fwlink/?LinkId=164776)
- Understanding forwarders (http://go.microsoft.com/fwlink/?LinkId=164778)
If you cancel the Active Directory Domain Services Installation Wizard, the wizard closes, but the AD DS binary files are not removed.

If you want to uninstall the binary files, use Server Manager to uninstall the AD DS role or run dcpromo /uninstallBinaries at a command line, and then restart the computer. This applies to Windows Server 2008 or Windows Server 2008 R2.

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008
Disk space requirements for upgrading to Windows Server 2008 R2
SYSVOL location on an RODC
AD DS installation failure if SYSVOL is located at the root of a drive
A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%
AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

Disk space requirements for upgrading to Windows Server 2008

The upgrade process from Windows Server 2003 to Windows Server 2008 requires free disk space for the new operating system image, for the Setup process, and for any installed server roles. An error is logged when the domain controller role has detected insufficient disk space to perform the upgrade.

Additional disk space information may appear in the compatibility report displayed by Setup.

In some cases, the upgrade from Windows Server 2003 to Windows Server 2008 or Windows Server 2008 R2 (or from Windows Server 2008 to Windows Server 2008 R2) can fail silently if there is insufficient disk space. In this situation, the installation rolls back to the previous operating system.

You may also find more information in the Setupact.log file located in theDrive:\$WINDOWS.~BT\Sources\Panther folder, where Drive represents the drive that contains the existing Windows installation.

For the domain controller role, the volume or volumes that host the following resources also have specific free disk space requirements:

Application Data (%AppData%)
Program Files (%ProgramFiles%)
Users Data (%SystemDrive%\Documents and Settings)
Windows Directory (%WinDir%)

The free space on the %WinDir% volume must be equal or greater than the current size of the resources listed above and their subordinate folders when they are located on the %WinDir% volume. By default, Dcpromo.exe places the Active Directory database and log files under %Windir%, in which case, their size would be included in the free disk space requirements for the %Windir% folder.

For example, suppose that you have the following resources located on the %WinDir% volume, with the sizes listed in the following table.

Resource	Size
Application Data (%AppData%)	100 MB
Program Files (%ProgramFiles%)	100 MB
Users Data (%SystemDrive%\Documents and Settings)	50 MB
Windows Directory (%WinDir%)	1 GB
Total size	1.25 GB

In this example, the free space on the %WinDir% volume must be equal to 1.25 gigabytes (GB) or greater.

However, if the Active Directory database is hosted outside any of the folders above, then the hosting volume or volumes must only contain additional free space equal to at least 10 percent of the current database size or 250 megabytes (MB), whichever is greater. Finally, the free space on the volume that hosts the log files must be at least 50 MB.

A default installation of Active Directory in Windows Server 2003 has the Active Directory database and log files under %WinDir%\NTDS. With this configuration, the Ntds.dit database file and all the log files are temporarily copied over to the quarantine location and then copied back to their original location; this is why additional free space is required for those resources. Although the SYSVOL directory is also under %WinDir% (that is, %WinDir%\SYSVOL), it is moved and not copied. Therefore, it does not require any additional free space.

After the upgrade, the space that was reserved for the copied resources will be returned to the file system.

Disk space requirements for upgrading to Windows Server 2008 R2

The Active Directory database, NTDS.dit, on Windows Server 2008 R2 domain controllers can be larger than in previous versions of Windows for the following reasons:

The changes in the online defragmentation process on Windows Server 2008 R2 domain controllers.
Windows Server 2008 R2 domain controllers add two new indices on the large link table.
The Windows Server 2008 R2 Recycle Bin preserves attributes on deleted objects for the Recycle object lifetime.

For Recycle Bin, the database increases in size at the following moments:
- After Windows Server 2008 R2 adprep /forestprep completes and the first Windows Server 2008 R2 domain controller is installed, there is a new indexed attribute, isRecycled, whose value is set for all deleted objects.
- After the Recycle Bin is enabled, all attributes are kept on deleted objects. More disk space is required as more object deletions occur.
In a production Windows Server 2008 R2 domain at Microsoft, the Recycle Bin feature increased the AD DS database size by an additional 15 to 20 percent of the original database size, using the defaultdeletedObjectLifetime and recycledObjectLifetime values of 180 days. Additional space requirements depend on the size and count of the objects that are recycled.

An in-place upgrade of a domain controller to Windows Server 2008 R2 requires sufficient disk space for the upgrade process to copy the following folders:

%SystemRoot%
%ProgramFiles%
%SystemDrive%\Program Files
%ProgramFiles(x86)%
%SystemDrive%\build
%SystemDrive%\InstalledRepository
%ProfilesFolder%
%ProgramData%
%SystemDrive%\Documents and Settings

The following table shows the test results for an upgrade of a domain controller from Windows Server 2008 to Windows Server 2008 R2. In this table:

<i> = 15 GB (the minimum amount of free space on a Windows hard drive that Windows setup requires)
The original size of Ntds.dit was 5 GB.

Ntds.dit location	Free space (GB) on the system drive	Result
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	1	In this scenario, Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder, but there is not enough space to copy Windows setup files. The compatibility report finds there is not enough space to copy Windows files. The upgrade is blocked at the compatibility report.
Ntds.dit is located on a different drive than the system.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.
Ntds.dit is located on the default folder: %windir%\ntds\	<i> + 1	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, which causes the compatibility report to be bypassed. However, Ntds.dit is located under the Windows folder, which causes the upgrade to copy it from the Windows.old folder to the Windows folder. This last step fails because there is not enough space on the disk to fit Ntds.dit because the database was not copied to the new operating system. On its first start, Windows Server 2008 R2 is not able to locate Ntds.dit, which causes an error and forces the computer to roll back to the previous operating system. ERROR_CODE: (NTSTATUS) 0xc00002ec - Directory Services could not start because of the following error: %hs Error Status: 0x%x. Click OK to shut down the system. You can use the recovery console to diagnose the system further. Err 0xc00002ec = STATUS_DS_INIT_FAILURE_CONSOLE The domain controller is rolled back to Windows Server 2008 successfully.
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.

SYSVOL location on an RODC

On an RODC that uses Distributed File System (DFS) Replication for SYSVOL, you should place the SYSVOL shared folder on a separate volume than the Windows folder. Storing a DFS, read-only, replicated folder on the same volume as the Windows installation will result in decreased performance for that volume, unless there are other minifilter drivers installed, such as an antivirus program or a backup program.

AD DS installation failure if SYSVOL is located at the root of a drive

You cannot place SYSVOL at the root of drive, such as C:\. Although the Active Directory Domain Services Installation Wizard allows you to specify the root of a drive as the SYSVOL location, the AD DS installation will subsequently fail.

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

If you place the Active Directory database and log files in the root directory of a disk other than the disk that contains %systemroot%, a Stop error will occur. You will also receive a Stop error if you place these files on an iSCSI drive that is not available as a boot device. This applies to Windows Server 2008 or Windows Server 2008 R2, and it applies to new AD DS installations and upgrades.

To avoid this, ensure that the Active Directory database and log files are in a volume other than the root volume of a local, nonremovable drive.

Some iSCSI devices incorrectly report that they are local drives even when they are not. If this occurs, contact the drive vendor to determine if the hardware can be configured as a boot device. If the hardware cannot be configured as a boot device, perform the following procedure.

To move the Active Directory database and log files

Restart the computer, and then enter Directory Services Restore Mode (DSRM) by pressing F8 while the computer starts.
Move the Active Directory database and log files to a subdirectory at least one level beneath the root of a local drive.
Use Regedit.exe to find this registry key:HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Change the DSA Database File value to the new path from step 2, for example, x:\ntds.
Change the DSA Working Directory value to the new path from step 2, for example, x:\ntds\logs.

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

The AD DS installation in Windows Server 2008 R2 and Windows Server 2008 can fail if you place Active Directory components, such as the Active Directory database or SYSVOL, on an advanced drive type such as an iSCSI device. In Windows Server 2008 R2, the AD DS installation can fail to find an NTFS formatted drive if the operating system files are installed on an iSCSI device.

The issue with placing Active Directory components on an advanced drive type can occur after the AD DS installation wizard is finished and the server is restarted inn order to complete the installation. After the restart, the server fails to start in normal mode. You might see error 0xc00002e1 in the dcpromoui.log file or a Stop error with code c00002e2 appearing on screen.

The error is caused by Active Directory components such as the database not being available at startup. Placing the Active Directory database on a Storage Area Network (SAN) is supported only if the database is available at startup. Generally, if you cannot install the operating system onto the device in question and have the operating system boot off of it, you cannot host the Active Directory database on it, because Active Directory is a key part of the operating system boot process on computers hosting the domain controller server role.

As a workaround in this situation, install the Active Directory components on a hard drive that is accessible at startup.

The issue with AD DS installation failing to find an NTFS formatted drive if the operating system files are installed on an iSCSI device occurs only in Windows Server 2008 R2 and will be fixed in Service Pack 1. In this situation, the AD DS installation wizard fails with the following error:

(You can convert drives formatted with the FAT file system with the convert.exe command-line tool.)

TechNet

TechNet Library

Windows Server

Windows Server 2008 and Windows Ser...

Browse Windows Server Technologies

Active Directory Services

Active Directory Domain Services

Active Directory Domain Services fo...

Getting Started

AD DS Installation and Removal Step...

Known Issues for Installing and Rem...

Known Issues for Installing and Removing AD DS

Updated: January 10, 2011

Applies To: Windows Server 2008, Windows Server 2008 R2

Review the following known issues before you install Active Directory Domain Services (AD DS):

Adprep.exe issues
Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues
Disk space and component location issues
Other AD DS server role issues
Changes to performance counters

Adprep.exe issues

The location for Adprep.exe is different in Windows Server 2008 and Windows Server 2008 R2. You must run Adprep.exe before you can add a domain controller that runs Windows Server 2008 or Windows Server 2008 R2 to an existing Windows 2000 Server or Windows Server 2003 Active Directory environment. In Windows Server 2008, Adprep.exe is located in the /Sources/adprep folder of the operating system installation disk. In Windows Server 2008 R2, Adprep.exe is located in the /Support/adprep folder. Windows Server 2008 R2 includes a 32-bit and 64-bit version of Adprep.exe. The 64-bit version runs by default. If you want to run one of the Adprep.exe commands on a 32-bit computer, you must use the 32-bit version of Adprep.exe.
The adprep /rodcprep command can log an error if the infrastructure operations master for an application directory partition is not available when you run the command. The error indicates the name of the application directory partition whose infrastructure operations master role is not available. For more information about how to fix this issue, see article 949257 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=114419). This issue affects the adprep /rodcprep command in Windows Server 2008 and Windows Server 2008 R2. However, if you have already run the adprep /rodcprep command for Windows Server 2008, you do not have to run it again for Windows Server 2008 R2.
If you have not run the adprep /rodcprep command, Dcdiag.exe returns an error when it runs the NCSecDesc test. This test checks that the security descriptors on the naming context heads have appropriate permissions for replication. The error indicates that the Enterprise Domain Controllers group does not have Replicating Directory Changes In Filtered Set access rights for the DNS application directory partitions. If you do not plan to add an RODC to the forest, you can disregard this error. If you plan to add an RODC to the forest, you must run adprep /rodcprep. For adprep /rodcprep, you can run the version of Adprep.exe that appears in either Windows Server 2008 or Windows Server 2008 R2 because that parameter performs the same set of operations in each version. For more information about running adprep /rodcprep, see Prepare a Forest for a Read-Only Domain Controller.
When you run adprep /forestprep for Windows Server 2008 R2, Windows 2000 domain controllers that are configured as global catalog servers perform a full synchronization of their partial domain replicas. This occurs because the /forestprep operation modifies the global catalog's partial attribute set (PAS). A reduction in the performance of Windows 2000 domain controllers is possible during the rebuild process. This is expected behavior for Windows 2000 domain controllers only; later versions of Windows Server add the additional attributes incrementally. To avoid the full synchronization, upgrade the Windows 2000 domain controllers to Windows Server 2003. Demoting the Windows 2000 domain controllers is also possible, but this action requires sufficient planning to ensure that no service outages are experienced.
If you run Adprep.exe or Adprep32.exe on a non-English version of Windows, the status and progress information does not appear.

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

When you install a new Windows Server 2008 or Windows Server 2008 R2 domain controller with DNS server into a domain such as treyresearch5.net, you might encounter the following error:

A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain “treyresearch5.net”. Otherwise, no action is required.

If you are not concerned that people in other domains or on the Internet will not resolve DNS name queries for computer names in the local domain, you can disregard the message and click Yes.

The error occurs when:
- The Active Directory Domain Services Installation Wizard (Dcpromo.exe) has been configured to install the DNS server role.
  
  -and-
  
  Enough delegations do not already exist between DNS servers in the immediate parent DNS zone and the subdomain where you are installing the new domain controller.
  
  -and-
  
  The domain controller you are installing is unable to create a delegation to the DNS subdomain on a DNS server that is authoritative for the parent zone.
Dcpromo.exe tries to create the delegation to ensure that computers in other domains can resolve DNS queries for hosts, including domain controllers and member computers, in the DNS subdomain.

Dcpromo.exe can auto-create such delegations only on Microsoft DNS servers and will always fail if the parent DNS domain zone resides on third party DNS servers such as BIND.

You can see this error when you install domain controllers in forest root domains with two or three-part names (such as contoso.com or corp.contoso.com) that are immediately subordinate to top-level domains on the internet such as .COM, GOV, .BIZ, .EDU or two-letter country code domains such as .NZ and .AU.

If your Active Directory domain was to be registered on the Internet by the time it was promoted, the logging of this warning text may indicate that your ISP or DNS hosting provider has not yet created the necessary delegation to your Active Directory subdomain.

Administrators may also encounter this error when creating domain controllers in a forest root domain that is subordinate to an existing corporate intranet namespace. For example, if the internal domain contoso.com is owned by bind DNS Servers, this error will be encountered when Dcpromo.exe attempts to create the delegation from contoso.com to the Active Directory forest root domain corp.contoso.com subdomain.

In order for Dcpromo.exe to create the delegation on authoritative DNS servers in the parent domain:
1. The parent DNS server must run the Microsoft DNS Server service.
2. The Microsoft DNS server in the parent domain must be online and accessible over the network from the domain controller you are installing.
3. The user running Dcpromo.exe on the domain controller that you are installing must have Domain Admins, Enterprise Admins, or DNS Admin credentials in the parent DNS zone.
Given that many Active Directory domains are not registered with an Internet registrar, and that the DNS servers for top level domains (TLDs) run BIND, this error message can safely be ignored by clicking Yes to continue the promotion.

Where delegations should exist between the parent domain and the subdomain being promoted, they can be created and validated before or after the Dcpromo.exe promotion. There is no reason to delay the promotion of a new domain controller presenting this error.

To avoid this error message in future Dcpromo.exe promotions, either:
1. Pre-create the delegation on third-party DNS Servers in the immediate parent domain.
2. Make sure that domain controllers that are being promoted have network connectivity and the necessary administrative credentials to create delegations on Microsoft DNS servers that host the parent DNS zone.
Alternatively, specify the /CreateDNSDelegation:No argument in the Dcpromo.exe command line or answer file.

For more information about delegation, see Understanding Zone Delegation(http://go.microsoft.com/fwlink/?LinkId=164773). If zone delegation is not possible in your situation, you might consider other methods for providing name resolution from other domains to the hosts in your domain. For example, the DNS administrator of another domain could configure conditional forwarding, stub-zones, or secondary zones in order to resolve names in your domain. For more information, see the following topics:
- Understanding zone types (http://go.microsoft.com/fwlink/?LinkID=157399)
- Understanding stub zones (http://go.microsoft.com/fwlink/?LinkId=164776)
- Understanding forwarders (http://go.microsoft.com/fwlink/?LinkId=164778)
If you cancel the Active Directory Domain Services Installation Wizard, the wizard closes, but the AD DS binary files are not removed.

If you want to uninstall the binary files, use Server Manager to uninstall the AD DS role or run dcpromo /uninstallBinaries at a command line, and then restart the computer. This applies to Windows Server 2008 or Windows Server 2008 R2.

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008
Disk space requirements for upgrading to Windows Server 2008 R2
SYSVOL location on an RODC
AD DS installation failure if SYSVOL is located at the root of a drive
A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%
AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

Disk space requirements for upgrading to Windows Server 2008

Additional disk space information may appear in the compatibility report displayed by Setup.

For the domain controller role, the volume or volumes that host the following resources also have specific free disk space requirements:

Application Data (%AppData%)
Program Files (%ProgramFiles%)
Users Data (%SystemDrive%\Documents and Settings)
Windows Directory (%WinDir%)

For example, suppose that you have the following resources located on the %WinDir% volume, with the sizes listed in the following table.

Resource	Size
Application Data (%AppData%)	100 MB
Program Files (%ProgramFiles%)	100 MB
Users Data (%SystemDrive%\Documents and Settings)	50 MB
Windows Directory (%WinDir%)	1 GB
Total size	1.25 GB

In this example, the free space on the %WinDir% volume must be equal to 1.25 gigabytes (GB) or greater.

After the upgrade, the space that was reserved for the copied resources will be returned to the file system.

Disk space requirements for upgrading to Windows Server 2008 R2

The Active Directory database, NTDS.dit, on Windows Server 2008 R2 domain controllers can be larger than in previous versions of Windows for the following reasons:

The changes in the online defragmentation process on Windows Server 2008 R2 domain controllers.
Windows Server 2008 R2 domain controllers add two new indices on the large link table.
The Windows Server 2008 R2 Recycle Bin preserves attributes on deleted objects for the Recycle object lifetime.

For Recycle Bin, the database increases in size at the following moments:
- After Windows Server 2008 R2 adprep /forestprep completes and the first Windows Server 2008 R2 domain controller is installed, there is a new indexed attribute, isRecycled, whose value is set for all deleted objects.
- After the Recycle Bin is enabled, all attributes are kept on deleted objects. More disk space is required as more object deletions occur.
In a production Windows Server 2008 R2 domain at Microsoft, the Recycle Bin feature increased the AD DS database size by an additional 15 to 20 percent of the original database size, using the defaultdeletedObjectLifetime and recycledObjectLifetime values of 180 days. Additional space requirements depend on the size and count of the objects that are recycled.

An in-place upgrade of a domain controller to Windows Server 2008 R2 requires sufficient disk space for the upgrade process to copy the following folders:

%SystemRoot%
%ProgramFiles%
%SystemDrive%\Program Files
%ProgramFiles(x86)%
%SystemDrive%\build
%SystemDrive%\InstalledRepository
%ProfilesFolder%
%ProgramData%
%SystemDrive%\Documents and Settings

The following table shows the test results for an upgrade of a domain controller from Windows Server 2008 to Windows Server 2008 R2. In this table:

<i> = 15 GB (the minimum amount of free space on a Windows hard drive that Windows setup requires)
The original size of Ntds.dit was 5 GB.

Ntds.dit location	Free space (GB) on the system drive	Result
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	1	In this scenario, Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder, but there is not enough space to copy Windows setup files. The compatibility report finds there is not enough space to copy Windows files. The upgrade is blocked at the compatibility report.
Ntds.dit is located on a different drive than the system.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.
Ntds.dit is located on the default folder: %windir%\ntds\	<i> + 1	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, which causes the compatibility report to be bypassed. However, Ntds.dit is located under the Windows folder, which causes the upgrade to copy it from the Windows.old folder to the Windows folder. This last step fails because there is not enough space on the disk to fit Ntds.dit because the database was not copied to the new operating system. On its first start, Windows Server 2008 R2 is not able to locate Ntds.dit, which causes an error and forces the computer to roll back to the previous operating system. ERROR_CODE: (NTSTATUS) 0xc00002ec - Directory Services could not start because of the following error: %hs Error Status: 0x%x. Click OK to shut down the system. You can use the recovery console to diagnose the system further. Err 0xc00002ec = STATUS_DS_INIT_FAILURE_CONSOLE The domain controller is rolled back to Windows Server 2008 successfully.
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.

SYSVOL location on an RODC

AD DS installation failure if SYSVOL is located at the root of a drive

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

To avoid this, ensure that the Active Directory database and log files are in a volume other than the root volume of a local, nonremovable drive.

To move the Active Directory database and log files

Restart the computer, and then enter Directory Services Restore Mode (DSRM) by pressing F8 while the computer starts.
Move the Active Directory database and log files to a subdirectory at least one level beneath the root of a local drive.
Use Regedit.exe to find this registry key:HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Change the DSA Database File value to the new path from step 2, for example, x:\ntds.
Change the DSA Working Directory value to the new path from step 2, for example, x:\ntds\logs.

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

As a workaround in this situation, install the Active Directory components on a hard drive that is accessible at startup.

(You can convert drives formatted with the FAT file system with the convert.exe command-line tool.)

TechNet

TechNet Library

Windows Server

Windows Server 2008 and Windows Ser...

Browse Windows Server Technologies

Active Directory Services

Active Directory Domain Services

Active Directory Domain Services fo...

Getting Started

AD DS Installation and Removal Step...

Known Issues for Installing and Rem...

Known Issues for Installing and Removing AD DS

Updated: January 10, 2011

Applies To: Windows Server 2008, Windows Server 2008 R2

Review the following known issues before you install Active Directory Domain Services (AD DS):

Adprep.exe issues
Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues
Disk space and component location issues
Other AD DS server role issues
Changes to performance counters

Adprep.exe issues

The location for Adprep.exe is different in Windows Server 2008 and Windows Server 2008 R2. You must run Adprep.exe before you can add a domain controller that runs Windows Server 2008 or Windows Server 2008 R2 to an existing Windows 2000 Server or Windows Server 2003 Active Directory environment. In Windows Server 2008, Adprep.exe is located in the /Sources/adprep folder of the operating system installation disk. In Windows Server 2008 R2, Adprep.exe is located in the /Support/adprep folder. Windows Server 2008 R2 includes a 32-bit and 64-bit version of Adprep.exe. The 64-bit version runs by default. If you want to run one of the Adprep.exe commands on a 32-bit computer, you must use the 32-bit version of Adprep.exe.
The adprep /rodcprep command can log an error if the infrastructure operations master for an application directory partition is not available when you run the command. The error indicates the name of the application directory partition whose infrastructure operations master role is not available. For more information about how to fix this issue, see article 949257 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=114419). This issue affects the adprep /rodcprep command in Windows Server 2008 and Windows Server 2008 R2. However, if you have already run the adprep /rodcprep command for Windows Server 2008, you do not have to run it again for Windows Server 2008 R2.
If you have not run the adprep /rodcprep command, Dcdiag.exe returns an error when it runs the NCSecDesc test. This test checks that the security descriptors on the naming context heads have appropriate permissions for replication. The error indicates that the Enterprise Domain Controllers group does not have Replicating Directory Changes In Filtered Set access rights for the DNS application directory partitions. If you do not plan to add an RODC to the forest, you can disregard this error. If you plan to add an RODC to the forest, you must run adprep /rodcprep. For adprep /rodcprep, you can run the version of Adprep.exe that appears in either Windows Server 2008 or Windows Server 2008 R2 because that parameter performs the same set of operations in each version. For more information about running adprep /rodcprep, see Prepare a Forest for a Read-Only Domain Controller.
When you run adprep /forestprep for Windows Server 2008 R2, Windows 2000 domain controllers that are configured as global catalog servers perform a full synchronization of their partial domain replicas. This occurs because the /forestprep operation modifies the global catalog's partial attribute set (PAS). A reduction in the performance of Windows 2000 domain controllers is possible during the rebuild process. This is expected behavior for Windows 2000 domain controllers only; later versions of Windows Server add the additional attributes incrementally. To avoid the full synchronization, upgrade the Windows 2000 domain controllers to Windows Server 2003. Demoting the Windows 2000 domain controllers is also possible, but this action requires sufficient planning to ensure that no service outages are experienced.
If you run Adprep.exe or Adprep32.exe on a non-English version of Windows, the status and progress information does not appear.

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

When you install a new Windows Server 2008 or Windows Server 2008 R2 domain controller with DNS server into a domain such as treyresearch5.net, you might encounter the following error:

A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain “treyresearch5.net”. Otherwise, no action is required.

If you are not concerned that people in other domains or on the Internet will not resolve DNS name queries for computer names in the local domain, you can disregard the message and click Yes.

The error occurs when:
- The Active Directory Domain Services Installation Wizard (Dcpromo.exe) has been configured to install the DNS server role.
  
  -and-
  
  Enough delegations do not already exist between DNS servers in the immediate parent DNS zone and the subdomain where you are installing the new domain controller.
  
  -and-
  
  The domain controller you are installing is unable to create a delegation to the DNS subdomain on a DNS server that is authoritative for the parent zone.
Dcpromo.exe tries to create the delegation to ensure that computers in other domains can resolve DNS queries for hosts, including domain controllers and member computers, in the DNS subdomain.

Dcpromo.exe can auto-create such delegations only on Microsoft DNS servers and will always fail if the parent DNS domain zone resides on third party DNS servers such as BIND.

You can see this error when you install domain controllers in forest root domains with two or three-part names (such as contoso.com or corp.contoso.com) that are immediately subordinate to top-level domains on the internet such as .COM, GOV, .BIZ, .EDU or two-letter country code domains such as .NZ and .AU.

If your Active Directory domain was to be registered on the Internet by the time it was promoted, the logging of this warning text may indicate that your ISP or DNS hosting provider has not yet created the necessary delegation to your Active Directory subdomain.

Administrators may also encounter this error when creating domain controllers in a forest root domain that is subordinate to an existing corporate intranet namespace. For example, if the internal domain contoso.com is owned by bind DNS Servers, this error will be encountered when Dcpromo.exe attempts to create the delegation from contoso.com to the Active Directory forest root domain corp.contoso.com subdomain.

In order for Dcpromo.exe to create the delegation on authoritative DNS servers in the parent domain:
1. The parent DNS server must run the Microsoft DNS Server service.
2. The Microsoft DNS server in the parent domain must be online and accessible over the network from the domain controller you are installing.
3. The user running Dcpromo.exe on the domain controller that you are installing must have Domain Admins, Enterprise Admins, or DNS Admin credentials in the parent DNS zone.
Given that many Active Directory domains are not registered with an Internet registrar, and that the DNS servers for top level domains (TLDs) run BIND, this error message can safely be ignored by clicking Yes to continue the promotion.

Where delegations should exist between the parent domain and the subdomain being promoted, they can be created and validated before or after the Dcpromo.exe promotion. There is no reason to delay the promotion of a new domain controller presenting this error.

To avoid this error message in future Dcpromo.exe promotions, either:
1. Pre-create the delegation on third-party DNS Servers in the immediate parent domain.
2. Make sure that domain controllers that are being promoted have network connectivity and the necessary administrative credentials to create delegations on Microsoft DNS servers that host the parent DNS zone.
Alternatively, specify the /CreateDNSDelegation:No argument in the Dcpromo.exe command line or answer file.

For more information about delegation, see Understanding Zone Delegation(http://go.microsoft.com/fwlink/?LinkId=164773). If zone delegation is not possible in your situation, you might consider other methods for providing name resolution from other domains to the hosts in your domain. For example, the DNS administrator of another domain could configure conditional forwarding, stub-zones, or secondary zones in order to resolve names in your domain. For more information, see the following topics:
- Understanding zone types (http://go.microsoft.com/fwlink/?LinkID=157399)
- Understanding stub zones (http://go.microsoft.com/fwlink/?LinkId=164776)
- Understanding forwarders (http://go.microsoft.com/fwlink/?LinkId=164778)
If you cancel the Active Directory Domain Services Installation Wizard, the wizard closes, but the AD DS binary files are not removed.

If you want to uninstall the binary files, use Server Manager to uninstall the AD DS role or run dcpromo /uninstallBinaries at a command line, and then restart the computer. This applies to Windows Server 2008 or Windows Server 2008 R2.

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008
Disk space requirements for upgrading to Windows Server 2008 R2
SYSVOL location on an RODC
AD DS installation failure if SYSVOL is located at the root of a drive
A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%
AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

Disk space requirements for upgrading to Windows Server 2008

Additional disk space information may appear in the compatibility report displayed by Setup.

For the domain controller role, the volume or volumes that host the following resources also have specific free disk space requirements:

Application Data (%AppData%)
Program Files (%ProgramFiles%)
Users Data (%SystemDrive%\Documents and Settings)
Windows Directory (%WinDir%)

For example, suppose that you have the following resources located on the %WinDir% volume, with the sizes listed in the following table.

Resource	Size
Application Data (%AppData%)	100 MB
Program Files (%ProgramFiles%)	100 MB
Users Data (%SystemDrive%\Documents and Settings)	50 MB
Windows Directory (%WinDir%)	1 GB
Total size	1.25 GB

In this example, the free space on the %WinDir% volume must be equal to 1.25 gigabytes (GB) or greater.

After the upgrade, the space that was reserved for the copied resources will be returned to the file system.

Disk space requirements for upgrading to Windows Server 2008 R2

The Active Directory database, NTDS.dit, on Windows Server 2008 R2 domain controllers can be larger than in previous versions of Windows for the following reasons:

The changes in the online defragmentation process on Windows Server 2008 R2 domain controllers.
Windows Server 2008 R2 domain controllers add two new indices on the large link table.
The Windows Server 2008 R2 Recycle Bin preserves attributes on deleted objects for the Recycle object lifetime.

For Recycle Bin, the database increases in size at the following moments:
- After Windows Server 2008 R2 adprep /forestprep completes and the first Windows Server 2008 R2 domain controller is installed, there is a new indexed attribute, isRecycled, whose value is set for all deleted objects.
- After the Recycle Bin is enabled, all attributes are kept on deleted objects. More disk space is required as more object deletions occur.
In a production Windows Server 2008 R2 domain at Microsoft, the Recycle Bin feature increased the AD DS database size by an additional 15 to 20 percent of the original database size, using the defaultdeletedObjectLifetime and recycledObjectLifetime values of 180 days. Additional space requirements depend on the size and count of the objects that are recycled.

An in-place upgrade of a domain controller to Windows Server 2008 R2 requires sufficient disk space for the upgrade process to copy the following folders:

%SystemRoot%
%ProgramFiles%
%SystemDrive%\Program Files
%ProgramFiles(x86)%
%SystemDrive%\build
%SystemDrive%\InstalledRepository
%ProfilesFolder%
%ProgramData%
%SystemDrive%\Documents and Settings

The following table shows the test results for an upgrade of a domain controller from Windows Server 2008 to Windows Server 2008 R2. In this table:

<i> = 15 GB (the minimum amount of free space on a Windows hard drive that Windows setup requires)
The original size of Ntds.dit was 5 GB.

Ntds.dit location	Free space (GB) on the system drive	Result
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	1	In this scenario, Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder, but there is not enough space to copy Windows setup files. The compatibility report finds there is not enough space to copy Windows files. The upgrade is blocked at the compatibility report.
Ntds.dit is located on a different drive than the system.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.
Ntds.dit is located on the default folder: %windir%\ntds\	<i> + 1	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, which causes the compatibility report to be bypassed. However, Ntds.dit is located under the Windows folder, which causes the upgrade to copy it from the Windows.old folder to the Windows folder. This last step fails because there is not enough space on the disk to fit Ntds.dit because the database was not copied to the new operating system. On its first start, Windows Server 2008 R2 is not able to locate Ntds.dit, which causes an error and forces the computer to roll back to the previous operating system. ERROR_CODE: (NTSTATUS) 0xc00002ec - Directory Services could not start because of the following error: %hs Error Status: 0x%x. Click OK to shut down the system. You can use the recovery console to diagnose the system further. Err 0xc00002ec = STATUS_DS_INIT_FAILURE_CONSOLE The domain controller is rolled back to Windows Server 2008 successfully.
Ntds.dit is located on the same drive as the system, but it is out of %windir%.	<i>	In this scenario, the disk meets the minimum free-space requirements for the Windows Files to be installed, and Ntds.dit does not have to be copied from the Windows.old folder to the Windows folder. The compatibility report warns the user that the amount of free space meets the minimum requirements and that the upgrade process would take longer. The domain controller is upgraded successfully.

SYSVOL location on an RODC

AD DS installation failure if SYSVOL is located at the root of a drive

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

To avoid this, ensure that the Active Directory database and log files are in a volume other than the root volume of a local, nonremovable drive.

To move the Active Directory database and log files

Restart the computer, and then enter Directory Services Restore Mode (DSRM) by pressing F8 while the computer starts.
Move the Active Directory database and log files to a subdirectory at least one level beneath the root of a local drive.
Use Regedit.exe to find this registry key:HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Change the DSA Database File value to the new path from step 2, for example, x:\ntds.
Change the DSA Working Directory value to the new path from step 2, for example, x:\ntds\logs.

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

As a workaround in this situation, install the Active Directory components on a hard drive that is accessible at startup.

(You can convert drives formatted with the FAT file system with the convert.exe command-line tool.)

你可能感兴趣的:(windows,server,服务器,Microsoft,database,domain)

android系统selinux中添加新属性property 辉色投像
1.定位/android/system/sepolicy/private/property_contexts声明属性开头：persist.charge声明属性类型：u:object_r:system_prop:s0图12.定位到android/system/sepolicy/public/domain.te删除neverallow{domain-init}default_prop:property
理解Gunicorn：Python WSGI服务器的基石范范0825 ipython linux 运维
理解Gunicorn：PythonWSGI服务器的基石介绍Gunicorn，全称GreenUnicorn，是一个为PythonWSGI（WebServerGatewayInterface）应用设计的高效、轻量级HTTP服务器。作为PythonWeb应用部署的常用工具，Gunicorn以其高性能和易用性著称。本文将介绍Gunicorn的基本概念、安装和配置，帮助初学者快速上手。1.什么是Gunico
swagger访问路径 igotyback swagger
Swagger2.x版本访问地址：http://{ip}:{port}/{context-path}/swagger-ui.html{ip}是你的服务器IP地址。{port}是你的应用服务端口，通常为8080。{context-path}是你的应用上下文路径，如果应用部署在根路径下，则为空。Swagger3.x版本对于Swagger3.x版本（也称为OpenAPI3）访问地址：http://{ip
高级编程--XML+socket练习题 masa010 java 开发语言
1.北京华北2114.8万人上海华东2,500万人广州华南1292.68万人成都华西1417万人（1）使用dom4j将信息存入xml中（2）读取信息，并打印控制台（3）添加一个city节点与子节点（4）使用socketTCP协议编写服务端与客户端，客户端输入城市ID，服务器响应相应城市信息（5）使用socketTCP协议编写服务端与客户端，客户端要求用户输入city对象，服务端接收并使用dom4j
linux sdl windows.h,Windows下的SDL安装奔跑吧linux内核 linux sdl windows.h
首先你要下载并安装SDL开发包。如果装在C盘下，路径为C:\SDL1.2.5如果在WINDOWS下。你可以按以下步骤：1.打开VC++，点击"Tools",Options2,点击directories选项3.选择"Includefiles"增加一个新的路径。"C:\SDL1.2.5\include"4，现在选择"Libaryfiles“增加"C:\SDL1.2.5\lib"现在你可以开始编写你的第
将cmd中命令输出保存为txt文本文件落难Coder Windows cmd window
最近深度学习本地的训练中我们常常要在命令行中运行自己的代码，无可厚非，我们有必要保存我们的炼丹结果，但是复制命令行输出到txt是非常麻烦的，其实Windows下的命令行为我们提供了相应的操作。其基本的调用格式就是：运行指令>输出到的文件名称或者具体保存路径测试下，我打开cmd并且ping一下百度：pingwww.baidu.com>./data.txt看下相同目录下data.txt的输出：如果你再
PHP环境搭建详细教程好看资源平台前端 php
PHP是一个流行的服务器端脚本语言，广泛用于Web开发。为了使PHP能够在本地或服务器上运行，我们需要搭建一个合适的PHP环境。本教程将结合最新资料，介绍在不同操作系统上搭建PHP开发环境的多种方法，包括Windows、macOS和Linux系统的安装步骤，以及本地和Docker环境的配置。1.PHP环境搭建概述PHP环境的搭建主要分为以下几类：集成开发环境：例如XAMPP、WAMP、MAMP，这
使用 FinalShell 进行远程连接（ssh 远程连接 Linux 服务器）编程经验分享开发工具服务器 ssh linux
目录前言基本使用教程新建远程连接连接主机自定义命令路由追踪前言后端开发，必然需要和服务器打交道，部署应用，排查问题，查看运行日志等等。一般服务器都是集中部署在机房中，也有一些直接是云服务器，总而言之，程序员不可能直接和服务器直接操作，一般都是通过ssh连接来登录服务器。刚接触远程连接时，使用的是XSHELL来远程连接服务器，连接上就能够操作远程服务器了，但是仅用XSHELL并没有上传下载文件的功能
SQL Server_查询某一数据库中的所有表的内容 qq_42772833 SQL Server 数据库 sqlserver
1.查看所有表的表名要列出CrabFarmDB数据库中的所有表（名），可以使用以下SQL语句：USECrabFarmDB;--切换到目标数据库GOSELECTTABLE_NAMEFROMINFORMATION_SCHEMA.TABLESWHERETABLE_TYPE='BASETABLE';对这段SQL脚本的解释：SELECTTABLE_NAME：这个语句的作用是从查询结果中选择TABLE_NAM
git - Webhook让部署自动化大猪大猪
我们现在有一个需求，将项目打包上传到gitlab或者github后，程序能自动部署，不用手动地去服务器中进行项目更新并运行，如何做到？这里我们可以使用gitlab与github的挂钩，挂钩的原理就是，每当我们有请求到gitlab与github服务器时，这时他俩会根据我们配置的挂钩地扯进行访问，webhook挂钩程序会一直监听着某个端口请求，一但收到他们发过来的请求，这时就知道用户有请求提交了，这时
Python 实现图片裁剪（附代码） | Python工具剑客阿良_ALiang
前言本文提供将图片按照自定义尺寸进行裁剪的工具方法，一如既往的实用主义。环境依赖ffmpeg环境安装，可以参考我的另一篇文章：windowsffmpeg安装部署_阿良的博客-CSDN博客本文主要使用到的不是ffmpeg，而是ffprobe也在上面这篇文章中的zip包中。ffmpy安装：pipinstallffmpy-ihttps://pypi.douban.com/simple代码不废话了，上代码
Linux MariaDB使用OpenSSL安装SSL证书 Meta39 MySQL Oracle MariaDB Linux Windows ssl linux mariadb
进入到证书存放目录，批量删除.pem证书警告：确保已经进入到证书存放目录find.-typef-iname\*.pem-delete查看是否安装OpenSSLopensslversion没有则安装yuminstallopensslopenssl-devel开启SSL编辑/etc/my.cnf文件（没有的话就创建，但是要注意，在/etc/my.cnf.d/server.cnf配置了datadir的，
网络编程基础记得开心一点啊网络
目录♫什么是网络编程♫Socket套接字♪什么是Socket套接字♪数据报套接字♪流套接字♫数据报套接字通信模型♪数据报套接字通讯模型♪DatagramSocket♪DatagramPacket♪实现UDP的服务端代码♪实现UDP的客户端代码♫流套接字通信模型♪流套接字通讯模型♪ServerSocket♪Socket♪实现TCP的服务端代码♪实现TCP的客户端代码♫什么是网络编程网络编程，指网络上
Linux查看服务器日志 TPBoreas 运维 linux 运维
一、tail这个是我最常用的一种查看方式用法如下：tail-n10test.log查询日志尾部最后10行的日志;tail-n+10test.log查询10行之后的所有日志;tail-fn10test.log循环实时查看最后1000行记录(最常用的)一般还会配合着grep用，(实时抓包)例如:tail-fn1000test.log|grep'关键字'（动态抓包）tail-fn1000test.log
Python多线程实现大规模数据集高效转移 sand&wich 网络 python 服务器
背景在处理大规模数据集时，通常需要在不同存储设备、不同服务器或文件夹之间高效地传输数据。如果采用单线程传输方式，当数据量非常大时，整个过程会非常耗时。因此，通过多线程并行处理可以大幅提升数据传输效率。本文将分享一个基于Python多线程实现的高效数据传输工具，通过遍历源文件夹中的所有文件，将它们移动到目标文件夹。工具和库这个数据集转移工具主要依赖于以下Python标准库：os：用于文件系统操作，如
笋丁网页自动回复机器人V3.0.0免授权版源码希希分享软希网58soho_cn 源码资源笋丁网页自动回复机器人
笋丁网页机器人一款可设置自动回复，默认消息，调用自定义api接口的网页机器人。此程序后端语言使用Golang，内存占用最高不超过30MB，1H1G服务器流畅运行。仅支持Linux服务器部署，不支持虚拟主机，请悉知！使用自定义api功能需要有一定的建站基础。源码下载：https://download.csdn.net/download/m0_66047725/89754250更多资源下载：关注我。安
2023最详细的Python安装教程（Windows版本）程序员林哥 Python python windows 开发语言
python安装是学习pyhon第一步，很多刚入门小白不清楚如何安装python，今天我来带大家完成python安装与配置，跟着我一步步来，很简单，你肯定能完成。第一部分：python安装（一）准备工作1、下载和安装python(认准官方网站)当然你不想去下载的话也可以分享给你，还有入门学习教程，点击下方卡片跳转进群领取（二）开始安装对于Windows操作系统，可以下载“executableins
博客网站制作教程 2401_85194651 java maven
首先就是技术框架：后端：Java+SpringBoot数据库：MySQL前端：Vue.js数据库连接：JPA(JavaPersistenceAPI)1.项目结构blog-app/├──backend/│├──src/main/java/com/example/blogapp/││├──BlogApplication.java││├──config/│││└──DatabaseConfig.java
深入浅出 -- 系统架构之负载均衡Nginx的性能优化 xiaoli8748_软件开发系统架构系统架构负载均衡 nginx
一、Nginx性能优化到这里文章的篇幅较长了，最后再来聊一下关于Nginx的性能优化，主要就简单说说收益最高的几个优化项，在这块就不再展开叙述了，毕竟影响性能都有多方面原因导致的，比如网络、服务器硬件、操作系统、后端服务、程序自身、数据库服务等，对于性能调优比较感兴趣的可以参考之前《JVM性能调优》中的调优思想。优化一：打开长连接配置通常Nginx作为代理服务，负责分发客户端的请求，那么建议开启H
最简单将静态网页挂载到服务器上(不用nginx) 全能全知者服务器 nginx 运维前端 html 笔记
最简单将静态网页挂载到服务器上(不用nginx)如果随便弄个静态网页挂在服务器都要用nignx就太麻烦了，所以直接使用Apache来搭建一些简单前端静态网页会相对方便很多检查Web服务器服务状态：sudosystemctlstatushttpd#ApacheWeb服务器如果发现没有安装web服务器：安装Apache：sudoyuminstallhttpd启动Apache：sudosystemctl
阿里云服务器4核8G配置购买及价格类文章汇总（10篇）阿里云最新优惠和活动汇总
阿里云服务器4核8G配置如何购买？价格是多少？4核8G配置的阿里云服务器可以通过云服务器产品页购买也可以通过阿里云活动去下单购买，一般通过活动购买的用户比较多，但是不同实例规格的阿里云服务器价格不一样，带宽不同价格也不一样，本文为大家汇总了10篇关于阿里云服务器4核8G配置购买教程文章和价格类文章，分为购买类文章和价格类文章，以供大家参考如何购买阿里云服务器4核8G配置和最新优惠价格是多少。阿里云
windows下python opencv ffmpeg读取摄像头实现rtsp推流拉流图像处理大大大大大牛啊 opencv实战代码讲解视觉图像项目 windows python opencv
windows下pythonopencvffmpeg读取摄像头实现rtsp推流拉流整体流程1.下载所需文件1.1下载rtsp推流服务器1.2下载ffmpeg2.开启RTSP服务器3.opencv读取摄像头并调用ffmpeg进行推流4.opencv进行拉流5.opencv异步拉流整体流程1.下载所需文件1.1下载rtsp推流服务器下载RTSP服务器下载页面https://github.com/blu
NPM私库搭建-verdaccio（Linux） Beam007 npm linux 前端
1、安装nodelinux服务器安装nodea)、官网下载所需的node版本https://nodejs.org/dist/v14.21.0/b)、解压安装包若下载的是xxx.tar.xz文件，解压命令为tar-xvfxxx.tar.xzc)、修改环境变量修改：/etc/profile文件#SETPATHFORNODEJSexportNODE_HOME=NODEJS解压安装的路径exportPAT
[实验室服务器使用]使用VSCode、PyCharm、MobaXterm和CMD连接远程服务器 YuanDaima2048 工具使用服务器 vscode pycharm cmd 代理模式机器学习实验
文章总览：YuanDaiMa2048博客文章总览实验室服务器使用：使用VSCode、PyCharm、MobaXterm和CMD连接远程服务器在进行实验室工作时，远程连接服务器是常见的需求之一。本篇文章根据个人的一些使用介绍使用不同工具连接服务器的方法，并提供优化功能，使服务器能够使用本机代理的说明。准备服务器账号信息Host（主机）:10.XXX.XX.XXXPort（端口）:[SSHPort]U
You have an error in your SQL syntax； check the manual that corresponds to your MySQL server version 努力的菜鸟~ sql 数据库
YouhaveanerrorinyourSQLsyntax;checkthemanualthatcorrespondstoyourMySQLserverversionfortherightsyntaxtousenear‘IDENTIFIEDBY‘123456’WITHGRANTOPTION’atline1在mysql5.7之前GRANTALLPRIVILEGESON*.*TO'root'@'%'I
mysql学习教程，从入门到精通，TOP 和MySQL LIMIT 子句（15）知识分享小能手大数据数据库 MySQL mysql 学习 oracle 数据库开发语言 adb 大数据
1、TOP和MySQLLIMIT子句内容在SQL中，不同的数据库系统对于限制查询结果的数量有不同的实现方式。TOP关键字主要用于SQLServer和Access数据库中，而LIMIT子句则主要用于MySQL、PostgreSQL（通过LIMIT/OFFSET语法）、SQLite等数据库中。下面将分别详细介绍这两个功能的语法、语句以及案例。1.1、TOP子句（SQLServer和Access）1.1
L1 L2 L3 缓存京天不下雨 windows 缓存 windows
L1L2L3缓存L1Cache(一级bai缓存)是CPU第一层高速缓存，分为数据缓存和指令缓存。du内置的zhiL1高速缓存的容量和结构对daoCPU的性能影响较大，不过高速缓冲存储器均由静态RAM组成，结构较复杂，在CPU管芯面积不能太大的情况下，L1级高速缓存的容量不可能做得太大。一般服务器CPU的L1缓存的容量通常在32—4096KB。L2由于L1级高速缓存容量的限制，为了再次提高CPU的运
golang实现从服务器下载文件到本地指定目录余生逆风飞翔 golang 服务器开发语言
一、连接服务器，采用sftp连接模式packagemiddlewaresimport("fmt""time""github.com/pkg/sftp""golang.org/x/crypto/ssh")//建立服务器连接funcConnect(user,password,hoststring,portint)(*sftp.Client,error){var(auth[]ssh.AuthMethod
鲲鹏 ARM 架构麒麟 Lylin v10 安装 Nginx (离线) 焚木灵 arm开发架构 nginx 服务器
最近做一个银行的项目，银行的服务器是鲲鹏ARM架构的服务器，并且是麒麟v10的系统，这里记录一下在无法访问外网安装Nginx的方法。其他文章：鲲鹏ARM架构麒麟Lylinv10安装Mysql8.3(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Node和NVM(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Pm2(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装P
Istio pilot-discovery服务发现源码解析（1.13版本） xidianjiapei001 #Istio istio 云原生服务发现
Istiopilot-discovery服务发现介绍工作机制初始化初始化Config控制器初始化Service控制器controller初始化NamespaceServiceNodePodPilotDiscovery各组件启动流程DiscoveryServer接收Envoy的gRPC连接请求流程Config变化后向Envoy推送更新的流程总结参考介绍IstioPilot的代码分为Pilot-Dis
继之前的线程循环加到窗口中运行 3213213333332132 java thread JFrame JPanel
之前写了有关java线程的循环执行和结束，因为想制作成exe文件，想把执行的效果加到窗口上，所以就结合了JFrame和JPanel写了这个程序，这里直接贴出代码，在窗口上运行的效果下面有附图。 package thread; import java.awt.Graphics; import java.text.SimpleDateFormat; import java.util
linux 常用命令 BlueSkator linux 命令
1.grep 相信这个命令可以说是大家最常用的命令之一了。尤其是查询生产环境的日志，这个命令绝对是必不可少的。但之前总是习惯于使用（grep -n 关键字文件名）查出关键字以及该关键字所在的行数，然后再用（sed -n '100,200p' 文件名），去查出该关键字之后的日志内容。但其实还有更简便的办法，就是用（grep -B n、-A n、-C n 关键
php heredoc原文档和nowdoc语法 dcj3sjt126com PHP heredoc nowdoc
<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <title>Current To-Do List</title> </head> <body> <?
overflow的属性周华华 JavaScript
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml&q
《我所了解的Java》——总体目录 g21121 java
准备用一年左右时间写一个系列的文章《我所了解的Java》，目录及内容会不断完善及调整。在编写相关内容时难免出现笔误、代码无法执行、名词理解错误等，请大家及时指出，我会第一时间更正。 &n
[简单]docx4j常用方法小结 53873039oycg docx
本代码基于docx4j-3.2.0，在office word 2007上测试通过。代码如下: import java.io.File; import java.io.FileInputStream; import ja
Spring配置学习云端月影 spring配置
首先来看一个标准的Spring配置文件 applicationContext.xml <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi=&q
Java新手入门的30个基本概念三 aijuans java 新手 java 入门
17.Java中的每一个类都是从Object类扩展而来的。　　18.object类中的equal和toString方法。　　equal用于测试一个对象是否同另一个对象相等。　　toString返回一个代表该对象的字符串,几乎每一个类都会重载该方法,以便返回当前状态的正确表示.(toString 方法是一个很重要的方法)　　 19.通用编程:任何类类型的所有值都可以同object类性的变量来代替。　
《2008 IBM Rational 软件开发高峰论坛会议》小记 antonyup_2006 软件测试敏捷开发项目管理 IBM 活动
我一直想写些总结,用于交流和备忘,然都没提笔,今以一篇参加活动的感受小记开个头,呵呵! 其实参加《2008 IBM Rational 软件开发高峰论坛会议》是9月4号,那天刚好调休.但接着项目颇为忙,所以今天在中秋佳节的假期里整理了下. 参加这次活动是一个朋友给的一个邀请书,才知道有这样的一个活动,虽然现在项目暂时没用到IBM的解决方案,但觉的参与这样一个活动可以拓宽下视野和相关知识.
PL/SQL的过程编程,异常,声明变量,PL/SQL块百合不是茶 PL/SQL的过程编程异常 PL/SQL块声明变量
PL/SQL; 过程; 符号; 变量; PL/SQL块; 输出; 异常; PL/SQL 是过程语言(Procedural Language)与结构化查询语言(SQL)结合而成的编程语言PL/SQL 是对 SQL 的扩展,sql的执行时每次都要写操作
Mockito(三)--完整功能介绍 bijian1013 持续集成 mockito 单元测试
mockito官网：http://code.google.com/p/mockito/，打开documentation可以看到官方最新的文档资料。一.使用mockito验证行为 //首先要import Mockito import static org.mockito.Mockito.*; //mo
精通Oracle10编程SQL(8)使用复合数据类型 bijian1013 oracle 数据库 plsql
/* *使用复合数据类型 */ --PL/SQL记录 --定义PL/SQL记录 --自定义PL/SQL记录 DECLARE TYPE emp_record_type IS RECORD( name emp.ename%TYPE, salary emp.sal%TYPE, dno emp.deptno%TYPE ); emp_
【Linux常用命令一】grep命令 bit1129 Linux常用命令
grep命令格式 grep [option] pattern [file-list] grep命令用于在指定的文件(一个或者多个,file-list)中查找包含模式串(pattern)的行,[option]用于控制grep命令的查找方式。 pattern可以是普通字符串，也可以是正则表达式，当查找的字符串包含正则表达式字符或者特
mybatis3入门学习笔记白糖_ sql ibatis qq jdbc 配置管理
MyBatis 的前身就是iBatis，是一个数据持久层(ORM)框架。 MyBatis 是支持普通 SQL 查询，存储过程和高级映射的优秀持久层框架。MyBatis对JDBC进行了一次很浅的封装。以前也学过iBatis，因为MyBatis是iBatis的升级版本，最初以为改动应该不大，实际结果是MyBatis对配置文件进行了一些大的改动，使整个框架更加方便人性化。
Linux 命令神器：lsof 入门 ronin47 lsof
lsof是系统管理/安全的尤伯工具。我大多数时候用它来从系统获得与网络连接相关的信息，但那只是这个强大而又鲜为人知的应用的第一步。将这个工具称之为lsof真实名副其实，因为它是指“列出打开文件（lists openfiles）”。而有一点要切记，在Unix中一切（包括网络套接口）都是文件。有趣的是，lsof也是有着最多
java实现两个大数相加，可能存在溢出。 bylijinnan java实现
import java.math.BigInteger; import java.util.regex.Matcher; import java.util.regex.Pattern; public class BigIntegerAddition { /** * 题目：java实现两个大数相加，可能存在溢出。 * 如123456789 + 987654321
Kettle学习资料分享，附大神用Kettle的一套流程完成对整个数据库迁移方法 Kai_Ge Kettle
Kettle学习资料分享 Kettle 3.2 使用说明书目录概述..........................................................................................................................................7 1.Kettle 资源库管
[货币与金融]钢之炼金术士 comsci 金融
自古以来,都有一些人在从事炼金术的工作.........但是很少有成功的那么随着人类在理论物理和工程物理上面取得的一些突破性进展...... 炼金术这个古老
Toast原来也可以多样化 dai_lm android toast
Style 1：默认 Toast def = Toast.makeText(this, "default", Toast.LENGTH_SHORT); def.show(); Style 2：顶部显示 Toast top = Toast.makeText(this, "top", Toast.LENGTH_SHORT); t
java数据计算的几种解决方法3 datamachine java hadoop ibatis r-langue r
4、iBatis 简单敏捷因此强大的数据计算层。和Hibernate不同，它鼓励写SQL，所以学习成本最低。同时它用最小的代价实现了计算脚本和JAVA代码的解耦，只用20%的代价就实现了hibernate 80%的功能,没实现的20%是计算脚本和数据库的解耦。复杂计算环境是它的弱项，比如：分布式计算、复杂计算、非数据
向网页中插入透明Flash的方法和技巧 dcj3sjt126com html Web Flash
将 Flash 作品插入网页的时候，我们有时候会需要将它设为透明，有时候我们需要在Flash的背面插入一些漂亮的图片，搭配出漂亮的效果……下面我们介绍一些将Flash插入网页中的一些透明的设置技巧。　　一、Swf透明、无坐标控制　　首先教大家最简单的插入Flash的代码，透明，无坐标控制：　　注意wmode="transparent"是控制Flash是否透明
ios UICollectionView的使用 dcj3sjt126com
UICollectionView的使用有两种方法，一种是继承UICollectionViewController，这个Controller会自带一个UICollectionView；另外一种是作为一个视图放在普通的UIViewController里面。个人更喜欢第二种。下面采用第二种方式简单介绍一下UICollectionView的使用。 1.UIViewController实现委托，代码如
Eos平台java公共逻辑蕃薯耀 Eos平台java公共逻辑 Eos平台 java公共逻辑
Eos平台java公共逻辑 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 蕃薯耀 2015年6月1日 17:20:4
SpringMVC4零配置--Web上下文配置【MvcConfig】 hanqunfeng springmvc4
与SpringSecurity的配置类似，spring同样为我们提供了一个实现类WebMvcConfigurationSupport和一个注解@EnableWebMvc以帮助我们减少bean的声明。 applicationContext-MvcConfig.xml  <
解决ie和其他浏览器poi下载excel文件名乱码 jackyrong Excel
使用poi,做传统的excel导出，然后想在浏览器中，让用户选择另存为，保存用户下载的xls文件，这个时候，可能的是在ie下出现乱码（ie,9,10,11),但在firefox,chrome下没乱码，因此必须综合判断，编写一个工具类： /** * * @Title: pro
挥洒泪水的青春 lampcy 编程生活程序员
2015年2月28日，我辞职了，离开了相处一年的触控，转过身--挥洒掉泪水，毅然来到了兄弟连，背负着许多的不解、质疑——”你一个零基础、脑子又不聪明的人，还敢跨行业，选择Unity3D？“，”真是不自量力••••••“，”真是初生牛犊不怕虎•••••“，••••••我只是淡淡一笑，拎着行李----坐上了通向挥洒泪水的青春之地——兄弟连！这就是我青春的分割线，不后悔，只会去用泪水浇灌——已经来到
稳增长之中国股市两点意见-----严控做空，建立涨跌停版停牌重组机制 nannan408
对于股市，我们国家的监管还是有点拼的，但始终拼不过飞流直下的恐慌，为什么呢？笔者首先支持股市的监管。对于股市越管越荡的现象，笔者认为首先是做空力量超过了股市自身的升力，并且对于跌停停牌重组的快速反应还没建立好，上市公司对于股价下跌没有很好的利好支撑。我们来看美国和香港是怎么应对股灾的。美国是靠禁止重要股票做空，在
动态设置iframe高度(iframe高度自适应) Rainbow702 JavaScript iframe contentDocument 高度自适应局部刷新
如果需要对画面中的部分区域作局部刷新，大家可能都会想到使用ajax。但有些情况下，须使用在页面中嵌入一个iframe来作局部刷新。对于使用iframe的情况，发现有一个问题，就是iframe中的页面的高度可能会很高，但是外面页面并不会被iframe内部页面给撑开，如下面的结构： <div id="content"> <div id=&quo
用Rapael做图表 tntxia rap
function drawReport(paper,attr,data){ var width = attr.width; var height = attr.height; var max = 0; &nbs
HTML5 bootstrap2网页兼容（支持IE10以下） xiaoluode html5 bootstrap
<!DOCTYPE html> <html> <head lang="zh-CN"> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge">

Windows Server 2003域服务器的搭建 中遇到的问题

Adprep.exe issues

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008

Disk space requirements for upgrading to Windows Server 2008 R2

SYSVOL location on an RODC

AD DS installation failure if SYSVOL is located at the root of a drive

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

To move the Active Directory database and log files

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

Adprep.exe issues

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008

Disk space requirements for upgrading to Windows Server 2008 R2

SYSVOL location on an RODC

AD DS installation failure if SYSVOL is located at the root of a drive

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

To move the Active Directory database and log files

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

Adprep.exe issues

Active Directory Domain Services Installation Wizard (Dcpromo.exe) issues

Disk space and component location issues

Disk space requirements for upgrading to Windows Server 2008

Disk space requirements for upgrading to Windows Server 2008 R2

SYSVOL location on an RODC

AD DS installation failure if SYSVOL is located at the root of a drive

A Stop error occurs if Active Directory database and log files are located in the root of a directory of a disk that does not contain %systemroot%

To move the Active Directory database and log files

AD DS installation can fail if directory components or operating system files are placed on advanced drive types such as iSCSI devices

你可能感兴趣的:(windows,server,服务器,Microsoft,database,domain)

Windows Server 2003域服务器的搭建中遇到的问题