 Kerio Connect 8 as Hyper-V image (VHD) ? [message #96596] |
Wed, 05 December 2012 11:08  |
Ada
Messages: 12
Registered: December 2012
|
|
|
|
We have Kerio Control as Hyper-V now - great!!!
What about Kerio Connect? You have "base" OS ready with Hyper-V integration - why not to release Connect Hyper-V image based on this OS too?
I would like to have Connect on separate VM (and not to install on Windows Server VM with bunch of other roles).
Benefits? Backup/restore/migrate, no need for 3rd party antivirus (sophos included),no need to add path "exceptions" to antivirus in Windows Server, less cost - more simplicity...
I hope to have this sometime in 2013 
|
|
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #96627 is a reply to message #96613] |
Wed, 05 December 2012 17:23  |
Ada
Messages: 12
Registered: December 2012
|
|
|
|
Right, but:
1) when I choose some linux distro, I have to configure/secure it and after then I can install Kerio. I do not have any Linux based OS in our domain now. I do not want one (except some pre-configured like Control Hyper-V image).
2) when separate Windows VM - additional costs for Windows licensing, ESET antivirus exceptions config, ...
So my suggestion solves both and follow your motto of recent forcing Sophos in Kerio products : Why? Because it is simple ...
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #96873 is a reply to message #96613] |
Wed, 12 December 2012 11:49 |
TEFICO
Messages: 16
Registered: February 2010
Location: Spain
|
|
|
|
Pavel Dobry (Kerio) wrote on Wed, 05 December 2012 14:32Kerio Connect can be installed to standard system and does not require special installation image. You can create your own Hyper-V image with your favorite system and install Kerio Connect there very easily.
For quick testing and fast deployment we support Vmware virtual appliance.
May be it's easy to install Connect as Hyper-V machine inside any of OSs supported. But the same for Vmware.
The reason to develope a Hyper-V appliance is simple: same than Vmware appliance .
We also would appreciate a Hyper-V appliance.
|
|
|
|
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #97124 is a reply to message #96627] |
Tue, 18 December 2012 17:31 |
hberm001
Messages: 20
Registered: August 2012
Location: United States
|
|
|
|
Ada wrote on Wed, 05 December 2012 17:23Right, but:
1) when I choose some linux distro, I have to configure/secure it and after then I can install Kerio. I do not have any Linux based OS in our domain now. I do not want one (except some pre-configured like Control Hyper-V image).
2) when separate Windows VM - additional costs for Windows licensing, ESET antivirus exceptions config, ...
So my suggestion solves both and follow your motto of recent forcing Sophos in Kerio products : Why? Because it is simple ...
The question is: Why are you afraid of Linux? Installing any recent version of linux + installing kerio is super easy, and takes all of an hour, tops. If Kerio releases more prebuilt stuff, its just more stuff that slows down the update release process, more stuff that has to be QA'd before it can go public, etc.
We have Connect (and workspace) running in VM's that we maintain on CentOS. We set up CentOS one time, created a template out of it, and thats it. Whenever you need a new appliance you just deploy from template, customize a handful of things (hostname, IP) and then intall whatever services you need.
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #97135 is a reply to message #97124] |
Wed, 19 December 2012 08:37 |
KursadOlmez
Messages: 25
Registered: December 2006
Location: Ankara - Turkiye
|
|
|
|
Hello hberm001;
You might be right that you said about linux installation and other things.
But I'm just curious; If it's easy as you and Kerio says why Pre-configured VMWare Virtual Appliance package created?
And If creating and Distributing a Hyper-V Virtual Appliance will slow down Kerio Connect's fixes and upates why Kerio Control Hyper-V Virtual Appliance created? Isn't it slow down Kerio Controls as well?
In my opinion, if Kerio creates Hyper-V Virtual Appliance for Kerio Control than they should create Hyper-V Virtual Appliance for Kerio Connect.
Thanks.
Edit: Meanwhile, I'm not afraid of Linux. If so, I wouldn't find a way to work Vmware image into Hyper-V by converting it. But the point is we don't have a VMWare Virtualization products and we are a Microsoft Hyper-V specialist company. So, it shouldn't be so hard to create a Hyper-V Virtual Appliance of Connect for Kerio Staff.
[Updated on: Wed, 19 December 2012 12:53] Report message to a moderator |
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #97886 is a reply to message #96596] |
Sun, 20 January 2013 10:45 |
Quentinb
Messages: 7
Registered: November 2009
|
|
|
|
I am also looking for Hyper-V image for connect. Why VMWare (which is so expensive - free version is limited to 1 CPU BTW). We run Citrix Xen Server, which Kerio does not support "officially" and Kerio supports Hyper-V "Officially" so why is there no "Official" Hyper-V image for connect?
I have tried the Control image and works great, now I want to run Connect image.. oh wait, there is no image for connect 
|
|
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #124340 is a reply to message #102603] |
Tue, 22 September 2015 09:49 |
TEFICO
Messages: 16
Registered: February 2010
Location: Spain
|
|
|
|
What about this? Why there is not a HyperV image?
Yes, I can install a linux distro and KConnect but it's more easy to deploy and very much easy to maintain if it would be and official HyperV image.
Why VMWare and not HyperV?
|
|
|
|
|
|
|
|
|
|
| Re: Kerio Connect 8 as Hyper-V image (VHD) ? [message #124533 is a reply to message #124532] |
Mon, 28 September 2015 18:06 |
TEFICO
Messages: 16
Registered: February 2010
Location: Spain
|
|
|
|
r1sh: I've installed KConnect in CentOS 64 bit with two vhdx disks and no problem about disks.
Maerad: First time installing KConnect in CentOS is complex for a not linux expert. After first time it's more easy
But the question is: it's so complex (or not) for VMWare users, isn't it?
|
|
|
|
Members
Search
Help
Register
Login
Home
