2017 Migration machine to machine

[TRLitsey]

ACE 2014 > 2017, all workstations Win 7 64-bit, projects are on the network but all ACE and ACE support files are installed on individual workstation.

Hi there,

I have seen similar questions but I want to be very explicit as I have been looking at how to do this for a few days and have not found the procedure. I used the migration tool on my workstation this afternoon.  It took 1-1/2 hour for the transfer from 2014 to 2017.  So far I like what I see.  There are a total of 4 ACE workstations in this office.  Mine is the heaviest with customization so the goal is to make the other three look and act like mine.  Up to ACE 2014 I would have copied the dozen or so files/folders to a jump drive and pasted them into the other workstations.  Will that work with 2017?  Or is there a slick way to create a migr file with all the pertinent data files?  I would like to select all the options and just say ‘go build a file for me.’  With what I have found it does not work that way, I have to select each file/folder one at a time and add them to a folder one at a time.  That is a real pain because IT has installed ACE with something other than standard default setting so files can be hard to find.  Is there a better way?

Thank you

I would like to grab these in one fell swoop:

[rhesusminus]

Sorry, but there are no quick ways på "extract" these files, and "paste" then onto another computer.
But you gave me an idea for a tool for my toolbox 🙂

[dougmcalexander]

By customization do you mean menu customization maybe?  If so you only need the acade.cuix and acad.cuix files, and the Images folder.  For my customers I have the IT group include a login script that copies such files, and any others they wish to share, from a network folder to each workstation.  As the CAD manager or lead designer modifies their files, he/she uploads them to this predetermined network folder, so the next time everyone logs in they automatically get the latest version of each file and any new icons from the Images folder.  Some of my customers even do this for menus and report format files, just to keep them on the local computer.  This is especially helpful since the Automatic Reports generator only looks for Report Grouping (RGF) files in the User folder.  I have a request on the Idea Station to force the Automatic Reports generator to look for the RGF files in the same folder with the .SET files, in case I have edited the WD.ENV file to instruct the software to look for them in a network folder.

[TRLitsey]

Hi again,

Thank you for the replies. Our department is small enough that IT will not setup a network configuration for us.  Up to ACE2014 I would copy my files to my folder on our network.  Goodies like menu(s) with added icons, added .dwg smart symbols, excel file with added wire way and manufactures, catalog with added components, etc.  The few other folks using ACE would copy those files to their workstation every month or two and use them to replace the corresponding files on the individual workstations.  It is my understanding that this method will create problems because of file structure differences for 2014 to 2017.  The migration tool worked just fine on my workstation going from 2014 to 2017 but I am have a bit of a challenge as to how I can get those updates onto other workstation, especially the workstations that have only 2017 installed.  They have nothing to migrate from.  Once upon a time I had a laundry list of files to move/update other workstations, I am leery that this list of files will not work or has changed with 2017.  I have found that I can copy the default_cat.mdb from one 2017 workstation to another 2017 workstation but I am afraid to try it on any of the other files/folder.  I would like to update my peers but I just don’t want to let all the good smoke out.

Any advice is welcome

Thank you