jspreha
join:2002-02-02
Harrisburg, PA
| reply to lcompton
Re: magicJack & Hewlett Packard T5710 Thin Client
Holman -- Thanks for the comments. I think that pretty much puts to bed my already accepted position -- that I'll be bringing my TC up to a 512/512 configuration.
said by lcompton  :My recommendation is to inhibit updates for anyone using (and managing their own) a Thin Client solution. At the very least this places control of the update process entirely in the hands of the end-user. This is exactly my rationale -- especially on a TC. |
|
mozerd
Light Will Pierce The Darkness
Premium,MVM
join:2004-04-23
Nepean, ON
| reply to lcompton
said by lcompton :This doesn't make sense to me. DirectX is not a codec at all. DirectX is not a codec ... its strictly an API that has significant abilities that enable a programmer/developer to exploit the OS's interaction with specific subsystems that also include how codecs are used. It is not clear to me [nor do I really care] how magicJack exploits DirectX ... and in fact I do not believe that magicJack write the code -- it is my opinion that TigerJet are contracted by magicJack to do stuff on behalf of magicJack.
said by lcompton :I didn't notice any changes in sound quality with the updated software. I did notice an improvement in sound quality.
Microsoft DirectX
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
mozerd
Light Will Pierce The Darkness
Premium,MVM
join:2004-04-23
Nepean, ON
| reply to jspreha
said by jspreha :said by lcompton :My recommendation is to inhibit updates for anyone using (and managing their own) a Thin Client solution. At the very least this places control of the update process entirely in the hands of the end-user. This is exactly my rationale -- especially on a TC. FYI, the magicJack software application was designed to dynamically update itself on demand and if you prevent it from doing so the consequences are yours to bear.
My observations are that magicJack/YMAX are making frequent changes to their network and software. The software changes IMO have a direct correlation to the changes that are made to the network/servers and how the magicJack software interacts -- so at some software update cycle if magicJack mysteriously stops to work on your TC because you've prevented the update from taking place you level of frustration with Why will rise. My suggestion is to not prevent magicJack software from updating when called to do so.
--
David Mozer
IT-Expert on Call
Information Technology for Home and Business |
|
jspreha
join:2002-02-02
Harrisburg, PA
| said by mozerd :My suggestion is to not prevent magicJack software from updating when called to do so. In this case you are damned if you do, damned if you don't.
IMO, the scenario where the MJ update breaks the TC setup is, more frequent than an update being pushed down from MJ/YMAX that is not backward compatible across all of the magicjack installations. I can't imagine that MagicJack would roll out a new software revision that cut off every single user in their userbase until they upgraded.
When that does happen, then I'll manually push the update to the TC. I'll continue to keep my auto-update ability off on my TC (once I get it working). |
|
lcompton
join:2008-05-04
Exton, PA
 ·Verizon Online DSL
|  reply to mozerd
said by mozerd :said by jspreha :said by lcompton :My recommendation is to inhibit updates for anyone using (and managing their own) a Thin Client solution. At the very least this places control of the update process entirely in the hands of the end-user. This is exactly my rationale -- especially on a TC. FYI, the magicJack software application was designed to dynamically update itself on demand and if you prevent it from doing so the consequences are yours to bear.
Good evening, mozerd.
The facts and available evidence to date clearly show that magicJack updates are initiated by a magicJack restart, which can be accomplished in any number of ways, but is generally user-initiated.
Additionally, it is a fact that not all magicJack software updates are triggered for auto-deployment on magicJack device restarts. The folks at magicJack seem inclined to reserve triggered update deployments for the significant improvements (such as the infamous 11 June update.)
said by mozerd :...so at some software update cycle if magicJack mysteriously stops to work on your TC because you've prevented the update from taking place you level of frustration with Why will rise.
This assertion is simply unsupported by the facts and available evidence to date. The fact is that there are many people still running older versions of the magicJack software because they are unable to get the latest version to function on their Thin Clients. In a number of cases, there are people who simply haven't upgraded their Thin Client memory to accommodate the latest magicJack upgrade software requirements.
In the unlikely event that magicJack did decide to block out an entire class of software releases from interoperability with their servers, I would think anyone inhibiting magicJack software upgrades would be keenly aware of where to look first.
said by mozerd :My suggestion is to not prevent magicJack software from updating when called to do so.
In the final analysis, it will be up to the readers to decide which strategy they use. However, I'd be willing to bet that inhibiting updates is absolutely the lesser risk of the two available choices where Thin Clients are concerned.
Do have a lovely evening. 
Thank you.
Lisa |
|
HolmanGT
Premium
join:2001-11-20
Saint George, UT
 ·Baja Broadband
| reply to mozerd
Mozerd,
I just have to say Amen brother. I got chewed by someone that didn't think it was a good idea to allow auto updates.
I am with you on the keeping the frustration level down and allowing the Pros to do what they think is in the best interest of themselves and their customers.
And I will quote myself, this last major update from MagicJack while it took a little work to resolve on an HP thin client is better than sliced bread.
When I am talking to someone and they pause in their thought for a little longer time than I am expecting I have to play Virizon (or whomever said it)game "Can you hear me". The line is so God awful quiet when no one is speaking I am never sure it the call has been dropped. But that is a good thing.  |
|
jss1008
join:2008-03-06
Los Angeles, CA
1 edit | reply to lcompton
Hi Lisa, HolmanGT:
I have recently bought s magicjack to use as my main phone service. It has been working great except that I think the overall performance of my laptop which is my main computer is being compromised being left on 24/7, so I bought an HP thin client T5710 from ebay and just received it.
Problem is that, not being a techie, I am at a loss on how to configure my new TC with magicjack.
Being that my main computer is a laptop, can I use it to manage my TC? I wouldn't want to have to spend more for a keyboard, monitor and mouse to manage my TC.
Also, I will appreciate it if you can provide a step by step procedure for how to prepare the T5710 for use with MJ.
Thank you so much and hope to hear from you....
John |
|
booyah5
join:2008-08-09
La Habra, CA | reply to lcompton
I've read some folks are using Teamviewer. I don't know if there is some special things you gotta do to install stuff on there computers. |
|
