I added the following registry information (don't add what's in parentheses, those are just my notes): under DefaultUser\Software\Microsoft\Office (new key)\15.0(new key)\FirstRun (new key) add a new DWORD (32-bit) value titled BootedRTM and give it a value of 1.As an administrator: load the Default User's HKCU registry (C:\users\Default\NTUSER.DAT) into HKEY_USERS (I named the key DefaultUser, but it doesn't really matter what you call it).It turns out that only one key was needed to fix the issue, so here is what I had to do. I examined the registry for a difference between a working user and the mandatory profile user and sure enough, the entire section of Office registry keys was missing from the mandatory profile user. It figures - I've been working on this for days, and shortly after posting I figured out the answer. This is done before any user interface is shown so can successfully be used to set the options that hide the first run dialogs. When a user runs an Office application it checks to see if it has previously migrated these settings before and if not it creates the relevant keys in HKEY_CURRENT_USER. The 15.0 part refers to Office 2013 / Office 365. Then under this key make another key called Create and under this create the registry settings that you want to set in HKEY_CURRENT_USER. You can even have multiple different names for different groups of settings. The M圜ustomSettings part of the key can be anything you like. In summary, you create keys under HKLM in the following locations (depends on the OS and version of Office):ģ2bit 32bit HKLM\SOFTWARE\Microsoft\Office\15.0\User Settings\M圜ustomSettingsĦ4bit 32bit HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\User Settings\M圜ustomSettingsĦ4bit 64bit HKLM\SOFTWARE\Microsoft\Office\15.0\User Settings\M圜ustomSettings There is no worthwhile documentation of this process except on this Deployment Guys blog post. To get this to work we can use a little-known feature of Office which allows you to specify some HKEY_LOCAL_MACHINE keys that are automatically migrated into HKEY_CURRENT_USER when an Office application is first run for that user. Its fully supported in the registry and works at run-time.Ĭredit Jonathan Bennett, Automating Office 365 Click-to-Run First Use Without Group Policy. I found a blog posting describing creating the FirstRun>BootedRTM reg entries on the fly for new users. installing and configuring the Office Administrative Templates for local GPO and setting the first run wizard to disabled under Local Computer Policy and also under Local Computer/Non-administrators Policy( )Īt this point the First Run wizard still appears each time the program is started for the mandatory user.running the Office program as an administrator (while logged in to a non-mandatory administrative account - the First Run wizard does not appear each time for other users, though).setting permissions on the Office registry key to be editable by regular users (This allowed me to accept the EULA, but still shows the first run wizard).running through the wizard to completion.The "Welcome to your new Office" wizard appears every single time an Office program is launched for the mandatory/default profile.
My issue is that I have recently installed Microsoft Office 2013 (subscription version) and I can't seem to turn off the "First Run wizard". This computer has a mandatory user profile and uses Local GPO to configure the profile on each login.
#How to turn off microsoft office 2007 activation wizard windows 7#
I have a Windows 7 Professional computer in a workgroup.
0 kommentar(er)
