Thursday, March 28, 2013

Configuring Windows Server 2008 Server Core Basic Networking Settings


Like any other server, Server Core machines must be properly configured to be able to communicate on your network. Some of these settings include:
  • Configuring an IP address
  • Configuring an administrator's password
  • Configuring a server name
  • Enabling remote MMC snap-in management
  • Enabling remote RDP connections
  • Enabling remote Windows Firewall management
  • Enabling remote shell management
  • Activating the server
  • Joining a domain
  • Configuring Windows Updates
  • Configuring error reporting
  • Adding server roles and features
And other tasks.
Before you start, you need to configure the server's IP address.

To set the server with a static IP address

  1. At a command prompt, type the following:
    netsh interface ipv4 show interfaces
  2. Look at the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address.
  3. At the command prompt, type:
    netsh interface ipv4 set address name="" source=static address= mask= gateway=
    Where:
    • ID is the number from step 2 above
    • StaticIP is the static IP address that you are setting
    • SubnetMask is the subnet mask for the IP address
    • DefaultGateway is the default gateway
  4. At the command prompt, type:
    netsh interface ipv4 add dnsserver name="" address= index=1
    Where:
    • ID is the number from step 2 above
    • DNSIP is the IP address of your DNS server
  5. Repeat step 4 for each DNS server that you want to set, incrementing the index= number each time.
  6. Verify by typing ipconfig /all and checking that all the addresses are correct.

To set the administrative password in Windows Server 2008

  1. At a command prompt, type the following:
    net user administrator *
  2. When prompted to enter the password, type the new password for the administrator user account and press ENTER.
  3. When prompted, retype the password and press ENTER.
Next, you might want to change the computer's name, as the default name is a random-generated name (unless configured through an answer file)

To change the name of the server

  1. Determine the current name of the server with the hostname or ipconfig /all commands.
  2. At a command prompt, type:
    netdom renamecomputer  /NewName:
  3. Restart the computer by typing the following at a command prompt:
    shutdown /r /t 0

To manage a server running a Server Core installation by using the Windows Remote Shell

  1. To enable Windows Remote Shell on a server running a Server Core installation, type the following command at a command prompt:
    WinRM quickconfig
  2. Click Y to accept the default settings. Note: The WinRM quickconfig setting enables a server running a Server Core installation to accept Windows Remote Shell connections.
  3. 3. On the remote computer, at a command prompt, use WinRS.exe to run commands on a server running a Server Core installation. For example, to perform a directory listing of the Windows folder, type:
    winrs -r: cmd
    Where ServerName is the name of the server running a Server Core installation.
  4. You can now type any command that you require, it will be executed on the remote computer.

To activate the server

  1. At a command prompt, type:
    slmgr.vbs –ato
    If activation is successful, no message will return in the command prompt.

To activate the server remotely

  1. At a command prompt, type:
    cscript slmgr.vbs -ato
  2. Retrieve the GUID of the computer by typing:
    cscript slmgr.vbs -did
  3. Type
    cscript slmgr.vbs -dli
  4. Verify that License status is set to Licensed (activated).

To join a Windows 2008 server to a domain

  1. At a command prompt, type:
    netdom join  /domain: /userd: /passwordd:*
    Where:
    • ComputerName is the name of the server that is running the Server Core installation.
    • DomainName is the name of the domain to join.
    • UserName is a domain user account with permission to join the domain.
    Note: Entering * as the password means you will be prompted to enter it on the command prompt window in the next step. You can enter it in the initial command, if you wish to. Note: Note that the word "passwordd" has 2 d's in it…
  2. When prompted to enter the password, type the password for the domain user account specified by UserName.
  3. Restart the computer by typing the following at a command prompt:
    shutdown /r /t 0

To remove the Windows 2008 server from a domain

  1. At a command prompt, type:
    netdom remove
  2. Reboot the computer.

To configure automatic updates

  1. To enable automatic updates, type:
    cscript C:'Windows'System32'Scregedit.wsf /au 4
  2. To disable automatic updates, type:
    cscript C:'Windows'System32'Scregedit.wsf /au 1
    BTW, in order to view your current settings you can type:
    cscript C:'Windows'System32'Scregedit.wsf /au /v

To configure error reporting

  1. To verify the current setting, type:
    serverWerOptin /query
  2. To automatically send detailed reports, type:
    serverWerOptin /detailed
  3. To automatically send summary reports, type:
    serverWerOptin /summary
  4. To disable error reporting, type:
    serverWerOptin /disable

Summary

Windows Server 2008 Core machines need to be properly configured for communication across your network. While most of the Server Core settings need to be configured via the local Command Prompt, some settings can also be configured remotely. This article, a part of a complete Server Core article series, will show you how to do that.

Recent Windows Server 2008 Forum threads

Got a question? Post it on our Windows Server 2008 forums!

How to Configure Windows Server 2008 for Configuration Manager 2007 Site Systems



Applies To: System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
Use the procedures in this topic to help you configure Windows Server 2008 and Windows Server 2008 R2 to support Configuration Manager 2007 SP1 or later site systems.
noteNote
Configuration Manager 2007 SP1 or later supports installing primary and secondary site systems on Windows Server 2008 and Windows Server 2008 R2 read-only domain controller (RODC) computers. During a site installation, the Configuration Manager 2007 Setup Wizard identifies that the site is being installed on an RODC and searches for a writable domain controller to create the necessary groups required by the type of site installation. However, when installing secondary sites by using the Install Secondary Site Installation Wizard from a Configuration Manager console, you must create the required groups in Active Directory Domain Services before you run the secondary site installation.
Use the following information in this topic to configure Windows Server 2008 and Windows Server 2008 R2 site systems for Configuration Manager:

Remote Differential Compression for site server and branch distribution point computers

Site servers and branch distribution points require Remote Differential Compression (RDC) to generate package signatures and perform signature comparison. By default, RDC is not installed on Windows Server 2008 or Windows Server 2008 R2 and must be enabled manually.
Use the following procedure to enable Remote Differential Compression for Windows Server 2008 and Windows Server 2008 R2.
  1. On the Windows Server 2008 or Windows Server 2008 R2 computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select the Features node and click Add Features to start the Add Features Wizard.
  2. On the Select Features page, select Remote Differential Compression, and then click Next.
  3. Complete the rest of the wizard.
  4. Close Server Manager.

Internet Information Services (IIS)

You must install Internet Information Services (IIS) for Windows Server 2008 and Windows Server 2008 R2 computers when they will be used to hold any of the following site system roles:
  • Management point
  • Distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS
  • Reporting point
  • Software update point
  • Server locator point
  • Fallback status point

Configure WebDAV to support management points and distribution points that are enabled for "Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS"

In addition to IIS, you must configure WebDAV extensions for management points and distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.
  • Windows Server 2008 with IIS 7.0: Manually install and configure WebDAV extensions after installing IIS 7.0.
  • Windows Server 2008 R2 with IIS 7.5: WebDAV extensions are included with IIS, and you do not have to download them manually, but you must enable WebDAV extensions during IIS installation.

Install Internet Information Services (IIS) on Windows Server 2008 and Windows Server 2008 R2 Computers

Use the following procedure that applies to Windows Server 2008 and Windows Server 2008 R2:
  1. On the Windows Server computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select theFeatures node, and then click Add Features to start the Add Features Wizard.
  2. On the Select Features page of the Add Features Wizard:

    • For Windows Server 2008, select the BITS Server Extensions check box. For Windows Server 2008 R2, select the Background Intelligent Transfer Services (BITS) check box. When prompted, click Add Required Role Services to add the dependent components, including the Web Server (IIS) role.
    • Select the Remote Differential Compression check box, and then click Next.
  3. On the Web Server (IIS) page of the Add Features Wizard, click Next.
  4. On the Select Role Services page of the Add Features Wizard:

    • Windows Server 2008 R2 only: For Common HTTP Features, select the WebDAV Publishing check box.
    • For Application Development, select the ASP.NET check box and, when prompted, click Add Required Role Services to add the dependent components.

      noteNote
      The ASP check box must also be selected if the site system will be configured as a reporting point.
    • For Security, select the Windows Authentication check box.
    • In the Management Tools node, for IIS 6 Management Compatibility, ensure that both the IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility check boxes are selected, and then click Next.
  5. On the Confirmation page, click Install, and then complete the rest of the wizard.
  6. Click Close to exit the Add Features Wizard, and then close Server Manager.

Install WebDAV for IIS 7.0

You must install WebDAV manually on Windows Server 2008 computers with IIS 7.0. The following procedure applies to Windows Server 2008 with IIS 7.0 installed:
  1. Depending on your server operating system architecture, download either the x86 or x64 version of WebDAV from: http://go.microsoft.com/fwlink/?LinkId=108052.
  2. Depending on the version you downloaded, run either the webdav_x86_rtw.msi or the webdav_x64_rtw.msi file to install WebDAV IIS 7.0 extensions.

Enable WebDAV and create an Authoring Rule

Use the following procedure to enable WebDAV and create an Authoring Rule for Windows Server 2008 and Windows Server 2008 R2:
  1. Navigate to Start / All Programs / Administrative Tools / Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager.
  2. In the Connections pane, expand the Sites node, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system.
  3. In the Features View, double-click WebDAV Authoring Rules.
  4. With the WebDAV Authoring Rules page displayed, in the Actions pane, click Enable WebDAV.
  5. In the Actions pane, click Add Authoring Rule.
  6. In the Add Authoring Rule dialog box, for Allow access to, select All content.
  7. For Allow access to this content to, select All users.
  8. For Permissions, select Read, and then click OK.
Use the following procedure to change the property behavior of WebDAV on Windows Server 2008 and Windows Server 2008 R2:
  1. In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings.
  2. In the WebDAV Settings page, for Property Behavior, set Allow anonymous property queries to True.
  3. Set Allow Custom Properties to False.
  4. Set Allow property queries with infinite depth to True.
  5. For a distribution point that is enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS, for WebDAV Behavior, setAllow hidden files to be listed to True.
  6. In the Action pane, click Apply.
  7. Close Internet Information Services (IIS) Manager.

Configure requestFiltering for IIS on distribution points

The following information applies when you use distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.
By default, IIS blocks several file extensions and folder locations. If package source files contain extensions that are blocked in IIS, you must configure the requestFiltering section in the applicationHost.config file on a distribution points that is enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.
For example, you might have source files for a software deployment that include a folder named bin, or that contain a file with the .mdb file extension. By default, IIS request filtering blocks access to these elements. When you use the default IIS configuration on a distribution point, clients that use BITS fail to download this software deployment from the distribution point. In this scenario, the clients indicate that they are waiting for content. To enable the clients to download this content by using BITS, on each applicable distribution point, edit the requestFiltering section of the applicationHost.config file to allow access to the files and folders in the software deployment.
ImportantImportant
When you enable WebDAV and modify the requestFiltering section of the applicationHost.config file for the Web site, this increases the attack surface of the computer. Enable WebDAV only when required for management points and distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS. If you enable WebDAV on the default Web site, it is enabled for all applications that use the default Web site. If you modify the requestFiltering section, it is modified for all Web sites on that server. The security best practice is to run Configuration Manager 2007 on a dedicated Web server. If you must run other applications on the Web server, use a custom Web site for Configuration Manager 2007. For more information, see Best Practices for Securing Site Systems.
Use the following procedure to modify requestFiltering for Windows Server 2008 and Windows Server 2008 R2.
  1. Open the applicationHost.config file located in the %Windir%\System32\Inetsrv\Config\ directory on distribution points that are enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS.
  2. Search for the <requestFiltering> section.
  3. Determine the file name extensions and folder names that you will have in the packages on that distribution point. For each extension and folder name that you require, perform the following steps:

    • If it is listed as a fileExtension element, set the value for allowed to true.

      For example, if your package contains a file with an .mdb extension, change the line true to allowed<add fileExtension=".mdb" allowed="false" /> to <add fileExtension=".mdb" allowed="true" />.

      Allow only the file name extensions required for your packages.
    • If it is listed as a <hiddenSegments> element, delete the entry that matches the file name extension or folder name from the file.

      For example, if your package contains a folder with the label of bin, remove the line <add segment=”bin” /> from the file.
  4. Save and close the applicationHost.config file.

See Also


http://technet.microsoft.com

Wednesday, March 27, 2013

Set Up a Home Server


Introduction

Before You Start – Alternatives

Setting up a home server can be a lot of fun and a great learning experience. But, depending on what you want to use it for and how good your connection to the Internet is, a home server may not be the best alternative. If your aim is serving web pages reliably or otherwise delivering information outside your home to friends or customers, it makes more sense to put the server into “The Cloud” – in other words, in a commercial data center. This saves nyou the worry and hassle of keeping it running or dealing with interruptions to your home’s power, cable or DSL service. “Cloud Computing,” or renting just as much of a server as you need on an hourly or monthly basis, is becoming quite popular for web companies or growing businesses, but the rates are inexpensive enough that you should consider it as an alternative to a home server. There are many cloud computing companies, ranging from Amazon Web Services which requires that you learn their command line interface to initiate a new server, to ENKI which offers personal support for getting you up and running. This isn’t the place to go into detail, but you can learn more by Googling “Cloud Computing.”

What you’ll need

To build your own server, you need just a few components, some or all of which you may well have already:
  • A computer
  • A broadband network connection
  • A network router, with Ethernet (CAT5) cable
  • A monitor and keyboard (just for the first few steps)
  • A CD/DVD drive/burner will be handy if you plan to use the server for media.

The computer

A server doesn’t have to be particularly powerful. eBay runs on mega-thousand-dollar Sun computers, and Google uses thousands of machines to power its search. But for personal use, a server needs considerably less horsepower than your average desktop computer. While other computers busy themselves with complex tasks like despeckling photographs and calculating missile trajectories, your home server has a much simpler task: receiving requests for data and then sending that data as requested. Your server won’t use much processing power, especially without a graphical interface to worry about. A machine with 64MB of RAM and a 300MHz processor can make a perfectly good server; with slightly more robust specs, it can handle almost anything you’ll throw at it.
An old machine can be turned into a server with minimal effort. You may already have a perfect machine for the job sitting in your attic. Or a relative or a friend might want to get rid of her older desktop; or you may well be able to pick up a suitable model cheap or free from a swap meet, a classified ad, or online equivalents like freecycle.org and craigslist.org. Alternately, you can buy a new machine to use as your server. Each approach has its advantages.
The reasons you might not want to use an old machine include:
Old hardware can be unreliable. Sometimes replacing bad RAM or putting in a new heatsink will fix the problem, but sometimes a computer just crashes every few hours, regardless of what operating system is installed. Time to donate or recycle it.
Space is an issue. If the old machine is in a big tower case and you are in a small apartment, you might want to get it a new case — or you might want to buy a new server that’s one tenth the size.
You want it quiet. Computers get hot, so fans are installed to keep them cool. Fans are loud, even the ones marketed as “whisper-quiet.” You might not notice that so much in an office setting, but when a server is left running 24 hours a day (as they should be), it becomes rather irritating to live with in close quarters. If you’re going to be sharing a living space with your server, you may want to invest in a fanless machine.
You don’t have an old computer on hand, and you live in a place where finding cheap, used hardware is difficult or expensive.
If any of the above apply, you can skip to the section titled Buying a server.

Repurposing a used computer

If you go the way of turning an older machine into a server, congratulations. If it’s a particularly geriatric model, you might have a little work ahead of you to get it ready for its new assignment. Upgrading a couple of its parts will make it a powerhouse for years to come. You can find plenty of support, if you have questions about what connector goes where, on hardware-nerd sites like tomshardware.com andarstechnica.com. Or, if messing with wires and chips is too daunting, your local computer shop should do it for a minimal fee.

Architecture

What sort of computer you use — i386, PowerPC, Gameboy — matters surprisingly little. Linux and BSD, the preferable server operating systems, run on just about any architecture you care to install them on. The official list of chips on which Debian can run includes Intel x86, Motorola 680xx, Sun Sparc, Alpha, PowerPC, ARM, MIPS, HP PA, Intel 64-bit, and S/390 processors, with more in the testing phase. That covers the vast majority of consumer computers ever made. Buy a notebook (the paper kind) and label it My Server. Write down all the model numbers and details of the hardware you set up.

Memory

RAM is cheap these days, and more is generally better.

Storage

The hard drive is the heart of the server. If everything else dies, you can pull out the hard drive and put it in another (comparable) machine, and pick up right where you left off. Depending on how many slots your computer is built with, you might want to have one hard drive or a few. Bigger is better.
Hard drives continuously drop in price. Start fresh with a new one. If you’re disposing of an old drive and replacing it with a new one, don’t forget to securely delete any private information before you put it in the trash.
The innards of a hard drive spin around thousands of times per second, so it’s very likely that the hard drive will be the first component of your server to fail, though you can generally count on a new drive for a few good years at least. Proper backup procedures are crucial; for now, if you have room in your server and in your budget, you may want to slot in a second or even third hard drive. Keeping secondary copies of data in another place — even if that’s just a second drive right next to the first one — is the way to safeguard your data against hard drive failure.

Cooling

Since the server’s going to be running all the time, you need to make sure it doesn’t overheat. The machine you have might already be fine in that department, or it might not. If it crashes unexpectedly, or exhibits weird, unpredictable behavior, it may be getting too hot. There’s software you can install to monitor the machine’s temperature as it runs, and even set it up to e-mail you automatically if it’s creeping into the danger zone on a hot day.
You can splurge on a wide variety of methods to keep the CPU and power supply cool, involving air, water, liquid nitrogen, and so on. You also may want to look into underclocking your processor. That makes it run slower (which is fine for a server, remember) but also cooler. If you’re handy with solder, there are dozens of underclocking tutorials online for your particular chip type. Generally, though, setting up good airflow through the box is sufficient for most home servers, with some quality fans sensibly arranged to pull air in at one end of the case, direct it over the hot components, and push it out the other. Larger fans tend to be quieter than smaller models, all else being equal. If you’re living with the server, you will want quiet fans, the quietest you can get.

Network

The server’s also going to need an Ethernet card (also known as a network interface card, or NIC), and one that works with your chosen operating system. You can’t go wrong with most cards (especially older models), but you’ll definitely want to check the model number on linux-drivers.org or elsewhere on the web before buying a new one. Big brands like 3Com and D-Link are generally a good, reliable bet.

Buying a server

Alternately, you could buy a server. There are plenty of up-to-date guides on the web. You can use a standard desktop computers, which contain powerful, expensive, and hot Intel and AMD-brand chips. That’s fine, but brands like Shuttle or Biostar, built on the mini-ITX or nano-ITX specification are smaller, cheaper, and cooler. These can fit in cigar boxes and run silently without fans, on low power. Complete systems using these chipsets can be bought from a variety of specialty retailers, including idotpc.com and mini-itx.com. You shouldn’t have to spend more than a couple of hundred dollars for a serviceable system.

The Connection

Apart from that, any sort of connection will do. Super speed is not important (unless you’re planning to stream videos to dozens of users). If you have a connection already (probably you do) you can continue to use it as normal. Just keep your server connected to the router. A static IP is not necessary, nor is a business-class connection.
Your choice of providers will vary depending on your area. If you have a choice, pick a provider that offers good, reliable speeds and makes its customers happy. Ask around, or search the web for the phrase “[provider] sucks” if you want to hear the worst. Some providers have very restrictive policies and prefer their users not to do things like build servers; others, like the excellent sonic.net, are thrilled to have adventurous users. The choice between cable, DSL, fiber, satellite, and so on is less important; after trying an assortment, you won’t notice a significant difference unless you’re streaming video or high-quality audio.

The Router

Get a reliable router. It can be wireless, if you want to connect other computers to it wirelessly, but plan on using a real old-fashioned cable between it and the server. A router is a pretty standard commodity these days; some may have extra features, but it’s the basics, not the extras, that count. Again, looking at what other shoppers have liked, on a site like newegg.com, can be an excellent guideline.

The Monitor and Keyboard

If you have an old spare desktop, you may have a spare monitor and keyboard to go with it. Or you can use your current computer, if you’re not using a laptop, and willing to switch back and forth while you get things set up. You’ll only need these until you get your server up and running. A monitor and keyboard are very handy to have tucked away somewhere for future debugging and upgrading of the server, though.

Power

If you live in an area prone to power surges, rolling brownouts, or the like, or even if you don’t, some sort of intermediary between your machine and the AC socket is a good idea. This can be as simple as a $10 surge suppressor (not just an extension cord) or an elaborate power conditioner with hours of battery backup.

Everything in Its Place

After your box is upgraded, you’ll need to find a home for it. You’ll want to keep a few practical considerations in mind.
  • Don’t place it next to a heater, or in a sunbeam. Don’t place it by an open window. Dust is a server’s enemy too, so don’t keep it under the bed.
  • Don’t let people trip over the cords, or let pets chew on them.
  • With proper attention to cooling, your server should be quite quiet, but some people are sensitive to even the faintest hum. Especially if your server is not the noiseless variety, you might want it in a less-trafficked area. The website Silent PC Review has advice and hardware recommendations for avoiding the noise.
  • Putting it in a little closet is good, as long as there’s enough airflow that the thing won’t overheat. Make sure to place it on a hard surface so as not to block the air intakes, leave a few inches of space around it on all sides, and don’t pile stuff on top of it.
  • Theft is another concern: keeping a shiny server right by the front door might not be the best idea.
  • A lot of your placement concerns may be dictated by your internet connection, since the server needs to be within a cord’s reach of that. If you use a wireless router to share the connection with the rest of the house, that ought to be centrally located, and the server plugged directly into it, wherever it is.
  • It’ll also need to be plugged into an electric outlet.
  • If you’re going to be doing stuff like ripping CDs with the server, you’ll want it conveniently placed for feeding discs in.

The Operating System

There are many, many options for an open source operating system. You can install Fedora, Ubuntu, FreeBSD, Gentoo, and the list goes on and on.
Another option is to install the open source home server from Amahi. This will do alot of the ‘heavy lifting’ to get you up and running, including installing and configuring apache, MySQL, a Ruby on Rails deployment environment, file sharing, a VPN and a range of share web applications. You’ll find alot of useful information on this topic at the Amahi website.

Suggested reading

What can you do with that server? Here are some projects:

What is a server?


A server is a computer system who's primary purpose (or even sole purpose) is to host files and/or applications and provide access to them on a network.
Server can share resources with various clients. 

Servers are often depended upon to provide services which are crucial to an organization. Therefore server-specific hardware is available which is engineered to be as robust as possible. 

It is not always necessary to build a server with this level of reliability, and so some servers are built using desktop parts. These machines can still be referred to as a server as the term refers to the systems primary purpose rather than its construction.
The counterpart to a server is a "client." Any computer which is accessing the server is said to be that servers client. Many servers are designed to handle very large numbers of clients, these servers must be very powerful and must have a very fast connection to their network in order to be able to do this reliably. 

The word "server" can also refer to a specific application, one which "serves" data or services to other applications. In this case, it is possible for the server and the client to both reside on the same system.

A server is any combination of hardware or software designed to provide services to clients. When used alone, the term typically refers to a computer which may be running a server operating system, but is commonly used to refer to any software or dedicated hardware capable of providing services. Another way of saying it: a server in a network is a central computer that is accessed by other networked computers which are operated by individual users. A server is maintained by a network technician, but in general it functions on its own without a human operator. 

A server is a host, it is used to host a network over a WAN, LAN, and any other connection types. with a network you can transmit files between computers and onto a system stored within the server. It is used to help computers to communicate with minimal collisions on the network route. A server is a computer with more storage space to hold all of the files that are used on each of the computers i.e. each computer that is used will back up the information or transmit it to the server to be stored securely and or backed up at the end of a period of time.


wiki

What are the functions of a computer?


The main and also basic function of a computer is to run programs. The programs they run can help to improve humans' every day lives.
But, there are four basic functions of a Computer. They are:
1. INPUT- you input data i.e. you provide data; set of instuctions. You input data through input devices which are keyboard, mouse, scanner,etc
2. PROCESSING- the computer processes it i.e. it manipulates the data which is done by the C.P.U
3. OUTPUT- After processing the data the computer displays the result , it gives an output. Output devices are the monitor, in the case of visual output. speakers, in the case of audio output, printers, etc
4. STORAGE- You can save your data for future use in the CPU itself which is stored in the computer's ROM. There are several other storage devices also like removeable disks , CDs, etc

What is Computer Science?




  • Computer science is a discipline that spans theory and practice. It requires thinking both in abstract terms and in concrete terms. The practical side of computing can be seen everywhere. Nowadays, practically everyone is a computer user, and many people are even computer programmers. Getting computers to do what you want them to do requires intensive hands-on experience. But computer science can be seen on a higher level, as a science of problem solving. Computer scientists must be adept at modeling and analyzing problems. They must also be able to design solutions and verify that they are correct. Problem solving requires precision, creativity, and careful reasoning.Computer science also has strong connections to other disciplines. Many problems in science, engineering, health care, business, and other areas can be solved effectively with computers, but finding a solution requires both computer science expertise and knowledge of the particular application domain. Thus, computer scientists often become proficient in other subjects.
    Finally, computer science has a wide range of specialties. These include computer architecture, software systems, graphics, artifical intelligence, computational science, and software engineering. Drawing from a common core of computer science knowledge, each specialty area focuses on particular challenges.
  • Computer Science is practiced by mathematicians, scientists and engineers. Mathematics, the origins of Computer Science, provides reason and logic. Science provides the methodology for learning and refinement. Engineering provides the techniques for building hardware and software.Finally, and most importantly, computer scientists are computer scientists because it is fun. (Not to mention lucrative career opportunities!)
  • Another definition from http://www.csab.org/comp_sci_profession.htmlComputer Science: The Profession
    Computer science is a discipline that involves the understanding and design of computers and computational processes. In its most general form it is concerned with the understanding of information transfer and transformation. Particular interest is placed on making processes efficient and endowing them with some form of intelligence. The discipline ranges from theoretical studies of algorithms to practical problems of implementation in terms of computational hardware and software.

    A central focus is on processes for handling and manipulating information. Thus, the discipline spans both advancing the fundamental understanding of algorithms and information processes in general as well as the practical design of efficient reliable software and hardware to meet given specifications. Computer science is a young discipline that is evolving rapidly from its beginnings in the 1940's. As such it includes theoretical studies, experimental methods, and engineering design all in one discipline. This differs radically from most physical sciences that separate the understanding and advancement of the science from the applications of the science in fields of engineering design and implementation. In computer science there is an inherent intermingling of the theoretical concepts of computability and algorithmic efficiency with the modern practical advancements in electronics that continue to stimulate advances in the discipline. It is this close interaction of the theoretical and design aspects of the field that binds them together into a single discipline.
    Because of the rapid evolution it is difficult to provide a complete list of computer science areas. Yet it is clear that some of the crucial areas are theory, algorithms and data structures, programming methodology and languages, and computer elements and architecture. Other areas include software engineering, artificial intelligence, computer networking and communication, database systems, parallel computation, distributed computation, computer-human interaction, computer graphics, operating systems, and numerical and symbolic computation.
    A professional computer scientist must have a firm foundation in the crucial areas of the field and will most likely have an in-depth knowledge in one or more of the other areas of the discipline, depending upon the person's particular area of practice. Thus, a well educated computer scientist should be able to apply the fundamental concepts and techniques of computation, algorithms, and computer design to a specific design problem. The work includes detailing of specifications, analysis of the problem, and provides a design that functions as desired, has satisfactory performance, is reliable and maintainable, and meets desired cost criteria. Clearly, the computer scientist must not only have sufficient training in the computer science areas to be able to accomplish such tasks, but must also have a firm understanding in areas of mathematics and science, as well as a broad education in liberal studies to provide a basis for understanding the societal implications of the work being performed.
  • From Mississippi State UniversityComputer Science is the study of principles, applications, and technologies of computing and computers. It involves the study of data and data structures and the algorithms to process these structures; of principles of computer architecture-both hardware and software; of problem-solving and design methodologies; of computer-related topics such as numerical analysis, operations research, and artificial intelligence; and of language design, structure, and translation technique. Computer Science provides a foundation of knowledge for students with career objectives in a wide range of computing and computer-related professions.
  • From http://www2.cs.unb.ca/ Problem solving.The study of efficient and effective software development techniques.
    Team work and communication skills.
    An interest in applying technology to problems in a wide variety of disciplines.
  • From the University of Missouri - Rolla http://www.cs.umr.edu/csdept/career/what_is_cs.htmlComputer Science is concerned with information in much the same sense that physics is concerned with energy; it is devoted to the representation, storage, manipulation and presentation of information.
    Computer Science is concerned with "the study of symbol-manipulating machines, with communication between man and machine and with the application of these machines".
    Major areas of Computer Science include:
    1. Operating Systems--concerned with the development and structure of complex programs which facilitate man-machine communications.
    2. Computational Science--the analysis of numerical methods for solving mathematical problems with a computer.
    3. Programming Languages--the study of the design and properties of languages by which humans communicate with computers.
    4. Architecture--the study and use of mathematical logic to design electronic circuits.
    5. Intelligent Systems--concerned with means by which computers may perform tasks which might be characterized as "intelligent" if performed by humans.
    6. Automata Theory--an abstract study of computers and their capabilities.
    7. Information Storage and Retrieval--the study of methods for storing a vast amount of data in a computer and methods for searching and retrieving this data.
    8. Software Engineering--the study of tools and techniques for software design, development, testing and maintenance.
  • Another way to view any science is to look at the methods used within that science. In some sense these methods are similar in many (most?) sciences, but they can take on different characteristics in each discipline. Four important methods used in the study of computer science are:
    • invention --- formulation of new algorithmic and new architectural paradigms
    • design --- software engineering uses design principles to build complex systems to solve computational problems
    • analysis --- certainly a major focus within computer science is the analysis and evaluation of software, algorithms and architecture.
    • experimentation --- use of experiments to reveal computing principles is an important method of scientific investigation within computer science.