Office 2013 macro warnings GPO

How do we enable all macros to run that are stored from our LAN?
At the moment we receive warning below the ribbon in excel and word advising that some content maybe dangerous and to enable macros. Also we receive a Security warning after enabling macros; Do you want to make this file a trusted documents? All files stored
on local drives and network shares should automatically be trusted so users are not faced with these prompts.
Please advise how i can suppress this using GPO?
regards

using office GPO templates, you need to change settings in Word and Excel - its under Word, Word Options, Security, Trust Center, Trusted locations. Excel path is similar. You can set trusted locations using gpo too.
The policy keys are at:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\word\security\trusted locations
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\excel\security\trusted locations
Dword: allownetworklocations
Vlaue: 1 (allow)
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Similar Messages

Office 2013 Administrative Templates & GPO

Hey, everyone!
I’m sure someone here will know what I’m doing wrong, so hopefully it’s something simple.
This is my first attempt to utilize Office 2013 Administrative Templates in a GPO. I downloaded the templates from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=35554)
and extracted them.
I then created a new GPO so that the policy folder was created in logonserver\sysvol\%userdnsdomain%\policies\Adm.
In that folder, I copy the appropriate .admx files and the en-us folder.
Then, when I go to edit that GPO, I get an error:
The following error has occurred in \\Hudsonchapel.org\SysVol\Hudsonchapel.org\Policies\<GUID>\Adm\proj15.admx on line 1: Error
51 Unexpected keyword.
Found <?xml
Expected: CLASS, CATEGORY,
[strings]
The file can not be loaded.
This occurs for any .admx file I’ve tried.
I’m not sure what else to try. I’ve followed what I know to do.
Could someone help me figure out what I’m doing wrong?
Thanks!
-Eric

Hi Eric,
>>I then created a new GPO so that the policy folder was created in logonserver\sysvol\%userdnsdomain%\policies\Adm.
In that folder
How is it going? Did we follow the article provided by Zanderol24 to create the Central Store for admx files? The location of central store is:
%systemroot%\sysvol\domain\policies\PolicyDefinitions
Regarding ADMX files, the following article can be referred to for more information.
Managing Group Policy ADMX Files Step-by-Step Guide
http://msdn.microsoft.com/en-us/library/bb530196.aspx
Best regards,
Frank Shen

Office 2013 GPO Silent install doesn't run consistently

client is all Dell Win 7. Servers are 2012. Project is to install Office 2013 silently with GPO at computer start. Everything is configured correctly and it works on some computers. I set it install in a larger group by linking the GPO to that group of computers. Told everyone to reboot and waited. Nothing. It didn't install. I know it works because I haven't changed it and I have seenit work multiple times. Try another reboot. Nothing. Then one of them works. Then another. Then another. Not all at once and not always at reboot. Some of them just install in the middle of the day. Is this a "load balancing" feature where all of them are not installed at once so the server isn't overwhelmed? If not, why does it work sometimes and then at random times. The actual install doesn't take very long. Maybe my server doesn't have the horsepower...
This topic first appeared in the Spiceworks Community

I've not tried the Dashboard connection yet.
I will try to connect and setup permissions using TDADM.
This is my thoughts etc. so far;
problem starts when running dpconfig.exe - therefore I can skip re-running (and 'repairing') the install using the MSI
dpconfig doesn't appear to have any command line options? (ran "dpconfig /?" from a command line and still just launched the wizard)
so far, even if permission are or get set correctly, processor hasn't been linked to the share yet - only dpconfig can do that?
had installed the Processor on Server 2012 in Core UI. Thought dpconfig might be trying to launch Explorer, which isn't available in Core, so went up to "Server with GUI" (bypassing "minimal"). However, this didn't change anything. Left at Server with GUI
for now (although would prefer to run as Core if supported - nothing says it isn't?)
by default, our server config blocks all Firewall ports incoming (the out of the box config) only opening up ports as required. I'll try turning the Processor Firewall off.
Seems like not a lot of people do this (install the 2013 Telemetry), as very little online apart from Microsoft pages. Trying to dig through the Powershell script posted (by you Jill?) here;
http://blogs.technet.com/b/office_resource_kit/archive/2012/09/25/quickly-set-up-office-telemetry-dashboard-on-a-workgroup-or-domain-joined-computer.aspx . However, looks like even in this one that for domain joined machines, dpconfig is launched interactively,
so still no cmd line options!

Deploying MS Office 2013 with GPO

OK i would like to deploy office 2013 via GPO, i finally have been able to get the script to work however there is one more detail i need to get figured out.... How can i incorporate into the script so that it will only run once... my script is below
and does the following, it uninstalls office 2010 whether it be 32bit or 64bit then silently installs office 2013 as a startup GPO... how would the script look if i'd like to add so that it looks for a specific txt file that if its there it does nothing and
if it's not it runs install script and perhaps at end of install script maybe it creates that txt file... I need help on the best way to just "RUNONCE"
here is my script:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
"C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
setlocal
REM ********************************************************************
REM Environment customization begins here. Modify variables below.
REM ********************************************************************
REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
set ProductName=Office15.PROPLUS
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\****\Office13
REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\****\Office13\ProPlus.WW\config.xml
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\****\Office13\LogFiles
REM ********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM ********************************************************************
IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
if NOT %errorlevel%==1 (goto End)
REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)
REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
echo %date% %time% %ComputerName% "Has Run the install Process" >> %LogLocation%\HasRunInstall.txt
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% %computername% Setup ended with error code %errorlevel%. >> %LogLocation%\FinishedInstall.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal

The problem with Office 2010 and later is that it is not designed to be installed remotely or by a script. You need to create an install spec and set up some prerequisites fist. If you ten follow the instructions for using a GPO to deploy Office
you will not need to use a "RunOnce" key or anything else.
Note that eh RunOnce key take a command or batch and command and is deleted as soon as it is executed. The problem you have to solve is how to set the RunOnce key to begin with.
You really must use the information in the links posted for Office deployment. You cannot do an end run around this with any success. If you search for forum posts on this you will see that many have been exactly where you are. Don't wast
your time. Follow the instructions as posted in the Office forum and on the TechNet link. YOu will find it is actually quite easy and very flexible once you understand the steps.
\_(ツ)_/

Will macros in excel work properly if I switch Office 2013 32 bit to Office 2013 64 bit?

hi,
Will macros in excel created with Office 2013 32 bit work properly if i switch to Office Execl 2013 64 bit?
Thanks

Hi,
As far as I know, most of the macros might work well between 32bit and 64bit Excel. But there are some limitations for Excel 64bit:
Solutions using ActiveX controls library, ComCtl controls won’t work.
Third-party ActiveX controls and add-ins won’t work.
Visual Basic for Applications (VBA) that contain Declare statements won’t work in the 64-bit version of Office without being updated.
Compiled Access databases, like .MDE and .ACCDE files, won’t work unless they’re specifically written for the 64-bit version of Office.
More reference:
https://msdn.microsoft.com/en-us/library/ff700513(v=office.11).aspx
https://msdn.microsoft.com/en-us/library/ee691831(v=office.11).aspx
https://support.office.com/en-sg/article/Choose-the-32-bit-or-64-bit-version-of-Office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261?ui=en-US&rs=en-SG&ad=SG
If you have any further question about macros, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
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.
George Zhao
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]

Office 2013 over Windows Server 2012 RDP World Add-On Macro/Template Error

I have a new Windows Server 2012 Remote Desktop environment for about ten users (not R2) with the latest Office 2013 Pro installed.
The users all have an add-on word template in Word for Office 2013. That add-on was installed as administrator and ONLY works as administrator.
When any other user (even if they are local administrators, domain admins, etc.) opens Word, they are immediately prompted with the following message:
"Could not load some objects because they are not available on this machine."
If a user "runs as administrator" it runs fine. Obviously, I don't want that. I have been searching and searching and thought maybe there was a group policy or Office setting someone may know that I just can't find.
Any help would be awesome! Thank you.

Hi,
Once you login with the user account which is not getting access, try the below steps and check if it helps fix the issue:
Click on start->control panel->programs and features->right click on the Office 2013 program->click on change->add or remove features-> click on the drop down arrow which is before the Microsoft Office->click on Run all from my computer->Continue.
Once completed restart the computer and then open to check if the issue occurs.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community 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 Support, contact [email protected]

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 SharePoint 2013 server properties - The required term set is not available.

Hi,
After creating new document from ribbon with the new document function on any template the managed metadata based server properties cannot be selected and properties boxes are grayed out. Mouse over displays "The Required term set is not available".
Works fine when using it form resource (SharePoint) domain both with user domain and resource domain accounts.
There is a two-way trust btw domains.
SPNs are done for AppPools.
AppPool accounts have delegations and are set to impersonate with GPO.
SharePoint Web Application is on kerberos authentication.
There is no difference when sites are using user or resource domain AppPool accounts.
The WFE and SQL Server have computer delegations.
Server env: Windows Server 2008 R2 with all updates, SQL Server 2008 R2 with all updates, on-prem SharePoint Server 2013 with no CU.
User env: Windows 7 ENT, IE10 and Office 2013 with all updates.
There is no internet connection and internet connection is not possible. The internet connection is cheated with two DNS A record setting for
www.msftncsi.com and dns.msftncsi.com. Also registry changes "ActiveDnsProbeContent" ip- address for Win7 is done via GPO to private IP. This is done because otherwise check-in/check-out does not work.
Last things on IIS log are:
2014-01-24 10:38:36 192.168.n.n PROPFIND /TestDoc - 5445 0#.w|userdomain\test3-user 192.168.51.51 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 207 0 0 639
2014-01-24 10:38:37 192.168.n.m OPTIONS / - 5445 0#.w|userdomain\test3-user 192.168.51.51 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 842
2014-01-24 10:38:54 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
2014-01-24 10:39:25 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 0
2014-01-24 10:39:56 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
2014-01-24 10:40:27 ::1 POST /_vti_bin/sharedaccess.asmx - 5445 - ::1 Microsoft+Office+Word+2013+(15.0.4551)+Windows+NT+6.1 200 0 0 15
What I missed.
Br,
-timo-

Same problem here!. Giving the computer network access allows the control to be populated. Then I disabled and restarted and it seems to be ok....

How to add MS Office add-in from inside a Thinapp 5 virtual application to a MS Office 2013 suite that is installed on a base image

Hi,
We have the following solution:
VMware Horizon View 5.3.1
Non-persistent Linked-clone pool with delete VM after logoff
Windows 8.1 Update 1 Enterprise 64 bit
MS Office 2013 32-bit installed on image
Thinapps registered for each user from logonscript with thinreg.exe command. Thinapps is located on a network share
Native Windows roaming profiles with appdata/roaming, appdata/local without appdata/locallow(persona management does not support Windows 8.1 in View 5.3.1)
This is our issue:
We have a 3rd party application with a couple Thinapp entrypoints(exe files) and in the Thinapp package process we also installed Office addins. We tested that the Add-ins was opened inside Outlook, Word and Powerpoint before post installation scan.
The problem is that the add-ins is not added to Office 2013 before or after the Thinapp is started on a test client.
I have tried several changes in the package.ini and virtual filesystem attributes(no registry changes yet):
Package.ini:
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;
ChildProcessEnvironmentDefault=External
ChildProcessEnvironmentExceptions=excel.exe;outlook.exe;powerpnt.exe;winword.exe
ChildProcessEnvironmentDefault=Virtual
VirtualizeExternalOutOfProcessCOM=0
DirectoryIsolationMode=Merged
RegistryIsolationMode=Merged
I have also read that you could make entrypoints to the locally installed Office 2013, but I get errors on the build process. ref. link: http://edwinfriesen.nl/content/?p=105#comments
The best thing would be if the add-ins were added in the logon process together with thinreg.exe, but if that is not supported, the add-ins must be added to Office either in a custom Office shortcut/entry point or after starting the Thinapp virtual application.
Remember that the application needs to registered every times the user logon, because we use a non-persistent View pool.
I would really appreciate if somebody could tell me how to add Office add-ins from inside a Thinapp virtual application/package to a locally installed MS Office 2013 suite on a Windows "base" image?
We do not want to add the whole Office suite to the Thinapp virtual package and not add the add-ins trough GPO,SCCM etc.

What about the COM object parameters in package.ini ?
We can live with scripting in logon or changed logon scripts etc.
And you don't no need to lock in the project files.
From package.ini documentation:
ObjectTypes Parameter
The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in
the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications.
An object type is registered to only one native or virtual application at a time. If you install Office 2003 on the
native machine and want to use a virtual Office 2007 package, you must determine whether to have the virtual
or native application handle the object types.
If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native Office
2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file before
building and registering the package.
You cannot add random entries to the ObjectTypes parameter.
You can only remove entries that were generated by the capture process.
Example: Starting a Virtual Application When a COM Object is Created
If a script or a native application creates an Excel.Application COM object or other COM objects listed in the
ObjectTypes parameter, ThinApp starts the virtual package.
[Microsoft Office Excel 2007.exe]
ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
Excel.Macrosheet;Excel.Sheet; Excel.Workspace

Office 2013 update KB 2726958 Problem

Our pcs applied the latest round of Windows Updates yesterday and the Office Update KB2726958 caused the macros in Excel 2013 spreadsheets to stop working. Uninstalling just this update returned full functionality to Excel.
These are all Windows 7 64 bit machines connected to an AD domain with 32-bit Office 2013 Professional or Pro Plus.
Any machine that had applied the latest updates released on Tuesday suffered from this problem. Opening a .xlsm spreadsheet looked fine but users were unable to click on Macro buttons to e.g. load a userform.
I have spent 28 minutes on the phone trying to speak to somebody, anybody, in Support but no-one was interested so I am trying this forum instead.

Performing the steps in the link (http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/13/forms-controls-stop-working-after-december-2014-updates-.aspx) does
restore the ability to run button driven macros as well as add controls and buttons.
However, a task as simple as:
Creating a new workbook.
Saving as macro enabled workbook.
Adding ActiveX form toggle button.
Adding: msgbox "Toggle this!" to the change even of the newly added toggle button.
Saving the workbook.
Everything works great on this machine.
When the workbook is opened on another machine (I've tried several that can open and use other macro enabled workbooks with buttons and such.), the button appears, but the button and macro are not functional. Deleting the sheet
in the workbook causes Excel to crash.
Once I uninstalled KB2726958 on the machine where the workbook is created, I am able to perform the above with no issues. Of course, this is a temporary work around that will be clobbered by policy driven Windows /Office Updates the next time I restart.
HALP!
MrMikeV

Office 2013 Home and Business OEM First Run screen

Hi There
We are starting to roll out office 2013 oem Home and Business our users are reporting that the first run screen get coming up every time there open an office application.
In Group Policy I've disable the First Run Movie and Office First run on application boot however the users are still getting to first run screen this is every annoying.
Any help with would be great?
Cheers,
Brett

The policy setting should work: it correctly adds bootedrtm=1 value to HKCU\Software\Policies\Microsoft\office\15.0\firstrun. But for some reason Office apps ignore it. I tried disabling the entire policy, then go through the welcome screen. After finishing
with it, office created the same value, but in another place (HKCU\Software\Microsoft\Office\15.0\FirstRun), and the screen never appeared anymore.
So to make the setting work, you have to manually create registry setting (via GPO preference) with the following data:.
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\FirstRun]
"BootedRTM"=dword:00000001
P.S. this was pretty easy, but did anyone look at disabling the EULA prompt? The acceptance is marked by creating a registry key for each user, but the path contains computer name :)) Therefore if all users of the PC have accepted the agreement, and you
renamed the computer, the popup comes back again. And of course group policy is impossible with such path.

APP-V Office 2013 configuration.xml

Hi all,
I'm trying to roll out Office 2013 with APP-V, whenever I change the config.xml to accept the EULA it still pops up with the EULA.
The documentation for APP-V differs from the normal ODT config.xml, what's the difference and am I missing out on something?
See the document from Microsoft on the configuration.xml within app-v:
https://technet.microsoft.com/en-us/library/jj219426.aspx
The XML file states to accept the EULA. The output in there is a configuration.xml like this:
<Configuration>
<Add SourcePath="C:\office2013" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="nl-nl" />
<Language ID="en-us" />
</Product>
<Product ID="ProjectProRetail">
<Language ID="nl-nl" />
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail" >
<Language ID="nl-nl" />
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="SharedComputerLicensing" Value="1" />
</Configuration>
Kind regards,
Jacob van Rooijen

You can use two registry keys to disable it, push them using a GPO:
HKCU\Software\Policies\Microsoft\Office\15.0\Registration
Reg_DWORD = "AcceptAllEulas"= 1
HKCU\software\policies\microsoft\office\15.0\firstrun
Reg_DWORD = "bootedrtm" = 1
See this post

Office 2013 UI questions

I am about to roll out a mixture of Office 2013 and Office 365 Pro Plus, finalizing UI and GPO settings, have a couple things I am wrestling with.
1. Is there a way via GPO or registry edits to set the default "Office Background" to "No Background"? I am not talking about the office theme, but the office background. I found where you can DISABLE backgrounds via GPO. But that is
not what I am trying to do here, I want to set the background to a certain default background (no background) as the default, but not completely remove the users ability to set a background themselves. Setting disable in the GPO sets it so the user cannot
set the background at all.
2. MS Word, is there a way to set Word that when you open Word, it goes right into a new blank document rather than the "recent" page. This is confusing to users and I want to set default to the old way which is just open a blank document
3. The "Open" dialog box in all Office Suite components. Is there a way to remove our Office 365 Sharepoint link and OneDrive from the open dialog? Or at least re-order it? Also I dont know who came up with this, but "computer" is a bad
way to describe network files. It seems unnecessary for a user to have to click open, then computer, then browse to just get to the network drives... this seems silly. Hint Hint Microsoft, not everyone is using Sharepoint, not everyone likes sharepoint, some
of us will NEVER use Sharepoint, stop trying to force us to use it...
4. Completely remove sharepoint integration? Can you do this? I want no reference to Sharepoint in Office

Re1: I haven't found a way to change Office Background via GPO, but we try to enable the Disable Office Backgrounds, it will disable the Office Background option and set it to No Background.
Group Policy location: User Configuration\Administrative Templates\Microsoft Office 2013 (Machine)\Miscellaneous
Re2: The function is want to disable is called Office Start Screen. We can disable it via OCT or GPO. To do it via GPO, set the "Disable the Office
Start screen for all Office applications" group policy to Enabled.
Group Policy location: User Configuration\Administrative Templates\Microsoft Office 2013\Miscellaneous
For more information, please refer:
http://blogs.technet.com/b/odsupport/archive/2012/11/19/how-to-manage-the-start-screen-for-all-microsoft-office-2013-applications.aspx
Re3: I haven't found a way to change this, it seems a hard-coded feature.
Re4: You can refer to this:
http://inoblog.com/sharepoint-client-integration-issues/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best Regards,
Steve Fan
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 group policies - not working

I'm using Office 2013 Pro Plus SP1 (volume license) on a Windows 7 Pro machine [both are 32 bit]. While I have Server 2003, it's configured to work with Windows 7 and Office 2013 Group Policy templates. I use RSAT on a Win 7 computer to
create/manage the Group Policies.
Since we're not using Office 365, I'm trying to block some of those features, as well as disabling the Office Start screens.
Thinking that SP1 might be the problem, I downloaded the group policy templates for SP1 and copied them to the server.
If I create a policy (Office_2013_settings), with a few settings, like "Block singing into Office". In Group Policy, I disabled the Computer Configuration, leaving the User Configuration enabled. If I force group policy on the target
computer and look at RSOP, I see the computer configuration settings disabled, but nothing for the user configuration, although it's enabled in the policy.
If I put a junk policy entry on the computer configuration and enable both policies on the backend, force group policy on the computer, and look at RSOP, under computer configuration, I see the Office_2013_settings policy, but the policy still doesn't appear
in the user configuration. If I scroll to the bottom of the file, where I can see other Administrative templates and their settings, my Office_2013_settings aren't visible.

I have created a group policy with a few settings, and applied to my own computer. It seems to be very nice to me. Please first check the apply status on the client site based on the GPSVC.log
Thinking the issue might be on the way how you create/manage the Group Policies on Windows Server side. Please check the model of how you deploy your group policy, on a domain or OU level? Loopback Merge or Replace? This might affect whether the user
would receive all settings from GPO applied to User or Computer. This article might be useful to you:
http://blogs.technet.com/b/askds/archive/2013/02/08/circle-back-to-loopback.aspx
This might be an issue on Windows server side, you may need to post your question to below forum to get more suggestions:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver

Patch management for Office 2013 on MDT

Hello,
on current MDT 2012, Office 2013 is added as an app. MSP was created for customization and placed in Update folder (did it a while ago)
I am preparing new MDT 2013. Deployed OS will be patched with latest updates. So Windows update will not take initially any time for applying patches after deployment from WSUS.
I would like to know best practices for Updating Office 2013 on Deployment Share.
Please provide a link or instructions: where to get latest O2013 Update Packages (at least security and critical) and how to place them properly in Update folder. Can it coexist with Customization.msp?
1. What is the right thing to manage this? No SCCM in place.
2. Does somebody includes Office 2013 in the image and then use GPO for customization?
Is it a valid scenario? I see at least 2 advantages: no additional time after deployment and full patches for the moment of image creation. Than it could be updated in the moment of image update.
Does it make sense? What are disadvantages of this approach?
thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Thanks to all!
Ty, I added a lot to my knowledgebase during bombing :) you with the questions since last week :) ... Thanks for the answers...
I purchased Johan's Fundamentals V4 (found it more applicable to my current needs).
A bit in pressure this week need to push 2 models deployment quickly and correctly as possible.
So don't have time to Deep Dive.
What I achieved Driver Group approach works find for tons of drivers. Tried just on model now...
Have to solve sudden issue with WinPE that was working fine and suddenly stopped working.
For O2013...
Just to make things fast I installed O2013 in reference image.
If I understand correctly I cannot use MSP file after the installation is made. I suppose to create it and add to Updates folder of the O2013 source.
So now my option is to work with GPO. I have a configured one for O2013 APPV deployment.
It works great.
Don't remember if I can manage by GPO applications appearance in the Office. (Example want to exclude Publisher and Access from being used on client PC).
Can somebody point where is the option in GPO for selecting individual apps within the Office.
In my MDT2012 I use O2013 deployment as App and use MSP.
For Appv Office I use apps selection from APPV manager. So not sure if it is doable from Office GPO.
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Office 2013 macro warnings GPO

Similar Messages

Maybe you are looking for