SCCM by Davis

5 ene 2013

SCCM by Davis: “Linux/Mac Clients now available for ConfigMgr 2012” plus 19 more

SCCM by Davis: “Linux/Mac Clients now available for ConfigMgr 2012” plus 19 more

Link to SCCM by Davis

Linux/Mac Clients now available for ConfigMgr 2012

Posted: 04 Jan 2013 06:05 PM PST

Microsoft System Center 2012 Service Pack 1 Configuration Manager - Clients for Additional Operating Systems
http://www.microsoft.com/en-us/download/details.aspx?id=36212

What is supported:

Mac
RedHat Linux
SUSE Linux Enterprise Server
Solaris

Feature Bullet Summary:
Mac Client:
The following Mac versions are supported in this release:
  • Mac OS X 10.6 (Snow Leopard)
  • Mac OS X 10.7 (Lion)

The following scenarios are supported through the Mac client in Microsoft System Center 2012 Configuration Manager SP1:
  • Discovery – Discovers Mac OS X system in Active Directory and through network discovery
  • Hardware Inventory – Provides hardware inventory and auditing of computers running Mac OS X, including a list of installed software similar to add/remove programs for Windows systems.
  • Settings Management – Ensures computers running Mac OS X comply with company policies using scripts and preference list management.
  • Application Deployment – Distributes required software via app model.
  • Software Updates Management – Distributes patches utilizing Software Distribution and Settings management features.

UNIX/Linux Client:
The following UNIX and Linux versions are supported in this release.
  • RHEL Version 6 (x86 & x64)
  • RHEL Version 5 (x86 & x64)
  • RHEL Version 4 (x86 & x64)
  • Solaris Version 10 (x86 & SPARC)
  • Solaris Version 9 (SPARC)
  • SLES Version 11 (x86 & x64)
  • SLES Version 10 SP1 (x86 & x64)
  • SLES Version 9 (x86)
For more information see the link provided at the top of this blog for the full offical post from Microsoft.

System Center 2012 Service Pack 1 – Configuration Manager Component Add-ons and Extensions

Posted: 04 Jan 2013 05:58 PM PST

http://www.microsoft.com/en-us/download/details.aspx?id=36213

Micrososft has released a new toolkit for SC 2012 CM  SP1

The following tools are available:

  • Client Spy - A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on System Center 2012 SP1 Configuration Manager clients.
  • Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on System Center 2012 SP1 Configuration Manager clients.
  • Security Configuration Wizard Template for Microsoft System Center 2012 SP1 Configuration Manager - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required.
  • Send Schedule Tool - A tool used to trigger a schedule on a client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.
  • Power Viewer Tool – A tool to view the status of power management feature on System Center 2012 SP1 Configuration Manager clients.
  • Deployment Monitoring Tool - The Deployment Monitoring Tool is a graphical user interface designed help troubleshoot Applications, Updates, and Baseline deployments on System Center 2012 SP1 Configuration Manager clients. This tool requires System Center 2012 SP1 Configuration Manager or later.
  • Run Metering Summarization Tool - The purpose of this tool is to run the metering summarization task to analyze raw metering data.
  • Role-based Administration Modeling and Auditing Tool – This tool helps administrators to model and audit RBA configurations.
  • Wakeup Spy – This tool shows network traffic and basic information about ConfigMgr wake up client state. This tool requires System Center 2012 SP1 Configuration Manager or later.
  • Content Library Transfer – This tool moves the content library from one drive to another drive.
  • Content Ownership Transfer – This tool re-assigns orphaned packages to an active ConfigMgr site.

#ConfigMgr #SCCM : How to Turn On Verbose, SQL, NAL logging

Posted: 12 Nov 2012 02:52 AM PST

One old topic and old post. There is a great post from Ismail-TS on "logging". I think,

Microsoft System Center 2012 Endpoint Protection Cookbook

Posted: 09 Nov 2012 02:00 PM PST

Recently I had the opportunity to review the Microsoft System Center Endpoint Protection Cookbook fr

Installing SCCM agent on Server 2012 with Orchestrator

Posted: 07 Nov 2012 08:01 PM PST

In this blog post I'm going to document the high level steps to get the SCCM agent (Pre beta 1) on Server 2012, Windows 8 and this can be used also as a secondary method to catch any machines that didn't get the agent installed by client push or WSUS depending on your main deployment method for the client.

Step 1. Create collection in SCCM for clients without an installed agent.

Select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client = 0 or SMS_R_System.Client is null

I also excluded some collections to removed objects that I know should not get agents (exp. Cluster objects and OSX machines that have been joined to the domain)

Step 2. Create a collection for failed objects and excluded this collection from the 1st collection (if you want to try the install more than once, you can modify this)

Step 3. Create a new runbook in orchestrator

clip_image002[4]

The first activity you need is a "Get Collection Members" from the SCCM 2012 IP

clip_image004[4]

The second activity is a .net Script from the system IP that we run the following powershell script

$SCCMServer = "Variable with the SCCM Server Name"

$destServer = "Published data Member Name from Get objects from non Client Collection"

$alive = Test-Connection -ComputerName $destServer -Quiet

if ($alive) {

$destshare = "\\"+ $destServer +"\C$\"

$SCCMshare = "\\"+ $SCCMServer +"\SMS_LH2\Client\"

Copy-Item -Path $SCCMshare -Destination $destshare -Recurse

start-sleep 15

$wsman = New-PSSession -ComputerName $destServer

Invoke-Command -ScriptBlock {cd c:\client; start-process ccmsetup.exe} -Session $wsman

}

else { $poweredoff = $destServer}

clip_image006[4]

clip_image008[4]

The last activity needs to be connected with a custom link

clip_image010[4]

Add the add collection rule activity

clip_image012

 

You can either add a monitor data time at the start of the runbook to check for new clients in the collection or use another scheduling utility.

This works in my environment but may need a few small tweaks since i have not added much error handling.

Hotfix para suporte do Windows 8 no SCCM 2007.

Posted: 07 Nov 2012 07:53 AM PST

Bom dia,

Está disponível uma atualização que adiciona suporte para computadores cliente baseados no Windows 8 no Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2).
Além disso, esta atualização adiciona 8 do Windows e Windows Server 2012 à lista da plataforma com suporte os seguintes recursos:

  • Distribuição de software
  • Gerenciamento de atualizações de software
  • Gerenciamento de configuração desejada (DCM)

Essa atualização também corrige os seguintes problemas:

  • Discovery Data Manager (DDM) não criar solicitações de configuração do cliente (CCRs) para computadores baseados em Windows 8 que são descobertas por meio de descoberta de sistema do Active Directory.
  • Quando o sistema processa um novo perfil de energia, o serviço SMS Agent Host (CcmExec) ou o serviço de Host de provedor de WMI (Wmiprvse. exe) pára inesperadamente.

Link.

Abs!

SCCM 2012 Reporting for dummies: Creating subscriptions

Posted: 07 Nov 2012 07:24 AM PST

Hey gang, so we've come all the way to my last post on my Reporting for Dummies series. We've now got all these lovely reports created and showing exactly what we want when we want to see them. But dammit, I want an easier way of getting the reports.

That's where subscriptions come in. Yes, SCCM 2012 has a nice little feature called subscriptions that can help compile up the reports you want and have them saved onto a file share or even sent straight to your inbox on a regular basis! How neat is that? You can set up subscriptions for yourself, others or groups of people as you would expect.

So for us to set up a subscription, we must first go to the report we want to subscribe to. In this tutorial, we'll create a subscription to "Computers with low memory (less than or equal to specified MB)". Expand the Reporting and Reports node and click on the "Hardware – Memory" node.

After the reports appear, right click on "Computers with low memory (less than or equal to specified MB)" and click "Create Subscription".

A "Create Subscription" wizard should appear asking you to specify the delivery method you wish for the report once the subscription is created. We'll be creating a file share where the reports will be written to for this example but if you have an exchange connector configured, you could have the reports emailed out. Fill out all the fields as required.  You'll need to specify a username and password for the subscription to be able to access the file share.

Click Next once you are happy with your settings. You'll now be able to specify the schedule and frequency of how the reports are delivered to your file share. Configure to your desires and click Next.

If you had chosen a report that has parameters in order to run then you will be prompted for their configurations in the next screen. Since we have chosen a report that does, we'll have to enter in the amount of memory we want to use as the parameter for the report. Fill out the fields and click Next.

Review the summary of your subscription for the report and click Next to create the subscription.

Once the report has created, click close and voila! You now have a new report subscription! You can view all the subscriptions you have created by viewing the Subscriptions node under the Reporting node.

You can review the status of the subscription to see if there are any issues (such as incorrect credentials or the last report created) in the Status field of in the Subscriptions Node.

~P~

SCCM 2012: You cannot install SCCM Client to a French version of Windows 7

Posted: 05 Nov 2012 11:04 AM PST

Microsoft published a hotfix for abovementioned problem: http://support.microsoft.com/kb/2737681

SCCM: Updates cannot be deployed due to WSUS improvements

Posted: 05 Nov 2012 11:00 AM PST

Recently Microsoft published a WSUS update to support Windows 8 and Server 2012.  A lot of updates must be re-downloaded after that, otherwise they cannot be deployed.

Here is the way to fix it:

SCCM 2007: Apply hotfix described in http://support.microsoft.com/kb/2783466

 

http://blogs.technet.com/b/configurationmgr/archive/2012/11/02/support-tip-configuration-manager-client-deployment-packages-may-not-deploy-due-to-updates-having-to-be-re-downloaded.aspx

#ConfigMgr #SCCM 2007 :: How to : Change Parent Site of a Primary Server and Simplify Hierarchy :: Part 2

Posted: 03 Nov 2012 06:44 PM PDT

This post is continuation of my previous post "How to : Change Parent Site of a Primary Server and S

#ConfigMgr #SCCM 2007 :: How to : Change Parent Site of a Primary Server and Simplify Hierarchy :: Part 1

Posted: 03 Nov 2012 04:09 AM PDT

Through this post, I'm trying to perform impact analysis of changing parent site of a primary site (

Preparing for SCCM 2012 Client Upgrade

Posted: 02 Nov 2012 01:02 PM PDT

Thought I would throw this gotcha out in case anyone else runs into this.

The scenario:  Installing SCCM 2012 Client Prerequisites prior to your upgrade.

After updating my WIM image with all the prereqs (that are applicable) from the SCCM 2012 Client directory, I then did a test deployment against my existing SCCM 2007 Infrastructure.  My Task Sequence step that installs FEP 2010 failed. (Fep-ApplyPolicy-WCOMPUTERNAME.log shows "ERROR FEP Client Installation failed.  Error Code 0x8004FF52″

Upon further investigation it was the SCCM 2012 prerq "Windows Firewall Configuration Provider" causing the fail.

Specifically the following message is displayed if you run the install with the GUI:

"One or more programs on your computer conflict with Forefront Endpoint Protection.  To Install Forefront Endpoint Protection, you must remove the following programs and then run the installation wizard again:

Windows Firewall Configuration Provider"

So long story short, do not pre-deploy this update prior to your SCCM 2012 client upgrade.  ;-)

So far the other prereqs seem to be fine and highly recommend you deploy these prior to your client upgrade otherwise the client install can be VERY lengthy. Especially .NET Framework 4.0.

*A side note, in my environment I also added Silverlight 5 to my image and will be deploying that out to all existing clients with the other prereqs as well (excluding Windows Firewall Configuration Provider of course!).  Silverlight 4 is included with SCCM 2012 RTM Client however SCCM 2012 SP1 will require Silverlight 5 and its backwards compatible with SCCM RTM.

SCCM 2012 Application Catalog Website: “Make sure WCF is activated” and .NET Unhandled Exceptions

Posted: 02 Nov 2012 12:42 PM PDT

In my brand new environment I am happily installing the marvelous SCCM features when from nowhere I have difficulty adding the application catalog website role to my single server standalone primary site. What in the world. I see two repeating errors:

Site Component Manager failed to install component

The WCF is not activated

Solution: Make sure the WCF is activated.

Screen Shot 2012-11-02 at 10.02.10 AM

Screen Shot 2012-11-02 at 10.05.33 AM

I start looking around and realize that I've forgotten to include the WCF service as a part of the .NET framework installation.

Screen Shot 2012-11-02 at 10.03.22 AM

I install the feature and both subfeatures, then open the CM service manager and restart the SMS_SITE_COMPONENT_MANAGER service so that the installation will immediately restart, or I could have waited 60 minutes and viola!

Screen Shot 2012-11-02 at 10.58.46 AM

Success!

image

Or so I thought….after it was successfully installed I was getting unhandled exception .NET errors when attempting to browse to the CMApplicationCatalog website.

Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.

Screen Shot 2012-11-02 at 11.21.37 AM

DOH! I forgot to register the .NET Framework 4.0 components like a big fool. Props to Russ Rimmerman for posting up.

I ran this command: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i –enable, which didn't work for me, it just kept spitting out the help message, which one other person complained of in the above Russ Rimmerman post, even when drilling into the directory with the command prompt. After fiddling around with that for a while I started getting this error: aspnet_regiis.exe is not a valid Win32 application.

Screen Shot 2012-11-02 at 12.53.11 PM

So I performed a repair of the .NET framework 4.0 from the Programs and Applications in control panel, then performed the following command line, which worked:

Screen Shot 2012-11-02 at 12.59.14 PM

Screen Shot 2012-11-02 at 12.59.28 PM

Annnnnd it worked! Except, then I was getting an authentication problem where no matter what credentials I used I couldn't log in. Peachy.

Screen Shot 2012-11-02 at 1.07.29 PM

So then  I found this article:

http://blogs.technet.com/b/michaelgriswold/archive/2012/06/08/application-catalog-not-working-for-everyone.aspx

Where they suggested to once again, remove the roles from the server, perform aspnet_regiis.exe /iru, then reinstall the roles.

and FINALLY 8 years later we have a working Application Catalog. And now I need a nap.

Screen Shot 2012-11-02 at 3.38.29 PM

Moral of the story:

  1. Ensure that .NET WCF is installed as a prereq
  2. Ensure that .NET 4.0 is registered with IIS (You can do this by installing .NET 4.0 before the IIS roles, or via the command line afterwards)
  3. Ensure that your installation of .NET 4.0 is good.

Prevent Old Computers from Being Discovered in AD by SCCM 2012

Posted: 02 Nov 2012 06:45 AM PDT

What's that you say? You hate it that system discovery in SCCM brings in ancient systems that don't exist, nobody cared to clean up and still resolve in DNS?

Have we got a deal for you! One of my favorite new options in the system discovery for SCCM 2012 allows you to choose to discover only computers that have logged onto the domain in the past X days, also only discover computers that have updated their computer account password in the past X days. This feature is so totally awesome, because it will keep your database clear of non-important non-client installed records that somehow still have DNS records. This will be particularly valuable for those organizations which don't clean out DNS and AD for their servers as a part of a proper decommission process. It's Friday, it's a good day. Carry on tech world!

Screen Shot 2012-11-02 at 9.37.43 AM

Doceri Silent Install

Posted: 01 Nov 2012 11:34 AM PDT

I swear I spend way too much time digging inside of installers trying to figure out how to install a piece of software silently.  Software manufacturers should be required to include silent install switches into all of their installers, or use msi packages!

Anyway, so today I got an email from Henry (that's my boss…more on him later) asking to package up Doceri and make it available for users to self-install (using run advertised programs in SCCM 2007).  Doceri is some sort of laptop/ipad integration program, and allows an ipad to be used as an interactive whiteboard.  So I download from their website and all I have is a single exe installer.  After trying a million combinations I finally got one to work:

Doceri_Desktop_setup_2_0_9.exe /verysilent /norestart

The /verysilent and /norestart switches are common inside of Inno installers (http://www.jrsoftware.org).  The problem is getting the site license code we purchased inserted into the program.  I'm thinking that is going to have to be done manually! :-(

Rod Trent wrote a new post, Webservices and Console Extensions for SCCM 2012 source code released to the community

Posted: 04 Jan 2013 03:47 PM PST

ThumbnailIn the System Center Configuration Manager 2012 group today, Rafal Pe announced that he is releasing the source code for his Webservices and Console Extensions for SCCM 2012 to the community.  He is releasing it […]

Comments: 0

Rafal Pe posted an update in the group Operating System Deployment: Hey, I have just released source code for Webservices and […]

Posted: 04 Jan 2013 01:58 PM PST

Hey,
I have just released source code for Webservices and console extensions for SCCM 2012 ! I strongly believe that we can make this solution much better together

Code – Source code for Webservices and SCCM console extensions available
Hey,

Comments: 0

Rafal Pe posted an update in the group System Center Configuration Manager 2012: Hey, I have just released source code for Webservices and […]

Posted: 04 Jan 2013 01:58 PM PST

Hey,
I have just released source code for Webservices and console extensions for SCCM 2012 ! I strongly believe that we can make this solution much better together

Code – Source code for Webservices and SCCM console extensions available
Hey,

Comments: 0

Stephen Proto became a registered member

Posted: 04 Jan 2013 01:27 PM PST

Comments: 0

Nicolas Coch joined the group System Center Service Manager

Posted: 04 Jan 2013 01:15 PM PST

Comments: 0
by to

No hay comentarios:

Publicar un comentario

Suscribirse a: Enviar comentarios (Atom)

SCCM by Davis

Cargando...