• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups

    Installation & Licensing

    Reply
    Member
    FieldEngineers
    Posts: 3
    Registered: ‎05-15-2011

    Upgrading Vista to 7 - Forcasted problems

    112 Views, 3 Replies
    07-26-2011 05:24 PM

    I have a query regarding licencing/activation of Autodesk products, and what constitutes 'significant changes' to a system.

     

    We have an employee who has very happily consented to have his Windows Vista Business (32-bit) laptop upgraded to Windows 7 Professional.  He is running a 2012 Design Suite without problems.

     

    What effect will an upgrade (not clean install - time constraints) have on the Autodesk software?  Is an upgrade such a significant change that it will require reactivation, or reinstallation entirely?  I have read recommendations that a licence be exported/transferred before making system changes as a safeguard, but there seems to be no hard-and-fast recommended course of action.  Transferring a licence to a "new machine" seems to be asking for problems too (or maybe this only existed with the older PLU).

     

    Having successfully completed the quick-and-nasty Vista to 7 upgrade previously without problems and in record time, I'm interested to hear how others have achieved this and how it affected their software.  This information is always better to have before the upgrade starts.  Given this is borne of "time constraints";  if the Autodesk software is going to cause known problems, a reschedule may be in order.

     

    Thank you,

    Hannah

    Please use plain text.
    Product Support
    Posts: 861
    Registered: ‎06-18-2008

    Re: Upgrading Vista to 7 - Forcasted problems

    07-27-2011 01:03 PM in reply to: FieldEngineers

    You can use the License Transfer Utility to upload the license file to our servers so that you can re-import it to an newly formated computer.  You can also try to re-activate the software and it doesn't automatically activate, you can contact the Autodesk Business Center with your serial number and request code.

     

    http://en.autodesk.ca/adsk/servlet/index?siteID=9719649&id=9830778

     

    For WIndows upgrades, I would prefer a clean install.  I am glad that the Vista upgrade to Windows 7 was relatively harmless but be prepared for a clean install at some point in the future.



    David Lau
    Product Support | Up and Ready Blog | If my reply was helpful, please Kudo or Accept as Solution. :smileywink:

    My 5 Top Issues in the Discussion Groups

    1402 Error [Uninstall] | Faro doesn't install | adlmPITSetProductInformation Errors | Empty Tool bar in AutoCAD Mac | Win 7 Registry Limit
    Please use plain text.
    Member
    FieldEngineers
    Posts: 3
    Registered: ‎05-15-2011

    Re: Upgrading Vista to 7 - Forcasted problems

    07-27-2011 03:25 PM in reply to: david.lau

    David, thank you for your response.

     

    While I'm aware that one can use the licence transfer utility in upgrade cases, there is a chance that the operation will be an offline one (as mentioned - quick and nasty), which I why I'm enquiring as to the effect a change in operating system has on the licence. 

     

    While a reformatted computer requires the licence be imported or reactivated, I would like to know whether an upgraded hard disk (same disk and many of the same system files) will require reactivation or importation. Is there a consistent/expected outcome, or is this largely a case-by-case situation?

     

    Thank you for your time,

     

    Hannah

    Please use plain text.
    Member
    FieldEngineers
    Posts: 3
    Registered: ‎05-15-2011

    Re: Upgrading Vista to 7 - Forcasted problems

    08-30-2011 02:27 PM in reply to: FieldEngineers

    To address the concerns of anyone who may have found this thread relevant to them -

     

    The Autodesk software continued to work as expected after the OS upgrade.  The upgrade itself was not as smooth as expected, asking for a lot of uninstallations of .NET components, but none of this ended up affecting Inventor.

     

    Thank you to David for his contribution to this thread.

    Please use plain text.