Trouble with Office 2013 and KMS activation.

I have a KMS server running on Server 2008 R2 that was serving out activations for Windows 7 and Office 2010. I ran the Office 2013 activation
pack on the KMS server and now it also shows our KMS key for Office 15. I realize that I need a minimum of 5 in the count field in order for activations to happen.
We use VMware VDI and I spun up a pool of 10 with Office 2013 installed on the master. Before creating the desktop clones, I rearmed the master and then shut it down, snapped it and created the desktop clones. I have logged onto most of the clones
with a number of different user IDs and when I look at the KMS server it now shows that the count is 9 - so I would assume that my copies are being activated. However, when I look at Office on the VDI clones or on my own personal computer that has 2013
installed I see that the product still needs to be activated.
Yes we have the VL service record in DNS pointing to the right server - it's been there for ages taking care of Windows and Office 2010. I did not have this issue with either of the other products and KMS. I am at a loss as to what
to do next.
Thanx...

check the client-side event logs for the SPP events (request/response), is the client (your pc for example), hitting the expected KMShost, and what response resulted?
Also check the KMShost event logs, is the request from your pc arriving there, and what came in, and went back as a response?
If you're not familiar with how to "decode" the events, check here:
http://technet.microsoft.com/en-us/library/ee939272.aspx
In case you have a "rogue" KMShost:
http://blogs.technet.com/b/odsupport/archive/2011/11/14/how-to-discover-kms-hosts-via-a-dns-query-and-remove-them-if-need-be.aspx
EDIT: PS, not that it matters for this question, but there is a dedicated forum for OFF2013:
http://social.technet.microsoft.com/Forums/en-US/home?forum=officesetupdeploy :)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

Error when enabling the connection group with office 2013 and a plugIn

Hi,
I've created the office 2013 proplusVolume with ODT, published it globaly, Sequenced the plugin, with only the office 2013 as a published app-v package on the system, made the connection group with correct xml, but when I enable the connection group, I got
the error:
The connection group {xxx} version {xxx} could not be published because the
virtual COM settings of the individual packages conflict.
Verify that the virtual COM settings are the same for all member packages and try again.
The COM settings are made the same as the office package on the plugin package, but I still have the same error.
The Deployment-, and user-XML have this values (as it was for the office originally):
<COM Mode=”Integrated”>
<IntegratedCOMAttributes
OutOfProcessEnabled=”true” InProcessEnabled=”true” />
<Objects Enabled=”false” />
Why do I get this error?
Why is it merly impossible to track down the realy error?
What can i do to make this connection group work?

Right now the catalog is pulling from the AppXManifests inside the AppV Packages. You can see these settings by renaming the AppV file to .ZIP and browsing those files (READ ONLY) to see the default COM settings. Simply changing the Deployment Config files
is not enough. You will need to make sure the information is dynamically applied at publishing by specifying the -DynamicDeploymentConfiguration option when adding the package using the Add-AppvClientPackage cmdlet. You do not need to worry about the UserConfig
file.
If you are doing this in band with the management system, you would import this configuration in under Advanced Configuration for the package.
Steve Thomas, Senior Consultant, Microsoft
App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat
http://blogs.technet.com/gladiatormsft/
The App-V Team blog: http://blogs.technet.com/appv/
The MED-V Team Blog: http://blogs.technet.com/medv
The SCVMM Team blog: http://blogs.technet.com/scvmm/
“This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

Unable to edit document from SharePoint 2007 using Office 2013 and IE 11

I am getting the following error when I try to edit a document from SharePoint 2007: "Edit document
requires a Windows Sharepoint services-compatible application and Microsoft Internet Explorer 6.0 or greater". I am using Windows 7 with Office 2013 and Internet Explorer 11. Troubleshooting steps that I've tried so far (that haven't worked) are as follows:
1) repaired Office; 2) switched from 64 bit version of IE to 32 bit version; 3) moved the owssupp.dll from C:\Program Files (x86)\Microsoft Office\Office14\ to C:\Program Files (x86)\Microsoft Office\Office15; 4) tried removing old versions of Office (but
I still need to use Office Communicator 2007 r2 and couldn't figure out how to get rid of the Office14 files from Program Files); and 5) running SharePoint in IE compatibility mode. Please advise...thanks!

Hi,
It seems you installed mixed version Office2007/2010/2013 on your client machine?
I would suggest you remove all Office 2007 and 2010 version, and reinstall Office 2013(include Office Tools->Microsoft SharePoint Foundation Support component) on your machine, and make sure "Open SharePointDocuments class" add-on is enabled
from IE11, then check if it could fix the issue.
If above works, please test again after installing the Office Communicator 2007 r2 on your machine.
http://social.microsoft.com/Forums/en-US/3e8c0976-2794-49a2-92fe-6a254b3cc4ca/a-microsoft-sharepoint-foundation-compatible-application-could-not-be-found?forum=projserv2010setup
http://blogs.technet.com/b/emeaoffice/archive/2013/04/29/you-get-an-error-message-when-you-open-an-office-file-from-sharepoint-on-a-computer-on-which-you-installed-more-than-one-version-of-office.aspx
Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Daniel Yang
TechNet Community Support

Acrobat XI combine to PDF feature is not working with Office 2013 is there a compatibility issue?

Tested with Office 2010 and it works fine
Seems to only be the combine to PDF feature that doesn't work, done updates, tried combining a variety of documents still no joy

There isn't any compatibility issue with Office 2013 and Combine should work with office 2013 same as it with 2010.
Can you please tell us some more details so that we can investigate the problem which you are facing:
1) Please update the exact Acrobat version you are using. This you can find out via "Help -> About Adobe Acrobat XI Pro.." Version should be something like 11.0.x. If it is not 11.0.7, then please update it to 11.0.7 and try again.
2) Is this problem you faced recently (after some update - Acrobat or OS update) or it never used to work earlier for you?
3) You mentioned that when combining, it convert first document only. Can you please let us know how many documents you are combining and what are those formats?
4) Also please update about you environment as well. Is you Operating System and MS Office 32bit or 64bit?
Thanks,
Vishal

MSO.DLL not installed with "office home and small business 2013"

Hello,
In my 32 bits application, I use the IInPlacePrintPreview interface on a "word.document" OLE object to show a preview of a word document.
That's work fine with Office 2013 Standard Edition (32 bits) on a Windows 7 x64 Edition, but my application crash with "office home and small business 2013" (32 bits).
I have noticed that the call to query the IInPlacePrintPreview interface on the OLE object load the mso.dll of Office into memory.
The mso.dll is installed with the Office 2013 Standard Edition, but not with the "office home and small business 2013" Edition.
I guess the problem is the lack of
mso.dll.
Do you know why the mso.dll is necessary for the preview of a word document ?
How do I install and configure mso.dll on a
"office home and small business 2013" edition ?
Thanks for your help.

Hi,
You may try the ODT (Office Deployment Tool) to configure the Configuration.xml file and install the Office 2013 Home and Business edition.
Please refer to the following steps:
1. Downloading ODT from: http://www.microsoft.com/en-us/download/details.aspx?id=36778
2. After downloading the ODT, there will be a Configuration.xml file ODT installed folder. Modify the Configuration.xml file as below so that we can download home business package.
<Configuration>
<Add SourcePath="D:\Office\" OfficeClientEdition="32" >
<Product ID="HomeBusinessRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="D:\Office\" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
For more information regarding to the ODT, you can refer to the following link:
http://technet.microsoft.com/en-us/library/jj219422(v=office.15).aspx
Should you have any questions, please feel free to let me know. many thanks!
Michael Bai
Office Client Support

Crystal report 8.5 export to csv and rtf format not working with office 2013

Hi Experts,
Crystal report version 8.5 hangs and eventually crash when i export my report to csv or rtf format on windows 7 with office 2013 installed, code is written in VB 6 although the same scenario is working with office 2010 installed.
i debugged the code and found the application hangs at function Report.Export(False).
below is the code snippet
       .PDFExportAllPages = True 'ePDFExportAllPages
       .PDFFirstPageNumber = ePDFFirstPageNumber
       .PDFLastPageNumber = ePDFLastPageNumber
       .RTFExportAllPages = True 'eRTFExportAllPages
       .RTFFirstPageNumber = eRTFFirstPageNumber
       .RTFLastPageNumber = eRTFLastPageNumber
       .UseReportDateFormat = eUseReportDateFormat
       .UseReportNumberFormat = eUseReportNumberFormat
       .UseReportNumberFormat = eUseReportNumberFormat
       .XMLAllowMultipleFiles = eXMLAllowMultipleFiles
       .XMLFileName = eXMLFileName
     Report.Export (False) ----Application hangs here and eventually crash
Looking forward for your help, as it is very urgent
Regards
Mohit

Hi Mohit
CR 8.5, being about 15 years old, does not support Windows 7. I am surprised this works for you with MS Office 2010 and to be honest, I'd consider my self lucky there. The fact that is does not work with office 2013... well, like I said, lucky with Office 2010 and your luck ran out with Office 2013.
Your option; rewrite the app in VS 2010 / 2012 / 2013 and use the CR Assemblies for VS .NET from SAP Crystal Reports, Developer Version for Visual Studio .NET. The CR Java SDK would be another option.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Office 2013 pro plus activation fail on windows 8

hi guys
I have issue about getting Office 2013 pro plus activation fail on windows 8 via KMS server.
When I test using KMS server via nslookup -type=srv _vlmcs._tcp all looks good with corporate KMS server.
Activation fine with windows 7 environment
Any idea
This topic first appeared in the Spiceworks Community

Hi
We recommend you download it from the website and extract it again to make sure your source install is complete.
Run setup.exe as administrator then try the install.
If the issue persists, refer to the article on General troubleshooting for installing Office 2013 and Office 365:
http://support.microsoft.com/kb/2822317
Regards
Tylor Wang
TechNet Community Support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Is it time yet for Microsoft to "Recall" Office 2013 and provide anyone who has a 2013 license a replacement Office 2010 license?

The interface is terrible and can't be changed. Every application in the suite locks up/crashes nearly constantly on any machine it is used on. The activation process is terrible and wastes hours of any support/IT dept's time. From a 'privacy
standpoint', the software is seemingly criminally intrusive. It is clearly a product that should never have been released and is so far from functional that it can't be repaired by any 'service pack', 'hotfix', or 'patch'. It needs to be completely
scrapped.
The only 'redeeming quality' of this software is that the guy who was in charge of creating it is gone from Microsoft. (Unfortunately, he is now President Obama's appointee for running the attempt at repairing the 'healthcare.gov' website...
out of the frying pan... )
When the software is installed using one profile (domain or machine account) and a different profile tries to use the software, it requires 're-activation' - which often fails because the software believes it has been installed multiple times. (This is particularly
frustrating because it has to be installed by an administrative user, but most of the time, the person who 'uses' the software is not the 'administrator' - so it is almost always being 'installed' using one profile and 'used' using another profile).
The necessary intrusion into privacy created by the requirement of a "Microsoft Account" to use the software is seemingly criminal.
The tracking of, and installation of licenses is absolutely ridiculous.
An example:
Many of my clients have many users and many computers (up to 75 or so).
I could create a "Microsoft User Account" for each 'user', but these machines get moved between users, and the software license is tied to the 'machine' and not to the 'user' so as soon as that happens, the licenses and the users are no longer
in line and become impossible to track.
I could create a "Microsoft User Account" for each 'computer'... and I can't even count the ways this would be a nightmare to try to track.
I actually did that up front for one client, and created Exchange email boxes for each computer so that "prove you are really you" emails from Microsoft could be received managed, and responded to, and passed out second usernames and passwords
to all of the users so they could "log-in" to their Office 2013 software, and created a database of the 'computer usernames and passwords' so I could track this... unfortunately, this confused the users (as it rightfully should) so they would change
the passwords for their computer's 'Microsoft User Account' thus locking me out and invalidating my database, ... and... CLUSTERF#%K!!!
As a 'best - worst case', I have had to create a single 'Microsoft User Account" for each of my clients' businesses so I can install and activate Office 2013 products. This is a whole new set of "Awesome Stupidity".
Now, I can put a new computer into a client's office and install their new license key for their oem Office 2013, and it shows up in the 'business's Microsoft User Account'. Then when I give the machine to the user, I get to 're-activate' the software
(hoping that it doesn't tell me to piss-off - which happens about 40% of the time. This is a process that can only be described as a "feat of engineering created by a group of monkeys whose former jobs included 'janitor at MAD magazine headquarters'
or 'beer-pong referee').
It starts with two hours of pressing phone buttons and ultimately talking to someone who tells me "yeah, nothin' I can do about that I'm just here for product activation" (which, incidentally, is done by machine until you pass through MS's ridiculous
labyrinth of repetitious keystroking until the machine is convinced you are just too stupid to punch in the right numbers and allows you to talk to a person... who then asks you for the exact same set of numbers and repeats back the exact same responding set
of numbers and acts dumbfounded when it still doesn't work - since it didn't work the first six times you punched or said it into the phone) followed by "I need to send you to the support group... but because it's 6:30 pm (in a process you started at
3:00pm) they are gone for the day and you'll have to call back on Monday morning"
At some point in the process, you get to log into the "Microsoft user account" and 'roll the roulette wheel of stupidity' by trying to activate the right software from a list of 40 different lines that all say "Microsoft Office 2013 Home and
Business oem", but none give any indicator or differentiating factor like for instance: license key, date installed, license key last 4 digits, mother's maiden name, phase of moon when software was first activated, color or type of blood of the user's
paperboy's dog's previous owner... NOTHING... RANDOM FREAKING STAB IN THE DARK - pick one, any one, hope its the license you are trying to install onto this machine, 'cause if not, you very well may kill the product on some other machine.
So through the process, the lucky support staff person gets' to waste roughly an hour and a half on average for every Microsoft Office 2013 installation. I have actually had to start telling my clients that they are going to likely have to pay an extra
$100 or so per machine in order to get their new Microsoft Office software which comes on their new computer activated - that number tends to work out roughly accurately - except that it is a terrible way of trying to 'please a client'.
Oh,... and did I mention... "THE SOFTWARE CONSISTANTLY FAILS"!?!
A client tries to open a document that they have been using for 8 years and Excel doesn't say "Hey, I don't know how to deal with some element of the file that you put in here using Excel 2003, or Office 2010 (both products, by the way, which worked
great) - no... instead,... it crashes. Doesn't really do any damage to the file it choked on, but the work you'd been doing on three other files which you also had open,... yeah,... that work is gone.
Yeah,.... over time, I have developed a pretty consistent spiel for client's needing new computers that goes over how absolutely terrible Office 2013 is, and explains that our options are further limited by Microsoft's yanking of all Office 2010 or previous
products from market availability, and explaining the merits of both LibreOffice and OpenOffice, as well as their drawbacks. I also have a strangely static response explaining how "larger companies are not burdened by these issues because they are
able to use MOPL which allows them to downgrade their productivity software to Office 2010 so they can continue to function happily, but this is really not a cost effective solution for smaller companies who primarily buy oem Office products with their replacement
computers".
Unfortunately, many clients still decide they want to go with Office 2013 because they apparently believe "it really can't be that bad". The value in my 'presale descriptions' are only really realized when they come back to me a week, two
weeks, or up to a month after the new machine is in place and say "wow,... you were right". The place I am left open for any further problems is when I don't impress upon them beforehand just HOW BAD OFFICE 2013 REALLY IS. In that case,
they still come back to me as though I have done something wrong foe selling them this piece of $#!% software and I have to remind them of our previous discussions.
Strangely, far too few heed the warnings and buy the software anyway - but the discussion has saved many clients the costs of Microsoft Project, because the discussion of LibreOffice and OpenOffice nearly always leads to at least a small philosophical conversation
about 'Open Source Software' in general, and my absolute favorite descriptive analogy in that discussion is to compare Microsoft Project at $600 v. ProjectLibre at $0 - and then further describe the costs of licensing and implementing the associated back-end
server solutions, etc.
This is a saving grace for me, because even though the client has been saddled with Office 2013, they have also saved substantially on Project and it is a rare (but granted, not absolutely absent) occasion that ProjectLibre is lacking some feature or function
that they actually need or want to use - and on those occasions, finding out has cost them absolutely nothing in software purchases.
Its not surprising, I suppose, that clients have grown to accept Office as a required 'cost', but still choke heavily on the price-tag of Project every time they have to buy it. The interesting thing to watch over the coming couple of years will be
'how many businesses stop accepting MS Office as a 'required cost' due to the failing of the software itself and the fact that most are being burned, at least once, by purchasing the software "against technical advice" and are learning, merely by
virtue of HOW BAD Office is, that there are other options out there that both cost less and work better... I mean,... LOTS BETTER.
How many businesses that are used to accepting the cost of Microsoft Office as a cost of doing business will be moved over to open source options and satisfied by them by the time Microsoft releases its next version - which will, presumably work - such that
they will no longer justify the cost of Microsoft's offering even if it is 'superior' to the open source offerings because the open source offerings are plenty sufficient and include a price tag of $0 and an installation/implementation time that is much, much
shorter than Microsoft's offering.
If Microsoft doesn't make some dramatic reparations, and do it soon, I expect their market share will be reduced in this area by a very significant margin.
I am suggesting either a 'Complete Recall' of Office 2013 including an 'uninstall 2013/install 2010' process driven by the automatic update engine, or at the very least, a free and easy downgrade rights offering for anybody who has already purchased 2013
and anyone who purchases it between now and the time the next "functional product" is released.

I understand the inconvenience you are experiencing when working with Office 2013.
If you have any feedback about Office 2013 product, click the and submit to Microsoft.
Microsoft will decide how to fix the problem for all customers.
For the activation mechanism, it intends to protect customers of their rights and interests.
For a retail version of Office, if it was purchased with a disk, Microsoft account is not necessary during the installation.
For volume license of Office, refer to the following link to deploy Office suites can be much efficient:
http://technet.microsoft.com/en-us/library/cc178982.aspx
For the problem Office 2013 keep crashing, check the following link to check:
http://support.microsoft.com/kb/2813143/en-us
http://support.microsoft.com/kb/2758592/en-us
Thanks,
Tyor Wang
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

Office 2013 and MS Server 2008 R2

I see an increasingly number of people having trouble with office 2012 running on 2008 R2 RDS servers, but i still am yet to find any good solution from Microsoft themselves.
We now have two customers with 2008 R2 RDS servers and Office 2013, where users are reporting that Outlook is slow when opening messages, typing messages, searching in the mailbox and sometimes everything also freezes for a few seconds if they are working
with an Office application. Similar problems are also happening with Word and Excel.
We have tried all the usual tweaks so far:
Ajusting RDP-settings to 16-bit color and no animations.
Disabling hardware acceleration for Office.
Disabling animations reg-key.
The servers are all virtual, running on vmware on some of the latest hardware from dell, so resource-wise there should be no problem. Increasing memory and CPU is not helping at all anyway.
The customer we have that are running RDS on 2012 and 2012 R2 also had this problem, but adjusting the visual effects solved all problems for these. But not for those on 2008 R2.
I am stuck at the moment, and the frustration is rising at my customers. Does anyone actually have anything that solved this problem for them? Or do we actually have to roll back to Office 2010 (where we had no problems)?

Hi,
For Office 2013 there should not be any concerns since it is windows installer based and things will be handled automatically. For the other software you could simply put the session in install mode in every case. For the servers/workstations
where install mode doesn't apply the change user /install and change user /execute will simply fail without any harmful effects.
You may check whether or not the machine is a terminal server using WMI, for example:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting Get TerminalServerMode
0 = Remote Administration mode (not a RDSH/TS)
1 = Application Server mode (aka RDSH/Terminal server)
-TP
When I run the command from the command line, it works, but when I try it in a "IF" statement, nothing happens. I am I doing something wrong using the wmic code in the IF statement?

Printer driver hangs when printing with Office 2013/Windows 8 64 bit

Printer: HP Color LaserJet CM1312nfi
Printer Driver: V5.1 (up to date, downloaded from HP support website) or Generic V5.6
OS: Windows 8 Professional 64bit
When I try to print a certain Excel document with Excel 2013 and printer driver V5.1, the program hangs and needs to be terminated via task manager. This happens always with the same document, but not with all documents. The program hangs also when opening the print preview for the same document.
The same document prints fine with the generic printer driver V5.6 and with the driver that comes with Windows 8.
The same document prints fine with driver V5.1 under Windows 7 and Office 2010. The combination Windows 7/Office 2013 was not tested. The combination Windows 8/Office 2010 was also not tested.
When I try to print an empty document with Word 2013 and generic printer driver V5.6, the program hangs and needs to be terminated via task manager.
My conclusion is that the HP printer drivers have a problem with either Windows 8 or Office 2013 or a combination of both.
The printer driver that comes with Windows 8 and is automatically installed is useful as a temporary workaround, but it lacks certain options, e.g. manual duplex.
On request, I am ready to send the Excel document by e-mail for verification of the problem.
Any help or suggestions will be very much appreciated.
Thanks in advance,
Uli
This question was solved.
View Solution.

From what you describe you are having issues printing from MS Office. Have you had trouble printing from other resources on your computer (e.g. from the internet or another program)? The first thing I am going to suggest is that we start by uninstalling and reinstalling the printer from the resources available online.
First if you use a USB cord, make sure to remove it (this is important). Do not plug it back in until the software directs you to. Then go through the Devices and Printers, Programs and Features and Device Manager folders and insure that all copies, files, and programs related to the printer are removed. Then as directed, restart the computer.
In the START menu type "%temp%" and press ENTER. Here I want you to press Ctrl+A and hit DELETE. Some of the files will not allow you to delete them, skip those files and delete the majority that allows it.
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3562006&lang=en&cc=us...
Install that and let me know the result!
Have a great day!

Trouble with Office being slow...

I have an iMac with 16 gb of RAM and have trouble with Office being slow... is there a way that I can assign more memory to MS Office, so I can utilize all the RAM that I have available?

Sig,
My hard drive has approx 1.5 TB Free. And the iMac has around 9 GB Of RAM (out of 16GB) in the green
on the activity monitor. I know in older versions of the operating system, one could assign
more RAM to an open application, thus allowing the app to access more memory when needed
such as having huge amounts of text on the clipboard.

Problem with Office 2013 documents after PC resumes from sleep

Have a number of PCs in a work environment that exhibit the following error messages when they are woken from a sleep state and the user was working on a Word or PowerPoint document via a network share.
PowerPoint error: The file you were working with was modified during suspend mode, and the original version is no longer available. <file path and name.ppt> must be re-saved.
Word error: Word cannot establish a network connection with this document after the system resumed from suspend mode. Save the document into a different file to keep any changes.
Having searched the error message I can see that hot fixes were created to fix the issue in Word 2007 and 2010, but nothing seems to relate to Office 2013.
All the PCs have the latest OS and Office updates.
I tried the NetworkAvailableTimeInSeconds reg fix from this link - http://support.microsoft.com/kb/2626998/en-gb , and obviously applied it to the Office 2013 key, but to no avail. The additional steps talk about applying the available hot fix, but this
is not applicable to Office 2013.
Information:
All PCs Windows 8.1 Enterprise and Office Professional Plus 2013
Any help would be appreciated.
Thank you.

I have the same issue with 8.1 and Office 2013, and yes, Office is at SP1 (15.0.4631.1002). I've likewise done the Reg fixes suggested for 2007/2010, but still have the issue. Any insight would be appreciated.
Thanks,
John

How do I BLOCK access to ONEDRIVE that come with Office 2013 Home & Business

System consists of
Window 2012 Server + Exchange 2013
Workstaions are Windows 7 Pro with Office Home and Business 2013
I have been asked by the business owners to Block access to onedrive
documents are to be only stored on local Server
ChrisS

Hi,
We can disable OneDrive in Office with Group Policy.
First, please download Office 2013 Administrative Template files (ADMX/ADML) from this link below:
http://www.microsoft.com/en-us/download/details.aspx?id=35554
Then, press Win + R, type "gpedit.msc" in the blank box, press Enter.
The settings can be found under User Configuration -> Administrative Templates -> Microsoft Office 2013 -> Miscellaneous. Select the “Block signing into Office” option in the list of settings. In the Properties window, click “Enable” and select
the option “None Allowed.” Save the settings and open Word to check, there should be no OneDrive option for the user.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Office 365, Office 2013 and IaaS

Hello all,
I am planning to use a RDS environment built on AWS with Office 2013 pro plus deployed in it. Office 2013 pro plus would be licensed with a Volume License from a SPLA.
I would like to know if I can subscribe to Office 365 business essentials and then use this Office 365 account from the RDS environment and especially by interconnecting Office 2013 pro plus to it. Would that be MS compliant?
Thank you very much for your help.
Best Regards.

Hi,
You cannot use Office 365 Business Essentials license to connect to Office 365 ProPlus via a Remote Desktop Connection. This is because Office 365 ProPlus does not come with Office 365 Business Essentials.
To use Office 2013 via RDS connection, each user should be assigned with a license for Office 365 ProPlus, Office 365 ProPlus will then contact the Office Licensing Service on the Internet to obtain a licensing token for the user who uses Office 365
ProPlus on the computer and then activate Office 365 ProPlus.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

HP Officejet 4500 Ethernet / Wifi Driver Problem (blank fields) with Office 2013

Hi,
I have an Officejet 4500 (Ethernet) and I have exactly the same problem as lots and lots of HP Printer owners!
Everytime I try to print on Office 2013 + Win 8 64-bit, the Printer window comes with strange "Asiatic" symbols, and not the original language (Portuguese or English, I tried both). (Note: my father has exactly the same printer I have and he already had some problems also on Win 7 + Office 2010, then I deleted all HP drivers, installed again and it solved the problem)
I already tried the menus you people talk about but in my model I do not have such options. I already installed everything again and again...and always the same problem! With another printer from another company I have no problems with the drivers on Office, so it must be from HP Drivers that do not get along with Office 2013!!! Please update them as soon as possible...

Hello DaveZiffer,
Welcome to the HP Forums.
I see that you are having an issue since the installation of the Office program.
Here is a link that will take you to the 4 updates that are available for your printer.
After doing the updates, if you are still having issues, please feel free to write me back and I will be happy to research this issue further.
Thanks for your time.
Cheers,
Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
W a t e r b o y 71
I work on behalf of HP

Trouble with Office 2013 and KMS activation.

Similar Messages

Maybe you are looking for