In Multipoint 2011 you were allowed to install Multipoint, rip out its guts and then install it as a child.  It kinda sorta made some sense when you were in the 2008R2 era as it saved the price tag of a GUI server OS to control a virtualized Multipoint.  But in the 2012 era it’s more of a ehhhhh do you really want to do that? and a ehhhhh should you do that?  Remember in the 2012 era you get a 1+2 virtualization right, not the 1+1 you had in 2008 r2.  So you already get a spare in the parent GUI 2012.

Also there’s more hoops to jump through to get RemoteFX working on server 2012. 

So while one CAN still install Multipoint 2012, rip out the guts and make it a base operating system for virtualization… the better question is… why not plop down a Server 2012 as your virtualization base?  It’s a better decision to do virtualization the right way.

So have a thin client where the user normally has a fujitsu usb scanner connected to a XP workstation.  And we’d like to keep the scanner there so we can have the ease of use for the user.  But how does one connect a scanner to a thin client that is hanging off a Multipoint?

So here’s how you do this… Step one get this –  There’s two parts of the software  – one is for the server one is for the client.  But you don’t install it where you think you might.  The “Server” is installed on the THIN client along with the scanner driver.  Because the thin client is a Win7 embedded and I got a “plus” version there’s enough room for this driver. 

You then install the “Client” software on the MultiPoint server. 

Next you go to the thin client and figure out what firewall port that the scanner “server” is talking through.

On the thin client there’s a “help about” on this remote scanner software and inside it says what port it’s talking to. 

Go into the firewall on the thin client and poke a hole through port 6077 (and check to see if your port is the same as that).  Now do the same on the MultiPoint server.

Now launch the software on the Multipoint and it should find the Remote-scan scanner.  You have to hit edit and add the “Hostname” and save the name.

Go into your application, in this case Adobe and in the “scan to scanner” you’ll now see that you can connect to this remote scanner and it will scan just as if it was physically attached to a normal workstation.


This is where you need to understand what each person does and what apps they use.  Need more options go with the thin clients.  Need less options?  Go with zero clients.

One nice advantage to thin client and multipoint is that it forces you to really design a much better managed network.  No more local admin rights, no more loosey goosey permissions, you make sure you are setting up a network right.

So got my multipoint set up (more on that later) and starting to set up the thin clients.  First lesson, don’t accidentally pull out the power cord as one is first setting up and if they are a Win7 embedded (they are) and you pull them out right at the time they are building the os you now have to find media on the HP site, build a usb flash drive/bootable thing and rebuild your thin client.

Next lesson… even though these are “thin clients’ they are still Windows machines, just with more locked down access.  So things like joining the domain isn’t as obvious as you think.

Domain or not for thin client? – Spiceworks:

What you do is you log into the thin client with a username of Administrator/password of Administrator and go into the control panel and manually join the client to the domain… BUT.. you don’t reboot.  You merely change the name of the thin client as you want, put in the domain stuff, say NO to reboot and then look in the system tray for the tiny green button.  The what you say?  The green HP ‘commit this to the image” button.

Right mouse click on that tiny green button down there and you see there’s a “Commit”.  That “commits it to the tiny little  c drive.

Now on the train home from the Sacramento IT pro group (see photos posted up on ) and here’s the answer to a couple of questions that came up…

Can you put Quickbooks on MultiPoint?

Answer:  Yes.  Officially speaking the party line of Intuit is that they will support Quickbooks Enterprise in a terminal server environment.  But here’s the reality of the real world.  Quickbooks Pro (non enterprise) works just fine in a TS environment. I’d recommend that you use the CUTEPDF writer instead of Intuit’s native pdf printer, but it-does-work. 

Can you put Lacerte and Lacerte’s DMS on MultiPoint?

Answer:  Yes.  Both Lacerte tax program and DMS are supported in a terminal server environment.
Although it is normally installed locally, Lacerte can be used in a Citrix/Terminal Server environment, if the firm has access to the IT expertise to set it up, providing remote offices or staff with access to the system

Bottom line MultiPoint is a terminal server box.  It it will work on TS, it will work on MultiPoint.

Just added an item to the MultiPoint wiki

Needed hotfixes
The SBS blog has posted regarding a needed hotfix that ensure that RDP connections will not be dropped.
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.

I just read over on the SMBMVP Tour blog that Dean Paron will be down in Los Angeles next week to discuss MultiPoint.

Now before you say …but Susan… to get into the WPC with a price tag of $2,000 to attend, that’s way out of my price league.  Quite honestly I understand.  I’m in my “cheap bastard” mode this year as we all are, and you aren’t alone in the feeling that it’s hard to justify $2,000 to attend.  One way to hear and see about MultiPoint is through the SMB MVP tour.  If you are affliated with a Partner group, ask them if they are making arrangements to have the tour come to your venue.  But there still may be a “cheap bastard” way to see Dean Paron in action…. I think … and I am confirming …that a $75 Expo only pass may get you into the area of the convention center to catch his sessions.  For those in the LA area, you might want to check out the options for a single day pass of $750.00 or an expo only pass.

One thing you can do on multipoint server that you can’t do on any other one is to join the multipoint server to the SBS Essentials domain using http://server/connect.  No other server OS can do this.

You are prompted to turn off the autologin


And there you go.. a multipoint server joined to a SBS Essentials domain to provide TS in a quick easy setup.


So far the multipoint server looks easier to know where/how to enter the cals for the RDS/Multipoint sessions.  Remember you need multipoint cals and Windows server cals IF you are in a normal network, but in a SBS Standard one, the Windows cals are covered by the SBS standard cals.

Don’t forget to watch this video as well:

So when the multipoint finishes the wizard we’re now set to set up the multiple workstations.

We then get to log in

And now on a Win7-ish background the console loads up

This is where you start to see the MAJOR bling of the Multipoint server.. this is where it’s the Las Vegas glitz version of Remote Desktop Services

For those of you with SBS-Standard and Essentials that console showcases that MultiPoint is a cousin of the family.

It’s here in this console that you get to control all the workstations/Remote Desktop/Terminal Server sessions in an easy to control console.

(more later tonght – have to clean up the house and garden a bit)