SCCM by Davis

28 mar 2013

SCCM by Davis: “Tom Lundqvist joined the group SCCM Right-click tools” plus 19 more

SCCM by Davis: “Tom Lundqvist joined the group SCCM Right-click tools” plus 19 more

Link to SCCM by Davis

Tom Lundqvist joined the group SCCM Right-click tools

Posted: 28 Mar 2013 01:16 AM PDT

Comments: 0

Tom Lundqvist became a registered member

Posted: 28 Mar 2013 01:15 AM PDT

Comments: 0

ChNaidu became a registered member

Posted: 28 Mar 2013 12:56 AM PDT

Comments: 0

Target task sequences to a specific machine using Computer Association in SCCM 2007

Posted: 15 Feb 2013 12:33 PM PST

I do the majority of my build-testing on virtual machines. I find it more convenient and quicker than using a physical machine. From time to time, I need to test something new in my build task sequences. Normally, I create a new virtual machine for each task sequence test. Since I create new virtual machines, they are not in the SCCM database and considered unknown machines. In production, I have my bare metal task sequence advertised to the All Unknown Computers collection. To avoid affecting production and also to not make a test task sequence available in the normal build process, I do not advertise any test task sequences to the All Unknown Computers collection. I create a test collection and advertise to it. This allows me to target my test task sequence to a specific virtual machine without affecting any other machines or the normal build process. Below is an example of how I tested the Install Language Pack Offline step.

Steps

  1. Duplicated my existing bare metal task sequences.
  2. Added a new step to duplicated task sequence to install the French language pack offline.
  3. Created a new collection. (Example in slides – Microsoft Windows 7 Enterprise x64 – Offline Language Pack.
  4. Advertised my test task sequence to the Microsoft Windows 7 Enterprise x64 – Offline Language Pack collection.
  5. Booted my test machine from my OSD boot media.
  6. Clicked Configure on the Welcome to Task Sequence wizard.
  7. Copied down the Physical Address listed.
  8. Expanded Operating System Deployment in the SCCM admin console.
  9. Right-clicked Computer Association and selected Import Computer Information.
  10. Selected Import single computer and clicked Next..
  11. In the computer name field, I typed in FRTest.
  12. In the MAC address field, I typed in the MAC address I got in step 7 and clicked Next.
  13. Clicked Next on the Data Preview screen.
  14. In the Choose Target Collection screen, I selected Add computers to the following collection.
  15. In the Collection field, I typed the name of the collection I created in step 3.
  16. Clicked Next.
  17. Clicked Close.
  18. Computer association has been created.

 

With the computer association created, I can now boot my  virtual machine up. The test task sequence is now available to it.

 

This slideshow requires JavaScript.

#SC2012 consultant available with #SCCM 2012, #SCVMM & #Hyper-V

Posted: 15 Feb 2013 03:43 AM PST

Contact me for details of this System Centre Consultant and CV.

Regards

Neil Mills

MillsHill

01803 321233

SCCM 2012 SP1 Site Backup

Posted: 12 Feb 2013 10:47 PM PST

t's always better and a preventive thought to Back-up your Daily SCCM 2012 Backup, (keeping a daily copy on the server and copying the backups to an alternate location). Because if your SCCM server falls down you still have a back-up!

In the process of SCCM's daily backup (visible in smsbkup.log), there's an 'AfterBackup.bat' file used to perform post-backup actions automatically after the Backup Site Server maintenance task runs successfully. By default, the AfterBackup.bat batch file does not exist. You have to create and place it manually.

As we all know there was a bug in the SCCM 2012 RTM Backup Site procedure. There was a workaround by creating a sub-folder underneath the Backup folder when using UNC paths.

This is described by Microsoft in: http://blogs.technet.com/b/configurationmgr/archive/2012/08/01/support-tip-a-backup-site-server-maintenance-task-may-fail-to-run-in-configmgr-2012.aspx

 

Microsoft stated this would be addressed in SP1 of SCCM 2012, well let's take a look and check-out the use of the 'AfterBackup.bat' procedure!

Activating site backup

ConfigMgr console > Administration tab > Site settings > Site maintainance > Backup site server

Edit and fill out the needed values.

You can set a local or remote UNC backup path and the scheduling options. Whatever you decide you can use the AfterBackup.bat to move or archive it afterwards.

The computer account of the ConfigMgr server has to have been granted full control permissions on the remote backup location.

Creating the AfterBackup.bat file

Here is a simple script for 'AfterBackup.bat' written by 'Garth Jones', which saves 7 days backup to a folder named after the first 3 letters of the day of the week, and also deletes/overwrites the older ones.

***********************************************************************************

REM @echo off

setlocal enabledelayedexpansion

set target=\\Destination_Server\E$\AfterBackup\%date:~0,3%

If not exist %target% goto datacopy

RD %target% /s /q

:datacopy

xcopy "\\Source_Server\*" "%target%\" /E /-Y

***********************************************************************************

where, "Source_Server" is the Primary Server from which the backup has to be copied,

and "Destination_Server" is the Remote Server where you want to copy the Site Backup.

 

Source_Server (This is the UNC path specified in ConfigMgr)

\\SCCM2012\sccm$\_Backup

Destination_Server (This is where we store the backup)

\\FILE01\SCCM$\SCCM_Backup

 

Although the intended use of AfterBackup.bat is to archive SCCM backup snapshots, you can use that file for other tasks that you need to perform at the end of every back up operation, such as:

 

  • Run a SQL Server DBCC test to verify that there are no integrity problems with the SCCM Site database.
  • Run a site health tool, or other health tools.

 

Putting the AfterBackup.bat to work

ConfigMgr has the ability to run an after backup batch file which you can use to perform archiving and other administrative functions.

Start by creating the AfterBackup.bat and copy it to the location below.

{ConfigMgrInstallPath}\inboxes\smsbkup.box\AfterBackup.bat

Once it's in place ConfigMgr will automatically execute its contents at the end of a sms_site_backup task. It runs as the computer system account.

ConfigMgr overwrites each backup when it runs the site backup task. You must use the AfterBackup.bat or manual copy to archive more than one backup.

Starting a backup outside of the schedule

You can start a backup at any time by going into the service manager which can be launched through the console.

Monitoring tab > System Status > Component State > Ribbon > Start > Configuration Manager Service Manager

Once in service manager, locate the SMS_SITE_BACKUP service and right click start. A backup will now start.

Another option is to go to Windows Services.msc and start the SMS_SITE_BACKUP service.

 

After a successful backup you will see this in your logs:

And the backup is copied over to your alternate backup location!

43.285400 5.376100

Follow up to WMF 3.0 and SCCM issues with SQL

Posted: 12 Feb 2013 08:29 PM PST

Since my original post on issues with the SCCM agent and WMF 3.0. We have only uninstalled the WMF 3.0 update on systems that created major issues or have documented compatibility issues. I have found the WMI queries don't report SQL Server data correctly.

Here is the Microsoft KB on how to fix this problem.

the common symptom I see is when attempting to run an application install that uses WMI to query the SQL version or any other information the setup wizrd reports either SQL is not installed or SQL is not the correct version.

New Online Training Sessions Available for System Center 2012 - #SC2012, #Microsoft

Posted: 12 Feb 2013 10:25 AM PST

Microsoft Virtual Academy has released a new training series that delves into System Center 2012 SP1 Service Manager. Topics covered include:

- Import Data and Runbooks 
- Build and Publish Request Offerings 
- Create, Invoke & Monitor 
- Chargeback

These sessions are now available to view online.

And now that System Center Universe 2013 is over, those sessions are also available online. You can now view the System Center Universe 2013 recordings online to learn about VMware and Hyper-V Data Protection, Advanced System Center Reporting, Windows Azure Infrastructure as a Service…

Continue reading here! 

//Richard

How To Install SCCM Client with GPO and Configure Firewall Policy

Posted: 12 Feb 2013 09:54 AM PST

What do each of the actions in the SCCM Client actually do?

Posted: 11 Feb 2013 06:33 AM PST

If you look up the Technet page regarding the Actions tab, you'll find that it tells you nothing about each action. All of the actions on the tab are scheduled tasks; that is, if the feature is enabled, it will automatically run on a periodic basis. In some circumstances (e.g. troubleshooting), you may find the need to manually initiate these tasks. That's where this tab comes in. The information on each action's functionality is scattered about the Technet website:

  • Branch Distribution Point Maintenance Task verifies any prestaged packages and downloads any that do not exist on the branch distribution point. While Technet does not explicitly state it, I believe this task is useful only on branch distribution points and is ignored on normal clients.
  • Discovery Data Collection Cycle causes the client to generate a new discovery data record (DDR). When the DDR is processed by the site server, Discovery Data Manager adds or updates resource information from the DDR in the site database.
  • File Collection Cycle When a file is specified for collection, the Microsoft System Center Configuration Manager 2007 software inventory agent searches for that file when it runs a software inventory scan on each client in the site. If the software inventory client agent finds a file that should be collected, the file is attached to the inventory file and sent to the site server. This action differs from software inventory in that it actually sends the file to the site server, so that it can be later viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Hardware Inventory Cycle collects information such as available disk space, processor type, and operating system about each computer. This is a part of SCCM inventory functionality.
  • Machine Policy Retrieval & Evaluation Cycle The client downloads its policy on a schedule. By default, this value is configured to every 60 minutes and is configured with the option Policy polling interval (minutes). However, there might be occasions when you want to initiate ad-hoc policy retrieval from the client—for example, in a troubleshooting scenario or when testing. This action initiates ad-hoc machine policy retrieval from the client outside its scheduled polling interval.
  • Software Inventory Cycle collects software inventory data directly from files (such as .exe files) by inventorying the file header information. Configuration Manager 2007 can also inventory unknown files — files that do not have detailed information in their file headers. This provides a flexible, easy-to-maintain software inventory method. You can also have Configuration Manager 2007 collect copies of files that you specify. Software inventory and collected file information for a client can be viewed using Resource Explorer. This is a part of SCCM inventory functionality.
  • Software Metering Usage Report Cycle collects the data that allows you to monitor and client software usage.
  • Software Updates Deployment Evaluation Cycle initiates a scan for software updates compliance. Before client computers can scan for software update compliance, the software updates environment must be configured.
  • Software Updates Scan Cycle Just after a software update installation completes, a scan is initiated to verify that the update is no longer required and to create a new state message that indicates the update has been installed. When the installation has finished but a restart is necessary, the state will indicate that the client computer is pending a restart.
  • User Policy Retrieval & Evaluation Cycle Similar to Machine Policy Retrieval & Evaluation Cycle, but this action initiates ad-hoc user policy retrieval from the client outside its scheduled polling interval.
  • Windows Installer Source List Update Cycle causes the Product Source Update Manager to complete a full update cycle. When you install an application using Windows Installer, those Windows Installer applications try to return to the path they were installed from when they need to install new components, repair the application, or update the application. This location is called the Windows Installer source location. Windows Installer Source Location Manager can automatically search Configuration Manager 2007 distribution points for the source files, even if the application was not originally installed from a distribution point.

Source: http://serverfault.com

Ezekiel Motley became a registered member

Posted: 27 Mar 2013 08:47 PM PDT

Comments: 0

Ben Fuller started the forum topic DMZ Workgroup client management. in the group System Center Configuration Manager 2012

Posted: 27 Mar 2013 08:11 PM PDT

I would like to use my ConfigManager 2012 SP1 environment to administer & update my DMZ based workgroup web servers. I have started putting together steps for a DMZ based management, software update & distribution […]

Comments: 0

Ben Fuller joined the group System Center Configuration Manager 2012

Posted: 27 Mar 2013 08:11 PM PDT

Comments: 0

Ben Fuller became a registered member

Posted: 27 Mar 2013 07:56 PM PDT

Comments: 0

Rod Trent posted an update in the group Windows PowerShell: Automatically determine target OU based on Computername with […]

Posted: 27 Mar 2013 05:50 PM PDT

Rod Trent posted an update in the group System Center Configuration Manager 2012: Automatically determine target OU based on Computername with […]

Posted: 27 Mar 2013 05:50 PM PDT

Stephan Schwarz wrote a new post, Automatically determine target OU based on Computername with powershell for MDT 2012 U1 / ConfigMgr

Posted: 27 Mar 2013 05:48 PM PDT

This is my first post on MyITForum, I've posted this article on my own blog yesterday but I want to share it on MyITForum to reach a broader audience.

While installing operating systems, software and […]

Comments: 0

Rod Trent posted an update in the group System Center Orchestrator/Opalis: SCORCH – Don’t Get Burned!

Posted: 27 Mar 2013 05:43 PM PDT

Brian Mason wrote a new post, SCORCH - Don't Get Burned!

Posted: 27 Mar 2013 05:36 PM PDT

Remember last year when Microsoft changed its licensing model for System Center as a whole? Evidently, things are still not quite as clear as we thought. I know our user group had Microsoft folks tell us that if […]

Comments: 0

Rod Trent posted an update in the group Software Licensing and SAM: 3 Reasons Why You Should Centralize Procurement of Your […]

Posted: 27 Mar 2013 04:27 PM PDT
by to

No hay comentarios:

Publicar un comentario

Suscribirse a: Enviar comentarios (Atom)

SCCM by Davis

Cargando...