0

0

Thanks Stefan! Yes if you put the $Data/Context/SampleValue$ in your alert description it should show you the last sampled vale.

0

0

Esker, it would be awesome if you can compile a step-by-step guide. Pete created some guides too but SNMP monitoring has it's pains and I guess there's always room for more guides... cheers, Stefan

0

0

Hi Oskar, first of all: great job on debugging this - and sharing your findings with us. Secondly, are you saying that changing $Data/Context/Value$ to $Data/Context/SampleValue$ in the alert description will put the last sampled value in the alert description? cheers, Stefan

0

0

the registry in the RMS under key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0" contains the following sections: Config Service DAL Machine Settings Modules MOMBins Registration SDK Service Server Management Groups Setup but no "Agent Management Goups" subkey. should i be adding one and how? thanks!

0

0

I am gettting the same warning message on RMS. it's complaining that it can't find anything at "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\MGGroup\AD Cache\Primary SCP Info\Service DNS Name" However, i found out that the key HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\ does not contain any Agent Management Groups sub sections AT ALL... can some one please help me - have i missed to make any entries here or what?

0

0

Hi all, We have a Server 2008 R1 with SCCM 2007 R2 SP2 w/ WS Trans Mgmt installed and configrued. All is well and he have multiple AMT provisioned Windows XP SP3 systems running on Lenovo T400 AMT 4.1.3 firmware. The issue we are having is with Windows 7 clients. The status that is showing up in SCCM is Not Supported and the logs for provisioing are below. I have bolded the item i think is the culprit. The only option available, aside from divorcing the client from the site, is to in-band provision this machine via the ConfigMgr Client Agent. The oobmgmt.log on the client contains only success messages with nothing to indicate any problem. The AMT, SOL / ME Drivers were all installed correctly on the Windows 7 machine. The hash is also verified below as being in the ME BIOS. After much review, i stumbled upon a document from technet stating that In-Band Provisioning via the SCCM SP2 agent is NOT SUPPORTED for Windows 7. The article can be reached here (Scroll down to the section

0

0

For PXE boot functionality you will need a PXE server as MDT does not contain one of its own. The obvious choice and the one that MDT was designed for is WDS, but that's not a strict requirement. WDS is part of Windows Server 2003/2008/2008 R2 so that shouldn't be an obstacle for most folks.

0

0

Jason, I think there is still one point of confusion here. Can PXE boot OSD be performed with MDT alone? Do we need WDS or ConfigMgr to deliver the images created with MDT 2010?

0

0

no, no errors indicating anything but not being able to get a new configuration.

0

0

this seems to have worked. why, i'm not sure why. but it did! New configuration became active. Management group "SCOM PROD", configuration id:"4B 83 83 0A B3 E0 AF A3 50 DA C2 4A 0C 7C 95 5E 87 36 73 5F ".