• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Is Plesk 8.1 stable on Win2003 64bit?

E

egarrison

Guest
I just setup a server running Windows 2003 R2 64 Bit. There are 2 sites on it but Plesk didn't set either one up 100% right.

Front Page Extensions - They should have been turned on in the site, but were not. I installed the 64bit frontpage before installing Plesk. I went to IIS manager and enabled it fine manually.

FTP - Microsoft FTP is installed, but when I go under a site to configure FTP, the Add user is grayed out. The user created for Front page is also not able to login via FTP.


Has anyone else rolled out 64 bit our should I roll back to 32.

Eric
 
I agree. The best investment I made was Plesk on Linux. The worst investment was Plesk for Windows. I took the server back to Windows 32 bit and Plesk is still SO unstable.

We also have Ensim management on other Windows servers. Ensim just sucks...but atleast it's console doesn't crash.
 
A bit frightening to read this - I also have a new Windows 2003 R2, 64 Bit server, and just purchased the Plesk for Windows license today. Am I going to have problems, or has support for the new OS and 64 bit edition improved over the past month and a half?
 
After weeks of testing on 64bit vs. 32 bit. Most things will run under 64 bit if they actually will work under 32 bit. The biggest problem we uncovered was to do with FTP and it not seeing our IP's properly. Those were show stoppers and I could not live with it. Because of that we went back to 32 bit. The IP that was on the box at build was fine, but the other ones that were bound later never worked. FTP never worked under 64 bit. We have since discovered that Plesk on windows is about 80% as good as on Linux. We have many more windows boxes and loved the Plesk admin on our Linux box. Luckily for us, we were installing Plesk on a VMWARE ESX instance of Windows that allows us to easily rebuild under 32 bit.

I hope this helps and I hope that someone at SWSOFT realized that from me alone they would get an order for lots of servers...if they fixed their product to work on Win64 properly and reliable.
 
I don't think so.

I have used plesk since version 7.5 (the first release) and I can say that each newer version of Plesk there is an improvment.
you can make a search after my username in swsoft forum and you will see that I help to developers of SWSOFT to find bugs.
I report about bugs alot's of time.
but this isn't the issue.
I can see that each time swsoft make improvment in the code and can say truly , if you are nebiwe then you need fist to read all the documentation of Plesk for windows platform.
even I suggest to install it in test enviroment just for get more expirence with that control panel.
after all this is a program in the bottom line and bugs are reasonable but the question is how fast a fix is release to the public.
 
Back
Top