Jump to content


catsky

Established Members
  • Posts

    4
  • Joined

  • Last visited

catsky's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. yes, indeed, SCOM has different version for different language. However, I hardly find the language tag or key in registry to indicated which version is installed. Could anyone have further information? very appreciated.
  2. Hi, All I has installed SCOM 2012 on my Server. How could I tell which language version of SCOM has been installed from registry? Thanks. I look through the following reg path, can't find any language related key or values. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager
  3. We face an issue when do the OSD OEM integration with SCCM 2012 SP1 beta. In task sequence editor, we add our customized step action control, and follow the step as MSDN indicated:http://msdn.microsoft.com/en-us/library/cc143499.aspx . We want to active the "apply" button in task sequence editor by using the API SetDirtyFlag(true) or Dirty = true when things changed in our action control. However, "apply" button is not enabled after call this method. We use the same logic to perform this task, and no issues happened on SCCM 2007 R2 or SCCM2012. SCCM2012SP1beta has this kind of issue, but SCCM2007R2/2012 don't. Env: windows2008r2 + SCCM2012SP1 beta Steps to Reproduce: (steps could be found on MSDN http://msdn.microsoft.com/en-us/library/cc143499.aspx ) 1. find the required dll under C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin on SCCM2012SP beta server, and reference these assemblies in my own project ---assemblies list---- AdminUI.Common.dll AdminUI.DialogFoundation.dll AdminUI.OsdCommon.dll AdminUI.TaskSequenceEditor.dll AdminUI.WqlQueryEngine.dll Microsoft.ConfigurationManagement.ApplicationManagement.dll Microsoft.ConfigurationManagement.ApplicationManagement.Extender.dll Microsoft.ConfigurationManagement.DialogFramework.dll Microsoft.ConfigurationManagement.exe Microsoft.ConfigurationManagement.exe.config Microsoft.ConfigurationManagement.ManagementProvider.dll ------------------------ 2. add event handler to my customized action control, e.g. for a text field, add an event handler once content changed. In the handler, set dirty flag by leverage the API "Microsoft.ConfigurationManagement.AdminConsole.SmsPageControl.SetDirtyFlag(bool" to active the "apply" button as we always do. Since this method is deprecated in SP1 dll, we also try set "Dirty" property to "true" as indicated. However, neither of them succeed to enable the "apply" button ---code--- SetDirtyFlag(true); //Dirty = true; 3. however the "apply" button doesn't active at all. if we click "ok" button, the changes doesn't save either. the user will not be able to save the any changes in my customized action control. It will be very annoying. So it is a must fix defect.
  4. Hi, all In version of SCCM 2012, We just to check the register path like below, it works as we expected. //if it is a primary site. the register path exists GetSafeRegistryStringValue("HKEY_LOCAL_MACHINE", @"SOFTWARE\Microsoft\SMS\Setup", "Installation Directory") //if it is a console only. after above register path check fail, we need to verify the following. If exists, it should be a console GetSafeRegistryStringValue("HKEY_LOCAL_MACHINE", @"SOFTWARE\Microsoft\ConfigMgr10\Setup", "UI Installation Directory") but in the version of SCCM 2012 SP1 beta, when we check on a console only server, we find the following path exists!! As we expected, it should not be exist on a console only server, but in primary server. GetSafeRegistryStringValue("HKEY_LOCAL_MACHINE", @"SOFTWARE\Microsoft\SMS\Setup", "Installation Directory") Could anyone help me to figure out how could I check the register path to tell which is SCCM server and which is just a console server?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.