Tag Info

Hot answers tagged

11

Major benefits of thin clients include: No need to upgrade machines in order to get more processing power Software upgrades and licenses are handled centrally User data, work products, are all centralized - no need to suffer loss when an indivdual PC goes out Virus issues, and many other factors, are better controlled from a central location Ease of ...


11

We're happily using a combination of Vine Server for OSX and JollyFastVNC for the clients. Vine Server provides for a "personal" VNC server instance on a unique port number for each logged in user. The only trick is that the user needs to be already logged into the Mac with VineServer running under their account to be able to VNC in. The solution for the ...


8

Take a peek at Aqua Connect Terminal Server. It provides multi-user OSX to clients via RDP, VNC, and X11.


6

Why upgrade? are you having problems with the current setup? are there new requirements? 3-5 yr old machines are just fine for web browsing. If the HDD's start going, or you'd like to lower maintenance overheard then switch to a linux live CD distro that's a web kiosk. Firefox kiosk plug-in. Easy to setup LiveKiosk distro. Make sure that the apps work ...


6

First thing you'll need to decide is if you want VDI or Terminal Services. VDI runs a whole "machine" for each user. Typically these "machines" are actually VMs on a ESX or Hyper-V host, but other solutions exist, including ones where they're connected to rack-mount workstation blades. For Terminal Services you'll have multiple users connecting to Terminal ...


6

It is a terminal server, with thin clients connected to it via a "dumb" machine (offers basic networking, video and mouse/keyboard input). Everything is living off of one server that everyone shares, and is therefore managed by an IT department. The clients connect (usually) with the RDP (Remote Desktop Protocol) used by Windows Servers, although there are ...


5

As of OS X Lion this is supported by the built-in Screen Sharing, if you have set up multiple accounts: Per-user screen sharing You can remotely log in to a Mac with any user account on that computer and control it, without interrupting someone else who might be using the computer under a different login.


5

Verveguy, I just set this up using Vine Server, works well. Since I'm using this computer solely for terminal purposes, I created a script that automatically does a fast user switch once you log in. #!/bin/bash /System/Library/CoreServices/Menu\ Extras/User.menu/Contents/Resources/CGSession -suspend I put that in a /opt/fastswitch then in Terminal did, ...


5

Check out Thinstation. I've used it in the past to create a CD bootable version for use in machines without hard drives. It's worth mentioning that I've come across two distinctly different systems with the name Thinstation.


5

If "thin clients" is using RDP to connect to virtual desktops within a Remote Desktop Server, then no, your SBS could not do it - there is a licensing and and a technical limitation which would prevent you from configuring it in this way. KB828056 says: To deploy Terminal Server on your Windows Small Business Server 2003-based network, you must install ...


5

You need to add a "Predefined Option". The UI is mostly the same as it was in Windows Server 2008 R2. From the DHCP management console, right-click the the "IPv4" node, choose "Set Predefined Options...", and click "Add" to add the new option definition. If you'd prefer to do it from PowerShell have a look at the Add-DhcpServerv4OptionDefinition cmdlet. ...


4

We use thin clients for our call center workforce a few years back. The price of them was far less than actual PCs and when one broke we just replaced it with a new one and sent the broken one to the manufacturer. They really shine when you have situation where the end users don't need to do much on their system, like run a call center web-app and a couple ...


4

I worked in a manufacturing environment that would constantly kill normal PCs due to metal dust and heat. Thin-clients were great in this hostile environment because even if one failed, it was easy to replace. Also, power spikes to due high voltage equipment may burn out a thin-client, but none of the data was lost because it was being run from a separate ...


4

I've never used it myself, but it sounds like Thinstation or maybe Thintux is what you are looking for. If you want to get more complicated, the Linux Terminal Server Project might be interesting also.


4

You probably have a pair of scissors somewhere; that'll block peer-to-peer software without costing anything, installing a firewall, or installing any software on a server.


4

It sounds like you don't have an Active Directory domain if you're "walking to the desktops outside our business hours" (sic). Simple solutions are better to my mind. Something like wpkg might be a better fit than the solution you're proposing. Rather than trying to abstract away the desktop computers, why not just manage them more effectively? Some decent ...


4

This entirely depends on what you're doing with your users. 20 VM's is going to be HARD on the server. A lot of memory, a lot of disk use, a lot of network use...I'd not try doing that. Terminal services are something we used to use. We could support on decent hardware about 15 to 20 sessions at a time. Problems...multimedia was crap, Office needs special ...


4

Virtualization for this is a bit much. There's a few options and it depends on the systems that are on the floor. You could go with the Linux Terminal Server Project (LTSP) or a NFS root setup, or a ramdisk image, or, or... it goes on. Also, is the Chrome browser the only one it works with? Will it work with any web browser? If so there are actual ...


4

No loopholes. Pay for the licenses you're going to use. Microsoft has built a good platform that you obviously benefit from as a business. Compensate them for their work as you would want your clients to compensate you for yours.


4

You will need to create a zone (primary or AD integrated) for ftp.hp.com. Then create a parent host record (A with no name) that points at 10.10.10.50. This should allow the server to respond to requests for ftp.hp.com without causing problems for the rest of the hp.com domain (except sub-domains of ftp.hp.com).


4

Mounting the root FS via a WLAN for 60 clients will never work in a even remotely sufficient manner. WLAN is a shared medium and it just doesn't have the capacity for this. Doing this via a wired connection is possible, but still requires many considerations, but with a wireless connection it's just not feasible. Well, maybe you could get it working ...


4

AppLocker and Software Restriction GPO policies will allow you to whitelist individual applications and prevent the launching of all others. Then, you can lock down the computer using other common GPOs like removing the run menu, disabling task manager, hiding control panel applets, etc. Also, use a policy to make outbound firewall rules that only allow ...


4

I fear that you may be having a problem with "licensing". I saw something similar with a couple Wyse thin clients but rather than troubleshoot the issue the Customer just opted to replace the hardware (because they only had two of the devices). This long thread on social.technet.microsoft.com is filled with users having a similar experience. The users there ...


4

If these are going to be critical tools for your users, then you need to build something resilient. A single SBS 2003 Server isn't going to be either resilient or powerful enough, so you are looking at something that clusters. You have a lot of choice. But before you start down this route, with only 25 clients and running SBS you seem like a fairly ...


4

Get Software Assurance licensing for the 300 PCs, install Windows Thin PC. Use GPO to configure: Windows Firewall Certificates (To install your Code Signing Cert) RDP Pass-Through Authentication. I like to also configure the Remote Registry service to Auto Start (Delayed), makes some maintenance easier. Set the users shell to a script in the netlogon ...


3

Never used that particular model, but typically, you may find the flash attached as either a MTD or IDE device. If you open it up and find that it contains something like a Compact Flash card, it is most likely connected to the IDE and can be used just like any other IDE drive. That would be your easiest way to flash it. If you open it up and find that it ...


3

RDP-TCP Listener does in fact represent the protocol and the biggest side-effect of resetting it while endusers are logged in is potential loss of data, this is also why it is not recommended to just use the shutdown button on a terminal server. Instead, it is best to utilize the tsshutdn command so that you can notify all users that they will be logged out ...


3

Coderebel makes iRAPP Terminal Server. Unlike Aqua Connect Terminal Server (ACTS), the price is listed on the site which is $298 as of this post. iRAPP currently supports Snow Leopard while ACTS says "a fully compatible version... is not currently available at this time." I haven't tried either but wanted to add the info I found to this question.


3

ChipPC Extreme PCs have dual and quad screen supporting models. After running an environment with lots of Wyse and HP and even testing some Igel clients - ChipPC is by far my favourite thin client platform, for what it's worth. They're easily integrated with Active Directory using their management platform - never got around trying their Linux versions ...


3

We run under peak load about 50 users on a single RDS, and a lot of it depends on whether or not you enable the "Desktop Experience". Desktop Experience runs best under 32-bit colour (default is 16-bit), and loads a lot of additional bitmaps. We keep it disabled, but our users have a traditional desktop for these duties. For a thin-client that might be worth ...



Only top voted, non community-wiki answers of a minimum length are eligible