SCCM by Davis

24 mar 2013

SCCM by Davis: “Deodato became a registered member” plus 19 more

SCCM by Davis: “Deodato became a registered member” plus 19 more

Link to SCCM by Davis

Deodato became a registered member

Posted: 24 Mar 2013 12:23 AM PDT

Comments: 0

SQL Query - Last Heartbeat updated

Posted: 07 Feb 2013 05:17 AM PST

This was more difficult than I thought it should be.
Machine, memory and last hardware inventory was easy.  It was fairly easy to add the last Heartbeat but for machines that roam each site visited would give a last heartbeat.

The embedded query that filters these out was the part that gave me the most grief.  If there is a better way of doing it let me know.

SQL —–
SELECT TOP (100) PERCENT SYS.Netbios_Name0 AS [Computer Name], SYS.User_Name0 AS [User], SYS.Operating_System_Name_and0 AS OS,
MEM.TotalPhysicalMemory0 / 1024 AS [RAM MB], dbo.v_GS_WORKSTATION_STATUS.LastHWScan, dbo.v_AgentDiscoveries.AgentSite AS [Last Seen Site],
dbo.v_AgentDiscoveries.AgentTime AS [Last Heartbeat]
FROM dbo.v_R_System AS SYS INNER JOIN
dbo.v_GS_X86_PC_MEMORY AS MEM ON SYS.ResourceID = MEM.ResourceID INNER JOIN
dbo.v_GS_WORKSTATION_STATUS ON SYS.ResourceID = dbo.v_GS_WORKSTATION_STATUS.ResourceID INNER JOIN
dbo.v_AgentDiscoveries ON dbo.v_AgentDiscoveries.ResourceId = SYS.ResourceID INNER JOIN
(SELECT ResourceId, AgentName, MAX(AgentTime) AS Expr1
FROM dbo.v_AgentDiscoveries AS v_AgentDiscoveries_1
WHERE (AgentName = 'Heartbeat Discovery')
GROUP BY ResourceId, AgentName) AS derivedtbl_1 ON dbo.v_AgentDiscoveries.ResourceId = derivedtbl_1.ResourceId AND
dbo.v_AgentDiscoveries.AgentTime = derivedtbl_1.Expr1
WHERE (dbo.v_AgentDiscoveries.AgentName = 'Heartbeat Discovery') AND (MEM.TotalPhysicalMemory0 / 1024 <= 1700) AND
(SYS.Operating_System_Name_and0 LIKE '%Workstation 6.1′) AND (NOT (SYS.Netbios_Name0 LIKE '%TEST%')) AND (NOT (SYS.Netbios_Name0 LIKE '%BDP%'))
ORDER BY [Computer Name], [Last Heartbeat] DESC

Sistemas Operacionais suportados para cada componente do SC 2012 SP1.

Posted: 07 Feb 2013 04:10 AM PST

Olá pessoal,

Segue uma tabela de todos os componentes do System Center 2012 SP1 com a versão do Windows Server suportado.

System Center 2012 SP1 server-side component

Windows Server 2008 R2 SP1 Standard, Enterprise, Datacenter

Windows Server 2012 Standard, Datacenter

Windows Server 2012 Core

App Controller Server
  •  
  •  
  
DPM Database Server
DPM Remote Administrator
DPM Server
Operations Manager Management Server
Operations Manager Data Warehouse
Operations Manager Gateway Server
Operations Manager Operational Database
Operations Manager Reporting Server
Orchestrator Management Server

 
Orchestrator Runbook Server
Orchestrator Web Service
Service Manager Management Server
Service Manager Data Warehouse Management Server
Service Manager Database or Data Warehouse Database
Service ManagerSelf-Service Portal (SharePoint Server and Web Content Server
Virtual Machine Manager Management Server
Virtual Machine Manager Virtual Machine Hosts
Virtual Machine Manager PXE Server
Virtual Machine Manager Update Server
Virtual Machine Manager Library
Service Provider Foundation API Web Server

Abs!

SCCM 2012 a local perspective

Posted: 06 Feb 2013 03:05 PM PST

Ok,

So I've been working with desktops for the last 5 years, the last biggest change we had was moving from PQI images to Microsoft WIM images using WAIK and MDT. A major leap forwards that took most of our service desk by surprise that we could suddenly deliver desktops in a more managed fashion far quicker and easier than before.

Nothing was particularly wrong with that setup, but management, as always, now wanted to deploy applications  in an automated fashion and get reports back about what applications were where. So after many meetings and much arguing we finally decided to try and get SCCM into our environment.

Now up to now I've never really touched Config Manager , though back in my service desk days we di use SMS as it was called back then. So I was unsure exactly what would be required and just how much it would cost in time and money to get it working the way mgmt. seemed to want.

So we've had SCCM 2012 installed for us by a trusted Microsoft partner, everything seemed to go rather well, part of the configuration we wanted was:-

: OS deployment

:Software deployment

:Hardware and software inventory

:Remote control

:Management reports

Now as luck, would or would not have it, as part of the final technical handover the 3rd party mentioned that service pack 1 was available and we should consider installing it to get over some known bugs with the base version of SCCM 2012.

So one quick change meeting later and I'm in the build dungeon with a colleague staring at a laptop screen going through what the 3rd party had told us would be , click next, next then finish and that should be it.

Let me tell you from todays experience this is NOT the case.

To install SP1 there are several pre-reqs you have to meet

Un-installing WAIK, and installing the new APK, which also means we need to create new builds

Upgrading WSUS

Running a pre-req checker

We started at roughly 10:00 am this morning, and by mid-day had that well known Microsoft sinking feeling that all was not going well, we hadn't got as far as step 2.

After lunch, where not for one second did we consider some light alcoholic refreshment, we again set about getting SCCM SP1 installed.

We made a few steps in the right direction but our biggest bug bear , the final pre -req was the account used to create the original SQL database, without knowing that account we were sunk. Our SQL Admin was very helpful .

"Do you know the Account used" he said

" No" I replied," if I did I wouldn't ring you"

Several frantic phone calls later and we were speaking to the technician from the 3rd party who had installed it for us, he confirmed the account and password and also confirmed that he had provided that information back to the project manager. I made a mental note to throttle the PM, and thanking the technician, delved hesitantly into logging on with the golden account.

What a difference it made, errors that had been there before just seemed to melt away, everything started to look brighter, launching the SP1 upgrade, I hesitated over the setup.exe and double clicked it.

What followed was probably the quietest most uneventful upgrade I've ever experienced, it knew it was an upgrade, we just put in our licence key, confirmed  a few basic details, thankfully by this team our PM had emerged from some dark meeting place and had handed the build notes the technician had written to us. Better late than never, but I was still convinced a good throttling was in order at some point.

The upgrade screen just happily kept us up to date with what it was doing using just two icons, either the classic green tick, for something completed, or a confusing re-cycling logo, which I guess meant it was thinking about something or trashing the server.

Finally after 35 minutes the upgrade was done, or at least that is what the prompt has me believe. Neatly beneath the row of green ticks was a friendly innocuous message saying we could close the upgrade window but there were some post upgrade task we may want to do. The only post upgrade task on my mind at that point was glad that's over time for home. However , being a thorough kind of guy I thought I should at least fire up the console.

Big mistake,

I got that wonderful, cannot connect to your site screen.

Several words came to mind none of which are printable.

I left work for the evening fuming, swearing , and cursing SP1.

However all was not lost, in a moment of late night calmness, I let google be my guide, issues with SP1 upgrade for SCCM, ok, plenty of hits there, issues connecting afterSP1 upgrade, still lots of hits , but the top result looked promising. It was someone who had upgraded a pre-release SCCM install with the Beta SP1. they had had the same issue, and the solution was so simple I swore again, which after today has been a recurring theme.

For some reason , either by poor Microsoft design or by our dumb luck the console had not upgraded, it separate. I quickly dialled back into work and found the console upgrade, 5 minutes later SCCM was back to life, I was happy, and definitely not looking forwards to SP2

Lessons learnt oh yes

Check for initial install notes

Check again for install notes

Beat up the PM if they claim there are no install notes

Use the account it was initially installed under,

Run every pre-req check

Ensure every KB is installed that should be

Back everything up

Kiss your loved ones goodbye as it may be a while before you see them again, then dive into the upgrade.

Next on the list of task sis to get the new client pushed out, and create a application package for the console.

Till them happy SCCM,ing

Tool to Monitor Software Updates Deployment on Servers via SCCM 2012

Posted: 06 Feb 2013 11:51 AM PST

Roger Zander the author of SCCM Client Center tool has released a new tool designed to help you during deployment of software updates. The tool gets a brief overview of status of the servers during patch deployment – Reboot pending, Updates missing, Install running, Users online and etc. The only downside of the tool is that it uses 4 of the 5 default WinRM connections to a server but you can change that with group policy. Keep in mind that no support or warranties are also provided. Requirements of the tool and download link you can find here.

Using Client Push Installation on WORKGROUP systems with ConfigMgr 2012

Posted: 03 Feb 2013 06:08 AM PST

This week my post will be about using the Client Push Installation on WORKGROUP systems. We all know that a manual installation will work on WORKGROUP systems, but wouldn't it be easier to just use the Client Push Installation? In my opinion the answer would be, YES! And as long as the WORKGROUP systems are configured the same, the configuration is actually quite easy.

Prerequisites

Before it is possible to use the Client Push Installation on WORKGROUP systems, there are a few things to keep in mind. The following points are a prerequisite and are not further explained in this post:

  • The FQDN of the Management Point system can be resolved on the WORKGROUP system.
  • The Network Discovery is enabled to find the WORKGROUP systems.
  • The Client Push Installation Account has administrative rights.

Configuration

Now let's start with the configuration! It is possible to configure the Client Push Installation for WORKGROUP systems, because it is possible to use a variable in the accounts used for a Client Push Installation. So this makes it possible to also configure local accounts. To configure Client Push Installation for WORKGROUP systems follow, at least, the following steps:

  • CPIP_AccountsNavigate to Administration > Overview > Site Configuration > Sites and select the site.
  • In the Home tab, click Settings > Client Installation Settings > Client Push Installation and the Client Push Installation Properties will show.
  • On the Accounts tab, click <YellowStar> > New Account and the Windows user Account popup will show.
  • Fill in with User name %COMPUTERNAME%<USERNAME> with the corresponding password in the appropriate fields and click OK.
  • On the Installation Properties tab, fill in as Installation Properties, at least, SMSSITECODE=XXX SMSMP=<FQDN_MP>. 

Results

After the configuration is done it is time to take a look at the results. The best place to look at the results is in the CCM.log after a Client Push Installation on a WORKGROUP system is performed. This log shows that it first tried my domain credentials. After the domain credentials failed it used the local credentials, which are configured via the COMPUTERNAME variable, as second. After the installation was successful the client will show up in the console as an active client with as Domain WORKGROUP.CCMLogWGSystem

Configuration Baseline for Veeam MP OpsMgr agent Config

Posted: 02 Feb 2013 10:07 AM PST

In preparing for the upgrade to SP1 for SCOM I decided to finally put in some alerting and simi-auto resolution to the settings for Veeam KB1036 that needs the SCOM agent reconfigured after every patch to the SCOM agent.

Issue: When the health service agent is upgraded with a CU/SP patch it stops reporting into the management server, this triggers a Health service alert but doesn't directly tell everyone that we also just lost all of our monitoring into ESX.

My goal is to resolve this with SCOM monitors for the registry values, a SCORCH runbook that can on demand trigger the SCCM baseline to check for compliance then restart the Health Service.

The manual fix for this KB

Manual configuration of the agent

To configure the agent manually, it is necessary to create/change certain keys in the registry on the VEM machine.

  1. The OpsMgr Agent queue, or cache DB, has to be updated by modifying Version Store Size
  2. HKLM\System\CurrentControlSet\Services\HealthService\Parameters\Persistence Version Store Maximum value should be set to 12800 decimal (equates to 200MB)
  3. The value for Persistence Cache Maximum is found in HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\ and needs set to 102400 (decimal)
  4. A new DWORD value has to be created and named "State Queue Items" in HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters. The new value needs set to 20480 (decimal)
  5. The value for MaximumQueueSizeKb needs is found in  HKLM\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\ Management Groups\<ManagementGroupName> and needs set to 204800 (decimal)
  6. When the registry changes are complete, restart Health Service.If the OpsMgr agent on any Collector server is repaired or reinstalled, then the above task should be run again.

Download the Compliance baseline

Microsoft - Security Compliance Manager 3.0 (SCM) has been released

Posted: 01 Feb 2013 04:04 PM PST

Microsoft has released the Security Compliance Manager 3.0 (SCM). This version includes support for Windows Server 2012, Windows 8, and Internet Explorer 10.

SCM enables you to quickly configure and manage computers and your private cloud using Group Policy and Microsoft System Center Configuration Manager. It provides ready-to-deploy policies and DCM configuration packs based on Microsoft Security Guide recommendations and industry best practices, allowing you to easily manage configuration drift, and address compliance requirements for Windows operating systems and Microsoft applications.

Basically in SCM 3.0 you can use predefined baselines, customize them or create completely new ones. Then you can export it from SCM 3.0 and apply it using an Active Directory GPO. To do this, create a new GPO in Group Policy Management, right click the GPO, import settings and complete the wizard.

You can also export existing GPO and then import it into SCM 3.0 and compare the differences.

[SCCM 2012] Task Sequence Hangs on Install Package During OSD (part 2)

Posted: 01 Feb 2013 11:11 AM PST

So, in my previous post on the issue, I described a complicated series of hotfixes and WMI rebuild scripts which fix this serious issue. After a whole lot of trial and error, I recently found an easier workaround.

The Problem

Task sequences hang indefinitely on the 'Install Package' task sequence action.

The Solution

  1. In the 'Apply Network Settings' action, join a workgroup instead of a domain.
  2. Add a 'Join Domain' action later in the task sequence, but before any 'Install Software Updates' actions.

I have no idea why this works :( . However, it really does seem to work for me at least. Yay!

 

 

Microsoft Systems Center Configuration Manager (SCCM) - The monster that can destroy your whole infrastructure

Posted: 31 Jan 2013 03:11 PM PST

some notes on SCCM

http://www.innovative-sol.com/

-25.274398 133.775136

SCCM collection query for NIC's with an error

Posted: 31 Jan 2013 10:07 AM PST

So here's the scenario, you've been told that there are machines showing a network adapt

Paul Byrd joined the group Microsoft Management Summit

Posted: 23 Mar 2013 06:27 PM PDT

Comments: 0

Paul Byrd joined the group System Center Operations Manager

Posted: 23 Mar 2013 06:27 PM PDT

Comments: 0

Paul Byrd joined the group Configuration Manager Queries, Reports, and MOFs

Posted: 23 Mar 2013 06:26 PM PDT

Comments: 0

Paul Byrd joined the group SCCM Right-click tools

Posted: 23 Mar 2013 06:26 PM PDT

Comments: 0

Paul Byrd replied to the forum topic Why do I need to instal a Secondary Site in SCCM 2012 in the group System Center Suite 2012

Posted: 23 Mar 2013 06:23 PM PDT

That depends on a lot of factors. What is you WAN utilization? Do you have client-server apps speaking across it? Do you employ split-tunneling at the Canadian site? What is your expected growth at that site over […]

Comments: 0

Paul Byrd joined the group System Center Suite 2012

Posted: 23 Mar 2013 06:23 PM PDT

Comments: 0

Paul Byrd joined the group System Center Configuration Manager 2012

Posted: 23 Mar 2013 05:37 PM PDT

Comments: 0

April Cook posted an update in the group New England Area SMS User Group (NEASMSUG): Our next Meeting is Tuesday 3/26 at Tech Target, Newton, […]

Posted: 23 Mar 2013 04:39 PM PDT

Our next Meeting is Tuesday 3/26 at Tech Target, Newton, Ma.
Jeff Gilbert will be presenting the overall MDOP portfolio and see it tied into CM12. Come see pretty much everything MDOP installed in his demo, with the main technologies of CM12, App-V, UE-V, and AGPM.
See link for additional information.

NEASMSUG Meeting March 26. 2013 - Eventbrite
Don't leave or refresh, you may lose your spot!

Comments: 0

Rod Trent posted an update in the group System Center Configuration Manager 2012: CU1 for ConfigMgr 2012 SP1 Released, 18 Fixes, New PowerShell Cmdlets

Posted: 23 Mar 2013 02:50 PM PDT
by to

No hay comentarios:

Publicar un comentario

Suscribirse a: Enviar comentarios (Atom)

SCCM by Davis

Cargando...