It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.
You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:
You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.
If you want to change the port for a particular connection on the Terminal Server, then follow these steps:
You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.
After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:
You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.
A print server is basically a computer that is connected with the printers or print devices. It is composed of an operating system like Windows XP, Vista and client computers. Client computers send requests to the print server and it fulfills those requests. It processes these requests on the first come first serve basis. Now let us discuss about the wireless print server. Due to the wireless print server, one or two printers can be easily shared across a WiFi network. These are available in both 802.11b and 802.11g varieties for home networks. Advantages of wireless print servers are as follows:
It permits that printers can be positioned anywhere, but within the network range. For performing a print job, it is not required that the computer always be turned on. It has the facility to transfer the work of a printer to another one present in the network. This feature also increases the performance of the printers. Administrators can alter the computer names and other settings, without assembling the network printing settings.
USB 1.1 or USB 2.0 is normally used for connecting the wireless print server with the printers. The print server itself can be linked with a wireless router over WiFi. For completing the initial configuration of the device, you have to install the setup software on one computer. This software is present on the CD-ROM, which is included with the print server products. Like network adapters, wireless print servers should be configured with the correct network name and encryption settings. A client software should be installed on each computer demanding the use of a printer.
This post provides print server support for Microsoft windows Vista operating system and provide steps by steps solution to fix multifunction print server
The Minolta Di450 all-in-one machine is meant for high-capacity printing applications such as printing multiple documents with many pages in rapid succession for a home or office computer network. If you want all of the computers on your network to be able to access the Minolta printer individually, you can set up a print server by using the built-in networking features of the Microsoft Windows Vista operating system.
Insert the software installation disc that came with the Minolta Di450 printer into the computer on your network that is closest to the router. Follow the instructions that will pop up on the computer screen to install the Minolta printer software.
Take an Ethernet cable and connect one end into the Ethernet port on the back of the Minolta Di450 printer. Connect the other end into an open Ethernet port on the back of your network's router.
Open the "Start" menu on the computer where you installed the Minolta software. Click on the icon labeled "Control Panel." Scroll through the options and locate the icon labeled as "Network and Sharing Center." Double click the icon to bring up a new window. Click on the "View Computers and Devices" link at the left side of the window.
Click on the blue button labeled "Add A Printer" at the top of the window. Click on the "Add a Network Printer" button, then click on the "Next" button at the bottom of the window. Wait for the list of available printers to appear on the menu screen. Click on the Minolta printer, then click on "Next." Click "OK" to finish the process.
Close the "Network and Sharing Center" window. Access the other computers on the network that will need to use the Minolta printer and repeat the process of adding the printer in the "Network and Sharing Center" menu.
The Minolta Di450 all-in-one machine is meant for high-capacity printing applications such as printing multiple documents with many pages in rapid succession for a home or office computer network. If you want all of the computers on your network to be able to access the Minolta printer individually, you can set up a print server by using the built-in networking features of the Microsoft Windows Vista operating system.
Insert the software installation disc that came with the Minolta Di450 printer into the computer on your network that is closest to the router. Follow the instructions that will pop up on the computer screen to install the Minolta printer software.
Take an Ethernet cable and connect one end into the Ethernet port on the back of the Minolta Di450 printer. Connect the other end into an open Ethernet port on the back of your network's router.
Open the "Start" menu on the computer where you installed the Minolta software. Click on the icon labeled "Control Panel." Scroll through the options and locate the icon labeled as "Network and Sharing Center." Double click the icon to bring up a new window. Click on the "View Computers and Devices" link at the left side of the window.
Click on the blue button labeled "Add A Printer" at the top of the window. Click on the "Add a Network Printer" button, then click on the "Next" button at the bottom of the window. Wait for the list of available printers to appear on the menu screen. Click on the Minolta printer, then click on "Next." Click "OK" to finish the process.
Close the "Network and Sharing Center" window. Access the other computers on the network that will need to use the Minolta printer and repeat the process of adding the printer in the "Network and Sharing Center" menu.
This post provides print server support to fix print server problems, If you have problem with your print server listed below you can get troubleshooting via this post.
1) If the printer is printing "garbage" characters, go to step 7b).
2) If there is a Windows error message when printing then, consult Windows Server Support.
3) Try printing from another computer. If this is successful, then there is a problem with your computer configuration, not the print server. Consult the computer and operating system documentation.
4) Turn off the print server, then turn it on. Test whether print server works.
5) Run the print server Setup Wizard. (Start > Programs > NETGEAR Print Server > NETGEAR Print Server Setup Wizard.)
6) For PC users, In the "Network Protocols on this PC" one of the three protocols must read "installed".
7) Click Next in the Wizard. If the print server is on the list found then:
(Retest your printer if you make changes to any of the following.)
7a) Check the print server's IP address. If it is 0.0.0.0, then the printer is not recognized. Unless you have a router, the print server's IP must be on the same segment. To set the IP, click Next until you see the TCP/IP screen. If you have a DHCP server on your network, select Obtain IP Address Automatically. Otherwise, click Fixed IP Address, and Suggest New Values. Click Next and Finish to exit the Wizard.
7b) If the printer does not match the printer driver in the operating system then run the Add Printer Wizard. (As described in the product manuals.)
7c) If the printer driver is PSName_Px, then run the Add Printer Wizard, or change it to the print server port.
7d) Disable the printer's bidirectional feature, if it's turned on.
8) Else, if the print server is not found:
8a) Click Refresh.
8b) Make sure you can access other places from your computer. If you can't, then troubleshoot computer or Internet connectivity.
8c) If you are running a software firewall, disable it, and use the NETGEAR firewall, instead. (It's almost certain to be faster.) This includes the Windows XP firewall — which may have been turned on during Windows upgrade or installation without you being aware of it. See Firewalls that Conflict with NETGEAR Such as Windows XP — unless you know for certain this feature isn't on.
1) If the printer is printing "garbage" characters, go to step 7b).
2) If there is a Windows error message when printing then, consult Windows Server Support.
3) Try printing from another computer. If this is successful, then there is a problem with your computer configuration, not the print server. Consult the computer and operating system documentation.
4) Turn off the print server, then turn it on. Test whether print server works.
5) Run the print server Setup Wizard. (Start > Programs > NETGEAR Print Server > NETGEAR Print Server Setup Wizard.)
6) For PC users, In the "Network Protocols on this PC" one of the three protocols must read "installed".
7) Click Next in the Wizard. If the print server is on the list found then:
(Retest your printer if you make changes to any of the following.)
7a) Check the print server's IP address. If it is 0.0.0.0, then the printer is not recognized. Unless you have a router, the print server's IP must be on the same segment. To set the IP, click Next until you see the TCP/IP screen. If you have a DHCP server on your network, select Obtain IP Address Automatically. Otherwise, click Fixed IP Address, and Suggest New Values. Click Next and Finish to exit the Wizard.
7b) If the printer does not match the printer driver in the operating system then run the Add Printer Wizard. (As described in the product manuals.)
7c) If the printer driver is PSName_Px, then run the Add Printer Wizard, or change it to the print server port.
7d) Disable the printer's bidirectional feature, if it's turned on.
8) Else, if the print server is not found:
8a) Click Refresh.
8b) Make sure you can access other places from your computer. If you can't, then troubleshoot computer or Internet connectivity.
8c) If you are running a software firewall, disable it, and use the NETGEAR firewall, instead. (It's almost certain to be faster.) This includes the Windows XP firewall — which may have been turned on during Windows upgrade or installation without you being aware of it. See Firewalls that Conflict with NETGEAR Such as Windows XP — unless you know for certain this feature isn't on.
One of the most common reasons for setting up a server and computer network is to set the server up as a file server.
Adding the File Server Role
Luckily, Microsoft Windows Server includes an easy to use Wizard to help you set up your server as a file server.
# Go to Start, Control Panel, Administrative Tools, Manage Your Server.
# Click the “Add or Remove a Role” link.
# On the Preliminary Steps screen, click Next.
# Under the Server Role heading, Click File Server and then click Next (Figure 1).
# On the summary screen, review the information and then click Next.
# The Add File Server Role Wizard will start. Click Next.
# Click next when prompted to install additional options. The Wizard will start configuring your server.
# After the configuration is complete, you will be prompted to reboot. Proceed and reboot the server to continue.
Configuring the Server
After the server restarts, you’ll want to set up some file shares and set permissions.
1. Log back into Windows.
2. Go to Start, Control Panel, Administrative Tools, File Server Management (Figure 2).
3. Expand Share Folder Management, Shared Folders, Shares.
4. You should notice a few Shares already exist – these are on all default installations of Windows. Under the Action Menu, select New Share.
5. Once the Share a Folder Wizard starts, click Next.
6. Select a location for the folder share and click Next.
7. Enter the name for your share and a description if you’d like. Click Next.
8. On the Permissions page, select the option you’d like – by default, you may choose to leave all readers with Read access.
9. Click Finish and then Close.
You’ve now shared your first user folder. End users can access this share by going to \\\ where is the name of your computer and is the name you gave the share in step 7 above.
From:http://www.brighthub.com/computing/windows-platform/articles/39793.aspx
Adding the File Server Role
Luckily, Microsoft Windows Server includes an easy to use Wizard to help you set up your server as a file server.
# Go to Start, Control Panel, Administrative Tools, Manage Your Server.
# Click the “Add or Remove a Role” link.
# On the Preliminary Steps screen, click Next.
# Under the Server Role heading, Click File Server and then click Next (Figure 1).
# On the summary screen, review the information and then click Next.
# The Add File Server Role Wizard will start. Click Next.
# Click next when prompted to install additional options. The Wizard will start configuring your server.
# After the configuration is complete, you will be prompted to reboot. Proceed and reboot the server to continue.
Configuring the Server
After the server restarts, you’ll want to set up some file shares and set permissions.
1. Log back into Windows.
2. Go to Start, Control Panel, Administrative Tools, File Server Management (Figure 2).
3. Expand Share Folder Management, Shared Folders, Shares.
4. You should notice a few Shares already exist – these are on all default installations of Windows. Under the Action Menu, select New Share.
5. Once the Share a Folder Wizard starts, click Next.
6. Select a location for the folder share and click Next.
7. Enter the name for your share and a description if you’d like. Click Next.
8. On the Permissions page, select the option you’d like – by default, you may choose to leave all readers with Read access.
9. Click Finish and then Close.
You’ve now shared your first user folder. End users can access this share by going to \\
Kaspersky Lab has released a beta-version of Kaspersky Anti-Virus for Linux File Server 6.0.
Kaspersky Anti-Virus for Linux File Server 6.0 is a solution offering antivirus protection to the vast majority of Linux file servers.
It supersedes two earlier products – Kaspersky Anti-Virus for Linux File Server 5.7 and Kaspersky Anti-Virus for Samba Server 5.5 by combining their functionalities and adding a number of new functionalities.
The architecture of Kaspersky Anti-Virus for Linux File Server 6.0 provides multilayered protection for file systems in Linux/heterogeneous networks, functioning simultaneously on the entire file system level and on the Samba server level.
Kaspersky Anti-Virus for Linux File Server 6.0 supports all modern 32-bit and 64-bit distributions of Linux-family operating systems, including Red Hat, Fedora, SUSE, openSUSE, Debian GNU, and Ubuntu. Another improvement on the previous product versions is the added support of Novell Open Enterprise Server 2 and Novell NSS.
Source:companies.mybroadband.co.za
The folks behind Opera recently announced it has added new technology to the Web browser enabling users to turn their computers into individual servers.
According to the company, users designate the directory they wish to share with their buddies and Opera Unite generates a direct URL to that directory for distribution to others. While sending that URL to a few close friends is unlikely to cause any infringement concerns, it’s easy to imagine mailing lists consisting of hundreds of thousands of potential down loaders waiting for that specific URL.
Along with file swapping, Opera Unite also provides a media player enabling users to listen to their private digital music stash wherever they may be. Other features include “The Lounge” – a self-contained chat service you can run on your computer, and “Fridge,” which gives users a virtual refrigerator for posting notes.
While Opera Unite may be full of whiz-bang whistles and bells, as soon as the company announced the new technology, tech bloggers cited possible security problems as well as local area network (LAN) issues. With internal corporate networks often experiencing congestion problems, it’s easy to speculate as to how those problems might grow if individual computers become Web servers.
But those security concerns are based on how writers think Opera Unite may work, and are not necessarily descriptive of how the technology actually performs in the real world. Plus, when you consider how Internet technology in general often focuses on providing individual users with more power, turning desktop computers into servers is a concept that would eventually have become reality – with or without Opera Unite.
“With sever capability in the browser, Web developers can create Web applications with profound ease,” said Opera CEO Jon von Tetzchner. “Consumers have the flexibility to choose private and efficient ways of sharing information. We believe Opera Unite is one of our most significant innovations yet, because it changes forever the fundamental fabric of the Web.”
Source: pollstar.com/blogs/news/archive/2009/06/17/673678.aspx
According to the company, users designate the directory they wish to share with their buddies and Opera Unite generates a direct URL to that directory for distribution to others. While sending that URL to a few close friends is unlikely to cause any infringement concerns, it’s easy to imagine mailing lists consisting of hundreds of thousands of potential down loaders waiting for that specific URL.
Along with file swapping, Opera Unite also provides a media player enabling users to listen to their private digital music stash wherever they may be. Other features include “The Lounge” – a self-contained chat service you can run on your computer, and “Fridge,” which gives users a virtual refrigerator for posting notes.
While Opera Unite may be full of whiz-bang whistles and bells, as soon as the company announced the new technology, tech bloggers cited possible security problems as well as local area network (LAN) issues. With internal corporate networks often experiencing congestion problems, it’s easy to speculate as to how those problems might grow if individual computers become Web servers.
But those security concerns are based on how writers think Opera Unite may work, and are not necessarily descriptive of how the technology actually performs in the real world. Plus, when you consider how Internet technology in general often focuses on providing individual users with more power, turning desktop computers into servers is a concept that would eventually have become reality – with or without Opera Unite.
“With sever capability in the browser, Web developers can create Web applications with profound ease,” said Opera CEO Jon von Tetzchner. “Consumers have the flexibility to choose private and efficient ways of sharing information. We believe Opera Unite is one of our most significant innovations yet, because it changes forever the fundamental fabric of the Web.”
Source: pollstar.com/blogs/news/archive/2009/06/17/673678.aspx
Many businesses host networked storage on file servers, but as data grows, so does the need for streamlined consolidation and organization. Failure to properly manage this data growth challenge can result in unused capacity, poor availability of files and data, and difficulty in finding shared files. The good news is that network attached storage (NAS) can be a quick, easy and powerful solution to manage file data. A complete discussion of file server options, including scalability Information on how networked attached storage (NAS) devices can optimize file serving A roadmap for future-proofing your file server software and hardware
Through proper choices in file server solutions, businesses can save money on infrastructure, keep networked data highly available, and keep infrastructure highly scalable. Let PCMagCast, a PC Magazine editor, an expert from Hewlett-Packard, and a product manager from Microsoft teach you what the best practices are in consolidating and managing data with file servers.
In this free, 60-minute webcast, you'll find:
Step1: Determine the number of users who will access the server simultaneously. If the answer is 10 or fewer, the file server can be built with very modest hardware. If more than 10 users will need to access the server on a consistent, concurrent basis, consider using a faster computer with more RAM for greater performance.
Step 2: Choose an operating system for the server. This is often a matter of preference or comfort level. Linux or other free Unix-based operating systems will run on modest hardware with high performance if a graphical user interface is not installed.
Step 3: Select a hard disk with the capacity to share your files. The types of files shared will determine the size hard disk you need. If most of the files that will be served are text, word processing files or spreadsheets, a hard disk of 60 or 80 gigabytes will suffice, since these types of files are relatively small. However, if you plan on sharing music, videos, or large database files, choose a disk that has several hundred gigabytes of capacity.
Step 4: Purchase a new or used PC or build your own. Low cost, budget PCs from any of the major retailers will meet the hardware requirements for most small Linux or Windows-based file sharing applications. If using Linux or an older version of Windows for a smaller server, an older spare PC can be used, or you can get one secondhand pretty cheap. The only absolutely necessary requirement for a file server machine must meet is an Ethernet card to connect to your home or office network.
Step 5: Install extra RAM if needed. Smaller file servers will get by with 256 megabytes of RAM, while higher performance computers will need 512 megabytes or more. The more users, the more RAM you'll need.
Step 6: Install the operating system and turn the file sharing capabilities on. If using Linux for a server that will be sharing files with Windows computers, install the Samba server package on the server. If using Windows on the server, turn on file and print sharing via the administrative tools or control panel.
Source: Ehow
Step 2: Choose an operating system for the server. This is often a matter of preference or comfort level. Linux or other free Unix-based operating systems will run on modest hardware with high performance if a graphical user interface is not installed.
Step 3: Select a hard disk with the capacity to share your files. The types of files shared will determine the size hard disk you need. If most of the files that will be served are text, word processing files or spreadsheets, a hard disk of 60 or 80 gigabytes will suffice, since these types of files are relatively small. However, if you plan on sharing music, videos, or large database files, choose a disk that has several hundred gigabytes of capacity.
Step 4: Purchase a new or used PC or build your own. Low cost, budget PCs from any of the major retailers will meet the hardware requirements for most small Linux or Windows-based file sharing applications. If using Linux or an older version of Windows for a smaller server, an older spare PC can be used, or you can get one secondhand pretty cheap. The only absolutely necessary requirement for a file server machine must meet is an Ethernet card to connect to your home or office network.
Step 5: Install extra RAM if needed. Smaller file servers will get by with 256 megabytes of RAM, while higher performance computers will need 512 megabytes or more. The more users, the more RAM you'll need.
Step 6: Install the operating system and turn the file sharing capabilities on. If using Linux for a server that will be sharing files with Windows computers, install the Samba server package on the server. If using Windows on the server, turn on file and print sharing via the administrative tools or control panel.
Source: Ehow
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
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=
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
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/
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.
Source: http://windowsitpro.com/mobile/pda/Article.cfm?ArticleID=101988&FAQ=1
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
Now that you have properly configured the Spooler resource with the necessary resources, you can create all of the print queues for all of the physical printers. You can also use the Clustool utility from the Resource Kit to migrate previously existing printer queues on a server to a clustered server. After that, use the Print Migrate utility to migrate the printer drivers. For best results, avoid having multiple servers configured to communicate directly with the same printer.
1. From one of the nodes or a remote computer that has administrative permissions to the cluster click Start, click Run, type \\VirtualServer where VirtualServer is the name that is specified for the Network Name resource on which the Spooler resource is dependent.
2. Double-click the Printers folder.
3. Double-click Add Printers to open the Add Printer Wizard, and then click Next.
4. Select Create a new port, and then click Next.
Note: TCP/IP ports are the only supported port type on a Windows Clustering. Use the Standard TCP/IP Port option unless the printing clients need RFC-compliant LPR ports. If this is the case, follow these steps:
1. In Control Panel, double-click Add/Remove Programs, and then click Add/Remove Windows Components to start the Windows Components Wizard.
2. Under Components, scroll down and click to select the Other Network File and Print Services check box.
3. Click Details to open the Other Network File and Print Services window, click to select the Print Services for UNIX check box, and then click OK to close the Other Network File and Print Services window.
4. Click Next to continue with the Windows Components Wizard.
When you complete the wizard, the LPR port will be available as a port type. By default, according to RFC 1179, LPR will use only eleven TCP ports.
5. Type the IP address of the network printer that you want to process the print jobs in the Printer Name or IP Address box.
You no longer have to create a locally-defined printer port configuration for each node. In Windows 2000 (and later) the port configuration is stored in the cluster registry and is therefore shared between all cluster nodes, under the following key:
HKEY_Local_Machine\Cluster\Resources\%Spooler GUID%\Parameters\Monitors\
6. Choose the appropriate driver for this printer, and then click Next.
7. Give the printer a unique name on the cluster server.
8. Choose a share name for the printer; this name must also be unique on this cluster. You do not want to have any other printers with the same share name on this cluster, even if they are in a different group and associated with a different Spooler resource.
9. Test the printing for this printer:
After you add all the desired print queues, use Cluster Administrator to move the group that contains the Print Spooler resource to all other nodes. This copies the printer drivers from the \PrinterDrivers folder on the shared disk to the %SystemRoot%\System32\Spool\Drivers\%Spooler GUID%\Drivers folder on that node.
For Detail Info: http://support.microsoft.com/kb/278455
1. From one of the nodes or a remote computer that has administrative permissions to the cluster click Start, click Run, type \\VirtualServer where VirtualServer is the name that is specified for the Network Name resource on which the Spooler resource is dependent.
2. Double-click the Printers folder.
3. Double-click Add Printers to open the Add Printer Wizard, and then click Next.
4. Select Create a new port, and then click Next.
Note: TCP/IP ports are the only supported port type on a Windows Clustering. Use the Standard TCP/IP Port option unless the printing clients need RFC-compliant LPR ports. If this is the case, follow these steps:
1. In Control Panel, double-click Add/Remove Programs, and then click Add/Remove Windows Components to start the Windows Components Wizard.
2. Under Components, scroll down and click to select the Other Network File and Print Services check box.
3. Click Details to open the Other Network File and Print Services window, click to select the Print Services for UNIX check box, and then click OK to close the Other Network File and Print Services window.
4. Click Next to continue with the Windows Components Wizard.
When you complete the wizard, the LPR port will be available as a port type. By default, according to RFC 1179, LPR will use only eleven TCP ports.
5. Type the IP address of the network printer that you want to process the print jobs in the Printer Name or IP Address box.
You no longer have to create a locally-defined printer port configuration for each node. In Windows 2000 (and later) the port configuration is stored in the cluster registry and is therefore shared between all cluster nodes, under the following key:
HKEY_Local_Machine\Cluster\Resources\%Spooler GUID%\Parameters\Monitors\
6. Choose the appropriate driver for this printer, and then click Next.
7. Give the printer a unique name on the cluster server.
8. Choose a share name for the printer; this name must also be unique on this cluster. You do not want to have any other printers with the same share name on this cluster, even if they are in a different group and associated with a different Spooler resource.
9. Test the printing for this printer:
After you add all the desired print queues, use Cluster Administrator to move the group that contains the Print Spooler resource to all other nodes. This copies the printer drivers from the \PrinterDrivers folder on the shared disk to the %SystemRoot%\System32\Spool\Drivers\%Spooler GUID%\Drivers folder on that node.
For Detail Info: http://support.microsoft.com/kb/278455
with Service Pack 1 for Windows Server 2003, a new feature called Access-Based Enumeration (ABE) has been added to how file sharing works on Windows platforms. By installing and enabling ABE on a Windows Server 2003 SP1 or R2 file server, users on Windows XP desktops will only be able to see files and folders if they actually have permission to access them. I recently wrote an article for Windows Networking.com that explains how to implement this feature and lists a few gotchas you need to be aware of.
Trouble is, ABE only works if your network shares are on an ABE-enabled Windows Server 2003 SP1 or R2 machine. What if you allow some of the "power users" in your company to share folders on their own Windows XP desktop computers? In that case, you're out of luck as ABE can't be enabled on XP. With Windows Vista however, this has now changed -- Vista has ABE built right into it, and this means that when a user shares a folder on her machine and other users browse that share over the network, they will only see files and folders that they have permissions to access.
Note however that ABE only works if Vista users share their files or folders from within their user profile. Yes that's right, I said files -- in Vista you can share individual files provided you do so from within your user profile. For example, if user Jane Doe shares the file EndOfQuarterPresentation.ppt from within her Documents folder on her computer desk22.mtit.com, then other users to whom she has granted permissions will be able to view and access this file over the network by using the path \\desk22.mtit.com\Users\JaneDoe\Documents\EndOfQuarterPresentation.ppt.
For Detail visit: http://www.itworld.com/nls_windows_tullochvista060925
Trouble is, ABE only works if your network shares are on an ABE-enabled Windows Server 2003 SP1 or R2 machine. What if you allow some of the "power users" in your company to share folders on their own Windows XP desktop computers? In that case, you're out of luck as ABE can't be enabled on XP. With Windows Vista however, this has now changed -- Vista has ABE built right into it, and this means that when a user shares a folder on her machine and other users browse that share over the network, they will only see files and folders that they have permissions to access.
Note however that ABE only works if Vista users share their files or folders from within their user profile. Yes that's right, I said files -- in Vista you can share individual files provided you do so from within your user profile. For example, if user Jane Doe shares the file EndOfQuarterPresentation.ppt from within her Documents folder on her computer desk22.mtit.com, then other users to whom she has granted permissions will be able to view and access this file over the network by using the path \\desk22.mtit.com\Users\JaneDoe\Documents\EndOfQuarterPresentation.ppt.
For Detail visit: http://www.itworld.com/nls_windows_tullochvista060925
Are you forever doomed to leaving a PC running 24-7 just to share the printer?
Not if you plug a print server into your router, then plug the printer into the server. Then all PCs on your network can tap that inkjet or laser.
This may not sound like a major deal, but trust me: Once you've sampled this kind of setup, you can't go back to old-school printer sharing.
Buy.com has the D-Link DP-301U Printer Server for $19.99 shipped. That's half the usual price and a bargain compared with buying a new, network-compatible printer.
These are new units, not refurbs, and you don't have to deal with any rebates. The DP-301U is compatible with Windows and Mac networks; all you need is a printer that has a USB interface.
Make that a compatible printer. The DP-301U works with most Canon, Epson, HP, and Lexmark models--check D-Link's compatibility list (which to me looks a little out of date--I suspect there are newer printers that will also work) to make sure your model is supported.
Not if you plug a print server into your router, then plug the printer into the server. Then all PCs on your network can tap that inkjet or laser.
This may not sound like a major deal, but trust me: Once you've sampled this kind of setup, you can't go back to old-school printer sharing.
Buy.com has the D-Link DP-301U Printer Server for $19.99 shipped. That's half the usual price and a bargain compared with buying a new, network-compatible printer.
These are new units, not refurbs, and you don't have to deal with any rebates. The DP-301U is compatible with Windows and Mac networks; all you need is a printer that has a USB interface.
Make that a compatible printer. The DP-301U works with most Canon, Epson, HP, and Lexmark models--check D-Link's compatibility list (which to me looks a little out of date--I suspect there are newer printers that will also work) to make sure your model is supported.
Source: CNET
A home file server is, in theory, a great convenience. In reality, setting up, configuring and running a home file server to link multiple personal computers has been a great pain in the neck. Now, manufacturers are putting out dedicated home file servers, but they can be confusing and complicated. You can build one - I promise you won't enjoy building a file server.
We wanted all our music, videos data, pictures, backups and other types of files on one computer so anyone in the house could access them without having to store duplicate and triplicate copies. Like this: I make a photograph and store it on my laptop. My daughter wants to send it to her friend. If we aren't sharing folders within a Windows home network, we have to figure out who has the file, then put the picture on a disk. Then port it over, name it, file it and then use it.
Even worse when we're talking home business - files have to be moved, shared, edited, and reedited. A home file server is a great home technology idea. If it's easy to set up. If users can configure it easily. If it's lean and quiet rather than bulky and buzzy.
A few weeks ago, CyberPower of California jumped into the home technology market with a dedicated home file server called Windows Home Server 100. They claim the product is a high-performance energy saver that makes storage easy and fast.
We wanted all our music, videos data, pictures, backups and other types of files on one computer so anyone in the house could access them without having to store duplicate and triplicate copies. Like this: I make a photograph and store it on my laptop. My daughter wants to send it to her friend. If we aren't sharing folders within a Windows home network, we have to figure out who has the file, then put the picture on a disk. Then port it over, name it, file it and then use it.
Even worse when we're talking home business - files have to be moved, shared, edited, and reedited. A home file server is a great home technology idea. If it's easy to set up. If users can configure it easily. If it's lean and quiet rather than bulky and buzzy.
A few weeks ago, CyberPower of California jumped into the home technology market with a dedicated home file server called Windows Home Server 100. They claim the product is a high-performance energy saver that makes storage easy and fast.
- It's got Intel inside with 2 gig of DDR memory.
- The server has a 500GB SATA-II 3.0Gb/s 16MB Cache 7200RPM hard drive - for those who just got bowled over by the string of numbers, that's a pretty nice hard drive. I'd say it's more storage than you'd ever need, but the way programs expand, who knows? Geeks will tell you you need a terabyte - you can add it for $50.
- The operating system is MS Windows 2003 Home Server - so you needn't learn another system.
- Home Server 100 can automatically backup your computers each evening, a nice plus.
- It appears Home Server is remotely accessible so you can grab home files when you're at work or school. Also nice.
Even though small businesses don't have the budget or the sheer volume of files that some of the larger enterprises do, you still have to protect the data. Smaller shops have their own issues to overcome that are just as difficult and just as important as the big guys.
Most notably, many small businesses will have only one server for file storage. The major issue with this strategy is that all your eggs are in one basket, and you rely on that same basket to serve all of your other office needs. Therefore, it becomes even more important to properly protect this file server from a possible disaster. Since the bandwidth and hardware required for most off-site replication systems is out of the question here, your choices are limited, but there are options available for you.
RAID
Most servers now come with RAID systems already available with whatever disks you get when the server is built. In addition, you can set up very simple RAID systems via Windows and many other common operating systems. By using mirroring via RAID, you can create another copy of the data that can be used for the purposes of disaster recovery (DR) operations, and do so at a low price point. The main drawbacks are that you'll have to configure and manage the RAID systems, and RAID doesn't protect against virus attacks or other real-time damage.
Backup systems
To protect yourself from virus attacks and other threats, you'll want to develop an effective backup strategy. While you can use the NTBackup systems that come with Windows and the backup tools that come with other OSs, you may wish to invest in a third-party backup system. These offer a large number of additional features, especially for scheduling and dealing with open files that NTBackup simply doesn't offer.
You'll also need some form of removable media. For very small shops, this can be a DVD burner, but for most others, this will mean a tape drive of some type. Also remember that you should be removing the tapes from the physical location of the tape device on a regular basis, so that the loss of your office space doesn't destroy the backups too. It is wise to perform full backups on a weekly basis—on a day and time each week when there are the fewest users on the server—and incremental backups nightly. This gives you the ability to recover from data-loss outages.
For midsize offices, you may want to consider local replication. Many replication tools work great in a LAN environment, and also offer many-to-one capabilities. This means that you can keep a copy of all the data on the servers that you have replicated to a single server. That DR server may even be a small network-attached storage device (NAS), which can be economically more feasible for these purposes. Much like RAID, these systems tend to be real-time by default, so you'd either have to utilize backup tape to provide point-in-time copies, or use a third-party snapshot tool for that purpose. These tools often come standard with the NAS devices (yet another reason to investigate that avenue), but keep in mind that snapshots to the same physical location don't get your data off-site.
Source: http://articles.techrepublic.com.com/5100-10878_11-5750072.html
Most notably, many small businesses will have only one server for file storage. The major issue with this strategy is that all your eggs are in one basket, and you rely on that same basket to serve all of your other office needs. Therefore, it becomes even more important to properly protect this file server from a possible disaster. Since the bandwidth and hardware required for most off-site replication systems is out of the question here, your choices are limited, but there are options available for you.
RAID
Most servers now come with RAID systems already available with whatever disks you get when the server is built. In addition, you can set up very simple RAID systems via Windows and many other common operating systems. By using mirroring via RAID, you can create another copy of the data that can be used for the purposes of disaster recovery (DR) operations, and do so at a low price point. The main drawbacks are that you'll have to configure and manage the RAID systems, and RAID doesn't protect against virus attacks or other real-time damage.
Backup systems
To protect yourself from virus attacks and other threats, you'll want to develop an effective backup strategy. While you can use the NTBackup systems that come with Windows and the backup tools that come with other OSs, you may wish to invest in a third-party backup system. These offer a large number of additional features, especially for scheduling and dealing with open files that NTBackup simply doesn't offer.
You'll also need some form of removable media. For very small shops, this can be a DVD burner, but for most others, this will mean a tape drive of some type. Also remember that you should be removing the tapes from the physical location of the tape device on a regular basis, so that the loss of your office space doesn't destroy the backups too. It is wise to perform full backups on a weekly basis—on a day and time each week when there are the fewest users on the server—and incremental backups nightly. This gives you the ability to recover from data-loss outages.
For midsize offices, you may want to consider local replication. Many replication tools work great in a LAN environment, and also offer many-to-one capabilities. This means that you can keep a copy of all the data on the servers that you have replicated to a single server. That DR server may even be a small network-attached storage device (NAS), which can be economically more feasible for these purposes. Much like RAID, these systems tend to be real-time by default, so you'd either have to utilize backup tape to provide point-in-time copies, or use a third-party snapshot tool for that purpose. These tools often come standard with the NAS devices (yet another reason to investigate that avenue), but keep in mind that snapshots to the same physical location don't get your data off-site.
Source: http://articles.techrepublic.com.com/5100-10878_11-5750072.html
In a continuing bid to capture some of the tape-backup market, Microsoft on Wednesday released a beta version of the upgrade to its file-and-application server recovery software, which includes support for a wider range of the company's server products.
The product, System Center Data Protection Manager (DPM) 2006 version 2, builds upon a previous version of DPM released last year that marked the company's first move into the data-protection software market.
Version 2 employs a patent-pending technology that constantly monitors data changes and can recover the data with zero loss, Microsoft said. During recovery, the new version can also draw data from tape, a new capability, as well as from disks, Microsoft said.
DPM version 2 now supports Microsoft's Exchange Server, SQL Server and Office SharePoint Portal Server, plus the already-supported Windows 2000 and Windows 2003 servers.
DPM is a candidate to replace low-end tape products with centralized disk-to-disk backup, the research analyst company Gartner wrote in a November 2005 report.
Gartner wrote that Microsoft is expected to make gains in the field because of the wide use of Windows file servers and typically low use of file-protection software among small- to medium-size businesses.
The product, System Center Data Protection Manager (DPM) 2006 version 2, builds upon a previous version of DPM released last year that marked the company's first move into the data-protection software market.
Version 2 employs a patent-pending technology that constantly monitors data changes and can recover the data with zero loss, Microsoft said. During recovery, the new version can also draw data from tape, a new capability, as well as from disks, Microsoft said.
DPM version 2 now supports Microsoft's Exchange Server, SQL Server and Office SharePoint Portal Server, plus the already-supported Windows 2000 and Windows 2003 servers.
DPM is a candidate to replace low-end tape products with centralized disk-to-disk backup, the research analyst company Gartner wrote in a November 2005 report.
Gartner wrote that Microsoft is expected to make gains in the field because of the wide use of Windows file servers and typically low use of file-protection software among small- to medium-size businesses.
Download from here
Source: http://www.infoworld.com/article/06/09/27/HNmsfileserverbackup_1.html?BACKUP%20AND%20RECOVERY
Multi-user access to your printer is now simpler than ever. NETGEAR's USB Mini Print Server does away with the hassles of sharing your printer among multiple PCs. Its easy external USB connection links one USB printer to as many as three PCs, so different network users can run multiple print jobs at the same time from anywhere on a home or office network.
The attractive case design looks great in any environment, and its compact size allows you to place it close at hand or out of the way to open up your work area. Easy setup with NETGEAR's Smart Wizard install assistant saves you time and effort so you're up and running in minutes. Since no parallel printer cable is needed, it saves you money too..
Technical Specification:
The attractive case design looks great in any environment, and its compact size allows you to place it close at hand or out of the way to open up your work area. Easy setup with NETGEAR's Smart Wizard install assistant saves you time and effort so you're up and running in minutes. Since no parallel printer cable is needed, it saves you money too..
Technical Specification:
| General | |
| Device Type | Print server |
| Form Factor | External |
| Interface (Bus) Type | USB |
| Width | 34.1 in |
| Depth | 23.2 in |
| Height | 9.6 in |
| Weight | 2.7 oz |
| Networking | |
| Connectivity Technology | Wired |
| Cabling Type | Ethernet 10Base-T, Ethernet 100Base-TX |
| Data Link Protocol | Ethernet, Fast Ethernet |
| Data Transfer Rate | 100 Mbps |
| Network / Transport Protocol | TCP/IP |
| Status Indicators | Link activity, power, alert |
| Features | DHCP support |
| Processor / Memory | |
| RAM | 4 MB |
| Flash Memory | 1 MB |
| Expansion / Connectivity | |
| Interfaces | 1 x network - Ethernet 10Base-T/100Base-TX - RJ-45 |
| Connections | 1 x USB |
| Miscellaneous | |
| Cables Included | 1 x USB cable ( external ) - 5 ft |
| Power | |
| Power Device | Power adapter - external |
| Software / System Requirements | |
| Software Included | Drivers & Utilities |
| OS Required | Microsoft Windows 98SE/2000/ME/XP |
| Manufacturer Warranty | |
| Service & Support | 1 year warranty |
| Service & Support Details | Limited warranty - 1 year |
| Environmental Parameters | |
| Min Operating Temperature | 32 °F |
| Max Operating Temperature | 104 °F |
| Humidity Range Operating | 5 - 95% |
| Universal Product Identifiers | |
| Part Numbers | PS121, PS121NA |
| UPC | 0606449034684 |
Following are the steps to install a File Server on windows server 2003:-
1) First step you Open the start menu and then click administrator and after that configure the server.
2) After that click next
3) Again next.
4) Then click file server in the server role box and then click next, on the file server disk quotas page configure any quotas you need to disk space usage on the server and then click Next. after that on the file server indexing service page you need to click indexing configuration that appropriate for you server and then click Next.
5) And choose the next and after it finish.
6) The share folder wizard starts and then clicks.
7) Click the Browse items and then OK.
8) And then Next.
9) You can type the share name for the folder that you want to share , and then click OK.
10) Click Next.
11) Click the one of the basic permission for the folder, after that finish.
How to Manually Install a File Server on windows server 2003:-
1) Click start and then click windows explorer.
2) That you want to share, Right click the folder and then click sharing and security.
3) Click the share this folder .and then accept default name for the share.
4) configure the number of users who can connect and you configure permission for this folder, after that Ok.
5) Windows explorer windows to indicate that the folder is beginning shared.
1) First step you Open the start menu and then click administrator and after that configure the server.
2) After that click next
3) Again next.
4) Then click file server in the server role box and then click next, on the file server disk quotas page configure any quotas you need to disk space usage on the server and then click Next. after that on the file server indexing service page you need to click indexing configuration that appropriate for you server and then click Next.
5) And choose the next and after it finish.
6) The share folder wizard starts and then clicks.
7) Click the Browse items and then OK.
8) And then Next.
9) You can type the share name for the folder that you want to share , and then click OK.
10) Click Next.
11) Click the one of the basic permission for the folder, after that finish.
How to Manually Install a File Server on windows server 2003:-
1) Click start and then click windows explorer.
2) That you want to share, Right click the folder and then click sharing and security.
3) Click the share this folder .and then accept default name for the share.
4) configure the number of users who can connect and you configure permission for this folder, after that Ok.
5) Windows explorer windows to indicate that the folder is beginning shared.
PS1126 for HP Output Devices Offers Protection of Investment With Integrated Future Technologies.
The German network specialist SEH has integrated future technologies into its new PS1126 interface card for HP printers with EIO port. PS1126 is the first print server worldwide to attach these HP output devices to gigabit fibre optic networks (1000BaseSX). Both gigabit and fibre optic technology are future technologies offering faster data transfer and more available bandwidth for large volume print jobs. In addition, fibre optic networks are eavesdropping-secure. PS1126 is IPv6-ready, equipped with ThinPrint technology for bandwidth optimization and control and ThinPrint SSL encryption, and comes with an unmatched security package. The new model is available as of now for 495 Euro.
The German network specialist SEH has integrated future technologies into its new PS1126 interface card for HP printers with EIO port. PS1126 is the first print server worldwide to attach these HP output devices to gigabit fibre optic networks (1000BaseSX). Both gigabit and fibre optic technology are future technologies offering faster data transfer and more available bandwidth for large volume print jobs. In addition, fibre optic networks are eavesdropping-secure. PS1126 is IPv6-ready, equipped with ThinPrint technology for bandwidth optimization and control and ThinPrint SSL encryption, and comes with an unmatched security package. The new model is available as of now for 495 Euro.
New IT technologies are often bandwidth-hungry. Print jobs with intensive use of graphic elements and colour also quickly grow into large volume files. Gigabit and fibre optic technologies play an increasingly important role for network design as both provide for greater bandwidth. The new PS1126 print server enables users to connect printers directly to gigabit fibre optic cabling. In this way network printing benefits from fast and eavesdropping secure data transmission, eliminating the need for special media converters, which also often cause failures.
Future Technologies for Network Printing
The SEH PS1126 print server comes with even more features which offer protection of investment. While being fully functional with the currently still prevalent network protocol IPv4, the print server is IPv6-enabled, allowing for a planned migration to this protocol which is spreading out more and more so printers, too, can be attached to IPv6 networks. The latest ThinPrint .print client is integrated for utilising PS1126 in environments with innovative ThinPrint .print software, e.g. desktop virtualisation or server-based computing, providing efficient bandwidth control and optimisation for network printing.
As all SEH print servers, PS1126 comes with a powerful security package as well as regular soft- and firmware updates, free tech support, and a warranty of up to five years.
Source: http://pressemitteilung.ws/node/149523
Users often have trouble setting up hardware in Linux they simply aren’t used to the way things are done in Linux. Setting up hardware is relatively simple (once you know where the tools are.) And setting up a printer is one of those jobs made very easy by modern Linux administration tools. One of those tools is the Common UNIX Printing System (CUPS). Once installed, CUPS is an amazingly simple tool to use and administer.
Getting and installing
Getting and installing
The easiest way to install CUPS is to fire up your package manager (such as Adept, Synaptic, Yumex, etc), do a search for CUPS, click it, and install it. Or, if you’re more comfortable with the command line, you can run apt-get install cups or yum install cups.
Once installed, you will want to run the CUPS daemon with the command
/etc/rc.d/init.d/cupsys start
Or
/etc/init.d/cupsys start
Once it is started, you are ready to go.
Configuring your printer
CUPS is managed through a Web browser. So open up Firefox and point it to http://localhost:631 and you will find yourself on the CUPS main page (Figure A) on your system. And no, you do not have to have Apache installed for this to work.
Figure A
It’s not exactly pretty, but from this page you can manage every aspect of your printer.
Now the first thing you want to do (after you have plugged in your printer and fired it up) is to click on the Add Printer button (from the front page of the CUPS Web tool). The first Add Printer dialogue (Figure B) is simple: Name, Location, and Description.
Figure B
You can not use a space, “/”, or “#” symbol in the Name field.
These fields are exactly as you would expect them to be. These are not taken from a driver or from the machines’ firm (or hard) ware. So fill out these fields and then click Continue.
The next step is to select a device to associate with the printer you are adding. This is where you actually select your printer (or printer type) from a list. As you can see, in Figure C my Samsung ML1710 was detected by the CUPS system.
Figure C
There are two instances of my Samsung ML1710. I will select the second because it was recognized as a USB printer.
The next step selects the PPD file for the device. A PPD file is the Postscript Printer Device file that describes the fonts, paper sizes, resolutions, etc that the printer can handle. As you can see, in Figure D, my ML1710 has a few entries (most of which are duplicates for some reason).
I will select the foomatic entry because foomatic entries tend to be the most reliable of the PPD files. Now, if your device does not have a listed PPD file, fear not. You most likely can find a PPD file from either the included drivers, from device’ manufacturer Web site, or from an online search. If you find one just upload it with the help of the browse button in the dialog shown in Figure C.
Once you have selected your PPD file click Add Printer at which point you will be prompted for a username and password. On an Ubuntu system I was able to get by with using my regular username and password. In some instances you may have to use the root user and password.
Once you have added the printer you will be redirected to the configuration page for that printer. The configuration page is broken up into five sections: General, Adjustment, Miscellaneous, Banners, and Policies. Each section has its own configuration options.
AdjustmentThese options will depend upon the type of printer you have added. Since I have added a laser printer I get options that relate to saving toner. These are crucial if you do a lot of printing and don’t want to be replacing expensive toner every month.
MiscellaneousThis section holds all of the options that don’t belong in any other section. Here you can actually correct for high altitude and other options as they relate to your printer.
Figure F
Altitude correction only gives you options for high or low altitude. There should be an option for “No correction”.
Banners
The Banners section allows you to select from six different starting and ending banners. These banners are: Classified, Confidential, Secret, Standard, Topsecret, or Unclassified. Or you can select None. These banners will be automatically added to the top and bottom (respectively) of every page printed.
“None” is the default (and toner saving) option.
Policies
The policies section is a bit more complex. Policies refer to configuring a printer such that a user would have to provide a password in order to use the printer or allowing use from only specified printers. The only configuration option available is to select a policy from the drop down. Of course you would have to create a policy (which is beyond the scope of this article) first. But if you have created policies, you can choose them from the list and apply them to the configured printer.
Figure H
As you can see there are two default policies available for this printer: Error Policy and Operating Policy.
Checking your printerOnce you have the printer added, the first thing you will want to do is check to make sure it is printing properly. To do this click on the Printers tab and you will see the newly added printer listed.
Figure I
Here you can start, stop, reject and move jobs, set as default, and a number of other options.
If this is the only printer you have added it will be set as the default. If this is a second (or third) printer you will have the option as setting this printer up as the default. To do that, click Set As Default button.
Now, let’s print a test page for this printer. Click the Print Test Page button and a test page should be immediately sent to your printer. You will get a quick banner page claiming a test page has been sent and then you will be redirected to the printer page.
If your test page prints successfully, congratulations, you have added a printer to a Linux-based computer.
Source: http://blogs.techrepublic.com.com/opensource/?p=222
Data Requirements
The following table lists the data requirements for setting up a print server.
| Parameter | Description | Your Value |
|---|---|---|
| Printer name | User-assigned name of the printer. | |
| Printer share name | User-assigned name of the printer as it will appear to network clients. This can be the same as the printer name if you want. Due to client limitations, this name should be limited to 8 characters. | |
| List of client operating systems | To facilitate automatic download of drivers from the server to the client, you must know in advance the operating systems of the clients which will use the shared printer. |
Configuration Procedure
Authority Level Required
1. The first step in setting up a print server is to set the machine up to print directly to the printer. If you have not already done so, do the procedure Configuring Windows 2000 to Print Directly to the Printer, and return here when done.Some of the following configuration steps may require administrative authority.
2. Select Start, then Settings, then Printers. You see the Printers folder.
3. Right-click on the printer and select Sharing....
4. Click the Shared radio button, then enter the printer's share name.
5. If there will be clients on other operating systems that are going to use this shared printer, click Additional Drivers, select all such operating systems in the resulting list, then click OK. At this point, you will be prompted to install the drivers by inserting the Setup CD-ROM. Follow the instructions to do this.
6. As an option, you can enter the location of the printer (such as "Building 3, Room 107") and a comment about the printer (such as "For use by marketing only"). To enter this information, select the General tab.
7. Click OK.
8. Inform the clients that will be using the printer of the share name of the printer.
Verifying the Configuration
You will test the shared printer by installing a client of the printer and printing a test page from that client. To install a print client, see Configuring Windows Print Clients on TCP/IP Networks.
Networks are naturally susceptible to failures because they contain many components and are affected by the configuration of every component. Where, exactly, is your network? In the switch? The drop cables? Bounded by all of the network interface cards in your systems? Any of those physical components can break, resulting in network outages or, more maddeningly, intermittent network failures.
Networks are also affected by configuration problems. Incorrect routing information, duplicate hostnames or IP addresses, and machines that misinterpret broadcast addresses can lead to misdirected packets. You’ll also have to deal with redundancy in network connections, as you may have several routers connecting networks at multiple points. When that redundancy is broken, or its configuration is misrepresented, the network appears to be down.
When a network that you trust and love is connected to an untrusted or unmanaged network, you run the risk of being subject to a denial-of-service attack or a network penetration attempt from one of those networks. These types of attacks happen within well-run networks as well. Security mogul Bill Cheswick asks the attendees at his talks if they leave their wallets out in the open in their offices. Nary a hand goes up. Then he asks how many leave unprotected network access points like twisted-pair wall jacks in open offices, and you see the tentative hands raised. Access to the network is valuable and has to be protected while still allowing user activity to proceed without onerous overhead.
Finally, networks use a variety of core services or basic information services that we lump into the network fabric. Naming systems like NIS or DNS, security and authentication servers, or host configuration servers for hosts requiring DHCP to boot and join a network will bring down a network if they are not functioning or are giving out wrong answers.
File and Print Server Failures
When file and print server fail, clients will hang or experience timeouts. A timeout can mean that a print job or a file request fails. The timeout can also lead to wrong answers or data corruption. For example, using Network File Systems (NFS) soft mounts, a write operation that times out will not be repeated. This can lead to holes in data files that will only be detected when the file is read.
Source: http://www.web-articles.info/e/a/title/File-and-Print-Server-Failures/
Networks are also affected by configuration problems. Incorrect routing information, duplicate hostnames or IP addresses, and machines that misinterpret broadcast addresses can lead to misdirected packets. You’ll also have to deal with redundancy in network connections, as you may have several routers connecting networks at multiple points. When that redundancy is broken, or its configuration is misrepresented, the network appears to be down.
When a network that you trust and love is connected to an untrusted or unmanaged network, you run the risk of being subject to a denial-of-service attack or a network penetration attempt from one of those networks. These types of attacks happen within well-run networks as well. Security mogul Bill Cheswick asks the attendees at his talks if they leave their wallets out in the open in their offices. Nary a hand goes up. Then he asks how many leave unprotected network access points like twisted-pair wall jacks in open offices, and you see the tentative hands raised. Access to the network is valuable and has to be protected while still allowing user activity to proceed without onerous overhead.
Finally, networks use a variety of core services or basic information services that we lump into the network fabric. Naming systems like NIS or DNS, security and authentication servers, or host configuration servers for hosts requiring DHCP to boot and join a network will bring down a network if they are not functioning or are giving out wrong answers.
File and Print Server Failures
When file and print server fail, clients will hang or experience timeouts. A timeout can mean that a print job or a file request fails. The timeout can also lead to wrong answers or data corruption. For example, using Network File Systems (NFS) soft mounts, a write operation that times out will not be repeated. This can lead to holes in data files that will only be detected when the file is read.
Source: http://www.web-articles.info/e/a/title/File-and-Print-Server-Failures/
File and print services are among the most critical in any organization. It is imperative that users have quick, guaranteed, and secure access to their data. Helping organizations to create highly available, well performing, and secure file and print services are amid the key improvements in Windows Server 2003.
| Feature | Benefit | Key Scenarios | Notes |
Windows SharePoint Service | Windows Server 2003 R2 provides a sophisticated collaboration system that takes your file and print level to the next level by empowering end users to share information and work together more effectively through collaboration on documents, meetings and projects. This enhances your operating efficiency, and provides the functionality that makes your end users more productive. This system also is designed to give the IT Pro, control over the environment, while providing end-user self-service to minimize calls to IT and/or the helpdesk. | Simplify end user collaboration by facilitating the sharing of documents amongst teams. Effectively manage your documents, lists, contacts, and tasks in a team and project centric Windows SharePoint Services environment. Leverage wide range of out-of-box custom scenarios with 30 new application templates for the Windows SharePoint Services platform, a starting point for effective collaborative experience. Easily extend it to support your business processes and customer interactions. | Now built-in with Windows Server 2003 R2 |
Print Management Console | New print management console based on a Microsoft Management Console (MMC) snap-in. This console enables the management of multiple printers and with integration with other Windows services, it is now easy to push drivers to the different resources and also enables the management of the print jobs from a remote location. | Facilitate the management of remote printing resources (in branch office for example) and enables management of multiple printers from the same console. | Integrated with Active Directory |
Volume Shadow Copy Service (VSS) | The ability to quickly create point-in-time copies of data, allowing easier and more reliable backups of important organizational data, even while files are open. VSS significantly reduces a server's backup window by providing on-disk, point-in-time recoverable data sets. | All major backup independent software vendors (ISVs) are developing solutions based on VSS to take advantage of this service. By moving a point-in-time copy to another server, a business analyst can query against the latest company data without affecting performance on the production system. | Introduced in Windows Server 2003 |
NTFS Journaling File System | Because NTFS offers reliable file system recovery, extremely large storage media, and strong granular security, organizations can be confident that their data is safer. | NTFS allows reliable, secure, and high performing access to data. | 100-139 percent increase in performance over Windows 2000 Server |
Encrypting File System (EFS) | EFS creates a layer of security that transparently encrypts data on the physical disk with no need for end user interaction, ensuring that data is safer. | Since data on the disk is encrypted, even a mobile user whose sensitive organizational data is lost or stolen will be safer from data theft. | Encryption of offline and Web folders now possible EFS files can be shared among multiple users |
Enhanced Anti-Virus Support | Choose from a huge selection of enterprise anti-virus vendors to protect resources in your organization from malicious code delivered by viruses. | Create a comprehensive anti-virus strategy by using third-party tools to scan file servers. | New kernel level anti-virus APIs Windows Hardware Quality Lab test suite and driver certification test process for antivirus and file system drivers New tools are available for third-party anti-virus vendors to enhance the performance and reliability of their products |
Improved Print Cluster Support | Improve administrator productivity by making it easier to install and configure print clusters. | Hundreds, perhaps thousands, of printers can be installed on a highly available print cluster therefore allowing end users to have continual access to their resources, even during a hardware failure. | 8-Node clusters supported in Windows Server 2003 Datacenter Edition, and Windows Server 2003 Enterprise Edition Clustering is not available in Standard or Web editions. Printer drivers automatically propagate to each node in the cluster |
64-bit processor support | Take advantage of the latest and best performing hardware in the industry. | File and print server consolidation can reduce administrative and hardware costs dramatically. | Introduced in Windows Server 2003 Supports GUID Partitioning Table (GPT) Approximately 3,800 in-box 64-bit print drivers |
Improved Print Performance and Availability | Users will get their printed documents faster than ever. | Organizations see the need to consolidate print servers to lower total cost of operation (TCO) without losing performance or availability. | Optimized file spooling for higher print volume management Kernel mode driver blocking Enhanced printer redirection through Terminal Services |
Enhanced Windows Defragmentation Tool | Optimizing files on a server can dramatically increase the performance and availability. | Administrators can use the scheduled tasks feature to schedule disk defragmentation seamlessly optimizing the file system. Administrators can also script disk defragmentation on servers using command line utilities. | Faster performance than in Windows 2000 Supports online defragmentation of the Master File Table (MFT) Defragmentation of any NTFS cluster size now possible Volume Shadow Copy support Command line scripting support |
Increased CHKDSK Performance | CHKDSK is a program that verifies the logical integrity of a file system on Windows. When CHKDSK encounters logical inconsistencies it takes actions to repair file system data. | Because NTFS has always been a true journaling file system that supports file system recovery, it is very rare that a disk need to be checked (less than 1percent of unplanned outages require checking). However, in Windows Server 2003, CHKDSK performs faster, requiring even less downtime. Source: http://www.microsoft.com/windowsserver2003/evaluation/overview/technologies/fileandprint.mspx | Performs 20-38 percent faster than Windows 2000 Server |
Subscribe to:
Posts (Atom)
