• RE: Need help with creating SSL certificate

    I forgot to run as administrator.

    What is the usage of: Subject Alternative Name (SAN)?

  • RE: Need help with creating SSL certificate

    Here's what happens to a test on Server 2016:

    New-SelfSignedCertificate -Subject "localhost" -TextExtension @("{text}DNS=localhost&IPAddress=")

    New-SelfSignedCertificate : CertEnroll::CX509Enrollment::_CreateRequest: Access denied. 0x80090010 (-2146893808
    At line:1 char:1
    + New-SelfSignedCertificate -Subject "localhost" -TextExtension @("2.5. ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [New-SelfSignedCertificate], Exception
        + FullyQualifiedErrorId : System.Exception,Microsoft.CertificateServices.Commands.NewSelfSignedCertificateCommand
  • RE: Need help with creating SSL certificate

    I found a PowerShell command that works for Server 2019, but will not work for 2012 R2, to create a self-signed certificate that worked.  Anybody have one that will work for 2012 R2?
  • RE: SSL certificate details for Cloud/On-premise synchronization-1516116891

    Where did the certificate come from that you imported?
  • Need help with creating SSL certificate

    I'm trying to get our customer's ahead of the change coming in Chrome next month.  I followed the instructions referenced by DocuWare Tech Support about creating a self-signed certificate from Sophos.  I am able to use https to login to the web client, but Chrome still reports the site as 'not secure'
  • RE: Please stop mistreating existing customers

    So that would be like saying we will only support on-premise systems running on IBM servers, but not on Dell servers.

    The mention of 'network multicasting outside of transit gateways' only applies to customers who use multi-server deployments.  So just say that multi-server deployments environments aren't supported.

  • Please stop mistreating existing customers

    You may not be aware of the recent change at DocuWare Corporation that precludes DocuWare 7.4 from running on AWS environments or in a Terminal Server environment.
    It was cowardly of DocuWare to not mention this fact during the recent DocuWorld sessions!  I’m sure they were afraid of a mass mutiny.
    The reason behind this action is to try to force any customer with plans to move to a cloud environment to utilize DocuWare Online.
    Our concern with the whole DocuWare Online approach, is that DocuWare is severely penalizing their existing on-premise customers.  We have large customers who have been paying regular support for twenty years, after spending large amounts of money to purchase the server license and user licenses.  Now DocuWare wants them to scrap all of that investment, without any allowances, to repurchase all of their client licenses, which can no longer be concurrent, along with a much higher monthly cost than they have been paying.  Not only that but the process to perform the migration is so daunting, it will be another major investment for the customers.  Besides the fact that DocuWare Online comes with many modules that many customers do not need!
    Since, these customers will in effect be starting over, they might be very tempted to source a competitor’s product, which hasn’t left a bitter taste in their mouths.  I know if a was a salesman for a competitor, I would certainly be knocking on the door of any DocuWare customers.

    And if a current customer is utilizing AWS or a Terminal server environment, they aren't able to even upgrade to DocuWare 7.4, so tht they could migrate to DocuWare Online.
  • RE: Export to CSV File Issue - To Excel-1530181630

    I can't seem to find the forum topic listed.