Systen Center 2012 Configuration Manager Client
Greetings.
is this just a CAL or Server?
thank you.
Ganga
http://www.microsoft.com/licensing/about-licensing/SystemCenter2012-R2.aspx
Similar Messages
-
Configure Web console for existing "System center 2012 configuration manager R2"
How to configure Web console for existing "System center 2012 configuration manager R2"
There is no web console in ConfigMgr 2012. If you want a web console you have to look at third-party products.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
System Center 2012 configuration manager
Hi All,
I have access to SCM 2012 R2 and i want to kill one ruining application program on user computer from software center so is it possible to kill from the server.
Br,
Ashish SangawarIf the installation is started, the easiest way to stop a running installation is by killing the installation process (in most cases msiexec.exe). This can not be done via the Configuration Manager Console.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
I added a number of folders and files in the excluded files and locations and after that I am unable to access the Antimalware Policies it gives the following error( I am new at sccm):
Unhandled exception occurred in your application. If you click continue the application will ignore this error and attempt to continue. I you click quit the application will close immediately
Object reference not set to an instance of an oblect
With the following details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryPropertySingleItem.get_BooleanValue()
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.Utilities.CreateSCIResultObject(IResultObject antimalwareResultObject)
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.Utilities.LoadDefaultSettingObjects(ConnectionManagerBase connectionManager, Dictionary`2& defaultSettingObjects, DialogType dialogType)
at Microsoft.ConfigurationManagement.AdminConsole.ClientAgentSettings.HomePageControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SccmPageControlDialog.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18051 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Microsoft.ConfigurationManagement
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.exe
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18022 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18045 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
Microsoft.EnterpriseManagement.UI.ConsoleFramework
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.ConsoleFramework.DLL
Microsoft.ConfigurationManagement.ManagementProvider
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.ManagementProvider.DLL
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.EnterpriseManagement.UI.Foundation
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.Foundation.DLL
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.ServiceModel.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18045 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Web/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll
System.ServiceModel
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18056 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll
SMDiagnostics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
System.ServiceModel.Internals
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18016 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
AdminUI.SmsTraceListener
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SmsTraceListener.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.EnterpriseManagement.UI.ConsoleFramework.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.ConsoleFramework.resources.DLL
Microsoft.EnterpriseManagement.UI.RibbonConsole
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonConsole.DLL
RibbonControlsLibrary
Assembly Version: 3.5.41019.1
Win32 Version: 3.5.41019.1
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/RibbonControlsLibrary.DLL
PresentationFramework.AeroLite
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.AeroLite/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.AeroLite.dll
Microsoft.EnterpriseManagement.UI.RibbonLayout
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonLayout.DLL
Microsoft.Windows.Shell
Assembly Version: 3.5.41019.1
Win32 Version: 3.5.41019.1
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.Windows.Shell.DLL
Microsoft.VirtualManager.UI.ViewModel.Core
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.VirtualManager.UI.ViewModel.Core.DLL
Microsoft.EnterpriseManagement.UI.Controls
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.Controls.DLL
Microsoft.EnterpriseManagement.UI.RibbonData
Assembly Version: 1.0.523.0
Win32 Version: 3.0.2085.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.RibbonData.DLL
AdminUI.HelpSystem
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.HelpSystem.DLL
AdminUI.UIResources
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.UIResources.DLL
AdminUI.PersonalFolders
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.PersonalFolders.DLL
AdminUI.ConsoleGlobalSearchView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleGlobalSearchView.DLL
PresentationFramework.Classic
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Classic/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Classic.dll
Microsoft.EnterpriseManagement.UI.Controls.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.Controls.resources.DLL
WindowsFormsIntegration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_4.0.0.0__31bf3856ad364e35/WindowsFormsIntegration.dll
PresentationFramework-SystemXml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemXml/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemXml.dll
PresentationFramework.Aero
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero.dll
PresentationFramework-SystemCore
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemCore/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemCore.dll
UIAutomationProvider
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll
UIAutomationTypes
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll
AdminUI.Controls
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Controls.DLL
AdminUI.Common
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Common.DLL
Microsoft.EnterpriseManagement.UI.WpfViews
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.WpfViews.DLL
Microsoft.EnterpriseManagement.UI.ViewFramework
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.EnterpriseManagement.UI.ViewFramework.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
AdminUI.WqlQueryEngine
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.WqlQueryEngine.DLL
AdminUI.WqlInitializer
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.WqlInitializer.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.CollectionMenuActions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.CollectionMenuActions.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.OSImage
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.OSImage.DLL
AdminUI.AssetIntelligence
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AssetIntelligence.DLL
AdminUI.SoftwareMeteringRule
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SoftwareMeteringRule.DLL
AdminUI.DcmProperties
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DcmProperties.DLL
AdminUI.UsmPolicy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.UsmPolicy.DLL
AdminUI.ClientAgentSettings
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientAgentSettings.DLL
AdminUI.FirewallPolicy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.FirewallPolicy.DLL
AdminUI.LegacySWD
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.LegacySWD.DLL
AdminUI.ConditionalDeliveryRule
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConditionalDeliveryRule.DLL
AdminUI.VirtualEnvironment
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.VirtualEnvironment.DLL
AdminUI.SideloadKeys
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SideloadKeys.DLL
AdminUI.SoftwareUpdateProperties
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SoftwareUpdateProperties.DLL
AdminUI.Driver
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Driver.DLL
AdminUI.DriverPackage
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DriverPackage.DLL
AdminUI.Subscriptions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Subscriptions.DLL
AdminUI.Queries
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Queries.DLL
AdminUI.SrsReporting
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SrsReporting.DLL
AdminUI.SiteHierarchyVisualization
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteHierarchyVisualization.DLL
AdminUI.SystemStatus
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SystemStatus.DLL
AdminUI.ClientOperation
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientOperation.DLL
AdminUI.ClientHealth
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ClientHealth.DLL
AdminUI.ContentMonitoring
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ContentMonitoring.DLL
AdminUI.AntiMalware
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AntiMalware.DLL
AdminUI.CloudServiceRoles
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.CloudServiceRoles.DLL
AdminUI.SiteHierarchy
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteHierarchy.DLL
AdminUI.SiteBoundaries
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteBoundaries.DLL
AdminUI.ExchangeConnector
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ExchangeConnector.DLL
AdminUI.Addresses
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Addresses.DLL
AdminUI.ActiveDirectory
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ActiveDirectory.DLL
AdminUI.AzureServices
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AzureServices.DLL
AdminUI.RbacUser
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacUser.DLL
AdminUI.RbacRole
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacRole.DLL
AdminUI.RbacCategory
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.RbacCategory.DLL
AdminUI.Package
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Package.DLL
AdminUI.Certificate
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.Certificate.DLL
AdminUI.SiteSystems
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.SiteSystems.DLL
AdminUI.HomePageView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.HomePageView.DLL
Microsoft.EnterpriseManagement.UI.WpfViews.resources
Assembly Version: 7.1.1000.0
Win32 Version: 7.1.3825.0
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/en/Microsoft.EnterpriseManagement.UI.WpfViews.resources.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.ViewCommon
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ViewCommon.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.AICustomizeCatalog
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AICustomizeCatalog.DLL
AdminUI.AISoftwareProducts
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.AISoftwareProducts.DLL
AdminUI.ConsoleView
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleView.DLL
AdminUI.External.Controls
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.External.Controls.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
PresentationFramework-SystemData
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemData/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemData.dll
Microsoft.ConfigurationManagement.DialogFramework
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.DialogFramework.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.DialogFoundation
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DialogFoundation.DLL
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
AdminUI.DetailPanel
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.DetailPanel.DLL
AdminUI.FeaturesUtilities
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.FeaturesUtilities.DLL
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.18058 built by: FX45RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
AdminUI.ConnectionAccount
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConnectionAccount.DLL
System.Runtime.Caching
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.17929
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll
AdminUI.ConsoleRootActions
Assembly Version: 5.0.0.0
Win32 Version: 5.0.7804.1000
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Configuration%20Manager/AdminConsole/bin/AdminUI.ConsoleRootActions.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
When I go and check the Endpoint Protection properties it gives me the following Error:
The SMS Provider reported and error
With the following Details:
ConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "ERROR ON Property Convert";
ErrorCode = 0;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspsitesettingitem.h";
Line = 377;
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_SCI_ClientComp WHERE FileType=2 AND SiteCode='CCM' AND ItemName='Antimalware Agent' AND ItemType='Client Component'";
ProviderName = "WinMgmt";
StatusCode = 2147749917;
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
The SMS Provider reported an error.
Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.EndpointProtectionSpynetControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()
System.Management.ManagementException
Unexpected error
Stack Trace:
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.EndpointProtectionSpynetControl.InitializePageControl()
at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()Hi,
If you only add one file into the excluded files and locations, does this error still appear?
Could you reproduce this error on another system?
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
To troubleshoot issues related to Inventory, we can view the related logs or force a full inventory to analyze the reason. In these article, we mainly introduce
the detailed ways to enable Verbose and Debug logging,
save the inventory report and force a full inventory on the client.
How to force a full inventory on the client
1. Open wbemtest and connect to “root\ccm\invagt”.
Figure 1.
2. Click “Enum Classes…”and then click “OK”.
Figure 2.
In the Query Result, you can view the cache for each entry. (Figure 3)
{00000000-0000-0000-0000-000000000001}
Hardware Inventory
{00000000-0000-0000-0000-000000000002}
Software Inventory
{00000000-0000-0000-0000-000000000003}
Heartbeat
{00000000-0000-0000-0000-0000000000010} File Collection
Figure 3.
3. You can highlight the entry that contains the action you want to force a full to be sent and click “Delete” to delete it:
Figure 4.
4. Close all wbemtest dialog boxes and initiate the appropriate action in the Client Agent Action to perform a full inventory.
Figure 5.
How to enable
Verbose and Debug logging
It is also helpful to trace the flow if you enable Verbose and Debug logging on the client,
Management Point and Site Server.
To set verbose/debug logging on an SCCM client or
Management Point, you can simply edit (or create) the following registry keys:
HKLM/Software/Wow6432Node/Microsoft/CCM/Logging/@Global/LogLevel to 0
HKLM/Software/Wow6432Node/Microsoft/CCM/Logging/DebugLogging/Enabled to True
Figure 6.
Figure 7.
On the site server, you edit the following registry key to enable verbose logging and then restart the SMS_Executive (or the state system
component):
HKLM/Software/Wow6432Node/Microsoft/SMS/Components/SMS_STATE_SYSTEM/Verbose Logging – Reg_DWORD set to 1
Figure 8.
How to save the inventory report
To force the ConfigMgr client to save off a copy of the report that it sends to the Management Point, you can create an empty folder/directory under the inventory temp directory
called archive_reports.sms.
Then edit the following registry value to point to the inventory temp directory:
HKLM\Software\Microsoft\SMS\Mobile Client\Inventory\ Temp Directory
Figure 9.
Figure 10.
From the figure 9, you can see that the temp directory path is C:\Windows\CCM\Inventory\Temp. After we run the hardware inventory Cycle again, you can see the report file is
saved in the path we have defined automatically. (Figure 10)
(Note: Please delete the
archive_reports.sms folder when have finished the troubleshooting steps to save disk space.)
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.Hi,
I have troubleshooted this error message several times and can say that this is a generic error message. The reason can be different in your Case. As suggested in the error message you should first check all the steps in the following kb article.
http://support.microsoft.com/kb/2742275/tr
In most of my cases the performance counter corruption was the reason of this error message there fore I would suggest you to first check the System and application event logs for performance counter corruption. Right click on the System event > Find
and search for corrupt.
Additionally it is also mentioned in one of the MS kb articles that deploying winrm policies on Hyper-V Host is forbidden in a SCVMM environment.
If this is the reason in your Case you should disable it. No other chance.
Regards,
Cengiz Kuskaya -
Managing Mac OS X clinet with System Center 2012 Configuration Manager
toby wells wrote:Most large sites would use Casper for Mac management....Does work best. OS X has its own ecosystem, and preference is to stay with it. Know Apple specifically intends 3rd party development of these management tools, and Casper is the established veteran option.
Keep in mind the other OS X admin tools—
OS X Server ($20, only need a Mac to install software)
ARD (Apple Remote Desktop)ReposadoMunkiTime Machine Server (great as current OS X versions allow multiple Time Machine mount points)etcJAMF, makers of Casper Suite, has its own ecosystem, community, user groups, and annual conference—http://www.jamfsoftware.com/products/https://jamfnation.jamfsoftware.com/http://www.jamfsoftware.com/events/jamf-nation-user-conference/etchi guys
I am keen on getting some sort of control on Mac OS X clients on my IT environment via SCCM2012 R2
Has any one done this? I did research on Google and couldn't find proper How to guide.
Feedback much appreciated
This topic first appeared in the Spiceworks Community -
User device affinity in Microsoft System Center 2012 Configuration Manager
What would be the microsoft recommended User device affinity time in sccm 2012
User device affinity usage threshold (minutes)-?
User device affinity usage threshold (Days)-?
Thanks,
Sengottuvel mThe default settings seem to work well.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
Remote Control System Center 2012 Configuration Manager
Hi all, first post on the forums. Was wondering if anyone was having a similar issue. We are slowly testing SCCM and I'm stuck on probably the most important feature, remote control. Whenever I "Start Control" of a workstation,
the remote control agent window shows "Connecting to Host Session" which brings up another prompt that alerts me that "The identity of the computer cannot be verified..." to which I reply "yes" to connect anyway. However
I never connect and in the remnote control agent window shows "Viewer DIconnected".
On the client itself, in the CmRcService.log file, even though it shows that "Session allowed full control" and that I'm an "authorized viewer", later on I see "Disconnecting the connection. An existing connection was forcibly
closed by the remote host. (Error: 80072746: Source Windows". One line below, the log reports "The connection has been terminated". Note I do not have a Firewall Policy enabled and I do not have any stringent virus protection
running. Currently testing on Win7 x86 machine but also happens on WinXP, Server 2008 x64 and x86, etc. Any have a resolution or idea why this is occuring? Any help and/or guidance would be greatly appreciated. Thanks all.Dear J Smith
Please get your account verified by requesting here : Verify
Your Account
In the above link you will have to do the following steps the you need to wait for some hours till you are verified.
Firstly:-
Please reply in that thread and request them to verify your account. An example given below :-)
BR
S. Saurabh
S Saurabh -
Storage Footprint on SC 2012 EP managed clients.
I have a scenario in which we are deploying the SCCM2012 agent and EP as part of a VDI solution. In this solution, we would only be allowed 10GB of use for the user and any changes the user makes to their virtual machine. Because of this we need to manage
space requirements and allocation closely.
I am trying to calculate the storage footprint of Endpoint, specifically the definition files and how the updates folder might bloat over time. If anyone knows of a way to do this, or has anecdotal experience from their own deployments I'd really appreciate
it.
http://support.microsoft.com/kb/977939 - A Support KB on Forefront definition updates. Defines new packages as 40MB for initial “full” install, and 1-15MB for incremental/delta definition updates. When I checked our test installs, the definition update folder
was 200MB for the initial install and 2 days of definition updates which doesn't seem to add up to this KB… too smalll a sample to know what this will look like over a week or a month but it has me nervous.
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx - Blog article, discusses the process for cleaning up old definition files, specifically for the reason we’re concerned
about with the VDI deployment: storage. It appears that this only addresses the repository and does not remove the definitions from the managed client collections. How might we clean up definition files if space becomes an issue?
Again, any feedback appreciated. Thanks in advance!Hi,
I checked our computers with SCEP 2012 agent installed for months. The size of definition updates folders are different.(130MB, 208 MB, 180MB...)
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Please clarify license about server managed and configuration manager client ML system center 2012
Could clarify why managed servers License required ,already we bought the configuration manager client ML License ? We are planing to buy system center operation manager 2012
Hello,
if you wants planing to Monitoring your AD with Exchange Server and you have only one physical Server with for example 2 CPUs and 2 VMs, you need to purchase the System Center Standard 2012 R2 SML for Monitoring your Server environement. However, if
your AD is a datacenter or for example 4 x Windows Server Standard with 8 VMs than, you need to purchase the System Center datacenter SML.
the System Center SML is licensed per physical Server: one license up to two physical CPUs. if you have for 2 physical Hosts with 2 CPUs each, you need to purchase two System Center licenses.
the only difference between Standard and datacenter is only about virtualization rights
for System Center Operation Manager for your Clients Desktop, you need to purchase the System Center Client Management Suite includes: Operation Manager; Services Manager; Data Protection Manager and Orchestrator.
thanks
diramoh -
SCCM 2012 R2 Configuration Manager Client Package - stuck "In Progress"
Hi Team; I’m having 2 issues with SCCM 2012 R2:
Issue 1: I'm having a strange issue with the default XXX00002 package - "Configuration Manager Client Package",
it will not deploy to the Secondary Site DP. The console is saying "In Progress" - below is the output from the
distmgr.log file.
~Package BDC00002 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6032 (0x1790)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00002, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.444+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00002. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~SourceVersion (1) of package BDC00002. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.462+240><thread=6032 (0x1790)>
~Package BDC00003 does not have a preferred sender.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.443+240><thread=6092 (0x17CC)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=BDC00003, Version=1, Status=2301
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.464+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6032 GMTDATE=Mon Mar 17 20:00:23.476 2014
ISTR0="Configuration Manager Client Package" ISTR1="BDC00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="BDC00002"
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.477+240><thread=6032 (0x1790)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.476+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.484+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.476+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.495+240><thread=6032 (0x1790)>
~StoredPkgVersion (1) of package BDC00003. StoredPkgVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.496+240><thread=6092 (0x17CC)>
~SourceVersion (1) of package BDC00003. SourceVersion in database is 1.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.497+240><thread=6092 (0x17CC)>
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=2768 TID=6092 GMTDATE=Mon Mar 17 20:00:23.510 2014
ISTR0="Configuration Manager Client Upgrade Package" ISTR1="BDC00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400
AVAL0="BDC00003" $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.510+240><thread=6092 (0x17CC)>
StateTable::CState::Handle - (2301:1 2014-03-17 20:00:23.510+00:00) >> (0:0 2014-02-28 16:33:45.383+00:00)
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.515+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='8ACCAE01-5079-4FCD-A988-C1CD3004B698' SID=2301 MUF=0 PCNT=2, P1='PRI' P2='2014-03-17 20:00:23.510+00:00' P3='' P4=''
P5='' $$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.526+240><thread=6092 (0x17CC)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\1sfb1dbj.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.571+240><thread=6032 (0x1790)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.572+240><thread=6032 (0x1790)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.574+240><thread=6032 (0x1790)>
CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\abaibh8y.SMX
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.637+240><thread=6092 (0x17CC)>
Successfully send state change notification 8ACCAE01-5079-4FCD-A988-C1CD3004B698
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.683+240><thread=6092 (0x17CC)>
~Exiting package processing thread.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:23.685+240><thread=6092 (0x17CC)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:26.886+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.948+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:27.950+240><thread=4900 (0x1324)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:31.934+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.021+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:33.023+240><thread=4900 (0x1324)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.108+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:00:38.111+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:06:28.094+240><thread=4968 (0x1368)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 16:30:52.271+240><thread=2936 (0xB78)>
Sleep 30 minutes...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.002+240><thread=2936 (0xB78)>
~Used 0 out of 3 allowed processing threads.
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.977+240><thread=4900 (0x1324)>
~Sleep 3600 seconds...
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:01:10.979+240><thread=4900 (0x1324)>
Sleeping for 60 minutes before content cleanup task starts.~
$$<SMS_DISTRIBUTION_MANAGER><03-17-2014 17:06:55.337+240><thread=4968 (0x1368)>
Issue 2: I'm trying to deploy a couple of Packages/Applications using SCCM 2012 R2 running on Win2K8 R2 with no luck, knowing that I could install the packages
on a test VM “in the DataCenter site”, but when trying to deploy the packages to production PC “in the Office Site”,
the status is packages deployment compliance stuck at 0%
Infrastructure:
3 SCCM servers: CAS, PRI & SEC. Both CAS and PRI are in the DataCenter site, and SEC is in the Office site. The office site has several IP subnets.
Boundaries are configured through Forest Discovery “IP Ranges and AD Sites” since that the AD site should contain all the IP subnets that the AD site contains, Boundaries groups are also configured and a site reference
server is configured for each group respectively.
A OU based Collection has been configured that contains 13 PC "the collection contains the PCs that the packages should be installed.
Packages/Applications are configured correctly since that I could successfully deploy the packages to the test VM which is on the same subnet as the CAS and the PRI servers "the DataCenter subnet". The issue
is that I can't deploy the packages to production PCs in the Office subnet!
Firewall rules are configured and applied via GP, and I even turned Windows Firewall off, and still nothing! I tried to manually initiate Computer Policy download via the SCCM GUI and via a script, still no luck!
I tried configuring IP Subnet Boundaries, still no luck!!
Here are the last 2 lines in the LocationServices.log of a client PC at the Office Site:
<![LOG[MPLIST requests are throttled for 00:00:44]LOG]!><time="14:47:00.766+240" date="03-17-2014" component="LocationServices" context="" type="2" thread="5776"
file="lssecurity.cpp:4528"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="14:47:00.777+240" date="03-17-2014" component="LocationServices" context="" type="1"
thread="4884" file="lsad.cpp:770">
And here are the last 4 lines in the ClientLocation.log
<![LOG[Rotating assigned management point, new management point [1] is: BBK-SCCM-PRI.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:04.880+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6311">
<![LOG[Assigned MP changed from <BBK-SCCM-PRI.bbk2310.com> to <BBK-SCCM-PRI.bbk2310.com>.]LOG]!><time="14:49:04.891+240" date="03-17-2014" component="ClientLocation" context="" type="1"
thread="3600" file="lsad.cpp:1532"> <![LOG[Rotating proxy management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState"
Value="0"/></Capabilities>]LOG]!><time="14:49:05.345+240" date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6374">
<![LOG[Rotating local management point, new management point [1] is: BBK-SCCM-SEC.bbk2310.com (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>]LOG]!><time="14:49:05.786+240"
date="03-17-2014" component="ClientLocation" context="" type="1" thread="3600" file="lsad.cpp:6436">
It looks like clients in the Office Site can’t connect to the DP/MP of the Secondary Site server which is also a DP.
While on the PC that the application was installed on I see the folowing in the LocationService.log:
<![LOG[Distribution Point='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSPKG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities>', Signature='http://BBK-SCCM-PRI.bbk2310.com/SMS_DP_SMSSIG$/Content_69547d2a-339f-4ac4-9523-238c79ff8a52.1.tar', ForestTrust='TRUE',]LOG]!><time="14:42:59.506+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="lsutils.cpp:415"> <![LOG[Calling back with locations for location request {144620BC-4BF0-4878-9554-F67D305ECCF8}]LOG]!><time="14:42:59.522+240"
date="03-17-2014" component="LocationServices" context="" type="1" thread="224" file="replylocationsendpoint.cpp:220">
Is there something wrong with the Distribution point on the Secondary Site server?
Please help…
Thanks..Update:
I fixed the issue with the default XXX00002 package - "Configuration Manager Client Package", it will not deploy to the Secondary Site DP. I did that through "Update Distribution Points" option, and after a while the status was 100%.
However; the second issue is still unsolved...
Please help.. -
Configuration issue on two items for system center 2012 config manager
My first issue was at the beginning of the install trying to extend the AD schema for system center 2012 config manager version 7.5.1561.0. The
path is missing for SMSSetup\Bin\x64\ to execute
Extadsch.exe is not on my disc. There is only a x86 and 64 bit folder with no bin.
Second issue when creating configuration manager connector. Error connecting to the database. So i went to my sqlserver and checked the permissions on the account I did notice that there are no smsdbrole_extract role permissions. Did I miss a step somewhere
along the way? On a side not that this is an instance and not under the default place. Also, i am using sql 2008 R2 version.OK, nothing wrong with that per se, but it has nothing to do with ConfigMgr. Also, ConfigMgr is not a "module", it's a distinct product unto itself with its own unique requirements and dependencies that is also architecturally completely different. So,
there's nothing to uninstall to install ConfigMgr. Also, I hope you're not trying to install these products on the same server. That is OK for a small lab environment, but nothing more. Even then, I wouldn't do it since its never something you'd do in production.
As mentioned, each product has its own unique dependencies with no true overlap.
Jason | http://blog.configmgrftw.com -
OSD with Configuration Manager Clients and PKI certifications
My team and I had just set up PKI Certs on our System Center 2012 R2 Server. We want the opportunity to utilize Out Of Band Management, but we also would like to make our OSD available to the following "Only Configuration Manager Clients." I have
done some testing and have found that without PKI enabled we have been able to use this feature. Once we enabled PKI we could only perform OSD through PXE or Boot Media.
Is there a way to have PKI enabled but also allow OSD's to be available through "Only Configuration Manager Clients"?Thanks for the reply, I will relay the info concerning OOB. It is not necessarily a technical problem we are running into, more of an inconvenience. OSD works great as long as you make your TS deployment available through Boot media or PXE. Our end goal
is to create a zero touch environment. To do this I was thinking of making the TS available only configuration manager clients. With PKI I loose that capability and it forces me to use boot media or PXE.
Is there a way to have PKI enabled and still be able to deploy TS with only configuration manager clients, and no other deployment method?
Thank you again.
-
Build and Capture TS fails in "Prepare Configuration Manager Client" task
I have a ConfigMgr 2012 R2 + CU1 I use for Windows 7 deployment.
I have made a "build and Capture" TS in ConfigMgr that I use to build my reference image.
When I run the TS it fails at the "Prepare Configuration Manager Client" step where I get the following error:
The task sequence execution engine failed executing the action (Prepare Configuration Manager Client) in the group (Capture the Reference Machine) with the error code 2147749938
Action output: ... 1 instance(s) of 'SMS_MaintenanceTaskRequests' successful
Successfully reset Registration status flag to "not registered"
Successfully disabled provisioning mode.
Start to cleanup TS policy
getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=80041032 (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,463)
ns.Query(sQuery, &spEnum), HRESULT=80041032 (e:\qfe\nts\sms\framework\tscore\utils.cpp,3666)
End TS policy cleanup
TS::Utility::CleanupPolicyEx(false), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,564)
pCmd->Execute(), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)
Wmi query 'select *from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0x80041032
Failed to delete policies compiled by TaskSequence (0x80041032)
Failed to prepare SMS Client for capture, hr=80041032
Failed to prepare SMS Client for capture, hr=80041032. The operating system reported error 2147942402: The system cannot find the file specified.
If I disable the "Install Software Updates" part of my TS it will run without probems. It installs 154 updates during the build.
I have seen another reference to this problem on this forum but why should the large number of the updates be the reason why the task sequcens cannot prepare the SCCM client for capture.
Sounds to me that it's a BUG :-(
Thomas Forsmark SoerensenI'm glad I'm not the only one running into this. I've been racking my brain for the past few days trying to figure out where I went wrong.
SCCM 2012 R2 CU1
Installation properties in TS: SMSMP=mp.f.q.d.n FSP=mp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp"
Drop Windows 7 WIM that has all the updates Schedule Updates (offline servicing) installed (169 of 277)
Apply several updates offline (the dual-reboot Windows 7 updates among others)
Run Windows Updates more than once to be sure I get everything
Breaks at the preparing client for capture step
Is this:
a bug?
a known issue
something that's just frowned upon for no technical reason?
I'd love to hear from an SCCM guru [at Microsoft] on what the heck is going on here. -
Unable to copy hidden package "Configuration Manager Client Package" to local DP
Content status lists it as successfully distributed to all DPs (including the local site server)
However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
NOTE: It appears to not be any of these causes.
If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
Intializing DP Monitoring Manager... SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
distmgr.log shows the following:
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001" SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Retrying package CDW00001 SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
No action specified for the package CDW00001. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\... SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1 SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Updating package info for package CDW00001 SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001" SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:45 PM 2124 (0x084C)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:50 PM 3784 (0x0EC8)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 1/2/2013 1:29:50 PM 3784 (0x0EC8)Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
http://support.microsoft.com/kb/811833) being enabled?
Nothing special with certificates; I've used the basic stuff for intranet management of clients.
The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
(as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?
Maybe you are looking for
-
Font issue between Reports Designer and Report Output
Hi. I've succesfully migrated several reports from 6i to 10g (10.1.2.0.2) with and without parameter form. However, I have the following font issue: - When report is run from Reports Designer, font is kept. - When report is run from a forms module (t
-
I installed windows successfully but when I inserted the leopard installation disc, the following error occurred: "Windows Installer Installation Wrapper This package requires a newer version of the windows installer. Do you want to update the versio
-
I am trying to upgrade Itunes 10.7 so I can access apps for Iphone 4S. While installing I get an error message indicating theres is a problem with the windows installer package. A program run as part of the setup did not finish as expected. Conta
-
X61 - Vista Business - Client Security Solution Error - There was a problem connecting to the TPM
During startup my x61 has been displaying the following message, 'Client Security Solution' - "There was a problem connecting to the TPM (security device) ont his computer. It is possile that anti-virus or firewall software is blocking the connection
-
"Error while using XML iview" with XML iview template
Our portal platform: HP-UX, WAS 6.40 JAVA, EP 6.0 SP14 We created an XML iview using XML iview template and configured the XML source URL with RSS feeder addresses such as"https://forums.sdn.sap.com/rss/rssmessages.jsp?forumID=41". And then select R