We went live with 17.0 last week at Sweetwater. A few gotchas and glitches, but ready for deployment in my opinion. Like you, this is our only window for a big upgrade during the year.
Our issues: - The new network layer has taken a step back from v16. Performance died at about 400 users/2000 processes. Version 16.3 HF2 could handle our load of 600+ users/3500+ processes. Luckily the old network layer is available in v17 for all platforms, which seems to be fine. - Issues on 64-bit Windows printing compared to 32-bit - for us this is with Zebra label printers (using the Designer driver) as well as printers with multiple bins. We'll have to dig into this more, but 32-bit Windows is fine. - There's a weird issue with cloned VMs or machines created from a master image that didn't exist in prior versions. If you see cloned workstations drop off the server when another clone connects to the server, you'll need to either create a new user account or reinstall the OS from scratch. We've seen this on both Mac and Windows now. On Windows, it was with 8 VMWare virtual machines that were all cloned from a master VM. On the Mac, we saw it in a department that had 9 iMacs that were all imaged from the same source. Other than these initial issues, Everything Seems OK™.... -- Jeffrey Kain [email protected] > On Jul 22, 2018, at 10:57 PM, Jim Crate via 4D_Tech <[email protected]> > wrote: > > Everyone that responded mentioned new projects. Has anyone pushed a legacy > project from v16 to v17 into production with 4D Server with 20 or more users? ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
