Why can't PublishWave Run on a Server OS?

BCranstonBCranston Moderator Posts: 34 mod

Why can't PW install on a server OS?  I would like to get it off a desktop computer and integrate it within my highly managed server architecture.  It is a pain maintaining it as a separate piece of hardware. PublishWave is an important part of our Adept infrastructure but is a weak link in the chain because of OS requirements.



  • Joe.GasperJoe.Gasper Member Posts: 4
    Our original design of PW did support both workstation and server OS's. Then, Autodesk started prohibiting the installation of some of the CAD applications on server OS's. Since PW uses these CAD applications to produce the output, we could no longer support PW on an OS where the CAD application was not supported. Therefore, PW is only supported on OS's where the PW CAD applications are supported.
    Joe Gasper
  • BCranstonBCranston Moderator Posts: 34 mod
    Hi Joe,

    Upon review of the EULA for Product Design Suite Ultimate I am unable to find exclusion to VMWare based Server OS's. (Granted, I'm not a legal scholar).  That OS is not supported but that is not the same as an exclusion.  Autodesk specifically defines a computer as real or virtual in Exhibit A of the EULA.  And then the various license types use the word "computer" in their definitions in Exhibit B.  I attached the EULA for review. 

    I find that running PW on a desktop OS is less than ideal.  The desktop OS's are subject to updates and other service interruptions not present in a server OS environment.  I need to get my PublishWave server into the hardened server infrastructure to take advantage of backup and fail-over technologies.  PW on Windows desktop is the only weak link in my Adept topology.  Please reconsider the current strategy.
    1) Allow PW to install on server os's.
    2) Run PW (and P2A, etc.) as a service to avoid having to stay logged into a user account.

    -Brian Cranston
  • jtomejtome Member Posts: 25
    Brian, I don't know if this helps your situation or not but I'm running PW on virtualized Win 10 inside Azure and it's been very stable.  Yes still workstation OS.

    I agree that it would be great to have PW run as a service.  It's annoying to have to log in to ensure that it is running after we do a reboot of the VM.

  • rnettlesrnettles Moderator Posts: 11 mod

    James, thanks for your comment. I'll look into an Azure hosted solution as well.  Were there any specific traps to avoid with your implementation?


  • jtomejtome Member Posts: 25
    It takes a knowledgeable IT department to embark on a hosted solution, especially with Azure.  I don't pretend to know all the details.  Our company uses O365 and therefore some part of Active Directory is in the cloud too.  There's a bug that Microsoft has acknowledged that doesn't allow authentication from Adept for a newly imported Adept user (when using AD) until the user has changed their O365 password.  It's annoying, but not a show stopper.

    Hosting isn't cheap and adds to the monthly operating expenses; so have a good case to take to management if you're going that route.  We're probably moving out of Azure later this year (because of costs) and building our environment on in-house iron in VM farms.

    We've got some other AD headaches, but it's not because of Adept or Azure, it's because the parent company acquired a lot of others and the IT department can't get caught up enough to put everyone in one AD.  Mergers and acquisitions... a fact of life these days.
Sign In or Register to comment.