Following are the steps:
Step 1: Make sure your computer is up to snuff. It doesn't take a lot to build a print server. All you need is a machine with a 386 processor or faster, 8 megs of RAM, a parallel port and a floppy drive.
Step 2: Install an ethernet network adapter card. If the machine doesn't already have an ethernet port, you'll need to install one. It doesn't have to be up-to-date either, an old 10 Mbps PCI card ought to do the trick.
Step 3: Install winzip and winimage. You'll need these programs to unpack the printer server software. Visit the Winzip and Winimage websites and read how to download and install it (see Resources below for links).
Step 4: Download the print server software. We'll be using a free print server from Pigtail.net. See the link below in Resources to download.
Step 5: Download a network card driver. You'll need a file called modules.lrp. There are many different versions of it, however, so follow the link for a modules.lrp list in the Resources section.
Step 6: Open winimage. If you installed it to the default directory, you'll need to click "Run" and then type C:\winimage\winimage.exe.
Step 7: Create a disk image. Drag and drop the printsrv image into the winimage window. This is the file you downloaded in Step 3. Next, drag and drop the modules.lrp file in.
Step 8: Save the image onto a disk. Insert a blank disk into your A drive and click Disk | Write.
Step 9: Connect your printer and power up. Connect the print server to the network. Connect a printer to the print server with a parallel printer cable, insert the disk you just wrote and boot it up. It will beep 3 times to indicate that it is ready.
Step 10: Set up client printers. In XP, click Start | Control Panel | Printers and Faxes | Add a printer | Local Printer. Uncheck "Auto Detect PnP." Click "Create new port" and then "Standard TCP/IP port." Type in the IP address as 192.168.1.252, the port name as PrintSrv and under Custom | Settings | Raw | Port, type in 9100.
Tips & Warnings
* Some printers, such as the Brother 2070N and the Dell 1710N, are able to act as a print server.
* If your network is not on 192.168.1.x, simply replace etc.lrp from the list in the resources.
* This print server does not support USB printers.
Source: ehow.com/how_2034850_build-server-computer.html
AutoVirt, the emerging leader in fully automated online data migration solutions for mid-range Windows environments (www.autovirt.com). (PRNewsFoto/AutoVirt, Inc.)
Will Highlight AutoMove(TM) Automated Data Migration, AutoClone(TM) Lightening Fast Data Replication, and AutoMap(TM) Network Discovery and Mapping
NASHUA, N.H., May 18 /PRNewswire/ --
When: Wednesday, May 20, from 10:00 a.m. - 6:00 p.m. EDT
(Logo: http://www.newscom.com/cgi-bin/prnh/20081014/NETU030LOGO )
Where: To learn more, register and attend this live virtual event, please visit: https://www.techwebonlineevents.com/ars/eventregistration.do?mode=eventreg&F=1001561&K=MAA2.
What: AutoVirt will feature its industry leading data migration and replication solutions for Windows environments, including:
* AutoMove(TM) -- Automated File Server Virtualization Software: By leveraging advanced file virtualization technology, AutoMove, the industry's first continuous data migration (CDM) solution, allows IT management to fully-automate the data migration and management function across their entire Windows environment. By automating this process, businesses benefit from consistently optimized storage resources and the resulting dramatic decrease in capital and operational expenditures (CapEx and OpEx).
* AutoClone(TM) -- Fast and Efficient Windows Data Replication: AutoClone helps IT Management to dramatically increase the speed (up to 20 times faster than competitors) and efficiency of their Windows data replications, in order to ensure resource optimization, data protection, consistency and availability, as well as disaster recovery (DR) and business continuity.
* AutoMap(TM) -- Network Discovery and Mapping Tool: AutoMap helps IT Management discover under and over utilized Windows file server and network attached storage (NAS) resources, in physical, virtualized and mixed environments. Once identified, they are able to fine-tune these assets and defer additional server and NAS purchases.
Source:http://news.prnewswire.com/ViewContent.aspx?ACCT=109&STORY=/www/story/05-18-2009/0005028134&EDATE=
Microsoft has added many features to
Windows Server 2008 R2, and once you install the roles and features to add these modular goodies to your implementation, there are many impressive new things you can do. In this post, I am going to look at a new feature that works for Windows Server 2008 R2
File Servers called File Classification Infrastructure.
To use the classification features, you will need to
install File Server Role and the File Server Resource Manager feature(s) associated with it. To install the File Server Role, complete the following steps:
1. Open the Server Manager.
2. Scroll down to section 3, Customize This Server.
3. Click Add Roles to add server roles.
4. Select the File Services Role and complete the roles wizard.
Once the needed roles are installed, the
File Server Resource Manager (FSRM) console can be launched by selecting it from the Administrative Tools group or by entering fsrm.msc in the search box on the Start menu.
Why classify data?
Classifying data can help make data more accessible (or less accessible) to the users in your environment who need it. For example, suppose the Human Resources department created a folder on the file server within their department called Litigation. In this folder they place files that are needed for any litigation the company is associated with. The permissions on the folder are configured so that HR employees can edit the contents of the folder and add documents. Senior management can read the documents in the litigation folder, and the HR manager can remove documents that are no longer needed.
The question is, how is it determined that a document is no longer needed and how do we apply these criteria to existing files in such a way that minimizes user interaction with them? The new classification feature in Windows Server 2008 R2 makes it possible to automatically assign classification information to files on file servers and apply policy to them based on that information.
Classification in
Windows Server 2008 R2 consists of several elements: properties, rules, and a policy segment including reporting and file management. Properties are the fields that you wish to assign a value for, and the rules are the criteria that set these values. There are other methods of classification available as well, including applications and scripts. More detailed examination of the methods of configuring the File Classification Infrastructure will follow in a future post.
To expire files, consider moving the files that meet a set of conditions, perhaps the last modified date greater than 30 days, to a different folder that an administrator can manually clean up at his or her leisure. Or you can create another rule, using a script, that can purge on a schedule, configured by the choice of the administrator or IT staff.
Source: http://blogs.techrepublic.com.com/networking/?p=1441
Windows Server 2008 has been out for a while and has proven to be a stable operating system. Now that Microsoft has released the first "real" service pack (SP2), more companies are looking at the possibility of upgrading to Windows Server 2008. Although the coexistence of Windows Server 2008 and Windows 2003 shouldn't pose a problem, the actual server migration process can be a bit tricky. In this article, I want to talk about some of the issues that you may encounter when migrating file servers.
The file server migration process can be deceptively simple. In fact, Microsoft offers a free utility to assist you with the migration process. Even so, there is usually a lot more to performing a migration than just running a migration utility.
Hardware considerations
One of the first things to consider is whether or not you will be reusing your existing file server hardware. Keep in mind that if you deploy new server hardware, then the migration process will likely be easier -- especially if you are using the Windows Distributed File System (DFS) on your current file servers. One of the primary advantages to using new hardware is that you can leave your existing server in its current state. That way, if something goes wrong during the migration process, you can still fall back on your old server.
If you choose to reuse your existing hardware, it's important to carefully plan the operating system upgrade. This is especially true if you are using DFS or a clustering solution.
How long will the migration take?
Another major consideration is the amount of time it takes to complete the file server migration process. For instance, suppose you are not using DFS, and you want to use new hardware to host the new file server. In that situation, you can install and configure Windows Server 2008 on the new server without disrupting the users.
The File Server Migration Toolkit
Microsoft has created a free download called the File Server Migration Toolkit that you can use to get around the UNC path issue for migrations to Windows Server 2003 or 2008.
Full detail available here: http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1353653,00.html
A
wireless print server allows one or two printers to be conveniently shared across a WiFi network. Wireless print servers for home networks generally are available in both 802.11b and 802.11g varieties.
Wireless print servers offer the following advantages: * Allows printers to be conveniently located anywhere within wireless network range, not tied to the location of computers
* Does not require a computer be always turned on in order to print
* Does not require a computer to manage all print jobs, that can bog down its performance
* Allows administrators to change computer names and other settings without having to re-configure the network printing settings.
A wireless
print server must be connected to printers by a network cable, normally USB 1.1 or USB 2.0. The print server itself can connect to a wireless router over WiFi, or it can be joined using an Ethernet cable.
Most print server products include setup software on a CD-ROM that must be installed on one computer to complete the initial configuration of the device. As with network adapters, wireless print servers must be configured with the correct network name (SSID) and encryption settings. Additionally, a
wireless print server requires client software be installed on each computer needing to use a printer.
The Linksys WPS54G 802.11g USB wireless print server is shown. Print servers are very compact devices that include a built-in wireless antenna and LED lights to indicate status.
Source: compnetworking.about.com/
Below is a list of the what you need to enable on
Windows Server 2008 for SCCM 2007 to pass the pre-requisites check and work.
Role: Web Server (IIS). This will add Windows Process Activation Service automatically. Under Security, add Windows Authentication and URL Authorization Under Management Tools, enable IIS 6 Management Compatibility Application Development, add ASP Make sure Anonymous Authentication and Windows Authentication is enabled for the default web site Make sure the Allow for All Users authorization rule is set under the default web site.
You also need to enable the BITS Server Extensions features, which will enable other IIS role services. You need to download and install WebDAV. Once installed, you need to enable and configure it. You must set your configuration as shown here.
Specifically you need to set: Allow property queries with infinite depth to true Allow Custom Properties to false Allow anonymous property queries to true Create an authoring rule for All users to give read access to all content
You should now pass SCCM 2007 prerequisite check, as shown here.
Below is a dump of all the roles and features that are enabled on my SCCM box. Note I have some extras, as I'm running a SCCM Preboot Execution Environment Boot point, so I also need WDS installed. ----- Roles ----- [X]
File Services [X]
File Server [FS-FileServer] [X] Web Server (IIS) [Web-Server] [X] Web Server [Web-WebServer] [X] Common HTTP Features [Web-Common-Http] [X] Static Content [Web-Static-Content] [X] Default Document [Web-Default-Doc] [X] Directory Browsing [Web-Dir-Browsing] [X] HTTP Errors [Web-Http-Errors] [X] HTTP Redirection [Web-Http-Redirect] [X] Application Development [Web-App-Dev] [X] ASP.NET [Web-Asp-Net] [X] .NET Extensibility [Web-Net-Ext] [X] ASP [Web-ASP] [X] ISAPI Extensions [Web-ISAPI-Ext] [X] ISAPI Filters [Web-ISAPI-Filter] [X] Health and Diagnostics [Web-Health] [X] HTTP Logging [Web-Http-Logging] [X] Logging Tools [Web-Log-Libraries] [X] Request Monitor [Web-Request-Monitor] [X] Tracing [Web-Http-Tracing] [X] Security [Web-Security] [X] Basic Authentication [Web-Basic-Auth] [X] Windows Authentication [Web-Windows-Auth] [X] URL Authorization [Web-Url-Auth] [X] Request Filtering [Web-Filtering] [X] Performance [Web-Performance] [X] Static Content Compression [Web-Stat-Compression] [X] Management Tools [Web-Mgmt-Tools] [X] IIS Management Console [Web-Mgmt-Console] [X] IIS 6 Management Compatibility [Web-Mgmt-Compat] [X] IIS 6 Metabase Compatibility [Web-Metabase] [X] IIS 6 WMI Compatibility [Web-WMI] [X] IIS 6 Scripting Tools [Web-Lgcy-Scripting] [X] IIS 6 Management Console [Web-Lgcy-Mgmt-Console] [X]
Windows Deployment Services [WDS] [X] Deployment Server [WDS-Deployment] [X] Transport Server [WDS-Transport] ----- Features ----- [X] .NET Framework 3.0 Features [NET-Framework] [X] .NET Framework 3.0 [NET-Framework-Core] [X] XPS Viewer [NET-XPS-Viewer] [X] BITS Server Extensions [BITS] [X] Remote Differential Compression [RDC] [X] Feature Administration Tools [RSAT-Feature-Tools] [X] BITS Server Extensions Tools [RSAT-Bits-Server] [X] Windows Internal Database [Windows-Internal-DB] [X] Windows PowerShell [PowerShell] [X] Windows Process Activation Service [WAS] [X] Process Model [WAS-Process-Model] [X] .NET Environment [WAS-NET-Environment] [X] Configuration APIs [WAS-Config-APIs]
Source: http://windowsitpro.com/mobile/pda/Article.cfm?ArticleID=101988&FAQ=1
