<div>
<div class="content wysiwyg-content">
I have very recently installed a Windows Server 2012 Standard server into a Windows 2008 SBS Network. Local and remote access to shares good except for Office Apps which are very slow to save and open files. Can see other people have come up with various solutions relating to invalid old shares, TCPIP settings on clients and Group Update changes on Server 2012 acting as Domain Controller (this one isn't as yet).<br />
Have not been able to pin this one down despite some alterations to TCPIP settings and checks on clients. Should I concentrate on server or clients or both?
</div>
</div>


I have very recently installed a Windows Server 2012 Standard server into a Windows 2008 SBS Network. Local and remote access to shares good except for Office Apps which are very slow to save and open files. Can see other people have come up with various solutions relating to invalid old shares, TCPIP settings on clients and Group Update changes on Server 2012 acting as Domain Controller (this one isn't as yet).
Have not been able to pin this one down despite some alterations to TCPIP settings and checks on clients. Should I concentrate on server or clients or both?

Windows Server 2012 has very slow Open/Save for MSOffice Apps

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.