Short blog post and a small finding with Lync 2013’s frontend installation.
As you would have seen with my installation blog guides, I’m building a comprehensive guide for Lync 2013 with all the key features being installed. What this means is both RAM and disk space is at a premium in my lab environment.
So for the SQL server i allocated 25gb disk space, and on the pooled front ends I’ve initially allocated 20gb’s of disk space. In the old Lync 2010 set up this was always enough space per server to complete an installation whereas with Lync 2013 i was getting an annoying error which at first left me wondering why. ? My SQL Server mirrors had 3gb space available and my Lync Frontends also had 4gb of free space still so why the error???
The problem information in the error log file gave very little help as to why i was getting this issue on the local database setup for collocated databases.
Well after a little bit of fact-finding with trial and error, it looks like there has to be a minimum of disk space available on the frontend servers even if its not going to be unitised by Lync.? Why oh Why Microsoft?!
Upping the disk space in 5gb iterations, in the end i’ve added another 20gb of free space meaning i was allocating a total 45gb per frontend which is madness for a lab machine. <of which 24 was still unallocated>
Following a server reboot and a install rerun. I successfully got past my issue.
Whats more annoying is I’m now left with 19.3gb of free space not used on the front ends.
I will ask the Microsoft Lync Partner group about what the reasons are for such a requirement on the install.