Re: Silent service pack install for Client Access for Windows

I agree completely, Rob. In fact, we know already that the java based
client solves the issue that we are hoping the service pack for the Windows
client would solve. Apparently, there is a fear of something, anything
breaking during the silent install of either the Java client or the service
pack for the Windows client that would cause downtime for any of our 200+
service reps, and we are required to avoid that at just about all costs.
So, management isn't willing to take the risk. I guess this means we'll
never upgrade our Windows clients to WIndows 10. The only way forward, it
seems, is that someone would need to come in on Sundays to manually deploy
the Java client and run a series of tests. Pigs will fly before that
happens.

- Dan

On Fri, Jul 21, 2017 at 12:21 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Dan,

I think that one of the huge reasons for going to the java based client
was that Microsoft kept slapping the cones of silence over things like the
service pack install that you have to be a local admin, etc. It pretty
much made it inoperable.

Make the move to the java client.

Now if someone else can help you figure out the java client roll out, with
a minimum of hands on, all the more power to them.