Tranquil IT Forum

Good morning

Windows 2012r2 server, in an Active Directory (no Samba).

I wanted to migrate my Wapt server to version 1.5
By using a domain administrator account during post-configuration, I inherit this message.
And this by trying with the old wapt, having previously deleted the old wapt, with the antivirus, without the antivirus, with vc++ 2008 or without VC++2008.


Las.
I logged in with the local administrator account.
And I have this error


The image capture is truncated because the password appears in plain text in the error pop-up.

Thankfully, my Wapt server is on a virtual machine. I can revert to the backup from 24 hours ago, but I've wasted an afternoon trying to install a proper version...

Good morning.

By using a weak password, I bypassed the setup step.
But upon logging in, this message appears:

I've gone back to WAPT 1.13.
But I'm looking for an alternative to WAPT.
Because between the secondary WAPT server bought outright, for which we have no documentation to make it work, which is struggling on a desktop, and a WAPT 1.5 Windows version that is buggy to the core.

Thank you... No! That's an abuse...

For the "SSL connecting error" message, you need to click on the small wrench icon and then click on "Check".

This is indeed indicated at the end of the Debian documentation, but not at the end of the Windows documentation.

Regarding the Wapt box, contact was made privately.

You must be installing WAPT 1.5 very often... It shows...

This time.
I uninstalled Kaspersky
I uninstalled WAPT Server and WAPT client
I removed Python 2.7
I uninstalled the Visual C++ 2008 Redistributable
I restarted it, of course.
And this is the error message I'm getting.
I started again and, in addition, I deleted the c:\private directory

And I'm still getting the same error message.


I'm giving up.

I forgot...

I installed WAPT 1.5 on a fresh install of Windows 2016 Server, on another machine with a different hostname.domain-name. It went without any problems.

I performed the same procedure on a fresh install of Windows Server 2012 R2
And the message is repeated again: Should I invest in a Windows Server 2016 license?
Do I need to change my hostname.domain-name for it to install?

I'm wondering.

Hello Mr. Pavilla,

olivetree wrote: ↑May 2, 2018 - 11:25 AM I forgot...

I installed WAPT 1.5 on a fresh install of Windows Server 2016, on another machine with a different hostname.domain-name. It went without any problems.

I did the same thing on a fresh install of Windows Server 2012 R2
, and the same message appeared:
wapt-errorCapture.PNG.

Do I need to invest in a Windows Server 2016 license?
Do I need to change the hostname.domain-name for it to install?

I'm wondering.

What special characters are in your password? It seems the Python call in waptserverpostconf.exe is probably buggy in this case. Could you use an alphanumeric password for the initial installation, and then change it in the waptconsole after the installation is complete?.

Sincerely,

Denis Cardon

And I'd like to remind you that Tranquil IT can assist you with your system upgrades. Our services are affordable, so if your time is valuable and the documentation seems too lengthy or not tailored to your specific situation, then calling us is an option.

Sincerely.

olivetree wrote: ↑May 2, 2018 - 10:44 You must be installing WAPT 1.5 very often... It shows...

There's no need to be unpleasant...

Wapt is open-source software; if you dislike something about it, you can fix the software. The source code is available.

Only users of the enterprise version of wapt are eligible for support.

For users of the community version (Free versionYou have access to the forum and mailing list. The TIS team responds when they have a moment, often in their free time outside of working hours...

So I tend to respond more easily to users who are friendly, sorry...

I performed the update.

Here's how I did it.

I used a domain user account that's in the domain administrators group instead of the "domain administrator" account.
Why? Because the error messages said it couldn't change the permissions on a directory.

I uninstalled the following:

* Visual C++ Redistributable 2008 x64 and x86
* Python 2.7
* Waptserver 1.3.

I then backed up the private directory as well as the waptdev directory.

I installed Wapt 1.5
. During installation, I entered a simple password.
Why? It seems that strong passwords weren't accepted. And I'm wondering if this isn't related to a restriction that appears after installation, stating that passwords must be at least 10 characters long.

Also, I don't remember the details for retrieving the certificate.

P.S. I am not friendly, certainly, but in my professional network I actively promote your tool to the point of giving a national presentation in November 2018 with concrete examples.

I'm unable to reproduce your problem.

I've tried several times on different operating systems: Windows 10, Windows 7, and Windows Server 2012 R2.

It works every time, even with User Account Control (UAC) enabled and a non-administrator account.

The only issue I'm encountering is with the password. A fix is ​​in progress for this.
You probably have a password containing a single quote (') or a double quote ('). The problem doesn't occur in the Linux version.

Perhaps an antivirus program is causing the issue? Does the machine host any other services? Have you tried it on a clean machine that isn't on the domain? (Some Group Policy Objects (GPOs) might be causing problems.)