Network Computer Sharing: Difference between revisions

From BetaArchive Wiki
(Windows Vista UI concepts, device install propagation)
(Jim Allchin comments)
Line 9: Line 9:
To join an existing Castle, users would be required to know the login credentials of an administrator account that was already joined to the Castle (in order to ensure that only authorized users had access). Once a relationship between the computer and existing Castle had been established, account profiles on the newly joined computer would automatically be replicated across other computers joined to the Castle and kept in sync, with each computer inheriting and respecting all policies pertaining to the shared data.<ref name="Microsoft.">Microsoft. (October 24, 2003). [https://web.archive.org/web/20060821085902/http://www.microsoft.com/windowsvista/privacy/privacy_pdc.mspx "Windows 'Longhorn' Pre-Release Privacy Statement"]</ref> Although Castle was originally conceived of as a way to simplify file sharing, other potential uses were envisioned, including application and setting synchronization on the same account across multiple machines, Windows Update patch distribution, and new licensing techniques for content protected by digital rights management technology. These features would not have necessarily have been included in Windows "Longhorn" as Castle in that operating system was intended to provide the foundation for these features in future versions of Windows.<ref name="Lyndersay, Sean.">Lyndersay, Sean. (January 16, 2009). [http://blogs.msdn.com/b/justsean/archive/2009/01/16/castle-and-homegroup-a-study-in-the-evolution-of-user-needs.aspx "Castle and HomeGroup: A study in the evolution of user needs"]</ref>
To join an existing Castle, users would be required to know the login credentials of an administrator account that was already joined to the Castle (in order to ensure that only authorized users had access). Once a relationship between the computer and existing Castle had been established, account profiles on the newly joined computer would automatically be replicated across other computers joined to the Castle and kept in sync, with each computer inheriting and respecting all policies pertaining to the shared data.<ref name="Microsoft.">Microsoft. (October 24, 2003). [https://web.archive.org/web/20060821085902/http://www.microsoft.com/windowsvista/privacy/privacy_pdc.mspx "Windows 'Longhorn' Pre-Release Privacy Statement"]</ref> Although Castle was originally conceived of as a way to simplify file sharing, other potential uses were envisioned, including application and setting synchronization on the same account across multiple machines, Windows Update patch distribution, and new licensing techniques for content protected by digital rights management technology. These features would not have necessarily have been included in Windows "Longhorn" as Castle in that operating system was intended to provide the foundation for these features in future versions of Windows.<ref name="Lyndersay, Sean.">Lyndersay, Sean. (January 16, 2009). [http://blogs.msdn.com/b/justsean/archive/2009/01/16/castle-and-homegroup-a-study-in-the-evolution-of-user-needs.aspx "Castle and HomeGroup: A study in the evolution of user needs"]</ref>


In addition to replicating user data, Castle could also replicate device installations across PCs connected to the same local network.<ref name="InstallPropagation">Roth, Tali. (2004). [http://web.archive.org/web/20040615004042/http://download.microsoft.com/download/1/8/f/18f8cee2-0b64-41f2-893d-a6f2295b40c8/TW04063_WINHEC2004.ppt "Web Services For Imaging And Printing Devices, Part One"]</ref>
According to Paul Thurrott, Jim Allchin remarked on Microsoft's plans for Castle, including an envisaged scenario where users could share their data with other users across the Internet: <blockquote>"The idea is to replicate identities across the home machines (if the user wants this to happen). Think about it as a domain in the home. For the scenario across the Internet we are trying to work out a solution so that it is easy to share and publish photos (or other data) with users across the Internet. Our goal is to do this so that standard Windows security IDs can be used."<ref name="RoadtoGoalTh">Thurrott, Paul. [http://winsupersite.com/article/product-review/road-to-gold-the-long-road-to-windows-vista-part-4-january---july-2005 "Road to Gold: The Long Road to Windows Vista Part 4: January - July 2005"]</ref></blockquote>
 
In addition to replicating user data, Castle was also designed to replicate device installations across PCs connected to the same local network.<ref name="InstallPropagation">Roth, Tali. (2004). [http://web.archive.org/web/20040615004042/http://download.microsoft.com/download/1/8/f/18f8cee2-0b64-41f2-893d-a6f2295b40c8/TW04063_WINHEC2004.ppt "Web Services For Imaging And Printing Devices, Part One"]</ref>


==HomeGroup==
==HomeGroup==

Revision as of 23:47, 2 January 2016

The Castle Discovery Service in Windows "Longhorn" build 4074.

Castle is the codename of a file sharing and identity replication service included in the Microsoft Windows "Longhorn" operating system. Castle was designed to simplify file sharing across multiple computers on the same network, and relied on WinFS and other technologies. The feature was shelved after the development reset of the operating system in 2004.[1]

Details

In spite of the feature being scrapped, preliminary UI concepts for Windows Vista incorporated the "Castle" feature in their designs, as seen in this promotional slide from WinHEC 2006.[2]

Historically, consumer-oriented editions of the Windows operating system have allowed users to share data across multiple machines. However, in order for users to share data, they are required to create individual user profiles for each machine and connect each machine to the same local network. More inexperienced users must also deal with the complexity of configuring login credential and user permission settings. The idea of creating a simplified file sharing solution for home users of the Windows operating system predates the development of Castle. Earlier consumer-oriented editions of Windows, including Windows 98 and Windows ME, allowed users to share data without protecting it with a password;[3] the first consumer edition of Windows NT, Windows XP, introduced a Simple File Sharing feature which offered similar functionality.[4] While these features made it easier for more inexperienced users to share data without the complexity of traditional sharing settings, they also introduced a potential security risk in that they allowed every user on the same local network to access it. Moreover, they did not solve the problem of allowing a single user to securely access his or her data from any computer without the complexity of creating individual accounts on multiple machines. Castle attempted to solve this problem by securely replicating user profiles across multiple machines; in this sense, it is similar to the roaming user profile feature in server versions of Windows where an administrator can store user profiles on a centralized server, thereby allowing users to access their data regardless of which computer they are using.[5][6]

To join an existing Castle, users would be required to know the login credentials of an administrator account that was already joined to the Castle (in order to ensure that only authorized users had access). Once a relationship between the computer and existing Castle had been established, account profiles on the newly joined computer would automatically be replicated across other computers joined to the Castle and kept in sync, with each computer inheriting and respecting all policies pertaining to the shared data.[7] Although Castle was originally conceived of as a way to simplify file sharing, other potential uses were envisioned, including application and setting synchronization on the same account across multiple machines, Windows Update patch distribution, and new licensing techniques for content protected by digital rights management technology. These features would not have necessarily have been included in Windows "Longhorn" as Castle in that operating system was intended to provide the foundation for these features in future versions of Windows.[1]

According to Paul Thurrott, Jim Allchin remarked on Microsoft's plans for Castle, including an envisaged scenario where users could share their data with other users across the Internet:

"The idea is to replicate identities across the home machines (if the user wants this to happen). Think about it as a domain in the home. For the scenario across the Internet we are trying to work out a solution so that it is easy to share and publish photos (or other data) with users across the Internet. Our goal is to do this so that standard Windows security IDs can be used."[8]

In addition to replicating user data, Castle was also designed to replicate device installations across PCs connected to the same local network.[9]

HomeGroup

HomeGroup is a password-based sharing solution that debuted in the Microsoft Windows 7 operating system. HomeGroup allows users on the same home network to share individual files, folders, and printers, and to set access control permissions on shared content. A HomeGroup can be created during Windows installation or after Windows has been installed.[10] Once a HomeGroup is created, a password is generated which is required for other users to join the HomeGroup; the feature will instruct the user to save this password after it is generated. Once other users join the HomeGroup, they can share their data with other members of the HomeGroup.

During development of Windows 7, technology bloggers compared HomeGroup to the Castle feature that was shelved after the development reset of Windows "Longhorn" and speculated that it was meant to be a reinstatement of the feature.[11][12] Although HomeGroup shares some design similarities with Castle in that they were both designed to create a simple and secure file sharing solution, HomeGroup only offers a subset of the functionality that was originally intended for Castle.[1]

See also

References