| 24 | | We currently have a single Win2K Pro buildslave generously hosted by Mike Taylor. |
| 25 | | |
| 26 | | == What we need: == |
| 27 | | |
| 28 | | === Hardware: === |
| 29 | | * A machine to run Win2K3 Server. This will be the primary Windows development machine for the Twisted community, primarily because it allows multiple concurrent RDP sessions (XP Pro allows at most two). This will hopefully be a fast machine with a goodly amout of RAM and lots of HD space. 2.0Ghz+ would be nice. 1GB+ RAM would be nice. We may not be able to have a seperate 2K3 buildbot slave, so this machine may need to serve that purpose as well. |
| 30 | | |
| 31 | | * A machine to run XP Professional. |
| 32 | | |
| 33 | | * A machine to run Windows 2000. |
| 34 | | |
| 35 | | === Hosting: === |
| 36 | | We need someone with a broadband Internet connection to provide hosting for one or more of the above machines. In order to avoid shipping boxes around, it would be ideal if the person providing the hardware could also arrange the hosting. This may not be possible, and so we will consider shipping arrangements as the need arises. |
| 37 | | |
| 38 | | We would like to avoid residential broadband if possible. However, as dedicated Internet connections are hard to come by, we will be gracious for any hosting offers that we receive. In order to provide a responsive desktop/shell environment dedicated bandwidth would be ideal (or at least enough bandwidth where it doesn't matter). Latency is also a consideration. A person downloading a file on residential broadband can easily saturate the line brinding remote desktop/shell sessions to a crawl. |
| | 26 | * Visual Studio license (2005 or 2003) |
| | 27 | |
| | 28 | We need someone with a broadband Internet connection to provide hosting for one or more of the above machines. In order to avoid shipping boxes around, it would be ideal if the person providing the hardware could also arrange the hosting. This may not be possible, and so we will consider shipping arrangements as the need arises. Dedicated/colo bandwidth preferred (of course), but please don't hesitate to offer residential broadband (most of our buildslaves run on residential lines, after all) |
| 52 | | === Specifics about Windows Server 2003 licensing === |
| 53 | | |
| 54 | | First, you need the OS license to install Windows Server 2003 on a machine. |
| 55 | | |
| 56 | | Second, since people will be connecting to the server either through SSH, Remote Desktop, etc., each user needs a separate license. These are '''Client Access Licenses'''. When you install Server 2003, you have to choose how your CALs will be applied. |
| 57 | | |
| 58 | | ''Per Server'' means you have one license for each simultaneous connection. If there are fifteen users who need SSH access to the machine, but only five will ever be connected at once, you can get five CALs and be done with it. In ''Per Server'' licensing mode, users '''cannot''' connect via Terminal Server (Remote Desktop, RDP). |
| 59 | | |
| 60 | | ''Per Device or Per User'' means you have one license for each device-agnostic user or each user-agnostic device. If there are fifteen users who need SSH and/or RDP access to the machine, but only five will ever be connected at once, you still need fifteen CALs. If five of them share one computer and only one of those sharing users will be logged on at once, you can get 1 Device CAL for those five, and 10 User CALs for everyone else. ''Per Device or Per User'' licensing mode is the only licensing mode that allows Windows sessions and use of Terminal Server. |
| 61 | | |
| 62 | | You can change your licensing mode a single time post-install. |
| 63 | | |
| 64 | | If you are in ''Per Device or Per User'' licensing mode and you want to allow users to connect via Remote Desktop, each CAL user or device connecting via Terminal Server requires a '''Terminal Server Client Access License''' in addition to the CAL license. |
| 65 | | |
| 66 | | As an alternative, since Twisted as an "organization" has no "employees, temporary personnel, or independent contractors on assignment at the worksite of the organization," and people logging into Server 2003 over Terminal Server are not "customers to whom organization provides hosted services," instead of getting CALs or CALs + TS CALs, you can get an '''External Connector License''' or '''Terminal Server External Connector License''' that are blanket licenses for unlimited users/devices/connections. |
| 67 | | |
| 68 | | Per the Microsoft Windows Server 2003 R2 retail licensing page (all prices in USD), Server 2003 with five CALs is $1000, or with ten CALs it is $1200. If SSH is your only way in, that may suffice. If you will be logging into the GUI via Terminal Server, then you additionally need at least five TS CALs, which are $750 for five; there's no individual pricing or ten-pack. So that's either $1750 or $2500 or five or ten TS users. |
| 69 | | |
| 70 | | Alternately, it's the $1000 Server 2003 license, plus either $2000 for the ECL (which would be SSH only) or $8000 for the TS ECL (which would allow Remote Desktop sessions). |
