Le 28/11/2014 15:03, Richard DURGAHEE a écrit :
Hello,
Actually I installed WAPT on a Windows server 2008 R2 which has WSUS and obviously IIS enabled..
I see.
I checked " wapt_password" line and has a very long password with letters and lot of numbers.
This part is probably fine then.
The console tries to connect to https://your-server/ by default ; to overcome Apache's absence you could try http://your-server:8080/, this is where waptserver lives.
Is there a way to make it work on this server? If it's not possible I will install it on another server.
It's probably doable but personnally I'm not versed into IIS configuration. It would be much easier to install on another - dedicated - host. No need for Windows server edition, btw.
This is the second time this month that IIS is a problem for a WAPT user. Writing a test to check for its presence is on my TODO list for too long, and the documentation could also be more explicit about the requirements...
Regards,