Project 2013 Standard Licensing Transfer

I currently have 4 "1-pc" licenses for Microsoft Project 2013 Standard edition. I am curious before I deploy these licenses that if I install the program. Let's say 3 months down the road a computer decides it hates life and just dies whether
it be a motherboard or hard drive failure, would I be able to transfer the license over to a new PC or would I have to purchase a new one?
P.S. I have looked into the licensing agreement it says that some programs might not honor the universal licensing terms, but never specified what programs it doesn't honor. So I'm trying to figure out if Project is one or not. 

Hi,
You will be able to transfer Project 2013 on another computer using the same product key. When you'll
activate it is possible that it will say that the key had already been acivated. You may have to call MS an activate manually.
Note that Office 2013 Products are transferable:
http://blogs.office.com/2013/03/06/office-2013-now-transferable/
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Similar Messages

  • Office 365 Midsize Business and Project 2013 Standard (Retail)

    Hi,
    Can someone explain to me how to install Project Standard 2013 (retail version) alongside Office 365 Midsize Business.
    I either get installation errors - "Something went wrong......" or activation errors whereby the activation code seems to be accepted (green tick) but I am then asked to link it to an email account which won't work as it is a retail version.

    Hi,
    "Office 365" refers to subscription plans that include access to Office applications plus other productivity services that are enabled over the Internet (cloud services), such as Lync web conferencing and Exchange Online hosted email for business,
    and additional online storage with OneDrive and Skype world minutes for home.
    You can refer to this FAQ link below, find more in the section "What is Office 365? How is it different from Microsoft Office":
    http://office.microsoft.com/en-001/business/microsoft-office-365-for-business-faq-FX103030232.aspx
    You may also find the information below helpful:
    Compare all Office 365 for business plans
    http://office.microsoft.com/en-001/business/compare-all-office-365-for-business-plans-FX104051403.aspx
    Choose your Office
    http://office.microsoft.com/en-001/buy/compare-microsoft-office-products-FX102898564.aspx
    Regards,
    Melon Chen
    TechNet Community Support

  • Remove Measurement Studio Enterprise trial computers with activated Standard licenses

    When I install Measurement Studio 2013 on a development computer, activate my Standard Development serial number and license that PC over the Internet, and build some software in Visual Studio, the Enterprise Development trial is automatically selected in the build process. After 30 days, the license expires, and the software behaves as if it is unlicensed - that is, it crashes. A Clean and Rebuild must be run to select the Standard Development license and make the software work again.  I believe that this default behavior is incorrect.  This 30 day window is often shortly after delivering the machine to a customer, so it fails on their floor right after we leave! This is not good for our reputation or for NI's reputation.
    One or more of the following options would be the preferred behavior:
    (1) Do not automatically enable the "Enterprise Development" trial. This trial should be deactivated by default when a Standard or Professional license is activated, and a user should be able to open NI License Manager and Activate it as required.
    (2) Show a warning on start-up whenever a trial license is used. This is what LabVIEW does: upon launch of LabVIEW the user would see something like "Evaluation License - 5 days remaining".  Measurement Studio users do not see this upon launch of Visual Studio, upon building the project in Visual Studio, or upon starting the resulting software.  It would be nice if you could provide a link that would instruct users on how to deactivate the Enterprise Development license in this warning.
    (3) Use the lowest possible development system. If Enterprise-only features are used and a Standard license and Enterprise trial are available, then the trial is necessary (though a warning as in #2 above would be nice), but otherwise use the Standard or Professional license. This issue has caused us some embarrassment several times. Please fix it!
    The workaround, according to Michael Keane from NI (in Service Request #7454045, if anyone from NI is reading this), is as follows:
    I assume that in License Manager during those 30 days you would see a green box next to Standard edition and a half white / half yellow box next to Enterprise. The workaround for what you are describing would be to go into ProgramData (hidden folder, will have to type it into Windows Explorer) >> National Instruments >> License Manager >> Licenses and move the Enterprise .lc file outside the Licenses folder. It probably has "TmpEthernet" in the name. This way, License Manager would not be able to find an evaluation version license and I would expect the checkbox next to Enterprise to appear white after refresh. Then, the software would have to look toward the full license and no builds would be expiring.
    This works, but is still leaves the possibility for the step to be forgotten and the software to fail shortly after delivery, which is obviously no good at all!  Please fix this!

    Thanks for the response Daniel,
    The issue and behavior are a little different than your scenario. First, I don't add a reference to Analysis.Enterprise.dll.  I only use DLLs which my standard license covers.  However, if I had used Analysis.Enterprise.dll, there would be no build error.  When I activate Standard edition, the Enterprise trial remains active, and is not cancelled or superceded by the Standard edition license.
    The process is similar to what you've described, though. I think that the evaluation period is longer than 7 days - I see that described at http://www.ni.com/mstudio/download/, but the manual at http://www.ni.com/pdf/manuals/350836e.pdf says on page 7 "Any applications you build with the Measurement Studio Evaluation package have a 30-day evaluation period.", which matches my experience.  The process goes like this:
    I first install Visual Studio 2012, and license it.
    Install Measurement Studio 2013 (2015 now!), which defaults to the Enterprise evaluation, licensing itwith my Standard serial number.  This is a part of the installation process: Download http://ftp.ni.com/evaluation/labview/ekit/other/downloader/MStudio2015_downloader.exe on a fresh install and click through, and you'll see that there's a screen in the installer which requests the serial number.  I enter it in this step; there's no reason for it to be licensed with the Enterprise trial at any time.
    Then, I check out the application from our source control, and open it in Visual Studio.  The check out includes the DLLs: 
    NationalInstruments.Common.dll
    NationalInstruments.DAQmx.dll
    NationalInstruments.MStudioCLM.dll
    NationalInstruments.NiLmClientDLL.dll
    NationalInstruments.UI.dll
    NationalInstruments.UI.Styles3D.dll
    NationalInstruments.UI.WindowsForms.dll
    (note that Enterprise Analysis is not included) and the license file: 
    NationalInstruments.UI.WindowsForms.ScatterGraph, NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4
    NationalInstruments.UI.WindowsForms.Legend, NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4
    (note that Enterprise Analysis is not included; these are the only UI components that the application used).  The project file references the DLLs in the project folder:
    <Reference Include="NationalInstruments.Common, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.Common.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.DAQmx, Version=14.1.45.13, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=x86">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.DAQmx.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.MStudioCLM, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <EmbedInteropTypes>False</EmbedInteropTypes>
    <HintPath>lib\NationalInstruments.MStudioCLM.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.NiLmClientDLL, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.NiLmClientDLL.dll</HintPath>
    <EmbedInteropTypes>False</EmbedInteropTypes>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.UI, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.UI.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.UI.Styles3D, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=x86">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.UI.Styles3D.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NationalInstruments.UI.WindowsForms.dll</HintPath>
    <Private>True</Private>
    </Reference>
    <Reference Include="NLog, Version=2.0.0.0, Culture=neutral, PublicKeyToken=5120e14c03d0593c, processorArchitecture=MSIL">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>lib\NLog.dll</HintPath>
    </Reference>
    Note that NiLmClientDLL and MStudioCLM are not copied to the output folder.  A later entry in the project file includes the license file in the build: 
    <EmbeddedResource Include="My Project\licenses.licx" />
    I then build the project, make whatever customizations required for this particular build, and we ship the machine.  Then, the customer calls 30 days later, complaining that the program won't start.  
     

  • MS Office 2013 Standard Error Code: 25004 on Windows Server 2012 R2

    We are doing some server maintenance and upgrades for one of our servers here at work. When trying to install MS Office 2013 Standard from a Volume License we are getting the error 25004 which states the installation cannot go through due to a previous
    installation of office on computer from a trial license. Everything has been removed and we've follow numerous steps to remove files in order to get the installation to reach 100%. Unfortunately every step we've taken we are still getting the error 25004.
    We've ran Microsoft FixIt as well as followed the steps from numerous articles here.  Please if anyone has experience and solved this issue respond back with the solution. As of now this server is down due to installation failure of office.

    The 25004 is normally associated with trying to re-installa trial on a machine that has had that trial installed. But you say that is not the case
    Did you just click "Run" directly when you try the Fixit tool? The Fix It tool
    might not work if you click "Run" directly, Please try to save the Fix it tool locally and then use it. Even if you think you don't have Microsoft Office installed, run it anyways.
    You might also need to try the manual removal steps given in
    http://support.microsoft.com/kb/2739501? If you’ve tried only the Fixit so far, try the manual removal steps now. Then restart and reinstall.
    This might be helpful:
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-visio/visio-install-fails-error-25004-system-error/e3663e9a-a112-487d-9e81-7a33cc2783fe
    Ashish

  • Co-Existence Office 2013 Standard & Professional

    Hi,
    We have 4 Remote Desktop Servers 2012R2 with Office 2013 Standard.
    We also own Open Licenses for this for each user.
    1 user now needs PowerPivots in Excel, which is only available in Excel 2013 Professional, not in the standard edition.
    We purchased 1 Open License for this user for Office 2013 Pro.
    On a Testserver I've installed Office 2013 Standard with all features.
    After that I've installed Excel 2013 Professional.
    Now, whenever someone opens "Excel 2013" on Testserver from apps it opens Excel 2013 Professional, not standard.
    Apparently Excel has totally forgotten about the Standard version.
    I wouldn't even know how I can specifically start Excel Standard instead of Professional since they both seem to share the same exe (C:\Program Files ((x86)\Microsoft Office\Office15\excel.exe). It just starts Excel Professional each time.
    Is there a way to restrict Excel professional to this one user ? and let other users still use Excel Standard ?
    I'd like to know this before I deploy Excel Professional in our RDS pool.
    If no one can answer this : Excel Professional it will be for everyone and this thread will serve as my answer the day MS comes complaining about missing Office Professional licenses.

    Hi Chloe,
    Thanks for the suggestion. 
    I went ahead and installed Excel 2013 Pro on our RDS pool, on top of the existing Office 2013 Standard.
    I've skipped all the other Pro features during install (access, etc.).
    We only need PowerPivot and users need to manually activate it in Trust Center > Add Ons. I've only enabled it for the one user who needs it and who is licensed to use it.
    So I guess we aren't really breaking any laws here.
    Thanks again, Vincent

  • App-V 5.0 SP2 sequencing Visio / Project 2013 with setup.exe /packager fails

    Hi @all,
    unsing the deployment tool this configuration.xml:
    <Configuration>
    <Add SourcePath="C:\office-appv\source\" OfficeClientEdition="32" >
    <Product ID="VisioProVolume">
    <Language ID="de-de" />
    <Language ID="en-us" />
    </Product>
    </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="OfficeSetup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>
    for Visio / Project VL (sources where downloaded with this configuration.xml as well)
    with this blog:
    http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
    Packager tells me that the package was created successfully, but no package was created.
    When I take a look in the logfile, it Shows me an error:
    Timestamp Process TID Area Category EventID Level Message Correlation
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run aqkhc Medium CmdLine:"C:\Users\bechtle1\AppData\Local\Temp\Microsoft Office 15\ClientX64\integratedoffice.exe" FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv"
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run Telemetry aqkhd Medium {"SessionID":"2e7c6873-7ef6-4ee4-bc2e-248c237f4bd9","GeoID":"94","Ver":"15.0.4569.1504","Bitness":"64","IntegrityLevel":"0x3000","SecuritySessionId":"5"}
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run Telemetry aqkhe Medium {"SessionID":"2e7c6873-7ef6-4ee4-bc2e-248c237f4bd9","GeoID":"94","Ver":"15.0.4569.1504","OSVersion":"6.1","SP":"1","ProductType":"3","ProcessorArch":"9","Locale":"1031"}
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run ap2kl Medium Args::Args - C2RClient IntegratedOffice.exe receives command line {FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv".}
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run ap2km Unexpected C2RClientCommandArgsFactory::CreateC2RClientCommandArgs - Not supported mode: FLATTEN
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Click-To-Run ap2ko Unexpected ::wWinMain - Error encountered starting IntegratedOffice.ext with command line FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv". Exception: InvalidArgument (Not supported mode).
    02/26/2014 16:46:45.307 INTEGR~1 (0xeac) 0x5030 Logging Liblet aqc99 Medium Logging liblet uninitializing.
    Regarding to KB VL is fully supported.
    Has anyone the same issue?
    Regards,
    Bernd.

    I 'sequenced' this recently. The Volume License version too. I believe the only difference in what I did was that I didn't set any other languages. If you try with just the below, do you see the same results? Could try and play the process of elimination
    game
    <Configuration>
      <Add OfficeClientEdition="32" >
        <Product ID="VisioProVolume">
        <Language ID="en-us" />
        </Product>
      </Add>
    </Configuration>
    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
    rorymon.com Twitter: @Rorymon

  • Choosing Office 2013 volume licensing plan ... or going retail ... or subscription ... or hunting for 2010 ... what a headache ...

    Our company currently runs an office software equivalent comparable to Office 2003 level. I was researching options (licensing!) for stepping up our office to real Microsoft Office product ... and got stuck with that idea ... totally confused at this point.
    Am I missing something or the cheapest SMB volume licensing option for MS Office 2013 (Standard, no Access component) is like twice as expensive as the retail equivalent? Why is that so? It makes no sense to me at all.
    I can find retail box of Office 2013 Home and Business for around $190 while the cheapest Open License for similar equivalent seems to be priced at $369 (what!?) ... and that is even without Software Assurance?
    Makes it kinda hard to convince management about benefits of VL program over retail ... especially since we are not a Volume Licensed customer (yet) and this purchase *might* make it worth becoming one (does it?).
    On top of that I can't even make decision if we should really go with Office 2013 after reading about live/online account requirement for activation, and here a question how does it work in volume licensing version? I assume it will be a great pain with
    installs from retail media and activation, but VL should have some tools or workarounds for that, no? I read that Office 2010 didn't have such problems and am sad I didn't push towards it when it was still available on retail market.
    Maybe we should go with 2013 subscription for first year and see how that works for us ...
    One thing for sure, I've been digging around this subject for weeks and my headache doesn't want to go away.
    Open to suggestions.

    anybody, any insights?
    Pls, also note that I run a one person IT department for this company, so all the dirty work (installs) will be done by me, hence my question. I can do deployments via GPO, but would like to know about activation gotchas (MS live accounts) for Office 2013,
    is that true for retail licenses?
    As per Volume Licensing, am I looking right and cheapest 1 computer Office 2013 open license stands for like $369? why is i so expensive in volume licensing plans? I doubt our management approves it this way ... which probably means retail licensing for
    me and a great headache with activations over a sneaker net ... times 30 ...

  • Acrobat XI no longer works after installing Project 2013

    Hello All,
    This one is really odd and I can't find any documentation anywhere.  I have a client that has Office 2010 and Acrobat XI Standard.  I just installed Project 2013 on the machine and now right clicking on any Office file will not show the option
    to create PDF.  He can right-click on a Project file and create one but not on any other Office file.  I have never seen this before.  Any thoughts?
    Regards,
    Rob Battaglia

    Yes I have - no luck.  This system is using Office 2010 x64 and Project 2013 x64.  This all happened after installing Project.  The right click on a file works for Project just not for Office.  I did check to make sure the add-in was
    present for both Excel and Word - PDFMaker.dll is selected in both and the user can create PDF files from within Word and Excel - just not when right-clicking on the file in Windows Explorer.
    Regards,
    Rob Battaglia

  • Can't Create PDF from Microsoft Projects 2013

    I am trying to PDF a Microsoft Projects 2013 files.  I've tried print PDF and save as PDF but both options give me a pop up window that says "Creating Adobe PDF" with a progress bar displayed with 3 blue bars filled.  I leave it that way for about an hour and nothing happens.  I've tried updating the Adobe Acrobat and Repairing it in the Programs and Features menu.  Any help will be greatly appreciated.  Thank you.

    Thanks for the prompt response.  I don't know how to print-to-file and open the file in Distiller.  The printing as PDF doesn't even work.  It gives me the "Creating PDF" pop up window to which there is no end to. (see photo above)  As for updating to version XI, my colleagues who are running Acrobat X Standard with MS Projects 2013 do not have a problem at all when printing.  I want to avoid upgrading if version X is still usable.  Any other thoughts?

  • The printing of .pdf file from Project 2013 stops when the file name should be written. Project 2013 crashes. Does someone know what is wrong between Project 2013 and Adobe Acrobat 9?

    The printing of .pdf file from Project 2013 stops when the file name should be written. Project 2013 crashes. Does someone know what is wrong between Project 2013 and Adobe Acrobat 9?

    The Acrobat 9.x product family passed into "End of Support" mid-year of 2013.
    Acrobat 9 support of MS Project via PDFMaker stops with Office 2007.
    For Office 2013 support you must use Acrobat XI (11.0.1) or newer. 
    A good to have reference:
    https://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html
    Acrobat Pro and Standard DC are what are currently available for purchase. 
    Be well...

  • Configuring RDS to specific NIC Adapter + Avoid Office 2013 Volume Licensing

    Background: Small Company basically 1 User (me)... I've recently purchased a new server class computer and have downloaded and installed Windows Server 2012 R2 Essentials.  I have 2 routers, 1 for home use (192.168..) and other provided to me by the
    company I contract to (10.41..).  I have a 4 port independent NIC card.  I connect to a company configured VM through a Remote Desktop Connection.  I also need to run Lync 2013 on the Windows Server 2012 machine in order to communicate internally
    with other members of the company.
    My Understanding: In order to configure the remote desktop connection to my VM to use a specific NIC adapter I must first install the Remote desktop Session Host service.  Then I should be able to configure the RDP-TCP connection to use a specific NIC
    adapter.  However, when I install the Remote desktop Session Host Service and I try and run Lync 2013 I receive an message stating that because I'm running Remote Desktop Services on this server I need to purchase volume licensing for my Office 2013 product.
    Question: Is there a way for me to configure my Windows Server 2012 R2 environment so that I can first specify a specific NIC adapter to use during my RDP session into my VM and also allow me not to have to purchase volume licensing for the Office 2013 product.
    -=Duane=-

    Hi Duane,
    As per my research, if you have RDS license and CAL installed still you need to purchase Office licensing to use office product. Office Professional Plus 2013 and Office Standard 2013 are licensed on a per-device basis. Users can only remotely access a copy
    of Office Professional Plus 2013 or Office Standard 2013 running on a network server from a licensed device. Therefore, your windows need the latest Office suite license assigned to the device.
    For more information.
    1.  Licensing Office on Remote Desktop Services
    2.  Microsoft Office
    For Network Adapter, you can try PowerShell Command and rename your NIC specific to RDS so that you can identify that specific NIC is used by RDS for connection. For that you can do following things.
    List of Network Adapter: Get-NetAdapter 
    Rename Network Adapter: Rename-NetAdapter -Name "Wired Ethernet Connection 4" PublicInternet1
    Please find below snap and link for more information.
    1.  Using PowerShell for NIC Configuration Tasks
    2.  Use PowerShell to Configure the NIC on Windows Server 2012
    Hope it helps!
    Thanks.

  • Lync with Microsoft Project 2013

    Hi,
    I have Microsoft Lync 2013 and Microsoft Project 2013.
    Can anyone send me the steps to integrate these two so that i can get the updates from the team members without leaving Microsoft Project?
    K.Gokulraj

    In addition to Ben his answer.
    The integration with Lync is not supported in Project Standard only in Pro & Web App:
    http://blogs.office.com/2012/10/19/project-and-lync-together-reducing-communication-barriers/
    https://technet.microsoft.com/en-us/library/ee683978.aspx
    - Dennis | Netherlands | Blog |
    Twitter

  • Exchange Server 2013 Standard User CALS

    Hi there we have exchange server 2013 Standard with 300 User CALS installed on Windows Server 2012 R2 Standard.
    We bought 300 User CALS for Exchange Server 2013 Standard  , do I need to Buy the same amount (300) user CALS for Windows Server 2012 r2 too .. for people to have acess to the outlook
    web app , or just the user cals that are bought for Exchnage server 2013 will be sufficient ?
    please some one let me know asap

    Hi,
    As you known, software license is a legal instrument governing the use or redistribution of software. However, software license is NOT universal for whole world. The license content is different for countries or regions.
    Please suggest customer contact local Microsoft customer support to confirm this issue.
    Thanks for your understanding.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange server 2013 Standard will support for Exchange cal Enterprise???

    Hi,
    We have Purchased Exchange Server 2013 STD Edition and Exchange server CALs are Enterprise.
    is it compatable for this...
    can u give reply for this...

    Hello Sashys,
    Here’s full explanation:
    http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx. You should have at least standard CAL for each of your users. Enterprise CAL's are an add-on to the standard license, that provides additional
    features. Moreover both types of CAL's can be used with either Exchange server 2013 Standard or Exchange server Enterprise.
    Hope it helps,
    Adam
    www.codetwo.com
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
    find the answer faster.

  • Dictionary Option in Word 2013 Standard on Server 2012 R2 Remote Desktop Services Server

    We have a customer running Server 2012 R2 RDS with Office 2013 Standard. They are licensed for Office 2013 via Office 365. Office 2013 Standard is installed on the server via a using the Volume license as directed by MS. 
    Each user has a Microsoft Office 365 account.
    When the user attempts to use the Right Click -> Define Option in MS Word, the user is prompted to sign in so they can select a dictionary. 
    This is where the problem begins. The login process does not accept the users Office365 account. I was able to create a new Microsoft account (using the same email address as the Office 365 account) and select a dictionary.
    Is this the only method to get the dictionary to work? All 100 users must create another Microsoft account and use that to select a dictionary?

    Hi,
    What Word prompts when user attempts to login with the original account? Any error messages?
    Since the feature will work if you create a new account, have you ever compared the property of these two accounts? Maybe the security or permission setting during the creation process?
    We lack testing environment here for this kind of issues, and we have another dedicated support teams in
    Microsoft Office 365 Community. I would suggest you to post there, where you can get more experienced responses:
    http://community.office365.com/en-us/f/default.aspx
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Thanks,
    Ethan Hua CHN
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

Maybe you are looking for