Can anyone help me create a certificate to use with the new version of Remote Desktop Connection Manager v2.7? I see the new version removed the "Store as plain text" option, but added using a certificate to the list.
I was wondering if anyone knew how to create a certificate (self-signed or whatever) that I could install on both computers to allow me to pass the config file between machines. I haven't been able to find anything online!
Thanks in advance.
If you in Remote Desktop Connection Manager click on the Help menu, and Usage, you will see a web page. On the Contents list, click on Encryption Settings (Under Local Options). There you will see how to create a personal certificate that RDCMan can use.
You will first need to get makecert.exe if you don't have it on your computer. You can get it by installing Windows SDK or Visual Studio.
Related
Having problem where the Mirth Connect Server Manager UI points to an earlier, non-working install version of the Admin interface.
Installed Mirth once and had to reinstall because the original install had set the password requirements to something that the default admin account could not pass. When I did this, the installer said that it detected that Mirth was already installed and asked if I wanted to re-install and I said yes. However, the Admin UI that the Mirth Connect Server Manager windows that remains in the upper menu bar of my desktop still appears to be using the old install with the password issue.
The Mirth Connect Server Manager icon in the upper menu bar takes me to wrong setup. Can't log in from the Admin UI that this bring up (told can't authenticate or connect (which was the problem I had with the earlier install)).
Need to use the Program from here
and make sure that I chose the right one, then I am able to use the default admin account to log in and proceed as normal.
Anyone know how to fix this (eg. somewhere in the underlying files where I can change this)? Anything else I should check that may be messed up due to this problem that I may not be noticing? I am on Ubuntu 18.04.4LTS MATE.
In the installation folder\conf\mirth.properties file, change the HTTP and HTTPS ports to values different from the prior one. Get to your browser type localaddress:new_http port then click on the icon -launch Mirth Connect administrator. Clicking the saved shortcut will launch an admin launcher which will allow you to edit and save the functional instance.
I am developing a clickonce C sharp project in Visual Studio.
On my main computer, I have generated a self-signed certificate for the clickonce manifest.
This works fine, I can compile, deploy and run.
I also sync this solution to my github account, and regularly pull updates down to a backup computer.
The backup computer is not able to simply compile this solution, as it gives errors in regards to self-signed keys.
I could generate a new one on the backup computer, but then when I deploy to same testbed, it causes issues because the certificate is from a different location.
I want to quickly be able to deploy from the backup computer in the event that there is an issue with the main.
How can I share the main computer's generated certificate with my backup environment without issue?
My apologies if this is straightforward or I am missing something obvious.
Run certmgr.msc (user) or certlm.msc (computer) and look in My Certificates for the certificate. Right click it an check if you can export it with the private key resulting in am PFX file (PKCS#12).
If this is not possible generate a new one with the -ExportPolicy Exportable option.
I created a VSTO Excel Add-in ribbon. That I published to setup.exe. But when the end user tries to install it, it fails with this error:
Customized functionality in this application will not work because the
certificate used to sign the deployment manifests for [Add-In] or its
location is not trusted. Contact your administrator for further
assistance.
I can install the Add-In by doing the following.
Unzip and right click on “setup.exe” and select properties
Click on Digital Signatures tab
Select [issuer] from the Signature list and click the Details button
When the Digital Signature Details dialogue appears, click View Certificate
When the Certificate dialogue appears, click on Install Certificate
The Certificate Import Wizard window should appear. Choose the following:
a. Store Location: Current User, click the Next button.
b. Certificate Store: Place all certificates in the following store, Click Browse, select Trusted Root Certification Authorities, click the Next button.
c. Click the Finish button.
d. A security Warning should appear asking “… Do you want to install this certificate?” Click Yes.
e. Click OK. On the “The import was successful.” Dialogue.
Click OK to exit the Certificate dialogue
Click OK to exit the Digital Signature Details dialogue.
Click OK to exit the setup Properties dialogue.
then I run the setup and all works. The problem is we must send this setup file to many users. and NO ONE will want to do that. I've been messing around with the solution properties -> Signing -> Sign the ClickOnce manifests, but I can’t seem to bring up the Trust Prompt on anything I alter. I don’t have a paid for certificate, I just need the prompt to appear for the user to choose to trust it. I haven’t found an answer online on how to allow this prompt to appear. Any help is greatly appreciated.
You can deploy your VSTO to the Program Files directory. Your add-in will be considered as being safe since admin rights are required to install in this directory. I believe it is the simplest way.
Granting Trust when using Windows Installer You can use Windows Installer to create an MSI file to install Office solutions into the
Program Files directory, which requires administrator rights. For
Office solutions in the Program Files directory, the Visual Studio
2010 Tools for Office Runtime considers these Office solutions to be
trusted and does not show the ClickOnce trust prompt.
source msdn
If you give it a second thought, this feature (certificate signing) is designed to specifically disable your scenario. Means, it is built to prevent users from installing non-signed add-ins downloaded from the internet.
I think, if you have so many users which are not in your organisation (so that "correct" certificate cannot be installed centrally), the only reasonable way to overcome this is to buy a certificate from some authority (to pass organization or identity validation). It's not really expensive, and will ensure your users that the thing they are installing is really coming from you.
I need to deploy some registry keys and install certificates in some stores on each of my clients computer.
To avoid errors and make it easy to use, I want to create an automated process to do so, but I don't what are the options.
What are the possibilities to upgrade the windows registry and install a few certificates?
Batch files?
Installer?
Deployment package?
The sweetest thing would allow my clients to configure their computer by clicking a button right into one of my ASP.net page, is it possible?
I'm facing the following problem :
On windows XP, the utility called "certutil", that is used to deploy certificates is unavailable.
To install it, I must install on each client the Windows server 2003 Administration tools and it's cumbersome.
The best solution I've found so far is to export my certificates from the registry, and install them through my clients' registry ! I can only share a big .REG file that will do all the installation work.
Each one of my certificates must go into the following registry key :
[HKEY_CURRENT_USER\Software\Microsoft\SystemCertificates\Root\Certificates]
And by exporting my registry, I can therefore share the exported .REG file to allow other users to install them!
Can I have trouble with that solution ? Is there a better way ?
Thanks for your help!
I looked again at the group policy preference I was using. There is an option "Run in logged-on user's security context (user policy option)" that I enabled and now the registry entry is persisting
I have a C# application (WinForms) (ClickOnce) whose repository is installed on a server that is about to crash, so my boss asked me to move the repository, but there are around 300 client machines which have the application installed.
The ClickOnce is signed with a Test Certificate.
Is it possible to move the repository without having to reinstall in the client machines?
Thanks in Advance
[EDIT]
I Have published the application to the new server, but the clients don't reach it, what else can I do? I think i should change something inside the manifest or something like that, but a actually don't know too much about ClickOnce... In any case, i would like to avoid the reinstallation on all the client machines, any ideas, suggestion? thanks in advance
The answer provided by Jhonny seemed promising to me, and I encountered an error when I tried it, which I had to solve. It had to do with certificates.
After following his setps, when I launch the ClickOnce app on the client machine, I get an error dialog: "Cannot Start Application".
When I click on the Details... button in the error dialog, the text file that opens shows that the app is trying to update from the Deployment Provider URL of the new server, but it gives this error:
"The deployment identity does not match the subscription."
The problem was the certificate used to publish the app on the old server was expired, and I had updated the certificate in the app published on the new server. The certificates didn't match.
The solution was to first publish the app to the old server with the new certificate, have the users open the app to get that update, then publish another new version with the Deployment URL of the new server, and copy the files to both servers. When the users updated the next time, they got the version of the app from the old server with the manifest pointing to the new server, and then, all subsequents updates were retrieved from the new server.
Here is what I have done, for people who may have the same issue.
Setup the new server on the publish package. (Project Properties, Publish Tab)
Publish to the new server
Copy the published files to the old server. (Include the .application file and the folder)
When the clients reach the old server, they will update, but the server location will be updated on the client to the new server name.
You could try to change the DNS alias so that it redirects to your new server.
The fact that the code signed using a certificate is not relevant, since code-signing certificates are not bound to a specific repository (as opposed to SSL certificates)
Btw, why don't you want to reinstall? The whole point of clickonce is to ease this kind of software update !!