How to wire your own ethernet cables and connectors.

What You Need:

Required:

• CAT 5 Cable – bulk Category 5, 5e or 6 cable
• RJ45 Ends
• Crimper for RJ45
• Wire Cutters – to cut and strip the cable if necessary

Recommend:

• Wire Stripper
• Cable Tester

About the Cable:

You can find bulk supplies of the cable at many computer stores or most electrical or home centers. You want UTP (Unshielded Twisted Pair) Category 5 cable for basic 10/100 functionality. You need CAT 5e for gigabit (1000BaseT) operation and CAT 6 gives you a measure of future proofing. Bulk cable comes in many types, there are 2 basic categories, solid and braided cable. Braided cable tends to work better in “patch” applications for desktop use. It is more flexible and resiliant than solid cable and easier to work with, but really meant for shorter lengths. Solid cable is meant for longer runs in a fixed position. Plenum rated cable should/must be used whenever the cable travels through an air circulation space. For example, above a false celing or below a raised floor.You’re likely going to want braided type cable but it may be difficult or impossible to tell from the box. Here is what the internals of the cable look like: <!–[if !vml]–><!–[endif]–>
Internal Cable Structure and Color Coding Inside the cable, there are 8 color coded wires. These wires are twisted into 4 pairs of wires, each pair has a common color theme. One wire in the pair being a solid or primarily solid colored wire and the other being a primarily white wire with a colored stripe (Sometimes cable doesn’t have any color on the striped cable, the only way to tell is to check which other wire it is twisted around). Examples of the naming schemes used are: Orange (alternatively Orange/White) for the solid colored wire and White/Orange for the striped cable. The twists are extremely important. They are there to counteract noise and interference. It is important to wire according to a standard to get proper performance from the cable. The TIA/EIA-568-A specifies two wiring standards for a 8-position modular connector such as RJ45. The two wiring standards, T568A and T568B vary only in the arrangement of the colored pairs. Tom writes to say “…sources suggest using T568A cabling since T568B is the AT&T standard, but the US Government specifies T568A since it matches USOC cabling for pairs 1 & 2, which allows it to work for 1/2 line phones…”. Your choice might be determined by the need to match existing wiring, jacks or personal preference, but you should maintain consistancy. I’ve shown both below for straight through cabling and just T568B for cross over cabling.

About the RJ45 Ends:

The RJ45 end is a 8-position modular connector that looks like a large phone plug. There are a couple variations available. The primary variation you need to pay attention to is whether the connector is intended for braided or solid wire. For braided/stranded wires, the connector has contacts that actually pierce the wire. For solid wires, the connector has fingers which pierce the insulation and make contact with the wire by grasping it from both sides. The connector is the weak point in an ethernet cable, choosing the wrong one will often cause grief later. If you just walk into a computer store, it’s nearly impossible to tell what type of connector it is. Here is a diagram and pinout:
RJ45 Jack and Plug Pinout

Ethernet Cable Pinouts:

There are two basic cables. A straight through cable, which is used to connect to a hub or switch, and a cross over cable used to operate in a peer-to-peer fashion without a hub/switch. Some interfaces can cross and un-cross a cable automatically as needed, really quite nice.

Standard, Straight-Through Wiring (both ends are the same):

RJ45 Pin #	Wire Color (T568A)	Wire Diagram (T568A)	10Base-T Signal 100Base-TX Signal	1000Base-T Signal
1	White/Green	<!–[if !vml]–><!–[endif]–>	Transmit+	BI_DA+
2	Green	<!–[if !vml]–><!–[endif]–>	Transmit-	BI_DA-
3	White/Orange	<!–[if !vml]–><!–[endif]–>	Receive+	BI_DB+
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC+
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC-
6	Orange	<!–[if !vml]–><!–[endif]–>	Receive-	BI_DB-
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD+
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD-

Straight-Through Cable Pinout for T568A

RJ45 Pin #	Wire Color (T568B)	Wire Diagram (T568B)	10Base-T Signal 100Base-TX Signal	1000Base-T Signal
1	White/Orange	<!–[if !vml]–><!–[endif]–>	Transmit+	BI_DA+
2	Orange	<!–[if !vml]–><!–[endif]–>	Transmit-	BI_DA-
3	White/Green	<!–[if !vml]–><!–[endif]–>	Receive+	BI_DB+
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC+
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	BI_DC-
6	Green	<!–[if !vml]–><!–[endif]–>	Receive-	BI_DB-
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD+
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	BI_DD-

Straight-Through Cable Pinout for T568B

Cross Over Cable (T568B):

RJ45 Pin # (END 1)	Wire Color	Diagram End #1	RJ45 Pin # (END 2)	Wire Color	Diagram End #2
1	White/Orange	<!–[if !vml]–><!–[endif]–>	1	White/Green	<!–[if !vml]–><!–[endif]–>
2	Orange	<!–[if !vml]–><!–[endif]–>	2	Green	<!–[if !vml]–><!–[endif]–>
3	White/Green	<!–[if !vml]–><!–[endif]–>	3	White/Orange	<!–[if !vml]–><!–[endif]–>
4	Blue	<!–[if !vml]–><!–[endif]–>	4	White/Brown	<!–[if !vml]–><!–[endif]–>
5	White/Blue	<!–[if !vml]–><!–[endif]–>	5	Brown	<!–[if !vml]–><!–[endif]–>
6	Green	<!–[if !vml]–><!–[endif]–>	6	Orange	<!–[if !vml]–><!–[endif]–>
7	White/Brown	<!–[if !vml]–><!–[endif]–>	7	Blue	<!–[if !vml]–><!–[endif]–>
8	Brown	<!–[if !vml]–><!–[endif]–>	8	White/Blue	<!–[if !vml]–><!–[endif]–>

Cross Over Cable Pinouts +Note: The cross over cable layout is suitable for 1000Base-T operation, all 4 pairs are crossed.

How to wire Ethernet Cables:

1. Strip off about 2 inches of the cable sheath.
2. Untwist the pairs – don’t untwist them beyond what you have exposed, the more untwisted cable you have the worse the problems you can run into.
3. Align the colored wires according to the diagrams above.
4. Trim all the wires to the same length, about 1/2″ to 3/4″ left exposed from the sheath.
5. Insert the wires into the RJ45 end – make sure each wire is fully inserted to the front of the RJ45 end and in the correct order. The sheath of the cable should extend into the RJ45 end by about 1/2″ and will be held in place by the crimp.
6. Crimp the RJ45 end with the crimper tool
7. Verify the wires ended up the right order and that the wires extend to the front of the RJ45 end and make good contact with the metal contacts in the RJ45 end.
8. Cut the cable to length – make sure it is more than long enough for your needs. Remember, an end to end connection should not extend more than 100m (~328ft). Try to keep cables short, the longer the cable becomes the more it may affect performance, usually noticable as a gradual decrease in speed and increase in latency.
9. Repeat the above steps for the second RJ45 end.
10. If a cable tester is available, use it to verify the proper connectivity of the cable.

That should be it, if your cable doesn’t turn out, look closely at each end and see if you can find the problem. Usually a wire ended up in the wrong place or more commonly, one of the wires didn’t extend to the front of the RJ45 connector and is making no, or poor contact. If you see a mistake or problem, cut the end off and start again.

---

Notes:

Power over Ethernet (PoE):

Power over Ethernet has been implemented in many variations before IEEE standardized 802.3af. 802.3af specifies the ability to supply an endpoint with 48V DC at up 350mA or 16.8W. The endpoint must be capable of receiving power on either the data pairs [Mode A] (often called phantom power) or the unused pairs [Mode B] in 100Base-TX. PoE can be used with any ethernet configuration, including 10Base-T, 100Base-TX and 1000Base-T. Power is only supplied when a valid PoE endpoint is detected by using a low voltage probe to look for the PoE signature on the endpoint. PoE power is typically supplied in one of two ways, either the host ethernet switch provides the power, or a “midspan” device is plugged in between the switch and endpoints which supplies the power. No special cabling is required.

RJ45 Pin #	Wire Color (T568A)	Wire Diagram (T568A)	10Base-T Signal 100Base-TX Signal	PoE
1	White/Green	<!–[if !vml]–><!–[endif]–>	Transmit+	Mode A +
2	Green	<!–[if !vml]–><!–[endif]–>	Transmit-	Mode A +
3	White/Orange	<!–[if !vml]–><!–[endif]–>	Receive+	Mode A -
4	Blue	<!–[if !vml]–><!–[endif]–>	Unused	Mode B +
5	White/Blue	<!–[if !vml]–><!–[endif]–>	Unused	Mode B +
6	Orange	<!–[if !vml]–><!–[endif]–>	Receive-	Mode A -
7	White/Brown	<!–[if !vml]–><!–[endif]–>	Unused	Mode B -
8	Brown	<!–[if !vml]–><!–[endif]–>	Unused	Mode B -

Power over Ethernet Power Delivery

Protocol Details:

	Frequency (MHz)	Symbol Encoding	Signal Rate (Mbaud)	Symbol Rate	Data Encoding	Data Bits per Symbol	Pairs per Channel	Pairs Used	Minimum Cable Category
10BaseT	10	Manchester	10	10	None	1	1	2	3
100BaseT4	12.5	Multi-level, 2T/Hz	25	25	8B6T	8/6	3	4	3
100BaseTX	31.25	MLT-3	125	125	4B5B	4/5	1	2	5
100BaseT2	12.5	PAM5×5 (2D-PAM5)	25	12.5	None	4 (2×2)	2	2	3
1000BaseT	31.25	4D-PAM5	125	31.25	None	8 (4×2)	4	4	5*

*Designed to work on MOST category 5 cable, category 5e specifications ensure 1000Base-T operation

Cable Category Details:

Cable Category	Rated Frequency Bandwidth (MHz)	Common Uses
1	None	Common Use
2	1	Telephone Wiring
3	16	Telephone Wiring, 10Base-T
4	20	Token-Ring, 10Base-T
5	100	100Base-TX, 10Base-T
5e	100	1000Base-T, 100Base-TX
6	250	1000Base-T, 100Base-TX
6a*	500	10GBase-T
7	600

Increasing category levels are backward compatible.
Manufacturers will often test and certify their cable well beyond the standards.
*10GBase-T should work on Cat6, but to get the full 100m range, Cat 6a is required.

Related Reading Material

• Get IEEE 802 – Ethernet Standards
• Charles Spurgeon’s Ethernet Website
• Network Connection Speeds Reference
• Fiber Optic Connector Reference
• Ethernet: The Definitive Guide <!–[if !vml]–><!–[endif]–>
• Interconnections: Bridges, Routers, Switches, and Internetworking Protocols <!–[if !vml]–><!–[endif]–>
• The Switch Book: The Complete Guide to LAN Switching Technology <!–[if !vml]–><!–[endif]–>
• TCP/IP Illustrated 3 Volume Set:
  
  • The Protocols (TCP/IP Illustrated, Volume 1)
  • The Implementation (TCP/IP Illustrated, Volume 2)
  • TCP for Transactions, HTTP, NNTP, and the UNIX(R) Domain Protocols (TCP/IP Illustrated, Volume 3)
• UNIX Network Programming
  
  • Unix Network Programming, Vol. 1: The Sockets Networking API, Third Edition
  • UNIX Network Programming, Volume 2: Interprocess Communications (2nd Edition)

How to troubleshoot the following message in Windows XP: “A network cable is unplugged“

MORE INFORMATION

loadTOCNode(1, \’moreinformation\’); This message generally appears after you lose a network signal. You may lose a network signal for several reasons. Use the following options to determine the cause of this issue:

•	The network cable is loose or unplugged. To resolve this issue, verify that the network cable is plugged in securely to the correct locations on the computer and on the network device. Note Some computers may have multiple network adapters. If you are not sure where to connect the network cable on the computer, see the computer documentation, or contact the computer manufacturer.
•	The network cable is defective or damaged. Examine the cable for breaks, for tears in the outer covering, or for damaged connectors. Test the network connection by using a network cable that works. If another network cable resolves the issue, replace the defective network cable.
•	The network cable is plugged in securely at both ends, but the network device may not be turned on. Verify that all network hardware is plugged in to a power supply if it is required and is turned on. To resolve this issue, you may have to reset the network device. Some network devices have a reset button. Other network devices require that you turn off the power, wait for several minutes, and then turn the power back on. For more information about how to reset the network device, see its documentation.
•	The network connection may be universal serial bus (USB)-based and may be plugged into a USB hub. Issues can occur on some USB hubs because of power constraints. Non-powered and congested hubs may not supply sufficient power. To resolve this issue, connect the network device directly into the USB port on the computer.
•	The network cable may be the wrong type of cable. For example, a crossover cable does not function correctly as a regular network cable. To resolve this issue, replace the network cable with a network cable that works.
•	The network cable is not connected to the correct port on the network device. To resolve this issue, verify that the network cable is connected to the correct port on the network device. You may lose the network signal if you connect the cable to the uplink port on a hub, on a switch, or on a router instead of on a regular port. If you are not sure where to connect the network cable, see the hardware documentation.
•	Some hubs, switches, and routers disable the port next to the uplink port when the uplink port is being used. To resolve this issue, verify that the port next to the uplink port is empty. If you cannot locate the uplink port, see the hardware documentation.
•	If the network adapter supports a power management option, the following check box may be selected: Allow the computer to turn off this device to save power If the network adapter supports this option, it is available on the Power Management tab of the network adapter properties dialog box. To resolve this issue, disable this option on the Power Management tab. For more information about how to disable this power management option, click the following article number to view the article in the Microsoft Knowledge Base: 811595 (http://support.microsoft.com/kb/811595/) “A network cable has been unplugged” message appears at seemingly random intervals
•	The value for the Media Type property on the network adapter may be set to Auto Select. This property is located on the Advanced tab of the network adapter properties dialog box. To resolve this issue, change the value of the Media Type property to a specific bandwidth. For example, set the value to 10Mbps/Full Duplex, to 100Mbps/Full Duplex, or to an optimum value. Note The steps to change this property vary depending on the manufacturer of the network adapter. In most scenarios, you can follow these steps to change the value of the Media Type property: 1. Click Start, click Run, type ncpa.cpl, and then click OK. 2. Right-click Local Area Connection, and then click Properties. 3. On the General tab, click Configure. 4. In the resulting dialog box, click the Advanced tab. 5. In the Property list, click Media Type or Link Speed & Duplex or something similar. Note If these properties do not appear, look for a property that has the values Duplex and Half-Duplex. 6. Click a specific bandwidth in the Value list, and then click OK. 7. Close the Network Connections dialog box. 8. Test the network connection. 9. If these steps do not resolve the issue, repeat steps 1 through 5, and then click a different value in step 6 until you have tested all values.
•	If you are using a PCI network adapter, the issue may relate to resources. To resolve this issue, physically move the network adapter to an adjacent PCI slot, and then restart the computer. After you restart the computer, the New Hardware Wizard detects and installs the network adapter. If you do not know how to install the network adapter, contact the computer manufacturer, or see the network adapter documentation.

REFERENCES

loadTOCNode(1, \’references\’); For more information about other related network issues, click the following article numbers to view the articles in the Microsoft Knowledge Base:

814152 (http://support.microsoft.com/kb/814152/) “A network cable is unplugged” message when you try to use a network cable to connect to your MN-100 or MN-500

240395 (http://support.microsoft.com/kb/240395/) Description of the possible “Local Area Connection” icon states

822585 (http://support.microsoft.com/kb/822585/) Internet Mail Wizard displays the IP address 0.0.0.0 when a network adapter is disabled

---

APPLIES TO

•	Microsoft Windows XP Professional
•	Microsoft Windows XP Home Edition

 

How To Set Up an FTP Server in Windows Server 2003

Install Internet Information Services and the FTP Service

 Because FTP depends on Microsoft Internet Information Services (IIS), IIS and the FTP Service must be installed on the computer. To install IIS and the FTP Service, follow these steps.

NOTE: In Windows Server 2003, the FTP Service is not installed by default when you install IIS. If you already installed IIS on the computer, you must use the Add or Remove Programs tool in Control Panel to install the FTP Service.

1.	Click Start, point to Control Panel, and then click Add or Remove Programs.
2.	Click Add/Remove Windows Components.
3.	In the Components list, click Application Server, click Internet Information Services (IIS) (but do not select or clear the check box), and then click Details.
4.	Click to select the following check boxes (if they are not already selected): Common Files File Transfer Protocol (FTP) Service Internet Information Services Manager
5.	Click to select the check boxes next to any other IIS-related service or subcomponent that you want to install, and then click OK.
6.	Click Next.
7.	When you are prompted, insert the Windows Server 2003 CD-ROM into the computer’s CD-ROM or DVD-ROM drive or provide a path to the location of the files, and then click OK.
8.	Click Finish.

IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.

Configure The FTP Service

loadTOCNode(2, \’summary\’); To configure the FTP Service to allow only anonymous connections, follow these steps:

1.	Start Internet Information Services Manager or open the IIS snap-in.
2.	Expand Server_name, where Server_name is the name of the server.
3.	Expand FTP Sites
4.	Right-click Default FTP Site, and then click Properties.
5.	Click the Security Accounts tab.
6.	Click to select the Allow Anonymous Connections check box (if it is not already selected), and then click to select the Allow only anonymous connections check box. When you click to select the Allow only anonymous connections check box, you configure the FTP Service to allow only anonymous connections. Users cannot log on by using user names and passwords.
7.	Click the Home Directory tab.
8.	Click to select the Read and Log visits check boxes (if they are not already selected), and then click to clear the Write check box (if it is not already cleared).
9.	Click OK.
10.	Quit Internet Information Services Manager or close the IIS snap-in.

The FTP server is now configured to accept incoming FTP requests. Copy or move the files that you want to make available to the FTP publishing folder for access. The default folder is drive:\Inetpub\Ftproot, where drive is the drive on which IIS is installed.

How To Set Up an FTP Server in Windows Server 2003

Install Internet Information Services and the FTP Service

Because FTP depends on Microsoft Internet Information Services (IIS), IIS and the FTP Service must be installed on the computer. To install IIS and the FTP Service, follow these steps.

NOTE: In Windows Server 2003, the FTP Service is not installed by default when you install IIS. If you already installed IIS on the computer, you must use the Add or Remove Programs tool in Control Panel to install the FTP Service.

1.	Click Start, point to Control Panel, and then click Add or Remove Programs.
2.	Click Add/Remove Windows Components.
3.	In the Components list, click Application Server, click Internet Information Services (IIS) (but do not select or clear the check box), and then click Details.
4.	Click to select the following check boxes (if they are not already selected): Common Files File Transfer Protocol (FTP) Service Internet Information Services Manager
5.	Click to select the check boxes next to any other IIS-related service or subcomponent that you want to install, and then click OK.
6.	Click Next.
7.	When you are prompted, insert the Windows Server 2003 CD-ROM into the computer’s CD-ROM or DVD-ROM drive or provide a path to the location of the files, and then click OK.
8.	Click Finish.

IIS and the FTP service are now installed. You must configure the FTP Service before you can use it.

Configure The FTP Service

To configure the FTP Service to allow only anonymous connections, follow these steps:

1.	Start Internet Information Services Manager or open the IIS snap-in.
2.	Expand Server_name, where Server_name is the name of the server.
3.	Expand FTP Sites
4.	Right-click Default FTP Site, and then click Properties.
5.	Click the Security Accounts tab.
6.	Click to select the Allow Anonymous Connections check box (if it is not already selected), and then click to select the Allow only anonymous connections check box. When you click to select the Allow only anonymous connections check box, you configure the FTP Service to allow only anonymous connections. Users cannot log on by using user names and passwords.
7.	Click the Home Directory tab.
8.	Click to select the Read and Log visits check boxes (if they are not already selected), and then click to clear the Write check box (if it is not already cleared).
9.	Click OK.
10.	Quit Internet Information Services Manager or close the IIS snap-in.

The FTP server is now configured to accept incoming FTP requests. Copy or move the files that you want to make available to the FTP publishing folder for access. The default folder is drive:\Inetpub\Ftproot, where drive is the drive on which IIS is installed.

---

APPLIES TO

•	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
•	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
•	Microsoft Windows Server 2003, Enterprise x64 Edition
•	Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
•	Microsoft Windows Server 2003, 64-Bit Datacenter Edition
•	Microsoft Windows Server 2003, Web Edition
•	Microsoft Internet Information Services 6.0

 

How do I install the DHCP Server Service?

 

1. Start the Network Control Applet by clicking on Network from Control Panel (Start – Settings – Control Panel) or right click on Network Neighborhood and select Properties
2. Click on the Services tab and click Add
3. Select “Microsoft DHCP <!–[if !vml]–><!–[endif]–> Server” and click OK
4. You will be prompted to insert the NT Server installation CD or say where the i386 directory is
5. A warning that all local adapters must use a static IP address and click OK
6. Click Close and select Yes to reboot

Under Windows 2000 to install perform the following:

1. Start the Add/Remove Programs Control Panel applet (Start – Settings – Control Panel – Add/Remove Programs)
2. In the left hand pane click ‘Add/Remove Windows Components”
3. Click the ‘Components’ button to start the Components wizard
4. Click Next
5. Select ‘Networking Services’ and click Details
6. Check the ‘Dynamic Host Configuration Protocol (DHCP)’ option and click OK
7. Click Next and the relevant files and services will be configured.
8. Click Finish when all operations have completed
9. Click Close to the Add/Remove Programs dialog

How to use Group Policy to remotely install software in Windows Server 2003

SUMMARY

This step-by-step article describes how to use Group Policy to automatically distribute programs to client computers or users. You can use Group Policy to distribute computer programs by using the following methods:

•

Assigning Software You can assign a program distribution to users or computers. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is finalized. If you assign the program to a computer, it is installed when the computer starts, and it is available to all users who log on to the computer. When a user first runs the program, the installation is finalized.

•

Publishing Software You can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add or Remove Programs dialog box, and it can be installed from there.

Note Windows Server 2003 Group Policy automated-program installation requires client computers that are running Microsoft Windows 2000 or later.

<!–[if !supportLineBreakNewLine]–>
<!–[endif]–>

Create a Distribution Point

To publish or assign a computer program, you must create a distribution point on the publishing server:

1.	Log on to the server computer as an administrator.
2.	Create a shared network folder where you will put the Microsoft Windows Installer package (.msi file) that you want to distribute.
3.	Set permissions on the share to allow access to the distribution package.
4.	Copy or install the package to the distribution point. For example, to distribute Microsoft Office XP, run the administrative installation (setup.exe /a) to copy the files to the distribution point.

Create a Group Policy Object

To create a Group Policy object (GPO) to use to distribute the software package:

1.	Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	In the console tree, right-click your domain, and then click Properties.
3.	Click the Group Policy tab, and then click New.
4.	Type a name for this new policy (for example, Office XP distribution), and then press ENTER.
5.	Click Properties, and then click the Security tab.
6.	Click to clear the Apply Group Policy check box for the security groups that you want to prevent from having this policy applied.
7.	Click to select the Apply Group Policy check box for the groups that you want this policy to apply to.
8.	When you are finished, click OK.

Assign a Package

To assign a program to computers that are running Windows Server 2003, Windows 2000, or Microsoft Windows XP Professional, or to users who are logging on to one of these workstations:

1.	Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	In the console tree, right-click your domain, and then click Properties.
3.	Click the Group Policy tab, select the group policy object that you want, and then click Edit.
4.	Under Computer Configuration, expand Software Settings.
5.	Right-click Software installation, point to New, and then click Package.
6.	In the Open dialog box, type the full Universal Naming Convention (UNC) path of the shared installer package that you want. For example, \\file server\share\file name.msi. Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
7.	Click Open.
8.	Click Assigned, and then click OK. The package is listed in the right pane of the Group Policy window.
9.	Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
10.	When the client computer starts, the managed software package is automatically installed.

Publish a Package

To publish a package to computer users and make it available for installation from the Add or Remove Programs tool in Control Panel:

1.	Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	In the console tree, right-click your domain, and then click Properties.
3.	Click the Group Policy tab, click the group policy object that you want, and then click Edit.
4.	Under User Configuration, expand Software Settings.
5.	Right-click Software installation, point to New, and then click Package.
6.	In the Open dialog box, type the full UNC path of the shared installer package that you want. For example, \\file server\share\file name.msi. Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
7.	Click Open.
8.	Click Publish, and then click OK.
9.	The package is listed in the right pane of the Group Policy window.
10.	Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
11.	Test the package: Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. a. Log on to a workstation that is running Windows 2000 Professional or Windows XP Professional by using an account that you published the package to. b. In Windows XP, click Start, and then click Control Panel. c. Double-click Add or Remove Programs, and then click Add New Programs. d. In the Add programs from your network list, click the program that you published, and then click Add. The program is installed. e. Click OK, and then click Close.

Redeploy a Package

In some cases you may want to redeploy a software package. For example, if you upgrade or modify the package. To redeploy a package:

1.	Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	In the console tree, right-click your domain, and then click Properties.
3.	Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
4.	Expand the Software Settings container that contains the software installation item that you used to deploy the package.
5.	Click the software installation container that contains the package.
6.	In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Redeploy application. You will receive the following message: Redeploying this application will reinstall the application everywhere it is already installed. Do you want to continue?
7.	Click Yes.
8.	Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.

Remove a Package

To remove a published or assigned package:

1.	Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	In the console tree, right-click your domain, and then click Properties.
3.	Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
4.	Expand the Software Settings container that contains the software installation item that you used to deploy the package.
5.	Click the software installation container that contains the package.
6.	In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Remove.
7.	Do one of the following: • Click Immediately uninstall the software from users and computers, and then click OK. • Click Allow users to continue to use the software but prevent new installations, and then click OK.
8.	Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.

Troubleshoot

loadTOCNode(2, \’summary\’); Published Packages Are Displayed on a Client Computer After You Use a Group Policy to Remove Them

loadTOCNode(3, \’summary\’); This situation can occur when a user has installed the program but has not used it. When the user first starts the published program, the installation is finalized. Group Policy then removes the program.

REFERENCESFor more information about how to use a Group Policy to deploy software, click the following article numbers to view the articles in the Microsoft Knowledge Base: 304953 (http://support.microsoft.com/kb/304953/) How to deploy Office XP over a network 302430 (http://support.microsoft.com/kb/302430/) How to assign software to a specific group by using Group Policy <!–[if !vml]–><!–[endif]–>Back to the top

---

APPLIES TO

•	Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
•	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
•	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
•	Microsoft Windows XP 64-Bit Edition Version 2003

Back to the top

Keywords:

kbhowtomaster kbmgmtservices KB816102

Step-by-Step Guide to a Common Infrastructure for Windows Server 2003 Deployment

Introduction

Step-by-Step Guides

The Microsoft Windows Server 2003 Deployment step-by-step guides provide hands-on experience for many common operating system configurations. The guides begin by establishing a common network infrastructure through the installation of Windows Server 2003, the configuration of Active Directory, the installation of a Windows XP Professional workstation, and finally the addition of this workstation to a domain. Subsequent step-by-step guides assume that you have this common network infrastructure in place. If you do not wish to follow this common network infrastructure, you will need to make appropriate modifications while using these guides.

The common network infrastructure requires the completion of the following guides.

•	Part I: Installing Windows Server 2003 as a Domain Controller
•	Part II: Installing a Windows XP Professional Workstation and Connecting it to a Domain

Once the common network infrastructure is configured, any of the additional step-by-step guides may be employed. Note that some step-by-step guides may have additional prerequisites above and beyond the common network infrastructure requirements. Any additional requirements will be noted in the specific step-by-step guide.

Microsoft Virtual PC

The Windows Server 2003 Deployment step-by-step guides may be implemented within a physical lab environment or through virtualization technologies like Microsoft Virtual PC 2004 or Virtual Server 2005. Virtual machine technology enables customers to run multiple operating systems concurrently on a single physical server. Virtual PC 2004 and Virtual Server 2005 are designed to increase operational efficiency in software test and development, legacy application migration, and server consolidation scenarios.

The Windows Server 2003 Deployment step-by-step guides assume that all configurations will occur within a physical lab environment although most configurations can be applied to a virtual environment without modification.

Applying the concepts provided in these step-by-step guides to a virtual environment based is beyond the scope of this document.

Important Notes

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred.

This common infrastructure is designed for use on a private network. The fictitious company name and Domain Name System (DNS) name used in the common infrastructure are not registered for use on the Internet. You should not use this name on a public network or Internet.

The Active Directory service structure for this common infrastructure is designed to show how Windows Server 2003 Change and Configuration Management works and functions with Active Directory. It was not designed as a model for configuring Active Directory for any organization.

This guide explains how to build a common network infrastructure beginning with the installation and configuration of the Microsoft Windows Server 2003 operating system as a domain controller. This common infrastructure allows you to learn about and evaluate Windows Server 2003. As you implement this guide, think about how you will use them in your organization.

This guide, which is the first in a two-part series, shows how to install a server as a domain controller and populate a sample Active Directory service structure. Part two describes steps to install a Windows XP Professional client and connect that client to the domain controller. First, complete the procedures in this guide, then use “Part II: Installing a Windows XP Professional Workstation and Connecting It to a Domain” to complete your common network infrastructure.

Prerequisites

•

None

Guide Requirements

These are the hardware requirements for the common infrastructure.

Item	Quantity	Comments
Server(s)	1	Capable of running Windows Server 2003
Workstation(s)	As Needed	Capable of running Windows XP Professional
Network Hub(s)	As Needed	A private network is recommended
Remote Access Hardware	As Needed	For testing slow-link and remote connections
Network Interface Cards	As Needed	100 MB Card
UPS	Optional	To protect the servers
Printer	Optional	To print configuration information and other tests

Notes:

•	An Intel processor–based server running Windows Server 2003 must have at least 128 megabytes (MB) of RAM. Microsoft also recommends that the server have several gigabytes of disk storage. In addition, servers should be equipped with high-speed network interface cards.
•	Use a sufficient number of workstations to simulate a variety of workstation environments, including your organization’s typical desktop, roaming user, mobile user, and any other configurations that may be appropriate. These computers must be capable of running Windows XP Professional. Microsoft recommends a minimum of 64 MB of RAM for Intel processor–based workstations.
•	When creating the physical infrastructure, a private network is recommended; therefore, you need sufficient network hubs and other networking hardware to connect all of the workstations and servers to a single network.
•	The most current information about hardware requirements and compatibility for servers is available at the Windows Server 2003 Product Compatibility Web site.

Additional Server Parameters

If you add additional servers to the common infrastructure, use the following server naming convention.

Parameter	Value
Computer Name(s)	HQ-CON-SRV-01 HQ-CON-SRV-nn

Server Configuration

Overview

Figure 1 shows the basic server configuration.

 

Figure 1.  The Server Configuration

Server Disk Configuration

To use a single server for the infrastructure in this guide, you will need a server with either two disk drives or a single disk drive with two partitions.

Note:  Subsequent step-by-step guides in this series may require additional servers or other equipment; those additions are addressed in the specific guide.

The first disk or partition holds Windows Server 2003 and other files for the common infrastructure, such as the Windows Installer packages and application source files. The second disk or partition is reserved for Active Directory log files and procedures required by other step-by-step guides.

Each disk or partition must hold several gigabytes of information, and each disk or partition must be formatted for the NT file system (NTFS). The steps for creating and formatting partitions are contained in this guide.

Server Installation

To begin the installation procedure, boot directly from the Windows Server 2003 CD. Your CD-ROM must support bootable CDs.

Note:  When you configure partitions and format drives, all data on the server hard drive is destroyed.

Beginning the Installation

Setup creates the disk partitions on the computer running Windows Server 2003, formats the drive, and then copies installation files from the CD to the server.

Note:  These instructions assume that you are installing Windows Server 2003 on a computer that is not already running Windows. If you are upgrading from an older version of Windows, some of the installation steps may differ.

To begin the installation

1.	Insert the Windows Server 2003 CD in the CD-ROM drive.
2.	Restart the computer. If prompted, press any key to boot from the CD.The Windows Server 2003 installation begins.
3.	On the Welcome to Setup screen, press Enter.
4.	Review and, if acceptable, agree to the license agreement by pressing F8.Note:  If you had a previous version of Windows Server 2003 installed on this server, you might get a message asking if you want to repair the drive. Press Esc to continue and not repair the drive.
5.	Follow the instructions to delete all existing disk partitions. The exact steps will differ based on the number and type of partitions already on the computer. Continue to delete partitions until all disk space is labeled as Unpartitioned space.
6.	When all disk space is labeled as Unpartitioned space, press C to create a partition in the unpartitioned space on the first disk drive (as applicable).
7.	If your server has a single disk drive, split the available disk space in half to create two equal-sized partitions. Delete the total space default value. Type the value of half your total disk space at the Create partition of size (in MB) prompt, and the press Enter. (If your server has two disk drives, type the total size of the first drive at this prompt.)
8.	After the New <Raw> partition is created, press Enter.
9.	Select Format the partition using the NTFS file system <Quick>, and then press Enter.

Windows Server 2003 Setup formats the partition and then copies the files from the Windows Server 2003 Server CD to the hard drive. The computer restarts and the Windows Server 2003 Installation Program continues.

Completing the Installation

To continue the installation with the Windows Server 2003 Setup Wizard

1.	The Windows Server 2003 Setup Wizard detects and installs devices. This can take several minutes, and during the process your screen may flicker.
2.	In the Regional and Language Options dialog box, make changes required for your locale (typically, none are required for the United States), and then click Next.
3.	In the Personalize Your Software dialog, type Mike Nash in the Name box and type Reskit in the Organization box. Click Next.
4.	Type the Product Key (found on the back of your Windows Server 2003 CD case) in the text boxes provided, and then click Next.
5.	In the Licensing Modes dialog box, select the appropriate licensing mode for your organization, and then click Next.
6.	In the Computer Name and Administrator Password dialog box, type the new computer name HQ-CON-DC-01 in the computer name box, and then click Next.Best Practice:  To facilitate the steps in these guides, the Administrator password is left blank and there is no password. This is not an acceptable security practice. When installing a server for your production network, a password should always be set. Windows Server 2003 requires complex passwords by default.
7.	When prompted by Windows Setup, click Yes to confirm a blank Administrator password.
8.	In the Date and Time Settings dialog box, correct the current date and time if necessary, and then click Next.
9.	In the Networking Settings dialog box, make sure Typical Settings is selected, and then click Next.
10.	In the Workgroups or Computer Domain dialog box (No is selected by default), click Next.Note:  A domain name could be specified at this point, but this guide uses the Configure Your Server Wizard to create the domain name at a later time. The Windows Server 2003 Installation continues and configures the necessary components. This may take a few minutes.
11.	The server restarts and the operating system loads from the hard drive.

Preparing a Secondary Partition or Secondary Disk Drive

The unpartitioned space from the installation of Windows Server 2003 requires formatting before it can be accessed by the operating system. Management of disks and partitions occurs through the Computer Management snap-in for Microsoft Management Console. The following steps assume a second disk drive is in use; modify procedures accordingly for a second partition.

To prepare a secondary partition or disk drive

Warning:  Formatting a partition destroys all data on that partition. Make sure that you select the correct partition.

1.	Press Ctrl+Alt+Del and log on to the server as administrator. Leave the password blank.
2.	Click the Start button, point to Administrative Tools, and then click Computer Management.
3.	To define and format the unpartitioned space, click Disk Management.
4.	Right-click Unallocated on Disk 1.
5.	To define a partition, click New Partition, and then click Next to continue.
6.	Select Primary Partition (default), and then click Next to continue.
7.	Click Next leaving the Partition size in MB set to the default.
8.	For Assign the following drive letter, select L, and then click Next to continue.
9.	Under Format this partition with the following settings, click Perform a quick format. Click Next, and then Finish to complete the configuration of the secondary disk drive. Once you have finished, your disk allocation should look similar to Figure 2. <!–[if !vml]–><!–[endif]–> Figure 2.  Disk Management
10.	Close the Computer Management console.

Configuring Your Server as a DHCP Server

Dynamic Host Configuration Protocol (DHCP) can be installed manually or by using the Windows Server 2003 Manage Your Server wizard. This section uses the wizard to complete the installation.

To install DHCP using the Windows Server 2003 Manage Your Server wizard

Warning: The following section will configure your server as a DHCP server. If this server resides on a production network, the server may distribute IP address information that might not be valid on the network. Microsoft recommends that these exercises be completed on an isolated network.

1.	Within the Manager Your Server page, click Add or remove a role.Note: If you closed the Manage Your Server page you can start the Configure Your Server wizard from Administrative Tools. If you select this option the following steps may differ slightly.
2.	After the Configure Your Server wizard appears, click Next.
3.	Click Custom configuration, and then click Next.
4.	Under Server Role, click DHCP server, and then click Next.
5.	Review the Summary of Selections, and then click Next to begin the installation.
6.	When the New Scope Wizard appears, click Next to define a DHCP scope.
7.	For Name, type Contoso HQ. Leave the description blank, and then click Next.
8.	Enter a Start IP address of 10.0.0.10 and enter 10.0.0.254 for the End IP address. Click Next.
9.	Exclusions will not be defined at this time. Click Next to continue the installation.
10.	To accept the default Lease Duration, click Next.
11.	To set DHCP Options, click Next.
12.	On the Router (Default Gateway) screen, type 10.0.0.1 for IP address, click Add, and then click Next.
13.	For Parent Domain on the Domain Name and DNS Server screen, type contoso.com. For IP address, type 10.0.0.2, click Add, and then click Next.
14.	Click Next as WINS Servers will not be utilized in this environment.
15.	Click Next to Activate Scope.
16.	Click Finish twice.
17.	Close the Manage Your Server screen.

Configuring Your Server as a Domain Controller

Domain Name Service (DNS) and DCPromo (the command-line tool that creates DNS and Active Directory) can be installed manually or by using the Windows Server 2003 Manager Your Server Wizard. This section uses the manual tools to complete the installation.

To install DNS and Active Directory using the manual tools

1.	Click the Start button, click Run, type DCPROMO, and then click OK.
2.	When the Active Directory Installation Wizard appears, click Next to begin the installation.
3.	After reviewing the Operating System Compatibility information, click Next.
4.	Select Domain controller for a new domain (default), and then click Next.
5.	Select Domain in a new forest (default), and then click Next.
6.	For Full DNS name, type contoso.com, and then click Next. (This represents a Fully Qualified name.)
7.	Click Next to accept the default Domain NetBIOS name of CONTOSO. (NetBIOS names provides for down-level compatibility.)
8.	On the Database and Log Folders screen, point the Active Directory Log Folder to L:\Windows\NTDS, and then click Next to continue.
9.	Leave the default folder location for Shared System Volume, and then click Next.
10.	On the DNS Registration Diagnostics screen, click Install and configure the DNS server on this computer. Click Next to continue.
11.	Select Permissions compatible only with Windows 2000 or Windows Server 2003 (default), and then click Next.
12.	Type password for Restore Mode Password and Confirm password, and then click Next to continue.Note:  Production environments should employ complex passwords for Directory Services Restore passwords. <!–[if !vml]–><!–[endif]–> Figure 3.  Summary of the Active Directory Installation Options
13.	Figure 3 represents a summary of the Active Directory installation options. Click Next to start the installation of Active Directory. If prompted, insert the Windows Server 2003 installation CD.
14.	Click OK to acknowledge the warning of having a dynamically assigned IP address for a DNS server.
15.	If you have more than one network interface, select the 10.0.0.0 network interface from the Choose Connection drop-down list, and then click Properties.
16.	Under the This connection uses the following items section, click Internet Protocol (TCP/IP), and then click Properties.
17.	Select Use the following IP address, and then type 10.0.0.2 for the IP address. Press the Tab key twice, and then type 10.0.0.1 for the Default gateway. Type 127.0.0.1 for the Preferred DNS server, and then click OK. Click Close to continue.
18.	Click Finish once the Active Directory Installation Wizard is finished.
19.	Click Restart Now to reboot the computer.

To authorize the DHCP server

1.	After the computer reboots, press Ctrl+Alt+Del and log on to the server as administrator@contoso.com. Leave the password blank.
2.	Click the Start menu, select Administrative Tools, and then click DHCP
3.	Click hq-con-dc-01.contoso.com. Right click hq-con-dc-01.contoso.com and then click Authorize
4.	Close the DHCP management console

Active Directory Sample Infrastructure

The common infrastructure is based on the fictitious organization Contoso. Contoso owns the DNS name contoso.com, which was configured with the Active Directory Installation Wizard in the preceding section. Figure 4 illustrates the sample Active Directory structure.

<!–[if !vml]–><!–[endif]–>

Figure 4.  Sample Active Directory Structure

The most interesting aspects of this structure are the Domain (contoso.com); the Accounts, Headquarters, Production, Marketing, Groups, Resources, Desktops, Laptops, and Servers organizational units (OUs). These are represented by folders (book) in Figure 4. OUs exist for the delegation of administration and for the application of Group Policy—not simply to mirror a business organization. For an in-depth discussion on designing an OU structure, see “Designing and Deploying Directory and Security Services”.

Populating Active Directory

This section describes how to manually create the OUs, Users, and Security Groups outlined in Appendix A.

Creating Organizational Units and Groups

To create OUs and Security Groups

1.	Click the Start button, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	Click the + next to contoso.com to expand it. Click contoso.com itself to show its contents in the right pane.
3.	In the left pane, right-click contoso.com, point to New, and then click Organizational Unit.
4.	Type Accounts in the name box, and then click OK.
5.	Repeat steps 3 and 4 to create the Groups and Resources OUs.
6.	Click Accounts in the left pane. Its contents now display in the right pane. (It is empty at the beginning of this procedure.)
7.	Right-click Accounts, point to New, and then click Organizational Unit.
8.	Type Headquarters, and then click OK.
9.	Repeat steps 7 and 8 to create the Production and Marketing OUs in Accounts. When you have finished, the OU structure should look like Figure 5. <!–[if !vml]–><!–[endif]–> Figure 5.  Creating Organizational Units See full-sized image
10.	In the same way, create Desktops, Laptops, and Servers in the Resources OU.
11.	Create the two security groups by right-clicking Groups, pointing to New, and then clicking Group. The two groups to add are Management and Non-management. The settings for each group should be Global and Security. Click OK to create each group. When all steps are completed, the final OU structure should look like Figure 6. <!–[if !vml]–><!–[endif]–> Figure 6.  Final OU Structure See full-sized image

Creating User Accounts

To create a user account

1.	In the left-hand pane, click Headquarters (in Accounts).. Its contents now display in the right pane. (It is empty at the beginning of this procedure.)
2.	Right-click Headquarters, point to New, and then click User.
3.	Type Christine for the first name and Koch for the last name. (Note that the full name automatically appears in the Full name box.)
4.	Type Christine for the User logon name. The window should look like Figure 7. <!–[if !vml]–><!–[endif]–> Figure 7.  Adding a User
5.	Click Next.
6.	Type pass#word1 for Password and Confirm password, and then click Next to continue.Note:  By default, Windows Server 2003 requires complex passwords for all newly created users. Password complexity requirements may be disabled through Group Policy.
7.	Click Finish. Christine Koch now displays in the right-hand pane as a user under Reskit.com/Accounts/Headquarters.
8.	Repeat steps 2 through 7, adding the names listed in Appendix A for the Headquarters OU. When you are finished, the Headquarters OU screen should look like Figure 8. <!–[if !vml]–><!–[endif]–> Figure 8.  User listing in the Headquarters OU See full-sized image
9.	Repeat steps 1 through 8 to create the users in the Production and Marketing OUs.

Adding Users to Security Groups

To add a user to a security group

1.	In the left pane, click Groups.
2.	In the right pane, double-click the Management group.
3.	Click the Members tab, and then click Add.
4.	Click Advanced, and then click Find Now.
5.	Select all appropriate users from the lower section by holding down the Ctrl key while clicking each name. Click OK while all members are highlighted. (The users who should be members of this security group are listed in Appendix A.) Click OK again to add these members to the Management Security Group. Click OK to close the Management Security Group Properties sheet. <!–[if !vml]–><!–[endif]–> Figure 9.  The Members of the Management Security Group Are Drawn from Three OUs
6.	Repeat steps 2 through 5 to add members to the Non-management group.
7.	Close the Active Directory Users and Computers snap-in.

<!–[if !vml]–><!–[endif]–>Top of page

Appendix A:  Active Directory Populace

Users

OU	Full Name	Login Name	Group Membership
Headquarters	Koch, Christine	Christine	Management
	West, Paul	Paul	Management
	Clark, Molly	Molly	Management
	Sprenger, Christof	Christof	Management
	Schleger, Yvonne	Yvonne	Management
	Nash, Mike	Mike	Management
	Brink, Monica	Monica	Non-management
Production	Ola, Preeda	Preeda	Management
	Grande, Jon	Jon	Non-management
	Hector, Clair	Clair	Non-management
	Kim, Jim	Jim	Non-management
	Nay, Lorraine	Lorraine	Management
	Randall, Cynthia	Cynthia	Non-management
	Browne, Kevin F.	Kevin	Non-management
Marketing	Fitzgerald, Charles	Charles	Management
	Mustafa, Ahmad	Ahmad	Non-management
	Narp, Sylvie	Sylvie	Non-management

 

How To Install and Configure a File and Print Server in Windows Server 2003

Install File and Printer Sharing

loadTOCNode(2, \’summary\’); By default, a Windows Server 2003-based computer is installed with Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and TCP/IP.

NOTE: You can view these services in the properties for the local area connection.

You can create a Windows Server 2003 file server and print server manually, or you can use the wizards that are provided in the Configure Your Server Wizard administrative tool.

How to Install a File Server on Windows Server 2003 by Using the Configure Your Server Wizard

loadTOCNode(3, \’summary\’); 1.	Click Start, point to Administrative Tools, and then click Configure Your Server Wizard.
2.	Click Next.
3.	Click Next.
4.	Click File server in the Server role box, and then click Next.
5.	On the “File Server Disk Quotas” page, configure any quotas you need to control disk-space usage on the server, and then click Next.
6.	On the “File Server Indexing Service” page, click the indexing configuration that is appropriate for your server, and then click Next.
7.	Click Next.
8.	Click Finish.
9.	The Share a Folder Wizard starts. Click Next.
10.	Click Browse, locate the folder that you want to share, and then click OK.
11.	Click Next.
12.	Type a share name for the folder, and then click Next.
13.	Click one of the basic permissions for the folder, or click Customize to set custom permissions on the folder. Click Finish.
14.	Click Close.

How to Manually Install a File Server on Windows Server 2003

loadTOCNode(3, \’summary\’); 1.	Click Start, and then click Windows Explorer.
2.	Locate the folder that you want to share.
3.	Right-click the folder, and then click Sharing and Security.
4.	Click Share this folder, and then accept the default name or type a different name for the share.
5.	Optionally, configure the number of users who can connect, configure permissions for this folder, and then configure the caching options.
6.	Click OK.
7.	A little hand is displayed in the Windows Explorer window to indicate that the folder is being shared.
8.	Quit Windows Explorer.

Install a Windows Server 2003 Print Server

loadTOCNode(2, \’summary\’); How to Install a Print Server on Windows Server 2003 by Using the Configure Your Server Wizard

loadTOCNode(3, \’summary\’); 1.	Click Start, point to Administrative Tools, and then click Configure Your Server Wizard.
2.	Click Next.
3.	Click Next.
4.	Click Print server in the Server role box, and then click Next.
5.	On the “Printers and Printer Drivers” page, click the types of Windows clients that your print server will support, and then click Next.
6.	Click Next.
7.	On the “Add Printer Wizard Welcome” page, click Next.
8.	Click Local printer attached to this computer, click to clear the Automatically detect and install my Plug and Play printer check box, and then click Next.
9.	Click the port for your printer, and then click Next.
10.	Click the printer make and model or provide the drivers from the printer manufacturer media, and then click Next. NOTE: If you are prompted to keep or not keep your existing printer driver, either keep the existing driver or replace the existing driver. If you replace the driver, you must provide the manufacturer driver for this printer. Click Next to continue.
11.	Accept the default name of the printer or provide a different name, and then click Next.
12.	Click the Share as option, type the share name, and then click Next. NOTE: This step is optional because you can share the printer later.
13.	You may provide the location of the printer and a comment to make it easier to locate. Click Next to continue.
14.	Click the Print a test page option, click Next, and then click Finish to quit the Add Printer Wizard. Your printer appears in the Printers and Faxes folder.

How to Share a Printer

loadTOCNode(3, \’summary\’); 1.	Click Start, and then click Printers and Faxes.
2.	Right-click the printer that you just installed, and then click Sharing.
3.	Click Share this printer, and then type a share name for the printer.
4.	Optionally, click Additional Drivers, click the operating systems of the client computers that may attach to this printer, and then click OK. By adding drivers for these operating systems, users on client computers can connect to the print server and automatically download the appropriate drivers for this model of printer without having to configure anything.
5.	When you are prompted to do so, insert the Windows Server 2003 CD-ROM.
6.	Click OK to close the printer properties.
7.	Close the Printers and Faxes folder.

How to Manually Install a Print Server on Windows Server 2003

loadTOCNode(3, \’summary\’); 1.	Click Start, point to Settings, and then click Printers.
2.	Double-click Add Printer to start the Add Printer Wizard.
3.	To complete the Add Printer Wizard, repeat steps 7 through 14 in the “Install a Windows Server 2003 Print Server” section of this article.

 

List of FTP commands for the Microsoft command-line FTP client

Command-line options

As you’re starting the program from a DOS prompt:
ftp [-v] [-d] [-i] [-n] [-g] [-s:filename] [-a] [-w:windowsize] [computer]

• -v – Suppresses verbose display of remote server responses.
• -n – Suppresses auto-login upon initial connection.
• -i – Turns off interactive prompting during multiple file transfers.
• -d – Enables debugging, displaying all ftp commands passed between the client and server.
• -g – Disables filename globbing, which permits the use of wildcard chracters in local file and path names.
• -s:filename – Specifies a text file containing ftp commands; the commands will automatically run after ftp starts. No spaces are allowed in this parameter. Use this switch instead of redirection (>).
• -a – Use any local interface when binding data connection.
• -w:windowsize – Overrides the default transfer buffer size of 4096.
• computer – Specifies the computer name or IP address of the remote computer to connect to. The computer, if specified, must be the last parameter on the line.

Client commands

• ! – Runs the specified command on the local computer
• ? – Displays descriptions for ftp commands
• append – Appends a local file to a file on the remote computer
• ascii – Sets the file transfer type to ASCII, the default
• bell – Toggles a bell to ring after each file transfer command is completed (default = OFF)
• binary – Sets the file transfer type to binary
• bye – Ends the FTP session and exits ftp
• cd – Changes the working directory on the remote computer
• close – Ends the FTP session and returns to the command interpreter
• debug – Toggles debugging (default = OFF)
• delete – Deletes a single file on a remote computer
• dir – Displays a list of a remote directory’s files and subdirectories
• disconnect – Disconnects from the remote computer, retaining the ftp prompt
• get – Copies a single remote file to the local computer
• glob – Toggles filename globbing (wildcard characters) (default = ON)
• hash – Toggles hash-sign (#) printing for each data block transferred (default = OFF)
• help – Displays descriptions for ftp commands
• lcd – Changes the working directory on the local computer
• literal – Sends arguments, verbatim, to the remote FTP server
• ls – Displays an abbreviated list of a remote directory’s files and subdirectories
• mdelete – Deletes one or more files on a remote computer
• mdir – Displays a list of a remote directory’s files and subdirectories
• mget – Copies one or more remote files to the local computer
• mkdir – Creates a remote directory
• mls – Displays an abbreviated list of a remote directory’s files and subdirectories
• mput – Copies one or more local files to the remote computer
• open – Connects to the specified FTP server
• prompt – Toggles prompting (default = ON)
• put – Copies a single local file to the remote computer
• pwd – Displays the current directory on the remote computer (literally, “print working directory”)
• quit – Ends the FTP session with the remote computer and exits ftp (same as “bye”)
• quote – Sends arguments, verbatim, to the remote FTP server (same as “literal”)
• recv – Copies a remote file to the local computer
• remotehelp – Displays help for remote commands
• rename – Renames remote files
• rmdir – Deletes a remote directory
• send – Copies a local file to the remote computer (same as “put”)
• status – Displays the current status of FTP connections
• trace – Toggles packet tracing (default = OFF)
• type – Sets or displays the file transfer type (default = ASCII)
• user – Specifes a user to the remote computer
• verbose – Toggles verbose mode (default = ON)

---

!

Runs the specified command on the local computer.Syntax: ! [command]

Parameter(s):
command – Specifies the command to run on the local computer. If command is omitted, the local command prompt is displayed; type “exit” to return to ftp.

?

Displays descriptions for ftp commands. ? is identical to help.Syntax: ? [command]

Parameter(s):
command – Specifies the name of the command about which you want a description. If command is not specified, ftp displays a list of all commands.

append

Appends a local file to a file on the remote computer using the current file type setting.Syntax: append local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to add.
remote-file – Specifies the file on the remote computer to which local-file will be added. If remote-file is omitted, the local filename is used for the remote filename.

ascii

Sets the file transfer type to ASCII, the default.Syntax: ascii

Note
FTP supports two file transfer types, ASCII and binary image. ASCII should be used when transferring text files. See also binary.

In ASCII mode, character conversions to and from the network standard character set are performed. For example, end-of-line characters are converted as necessary, based on the target operating system.

bell

Toggles a bell to ring after each file transfer command is completed. By default, the bell is off.Syntax: bell

binary

Sets the file transfer type to binary.Syntax: binary

Note
FTP supports two file transfer types, ASCII and binary image. Binary should be used when transferring executable files. In binary mode, the file is moved byte-by-byte. See also ascii.

bye

Ends the FTP session with the remote computer and exits ftp.Syntax: bye

cd

Changes the working directory on the remote computer.Syntax: cd remote-directory

Parameter(s):
remote-directory – Specifies the directory on the remote computer to change to.

close

Ends the FTP session with the remote server and returns to the command interpreter.Syntax: close

debug

Toggles debugging. When debugging is on, each command sent to the remote computer is printed, preceded by the string —>. By default, debugging is off.Syntax: debug

delete

Deletes a single file on a remote computer. See also mdelete, which can delete multiple files.Syntax: delete remote-file

Parameter(s):
remote-file – Specifies the file to delete.

dir

Displays a list of a remote directory’s files and subdirectories. See also mdir, which can list multiple directories.Syntax: dir [remote-directory] [local-file]

Parameter(s):
remote-directory – Specifies the directory for which you want to see a listing. If no directory is specified, the current working directory on the remote computer is used.
local-file – Specifies a local file to store the listing. If not specified, output is displayed on the screen.

disconnect

Disconnects from the remote computer, retaining the ftp prompt.Syntax: disconnect

get

Copies a remote file to the local computer using the current file transfer type. See also mget, which can copy multiple files.Syntax: get remote-file [local-file]

Parameter(s):
remote-file
Specifies the remote file to copy.

local-file
Specifies the name to use on the local computer. If not specified, the file is given the remote-file name.

glob

Toggles filename globbing. Globbing permits use of wildcard characters in local file or path names. By default, globbing is on.Syntax: glob

hash

Toggles hash-sign (#) printing for each data block transferred. The size of a data block is 2048 bytes. By default, hash mark printing is off.Syntax: hash

help

Displays descriptions for ftp commands.Syntax: help [command]

Parameter(s):
command – Specifies the name of the command about which you want a description. If command is not specified, ftp displays a list of all commands.

lcd

Changes the working directory on the local computer. By default, the working directory is the directory in which ftp was started.Syntax: lcd [directory]

Parameter(s):
directory – Specifies the directory on the local computer to change to. If directory is not specified, the current working directory on the local computer is displayed.

literal

Sends arguments, verbatim, to the remote FTP server. A single FTP reply code is expected in return.Syntax: literal argument [ ...]

Parameter(s):
argument – Specifies the argument to send to the FTP server.

ls

Displays an abbreviated list of a remote directory’s files and subdirectories.Syntax: ls [remote-directory] [local-file]

Parameter(s):
remote-directory – Specifies the directory for which you want to see a listing. If no directory is specified, the current working directory on the remote computer is used.
local-file – Specifies a local file to store the listing. If not specified, output is displayed on the screen.

mdelete

Deletes one or more files on a remote computer.Syntax: mdelete remote-files [ ...]

Parameter(s):
remote-files – Specifies the remote files to delete.

mdir

Displays a list of a remote directory’s files and subdirectories. Mdir allows you to specify multiple files.Syntax: mdir remote-files [ ...] local-file

Parameter(s):
remote-files – Specifies the directory for which you want to see a listing. Remote-files must be specified; type “-” to use the current working directory on the remote computer.
local-file – Specifies a local file to store the listing. Type “-” to display the listing on the screen.

mget

Copies one or more remote files to the local computer using the current file transfer type.Syntax: mget remote-files [ ...]

Parameter(s):
remote-files – Specifies the remote file(s) to copy to the local computer.

mkdir

Creates a remote directory.Syntax: mkdir directory

Parameter(s):
directory – Specifies the name of the new remote directory.

mls

Displays an abbreviated list of a remote directory’s files and subdirectories.Syntax: mls remote-files [ ...] local-file

Parameter(s):
remote-files – Specifies the files for which you want to see a listing. Remote-files must be specified; type “-” to use the current working directory on the remote computer.
local-file – Specifies a local file to store the listing. Type “-” to display the listing on the screen.

mput

Copies one or more local files to the remote computer using the current file transfer type.Syntax: mput local-files [ ...]

Parameter(s):
local-files – Specifies the local files to copy to the remote computer.

open

Connects to the specified FTP server.Syntax: open computer [port]

Parameter(s):
computer – Specifies the remote computer to connect to. Computer can be specified by IP address or computer name (a DNS or HOSTS file must be available). If auto-login is on (default), FTP also attempts to automatically log the user in to the FTP server (see Ftp command-line options to disable auto-login).
port – Specifies a port number to use to contact an FTP server.

prompt

Toggles prompting. Ftp prompts during multiple file transfers to allow you to selectively retrieve or store files; mget and mput transfer all files if prompting is turned off. By default, prompting is on.Syntax: prompt

put

Copies a local file to the remote computer using the current file transfer type. See also mput, which can copy multiple files.Syntax: put local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to copy.
remote-file – Specifies the name to use on the remote computer. If not specified, the file is given the local-file name.

pwd

Displays the current directory on the remote computer.Syntax: pwd

quit

Ends the FTP session with the remote computer and exits ftp.Syntax: quit

quote

Sends arguments, verbatim, to the remote FTP server. A single FTP reply code is expected in return. Quote is identical to literal.Syntax: quote argument [ ...]

Parameter(s):
argument – Specifies the argument to send to the FTP server.

recv

Copies a remote file to the local computer using the current file transfer type. Recv is identical to get.Syntax: recv remote-file [local-file]

Parameter(s):
remote-file – Specifies the remote file to copy.
local-file – Specifies the name to use on the local computer. If not specified, the file is given the remote-file name.

remotehelp

Displays help for remote commands.Syntax: remotehelp [command]

Parameter(s):
command – Specifies the name of the command about which you want help. If command is not specified, ftp displays a list of all remote commands.

rename

Renames remote files.Syntax: rename filename newfilename

Parameter(s):
filename – Specifies the file you want to rename.
newfilename – Specifies the new filename.

rmdir

Deletes a remote directory.Syntax: rmdir directory

Parameter(s):
directory – Specifies the name of the remote directory to delete.

send

Copies a local file to the remote computer using the current file transfer type. Send is identical to put.Syntax: send local-file [remote-file]

Parameter(s):
local-file – Specifies the local file to copy.
remote-file – Specifies the name to use on the remote computer. If not specified, the file is given the local-file name.

status

Displays the current status of FTP connections and toggles.Syntax: status

trace

Toggles packet tracing; trace displays the route of each packet when running an ftp command.Syntax: trace

type

Sets or displays the file transfer type.Syntax: type [type-name]

Parameter(s):
type-name – Specifies the file transfer type; the default is ASCII. If type-name is not specified, the current type is displayed.

Note
FTP supports two file transfer types, ASCII and binary image.

ASCII should be used when transferring text files. In ASCII mode, character conversions to and from the network standard character set are performed. For example, end-of-line characters are converted as necessary, based on the destination’s operating system.

Binary should be used when transferring executable files. In binary mode, the file is moved byte-by-byte.

user

Specifes a user to the remote computer.Syntax: user user-name [password] [account]

Parameter(s):
user-name – Specifies a user name with which to log in to the remote computer.
password – Specifies the password for user-name. If not specified, but required, ftp prompts for the password.
account – Specifies an account with which to log on to the remote computer. If account is not specified, but required, ftp prompts for the account.

verbose

Toggles verbose mode. If on, all ftp responses are displayed; when a file transfer completes, statistics regarding the efficiency of the transfer are also displayed. By default, verbose is on.