| Re: KOFF and Windows Server 2012 R2 terminal server support [message #118661 is a reply to message #118657] |
Thu, 15 January 2015 23:03   |
mwolf
Messages: 44
Registered: January 2012
Location: Germany
|
|
|
|
It is an virtualized Windows 8.1 / 2012R2 Server...the Administrator could configure the Outlook Profile and the password is saved but another user without any permissions (standard user) could not save the password in KOFF...
...I rolled back to Windows 8 / 2012 Server ...everything works fine.
|
|
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #118666 is a reply to message #118662] |
Fri, 16 January 2015 06:38 |
mwolf
Messages: 44
Registered: January 2012
Location: Germany
|
|
|
|
|
No my Hypervisor is RedHat Enterprise Virtualization Cluster (KVM) and I tried Windows 8.1 with ThinStuff Terminalserver Extension and Windows 2012R2 TerminalServer as virtual machine. And like I said with Windows 8 with Thinstuff and Windows 2012 as VM everithing works fine with KOFF and Outlook 2013.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #118675 is a reply to message #118674] |
Fri, 16 January 2015 13:42 |
mwolf
Messages: 44
Registered: January 2012
Location: Germany
|
|
|
|
Ok I just verified Win8 with Thinstuff works and Win8.1 not. Same domain, same group policies.
You could also try Win8.1 with a restricted User without Thinstuff. And the user from the first post had also a vanilla Win2012R2.
So I rolled back to Win8 and hoping for an updated KOFF.
Thank you.
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #118702 is a reply to message #118675] |
Tue, 20 January 2015 16:10 |
Maerad
Messages: 275
Registered: August 2013
|
|
|
|
Maybe some ideas ... 
I tried some test installations with a combination of Windows 8.1 / Windows 7 as clients (VM and usual host install) with Server 2012 (+R2) as Terminalserver (Standard Windows Remote Desktop Server Host) with Server 2012 (no R2) as AD/DC. I encountered no problems.
It might be a SSO problem. What Domaincontroller / AD do you run? Do you have the latest AD files installed from MS for Support of Win 8.1 / Server 2012 R2?
Did you upgrade the AD program/setup for Kerio (Kerio Active Directory Connector)?
Does the AD Connection work from Kerio to the AD Server? Does the TS work with the AD Server? DFS working? Grouppolices can be changed etc.?
Also login with the domainuser > system panel > mail > delete any mail account you can find. After that go online to the mailserver and dl the script again for auto install and execute it (you have to dl it with the domain user kerio login to be sure)
You could also change the reg key for the cache folder to somewhere else if that is the problem (admin manual).
Annndddd check the event viewer if there are other errors. Server 2012 R2 has some adv. for RDP from server 2012, but those are connection based ones like a better network connection etc. - the functions outlook uses wont differ from the 2012 server.
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #118749 is a reply to message #118702] |
Thu, 22 January 2015 09:04 |
 |
Schulmeister
Messages: 19
Registered: June 2012
Location: Cologne, Germany
|
|
|
|
I just installed a TerminalServer with config as follows:
2 Servers Fault Tollerance which virtualize:
1 Domain Controller
1 RemoteDesktopServer
1 Kerio Server
1 SQL Server
(all Server2012R2)
1 Server 2003 (old SQLDatabase - don't ask)
I installed the KOFF on the RDS Server and the only thing I did was NOT using the Install-Script for the clients - that I did manually for every User.
No problems at all.
|
|
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #119406 is a reply to message #119405] |
Sun, 15 February 2015 13:04 |
Maerad
Messages: 275
Registered: August 2013
|
|
|
|
mwolf wrote on Sun, 15 February 2015 10:06I´m glad I´m not the only one...
http://forums.kerio.com/t/28760/
cheers
His Problem is quite different from yours and I also might've spotted one problem of you.
You said you installed office with the local admin. If the server is joined to a domain NEVER do that. Also if someone with a domain account tries to access or use the server with programs installed with a local admin acc. of the server itself can run into problems with the user rights.
Install the server, join it to the domain, install RD-Services, Office etc.
Also I did a test like this around 2 weeks ago (forgot about this thread actually), because I was trying out 2012R2 with our new ERP and Office 2013. So I set up a AD/DC, installed a new TS on 2012 R2 base, installed Kerio on the AD/DC (better said copied), office 2013 on the ts and tried it with 2 test users.
Absolutly no problems. Office, our ERP was installed by me as a Domain Administrator on the TS Server. Connected as restricted user, dled the config bat, started it, worked.
Even after a reboot.
Some ideas for you as error search (mentioned some of them before, didn't see an answer):
- Did you install the right Active Directory Tools for Kerio with the same version number as your server version?
- Did you use the right KOFF Client? (Best is to DL it from the "Integrate with Windows..." Link from the server website)
- Are any gpo enforced on the ts and did you try to disable them?
- The mapi error suggest a problem within outlook and the registry. Office 2013 changed in a big way their auth/activation and also user usage. If kerio loses his keys etc. it might be because it can't write to the reg.
- Did you check the event manager, did something turn up?
- Did you start up outlook 2013 as domain admin before adding a kerio account? Did you activate it before?
- Do you use a volume licence Office for the RDS? MS changed some things here with 2012/8.1 and office 2013 (guess with a update too). At least I heard that you can't install it anymore or only for one user on a RDS.
Also I suggest not to use Win 8.1 with the TS addon thing. First of all, Windows 8.1 IS capped in may points and not made to be a TS Server or any server in general. Even if the producer tells you it is - the underline functions are NOT the same. The RDS of Win 8.1 is missing SOME things the RDS Server on 2012 has. Second, you need to buy RDS Cals (the expensive ones) even if you set up 8.1 as TS. The PUR of Microsoft (Product Usage Rights) clearly state that you need a RDS CAL for ANY KIND OF REMOTE DESKTOP CONNECTION ON A WINDOWS. It dosn't matter if you use Windows 8, Server 2012, XP or whatever.
Like I said, it worked for me and kerio, so I might suggest there is something wrong with your system or installation. A domain system with a RDS has a fuckload of things that could go wrong, a small little option you didn't really care about could kill your whole system. So IMHO you're still not done with the error search.
And I'm also quite interested in it, because I like to solve problems :3
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #119410 is a reply to message #119406] |
Sun, 15 February 2015 13:32 |
mwolf
Messages: 44
Registered: January 2012
Location: Germany
|
|
|
|
Maerad wrote on Sun, 15 February 2015 13:04mwolf wrote on Sun, 15 February 2015 10:06I´m glad I´m not the only one...
http://forums.kerio.com/t/28760/
cheers
His Problem is quite different from yours and I also might've spotted one problem of you.
You said you installed office with the local admin. If the server is joined to a domain NEVER do that. Also if someone with a domain account tries to access or use the server with programs installed with a local admin acc. of the server itself can run into problems with the user rights.
Install the server, join it to the domain, install RD-Services, Office etc.
Also I did a test like this around 2 weeks ago (forgot about this thread actually), because I was trying out 2012R2 with our new ERP and Office 2013. So I set up a AD/DC, installed a new TS on 2012 R2 base, installed Kerio on the AD/DC (better said copied), office 2013 on the ts and tried it with 2 test users.
Absolutly no problems. Office, our ERP was installed by me as a Domain Administrator on the TS Server. Connected as restricted user, dled the config bat, started it, worked.
Even after a reboot.
Some ideas for you as error search (mentioned some of them before, didn't see an answer):
- Did you install the right Active Directory Tools for Kerio with the same version number as your server version?
- Did you use the right KOFF Client? (Best is to DL it from the "Integrate with Windows..." Link from the server website)
- Are any gpo enforced on the ts and did you try to disable them?
- The mapi error suggest a problem within outlook and the registry. Office 2013 changed in a big way their auth/activation and also user usage. If kerio loses his keys etc. it might be because it can't write to the reg.
- Did you check the event manager, did something turn up?
- Did you start up outlook 2013 as domain admin before adding a kerio account? Did you activate it before?
- Do you use a volume licence Office for the RDS? MS changed some things here with 2012/8.1 and office 2013 (guess with a update too). At least I heard that you can't install it anymore or only for one user on a RDS.
Also I suggest not to use Win 8.1 with the TS addon thing. First of all, Windows 8.1 IS capped in may points and not made to be a TS Server or any server in general. Even if the producer tells you it is - the underline functions are NOT the same. The RDS of Win 8.1 is missing SOME things the RDS Server on 2012 has. Second, you need to buy RDS Cals (the expensive ones) even if you set up 8.1 as TS. The PUR of Microsoft (Product Usage Rights) clearly state that you need a RDS CAL for ANY KIND OF REMOTE DESKTOP CONNECTION ON A WINDOWS. It dosn't matter if you use Windows 8, Server 2012, XP or whatever.
Like I said, it worked for me and kerio, so I might suggest there is something wrong with your system or installation. A domain system with a RDS has a fuckload of things that could go wrong, a small little option you didn't really care about could kill your whole system. So IMHO you're still not done with the error search.
And I'm also quite interested in it, because I like to solve problems :3
Hi, like I said earlier it is working for me now. Here is my setup:
Hardware: Dell Poweredge R515
Hypervisor: Proxmox VE Cluster 3.3 (based on KVM)
Directory: Zentyal Server 4.0 (based on Samba4)
Mailserver: CentOS 7 with Kerio 8.4.1 x64
Fileserver: CentOS 7 with BTRFS (hourly snapshots) and Samba4 (Sernet)
3 Terminalservers: Windows 8.0 x64, Office 2013, Thinstuff Professional (with USB redirect), Serverbased Profiles, KOFF 8.4.1
In my testlab the only thing that didn´t work was the Terminalserver based on Windows 8.1 / Windows 2012R2. Though the Install of KOFF works and the Outlook integration with the Domain Admin User also works. Just the standard Users bring the error as stated above.
So no problem for me, cause I rolled out my serverbased computing with Windows 8.0 x64 and now I`m waiting for Windows 10 to fix it
nice weekend
|
|
|
|
| Re: KOFF and Windows Server 2012 R2 terminal server support [message #119437 is a reply to message #119410] |
Mon, 16 February 2015 23:55 |
Maerad
Messages: 275
Registered: August 2013
|
|
|
|
Well, that's quite the setup. Seems interesting and I will take a closer look
Just some more questions:
- Why do you use Win 8 with Thinstuff and not a full 2012 Server?
- Did you try a real server 2012 r2 and the same problem happend?
- Did you try it with a standard account WITHOUT server based profiles?
I still have a feeling that the culprit is Windows 8.1. Thinstuff removes some limitations of Windows 8 and makes it usable as a Terminal Server, but MS constructed Win8 quite different to a real 2012 server - so win 8 has missing featues thingstuff cant reimplent.
That goes espacially for CPU share times, user integration, domains, security polices/file security etc.
It also might a problem with samba and/or the files shares. Maybe check the kerio install log if the setup wasn't being able to write to the reg. or into appdata/remote or somewhere else.
|
|
|
|
Members
Search
Help
Register
Login
Home
