Steps:

0: Specify the new timeout value in script:

e.g.(set new value as 10mins): NewValue =          600

1: Save the script in a vbs file.

e.g.: test.vbs

2: Run the script by sepcify the site server and site code in a correct credential which has the permission the make the change on your site server.

e.g.: c:\cscript.exe test.vbs MySite PRS 

3: After it modified the value successfully, you can triger a machine policy retrieval and evaluation cycle for your client, then your client would download the latest policy and the value should be changed. To verify the new value applied on client, you can run wbemtest, and connect to the namespace "root\ccm\policy\machine\actualconfig" then run query: "Select ScriptExecutionTimeout from CCM_ConfigurationManagementClientConfig" to see if value has been changed.

-Script Body-

On Error Resume Next

' Define string variables

Class_Name =        "SMS_SCI_ClientComp"
Class_ItemName =    "Configuration Management Agent"
Class_ItemType =    "Client Component"
Property_Name =     "ScriptExecutionTimeout"
NewValue =          600

' Check command line parameters ?on failure, report the error and terminate.
' The SMS Provider server name and the site code are required.

set args=wscript.arguments

If args.Count = 2 then
    SMSProviderServer = UCASE(Wscript.Arguments(0))
    SiteCode = UCASE(Wscript.Arguments(1))
Else
    wscript.Echo "Incorrect command line arguments." & vbCrLf & "Usage: cscript /nologo ModifySCFProperty.vbs <smsproviderserver> <sitecode>" & vbCrLf & "Example: cscript /nologo ModifySCFProperty.vbs SERVER1 S01" & vbCrLf
    WScript.Quit(1)
End If

' Connect to the SMS Provider ?on failure, report the error and exit.

SMSProviderServer = "\\" + SMSProviderServer + "\"
Set ObjSvc = GetObject("winmgmts:" & "{impersonationLevel=Impersonate,authenticationLevel=Pkt}!" & SMSProviderServer & "root\sms\site_" & SiteCode)

If Err.Number <> 0 Then
    wscript.Echo "Failed to connect to provider server with code: " & Err.Number & ".  Exiting!"
    WScript.Quit(2)
End If

' Get the requested instance of the class ?on failure, report the error and exit.

Set objInst = ObjSvc.Get(Class_Name & ".ItemName='" & Class_ItemName & "',ItemType='" & Class_ItemType & "',SiteCode='" & SiteCode &"'")

If Err.Number <> 0 Then
    WScript.Echo "Failed to open desired object with error code " & Err.Number & " (" & Err.Description & ").  Exiting!"
    WScript.Quit(3)
End If

' Loop through the properties until we find a match (or run out of properties) ?on failure, report the error and exit.

bFoundProperty = False

For Each objProp in objInst.Props
    If objProp.PropertyName = Property_Name Then
        bFoundProperty = True
        Exit For
    End If
Next

If bFoundProperty = False Then
    WScript.Echo "Requested class instance was found but the property was not found.  Exiting without making any changes."
    WScript.Quit(4)
End If 

' Property found. Check to see if existing value matches, change it as appropriate - on failure to save, report the error and exit.

If objProp.Value = NewValue Then
    WScript.Echo "Property '" & Property_Name & "' found and matches the new value '" & NewValue & "'.  Not making any changes."
    WScript.Quit(0)
Else
    OriginalValue = objProp.Value
    objProp.Value = NewValue
    objProp.Put_
    objInst.Put_

    If Err.Number <> 0 Then
        wscript.Echo "Failed to save the change with error code: " & Err.Number & ".  Exiting!"
        WScript.Quit(5)
    Else
        WScript.Echo "Property '" & Property_Name & "' successfully change from '" & OriginalValue & "' to '" & NewValue & "'."
    End If
End If

Besides, you can modify the class/property names in the script to modify other values to customize your site configuration.

Thanks,

Fei

Then I tried to run the “\Windows\Microsoft.Net\Framework64\v4.0.30319\aspnet_regiis.exe
–i” to refresh the ASP.net and IIS configuration, now the issue was resolved, the
DMP request is back to normal!

Thanks,

Fei

Please refer the link https://support.microsoft.com/kb/2692929 for more details: "0x80041001" error when the Win32_Environment WMI class is
queried by multiple requestors in Windows 7 or in Windows Server 2008 R2

Issue Discription:

Recently, some of customers reported that they imported the new SCCM Monitoring Pack and encountered several script errors with the error message “Failed to read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class”. Peoples on the System Center Central forum(https://www.systemcentercentral.com/Forums/tabid/60/indexId/89622/vsdCurPage/1/Default.aspx?tag=Forums+Operations_Manager) also had long discussion about this but still no workaround to resolve it.

Repro: <Executing multiple scheduled task(~4) to execute following script>

Environment: Windows Server 2008 R2

On Error Resume Next

Dim sCimv2namespace, sProcArchQuery, oProcArchObjectSet, oProcArchObject, sProcArch

sCimv2namespace = "winmgmts:\\.\root\cimv2"

sProcArchQuery = "Select * From Win32_Environment Where Name = ""Processor_Architecture"""

Set oProcArchObjectSet = WMIExecQuery (sCimv2namespace, sProcArchQuery)

Set oProcArchObject = oProcArchObjectSet.Item("Win32_Environment.Name=""PROCESSOR_ARCHITECTURE"",UserName=""<SYSTEM>""")

sProcArch = oProcArchObject.VariableValue

On Error GoTo 0

Select Case sProcArch

  Case "AMD64"

    REG_PATH_SMS = "SOFTWARE\Wow6432Node\Microsoft\SMS"

  Case "x86"

    REG_PATH_SMS = "SOFTWARE\Microsoft\SMS"

  Case Else

     ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class."

End Select

Investigation:

Actually, this error is caused by a Windows WMI bug, when there are multiple scheduled tasks to executing the script and it will fail after some times with 0x80041001 /WBEM_E_FAILED.

Workaround:

Option#1:

Modify the script to check the registry instead of WMI.

Sample:  Modify the System Center Operations Manager 2007\Health Service State\Management
Pack\Microsoft.SystemCenter.ConfigurationManager.2007.{GUID}{GUID}.xml

-------------------------------- Disable/remove all of the WMI check script in the xml----------------------------

On Error Resume Next

Dim sCimv2namespace, sProcArchQuery, oProcArchObjectSet, oProcArchObject, sProcArch

sCimv2namespace = "winmgmts:\\.\root\cimv2"

sProcArchQuery = "Select * From Win32_Environment Where Name = ""Processor_Architecture"""

....

....

ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class."

End Select

-------------------------------- Use following registry check script instead ----------------------------

Please note, the Sub Main of the script for ConfigMgr 2007 Monitor SMS Executive Crash Dumps would set the REG_KEY_IDENTIFICATION(not REG_PATH_SMS) after the processor architecture check.

If (CheckWow64RegistryKeyExists() = True) Then

  REG_PATH_SMS = "SOFTWARE\Wow6432Node\Microsoft\SMS"  ‘ or REG_KEY_IDENTIFICATION = REG_KEY_WOW64_IDENTIFICATION

Else

  REG_PATH_SMS = "SOFTWARE\Microsoft\SMS"  ‘ or REG_KEY_IDENTIFICATION = REG_KEY_WOW64_IDENTIFICATION

End If

------------------------------------------------------------------------------------------------------------------------------

Option#2:

Add code to retry the WMI Query when the query failed for the first time.

Sample: Modify
the System Center Operations Manager 2007\Health Service State\Management
Pack\Microsoft.SystemCenter.ConfigurationManager.2007.{GUID}{GUID}.xml

-------------------------------- Disable/remove all of the WMI check script in the xml----------------------------

On Error Resume Next

Dim sCimv2namespace, sProcArchQuery, oProcArchObjectSet, oProcArchObject, sProcArch

sCimv2namespace = "winmgmts:\\.\root\cimv2"

sProcArchQuery = "Select * From Win32_Environment Where Name = ""Processor_Architecture"""

....

....

ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class."

End Select

-------------------------------- Use following script
instead(would try to query the WMI 5 times with 5 seconds period) ----------------------------

Please note, the Sub Main of the script for ConfigMgr 2007 Monitor SMS Executive Crash Dumps would set the REG_KEY_IDENTIFICATION (not REG_PATH_SMS) after the processor architecture check.

Dim sCimv2namespace, sProcArchQuery, oProcArchObjectSet, oProcArchObject, sProcArch, StartTimeA, EndTimeB, TimeOutC, RetryResult, RetryCount, RetryErrMessage

sCimv2namespace = "winmgmts:\\.\root\cimv2"

sProcArchQuery = "Select * From Win32_Environment Where Name = ""Processor_Architecture"""

RetrunResult = false

RetryCount = 5 'will retry 5 times

TimeOutC = 5 'wait 5 sec per time

Do While RetryCount > 0

  On Error Resume Next

  Set oProcArchObjectSet = WMIExecQuery (sCimv2namespace, sProcArchQuery)

  Set oProcArchObject = oProcArchObjectSet.Item("Win32_Environment.Name=""PROCESSOR_ARCHITECTURE"",UserName=""<SYSTEM>""")

  sProcArch = oProcArchObject.VariableValue

  If Err.Number <> 0 Then

    RetryCount = RetryCount – 1

    ‘if encountered runtime error, then collect the error message into RetryErrMessage.

    RetryErrMessage = RetryErrMessage + "Try#" & 5 - RetryCount & ":Runtime Error(" & CStr(Err.Number) & ") - " & Err.Description & ";"

  Else

    Select Case sProcArch

        Case "AMD64"

                REG_PATH_SMS = "SOFTWARE\Wow6432Node\Microsoft\SMS" ‘or REG_KEY_IDENTIFICATION = REG_KEY_WOW64_IDENTIFICATION

                RetryResult = true

                Exit Do 

        Case "x86"

                REG_PATH_SMS = "SOFTWARE\Microsoft\SMS"  ‘or REG_KEY_IDENTIFICATION = REG_KEY_WOW64_IDENTIFICATION

                RetryResult = true

                Exit Do

        Case Else

                RetryCount = RetryCount – 1

                ‘if not a runtime error, then it should be an invalid value, so collect the invalid value into RetryErrMessage

                RetryErrMessage = RetryErrMessage + "Try#" & 5 - RetryCount & ":Invalid Value - '" & sProcArch & "', should be 'AMD64' or 'x86';"

   End Select

  End If

  ‘waiting...

  StartTimeA = Timer

  EndTimeB = 0

  Do While EndTimeB - StartTimeA <= TimeOutC

    EndTimeB = Timer

    If EndTimeB < StartTimeA Then

      StartTimeB = EndTimeA

    End If

  Loop

  On Error GoTo 0

Loop

‘if retry to get the value successfully, then it would not report the pervious error.

If RetryResult = false Then

ScriptError "read %PROCESSOR_ARCHITECTURE environment variable from Win32_Environment WMI class. Script tried to query the WMI 5 times but all failed... [Error Detail]: " & RetryErrMessage

End If

Installing the Configuration Manager 2007 database on a clustered virtual Microsoft SQL Server instance

The Configuration Manager 2007 site database can be installed on a clustered virtual Microsoft SQL Server instance by following steps:

1. Create the virtual SQL Server cluster to host the site database on an existing Windows Server cluster environment.  We suggest that you to enable Kerberos and register the SPN for the clustered SQL Server since failure to do so can cause SQL backup issues. 

See the following link for more information: https://social.technet.microsoft.com/forums/en-US/configmgrbackup/thread/de3d7be3-7d1f-47d6-90bc-fe25b1a19321/.

To configure these, please refer the online document on https://msdn.microsoft.com/en-us/library/ms191153.aspx.

2. Add the machine account of the primary site server machine to the Local Administrators group of each Windows Server cluster node computer. This is required to allow the site server to install and configure settings later.

3. In the virtual SQL Server instance, assign the sysadmin SQL Server role to the user account running Configuration Manager Setup.

4. Start Configuration Manager Setup and select to install Configuration Manager using custom settings.

5. On the Configuration Manager Database Server page of the Configuration Manager Setup Wizard, enter the name of the clustered virtual SQL Server instance to host the site database and the name for the site database to be created on that instance by setup.

After the installation, the site system list will show all the SQL Cluster nodes with the database role on them.  In the screen shot below the two SQL Cluster nodes are 2K3SQL1 & 2K3SQL2:

ref: https://technet.microsoft.com/en-us/library/bb680513.aspx

Moving the Configuration Manager 2007 site database to a clustered virtual Microsoft SQL Server instance

The Configuration Manager 2007 site database can be moved to a clustered virtual Microsoft SQL Server instance by following the steps below(and please remember the SQL Collation to move SCCM DataBase.):

1. Back up the site database on the current site database server and restore it on the clustered virtual Microsoft SQL Server instance using the SQL Server Management Studio.  We suggest that you enable Kerberos and register the SPN for the clustered SQL Server to avoid potential SQL backup issues.

2. Ensure the primary site server computer account has administrative privileges over each SQL cluster node computer.

3. Close any open Configuration Manager console connections to the site server.

4. On the primary site server computer, use the hierarchy maintenance tool (Preinst.exe) to stop all site services with the following command:

Preinst /stopsite

5. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup.  Alternatively you can navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.

6. Click Next on the Configuration Manager Setup Wizard Welcome page.

7. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.

8. Select Modify SQL Server configuration on the Configuration Manager Setup Wizard Site Maintenance page.

9. Enter the name of the clustered virtual SQL Server instance to host the site database for the new site database server as well as the site database name on the Configuration Manager Setup Wizard SQL Server Configuration page.

10. Configuration Manager Setup performs the SQL Server configuration process.

11. Restart the primary site server computer and verify the site is functioning normally.

After the process is done, the site system list should show the clustered virtual Microsoft SQL Server temporarily with the database role.  In the screenshot below, the virtual SQL Cluster server is SQL2K8CLUSTERNA and the old database server is SQLCLUSTER-DC.

Just wait few minutes and refresh the Site System list.  After a few moments all of the SQL Cluster nodes should be displayed in the site system list with the  database role, and the clustered virtual Microsoft SQL Server will have no longer with the database role.  In the screen shot below, the SQL Cluster nodes are SQL2K8NMND2 & SQL2K8SP2N, and the SQL Cluster virtual server is SQL2K8CLUSTERNA:

ref: https://technet.microsoft.com/en-us/library/bb680707.aspx

Thanks,

Fei 

Consider following scenario:

You specified the “domain\user” with password correctly in your System Center Updates Publisher 2011 proxy settings.

Your proxy admin enabled both the “Integrated” and “Basic” authentication methods on your proxy server(Microsoft Forefront TMG server as the example here):

Then you would encounter the 407 proxy authentication error when your System Center Updates Publisher tried to access internet to download catalogs with the proxy settings.

ROOT CAUSE:

The System Center Updates Publisher 2011 would only support the “Basic” authentication method.

WORKAROUND:

#1: Disable the “Integrated” and enable the “Basic” method on your proxy server.

#2: Download the catalogs manually from internet then import into the System Center Updates Publisher.

Thanks,

Fei

The SCUP tool would help users to publish their private updates to WSUS and sync by ConfigMgr 2007 easily,  and users always tried to sync these updates with WSUS by click “Run Synchronization” on ConfigMgr console. But this manually sync would not sync the “Expired” flag from WSUS to SCCM, so if the user want to expire his update by SCUP and run the manual sync, the log (SMS\logs\wsyncmgr.log) would say “No changes made to the SMS database”:

That’s because the manual sync would not sync the expired flag for the existed update, and only the scheduled sync could do that, so we put the workaround here to resolve this problem by using the scheduled sync.   

WORKAROUND:

1.  Open the SCUP console, then select and expire the update that you want to expire.

2.  Set the update with “Publish” flag and click publish update to re-publish it, so the update record in WSUS database would be flagged as “Expired”.

    Record in WSUS Database:

3.  Open the ConfigMgr console, then navigate to Site Management-><SiteCode>->Component Configuration->Software Update Point and open the properties, and make sure the “Enable synchronization on a schedule” is checked.(Note: Default is 7 days, you could also set a custom schedule for a quick check.)

 4.   Wait the scheduled sync and check the log(SMS\Logs\wsyncmgr.log), it would say: ”Removed 1 unreferenced updates”

5.    Refresh your update list in ConfigMgr console, and now the update was flagged as “Expired”.

-Fei