Deploy custom templates in Office 2013

Hi All,
We have been using the backstage view of Office 2010 to deploy custom templates, as described in the TechNet article
http://technet.microsoft.com/en-us/library/cc178976(v=office.14).aspx
We recently upgraded to Office 2013 and have not been successful in getting our templates to show up in the backstage view. We have tried creating the spotlight registry keys under
the \Microsoft\Office\15.0\Common\Spotlight but this was also unsuccessful.
Has anyone been able to deploy custom templates using the 2007/10 spotlight approach outlined in that TechNet article?
Thanks
Dan

Thank you Max,
Can you please specify how the permissions should be set to allow Word 2013 to access SP 2013 via the XML file? Is it enough to simply be logged into SharePoint with Contribute rights to the library or is there more that needs to be done?
Hi Katie,
I believe Contribute permissions are enough for this case.
Have a look at the following solution, see if it works for your situation:
http://zasharepoint.blogspot.com/2014/04/sorry-we-couldnt-find-your-file-is-it.html
More hints to troubleshoot this issue:
Have you tested this issue on another machine?
Is proxy used?
Does the SharePoint environment has complex permission settings (e.g. the inheriting permissions are broken, or cross domain environment, etc.)?
Max Meng
TechNet Community Support

Similar Messages

Deploying custom templates only shows first template

Hi guys, I'm having an issue deploying custom templates.
I have followed the steps outlined here (http://technet.microsoft.com/en-us/library/cc178976.aspx) but when I open up Word/New I see the "CompanyName" under custom templates but when I open it I only see the first template "Letter".
I created the following entry in the registry:
HKEY_Current_User\Software\Microsoft\Office\14.0\Common\Spotlight\Providers\Companyname with a string ServiceURL pointing to the path of the xml file.
The XML file contains:
<?xml version="1.0" encoding="utf-8"?>
<o:featuredcontent lcid="1033" xmlns:o="urn:schemas-microsoft-com:office:office">
<o:application id="WD">
<o:featuredtemplates startdate="2011-03-01" enddate="2015-03-01">

<o:featuredtemplate title="Letter" source="C:\Program Files (x86)\Microsoft Office\Templates\Companyname\Letter.dotx" >
</o:featuredtemplate>

<o:featuredtemplate title="Budget" source="C:\Program Files (x86)\Microsoft Office\Templates\Companyname\Budget.dotx" >
</o:featuredtemplate>
</o:featuredtemplates>
</o:application>
</o:featuredcontent>
I read in another post (http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/fbc4bf23-c9fb-4a6c-a981-49f68127bf77/) where someone was having the same problem and advised deleting the ..Spotlight\Content\Companyname\WD1031 reg key but that
hasn't help. I still only see 1 template.
Any help would be appreciated.

Step.1
Close Word and delete the following registry key
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Spotlight\Content
Step.2
Replace your XML file with the following sample
<?xml version="1.0" encoding="utf-8"?>
<o:featuredcontent lcid="1033" xmlns:o="urn:schemas-microsoft-com:office:office">
     <o:application id="WD">
         <o:featuredtemplates startdate="2011-03-01" enddate="2015-03-01">
             
             <o:featuredtemplate title="Letter" source="C:\Program Files (x86)\Microsoft Office\Templates\Companyname\Letter.dotx" >
                <o:media mediatype="" filename="" source="" />
                <o:preview filename="" source="" />
             </o:featuredtemplate>
             
             <o:featuredtemplate title="Budget" source="C:\Program Files (x86)\Microsoft Office\Templates\Companyname\Budget.dotx" >
                <o:media mediatype="" filename="" source="" />
                <o:preview filename="" source="" />
             </o:featuredtemplate>
         </o:featuredtemplates>
     </o:application>
</o:featuredcontent>
Tips: Keep <o:media ---> and <o:preview ---> even you don't use them.
Step.3
Restart Word, check result
Max Meng
TechNet Community Support

Office 2010 deployment - Bypass/Skip if Office 2013 present

We have predominantly Office 2007 installed thought out environment and I now have a working Office 2010 app deployment package. Now I am finding that we have a few systems that already have Office 2013 and I'd like to bypass any system that already has
2013 installed. Currently my 2010 package is installing side by side with 2013 and has resulted in Office being corrupted. I have not been able to find a way to detect Office 2013 and bypass/skip installation. Please help. Thank you in advance.

Hi,
You could simply use a Collection query and exclude all devices from the Office 2013 collection that already has Office 2010 installed.. If you deploy it it devices and not users that is..
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Deploying custom dictionaries to Office 365 users

Hi All,
We are currently in the process of migrating some of our user accounts to Office 365 during which we have discovered that once these account are migrated they are no longer using the organisations custom dictionary we deploy via group policy to
all users. If we clear all of the values out of "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" and then add the dictionaries in as per the below article's instructions Word will use our custom dictionaries.
However we want to avoid clearing all of the values out of "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" because this will mean that any custom dictionaries our users have manually added will be lost.
(http://blogs.technet.com/b/office_resource_kit/archive/2011/12/16/deploying-a-custom-dictionary.aspx)
Below is the result of GPP registry items we have in place to set custom dictionaries.
However after Office 365 it appears users are logging into Office applications with their Organisational account and we're seeing the following registry changes and the custom dictionaries are
no longer applied:
If you add the registry items in the article to the above key once the users have migrated to office 365 it doesn't work.
Any advice about how we can get our custom dictionary deployed to all of these users without wiping out all of their custom dictionaries would be greatly appreciated.
Cheers,
Joe

Hi,
Since I don't have the exactly same environment, I suggest you try to manually transfer the user's dictionary, after the dictionary is added to Office 365 Application, check what changes have been made in the Registry settings, maybe this can let
us know how to modify the registry keys to accomplish the migration.
To transfer the custom dictionary, copy the custom dictionaries to your transfer location. If you've saved other custom dictionaries in different folders, copy them too.
On the new Office, open Word -> FILE -> Options -> Proofing -> When correcting spelling in Microsoft Office programs -> Custom Dictionaries -> Click "Add" and browse to the dictionary file, open it. After the dictionary is added
to the new Office install, check the registry settings under "HKCU\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Custom Dictionaries" to know what changes have been made to let it take effect.
This method doesn't bring you to the direct solution but may be a way to find it.
Regards,
Melon Chen
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

No Preview Displaying with Custom Templates in 2013

We have deployed custom PowerPoint and word templates using the instructions in Deploy custom templates in Office 2010.<o:p></o:p>
In 2010, they seem to be working perfectly fine. When you select File - New there is a <companyname> folder next to Featured folder and when you click on it you can see 3 thumbnail images
of the custom templates. When you click each thumbnail it presents the appropriate preview image that are specified in the XML file. <o:p></o:p>
In PowerPoint 2013, you can see the thumbnail image but the Preview is blank. I have attempted to use both .png and .jpg files as well as saving the template as .pptx and .potx. The .pptx seems
to work the best as the .potx seem to just give a spinning wheel in the preview window. In Word 2013 there is no preview comes up at all - it just creates the new file. You can still create a new file using the template. <o:p></o:p>
We are using the Group Policy to deploy the templates to all users. The Registry settings appear to be correct and I have tried some suggestions in the forum without any change. <o:p></o:p>
Is there a different way to deploy them to 2013 users.
Any ideas??
Diana

Hi,
Just tried this on my desktop, issue also repro’s on my Office 2013, but everything looks OK for Office 2010.
Since we did this with the instruction specified for Office 2010, there might be some updates on below code for 2013 version of Office in
XML configuration file which used to create thumbnail and preview files:
<o:preview filename="1big.gif" source=<path> />.
The bad news is we cannot find any descriptions/documentations on the internet about this for Office 2013 currently. We might still need to wait to see if Microsoft will publish any technical articles on this to guide
user on how to make it on Office 2013.

Using Office 2013 group policy template to define Trusted Locations and Template Locations doesn't work

User Configuration/Policies/Administrative Templates
- Using Office 2013 group policy template to define Trusted Locations and Template Locations doesn't work
Microsoft Word 2013/Word Options/Security/Trust Center/Trusted Locations
- Allow Trusted Locations on the network:
Enabled
- Trusted Location #1:
Enabled
Path: //server/sharedfoldername [Edit: Path:
\\server\sharedfoldername]
Date: June 10, 2013
Description: Trusted Location
Allow sub folders: Enabled
The policy appears to apply to the client correctly by adding the following registry key and values:
HKEY_CURRENT_USER\Software\Policies\Microsoft\office\15.0\word\security\trusted locations\location1
allowsubfolders: 1
date: June 10, 2013
Description: Trusted Location
Path: //server/sharedfoldername [Edit: Path:
\\server\sharedfoldername]
However, when you open Word Options/Trust Centre/Trust Centre Settings…/Trusted Locations
There are no trusted locations listed under ‘Policy Locations’
I have tried setting similar settings for setting the Shared Templates folder location and just like the trusted locations policy, the registry keys are created properly in HKEY_CURRENT_USER\Software\Policies however word doesn’t
seem to recognize these either.
This used to work flawlessly using the administrative templates for Word 2007 and 2010. Has anyone been able to get these policies to apply successfully, or know why office doesn’t recognize these settings from the Policies registry
Key?

This would have been an easy solution to the issue. Unfortunately it isn't the problem. This question was originally posted on another Microsoft site and
was transferred here and when it was transferred the path's changed from the original post:
\\server\sharedfodlername to //server/sharedfoldername. (I will edit the question to show up as it did in the original post) Not sure how that happened. This
is still an issue that I haven't been able to get working correctly.
As it turns out the 'New from Template' interface Word 2013 has developed is very bulky with large thumbnails and is not very customizable nor practical for an office
that has a large number of templates. Because I am unsatisfied with the display and performance of the 'New' template chooser I sought after a solution to change the way word creates a document from a template in another thread:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-word/how-can-you-change-the-display-of-templates-in/d49194b9-a6b4-4768-8502-7d7b50e9dd65 working through this issue with Jay we were able to develop
some VB script with handles a very large number of templates in a list view and it works much faster than the built-in Word interface. The above thread is how I've worked around trying to define a shared template location and I am quite happy with it.

Office 2013 - Templates contacting MS Server

Dear Community,
I've installed Office 2013 Std. on one of our Windows 7 (32 bit) without Office templates. But when I start Word or Excel, the system is always asking for a username & password. This message popups, because our proxy is blocking the connection to: office15client.microsoft.com
We won't allow the access to that and what I don't understand is: we installed without templates, but Office 2013 wants to connect to the internet. Has anyone an idea how to disable that?
Thanks for helping/discussing.

Hi,
How did you install Office 2013 without templates? Based on my test, only Access and Outlook have templates in the installation.
And try to uncheck File>options>trust center>trust options>privacy> "Allow office to connect to the internet" option in Excel 2013 and Word 2013 to check the issue.
If you have any feedback on our support, please click
here
Jaynet Zhang
TechNet Community Support

Office 2013 Document Templates

Morning All,
I have successfully installed the ADMX templates for Office 2013
Changed the workgroup path to the server where I stored all the letterheads etc
However by default in MS Word the workgroup path hasnt changed to what it should be I have to select it manually
The GPO should force it to the path I entered unless I am mistaken?

I did ineed, I tested it with a SG and although the workgroup templates are there. the path on each machine still is blank so I have to point it at the share on the server where the templates are stored.
if you check the registry directly, is this registry path correctly populated?
HKCU\software\policies\microsoft\office\15.0\common\general!sharedtemplates
If you set the setting by using the UI, it will set this key instead:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\General!sharedtemplates
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!)
On every single machine on the domain?
On every single machine on the domain?

Deploy Office 2013 - Uninstall Office 2010

Hello,
I am planing to deploy Office 2013 and created a MSP File (Setup /admin) for the silent Installation - everything works fine - except the uninstallation of Office 2010. In the OCT I´ve selected the Option to remove previous Versions of Office. I can
remeber that this works perfect in Office 2010 to remove Office 2007 too.
But in Office 2013 this doesn´t work anymore, the installed applications wizard (appwiz.cpl) Shows both Version of Office are installed. What is the best way to remove the old Version silently and install Office 2013? I would like to have all in one
"Application" deployed via SCCM 2012 SP1.

Have you looked at this document, or it's online equivalents:
http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
In the section "Setup command-line options for Office 2013", they say:
/uninstall [ProductID]
Runs Setup to remove the specified product from the user’s
computer. Look up the value of [ProductID] in the Setup.xml
file for the product that you want to modify.
Example
\\server\share\Office15\setup.exe /uninstall ProPlus
where:
Office15 is the root of the network installation point.
ProPlus is the
[ProductID] ([ProductID]
is equal to the ID attribute of the
Setup element listed in
\\server\share\Office15\ProPlus.WW\setup.xml), where
ProPlus.WW is the location of the Office Professional Plus 2013 installation files.
You can customize the
/uninstall option by using it with
/config and a modified Config.xml file. This is necessary if you want to run a
“silent”
uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for user interactions, even when files are being used.
To run a silent uninstall
Using a text editor, edit the following element attributes in the
\\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml file:
<Configuration Product="ProPlus">
<Display Level="none"
CompletionNotice="no" SuppressModal="yes"
AcceptEula="yes" /> </Configuration>
At the command line, use the following syntax:
\\server\share\Office15\setup.exe /uninstall ProPlus /config \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml
Note:
In Office 2013, just as in Office 2010 and Office 2007, you cannot use the Setup.exe command line to set Windows Installer properties, such as
PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked
and unsupported properties, see Setup properties in Office 2010.
The information also applies to Office 2013.
Office Customization Tool (OCT) in Office 2013
Config.xml file in Office 2013

Corporate templates and office startscreen

Hi
I know that there is a problem with getting the startscreen in for ex Word to show what you want when you have set the path for workgroup templates. I have a similar problem.
What I want is that when the user starts for ex Word, the startscreen shows our Corporate templates. I know how this can be done and it works, as long as you not set the path for workgrouptemplates or as in our case, it looks ok until you in SharePoint has
choosen "connect to office", then the personal disapears from startscreen. instead you see featured and custom and under custom you see the templates folder but also the sharepointsites etc. This looks quite messy. I know we could go around it by
just not showing the startscreen but you have the same problem when you choose new document, and it would look so nice if the startscreen showed what we want it to.
So I wonder
Is there any policy from microsoft telling us how to manage Corporate templates in Office 2013?
Is it possible to manipulate the startscreen with coding ( I know how to customize backstage print for example, but I can not do it with startscreen or new)
Is it possible to call backstage from vba?
Best regards/ P

This may help:
File New Variations in the Versions of Word
Charles Kenyon Madison, WI

Adding user created templates into Office 2007/2010 using Group Policy

I am trying to show some of our templates that we have created for work within Microsoft Office (work and excel) but I want them to show for everyone and not just 1 or 2 people. Being in a company that employ's 200+ people in multiple locations, the
task to manually go around to each and every machine to point to a different set of templates seems very time consuming. I am wondering if there is a gpo and/or registry edit that can be used. Anybody's assistance is greatly appreciated!
We have a mixture of Office 2007/2010. Server is a Win 2008 r2 standard.

Hi,
You can create and deploy custom templates using the steps below:
1. Create your templates.
2. Create thumbnail and preview files.
3. Create an XML configuration file that describes the custom template, thumbnail, and preview files.
4. Deploy a registry key that enables Office to read the XML configuration file.
For more information, please refer to the following article:
http://technet.microsoft.com/en-us/library/cc178976(v=office.14).aspx
In addition, a simple way to achieve the goal is setting the file location for "Workgroup templates" and save the custom templates to the shared location,
then users can select the templates via File > New > My Templates. To change the location, you can modify the
SharedTemplates key under [HKEY_CURRENT_USER\Software\Microsoft\Office\xx.0\Common\General].
Hope this helps.
Regards,
Steve Fan
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 Store not working in Office 2013 ProPlus

I have few policies set up for managing our network deployment of Office 2013 ProPlus. Pretty standard things like disabling the first time run movie, disabling the office start screen, and disabling OneDrive. I actually made most of these changes through
the registry as well.
Now, it seems as though the Office Store is disabled but I have no recollection of specifically disabling such a feature nor could I find a registry or GPO which does disable it. I even undid many of the registries I use on a test bench but still could not
get the Office Store functionality back. We've had Office 2013 rolled out on our network for almost a year, and it's taken this long for 1 person of 150 members of staff to notice that the Dictionaries feature is not working due to Office Store not working.
I feel a bit daft posting something seemingly so trivial on TechNet, but half an hour on Google didn't turn up anything relevant that I wasn't already aware of.
Many thanks in advance.

Hi,
Please check if you have disabled the option of "Don't allow any apps to start" and "Don't allow apps from the Office Store to start" in Office Trust Center.
Location: FILE->Options->Trust Center->Trusted App Catalogs
GPO settings for these options:
Block Apps for Office
Block the Office Store
Location: User Configuration->Administrative Templates->Microsoft Office 2013->Security Settings->Trust Center->Trusted Catalogs
Hope this helps.
Thanks,
Ethan Hua CHN
TechNet Community Support

Installing Office 2013 on several PCs in a small company

Rather than create individual Live IDs for each of the 7 PCs in a small company, in order to install Office 2013, can we install 7 copies of Office 2013 using a single Live ID? (each copy of Office 2013 is licenced individually, not bought through
VLSC).
Or, is there a better way to install several copies of Office 2013 in an organisation (that does not want to buy Volume Licencing, they just want to buy individual copies)?

Are you talking about the local install version Office 2013, or Office 365 (2013)?
Office 365 is "easier" if you are dealing with volume licenses. Office 365 "installs" very quickly, in a matter of minutes. So if you are talking about buying individual 365 business licensees, just document a short procedure telling users how to install
Office 365 (sorry, that may not work if they don't have admin rights on the PC).
If you bought Office 365 volume license, here is a procedure I pieced together:
How does a company install and control licenses - Business
Using Click to Run virtualization, the process of getting new users running has substantially changed. Because CTR installations are so fast, you no longer have to pre-install the software for users.
A business IT Admin controls use of corporate Office 365 licenses through the Office 365 Administration Center online.
Overview:
- In the Office 365 Administration Center the designated Office Administrator sets up the new USER ID
- Setup the associated email account(s)
- Setup Office licenses allowed to the userid
- the new User logs in to their new computer
- in Internet Explorer the user goes to the “Office 365 Portal” site to get their allowed Office 365 installation
- using the Click to Run installation process, Office 365 is installed and running on a new computer is a matter of minutes.
The following links will provide you with more detailed information of where to look and what to do. You may require some additional support from an “expert” .
Free MS training for Office 365 Administration Center / Portal
http://office365support.ca/does-microsoft-have-free-training-for-the-new-office-365/
Excellent resource to get you started administering your business Office 365 licenses.
The first video,
Exploring the Office 365 Administration Center (9:32), describes
how to create new userids, and to assign Office licenses to them. It also very quickly breezes by how to install Office.
The second vidow,
Office 365 Overview for IT Administrators (14:00), quickly walks you
through setting up new company and users.
On basic setup page, step 3 “Set up User Access” provides links to instructions on how to set up new users.
In Service Settings, Downloads, you can control what Office apps the user can download.
Creating Users for the NEW Office 365
http://office365support.ca/creating-cloud-users-for-the-new-office-365/
This page provides more detailed instructions for setting up the new userids and granting them Office 365 licenses
Configuring Desktops for the NEW Office 365
http://office365support.ca/configuring-desktops-for-the-new-office-365/
The following post will document how to setup a Windows 8 desktop for a cloud user for Office 365. I have already installed Windows 8 and created
the local account for my test user. I have logged into the Office 365 portal and had the user change his password. The password for Office 365 and the password for the desktop are the same.
Office 365 for enterprises: A tour for administrators
http://office.microsoft.com/en-us/videos/office-365-for-enterprises-a-tour-for-administrators-HA102654955.aspx
Office 365 for enterprises brings together the online services your business needs. To see how to set up and manage these services, watch these four short videos.
Where did My MSI go - Deployment Video
http://www.microsoft.com/resources/technet/en-us/office/media/video/video.html?cid=otc&from=mscomoffice&VideoID=670e3969-0509-4d3a-a8a6-ffbe526d3e6f&src=v5:endslate:related^play:related_0&from=shareembed-syndication
10 minute comparison of MSI and CTR
Touches on corporate provisioning in”User Based License Model Activation”. Users activate/deactivate, but IT still has control to deprovision the license (starting at about minute 8:15).
Then in this video / article :
http://blogs.technet.com/b/office_resource_kit/archive/2013/03/20/the-new-office-garage-series-identity-activation-data-access.aspx
They again say the companies can still allow userid activation while maintaining control of the licenses through Active Directory
<snip>
Jeremy: So we showed the installation experience for a domain-joined computer where single sign on is enabled and one that is not domain-joined, but installs via the Office 365 portal. In the direct from portal case when you kick off the
installation, you will see a file that looks something like this:
Setup.X86.en-us_O365ProPlusRetail_24*****-45a2-4eeb-b06f-b14****189c8_TX_PR_.exe
In a future episode we'll talk about all of the configurations needed to suppress completely sign-in, first run experiences and user prompts. IT admins have had to deal with these in past releases of Office, but now there are ways to
automatically sign users in to Office 365 installs picking up their domain credentials. I also showed the effects of deleting the user account from the Azure AD store and how it put Yoni's Office into Reduced Functionality Mode (RFM) -
even if Yoni installs Office on his personal devices using his organization's Office software assets, once Yoni leaves the org the IT department can deprovision his personal installs. That keeps software asset management cleaner and IT is in control.
Yoni: Don't forget we also had Mark Russinovich on the show and he explained the security model for online services with Azure AD - in your car. It sounds like they are taking the defense in depth approach to harden the service. And you
made him slum it in your car, Jeremy.
</snip>
Overview of ID, Authentication and Authorization in Office 2013
<snip http://blogs.technet.com/b/office_resource_kit/archive/2013/04/16/new-poster-and-content-roadmaps-about-office-identity-authentication-authorization-and-security.aspx
>
This page has links to 3 posters. The first poster “Identity and Authentication in the Cloud: Office 2013 and Office 365” describes at a high level how to control new user setup in a corporate / small business environment.
</snip>
<snip http://technet.microsoft.com/en-us/library/jj683102.aspx
>
This page also has a link to the same poster online (http://www.microsoft.com/en-us/download/details.aspx?id=38193 has PDF and Visio versions of the chart). As well, it goes into
more detail with information like the following:
… Because Office is a tool that is used by the same individual in two different roles, the new Office offers two identities with which users can log on to Office 2013:
A Microsoft account, which most people use for personal business
An organization ID that is assigned by Microsoft, which most people use when doing work for an organization, such as a business, charity, or school.
The credentials that are used to sign in are recognized as either personal or organizational. That sign-in identity becomes the user's “home realm” and determines which documents the user has access to on SharePoint, SkyDrive, or Office 365 Services for
a specific session. Each unique sign in identity is saved in a most-recently used list so that it is easy to switch between identities without leaving the Office experience.
a personal SkyDrive can be mounted to an organization identity so that personal documents can be accessed at work or school without ever switching identities. Also, when a user authenticates by using an identity, this authentication is valid for all Office
applications, not just the application he or she signed in to.
Two logon types are supported when users sign in to Office 2013, a Microsoft account or an organization ID that is assigned by Microsoft.
Microsoft account (the user’s individual account). This account, formerly known as Windows Live ID, is the credential that users use to authenticate with the Microsoft network and is frequently used for personal or non-business work, such
as volunteer work. To create a Microsoft account, a user provides a user name and password, certain demographic information, and “account proofs,” such as an alternative email address or phone number. For more information about the new Microsoft account, see
What is a Microsoft account?.
An organization ID that is assigned by Microsoft / Office 365 account ID that is assigned by Microsoft. This account is created for business use. An Office 365 account can be one of three types: a pure Office 365 ID, an Active Directory
ID, or an Active Directory Federation Services ID. These are described below:
Office 365 ID. This ID is created when an admin sets up an Office 365 domain and takes the form <user>@<org>.onmicrosoft.com, for example:
[email protected]
Organization ID that is assigned by Microsoft that is validated against a user's Active Directory ID. An organization ID that is assigned by Microsoft and validated against Active Directory as follows:
First, a person who has an [on-premise domain]\<user> account attempts to access organization resources.
Next, the resource requests authentication from the user.
Then, the user types in their organization user name and password.
Finally, that user name and password are validated against the organization AD database, the user is authenticated, and is given access to the requested resource.
An organization ID that is assigned by Microsoft that is validated against a user’s Active Directory Federation Services ID. An organization ID that is assigned by Microsoft and validated against Active Directory Federation Services (ADFS)
as follows:
First, one person who has an org.onmicrosoft.com attempts to access
partner organization resources.
Then, the resource requests authentication from the user.
Next, the user types in their organization user name and password.
Then, that user name and password are validated against the organization AD database.
Finally, that same user name and password are passed to the partner’s federated AD database, the user is authenticated, and is given access to the requested resource.
For on-premises resources, Office 2013 uses the domain\alias user name for authentication. For federated resources, Office 2013 uses the [email protected] user name for authentication.
</snip>
Office 365 Administration / Office 365 Administration Center / Office 365 Portal
http://technet.microsoft.com/en-us/library/jj819272.aspx
This page summarized methods of administering Office 365
User Account Management
http://technet.microsoft.com/en-us/library/jj819300.aspx
Sign-in for Small Business subscriptions
Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud services.
Sign-in options for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions
Office 365 for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions has two systems that can be used for user identities:
Organizational account (cloud identity) Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud
services. This is the default identity, and is recommended for small and midsize businesses in order to minimize deployment complexity. Passwords for organizational accounts use the Windows Azure Active Directory
password policy.
Federated account (federated identity) For all subscriptions other than Office 365 Small Business and Office 365 Small Business Premium, in organizations with on-premises Active Directory that use single sign-on
(SSO), users can sign into Office 365 services by using their Active Directory credentials. The corporate Active Directory stores and controls the password policy. For information about SSO, see
Single sign-on roadmap.
The type of identity affects the user experience and user account management options, as well as hardware and software requirements and other deployment considerations.
Custom domains and identity options
When you create a new user, the user’s sign-in name and email address are assigned to the default domain as set in the Office 365 admin center. By default, the Office 365 subscription uses the <company name>.onmicrosoft.com
domain that was created with the Office 365 account. You can add one or more custom domains to Office 365 rather than retaining the
onmicrosoft.com domain, and can assign users to sign in with any of the validated domains. Each user’s assigned domain is the email address that will appear on sent and received email messages.
You can host up to 600 registered Internet domains in Office 365, each represented by a different namespace.
For organizations using single sign-on, all users on a domain must use the same identity system: either cloud identity or federated identity. For example, you could have one group of users that only needs a cloud identity because they don’t access on-premises
systems, and another group of users who use Office 365 and on-premises systems. You would use add two domains to Office 365, such as
contractors.contoso.com and
staff.contoso.com, and only set up SSO for one of them. An entire domain can be converted from cloud identity to federated identity, or from federated identity to cloud identity.
For more information about domains in Office 365, see the
Domains service description.
Creating user accounts
Office 365 provides five ways to create user accounts, some of which are not available for Office 365 Small Business and Office 365 Small Business Premium: Add single User, Bulk upload using *.CSV files, Active Directory Synchronization, Azure Active Directory
Module for powershell, Exchange Simple Migration
Password management
The policies and procedures for password management depend on the identity system.
Cloud identity password management:
When using cloud identities, passwords are automatically generated when the account is created.
For cloud identity password strength requirements, see
Change your password.
To increase security, users must change their passwords when they first access Office 365 services. As a result, before users can access Office 365 services, they must sign into the Office 365 portal, where they are prompted to change their passwords.
Admins can set the password expiration policy. For more information for Enterprise and Midsize subscriptions, see
Set a user’s password expiration policy. For Small Business, see
Change how often passwords expire.
License management
A subscription to Office 365 is made up of a number of licenses to a set of services. An administrator assigns a license to each user for each service that user needs access to. For more information about managing licenses, see
Assign or remove a license in Office 365 Enterprise, or
Assign or remove a license in Office 365 Small Business.
Office 365 for Business FAQ
http://office.microsoft.com/en-us/business/microsoft-office-365-for-business-faq-FX103030232.aspx
Some general questions are answered
Deployment guide for Microsoft Office 2013
http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
Free Download, 147 pg
Table of Contents
Getting help
Volume activation of Office 2013
Plan volume activation of Office 2013
Volume activation methods in Office 2013
Deploy volume activation of Office 2013
Use tools to configure client computers in Office 2013
Customize installations of Office 2013
Customize Setup before installing Office 2013
Configure a silent installation of Office 2013
Create custom configurations of Office 2013
Office Customization Tool (OCT) in Office 2013
Config.xml file in Office 2013
Setup command-line options for Office 2013
Setup properties in Office 2013
Setup architecture overview for Office 2013
Customize the Accessibility Checker for Office 2013
Outlook 2013
Planning overview for Outlook 2013
Choose between Cached Exchange Mode and Online Mode for Outlook 2013
Plan a Cached Exchange Mode deployment in Outlook 2013
Plan feature customizations in Outlook 2013
Choose security and protection settings for Outlook 2013
Configure multiple Exchange accounts for Outlook 2013
Configure Cached Exchange Mode in Outlook 2013
Configure Outlook Anywhere in Outlook 2013
Configure junk e-mail settings in Outlook 2013
Roll out Office 2013
Install Office 2013 from the local installation source
Deploy Office 2013 from a network installation point
Deploy Office 2013 by using Group Policy computer startup scripts
Language in Office 2013
Plan for multi-language deployment of Office 2013
Customize language setup and settings for Office 2013
Add or remove language packs after deployment of Office 2013
Mixed language versions of Office 2013
Companion proofing languages for Office 2013
Language identifiers and OptionState Id values in Office 2013
Security in Office 2013
Security overview for Office 2013
Authentication in Office 2013
Plan for Information Rights Management in Office 2013
Group Policy for Office 2013
Planning for Group Policy in Office 2013

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]

Deploy custom templates in Office 2013

Similar Messages

Maybe you are looking for