Introduction
The compatibility pack that is described in this article enables the following features for Windows 10 Enterprise 2015 long-term servicing branch (LTSB) edition. (Other editions of Windows 10 are not supported.)Â
-
Microsoft System Center Configuration Manager client features
-
The Branch Distribution Point role
-
The Administrator Console
Additionally, this compatibility pack adds Windows 10 to the list of supported platforms for the following features:
-
Software distribution
-
Software update management
-
Desired configuration management
Note Operating System Deployment is not supported on Windows 10 together with System Center Configuration Manager 2007. Additional notes
-
To use the Configuration Manager Console and the Configuration Manager client on a computer that is running Windows 10 Enterprise 2015 LTSB edition, the Microsoft .NET Framework 3.5 must be enabled. For more information, refer to Installing the .NET Framework 3.5 on Windows 8, Windows 8.1, and Windows 10.
-
When you use the option to check a file version in a task sequence, some files have unexpected versions. This issue occurs for files in the \Windows directory and its subdirectories, such as \Windows\System32. Some files will have versions in the 6.x range instead of the 10.x range.
For example, some files may return a version of 6.2.10240.0 instead of 10.0.10240.0 when they are queried programmatically. You can avoid this scenario by using the option to query Windows Management Instrumentation (WMI) instead of checking a file version. For example, the following query would evaluate as expected:select * from CIM_Datafile Where Name = 'c:\\windows\\system32\\notepad.exe' and Version = '10.0.10240.16394'
More Information
To fix these issues, install the following hotfix rollup package on the affected System Center Configuration Manager 2007 SP2 primary site server. The installation wizard for the package creates another package for clients. To deploy the package to all clients after you run the package on the primary site server, you have to create an advertisement.
Note The hotfix package can be installed on a System Center Configuration Manager 2007 SP2 site server that is running an x86-based or x64-based version of an operating system. For more information about how to deploy a hotfix package to the System Center Configuration Manager 2007 SP2 site server, click the following article number to view the article in the Microsoft Knowledge Base:2477182Â System Center Configuration Manager 2007 hotfix installation guidance
Hotfix information
A supported hotfix is available from Microsoft Support. 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 aren't 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 get 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 don't 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:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.
Prerequisites
To apply this hotfix, you must have Service Pack 2 for System Center Configuration Manager 2007 installed.
Registry information
To use the hotfix in this package, you don't have to make any changes to the registry.
Restart information
You don't have to restart the computer after you apply this hotfix.
Note We recommend that you close the Configuration Manager Administration Console before you install this hotfix package.Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Adminui.common.dll |
4.0.6487.2239 |
1,845,936 |
01-Feb-2010 |
19:30 |
x86 |
Adminui.consolerootactions.dll |
4.0.6487.2239 |
55,984 |
01-Feb-2010 |
19:30 |
x86 |
Adminui.dcmproperties.dll |
4.0.6487.2239 |
371,376 |
01-Feb-2010 |
19:30 |
x86 |
Adminui.softwareupdatemanagementpoint.dll |
4.0.6487.2239 |
252,592 |
01-Feb-2010 |
19:30 |
x86 |
Adsource.dll |
4.0.6487.2239 |
128,176 |
01-Feb-2010 |
19:30 |
x86 |
Baserc.dll |
4.0.6487.2239 |
61,616 |
01-Feb-2010 |
19:30 |
x86 |
Basesql.dll |
4.0.6487.2239 |
195,760 |
01-Feb-2010 |
19:30 |
x86 |
Basesvr.dll |
4.0.6487.2239 |
1,746,608 |
01-Feb-2010 |
19:30 |
x86 |
Ccm.dll |
4.0.6487.2239 |
154,800 |
01-Feb-2010 |
19:30 |
x86 |
Imrsdk.dll |
10.0.0.13059 |
2,143,688 |
15-Jun-2015 |
09:25 |
x86 |
Mp.msi |
Not applicable |
9,355,264 |
01-Feb-2010 |
19:30 |
Not applicable |
Policypv.dll |
4.0.6487.2239 |
478,896 |
01-Feb-2010 |
19:30 |
x86 |
Sccm2007ac-sp2-kb3044077-x86-enu.msp |
Not applicable |
684,032 |
01-Feb-2010 |
19:30 |
Not applicable |
Smsprov.dll |
4.0.6487.2239 |
3,890,352 |
01-Feb-2010 |
19:30 |
x86 |
Update.sql |
Not applicable |
9,944 |
01-Feb-2010 |
19:30 |
Not applicable |
Wuahandler.dll |
4.0.6487.2239 |
229,552 |
01-Feb-2010 |
19:30 |
x86 |
Baserc.dll |
4.0.6487.2239 |
61,616 |
01-Feb-2010 |
19:30 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.