Blog post here. Vendors of Multipoint Hardware solutions can be found here.
Blog Part 1 Blog Part 2 from TechEd Blog Part 3 forum FAQs Blog Part 4 virtualization
The SBS blog has posted regarding a needed hotfix that ensure that RDP connections will not be dropped.
http://blogs.technet.com/b/sbs/archive/2011/10/21/your-remote-desktop-connection-to-a-windows-multipoint-server-2011-or-a-windows-server-2008-r2-server-may-disconnect-on-a-regular-basis.aspx
While this will be included in an upcoming service pack for Windows, I'd urge you to get it installed. It has been tested by various community members and the Multipoint team and is safe to install. Slow boot times for your WMS Server? Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7 this is NOT in update rollup 1.1
If you have WMS 2011 joined to an SBS 2011 and have a broken SBS Connector, install Update Rollup 1.1 (below). Details about the broken connector can be found here.
Update Rollup 1.1 is out
After you patch the server, you can reclaim disk space taken up by the patches by issuing the following command from an Administrative Command Prompt
Blog post here.
Windows MultiPoint Server 2011 and Interaction with Small Business Server 2011 Essentials
To use a MultiPoint server in either a SBS 2008 or SBS 2011 standard domain, follow the similar guidance previously posted here: http://social.technet.microsoft.com/wiki/contents/articles/3298.terminal-serverrds-role.aspx Skip the part about installing, but pay attention to where the server has to be moved into the proper OU and the registry edit to get it to show up in RWA.
If you cannot get your workstations to connect via RDP to your Multipoint server, there's a good chance that all you need is to repair the RDS bindings on the assigned network card. And that's accomplished by running a slightly hidden WMS utility called ConfigWiz.exe. Login as the Administrator, flip WMS to maintenance mode, and then run %ProgramFiles%\Windows Multipoint Server\ConfigWiz.exe. Upon completion of the wizard, flip WMS from Maintenance mode to Normal mode, which will force WMS to reboot.
First, if you want to run WMS in a Hyper-V scenario, you will need the WMS 2011 Premium version; you cannot use WMS Standard. WMS 2011 Premium can be used as a Hyper-V host and/or a Hyper-V guest. Here is an excellent overview of implementing Multipoint in a Hyper-V scenario: http://blogs.technet.com/b/multipointserver/archive/2011/08/10/understanding-multipoint-server-2011-and-hyper-v.aspx
Not all zero clients will work with a virtual Multipoint Server. See below for a list of Zero Clients and support info. Brand/Model Works with WMS as a Hyper-V Guest HP T100 No (USB) HP T150 No (USB) HP T200 No (USB or USB over Ethernet) NComputing X550 Unknown NComputing U170 Unknown NComputing L300 Unknown NComputing M300 Unknown MCT 8840 Unknown MCT 9940 Unknown Wyse E02 Unknown Atrust M200 Unknown Atrust M202 Unknown Atrust M220 Unknown
Unknown, but most USB Credit Card Swipers are considered keyboard devices, so it should work.
Helpful tip: If you are using a VoIP phone system and are planning on connecting the zero clients to the phones via the ethernet jack on the back of the phones, you may experience intermittent connectivity problems, especially if you are using a different IP scheme for your phones. To work around this issue, program your Zero Clients with a static IP address, while directly connected to your switch (not through a phone). once you've programed it and assigned it to your WMS server, you should be good to go connecting it through a VoIP phone.
HP T150 Device Drivers: Drivers for the HP T-150 are on the HP site (click here). Go to Support, click Drivers, tell it "MultiSeat", select 6200, select WMS 2011, scroll down to Software Solutions. You can also use drivers directly from the DisplayLink site (click here). HP T200 Device Drivers: Drivers for the HP T-200 are on the HP site (click here). Please note: Do NOT mix T100/T150 and T200s on the same server - the drivers are incompatible with each other (this from the HP documentation on the T200). NComputing X550, U170, L300 and M300 Magic Control Technologies 9940 Video/USB/LAN client
Magic Control Technologies 8840 Video/USB client
Wyse E02 (based on MCT above) ATrust M200, M202, M220
WMS doesn't work with the following remote control tools due to the way it handles it's "Console" session and the SRCShell user. - Logmein - Crossloop WMS DOES work with the following - Microsoft Remote Assistance - Team Viewer - join.me
If you use custom login disclaimers on your network, this may conflict with WMS 2011.
Blog post here
http://www.microsoft.com/multipoint http://twitter.com/msmultipoint http://www.facebook.com/windowsmultipointserver Whitepaper on the Total Economic Impact of Windows Multipoint Server Pricing and Part numbers here Licensing info here Multiple Languages info here ISVs wanting to create WMS solutions check here
http://www.youtube.com/msmultipoint
Download Windows Multipoint Server 2011 Deployment Guide (Word doc) here Download Windows Multipoint Server 2011 Planning Guide (Word doc) here Download Intern's Guide to Setting Up Multipoint in Eight Easy Steps (Powerpoint) here
http://blogs.technet.com/b/multipointserver http://social.technet.microsoft.com/Forums/en-US/windowsmultipointserver
http://rdcompatibility.com/compatibility/Default.aspx?srv=4