XI, configure DNS in the new working group environment in Windows Server 2003
SUMMARY This step-by-step guide is facing a new working group without a Domain Name System (DNS) server. With DNS servers, users can use friendly names with resources. "Friendly" name is a simple English name representing network resources. You can use the DNS name to publish and naming all networked resources in the workgroup.
Installing the DNS service Before configuring, you must install DNS service on the server. By default, DNS is not installed during the installation of Windows Server 2003. You can install DNS after or after the installation process. How to install the DNS service on an existing server Click Start, point to Control Panel, and then click Change or Remove Programs. Click Add / Remove Windows Components. In the list of components, click Network (but do not select or clear the check box), then click Details. Click the Domain Name System (DNS) check box, select it, and then click OK. Click Next. When prompted, insert the Windows Server 2003 CD-ROM into the computer's CD-ROM drive or DVD-ROM drive. When the installation is complete, in the Finish Windows Component Wizard page, click Finish. Click Close to close the Add or Remove Programs window.
How to install the DNS service during the installation process To install DNS during the initial installation of Windows Server 2003, please prompt you to install and configure Windows components, follow this article "How to Install DNS Service on Existing Servers" in this article Step 3 and 4 perform XX work. Configuring the DNS server to run correctly, the DNS server requires a positive search area so that its local domain is a host recorded by the locator. The forward search area contains the information necessary to analyze the names in the DNS domain. You may also need to configure the reverse search area so that the user can determine its name according to the IP address of the local resource. In addition, in order to simplify the management of DNS services as much as possible, you should configure these regions to accept dynamic updates.
After installing the DNS service, use the Configure DNS Server Wizard to configure DNS services.
How to configure DNS services Click Start, point to Administrative Tools, and then click DNS. Right-click the server name, where the server name is the name of the server, and then click Configure the DNS server.
"Configuring DNS Server Wizard" will start. Click the DNS list, read the DNS list, and then click Next. Based on the role of the DNS server, click Next, click Next: Create a forward search area (recommended for small networks). Use this option for a small network that uses Active Directory or use Internet Service Provider (ISP) to resolve DNS name queries. By using this option, you can: create a DNS area for the DNS domain used by the Active Directory domain used by your network. Create a second area for the DNS area carried by the DNS server in your ISP. Create a forward and reverse search area (recommended for large networks). Use this option if you want to add a DNS server to a large network that has a DNS structure. By using this option, you can: Create a forward and reverse area to resolve queries in the DNS domain of your DNS namespace. Specifies that the DNS server is used as a transponder, and the name query that this DNS server cannot answer will be sent here. Specify a replication range for the area you want to create (if this DNS is running on the Active Directory domain controller). Specifies that the DNS server is used as a transponder, and the name query that this DNS server cannot answer will be sent here. Configure dynamic updates to the area you want to create. Only the root prompt is configured (only the advanced user is recommended for this XX). Use this option if you want to create a pure forward DNS server, or you want to add a root prompt to the DNS server that is currently configured with the area and the repeater. Follow the instructions on the balance of the wizard to configure your DNS server. How to configure a forward search area to allow dynamic updates to configure a new forward search area, configure these areas to allow dynamic updates (if you are not used)
Click Start, point to Administrative Tools, and then click DNS. Expand the server name, where the server name is the name of the server and then expands the forward search area. Right-click the forward search area created for your domain and click Properties. Click General tab, click Yes, and then click OK.
12. Assign a login script to the local user profile in Windows Server 2003
SUMMARY This article describes how to assign a login script in the configuration files for the local user account in Windows Server 2003. This login script runs when you log in to your computer locally. This login script does not run when the user logs in to the domain.
Note: You must log in as a member of the administrator or administrator group to complete this step. If your computer is connected, the network policy settings may also make you unable to complete this process.
How to assign the login script to the User Profile Click Start, point to Administrative Tool, and then click Computer Management. In the console tree, expand Local Users and Groups, and then click Users. In the right pane, right-click the desired user account and click Properties. Click the Profile tab. In the Login Script box, type the file name of the login script (if needed, type the relative path).
Note: If the login script is stored in the subfolder of the default login script path, add the relative path of the folder before the file name. For example, if the startup.bat login script is stored in // Computer Name / NetLogon / Folder Name £? Please type folder name /startup.bat. Click Apply, and then click OK. Note: The login script stored on the local computer is only available to users who log in to the local computer. The local login script must be stored in a folder using the "NetLogon" shared name, or must be stored in the subfolder of the NetLogon folder. The default location of the local login script is the SystemRoot / System32 / RESTEMROOTS / SCRIPTS folder. This folder is not created in the new installed Windows. Therefore, you must create and share the SystemRoot / System32 / REPL / IMPORTS / Scripts folder by using the "Netlogon" shared name. If you don't want to create a "NetLogon" shared by default, place the login script in any folder that the user can access during the login process and share this folder. Thirteen, configure the NAT server in Windows Server 2003
SUMMARY This article describes how to configure the Network Address Translation (NAT) server by using Windows Server 2003. Windows Server 2003 "Routing and Remote Access" services include NAT routing protocols. If you install NAT routing protocols on a server running "Routing and Remote Access", the internal network client using a dedicated Internet Protocol (IP) address can access the Internet via the external interface of the NAT server.
How to configure routing and remote access NAT Server When the internal network client sends a request to connect to the Internet, the NAT protocol driver intercepts the request and forwards it to the target Internet server. All requests look like an external IP address from the NAT server. This hides your internal IP address configuration.
Configuring "Routing and Remote Access" NAT Server: In the Administrative Tools menu, click Routing and Remote Access. In "Routing and Remote Access" MMC, expand your server name (where the server name is the name you want to configure the server, then expand the IP route in the left pane. Right-click General, and then click New Routing Protocol. Single Tap NAT / Basic Firewall check box, select it, and then click OK. Right-click the NAT / Basic Firewall in the left pane, and then click the New Interface. Click the interface indicating the internal network interface, then click OK In the Network Address Conversion Properties, click the "Private Interface Connect to Private Network", then click OK. Right-click the NAT / Basic Firewall in the left pane, and then click New Interface. Click to represent the external network Interface of the interface, then click OK. In the Network Address Translation property, click the "Public Interface Connect to the Internet". Click "Enabling the NAT" check box on this interface, select it, and then click OK The NAT server can automatically assign an IP address for the internal network client. If you do not have the DHCP server that has been assigned address information on the home network, you may need to use this feature.
How to configure routing and remote access NAT servers to assign IP addresses and execute proxy DNS Query NAT servers can also perform a domain name system (DNS) query on behalf of the NAT client. "Routing and Remote Access" NAT server parsed the Internet hostname included in the client request and then forwarding the IP address to the client.
To configure the Routing and Remote Access NAT server to assign an IP address and represent the internal network client execution proxy DNS query, follow these step xx: Right-click the NAT / Basic Firewall in the left pane, and then click Properties. Click Address Assignment tab, and then click the "Automatically Assign IP Address" check box to use the DHCP. In the IP address box, type the network ID. In the mask box, type the subnet mask. Click the Name Resolution tab, and then click Use the Domain Name System (DNS) to check boxes. If you are connected to the Internet using the request dial interface, click "Connect to the Public Network" check box when the name needs to be parsed, will be selected. In the request dial-up interface box, click the interface you want to dial. Click Apply, and then click OK. Note: After completing these basic configuration steps, the internal network client can access the server on the Internet.
How to configure Windows Server 2003-based computers to use the NAT server to start, point to the Control Panel, point to Network Connections, and then click Locally. Click Properties. Click Internet Protocol (TCP / IP). Click Properties. In the Default Gateway box, type the internal IP address of the NAT server.
Note: If your computer receives its IP address from the Dynamic Host Configuration Protocol (DHCP) server, click Advanced, click the IP Settings tab, click Add, Type the internal IP address of the NAT server, click Add, click OK, then proceed to step 6. Click OK, click OK, and then click Close.
Fourteen, configure the printer and print server settings in Windows Server 2003
Summary This article describes how to configure printers and print server settings in Windows Server 2003. It also describes how to perform some of the more common management tasks, for example, how to configure a separate page and print notifications.
Configuring printer settings is performed in the printer properties of the printer, configuring print server settings are made in the print server properties. You must log in as a member of the administrator or administrator group to perform these steps.
How to configure printer settings Please note that for different printers, options you can configure may vary. This section describes how to configure general settings available in most printers. Click Start, and then click Print and Fax. Right-click the printer you want to configure and click Properties. You can configure the options you want using any of the following methods (how appropriate): Configuring Separation: Click the Advanced tab, and then click Separator. To add a separate page, type the path to the file you want to use as a file from the Separation page, and then click OK. Or, click Browse, find the file you want to use, click Open, and then click OK. To delete a separator, delete an entry in the Sneakers box, then click OK. Configure the print processor: Click the Advanced tab, and then click the Print Processor. In the Default Data Type box, click the type of data you want to use, and then click OK. Add printer drivers for Windows other versions: Click the Shared Tab, and then click Other Drivers. Click the check box next to the driver you want to add, select it, and then click OK. Modify User Access Permissions: Click the Security tab, then do one of the following XX: To change the privileges of existing users or groups, click Group or User Name list, click the group you want to modify its permissions or user. To configure permissions for new users or groups, click Add. In the Select User or Group dialog box, type the name of the user or group you want to set permissions, and then click OK. In the user or group's permission list, click the Allow check box next to the permissions you want to Allow, select it, or click the rejection check box next to the permissions you want to reject, and select it. Or, to delete a user or group from the Group or User Name list, click Remove. Click OK. How to Configure Printer Server Settings This section describes some of the common print server settings you can configure. Click Start, and then click Print and Fax. On the File menu, click Server Properties. You can configure the options you want using any of the following methods (as needed): Configure the port settings of the printer: Click the Port tab. To configure port, click the port you want to configure in the Port of this Server, and then click Configure Port. Type the number of seconds in the transfer retry box (if the printer is lost to reach this second, you will get notifications), then click OK. To add a new port, click Add Port, and then click the Port Type you want to add in the "Available Port Type" box, then click the new port. Type the name you want to specify to the new port in the Enter Port Name box, and then click OK. To delete a port, click the port you want to delete in the "Port of this server" box, click Remove Port, and then click Yes, confirm the deletion. Add, delete, or reinstall the current printer driver: Click the Driver tab. In the Installation Printer Driver box, click the driver you want to modify, then click Add, Remove, or Reinstall (as needed). Add, delete, or reinstall the printer driver according to the description displayed on the screen. Turn the printer notification in or off:
Click the Advanced tab, and then click the "Remote Document Print Complete Notification" check box to select or clear it.
Click the Advanced tab. Click the check box next to the records you want to record the check box next to the Backup Options (or multiple options), select or clear it. Click OK.
Fifteen, use the Sysprep Tool to Clear the page file before the image is created in the Windows Server 2003 Series products
SUMMARY This article describes how to use the Microsoft Sysprep tool to automatically complete the deletion of page files (to reduce the overall size of the reproduction image) before creating a Windows Server 2003 image. Note: Microsoft recommends that you do not use sysprep on the domain controller.
WARNING: "Registry Editor" can cause serious problems, these issues may need to reinstall the XX as system. Microsoft does not guarantee the problem that the "Registry Editor" uses improper use. Use Registry Editor at your own risk.
To use sysprep to complete the deletion of page files before creating a Windows Server 2003 image, use one of the following methods.
Method 1 Start the Registry Editor (regedit.exe). Find pagingfiles values in the following registry key: hkey_local_machine / system / currentcontrolset / control / session manager / memory management
Double-click the PagingFiles value, then type the following: c: /pagefile.sys 0 0
Click OK. Exit Registry Editor". Run sysprep. The registry settings in Method 1 will force Windows to delete page files when you turn Windows. You can then use your favorite way to create a mounting partition image and deploy it to the target computer. During the first guidance of the target system, the page file settings above it will match the size to the memory module of the new system after deployment.
Method 2 Create a registry (.reg) file called Zeropage.Reg using any of the following procedures: Start the Registry Editor (regedit.exe). Find pagingfiles values in the following registry key: hkey_local_machine / system / currentcontrolset / control / session manager / memory management
Double-click the PagingFiles value, then type the following: c: /pagefile.sys 0 0
Click OK. On the File menu, click Export, and then export this item to a file named Zeropage.REG. Exit Registry Editor". - or -
Copy the following text into a .reg file named Zeropage.reg: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Control / Session Manager / Memory Management] "PagingFiles" = hex (7): 43,00,3a 00, 5C, 00, 70, 100, 61, 67, 100, 65, 100, 66, 69, 100, 6C, / 00, 65, 0, 2E, 00, 73, 100, 79, 00, 73, 200, 20, 30, 200, 20, 30, 100, 100, 100,000
Copy the following text and any other sysprep command line parameters to a batch file named sysprep.cmd: regedit / s A: /ZEROPAGE.REG A: / SYSPREP -NOREBOOT -PNP
The new computer memory matching on the standard computer.
XVI, add components and programs to your computer in Windows Server 2003 series products
Summary This article describes how to add a program and a Windows component to a Windows Server 2003-based computer.
The Add or Remove Programs tool helps you manage programs on your computer. With this tool, you can add new programs or changes to delete existing programs. You can also use the Add or Remove Programs tool to add your Windows Server 2003 components that are not installed during initial installation. How to install the Windows component to log in to your computer as a member of the Administrator or "Administrator" group. Click Start, point to Control Panel, and then click Add or Remove Programs. Click Add / Remove Windows Components. The Windows Components page of the Windows Component Wizard appears on the screen, the following components are listed in the component list (Windows components displayed in this list may vary depending on the version of Windows Server 2003): attachments and Tool Certificate Service Fax Services Index Services Internet Explorer Internet Information Services (IIS) Administration and Monitoring Tool Message Queue Network Services Other Network Files and Print Services POP3 Services Remote Installation Services Remote Storage Terminal Server Terminal Server Authorized UDDI Services Update Root Category Certificate Windows Media service
To add a component, click the appropriate check box to select it. To delete a component, click the appropriate check box to clear it.
Remarks: The box with a shading indicates that only part of the component can be installed. To view the contents of the component, click the component, and then click Details. Click the check box next to the subcaps you want to add, select it, and then click OK.
Note: If the details button (gray) cannot be used, the component does not have a subcomponent associated with it. Click Next. In accordance with the description of the remaining pages of the Windows Component Wizard, XX works. Click Close to close the Add or Remove Programs dialog. Note: You need to configure before using some Windows components. If one or more such components are installed, but do not configure them, when you click Add / Remove Windows Components, a list of components that must be configured will be displayed. To configure components, click Configure and follow the instructions on the screen XX. To add a new component, click Components, follow the instructions in the Windows Component Wizard to perform XX.
The installation example of the DHCP service logs in to the computer as a member of the "Administrator" or "Administrator" group. Click Start, point to Control Panel, and then click Add or Remove Programs. Click Add / Remove Windows Components. In the list of components, click Network (but do not select or clear the check box), then click Details. Click the "Dynamic Host Configuration Protocol (DHCP)" check box, select it (if not selected), then click OK. Click Next. When prompted, insert the Windows Server 2003 CD-ROM into your computer's CD-ROM or DVD-ROM drive.
The installer copies the DHCP server and tool files to your computer. When the installation is complete, click Finish the completion of the Windows Component Wizard page. Click Close to close the Add or Remove Programs dialog.
How to install the program To install the program, follow the steps below XX (if your situation). Log in from the CD-ROM or floppy disk installer as a member of the "Administrator" or "Administrator" group. Click Start, point to Control Panel, and then click Add or Remove Programs. Click Add new program. Click CD or floppy disk. Insert the floppy disk into the computer's floppy drive, or insert the CD-ROM into the computer's CD-ROM or DVD-ROM drive, and then click Next. Follow the instructions displayed on the screen for XX to install the program. Click Close to close the Add or Remove Programs dialog. Note: When using the Add / Remove Programs tool, you can only install the program written for the Windows XX as a system. Log in from the network installer as a member of the "Administrator" or "Administrator" group. Mode installation; program file has been deleted or corrupted; or you try to use the program functionality that is not installed during installation. If the program is installed from a CD-ROM, or you are no longer connected to the network, the Windows installer may prompt you to insert the CD-ROM or DVD-ROM drive. When the Windows installer is complete, the programs or feature attempt to use will be started.
17. Application Registry and File System ACL on a computer upgraded from Windows NT 4.0 to Windows Server 2003
SUMMARY This step-by-step guide describes how to apply Registry "Access Control List" (ACLS) and file system ACLs on a computer upgraded from Windows NT 4.0 to Windows Server 2003.
When upgrading Windows NT 4.0-based computers to Windows Server 2003, "Windows Installer" does not change the registry and file system
ACL. Windows Server 2003 allows for higher level security, and it is dealing with the registry and file system permissions. It is different from Windows NT 4.0. Microsoft recommends that you apply Windows 2003 ACL to your computer upgraded from Windows NT 4.0.
To apply registry and file system ACL, you can use the Security Configuration and Analysis management unit. Note that you must be a member of the "Administrators" group to perform this process.
How to apply the default system security settings on a computer upgraded from Windows NT 4.0 to Windows Server 2003 to log in as "Administrator" or "Administrators" group member. Click Start, click Run, type the MMC in the Open box, and then click OK. On the File menu, click Add / Delete Administration Unit. Click Add, Secure Configuration, and Analyze, Add, click Close, and then click OK. In the console tree, right-click Security Configuration and Analysis, and then click Open Database. Specify the name of the database (for example, UpGDBase) and location, and then click Open. In the Import Template dialog box appearing on the screen, click Set Security.inf, and then click Open. Right-click Secure Configuration and Analysis, and then click Analyze your computer now. In the Executation Analysis dialog box appearing on the screen, accept the default log file path displayed in the Error Log File Path box, or specify the required location, and then click OK.
This template security setting is compared to existing computer settings.
Note: At this point, you will not make any changes to your computer. The results of this process indicate what the security settings in the template are different from the actual system settings. When analyzing, expand the various components in the console tree, such as account policies, local policies, event logs, restricted groups, and system services. For each component expanded in step 10, view its security property item in the right pane of the policy column, and pay attention to the following: items with green selection indicates the current computer settings and databases Safety settings are the same. Items with red "X" indicates that the current computer settings are different from security settings in the database. This security attribute is not defined in the template if the green selection tag or red "X" is not displayed, and it is not analyzed. If you want to add or modify the database settings, right-click the security properties you want to add or modified, and then click Properties. Click "Define this Policy in the Database" check box, select (if not yet selected), make the desired changes to the policy settings, and then click OK.
Remarks: The Database Settings Column will display the security settings contained in the template, and the computer settings column displays the current settings of your computer. To configure your computer to use security settings in a database, right-click Secure Configuration and Analysis, and then click Configure your computer. In the Configuration System dialog box appearing on the screen, accept the default path and log file name, or type the required path and file name, then click OK.
The secure database configuration is applied to your computer.
Note: If there is a conflict between the database items and the existing security configuration on your computer unless you eliminate the difference between the two before configuring your computer, the existing project will be rewritten.
Eighth, apply local strategy to all users other than administrators in Windows Server 2003 in WINDOWS SERVER 2003 in Working Group
SUMMARY This article describes how to apply local policies to all users other than administrators on a WINDOWS Server 2003-based computer.
When using Windows Server 2003-based computers in Working Group Settings (rather than domain), you may need to implement local policies on this computer, which can be applied to all users of the computer, but are not applicable to administrators. With this exception, administrators can retain unlimited access to the computer and control, and can also limit users who can log in to the computer.
Applying local policies to all users other than administrators to implement local policies to all users other than administrators, perform the following steps: Log in to your computer as an administrator. Open local security policies. To achieve this, do one of the following XX:
Click Start, and then click Run, type gpedit.msc, and press Enter.
- or - click Start, click Run, type MMC, press Enter, add Group Policy Object Editor, and configure it for local security policies. If the delete run command is one of the strategies you need, Microsoft recommends that you edit the policy via "Microsoft Management Console" (MMC) and save the results as an icon. This way, you don't need to use the run command to reopen the policy. Expand the user configuration object and expand the management template object. Enable any policies you need (for example, "hidden 'online neighbor'" on your desktop "or hide the Internet Explorer icon on your desktop").
Note: Be sure to select the correct policy, otherwise you may limit the ability of the administrator to log in to your computer (and the steps required to configure your computer). Microsoft recommends that you record any changes made (this information is also used in step 10). Turn off the "GPEDIT.MSC Group Policy" management unit, or if you use MMC, save the console as an icon so you can access it later, then log out of your computer. Log in to your computer as an administrator. You can verify the previous policy changes in this login session, because the local policy is applied to all users, including administrators. Log in from your computer, then log in to your computer as all other users of this computer (you want them to apply these policies). These strategies are implemented for all of these users and administrators
of.
Note: These policies cannot be implemented for any user account that is not logged in to the computer in this step. Log in to your computer as an administrator. Click Start, point to Control Panel, and then click Folder Selection. Click View tab, click Show Hide Files or Folders, and then click OK to view the Group Policy Hide folder. Or, open the Windows Explorer, click Tool, and then click Folder option to view these settings. Copy the registry.pol file in the% SystemRoot% / System32 / GroupPolicy / User folder to the backup location (for example, copy to another hard drive, floppy disk or folder). Use the "GPEDIT.MSC Group Policy" management unit or your MMC icon to open the local policy again, then enable the actual features disabled in the original policy created by the computer.
Note: When you perform this XX, the Policy Editor creates a new registry.pol file. Turn off the policy editor and copy the backup registry.pol file created in step 10 to the% SystemRoot% / System32 / GroupPolicy / User folder.
When the system prompts replace the existing file, click Yes. Log out from your computer and log in as an administrator.
Since you are logged in to your computer as an administrator, you can verify that there is no change in the original changes. Log in from your computer and log in as other users.
Since you are logged in as a user (not administrator), you can verify that the original changes are implemented. Log in to the computer as an administrator to confirm that the local policy does not affect the computer as a local administrator.
Restore the original local policy To undo the process described in this article section describes the process described in all users other than the administrator ", perform the following steps: Log in to your computer as an administrator. Click Start, point to Control Panel, and then click Folder Selection. Click View tab, click Show Hide Files and Folders, and then click OK to view the Group Policy Hide folder. Or, open "Windows Explorer", click Tool, and then click the folder option. Move, rename or delete the registry.pol file from the% SystemRoot% / System32 / GroupPolicy / User folder.
After you log out or restart your computer from your computer, the Windows File Protection system creates another default registry.pol file. Open the local policy. To achieve this, click Start, click Run, and type GPEDIT.MSC. Or, click Start, click Run, type MMC, and then load local security policies. Then, all items set to disable or enable are set to unconfigured to undo any policy changes to the Windows Server2003 registry registry specified by the registry.pol file. Log out from the computer as an administrator and then log in to the computer as an administrator. Log in from the computer, then log in to the computer as all users of the local computer, which can also be revoked for their account to change the 19th, how to reset the Internet Protocol (TCP / IP) "in Windows Server 2003
Summary If you display this connection in the Local Connection property Using the Internet Protocol (TCP / IP) item in the list of items, you will find that the uninstall button is not available (disabled). This is because the Transmission Control Protocol / Internet Protocol (TCP / IP) stack is the core component of Microsoft Windows Server 2003 and cannot be deleted.
In some cases, you may need to reinstall the TCP / IP to restore the TCP / IP stack to the original state. You can reset the TCP / IP stack using the NetShell utility to restore the status of the initially installed XX as a system. MORE INFORMATION NETSHELL Utilities (NETSH) is a command line script writing tool that you can use to configure and monitor Windows Server 2003 networking. This tool provides an interactive network housing interface.
You can use the RESET command in the Internet Protocol (IP) context of this utility to override the following with TCP / IP-related registry key: system / currentcontrolset / services / tcpip / parameters / system / currentcontrolset / services / DHCP / parameters / The results of running this command are the same as deleting and reinstalling the TCP / IP protocol. Command Syntax Netsh INT IP RESET [LOG_FILE_NAME]
To reset the TCP / IP stack using the netsh command, you must specify the name of the log file of the log file. If any of the commands described in the "command example" section of this article, the TCP / IP stack in the current computer will be reset, and the XX active activity will be recorded to the resetlog.txt file specified in the command line. In the first example, the log file is created in the current folder; in the second example, the full path to the resetLog.txt log file is specified.
Note: If the name of the file is the same as the name of the existing log file in the destination folder, the information of the new log file is attached to the end of the existing file. Command Example The following example illustrates how to reset the TCP / IP protocol stack using the netsh command. Example 1 Click Start, and then click Run. Type CMD in the Open box, then click OK. Type the following command after the command prompt, then press ENTER: Netsh IP ResetLog.txt
Note: In the above command, "int" is an abbreviated form of the interface command. Type EXIT, then press ENTER. Example 2 Click Start, and then click Run. Type CMD in the Open box, then click OK. Type the following command after the command prompt, then press Enter: Netsh IP Reset C: /Restlog.txt
Type EXIT, then press ENTER. To see the help of the command, type space and type it? Other help on the available commands in the NetSH command sub context will be displayed. For example, to view the Netsh command described in the previous section, type the following command after the command prompt: Type Netsh?, Then press Enter. Type Netsh Int? And press Enter. Type NetSh INT IP?, Then press Enter. Type NetSh INT IP RESET? And press ENTER. Netsh IP Reset log file examples The following article is an example of a log file, which is generated by Netsh after running the IP reset command. The actual log file will vary depending on the computer that issues a command. Typically, if there is no original configuration of the TCP / IP registry key, no XX work is recorded in the file. RESET System / CurrentControlSet / Services / DHCP / Parameters / Options / 15 / RegLocationOLD REG_MULTI_SZ =
System / currentcontrolset / services / tcpip / parameters / interfaces /? / Dhcpdomain
System / CurrentControlset / Services / Tcpip / Parameters / DHCPDOMAIN
added SYSTEM / CurrentControlSet / Services / Netbt / Parameters / Interfaces / Tcpip_ {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / NetbiosOptions added SYSTEM / CurrentControlSet / Services / Netbt / Parameters / Interfaces / Tcpip_ {BAA9D128-54BB-43F6-8922- 313D537BE03E} / NetbiosOptions reset SYSTEM / CurrentControlSet / Services / Netbt / Parameters / Interfaces / Tcpip_ {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / NameServerList old REG_MULTI_SZ = 10.1.1.2
deleted SYSTEM / CurrentControlSet / Services / Netbt / Parameters / EnableLmhosts added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / AddressType added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / DefaultGatewayMetric added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / DisableDynamicUpdate deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / DontAddDefaultGateway reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / EnableDhcp old REG_DWORD = 0added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / NameServer added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / RawIpAllowedProtocols added SYSTEM / CurrentControlset / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / TcpAllowedPorts added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {2DDD011E-B1B6-4886-87AC-B4E72693D10C} / UdpAllowedPorts added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / DisableDynamicUpdate reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / EnableDhcp old REG_DWORD = 0
RESET System / CurrentControlset / Services / TCPIP / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / ipaddress old reg_multi_sz = 12.12.12.12
Deleded System / CurrentControlSet / Services / TCPIP / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E}
/ IpAutoconfigurationAddress deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / IpAutoconfigurationMask deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991- 04DA31024C4E} / IpAutoconfigurationSeed reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / RawIpAllowedProtocols old REG_MULTI_SZ = 0reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {5B3675C3-6EB9 -4936-b991-04da31024c4e} / subnetmask ild reg_multi_sz = 255.255.255.0
Reset system / currentcontrolset / services / tcpip / parameters / interfaces / {5b3675c3-6eb9-4936-b991-04da31024c4e} / tcpallowedports Old reg_multi_sz = 0
RESET SYSTEM / CURRENTCONTROLSET / SERVICES / TCPIP / Parameters / Interfaces / {5B3675C3-6EB9-4936-B991-04DA31024C4E} / udpallowedports Old Reg_Multi_SZ = 0
added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / AddressType added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / DefaultGatewayMetric added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / DisableDynamicUpdate deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922- 313D537BE03E} / DontAddDefaultGateway reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / EnableDhcp old REG_DWORD = 0
added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / NameServer added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / RawIpAllowedProtocols added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922-313D537BE03E} / TcpAllowedPorts added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BAA9D128-54BB-43F6-8922- 313D537BE03E} / UdpAllowedPorts reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / DefaultGateway old REG_MULTI_SZ = 10.1.1.2reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / { BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / defaultgatewayMetric Old reg_multi_sz = 0
added SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / DisableDynamicUpdate reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / Enabledhcp old reg_dword = 0
RESET System / CurrentControlSet / Services / TCPIP / parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / ipaddress old reg_multi_sz = 10.1.1.1
Deleded System / CurrentControlSet / Services / TCPIP / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A}
/ IpAutoconfigurationAddress deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / IpAutoconfigurationMask deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE- 3D246F90A81A} / IpAutoconfigurationSeed reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / NameServer old REG_SZ = 10.1.1.2,10.1.1.3reset SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / RawipAllowedProtocols Old Reg_Multi_SZ = 0
RESET SYSTEM / CURRENTCONTROLSET / SERVICES / TCPIP / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / SubnetMask Old REG_MULTI_SZ = 255.255.255.0
RESET System / CurrentControlset / Services / TCPIP / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / tcpallowedports Old Reg_Multi_SZ = 0
RESET System / CurrentControlset / Services / TCPIP / Parameters / Interfaces / {BD2859BA-B26A-4E2B-A3FE-3D246F90A81A} / udpallowedports Old Reg_Multi_SZ = 0
deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / DontAddDefaultGatewayDefau lt deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / EnableIcmpRedirect deleted SYSTEM / CurrentControlSet / Services / Tcpip / Parameters / EnableSecurityFiltersdeleted SYSTEM / CurrentControlSet / Services / Tcpip
/ Parameters / searchlist deleted system / currentcontrolset / services / tcpip / parameters / usedomainNameDevolution
Twenty, how to add custom user settings in Windows Server 2003 when running Sysprep
SUMMARY This article describes how to add custom user settings when running the Sysprep.exe.
When running sysprep.exe, some user settings cannot be captured in the .reg file and apply when the installer is complete, and cannot write scripts for these settings and apply them to all new users. To resolve this issue, copy the custom user settings to the "Default User" profile before running Sysprep.exe.
To perform the steps described in this section, your system must meet the following conditions: Windows Server 2003 is fully installed to your computer and can run normally. The computer is not part of a certain domain. All user programs have been pre-installed and can be run normally. Remarks: If the client's desktop settings are stored in the user's configuration file, you can use the procedures described in this section to define any of these settings. For example, you can use this procedure to configure the Auto Hidden Tasklet option and "Show Small Icon" options in the 'Start' menu. You cannot use this procedure to customize the settings stored outside the user profile. Use the following procedure to deploy custom power option settings for all new users.
Creating a test user using administrator privileges Log in to your computer as local administrator. Click Start, right-click My Computer, and then click Manage.
Note: If Active Directory is installed, the Local User and Group tool in the Computer Management console is disabled. If you want to perform this procedure from a domain controller computer with Active Directory, you must create a new user account through the "Active Directory User and Computer". Click Local Users and Groups, right-click the user, and then click New User. Type Testuser in the "User Name" box, type your password, click the "User Log in" check box, clear it, and then click Create. Turn off the New User dialog box. In the Local User and Group, click Group, double-click Administrator, and then click Add. Type Testuser and click OK. Click OK to close the Administrator Properties dialog. Turn off the Computer Management console.
To test the user to create a custom settings to log in to the computer as Testuser. Click Start, point to Control Panel, and then click Power Options. Set the settings for monitoring, hard drives, standby, and sleep, etc. to be used as the default settings of all users. Note: You can make additional customization as needed. These specific settings are just an example
Copy the profile folder of the test user to the default user profile file folder pin TestUser account and log in again as an administrator. Right-click Start, and then click Resource Manager to launch "Windows Explorer". On the Tools menu, click the Folder option, and then click the View tab. In the Advanced Settings box, click the Show Hide Files and Folders check boxes, select it. Exit "Windows Explorer". Right-click on my computer and click Properties. Click the Advanced tab, and then in the User Profile section, click Settings. Click the Testuser account and click Copy to. Type C: / Documents and Settings / Default User in the Path box, or click Browse to find the "default user folder". Click Change in the Allowed Use section. Type EVERYONE and click OK. Click OK in Copy to the dialog, then click Yes, confirm this XX. Click OK to close the User Profile dialog. Right-click on my computer and click Manage. Click Local User and Group, click the user, click the Testuser account, and then delete it. Turn off the Computer Management console. Be prepared to start the sysprep process after you are ready.
