Screenshot of the Windows Home Server, showing the Start menu, About. Dialog box, task bar and Microsoft Source model / 4 November 2007; 10 years ago ( 2007-11-04) 6.0 (Build 2423: Power Pack 3) / 24 November 2009; 8 years ago ( 2009-11-24) type Succeeded by (2011) Official website Support status Unsupported as of 8 January 2013 Windows Home Server, code-named Quattro, is a from.

Windows Server Configuration Guidelines. The following guidelines and best practices can be used to secure Microsoft Windows servers on the. NAU network and to protect the data housed on them. The use of the word “server” indicates either a physical or virtual server where files or services are being used.

It was announced on 7 January 2007 at the by, on 16 July 2007 and on 4 November 2007. Windows Home Server is based on and is intended to be a solution for homes with multiple connected PCs to offer, automated backups,, and remote access. Power Pack 1 for Windows Home Server was released on 20 July 2008. Power Pack 2 was released on 24 March 2009 and Power Pack 3 was released on 24 November 2009., the next version of this operating system, was released on 6 April 2011. Microsoft confirmed Windows Home Server 2011 to be last release in the Windows Home Server product line.

Contents • • • • • • • • • • • • • • • • • • Features [ ] • 10 computers and 10 users: Allows a maximum of ten user accounts to be created on the server console and ten computers to have WHS connector installed, without any. • Centralized backup: Allows of up to 10 PCs, using technology to avoid multiple copies of the same file, even if that file exists on multiple PCs.

• Health monitoring: Can centrally track the health of all on the network, including and status. • File sharing: Creates and operates for computers to store the files remotely, acting as a device. Separate categories are provided for common file types like Documents, Music, Pictures and Videos. The files are for fast searching. • Printer sharing: Allows a to handle print jobs for all users. •: Uses Volume Shadow Copy Service to take point in time snapshots that allow older versions of files to be recovered.

• Headless operation: No monitor or keyboard is required to manage the device. Is performed by using the Windows Home Server Console client software provided in the bundle. Connections to the server are supported while connected to the same LAN.

• Remote access gateway: Allows remote access to any connected PC on the network, including the server itself, over the Internet. •: Can stream media to an or other devices supporting. Bodyguard Salman Khan Ringtone Tau Tau. • Selective: Guards against a single drive failure by duplicating selected data across multiple drives. • Expandable storage: Provides a unified single and easily expandable storage space, removing the need for. • Extensibility through add-ins: Add-ins allow third-party developers to extend the features and functionality of the server.

Add-Ins can be developed using the Windows Home Server SDK, to provide additional services to the client computers or work with the data already on the server. Add-ins can also be applications, hosted in running on WHS. • Server backup: Backs up files which are stored within shared folders on the server to an. Technology [ ] Home Server Console [ ].

Windows Home Server Console The configuration interface is designed to be user friendly enough that it can be set up without prior knowledge of server administration. The configuration interface, called the Home Server Console, is delivered as a application to remote PCs - while the application runs on the server itself, the is rendered on the remote system. The Home Server Console client application can be accessed from any Windows PC. The server itself requires no video card or peripherals; it is designed to require only an card and at least one, or computer.

Harry Potter Po Angielsku Ebook Library. Drive Extender [ ] Windows Home Server Drive Extender was a file-based replication system that provided three key capabilities: • Multi-disk redundancy so that if any given disk failed, data was not lost • Arbitrary storage expansion by supporting any type of drive (e.g.,, ) in any mixture and capacity, similar in concept to • A single folder namespace (no drive letters) With drive extender, users could add larger capacity hard disk drives and then could offline lesser capacity drives to upgrade capacity. For example, if the user was reaching capacity of the share with five of the six-terabyte capacity used with six one-terabyte drives then the user could offline one of the one-terabyte drives and physically replace it with a two-terabyte drive.

The WHS automatically equalizes the redistribution of used space across all available drives on a regular basis. The offline process would compress the used data across the minimum amount of drives allowing for the removal of one of the lesser capacity drives. Once replaced with a drive of higher capacity the system will automatically redistribute used capacity among the pool to ensure space capacity on each drive. Users (specifically those who configure a family's home server) dealt with storage at two levels: and Disks. The only concepts relevant regarding disks was whether they had been 'added' to the home server's storage pool or not and whether the disk appeared healthy to the system or not. This was in contrast with Windows' which requires a greater degree of technical understanding in order to correctly configure a array.

Shared Folders had a name, a description, permissions, and a flag indicating whether duplication (redundancy) was on or off for that folder. If duplication was on for a Shared Folder (which was the default on multi-disk Home Server systems and not applicable to single disk systems) then the files in that Shared Folder were duplicated and the effective storage capacity was halved. However, in situations where a user may not have wanted data duplicated (e.g. TV shows that had been archived to a Windows Home Server from a system running ), Drive Extender provided the capability to not duplicate such files if the server was short on capacity or manually mark a complete content store as not for duplication.

A known limitation of Drive Extender was that it in some cases changed timestamp of directories and files when data was moved around between disks. According to Microsoft this was expected behaviour. This caused unexpected behaviour when using clients that sort media based on date. Examples are,, and. The aforementioned programs worked fine with WHS; however, files may have appeared out of order due to this caveat. Cancellation [ ] On 23 November 2010, Microsoft announced that Drive Extender would be removed from.

This announcement has led to public outcry in the announcement's comments section. Criticism of Drive Extender's removal is mainly related to it being seen as a core feature of Windows Home Server and a key reason for adoption. As a replacement for Drive Extender, Microsoft states that OEMs will use RAID on their Windows Home Server products.

Computer Backup and Restore [ ] Windows Home Server Computer Backup automatically backs up all of the computers in a home to the server using an image-based system that ensures point-in-time-based restoration of either entire PCs or specific files and folders. Complete are initiated through a restore, file based restores are initiated through the WHS client software which allows the users to open a backup and 'drag and drop' files from it. This technology uses technology on the client computer to take an image based backup of a running computer. Because the backup operates on data at the level, can be performed to minimize the amount of data that travels over the network and that will ultimately be stored on the home server. This single instancing gives the server the ability to store only one instance of data, no matter if the data originated from another computer, another file, or even data within the same file.

Computer backup images are not duplicated on the server, so if a server hard drive fails, backups could be lost. The 'Server Backup' feature added in Power Pack 1 does not include duplication of backup images. Remote File Access [ ]. Web Interface showing the shared files UI The system also offers an secured based interface over the to the shared file stores. The release version offers access to the web interface via a free -provided, which uses. The web interface also allows the uploading to and downloading of files from the content stores. However, there is a limit of 2 GB for a single batch of upload.

Remote Desktop Services [ ] The system also supports, allowing of any Windows computer on the home network. Currently supported systems are those which would normally support: Professional, Tablet and Media Center editions, Business, Enterprise and Ultimate editions and Professional, Enterprise and Ultimate editions. The web interface also supports embedding the Remote Desktop control, to provide remote access to home computers from within the web interface directly. Remote sessions can also connect to the Home Server console to configure the server over the internet. Add-Ins [ ] Windows Home Server allows for developers to publish community and commercial add-ins designed to enhance the Windows Home Server with added functionality. As of January 2010, nearly 100 of these add-ins have been developed for WHS, including applications for antivirus & security, backups, disk management, automation, media, network/power management, remote access, BitTorrent and more.

The Windows Home Server SDK (Software Development Kit) provides developers with a set of APIs and tools to use when developing for and extending Windows Home Server. Compatibility [ ] System requirements Requirements x86 CPU 1.0 (or equivalent) Memory 512 Hard drive 80 Media or Network Input device(s) and Windows Home Server features integration with (SP2 or newer),, and (after the release of Power Pack 3) through a software installation, either from a client CD or via a network share. The connector software may also be installed by accessing, where a link is provided to download the connector software and to install troubleshooting tools. Files stored on Windows Home Server are also available through a, opening compatibility to a wide variety of operating systems.

Also, the Administration console is available via Remote Desktop, allowing administration from unsupported platforms. Windows Home Server does not support. 64-bit Windows client support was introduced in Power Pack 1, though the Restore Wizard on the Windows Home Server Restore CD is unable to restore clients running 64-bit operating systems, due to the fact that the Restore CD does not support 64-bit drivers.

Windows XP Professional x64 isn't officially supported. However, unofficial workarounds allow Connector software to work on XP x64. Integration of the file sharing service as a location for was apparently being considered, but upon Mac OS X Leopard's release, Apple had removed the ability to use the SMB file sharing protocol for Time Machine backups. One WHS provider,, provides their own plug-in with their home server line capable of Time Machine backup to a home server. Windows Home Server has not officially supported capability and cannot readily join a. Wireless networking is supported.

Dedicated devices will have the operating system pre-installed and may be supplied with a server recovery disk which reloads the OS over a network connection. This is utilized on the HP MediaSmart Server, and the Fujitsu Siemens Scaleo Home Server. Resolved issues [ ] File corruption [ ] The first release of Windows Home Server, RTM (Release to manufacturing), suffered from a file corruption flaw whereby files saved directly to or edited on shares on a WHS device could become corrupted. Only the files that had were susceptible to the flaw. The flaw led to data corruption only when the server was under heavy load at the time when the file (with ADS) was being saved onto a share. Backups of client PCs made by Windows Home Server were not susceptible to the flaw. Even though the issue was first acknowledged in October 2007, formally warned users of the seriousness of the flaw on 20 December 2007.

Microsoft then issued a list of applications, including,, and 2.0, which might have triggered the flaw if they were used to edit the files on a WHS share directly. This issue was fixed by Power Pack 1, released on 21 July 2008. No native backup [ ] Windows Home Server RTM did not include a mechanism for backing up the server.

Power Pack 1 added the ability to back up files stored on the Shared Folders, to an external drive. Users can also subscribe to 3rd-party online services, for a fee. However, there remains no way to back up the installed server operating system. Backing-up of the client backup database is available either manually using the instructions provided by Microsoft on page 24 of or can be done using the WHS BDBB add-in written by Alex Kuretz and available from. Pricing [ ] While some hardware manufacturers have developed dedicated boxes, Microsoft has also released Windows Home Server under the /System Builder license. In November 2008, Microsoft lowered the price of the WHS System Builder SKU to US$100. Users can also choose to use an existing PC or build their own systems, which would include the use of WHS System Builder.

As of 23 March 2009, Microsoft has also made Windows Home Server available to and subscribers. Some computer systems are available only with a bundled Windows Home Server license. As is the case with other versions of Windows it is possible to request a paid for Windows Home Server. See also [ ] • • References [ ]. The Windows Blog. 24 November 2009.

Archived from on 27 November 2009. Retrieved 24 November 2009. Windows Home Server Blog..

Archived from on 2009-11-22. Retrieved 30 January 2017.

Retrieved 2007-01-08. Former Windows Home Server Team Blog. Microsoft Corporation. 16 July 2007. Retrieved 2 February 2011. Microsoft News Center.

Redmond, Washington: Microsoft Corporation. 4 November 2007.

Retrieved 2 February 2011. Retrieved 2008-07-22. The Windows Blog.

29 March 2011. Retrieved 2 April 2011. Retrieved 5 July 2012.

Windows Home Server Team Blog. 4 September 2008. Retrieved 10 June 2013. Retrieved 2007-05-07. • ^ Paul Thurrott (2007-01-07).. Windows SuperSite.

Retrieved 2007-01-08. Retrieved 2007-10-15. • Nathan Weinberg (2007-01-07).. Retrieved 2007-04-28. Retrieved 2007-10-04.

Windows Home Server Team Blog. Retrieved 2007-04-28. • Windows Home Server Team Blog. Retrieved 2007-04-28. 15 September 2008.

•, Jon Honeyball, PCPro •. Windows Home Server Team Blog. Retrieved 2007-04-28. Microsoft Connect. January 2007. Retrieved 2007-04-28. Retrieved 2008-07-14.

Retrieved 2009-09-24. Retrieved 2010-09-29. MS Windows Home Server. Retrieved 13 January 2016.

Paul Thurrott's SuperSite. Retrieved 2008-07-02. Retrieved 2008-07-02. • Technology, Expert (2008-12-29)..

Retrieved 2009-03-02. Retrieved 13 January 2016. Retrieved 2007-12-27. Retrieved 13 January 2016. 2 October 2007.

Archived from on 31 December 2007. Retrieved 2007-12-27. The Seattle Times. Windows Home Server Team Blog. Further reading [ ].

2016 / October 25, 2016 Website Windows Server Essentials (formerly Windows Small Business Server or SBS ) is an integrated server suite from designed for running network infrastructure (both management and access) of small and midsize businesses having no more than 25 users or 50 devices. Application server technologies are tightly integrated to provide and offer management benefits such as integrated setup, enhanced monitoring,, a unified, and remote access. Since the release of SBS 2003, the same service packs as those for or other server products can be used to update the OS. Contents • • • • • • • Editions [ ] Windows Server 2016 Essentials, based on Windows Server 2016, is the current version of Server Essentials, released in September 2016 with general availability October 12, 2016. Windows Server 2012 R2 Essentials and Windows Server 2012 Essentials were the previous versions of corresponding releases of Windows Server. Older versions: Windows Small Business Server 2011 was available in Essentials, Standard, and Premium editions. Essentials is a scaled down version for 1 to 25 users; both the other editions are based on the codebase and include, (IIS), for collaboration, 2003 email client (not included in 2008), (RRAS), for update management across the network, and a.

Up to SBS 2003, the Premium edition also included, and 2003. SBS 2008 Premium edition will not include but will include a license and SQL Server 2008 for running on a second server. Those upgrading to SBS 2008 Premium edition via Software Assurance will be compensated with a free license for the latest version of ISA Server. The version of Windows Server that is part of Small Business Server 2008 and Essential Business Server 2008, known as Windows Server 2008 for Windows Essential Server Solutions (WinWESS) (also known as Windows Server 2008 Standard FE) is available outside the product suite, supporting a maximum of 15 Client Access Licenses. Initially, Small Business Server was marketed as an edition of. When was released, it was marketed as Microsoft Small Business Server 2000, and finally was rebranded as a member of the family. In December 2008, Microsoft also introduced a product aimed at medium-sized businesses, but this was discontinued in June 2010 due to low demand.

Design and licensing considerations [ ] All editions of Windows Server Essentials since the 2011 release do not need any (CAL). Windows Small Business Server (not Essentials) had its own type of CAL, and included the user CALs for Windows Server, Exchange Server, and eventually SQL Server; the SBS CAL cost more than the Windows Server license, but less than the sum of separate access licenses for the two or three servers. Windows Small Business Server has the following design restrictions: • Only one computer in the can be running Windows Small Business Server.

The domain supports multiple servers (including additional ) running any other operating system, such as Windows Server Standard Edition, but only one SBS. • Windows Small Business Server must be the root of the forest. • Windows Small Business Server cannot trust any other domains.

It cannot have any child domains. • Windows Small Business Server is limited to 75 users or devices depending on the type of CAL. • All Windows Small Business Server versions up to SBS 2003 are limited to no more than 4 GB of.

2008 requires a minimum of 4GB for installation, it needs more for performance. 2008 supports a maximum of 32GB.

• Windows Small Business Server versions prior to Windows Small Business Server 2008 are only available for the x86 (32-bit) architecture. • Windows Small Business Server 2008 is only available for the (64-bit) architecture. This is due to the requirements of Exchange Server 2007, whose production version is 64-bit only. The 32-bit version of Exchange Server 2007 is only supported for testing and non-production use.

• The SQL Server which comes with SBS 2008 is 'SQL Server 2008 Standard Edition for Small Business.' It cannot be installed outside of a network that has a domain controller, and must have fewer than 75 PCs and/or users. • Only the mode is available because Small Business Server always runs on the domain controller, and only two simultaneous sessions are allowed. (Change from SBS 2000 policy) Terminal Services in application sharing mode needs to be run on a second server on the network. This however is possible with SBS 2011 Premium add-on which includes a license for running the second server.

• To remove these restrictions and upgrade to regular editions of Windows Server, Exchange Server, SQL Server and ISA Server, there is a Windows Small Business Server 2003 R2 Transition Pack. Unique features [ ] • • (for ) • Shared Service (Modem server, not supported in Small Business Server 2003 and later) Versions [ ] • October 22, 1997 – BackOffice Small Business Server 4.0 Consists of SP3 and includes Exchange Server 5.0 SP1, Internet Information Services 3.0, SQL Server 6.5 SP3, Proxy Server 1.0, 3.02 or 4.01, and Outlook 97; allows 25 client licenses.

• May 24, 1999 – BackOffice Small Business Server 4.5 Consists of Windows NT Server 4.0 SP4 and includes Exchange Server 5.5 SP2, IIS 4.0, SQL Server 7.0, Proxy Server 2.0, Internet Explorer 5.0, Outlook 2000, and 2000; allows 50 client licenses. • February 21, 2001 – Microsoft Small Business Server 2000 Consists of (including Internet Explorer 5.0 and IIS 5.0) and includes Exchange 2000 Server, SQL Server 2000 Standard Edition, Internet Security & Acceleration Server 2000, Outlook 2000 and FrontPage 2000; allows 50 client licenses.

• October 9, 2003 – Windows Small Business Server 2003 (codenamed Bobcat) Consists of and includes 2003, 2003, 2.0, and optionally 2000, 2000 (upgrade to ISA Server 2004 in Small Business Server Premium SP1), and 2003 in Premium edition; allows 75 client licenses. Service Pack 1 for Windows Small Business Server 2003 was released on July 25, 2005.

• July 29, 2006 – Windows Small Business Server 2003 R2 Consists of and includes 2003, Microsoft Outlook 2003, 2.0, and optionally 2005 Workgroup Edition, 2004, and 2003 in Premium edition; allows 75 client licenses. A major addition is a built-in patch management tool optimized for small businesses, based on Microsoft. Exchange database size limit is set to 18 GB by default but can be expanded to 75 GB using a registry key. • August 21, 2008 – Windows Small Business Server 2008 (codenamed Cougar) Consists of and includes 2007, 3.0 and 120-day trial subscriptions of new security products from Microsoft, namely, and Windows Live OneCare for Server.

The standard edition of SBS 2008 will be a single server product for small businesses. The premium edition will contain a license for and SQL Server 2008 Standard Edition, with the option to run SQL Server on either the main SBS server, or a second server. The premium edition will therefore be targeted at dual-server scenarios such as terminal services application sharing, applications, edge security, secondary domain controllers, and virtualization. Windows Server Essentials portal.. 5 October 2012. Retrieved 11 July 2013. Q: Why did Microsoft change the name of Windows Small Business Server Essentials to Windows Server Essentials?

A: [.] • WindowsServer2003-KB914961-SP2-x86-ENU.exe (December 3, 2007).. Retrieved August 30, 2012. • ToDownLoadFilesandReadInstructions.htm (August 18, 2012).. Retrieved August 30, 2012. Microsoft Technet. Retrieved 10 February 2013.

Retrieved August 30, 2012. Microsoft Technet. Microsoft Corporation. Retrieved June 9, 2010. Windows Server 2008 Standard FE is the shortened name for Windows Server 2008 for Windows Essential Server Solutions. When you run the Winver tool you will see this reference.

March 10, 2009. Retrieved August 30, 2012. July 11, 2006. Retrieved September 2, 2006. Retrieved August 30, 2012.

Retrieved August 30, 2012. Retrieved September 2, 2006.

Retrieved August 30, 2012. • ToDownLoadFilesandReadInstructions.htm (August 18, 2012).. Retrieved August 30, 2012.

Retrieved August 30, 2012. Retrieved August 30, 2012. February 20, 2008. Retrieved August 30, 2012.

• SBS Server #1 is required to be 64-bit; SBS Server #2 will provide the option to run as either 32-bit or 64-bit. • • (in German). Retrieved August 30, 2012.

Retrieved August 30, 2012. Retrieved August 30, 2012. Retrieved August 30, 2012. Migration Tool has increased default 7 day Active Directory coexistence period to 21 days to address this •. April 27, 2009. Retrieved August 30, 2012. Retrieved August 30, 2012.

Retrieved August 30, 2012. Retrieved August 30, 2012.

• Further reading [ ] •.. Retrieved 1 November 2013. Microsoft Technet. Retrieved 10 November 2013.

Retrieved 1 January 2014. Retrieved 1 March 2014. External links [ ] • on • on • on •.