Disable Office 2016 – First things first Prompt
When you first launch Office Click to Run or Office 2016, you will get a First things first dialog box come up like below. Users will always click accept, what other choice do they have?
You can disable this by configuring the below Registry key:
Disable Office 2016 Default File Types Dialog
Another thing I disable on my desktop builds is the Office 2016 Default File Types prompt as shown below. Normal users will not understand what it means. All they will do is ask questions.
Use the registry key below to stop it appearing :
When you are performing a PXE boot, most of the time you need to press F12 to trigger the PXE boot action. Then after connection is initiated with the PXE server, the boot rom image asks for the F12 key to be pressed again. If the key is not pressed, the machine will continue to boot normally into the installed OS (if available). This can be confusing for some Admins because they except the client to boot through to the Boot image, or maybe they want to create a fully automated OSD Deployment. Continue reading Disable F12 confirmation at PXE boot into WinPE
You might have tried following this guide in order to deploy Office Pro Plus (Click-to-Run) via Intune, resulting in the MSI being deployed but the Office bits not being streamed. I’ve found many people in my inbox struggling and eager to find a solution. I’m glad that Pouyan Khabazi and Paul Huijbregts (both from Wortell) have spent time investigating and came with a workaround/fix. This guide is 100% their work and all credits go out to them:
Please read more about the solution on Microsoft Blog:
Windows caches your user names and passwords entered for network shares, drives etc. That’s fine until there’s an incorrect password or username in the cache, and you want to remove it.
The utility to delete cached credentials is hard to find. It stores both certificate data and also user passwords.
Open a command prompt, or enter the following in the run command:
rundll32.exe keymgr.dll, KRShowKeyMgr
In my lab environment I’m doing quite a lot of ConfigMgr testing. Recently, I was doing some testing on System Center Configuration Manager and Endpoint Protection (current branch – version 1511) and I broke the ConfigMgr primary site server and decided to re install the primary site. Continue reading Configuration Manager requires a dedicated SQL Server instance