In this scenario, Group Policy Preferences incorrectly sets its mapped network printer as the default printer. The expected behavior is that the original default printer setting on the client computer is not changed because the client computer has a local DOT4 printer.
This problem is caused by the printer detection code. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing.
Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request.
The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language.
The English United States version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias.
Microsoft recommends that you use the Optional limited Enhanced Limited level with Desktop Analytics. For more information, see Configure Windows diagnostic data in your organization. This setting only applies when the AllowTelemetry setting is 2. It limits the Enhanced diagnostic data events sent to Microsoft to just those events needed by Desktop Analytics.
For more information, see Windows 10 diagnostic data events and fields collected through the limit enhanced diagnostic data policy. Enable devices to send the device name. The device name isn't sent to Microsoft by default. If you don't send the device name, it appears in Desktop Analytics as "Unknown".
For more information, see Device name. Desktop Analytics requires a value of 1. For more information, see Commercial Data Opt-in in Windows 7. If your environment requires a user-authenticated proxy with Windows Integrated Authentication for internet access, Desktop Analytics requires a value of 0 for data collection to work correctly. For more information, see Proxy server authentication. If you set this policy to a different value, it overrides the Commercial ID set by Configuration Manager.
If it's not the same ID, configured devices may not appear in Desktop Analytics. If you set this policy to a different value, it overrides the global diagnostic data level that you set in Configuration Manager for the target collection. This policy is dependent upon the prior AllowTelemetry setting. Depending upon the level you set in Configuration Manager or with group policy, this policy can change the diagnostic data level on the device to Enhanced or Enhanced Limited.
This policy only applies if AllowTelemetry is set to 2 Enhanced. If you opt-in to send device names in Configuration Manager, you can override it by configuring this policy to Disabled.
When you disable this setting, device names appear as "Unknown" in Desktop Analytics. If you configure Configuration Manager devices to use user-authenticated proxy 0 , if you then configure this policy to Disable Authenticated Proxy usage 1 , then the device sends diagnostic data in the system context instead of the user's context. If you don't configure the device with a proxy in system context, or the device can't authenticate to the proxy, Windows can't send diagnostic data to Desktop Analytics.
If you configure this policy to Disabled 0 , devices may not appear in Desktop Analytics. Starting in Windows 10, version , Windows notifies users when the diagnostic data level changes. Use this policy to disable notifications. Starting in Windows 10, version , users can set a lower level. Use this policy to prevent users from changing the diagnostic level. Important Windows Vista hotfixes and Windows Server hotfixes are included in the same packages.
However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
Service Pack 1 is integrated into the release version of Windows Server RTM milestone files have a 6. Important Windows 7 hotfixes and Windows Server R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems.
The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature. Update the Group Policy preferences again. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. For more information about Group Policy preferences, visit the following Microsoft TechNet Web site: Group Policy preferences For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:.
Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you!
0コメント