none
Office Pro 2013 0n Terminal Server slows server down

    Question

  • Using server 2008 R2, in Remote Desktop Services mode.  Some in a domain environment as a member server, some stand-alone.  All were running Office Pro 2010. All running on virtual machines.   All servers performed admirably.  Removed Office Pro 2010.  Installed Office Pro 2013. Server performance degraded to unacceptable.  Added processors and memory to the virtual machines.  No joy.  Move the storage to fiber channel.  No joy.  Uninstalled 2013 and reinstalled 2010; runs great.  Found a few articles about installing 2013 on a Terminal Server.  Nothing "earth shattering", just a few minor tweaks. Tried the suggestions.  No Joy.  Can't find much in the way of support questions related to RDS and office 2013. May I'm missing something obvious.  Any suggestions?
    Thursday, April 25, 2013 4:08 PM

All replies

  • Hi,

    If I understand correctly, the problem is that the whole server is slow down, other than just the Office applications, right?

    If so, what's the exact slow down behavior? Is memory or cpu occupied a lot by Office applications? Do we have any special event log?

    BTW, is this behavior specific to specific Office applications?

    ...

    Try to configure a clean boot mode to help determine if this behavior could be caused by the conflict with some 3rd-party services.


    Max Meng
    TechNet Community Support

    Friday, April 26, 2013 9:01 AM
    Moderator
  • Hi,

    Just checking in to see how is everything going on?


    Max Meng
    TechNet Community Support

    Tuesday, April 30, 2013 7:45 AM
    Moderator
  • Hi Max,

    I did a lot of experimenting with processors and memory. What I found is that to get acceptable performance I had to have 4 processors and 4GB of RAM.  More RAM didn’t make any difference, as nothing I did took it over that amount.  I uninstalled GoToAssist and Virtual Clone Drive.  Didn’t notice any difference.

    1. Opening Outlook takes 35% of 4 procs for several seconds.
    2. Opening an e-mail takes 11-30% of 4 procs depending on the graphics in the message.  After opening processor goes down to 1 or 2% until you move around in the document when it goes back up to around 12%.
    3. Same with Word and Excel.
    4. Opening a web page takes similar processor resources.
    5. None of the other programs take much in the way of resources after opening.

    It appears that Office 2013 and IE are taking most of the processing resources.  IE was the same when using Office 2010.  Office 2010 used roughly a third of the resources of Office 2013.

    In the Application log there is a COMRuntime error 18209 per reboot that references “unavailable” as the source.  Otherwise the log is clean.

    In the System log there is an entry vsepfit failed to load.  That seems to be something to do with headless operation of the server.

    All of my servers have 100Mbps connections to the Internet.

    It seems as if any program connecting to the Internet OR any program that uses a lot of graphics is causing the slow-down.  It all points to Office 2013.

    BTW, my personal RDS Server is used for customer support.  I was using one processor and 4GB of RAM before Office 2013 and it was satisfactory.  You can see why I’m thinking…

    • Proposed as answer by Sagar 1987 Tuesday, May 14, 2013 6:56 PM
    Sunday, May 05, 2013 3:49 PM
  • Hi Max,

    Any thoughts?

    Monday, May 13, 2013 6:07 PM
  • well run->msconfig and disable all 3rd party applications & then check

    After applying Service Pack 4 for Terminal Server, ensure that the following registry entry is configured:
    HKEY_LOCAL_MACHINE\SYSTEM\CCS\Services\NwRdr\Parameters

    Use the following information for configuring:
    Disconnect REG_DWORD
    1 Original Behavior, Disconnect (Default)
    0 New Behavior, Do not Disconnect
    Monday, May 27, 2013 6:24 PM
  • I'm not aware of "Service Pack 4 for Terminal Server" as it might relate to Server 2008 R2.  Please enlighten me.

    I did stop all unnecessary 3rd party applications on startup.  If there was a difference, it was indiscernible.

    I don't have a NwRdr parameter as described, but am not using Netware in the environment.

    Perhaps this replay wasn't for this post?

    Monday, May 27, 2013 7:55 PM
  • We have the same problem in a virtual RDS-server (Esx) after upgrading from Office 2003 to Office 2013 in a 2008 R2 server. About ~30 users:

    Earlier: worked perfectly with ~30 users
    2008 R2
    Office 2003
    CPU: 4vCPU x 2,26 GHz
    RAM 12 GB

    Now: Really slow performance with all users connected
    2008 R2
    Office 2013
    CPU: 4vCPUx2,26 GHz
    RAM: 24 GB
    Tweaks: Disabled hardware accelerations, Disabled Animations

    Works OK with just a few users signed in, but when all 30 are working the CPU peaks at 100% many times. And cannot assign more with the customers VMWare licens





     


    Thursday, May 30, 2013 6:43 PM
  • Thanks for responding.  It sounds like we are having a similar issue.  Microsoft must be aware of this issue.  There just isn't much information "out there".

    I have tried Condusiv, V-Locity 4.  It made a noticeable difference in file handling, but didn't do much for the processor requirement.  We were still banging hard on four procs.

    We tries Ericom Blaze.  That is pretty nice on the video refreshes.  At $125 per user?  It is pricey.  That didn't give the processors much relief either.

    I'm trying so other things.  I'll keep in touch.

    Thursday, May 30, 2013 10:20 PM
  • We disable Windows Audio Service and Windows Audio Endpoint Builder Service on the RDS Server.  That dropped the CPU usage sufficiently to reduce the number of CPUs required for the same level of usability on my company server.  I'm not sure why those services were running by default. 

    I performed this on two 20+ installations and the customers both remarked that there was a huge improvement.  I didn't drop CPUs on those two particular installations yet as I will be monitoring them for a while.

    Anyone else got anything?

    Monday, June 10, 2013 4:38 PM
  • I came across this article http://blogs.technet.com/b/askperf/archive/2012/03/06/performance-issues-due-to-inactive-terminal-server-ports.aspx

    On my "lightly used" company RDS server, there were over 2500 inactive terminal services ports.  I ran the hotfix and the "Fix-it" routine and it cleared out the inactive ports as advertised.

    Now, Outlook is only using a few % of the CPU.  Interesting.

    Skydrive (not Skydrive Pro from Office 365) was taking 22-33% of the CPU processing synchronizing from some work I did this past weekend.  After 20 minutes, I "Xed" out of the session to let it run.  I intend to uninstall the Skydrive program to see if that provides any relief.  Will wait until it is finished synchronizing to avoid unintended consequences.

    Monday, June 10, 2013 11:51 PM
  • Hi,

    I'm having the exact same problem too. I have rolled out 2 brand new 2008 R2 Datacenter terminal servers, with Office 2013 Pro Plus. Performance seems horrible.

    Have tried adding that patch and disabling the windows audio services, but no great difference is made.

    Only solution at the moment is to remove 2013 and put on 2010.

    Anyone else had much luck with this issue?

    Mark

    Friday, June 21, 2013 2:01 PM
  • Hasn't tested this, but try adding a GPU and configure RDS to use it. Background: Office 2013 uses D2D/DWrite instead of GDI. Without hardware acceleration, this has to be emulated using WARP on the CPU.

    Yuhong Bao

    Saturday, July 06, 2013 2:01 AM
  • We're struggling with the same problem too, except we're running Citrix XenApp 6.  I've just started researching the problem and found this post.  Anyone had any luck since last posting?

    K

    Wednesday, September 04, 2013 4:42 PM
  • Nothing new.  Yuhong Bao suggested a video card, but we can't add one to these servers.  We don't own them.  All the tweaks we did are referenced in this discussion.  No one from Microsoft seems to have an answer.  Hopefully someone from the community will come across this thread and have a solution.  Personally, I don't think Citrix is the problem.  Surely, it is an Office 2013 configuration.
    Thursday, September 05, 2013 9:58 PM
  • We've been noticing the same lag.  Running a virtual TS with approx 40 users (not always active at the same time).  This thing has 24GB of memory and 8 CPUS.  It is DEFINITELY a 2013 issue. Microsoft applications are my only complaints.  Microsoft - it would be awesome if you could weigh in on this. There are Technet forums and Spiceworks forums still searching for a solution. Just wanted to throw my 2 cents in as we're searching for an answer as well. 
    Monday, September 23, 2013 2:59 PM
  • We are also experiencing the same performance
    issues. The first Office 2013 on a 2008 std server that we have rolled out
    was experiencing performance issues. At first we did not expect is was Office
    2013 until we have de-installed it and installed Office 2010
    instead. Because Office 2013 was brand new when we've tried to install it
    for the first time, we have decided to wait until a fix/solution would be
    available. From now on all new RDS servers based on Server 2008 or
    Server2012 we perform an installation with Office 2010. However, at a
    certain point our customers would like to use Office 2013 as well. We are also
    looking for the solution to this problem. We have already tried to disable the
    animations and turn off hardware acceleration from the option/advanced menu...but
    nothing helps. I think the only solution is to provide hardware acceleration
    from the RDS server, unfortunately we are using VMWare.<o:p></o:p>

    We are going to set-up a test server and try to
    install Office 2013 again. We will try to look if hardware acceleration emulation
    somehow does the trick.<o:p></o:p>



    Tuesday, September 24, 2013 1:27 PM
  • I have a rollout of 2008 in a couple weeks - we have Office 2013 - Anybody finally get this resolved???

    David

    Saturday, September 28, 2013 2:46 AM
  • We narrowed our problems down to winword.exe, excel.exe and outlook.exe periodically claiming 50% of the processor.  It happens to multiple users and doesn't only happen on one server. 

    We have a ticket open with Microsoft, but they haven't found anything yet. They're quite slow at getting back to me too.

    I will post back here when we find a solution.


    K

    Saturday, September 28, 2013 6:13 PM
  • I hope you have better luck than I did.  April 2014 will be upon us soon, with the end of Office 2010 support.

    I look forward to the MS response to you.

    Bob Hengen

    Monday, September 30, 2013 5:10 PM
  • Hi all,

    Are there any improvements for Office 2013?

    We have a virtual server RDS 2012 running on hyper-v and i see Office 2013 eating all the resources of CPU.

    I am really looking forward to see MS response but so far NO SOLUTION!!!

    Ati

    Thursday, November 07, 2013 2:40 PM
  • No improvements.  We ended up closing our ticket with Microsoft because the only troubleshooting steps they had were to do a clean boot and disable addins and our users can't do their jobs in those situations, so there was no way to test it.  

    Our users were geting upset with performance, so we downgraded to Office 2010 and all is well now.

    What sucks now is that we'll have a hard time convincing them to upgrade to 2013 again in the future.  We probably won't even try until SP1 is released.


    K

    Thursday, November 07, 2013 2:46 PM
  • We are putting up a 2012 R2 Server (actually muddling through the install) and will put Office 2013 on that.  We hope it isn't a fools errand.  Maybe there's some magic in the new server.

    You know, April is going to be here pretty quick. We need resolution. 

    Has anyone hosted an RDS server on Azure? Just a thought.

    Thursday, November 07, 2013 10:50 PM
  • dbwebnet, any luck on the 2012 install with Office 2013?
    Monday, December 09, 2013 2:23 PM
  • No.  The tech on that project got slammed with customer projects.  We are going to get back to that when the Office 2013 SP comes out. It shouldn't be too long now.
    Monday, December 09, 2013 3:17 PM
  • We had pretty good success with disabling hardware acceleration through group policy.  We have 4 CPUs and 16 GB of RAM on each of our Citrix servers.  About 10 to 12 users per server right now.  RAM is about 50%  CPU is pretty normal near zero but I do see spikes of 15 to 25% on the Office .exe but not as long as before the tweaks.

    Ran this registry adjustment at the same time so I am not sure which helped more, but it did help visual performance:

    Windows Registry Editor Version 5.00

    ;
    ;Disables the Office 2013 shadow boarder
    ;Download from ThomasKoetzing.de
    :
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\MSO_BORDEREFFECT_WINDOW_CLASS]
    "ClassName"="MSO_BORDEREFFECT_WINDOW_CLASS"
    "Type"=dword:00001000


    We use Office 365 so I also disabled all the Office apps from the Office 365 portal.  Also turned off all annimations in Group Policy.  Used the OCT to install Office 2013 and did not install SkyDrive Pro.  I also turned off as many of the Internet connected features and templates as I could find.  No need for Office to be heading out to the Internet all the time.  I'd be happy to share my Office Group Policy if anyone is interested.

    Friday, December 13, 2013 9:57 PM
  • Hi pmabke,

    Can you please share the Office 2013 Group policy?

    Wednesday, December 18, 2013 7:55 PM
  • I have been dealing with the issue of slow office 2013 all day today as well and I think I found a solution. I forced the remote clients to be at 16bit color depth and the performance increase was dramatic. It appears that all the visual enhancements are causing the RDP server to strain when drawing the colors, more so then the animations themselves.

    For anyone that doesn't know how to change the color depth settings check this link http://technet.microsoft.com/en-us/library/cc772048.aspx

    Friday, December 27, 2013 6:58 PM
  • Thanks Creative IT Services.

    We applied the fixes some time ago. This gave some relief.  We instituted 16 bit color, much to the chagrin of the end users.  Most everyone on our many terminal servers use two monitors.  16 Bit color was helpful to a point.  The users don't like it because, well, they maintain it hurts their eyes after a few hours.  In particular, they hate using Outlook that way. Truth be told, it is fuzzy.

    An update:  we had to turn audio back on so the users can access their voice mail. Audio ups the resources significantly. Had to add 6GB memory to a 15 users TS to maintain status quo. My ISP is charging $50 per GB per month. Will no doubt lose this customer when the contract ends.

    Again I ask, is anyone using Azure for RDS with Office 2013?

    Friday, December 27, 2013 11:51 PM
  • Just to note, and I think it's related, we are having big problems with Vmware Horizon View desktops running great, up until the point where you open any Office 2013 app, especially Outlook 2013.  I don't think this issue is limited to terminal servers, I think Office 2013 has serious performance problems.
    Monday, March 03, 2014 6:25 PM
  • Where are you seeing the performance problems?

    I ask because I saw them in our VDI environment at initial login, I was able to get the login time from 2 minutes down to ~7-10 seconds.

    Jared

    Tuesday, March 18, 2014 10:17 PM
  • Hi Jared,

    I'm not using a VDI environment and am not qualified to comment on VDI.  I'm using RDS and Office 2013. The slowness starts the minute Outlook is opened by any user, and gets worse as other users open Office applications. The issues don't exist with Office 2010. Most of our cloud-hosted customers are Office 365 E3 customers.  They use Office 2010 on the RDS server and Office 2013 on their desktops. I'm still waiting for Office 365 to release SP1 for Office 2013.  Hoping that will make a difference.

    I have done two things recently that made a difference in my experience on a small RDS server running Office 2013 on 2008R2 Server.

    1.  Changed Local Security Policy, Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Remote Session Environment, Set compression algorithm for RDP data to ENABLED. That seemed huge.

    2.  Changed the RDC Client Display to 16 Bit color, and Experience to Low-speed Broadband and only Font Smoothing and Visual styles, and Persistent bitmap caching and Reconnect... checked. That was huge for the visuals.

    Let me know if that helped anyone out there.

    Wednesday, March 19, 2014 8:36 PM