I know it's possible to create and register an executable or .dll as an additional Windows Control Panel via the registry but would like to integrate with the Windows 10 Settings application, for instance as an additional entry in the 'Network and Internet' Settings pane. I've found a reference to OEM Partner Settings but am neither an OEM, nor a Partner, and just want to add Control-Panel like functionality in an obvious place. I can't find any more developer documentation on SO or MSDN that relates to this so wonder if it's possible or whether MS have locked the Settings application a little tighter than the old (and maybe to be deprecated?) Control Panel? What's best practice for Windows 10 system-wide settings applications/applets/panels?
Related
I am working on Win 10 upgrade activity. As you know we can select application for file extension. So, those file will open on that app. e.g. html files only open in Chrome when user double click on that.
We can create XML file (DefaultAppAssociations.xml) and place it in C:\windows\system32
Now, I got the request to make one application default but let user decide if they want any other app. Is there any way to handle such things because defaultappassociations.xml will hard code this. Every time machine restart and it will set the same.
This is only possible as part of the operating system deployment or rather for newly created user profiles.
The command (official documentation):
Dism.exe /online /Import-DefaultAppAssociations:<path to exported xml>
However as I said you cannot alter existing profiles that way. Altering existing profiles in any way that is not the force via gpo is afaik not possible anymore because Microsoft does not want to allow it. A pretty stupid decision but at least you can tell whoever made the request that it is by MS design.
Like on the image:
Can't find any info on msdn. Also found sample Outlook add-ins on github, but they don't have icons on email items. Any help is appreciated.
It definitely does not apply to all add-ins installed from the marketplace. I have Salesforce plugin from marketplace and it is not pinned.
The configuration of the area where add-ins are pinned (known as "SurfaceArea") is stored in your mailbox under 7ae974c5-1af7-4923-af3a-fb1fd14dcb7a\OutlookOptions\RawJSON as a JSON object. If you are in a controlled environment, you can add GUID of your add-in to "ReadSurfaceAddins" property. You can use ApplicationImpersonation to do this for other people's mailboxes in your organization.
There are some plugins that pin themselves on install (the two examples I know are both from Microsoft Corporation). I tried to grab the cached manifest of one of those addins, change its GUID (so it won't conflict with the existing app in the store) and sideload it both as a user and via centralized deployment -- no luck, the add-in doesn't pin automatically. So the whatever magic makes those addins pin, does not happen in the manifest, but rather in some app store settings that aren't available to third party developers like us. UPD: I stand corrected, this feature is available to third parties as well - I've seen a third party add-in (Hubspot) that pins itself - again, this is an app store addin, not sideloaded.
You can go to Settings -> View all Outlook Settings -> Customize Actions -> Toolbar to configure the add-ins that appear on the Message compose surface. Additional documentation is here: https://support.office.com/en-us/article/customize-actions-on-your-messages-in-outlook-com-c8110dcb-892e-4903-94b3-f6eb41ada2a3
I am working on a ASP.NET MVC project in Visual Studio.
Since today I see am seeing every now and then
a dialog window "Connect to SQL Server" that uses {0} as user name:
I always click Cancel as the user name is just a place holder. It is read - as the rest of the database configuration - from Web.config.
The documentation just states:
This dialog box appears when specific access permission is required
for the current database process.
I believe I do not need this access. How can I prevent Visual Studio from showing this dialog?
PS: I do not want to remove the configuration from Web.config as it is needed by my project.
After a little debugging, it turned out that it was the awesome Meene VS Tools 2017 extension which caused this problem. Specifically, the Enable tasks provider option. Just disabling it helped to get rid of the nasty dialog. Maybe one could also add the Web.config to the Excluded file name patterns to fix the problem. Since I do not use the tasks, I did not try though.
I am facing problems with interface customizations in the latest OBIEE release.
Is it possible to "hide" the Mobile, VA and BiPublisher options - marked red in the appendix.
(Privileges in Administration and roles in EM are configured - users can not access Mobile, BiPub however the buttons are still visible - OBI 11 did not display them afterwards...)
I am looking for a "clean" design.
Any help is much appreciated
Unfortunately up to and including 12.2.1.2 (the current version) the "Visual Analyzer" menu point will keep being rendered even if they permission has been removed from the application role(s) of the user.
Mobile and BIP disappear completely on the other hand.
So the question to be asked is: how did you configure your application roles and policies? Did you reuse vanilla ones? Then it may just be the case that some rights still persist due to ootb inheritance between roles and hence some rights stay even though you think you removed them.
I'm writing a service application for SharePoint 2010. I've implemented the Microsoft.SharePoint.Administration.IServiceAdministration in my service class. There's method called GetCreateApplicationOptions in this interface which returns the SPCreateApplicationOptions enumeration.
The enumeration has three distinct values, e.g. "None". The description of "None" reads: This service application is not created in single-click (eval) mode or shown/created in the farm configuration wizard.
I'm good with the farm creation wizard, but what is "single-click (eval) mode"? There seems to be no info around...
Yes, there is not a lot of help available. But based on description, it sounds like: Single-Click (eval) mode is applicable when you do NOT choose to install/configure SharePoint Farm yourself. For example, when you want to install everything on same machine on windows 7. And when you are not in single-click mode, SharePoint presents you a config wizard when you run the central admin first time, soon after installation.