Use the following sections to review information about significant changes in System Center 2012 Configuration Manager SP1 since System Center 2012 Configuration Manager:

Setup and Site Installation
Sites and Hierarchies
Migration
Client Deployment and Operations
Software Deployment and Content Management
Monitoring and Reporting Erectiestoornis diabetes

To backup your configuration:
1) Click on files
2) Click on backup.
mikrotik-backupimg

3) The system configuration will automatically be saved
4) To download the file, ftp to the router and download the file
To restore your configuration:
1) Open an ftp connection to the router and upload the configuration file.
2) Click on files.
3) Select the backup file and click on restore.

Configuration Manager 2007 gives you an option to create New folder (kind of Custom reports folder ) with New Category to create your Own reports what you required But in Configuration Manager 2012,i don’t see way to create New folder to create all the custom reports for your reference.
Creation of Custom folder is not available in configuration Manager 2012 ,the only option left out is to go with Category .
How do you create New Citatory ? If you right click on reports node from Configuration Console,you don’t get such option to create one.
You will have to go with web reports with enough rights to create it.

Open IE with SSRS report manager website : http://SCCMServername/reports Viagra bloeddruk

The yum update utility can be run by hand from the command line, called through one of the provided  front-end tools,or configured to run automatically at specified intervals.

Manually Check for Package Updates
The following command prints a list of packages that need to be updated:
# yum check-update
To actually install these updates, run:
# yum update

Configure Automatic Update Retrieval and Installation with Cron
The yum-updatesd service is not mature enough for an enterprise environment, and the service may introduce unnecessary overhead. When possible, replace this service with a cron job that calls yum directly.

Disable the yum-updatesd service:
# chkconfig yum-updatesd off
Create the file yum.cron, make it executable, and place it in /etc/cron.daily:
#!/bin/sh
/usr/bin/yum -R 120 -e 0 -d 0 -y update yum
/usr/bin/yum -R 10 -e 0 -d 0 -y update
This particular script instructs yum to update any packages it finds. Placing the script in /etc/cron.
daily ensures its daily execution. To only apply updates once a week, place the script in /etc/cron.weekly instead.

To ensure that the system can cryptographically verify update packages (and also connect to the Red Hat Network to receive them if desired),
run the following command to ensure that the system has the Red Hat GPG key properly installed: $rpm -q –queryformat “%{SUMMARY}\n” gpg-pubkey
The command should return the string:    gpg(Red Hat, Inc. (release key <[email protected]>)

To verify that the Red Hat GPG key itself has not been tampered with, its fingerprint can be compared to the one from Red Hat’s web site at http://www.redhat.com/security/team/key. The following command can be used to print the installed release key’s fingerprint, which is actually contained in the file referenced below:
$ gpg –quiet –with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
More information on package signing is also available at https://fedoraproject.org/keys.