Labels

Showing posts with label TUTORIAL. Show all posts
Showing posts with label TUTORIAL. Show all posts

Friday, 2 September 2016

Synchronizing Updates with Export and Import

When a software update point is not configured or cannot synchronize with its upstream server in the Configuration Manager 2012 hierarchy, the export and import functions of the WSUSUtil tool can be used to synchronize Software Updates metadata manually. The user who performs the export/import must be a member of the local Administrators group on the WSUS server, and the tool must be run locally on the WSUS server itself.

The files found in the WSUSContent folder (by default located in <WSUSInstallDrive>\WSUS\ WSUSContent) must also be copied from the upstream update server to the software update point so that locally stored updates and the license terms for the updates are available to the import server. This procedure can also be used for migrating the software update content from Configuration Manager 2007 to Configuration Manager 2012.

To export and import software updates from the export WSUS server to the import WSUS server, follow these steps:
1. Copy files from the export server to the import server:
     a. On the export server, go to the folder where software updates and the license terms for those software updates are stored. By default, this will be <WSUSInstallDrive>\WSUS\ WSUSContent.
     b. Copy all of these files to the same folder on the import server.

2. Export metadata from the database of the export server:
     a. At a command prompt on the export WSUS server, go to the folder that contains WSUSUtil.exe. By default, this will be located at %ProgramFiles%\Update Service\ Tools.
     b. Then enter the following:
                     WSUSUTIL.exe export packagename logfile 
The name of packagename doesn’t really matter, as long as it and the log file are unique in that folder. This command will export the Software Updates metadata into a file called packagename.cab.
     c. Move the export package that you just made to the folder that contains WSUSUtil.exe on the import WSUS server.

3. Import metadata to the database of the import server:
     a. At a command prompt on the WSUS server that you are importing the updates to, go to the folder that contains WSUSUtil.exe, which is %Program Files%\Update Services\ Tools.
     b. Enter
WSUSUTIL.exe import packagename logfilewith packagename being the name of the export file that you exported in step 2.

This will import all the metadata from the exporting server and create a log file that you can use to review the status.

Configuring Software Updates Settings and Synchronization

Software updates in Configuration Manager 2012 must be synchronized with Microsoft Update or an upstream WSUS server before information on those updates will be available to view in the Configuration Manager console. Synchronization starts at the highest level in the hierarchy that has a software update point and either has a configured schedule or is started manually using the Run Synchronization action.

When synchronization is started on a configured schedule, all changes to the Software Updates metadata since the last scheduled sync are inserted into the site database. This will include metadata for new software updates or metadata that has been modified or deleted. When a sync is started manually, only new software updates metadata since the last sync is inserted into the database. The manual sync process is faster since it is not pulling as much Software Updates metadata. A manual sync action is available only on parent sites.

To manually sync the software update point, do the following:

1. In the Configuration Manager console, choose the Software Library workspace ➢
Overview ➢ Software Updates ➢ All Software Updates.
2. Select the Home tab of the ribbon and click Synchronize Software Updates. Click Yes to initiate a sitewide synchronization of software updates.

The synchronization process might take longer than an hour to finish, depending on several factors, including whether a synchronization has been run before and what languages, products, and update classifications have been configured to be synchronized. You can monitor the synchronization process by looking at the log file for WSUS Synchronization Manager, wsyncmgr.log. This is located by default at %Program Files%/Microsoft Configuration Manager/Logs.

When the synchronization is complete, you will see a 6702 status message from SMS_WSUS_SYNC_MANAGER.
New in Configuration Manager 2012 is that you also can monitor the synchronization in the Configuration Manager console.

To monitor the synchronization in the hierarchy do the following:
1. In the Configuration Manager console, choose the Monitoring workspace ➢ Overview ➢
software update point Synchronization Status.
2. Look at the synchronization status, the link state, and the catalog versions. When the synchronization with Microsoft Update is complete (either from a schedule or started manually) at the highest site in the hierarchy, sync requests are sent to all child sites, and they in turn start synchronization with their configured upstream WSUS servers as soon as the request has finished processing.

The Software Updates metadata that is synced from Microsoft Update is based on the update classes, products, and languages that were selected when the software update point was first configured. A child site will synchronize whatever updates have been configured on its parent site.
Although all of the settings for update classes, products, and so on were configured at
the setup of the software update point, you can still reconfigure these options if needed. To
configure the update properties for software updates, follow these steps.
1. In the Configuration Manager console, choose the Administration workspace ➢
Overview ➢ Site Configuration ➢ Sites, and select the site that is the highest in the
hierarchy.
2. Choose Configure Site Components on the Settings section of the Home tab of the ribbon,
and click software update point.
3. To configure Update Classifications, click the Classifications tab, as shown in Figure 

4. To configure products that are being synced, click the Products tab, as shown in Figure

 5. To configure languages that are being synced, click the Languages tab, as shown in Figure .

 6. To reconfigure the supersedence settings, click the Supersedence Rules tab, as shown in Figure



To configure the software updates synchronization schedule, follow these steps:
1. In the Configuration Manager console choose the Administration workspace ➢ Overview ➢ Site Configuration ➢ Sites, and select the site that is the highest in the hierarchy.
2. Choose Configure Site Components on the Settings section of the Home tab of the ribbon, and click software update point.
3. To configure the synchronization schedule, click the Sync Schedule tab, as shown in Figure



 

4. To enable synchronization on a schedule, select Enable Synchronization On A Schedule, and set the schedule as you want it.
5. When you have finished, click OK to save the schedule.
Unless you change the Start value in the custom schedule, synchronization will be started as soon as possible and will repeat based on the schedule that you configured.
6. If you want alerts to be reported in the Alerts node of the Configuration Manager 2012 console, enable the Alert When Synchronization Fails On Any Site In The Hierarchy option.

Setting Up the Software Update Point

There can be several Configuration Manager site systems with the software update point system role, but there can be only one site system server configured as the software update point that synchronizes with a synchronization source like Microsoft Update in a Configuration Manager site. By default this is the first software update point you install in your environment. All other software update points are replicas of the first one you installed and use that one as the synchronization source.

When your Configuration Manager site is in HTTPS mode, you can have an Internet-based software update point assigned to a remote site system server that allows communication from only Internet-based client computers. Also, if the first software update point is on a Network Load Balancing cluster, there should be a software update point installed on every server that is in the NLB cluster. When you have a Central Administration Site in your Configuration Manager 2012 hierarchy, you first need to install and configure a software update point at one of the site servers in your Central Administration Site.


Installing the Windows Server Update Services 3.0 SP2 Administrative Console

The Windows Server Update Services 3.0 SP2 Administrative Console is required on the Configuration Manager 2012 site server, if WSUS is installed on a remote server, to allow it to communicate with WSUS so it can configure and synchronize software update points. The WSUS Administrative Console can be installed using the WSUS 3.0 Setup Wizard or installed silently from a command line.

To install the WSUS on a Configuration Manager site server, follow one of the procedures discussed in the sections that follow.

Installing Windows Server Update Services 3.0 Server

Windows Server Update Services 3.0 Server (WSUS) SP2 or later is required in order to use Software Updates in Configuration Manager 2012. Installing WSUS for use with Configuration Manager is different from a standard install of WSUS without the Configuration Manager infrastructure.

The WSUS installation procedure that we’re going to use can be used for both the first software update point (the main software update point installed on the Central Administration Site) and all other software update points (those for any other primary Configuration Manager sites) or for installing WSUS on a remote server that is not a Configuration Manager site server. The decision to install WSUS on the same server as your site servers or on another remote server will depend on your server resources and your plans for the software update infrastructure.
Next, you have to go through a series of steps to make a software update point the active one for the Configuration Manager hierarchy.  

Depending on the version of your operating system, you need to either add the Windows Server Update Services role though the Server Manager of Windows Server 2008 R2 or Windows Server 2012 or make sure that you have downloaded the latest version of WSUS at the WSUS home page:

Thursday, 1 September 2016

Configuring Software Updates in SCCM

Now that we have taken the time to look at the components of Software Updates and how they fit together, and you have taken that information with your deployment intelligence and put together a plan as to how you want to set up Software Updates in your environment, we can examine how to get everything working.

Before Software Updates data can be displayed in the Configuration Manager 2012 console and software updates can be deployed to clients, you must set up and configure the software update point, as well as the rest of the components of Software Updates.



Monday, 29 August 2016

The Software Update Process in Configuration Manager

As you’ll see throughout the hands-on portions of this chapter, the biggest parts of the software update process are planning and configuration. After you’ve completed those, Configuration Manager itself performs three main operational phases: synchronization, scanning for compliance, and deployment.

Friday, 26 August 2016

Elements of Software Updates

Before you can plan to implement the Software Update process, you need to become familiar with the various elements of the process and their roles in the overall picture.

Prerequisites for Software Updates in SCCM


Before you can plan and set up the Software Updates feature, you need to be familiar with its components, so you can determine which ones to install and configure for your environment.

External prerequisites to the Configuration Manager Software Updates feature.--

 Of course, you will also need to configure a SQL Reporting Services (SRS) reporting point before you can use the Software Updates reports.

 

What’s New in Software Updates

After integrating Windows Server Update Services in Configuration Manager 2007 as the Software Updates feature, Microsoft further enhanced the feature in Configuration Manager 2012. With Configuration Manager 2012 you can manage your software updates more easily and quickly. The following changes and enhancements are available in Configuration Manager 2012:

Thursday, 11 August 2016

Troubleshooting Application Deployment

With any product, in-depth troubleshooting requires a good understanding of the overall system to know where to look and common things that might go wrong. Configuration Manager 2012 is a large product with many moving parts, so understanding how to troubleshoot effectively comes with experience. The depth of troubleshooting attempted will depend on available time and your experience level with the system.
Log Files
Configuration Manager 2012 provides an extensive set of log files to aid administrators in troubleshooting scenarios. The information provided by the log files is significant, but even more detail is possible if you configure verbose or debug logging Logs in Configuration Manager 2012 are very beneficial for experienced administrators to quickly pinpoint a problem. For beginning administrators, though, the logs may beintimidating. Experience will help increase your comfort level with logs. A few suggestions will
help keep things on track:

◆ Determine which logs to review.
Configuration Manager 2012 processes generally can be broken into processing that happens on the server and processing that happens on the client. The management point is in the middle and can have elements that interact with both the server and the client. The place to start reviewing log information depends on where the processing problem seems to be happening: server side or client side.

S.no
Application Deployment :
Server Side Logs
Application Deployment :
Client Side Logs
1
Distmgr.log
AppIntentEval.log
2
Offermgr.log
App Discovery.log
3
PkgXfrMgr.log
AppEnforce.log
4
Schedule.log
policyAgent.log
5
Sender.log
Execmgr.log
6
Despooler.log
CAS.log
7
Replmgr.log
CTM.log
8

DTS.log

◆ Be patient.
The logging system in Configuration Manager 2012 is extensive, and finding the right log to review at first might be challenging. Many different Configuration Manager 2012 client components are required when trying to process an application deployment. These components pass information back and forth as the work gets done. With experience it becomes easier to know which log to start with, and it’s well worth learning. Never fear though; if it gets too time consuming to dig through the information provided, Microsoft support is just a phone call away.

◆ Watch the time stamp.
Following data in the log files boils down to following the time stamps. As logs update, their time stamps do too. A quick look at which logs have been active recently will help you identify logs that might be good candidates for review after an action is attempted and a failure encountered.

◆ Use CMTrace.
The log files are viewable with Notepad, but it’s definitely not the best environment. The CMTrace utility (formerly known as Trace32) available in Configuration Manager is perfect for viewing Configuration Manager logs—and many other types of text logs as well. Trace includes an error-lookup capability, the ability to filter by keyword or processing thread, the ability to merge log files to view the entire conversation between components (remember the time stamp discussion?), and so on. The utility has been updated for Configuration Manager 2012. 


Friday, 29 July 2016

Default Client Settings

A word about client settings: The default list of client settings applies to all clients in the Configuration Manager 2012 hierarchy. It is possible to override the default settings and specify different values for specific sites or specific systems via collection targeting.

This flexibility allows administrators complete control of which settings apply to devices and removes the technical limitation that often resulted in multiple sites or hierarchies, such as scenarios where servers and workstations needed separate management settings. The flexibility offered with client settings applies generically throughout Configuration Manager, but several settings that are available have specific impact with Application Deployment, as discussed in the following sections.

Thursday, 28 July 2016

Deployments in Configuration Manager 2012

Deployments in Configuration Manager 2012 directly influence the flow of application deployment. There are a number of new options available to help control this flow, as described here:

Applications: Application References

The Application References mechanism allows administrators to view what dependency and supersedence relationships are associated with a given application.
NOTE : Be careful when building relationships between applications. Relationships will prevent an  application from being deleted, and excessive numbers of relationships will increase complexity and potential confusion.

Distribution Point Changes

Distribution points are key components for any kind of content delivery in Configuration Manager. Understanding the changes to and optimizations of this role will directly relate to the efficiency of your design and satisfaction with the product.

Wednesday, 27 July 2016

Discovery Methods in SCCM

Discovery Methods 2007
  1. Active Directory System Discovery -Discovers details about the computer
  2. Active Directory System Group Discovery - Discovers details such as organizational unit, global groups, universal groups, and nested groups.
  3. Active Directory User Discovery-Retrieves Active Directory User Discovery
  4. Active Directory Security Group Discovery-Discovers security groups created in Active Directory.
  5. Heartbeat Discovery-Refresh Configuration Manager client computer discovery data in the site database.
  6. Network Discovery-Searches the network for resources that meet a specific profile, From router's ARP cache, SNMP agent and DHCP Each discovery method creates data discovery records (DDRs) for resources and sends them to the site database, even if the discovered resource is not capable of being a SCCM 2007 client.
Discovery Methods 2012

In Configuration Manager 2012 the discovery of users, groups and devices has been improved since Configuration Manager 2007. In this blog I would like to point out the available options that come with Configuration Manager 2012.
The discovery feature in Configuration Manager 2012 enables you to identify computer and user resources that can be managed with Configuration Manager. You are able to configure the discovery of resources on different levels in the Configuration Manager 2012 hierarchy. Let’s see how you are able to discover your user and devices.
   1.      Active Directory Forest Discovery
The Active Directory Forest Discovery is a new discovery method in Configuration Manager 2012 that allows the discovery of Active Directory Forest where the site servers reside and also any trusted forest. With this discovery method you are able to automatically create the Active Directory or IP subnet boundaries that are within the discovered Active Directory Forests.
Active Directory Forest Discovery can be configured on Central Administration Sites and Primary Sites.
To enable the discovery of Active Directory Forest you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Active Directory Forest Discovery.


Enable Active Directory Forest Discovery
   2.      Heartbeat discovery
The Heartbeat Discovery method is enabled by default and is used to configure the heartbeat schedule. The heartbeat discovery runs on each Configuration Manager client and is used to create a discovery data record (DDR). This record is reported back to the management point every x period of time. For mobile device clients, the DDR is created by the management point that is used by the mobile device client.
The Heartbeat discovery can be configured on every Primary Site.
To enable the Heartbeat Discovery you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Heartbeat Discovery.
   3.      Network Discovery
The Network Discovery method is used to discover the topology of your network and the devices on that network. The Network Discovery “service” searches your network for IP enabled resources. This is done by querying services that run an implementation of Microsoft’s DHCP, ARP tables in routers, SNMP enabled devices and Active Directory Domains.


Configure Network Discovery
It is a best practice only to use this method when all other methods cannot find the devices you want to discover and manage.
You are able to configure network discovery on the Central Administration Site, Primary Sites and Secondary Sites.
To enable the Network Discovery you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Network Discovery.
    4.      Active Directory User Discovery
The Active Directory User Discovery is used to discover users in the Active Directory You are able to configure the discovery only to look into one or more definable OUs or a complete domain, search into child containers and discover object within Active Directory groups like shown in the figure beneath.

Limit the scope of discovery
You are able to configure the full discovery polling schedule to occur every period of time (minutes, hours, days, weekly, monthly) and you are able to configure a delta discovery every X number of minutes. Delta discovery finds resources in the Active Directory that are new or modified since the last full discovery cycle.
Besides the default attributes, you are able to add attributes that need to be discovered.


Add attributes to the scope of discovered attributes
Active Directory User Discovery can be configured on Central Administration Sites and Primary Sites.
To enable the discovery of Active Directory Users you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Active Directory User Discovery.
    5.      Active Directory System Discovery
The Active Directory System Discovery has the same discovery options regarding OUs, scheduling and adding attributes that needs to be discovered. Two new and very welcome options are that you now can define that the discovery method only must discover computers that have logged on to a domain in a given period of time and that the discovery method only must discover computers that have updated their computer password in a given period of time. This way you won’t discover obsolete computer accounts from the Active Directory.


Exclude "obsolete" computers
Active Directory System Discovery can be configured on Central Administration Sites and Primary Sites.
To enable the discovery of Active Directory Systems you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Active Directory System Discovery.

    6.      Active Directory Group Discovery
The old Configuration Manager 2007 System Group and User Group discovery are merged to one discovery method, which is called Active Directory Group Discovery. Besides merging the methods, Configuration Manager will now also remove devices or users from collections that are for instance removed from an Active Directory Group. You are able to discover Groups via a definable Location (OU or domain) or via definable Groups that are available in the Active Directory domain.



Configure group discovery
Also with the Active Directory Group Discovery you are able to configure the “Time since last logon”  and “Time since last password update”  options. You are also able to discover the membership of distribution groups.
Exclude "obsolete" computers and discover membership of distribution groups
Active Directory Group Discovery can be configured on Central Administration Sites and Primary Sites.
To enable the discovery of Active Directory Groups you need to configure this option in Administration -> Overview -> Site Hierarchy -> Discovery Methods -> Active Directory Group Discovery.
With all these discovery methods you are able to gather the resources that you want to manage in your Configuration Manager sites. Try to limit the resources that you want to discover to those you need for Configuration Manager 2012.