ASEM6300T from Allen-Bradley

Reduce Your Organization’s Risks to Stand Apart from the Crowd

The proliferation of the Internet has created the largest interconnected network of machines the world has ever known. Our connected world is so complex that no one person or group understands everything that is needed to maintain the network and keep it in a healthy state.

The effort to maintain the network as “up” is constant. No matter where you live, someone near you is working right now to prevent something or stop something from losing its connected state. They may work just as tirelessly to get something back online that has lost its connection to everything else.

Of course, most of us never concern ourselves with these issues until we lose our connection to everything else. This scenario recently happened when many woke up to the CrowdStrike outage that caused major business disruptions over the last few weeks, especially for airlines and healthcare agencies.

This is a Big Deal
This issue is a big deal because it demonstrates the real dangers, and highlights the fragility, of a connected world of computers. Almost all these computers have an operating system. If you are unfamiliar, the operating system, or OS, is the intelligence behind every computer.

Even though operating systems are all around us now (PCs, phones, cars, etc.) most of them get updated automatically. The average person does not, and will not, take the time to manage this task manually. Many businesses cannot manage this job any better than individuals. This fact is why businesses like CrowdStrike exist. These datacenters oversee computer systems used by third parties. These third parties rely on their providers to take care of managing and distributing these updates in a planned, secure manner. Good news – this system works most of the time!

The problem is, when it fails, the failure can be wide and catastrophic. The recent CrowdStrike issue is being called the largest outage in IT history.

So if we know that any device connected to a network is exposed to the possibility of being compromised, what steps can organizations take to mitigate the risks associated with a fully connected enterprise? Since making everything less connected is not an option for most businesses, other solutions must be sought. [...]

MailBag Friday (#20)

Every Friday, we dedicate this space to sharing solutions for some of the most frequently asked questions posed to our ThinManager Technical Support team.  This weekly feature will help educate ThinManager Platform users and provide them with answers to questions they may have about licenses, installation, integration, deployment, upgrades, maintenance, and daily operation.  Great technical support is an essential part of the ThinManager Platform, and we are constantly striving to make your environment as productive and efficient as possible.

 

 

I’m observing a strange behavior with our Terminal Server operating ThinManager in a Virtualized environment. I have found the users profile is duplicating and haven’t found the reason.  There is no domain server, no change in server name, and no change in configuration. It’s just happening randomly in each thin client with the following message:

“…. The user manually logged off…”

The real problem is the app that the thin clients displays uses files stored in the profile folder to configure some parameters. So, every time this new folder profile is created… my app stops working correctly.  Any Ideas on what is causing this?

 

 

The problem is caused by a bug in the VMware tools “shared folder” feature. Such feature is installed when VMware tools are installed with the “Complete” option. When a user logs off, the Terminal Server tries to copy the hgfs.dat file back to the profiles folder but the operation fails because VMware keeps the file locked with exclusive access. When the user logs in again, a new and duplicated user profile folder is created.

You can view this page for more information:  http://www.desktapp.it/?p=120

-TM

_______________________________________

 

Our existing clients automatically connect/try to connect to the Thin Manager servers. Can we leave them running while performing an upgrade on the servers? I know they will be disconnected and will keep trying to reconnect, but when the upgrade is done will they re-connect themselves? 

 

 

Yes, it is possible to leave the thin clients on while Thin Manager is being updated. Once ThinManager becomes available, they will reconnect.

-TM

_________________________________________

 

I am having an issue with my Security Network policies restricting access to specific ports.  Is it possible to use a different port for TFTP? 

 

 

No. Port 69 is the standard port as defined in RFC 1350 for the TFTP Protocol.  Please see the enclosed link for further detail on TFTP.

http://tools.ietf.org/html/rfc1350

-TM

_______________________________________________________

 

There used to be an ACP enabled PCI card that could be installed in a PC to turn it into a thin client.  Is this still available for purchase?

 

You are referring to ThinAdaptor, which we no longer sell. We do support PXE booting as of ThinManager 5.0 which would turn any PC into a ThinManager ready thin client.

-TM

______________________________________________

 

To review the cost savings of using the ThinManager Platform, visit our ROI Calculator here.

To read about successful ThinManager Platform deployments, visit here.

To see when the next ThinManager 2-Day Training Session is being offered, visit here.