mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-23 06:13:41 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-7489849
This commit is contained in:
@ -84,9 +84,11 @@ IE opens the app’s website.
|
|||||||
**Security Note:**<br>If you don’t fully trust a site, you shouldn’t allow it to launch an outdated app. However, although we don’t recommend it, you can let the webpage launch the app by tapping or clicking **Allow**. This option opens the app without updating or fixing the problem. The next time you visit a webpage running the same outdated app, you’ll get the notification again.
|
**Security Note:**<br>If you don’t fully trust a site, you shouldn’t allow it to launch an outdated app. However, although we don’t recommend it, you can let the webpage launch the app by tapping or clicking **Allow**. This option opens the app without updating or fixing the problem. The next time you visit a webpage running the same outdated app, you’ll get the notification again.
|
||||||
|
|
||||||
## How does IE decide which ActiveX controls to block?
|
## How does IE decide which ActiveX controls to block?
|
||||||
IE uses Microsoft’s versionlist.xml file to determine whether an ActiveX control should be stopped from loading. This file is updated with newly-discovered out-of-date ActiveX controls, which IE automatically downloads to your local copy of the file.
|
IE uses Microsoft’s versionlist.xml or versionlistWin7.xml file to determine whether an ActiveX control should be stopped from loading. These files are updated with newly-discovered out-of-date ActiveX controls, which IE automatically downloads to your local copy of the file.
|
||||||
|
|
||||||
You can see your copy of the versionlist.xml file here `%LOCALAPPDATA%\Microsoft\Internet Explorer\VersionManager\versionlist.xml`, or you can view Microsoft’s version at [Internet Explorer version list](http://go.microsoft.com/fwlink/p/?LinkId=403864).
|
You can see your copy of the file here `%LOCALAPPDATA%\Microsoft\Internet Explorer\VersionManager\versionlist.xml` or you can view Microsoft’s version, based on your operating system and version of IE, here:
|
||||||
|
- [Internet Explorer 11 on Windows 7 SP1 or Windows Server 2008 R2](http://go.microsoft.com/fwlink/p/?LinkId=403864)
|
||||||
|
- [All other configurations](https://go.microsoft.com/fwlink/p/?LinkId=403864)
|
||||||
|
|
||||||
**Security Note:**<br>Although we strongly recommend against it, if you don’t want your computer to automatically download the updated version list from Microsoft, run the following command from a command prompt:
|
**Security Note:**<br>Although we strongly recommend against it, if you don’t want your computer to automatically download the updated version list from Microsoft, run the following command from a command prompt:
|
||||||
|
|
||||||
@ -171,7 +173,7 @@ Here’s a detailed example and description of what’s included in the VersionA
|
|||||||
### Inventory your ActiveX controls by using a local WMI class
|
### Inventory your ActiveX controls by using a local WMI class
|
||||||
For Windows 10 you also have the option to log your inventory info to a local WMI class. Info logged to this class includes all of info you get from the .csv file, plus the CLSID of the loaded ActiveX control or the name of any apps started from an ActiveX control.
|
For Windows 10 you also have the option to log your inventory info to a local WMI class. Info logged to this class includes all of info you get from the .csv file, plus the CLSID of the loaded ActiveX control or the name of any apps started from an ActiveX control.
|
||||||
|
|
||||||
### Before you begin
|
#### Before you begin
|
||||||
Before you can use WMI to inventory your ActiveX controls, you need to [download the configuration package (.zip file)](http://go.microsoft.com/fwlink/p/?LinkId=616971), which includes:
|
Before you can use WMI to inventory your ActiveX controls, you need to [download the configuration package (.zip file)](http://go.microsoft.com/fwlink/p/?LinkId=616971), which includes:
|
||||||
|
|
||||||
- **ConfigureWMILogging.ps1**. A Windows PowerShell script.
|
- **ConfigureWMILogging.ps1**. A Windows PowerShell script.
|
||||||
|
@ -41,7 +41,7 @@ What you'll have to set up:
|
|||||||
|
|
||||||
- LOB publishers need to have an app in the Store, or have an app ready to submit to the Store.
|
- LOB publishers need to have an app in the Store, or have an app ready to submit to the Store.
|
||||||
|
|
||||||
### <a href="" id="add-lob-publisher"></a>Add an LOB publisher (admin)
|
### <a href="" id="add-lob-publisher"></a>Add an LOB publisher (Store for Business Admin)
|
||||||
|
|
||||||
For developers within your own organization, or ISVs you're working with to create LOB apps, you'll need to invite them to become a LOB publisher.
|
For developers within your own organization, or ISVs you're working with to create LOB apps, you'll need to invite them to become a LOB publisher.
|
||||||
|
|
||||||
@ -49,7 +49,8 @@ For developers within your own organization, or ISVs you're working with to crea
|
|||||||
|
|
||||||
1. Sign in to the [Windows Store for Business]( http://go.microsoft.com/fwlink/p/?LinkId=623531).
|
1. Sign in to the [Windows Store for Business]( http://go.microsoft.com/fwlink/p/?LinkId=623531).
|
||||||
2. Click **Settings**, and then choose **LOB publishers**.
|
2. Click **Settings**, and then choose **LOB publishers**.
|
||||||
3. On the Line-of business publishers page, click **Add** to complete a form and send an email invitation to a developer.
|
3. On the Line-of business publishers page, click **Add** to complete a form and send an email invitation to a developer.<br>
|
||||||
|
**Note** This needs to be the email address listed in contact info for the developer account.
|
||||||
|
|
||||||
### <a href="" id="submit-lob-app"></a>Submit apps (LOB publisher)
|
### <a href="" id="submit-lob-app"></a>Submit apps (LOB publisher)
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user