SCCM Training - Delhi , NCR and North India

Those Interested for SCCM Training can send in the details at sccmtrainings@gmail.com

SCCM 2007 to SCCM 2012 Migration - Step by Step Guide - Part 1

In this Post , You will learn on how to Migrate SCCM 2007 to SCCM 2012 . Although the Actual Environment would be a more Complex Scenario but the Underlying steps remain the same .

Before we Migrate , I will give you a brief about the Environment in which this Migration has been Performed ( It is Based on MS Virtual Lab ) with One SCCM 2007 Primary Site Being Migrated to SCCM 2012 Central , There is One Primary Site and One Client which is Finally Upgraded to SCCM 2012 From SCCM 2007 .

It Should be Noted that there is no Direct Method of Migration but the only way to perform Migration is a Side by Side Migration , Which Involves Specifying Source Hierarchy , Migrating Collections , Packages , OS Images , Etc .

Very First step is to Specify the Source Hierarchy on the SCCM 2012 Central Site . For this  you Need Access to Account which has read Access to Objects in SCCM 2007 Environment and Server .

After the Account has been Specified , Check the test Connection .

Keep Checking IF SCCM Set up is running on Client Machine . After some time you will see Configuration Manager and find that all information is gone  and New information is Populated .

Application Catalog Web Service Point Installation - Step by Step

This Guide Helps you to Install Application Catalog Web Service Point  on SCCM Server . Before we start with it let us take a look at the Log Files that are present on the server :

Clearly You can see that there is no File related to Application Catalog Web Service Point  or Application Catalog Website . awebsctl.log , awebsvcMSI.log are two of them .

let us now go through the Installation . We are only considering Intranet Based clients in this example .

 

 

 

 

 

 

After the Roles have been Installed let us have a look at the awwebsvcMSI.log .

Content Status Monitoring - This wasn't there in SCCM 2007

Content Status Monitoring

---

The Content Status node in the Monitoring workspace provides information about content packages. In the Configuration Manager console, you can review information such as the package name, type, how many distribution points have been targeted, the compliance rate, when the package was created, package ID, and source version. You also find information about distribution status for the package, such as the number of failures, pending distributions, installations, and so on. You can also view detailed status information for any package.

Beginning with System Center 2012 R2 Configuration Manager, when you view the status of a distribution in the Content Status node, you can manage distributions that remain in progress to a distribution point or that failed to successfully distribute content to a distribution point. The applicable option to either cancel or redistribute content is available when you view the deployment status message of a distribution job to a distribution point in the Asset Details pane of either the In Progress tab orError tab of the Content Status node. Additionally, the job details display the percentage of the job that has completed when you view the details of a job on the In Progress tab, and the number of retries that remain for a job as well as how long before the next retry occurs when you view the details of a job that is available from theError tab.

When you cancel a deployment that is not yet complete, the distribution job to transfer that content stops. The status of the deployment then updates to indicate the distribution failed and was canceled by a user action. This new status appears in the Error tab. When you redistribute content that previously failed to transfer to a distribution point, Configuration Manager immediately begins deploying that content to the distribution point again and updates the status of the deployment to reflect the ongoing state of that redeployment. When a deployment is near completion, it is possible the action to cancel that distribution will not process before the distribution to the distribution point completes. When this occurs, the action to cancel the deployment is ignored, and the status for the deployment displays as successful.

 

Package Distribution Process SCCM

 

The Post Assumes that there is No Package Replication that is taking place .

Mac Management Using SCCM – Parallels Management Suite for Microsoft SCCM- Part 2

SCCM 2007

---

 

• Microsoft Windows:  All versions of Windows that are supported by System Center Configuration Manager 2007. Make sure you have the latest service pack and critical updates for the SCCM 2007.
• Mac OS X:  10.6x, 10.7x, 10.8x. Each Mac must have the Parallels Management - Mac  Agent installed on it to be managed.
• At this time, some Mac OS X Configuration Profile payloads must be created using the Mac OS X Server web-based profile editor.

SCCM 2012

---

 

• Microsoft Windows:  All versions of Microsoft Windows that are supported by System Center Configuration Manager 2012. Make sure you have the latest critical updates for SCCM 2012.
• Mac OS X: 10.6x, 10.7x, 10.8x. Each Mac must have the Parallels Management - Mac Agent installed on it to be managed.
• At this time, some Mac OS X Configuration Profile payloads must be created using the Mac OS X Server web-based profile editor.

Mac Management Using SCCM - Parallels Management Suite for Microsoft SCCM

From Parallels, the industry leader in making Windows and Mac work together seamlessly, comes the Parallels Management Suite for Microsoft System Center Configuration Manager (SCCM). The initial offering in the suite – Parallels Management-Mac for Microsoft SCCM – means, for the first time, you can have a universal and comprehensive cross-platform solution to manage Macs and PCs with ease. This plug-in extends your SCCM (2007/2012) infrastructure, processes, and skills, so you can master your Macs.

 

Parallels Management-Mac for Microsoft SCCM – Overview

Macs are a reality in businesses today, and they need to be managed. Whether you want to extend your current SCCM-based desktop management infrastructure or consolidate multiple systems to minimize redundancy and save money, we can help. As the leaders in making Windows and Mac work together seamlessly, we understand Apple technologies and the needs of IT teams who use SCCM and also need to manage Macs.

Full visibility of the Macs on your network
No more guessing how many Macs are really there. Automatically scan the network ranges you choose, and discover Macs on your network. Then, have the Parallels Management-Mac for Microsoft SCCM agent auto-install and enroll them. The plug-in ensures you have the broadest range of Macs covered, including Mac OS X 10.8x, 10.7x, and 10.6x.

Gain control – easily 
Software discovery, distribution, and inventory occur just like with your PCs, but without costly Mac-only infrastructure. Our wizard-driven system for application packaging and Mac profile setup makes it easy for SCCM admins with minimal Mac skills, so anyone can be a pro in no time. And we make it simple to use Apple's latest FileVault 2 technology to provide the best security available on your Macs.

Securely deploy and manage Windows on Mac 
Parallels Management-Mac extends your management abilities even further, to Windows applications on Macs. In conjunction with Parallels Desktop for Mac, manage delivery of your policy-compliant Windows stack to Mac users. All your management needs, centralized in SCCM.

SCCM Secondary Site - Restore !!

Today we are going to talk about SCCM Secondary Site Failure and Restore !! For a Long while SCCM Admins would have nightmare if the Secondary Site Goes down . The only option you have in this case is to re Install it . You may use copy and paste tools and tools like Imagex to get things working , but it's a pain .  IN SCCM 2012 SP1 ( Though it started from RTM ) SCCM Secondary Site restore is officially supported . Some of the important points are discussed as below :

 

1. The restore does not happen from back up on Secondary site . However , it happens from the Parent site .

2. The Restore option does not Install SQL Express by default . If you do not have it installed then install it as SQL Express Installation is not a part of Secondary Site Restore .

3. As is obvious , the DB Name and other things should remain the same .

4.  You must use a computer with the same configuration as the failed computer, such as its FQDN, to successfully recover the secondary site. The computer must also meet all secondary site prerequisites and have appropriate security rights configured. Also, use the same installation path that was used for the failed site.

 

OSD Bare Metal Flow Chart SCCM

Operating System Deployment SCCM 2012 - Step by Step Guide

Its been long since I was planning to write a post on SCCM OSD . This guide Explains most of the steps for OSD . The last step of the guide is pending and I will soon be writing a post on this .

 

Do share your feedback at sccmabheek@gmail.com . 

 

 

On the Client Machine you need to make sure that the client is a member of work group and not Domain .