Jump to content

hairyprogrammer1

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral

About hairyprogrammer1

  1. Just to add.... Just to follow up...what i did find...though...was... on Server 1 where the Word version is Word = (15.0.5101.1001) MSO (15.0.5101.1000) 32-bit There are 127 Microsoft Office Professional Plus 2013 updates installed....with no more to be installed after running a Windows Update on Server 2 where the Word version is: Word = (15.0.5023.1000) MSO (15.0.5023.1000) 32-bit There are 121 Microsoft Office Professional Plus 2013 updates installed....with no more to be installed after running a Windows Update I'm a bit stumped....
  2. Morning. Completed the updates...Word versions remain the same. There are no more updates for each server....? Any other suggestions?
  3. Connect to the server....and...?
  4. We have 2 RDS servers (Windows Server 2012 R2) We also have an MS Office 2013 installation: RDS 1 Word = (15.0.5101.1001) MSO (15.0.5101.1000) 32-bit RDS2 Word = (15.0.5023.1000) MSO (15.0.5023.1000) 32-bit I am trying to bring the MS Word versions to be at the same level...and fully patched. Partially because it's good practice to have the application on the server fully patched, and then secondly because we are experiencing an issue with the Word application itself which ill talk about in a little bit... I have been advised by an external contractor that: "It could be that we need to install the latest Word patches in install mode as opposed to RDS mode" Can anyone shed light on that statement for me...? I have googled in vain. At the moment if i run windows updates on the 2 servers...it doesn't find any new Office 2013 updates...yet the versions remain different. I am hoping if i can fully patch both servers with Office updates then the Word versions will become the same. Secondly...we are having a problem with Page Number insertions for users...in the fact that they can't! I know it's related to building block template file and the fact that on the RDS server we have (in the publishing section) Command-line parameters set to: Always use the following command-line parameters: /a We are reluctant to change this particular option. Anyone ran into this issue...or can you advise?
×
×
  • Create New...