Below are the high level Capabilities when compared with SCCM 2007 R3 vs SCCM 2012 vs SCCM 2012 Sp1

Below are the high level Capabilities when compared with SCCM 2007 R3 vs SCCM 2012 vs SCCM 2012 Sp1

Finding out the user account gets lockouts frequently....for investigation

1) Find out the computer that lockouts are originating from

Great tool from Microsoft to use is LockOutStatus [Account Lockout and Management Tools]
http://www.microsoft.com/en-us/download/details.aspx?id=18465

These tools are mainly for Windows XP and Server 2003, but LockOutStatus.exe works on Server 2008 R2 Active Directories.

Usmt local profiles not migrating

Usmt local profiles are not migrating when try to migrate with default task sequence as  /lac /lae /ui /ue and uel used 

Use the two options

1) remove the local user profiles and give a try

2) in the task sequence provide the local profiles password 

Above should work the trick... See this Http://goo.gl/OoduWZ

Umt local profiles not migrating

Usmt local profiles are not migrating when try to migrate with default task sequence as  /lac /lae /ui /ue and uel used 

Use the two options

1) remove the local user profiles and give a try

2) in the task sequence provide the local profiles password 

Above should work the trick... See this Http://goo.gl/OoduWZ

Back to USMT basics

Here is a nice explanation of USMT from basics http://tr.im/4bb67

DropBox My Files Scripts Shares and Recordings will be availble

Register if you don't have Dropbox account, Soon I will be sharing the Scripts and usefull stuff

http://db.tt/SSzfaDYE

Thank You,

ITIL Qualification Scheme

 

These are the levels of qualifications within the scheme:

• ITIL Foundation
• ITIL Intermediate Level
• ITIL Managing Across the Lifecycle
• ITIL Expert Level
• ITIL Master Qualification

Where is the key for SCCM Client log file folder path

Below would be the key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\Logging\@GLOBAL
String as "LogDirectory"
Value Data: E:\Logs\SCCMClient\


Changing this Value should be from WMI is recommended.
 

SCCM 2012 With SP1 and Updates

The realase of SCCM 2012 was very smooth, but the Sp1 created some issues, However MS updated the Binaries that resolved lot, but few of them were fixed in March 2013, by Collection of Updates we called Cumulative Update 1.

Find the direct link for Cummulative update 1 http://support.microsoft.com/kb/2817245
 

Delete all packages from Distrubution Point

Did you get ever a situation to delete all the Packages from one Specific DP ?

There are few tools/Scripts are available

-          ConfigMgr 2007 Distribution Point Package Utility

o   Can be downloaded from http://www.myitforum.com/inc/arts/12171Setup.zip

-          Vbscript I like this tool as it is very quick

o   http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-00-54-13-12/DPClean.zip

For SCCM 2012 http://gallery.technet.microsoft.com/scriptcenter/Remove-Packages-from-5031a1b5

'Rslaten 03/2005
'http://blogs.msdn.com/b/rslaten/archive/2006/03/01/removing-a-retired-dp-from-all-your-packages.aspx  
On Error Resume Next

WScript.Echo ""
WScript.Echo "SMSDPClean v1.3"
WScript.Echo "Usage: cscript.exe SMSDPClean  "
WScript.Echo "Example: cscript.exe SMSDPClean.vbs myCentralSiteServer myDistributionPoint"
WScript.Echo ""

Dim SMSSiteServer, SMSNameSpace, oLocator, oServices, bDone

'Get Args, add error checking here if needed
SMSSiteServer = WScript.Arguments(0)
DP = WScript.Arguments(1)

'Get SMS namespace
SMSNameSpace = GetSMSNameSpace(SMSSiteServer)

'Connect to SMS namespace
Set oLocator = CreateObject("WbemScripting.SWbemLocator")
Set oServices = oLocator.ConnectServer(SMSSiteServer, SMSNameSpace,,,,,128)
If Err.number <> 0 Then
    WScript.Echo "Error connecting to " &SMSNameSpace& " on " &SMSSiteServer& ": " &Err.Number
    Set oLocator = Nothing
    Set oServices = Nothing
    WScript.Quit
End If

'Call main procedure
PackageLoop

'Loop until async task is done
Do While not bDone
    WScript.Sleep 1000
Loop

Set oLocator = Nothing
Set oServices = Nothing
WScript.Quit


'Functions
'''''''''''''''''''''''''''''''''''''''''
'
'GetSMSNameSpace Function
'
'''''''''''''''''''''''''''''''''''''''''
Function GetSMSNameSpace(SiteServer)
    On Error Resume Next
    Dim colNameSpaceQuery, refitem, refWMI
    Set refWMI = GetObject("winMgmts:\\" &SiteServer&"\root\sms")
    If Err.number <> 0 Then
        WScript.Echo "Error connecting to SMS namespace on " &SiteServer
        WScript.Quit
    End If
    Set colNameSpaceQuery = refWMI.ExecQuery("select * from SMS_ProviderLocation")
    For Each refitem in colNameSpaceQuery
        GetSMSNameSpace = refitem.NamespacePath
    Next
    Set colNameSpaceQuery = Nothing
    Set refitem = Nothing
    Set refWMI = Nothing
End Function

'''''''''''''''''''''''''''''''''''''''''
'
'ValidDP Function
'
'''''''''''''''''''''''''''''''''''''''''
Function ValidDP(DP, SiteCode)
    On Error Resume Next
    Dim SysRes, start, finish, tempDP
    ValidDP = False
    Set SysRes = oServices.ExecQuery("select * from sms_sci_sysresuse where SiteCode = '" &SiteCode& "'")
    For each res in SysRes
        start = InStr(res.NALPath,"=\\") + 3
        finish = InStr(res.NALPath,"]MSWNET") - 2
        tempDP = mid(res.NALPath,start,finish-start)
        If (UCase(tempDP) = UCase(DP)) and (res.RoleName = "SMS Distribution Point") Then
            Set SysRes = Nothing
            ValidDP = True
            Exit Function
        End If
    Next
    Set SysRes = Nothing
End Function

'''''''''''''''''''''''''''''''''''''''''
'
'PackageLoop SubRoutine
'
'''''''''''''''''''''''''''''''''''''''''
Sub PackageLoop
    On Error Resume Next
    Dim sinkcol, retValuecol
    bDone = False
    Set sinkcol = wscript.CreateObject("WbemScripting.SWbemSink","SINKCOL_")
    retValuecol = oServices.ExecQueryAsync(sinkcol,"SELECT * FROM SMS_DistributionPoint")
    If Err.Number <> 0 Then
        WScript.Echo "Error running query:" &err.description
        WScript.Quit
    End If
End Sub
Sub SINKCOL_OnObjectReady(objDP, objAsyncContext)
    On Error Resume Next
    Dim start, finish, tempDP
    start = InStr(objDP.ServerNALPath,"=\\") + 3
    finish = InStr(objDP.ServerNALPath,"]MSWNET") - 2
    tempDP = mid(objDP.ServerNALPath,start,finish-start)
    If UCase(tempDP) = UCase(DP) Then
        WScript.Echo "Found " &DP& " on "& objDP.SiteCode& " linked to package " &objDP.PackageID
        If ValidDP(DP, objDP.SiteCode) Then
            WScript.Echo "Validated " &DP& " for site " &objDP.SiteCode
            objDP.Delete_()
            If Err.number <> 0 Then
                WScript.Echo "Failed to delete " &DP& " from package " &objDP.PackageID& " on site " &objDP.SiteCode
                WScript.Echo "Error = " &Err.number& " - " &Err.Description
            Else
                WScript.Echo "Successfully deleted " &DP& " from package " &objDP.PackageID& " on site " &objDP.SiteCode
            End If
        Else
            WScript.Echo DP& " is not specified as a distribution point on site " &objDP.SiteCode
        End If
    End If
End Sub
Sub SINKCOL_OnCompleted(iHResult, objErrorObject, objAsyncContext)
    bDone = True
End Sub

To Upgrade SCCM 2012 secondary site to a Service Pack 1

  Ensure you complete these go through with this ms link
http://technet.microsoft.com/en-us/library/jj822981.aspx

1. Log on to the Secondary site and start the SQL Server Configuration Manager

1. Select SQL Server Network Configuration, Protocols for CONFIGMGRSEC.

2. Right click TCP/IP and click Properties.

3. Select the IP Addresses tab and scroll down to IPALL. Delete the entry in TCP Dynamic Ports and click OK. When prompted with a warning, click Yes.

4. Select SQL Server Services, right-click SQL Server, and click Restart.

5. Log on to the primary site server and start the ConfigMgr administrator console.

6. Navigate to the Administration workspace, and select Site Configuration and Sites.

7. Select the secondary site server and click Upgrade on the ribbon

8. Click Yes on the site upgrade warning.

9. Click Show Install status on the ribbon. Click the Refresh button a few times to receive real-time information about the upgrade process.

10.    Click OK to close the installation status

PowerShell script to check WDS Service status against of List of servers.

Below is a PowerShell script, this will list WDS Service status against of List of servers.

Below is a powershell script will list WDS Service status againest of List of servers.

$InPutComputersList = get-content "c:\MyScripts\list.txt"
$OutPutFile = "c:\MyScripts\WDS_ServiceStatus.csv"
$NotReachble = "c:\MyScripts\NonPingSystems.csv"
$listResult = @()
foreach($ForEverComputerIntheTextFilelinebyLine in $InPutComputersList) {
if (test-path \$ForEverComputerIntheTextFilelinebyLine\c$\windows\write.exe)
{
$objService = Get-Service WDSServer -ComputerName $ForEverComputerIntheTextFilelinebyLine | select machinename, status, name, displayname

$objResult = New-Object PSObject -Property @{
ComputerName = $ForEverComputerIntheTextFilelinebyLine
ServiceStatus = $objService.Status
ServiceDisplayName = $objService.DisplayName
ServiceName = $objService.Name

}
$listResult += $objResult
}
Else
{
Write-Output "$ForEverComputerIntheTextFilelinebyLine,NotReachable" | out-file $NotReachble -append
}
}
$listResult| Export-Csv -Path $OutPutFile

SCCM 2012 Replication – What is replicated in each type From where to where

 

There are TWO types of replication can happen

1) Database Replication
2) File-Based Replication

Database Replication Includes Global Data & Site Data

Global data that replicates by using database replication.

Site data that replicates by using database replication.

Note:- Apart from above two there is local data this is just to specific to the local site.

Global data includes below : these are flow from CAS to below the Hierarchy

Alert rules

Client discovery

Collections rules and count

Configuration Items metadata

Deployments

Operating system images (boot images and driver packages)

Package metadata

Program metadata

Site control file

Site security objects (security roles and security scopes)

Software updates metadata

System Resource List (site system servers)

 

Site Data Replication: These are from Client to reporting/assigned Site

Alert messages

Asset Intelligence client access license (CAL) tracking data

Client Health data

Client Health history

Collection membership results

Component and Site Status Summarizers

Hardware inventory

Software distribution status details

Software inventory and metering

Software updates site data

Status messages

Status summary data

File-Based Replication: Earlier products there was only one type of Replication and this is file type. Now with SCCM 2012 this was limited two below types, Mainly used for Software packages and software updates.

File content that replicates by using file-based replication.

File based Data	To the Destination
Package files used by deployments	Sent to primary and secondary sites.
Data from secondary sites	Sent to the primary site (parent) of the secondary site.
Fallback status point state messages	Forwarded to the assigned site when only a single fallback status point is in use.
Discovery data records	Forwarded to the assigned site when not processed at the site where they are generated.

SCCM 2012 Client Push – Pre Requirement (HotFix)

 

The hotfix described in KB2552033 must be installed on site servers that run Windows Server 2008 R2 when client push installation is enabled.

For package pre-stage in 2012

On dp take the check box as pre stage

From package right click create "prestage content file" to create the package
This will create the .pkgx file.
Get the file extractcontent.exe from bin/x64

Run the below command

extractcontent.exe /p:e:\path of .pkgx files /s

These two steps will distribute the package as pre-stage method

Setupwpf.exe /script

Configmgrautosave.ini

Script to check the drive space in the server against the threshold value and triggers an alert

Script to check Disk Space
#Purpose: Script to check the drive space in the server against the threshold value and triggers an alert
#powershell script for disk space monitoring

$computer = get-content -path .\list.txt #get-content env:computername; #Get the server name
$percentWarning = 50; # Store the percentage warning threshold
$disks = Get-WmiObject -ComputerName $computer -Class Win32_LogicalDisk -Filter "DriveType = 3";
$mailbody = "The following drive(s) have less than $percentWarning% free sapce in Server,Please cleanup: $computer`n`n";
$mailbody+="Drive`t`tTotalspace(GB)`t`t`Freespace(GB)`n ________________________________________________________________________ `n";
$drivedata="";
$emailsubject="$computer - Low Disk Space Alert!";

# Code to send email to the File Server Owners
function SendEmail([string]$msg)
{
 $SMTPClient = new-object System.Net.Mail.smtpClient;
 $SMTPClient.host = "smtp.Domain.com"
 $MailMessage = new-object System.Net.Mail.MailMessage;
 $MailMessage.Subject = $emailsubject;
 $MailMessage.Body = $msg;
 $MailMessage.From = "SCOMN_No_Reply@Domain.com";
 $MailMessage.To.add("ToJhon@Domain.com");
 $SMTPClient.Send($MailMessage);
}

#The following block performs the core functionality
foreach($disk in $disks)
{
 $deviceID = $disk.DeviceID;
 [float]$size = $disk.Size;
 [float]$freespace = $disk.FreeSpace;  
 $percentFree = [Math]::Round(($freespace / $size) * 100, 2);
 $sizeGB = [Math]::Round($size / 1073741824, 2);
 $freeSpaceGB = [Math]::Round($freespace / 1073741824, 2);  
 if($percentFree -lt $percentWarning)
 {
  $drivedata += "$deviceID`t`t $sizeGB`t`t`t$freeSpaceGB`n";
 }
}
#Email to be sent only if any drive has free space less than threshold value
if($drivedata.length -gt 0)
{
 $msg=$mailbody+$drivedata;
 SendEmail($msg);
}

Source:- http://www.sharepointdiary.com/2012/11/drive-space-monitoring-using-powershell.html

Migrate reports from SCCM 2007 to SCCM 2012

Sync SSRS report between two report servers:

The built-in migration wizard in ConfigMgr 2012 can migrate most objects but not reports. In ConfigMgr 2012 classical ASP reports (as we know them from earlier versions) are no longer supported.
Migrate the classical reports to SQL Reporting Services in SCCM 2007
Below is a walk thru of how you migrate your existing classical reports to SQL reporting Services in SCCM 2007. Notice that you will still be able to run all classical reports after the migration.

1. On you SCCM 2007 site server install either SCCM 2007 R2 or SCCM 2007 R3, both will add SQL Reporting Services support for SCCM 2007.
2. In the ConfigMgr. console, navigate to Site Database, Site Management, A01 (where A01 is the sitecode), Site Systems. Right click the Site system server that will become a Reporting Services Point and click New Roles. Select Reporting Services Point and finish the wizard using the default values.
3. In the ConfigMgr. console, navigate to Site Database, Computer Management, Reporting, Reporting Services, and expand the node.
4. Right-click SCCM1 (where SCCM1 is the name of your server), and then click Properties.
5. On the Data Source Settings tab, specify SCCM1 as the database server and SMS_A01as the database name (where SMS_A01 is the name of your SCCM 2007 database. ClickTest.
6. On the Data Source Authentication tab, select Windows integrated security.
7. Click OK.

Copy reports to SQL Reporting Services

1. Right-click SCCM1, and select Copy Reports to Reporting Services.
2. On the Data Source Settings page, accept the default settings, and click Next.
3. On the Data Source Authentication page, accept the default settings, and click Next.
4. On the Select Reports page, accept the default settings, and click Next.
5. On the Security page, accept the default settings, and click Next.
6. On the Summary page, click Next.
7. On the Progress page - once all of the reports have copied - click Next and then clickClose.

Migrate the SCCM 2007 reports to SCCM 2012
You can’t use the built-in migration tools to migrate reports from SCCM 2007 to SCCM 2012. This leaves you with two choices; 1) Download each RDL file one by one from SCCM 2007 and upload them to SCCM 2012 or 2) Use one of the free community tools that can download multiple folders at the time. In my last project I used this tool – ReportSync - to assist me.

1. Launch ReportSync
2. In Source server type in the name of the SCCM 2007 Report server in form of http://CM01/ReportServer. Provide credentials and click Load
3. In Destination server type in the name of the SCCM 2012 Report server in form of http://CM02/ReportServer. Provide credentials and click Load
   
4. Select the folders or individual reports you want to migrate and click Sync
   
5. Once the process is finished click OK and your reports are now ready in SCCM 2012.
6. This tool keeps the old Data source which will generate an error the first time you run the report.
   
7. Open the report properties (by clicking on the report link)
8. Select Data Sources, click Browse and select the shared SCCM 2012 data source. The data source is found in Home\ConfigMgr_Sitecode. The data source is the object with long GUID. Select the data source click OK and Apply.
   
9. Run the report and verify that it works. There is no guarantee the all SCCM 2007 reports work out of the box in SCCM 2012.
   

Download link : http://code.google.com/p/reportsync/downloads/list

All credits goes to Kent.

SCCM 2012 Replication Data

From SCCM 2012 site to site replication is moved to SQL replication, Where as in SCCM 2007 it was file based.

Below chart explains the What kind of Data type will be replicated between sites with Replication Types.

What is there in Global Data & Site Data ?

When do we need a CAS (Central Administration) 2012 Site

• If you have more than one Primary Site in a single hierarchy
• For Central Reports and administration for your primary sites management.

Question:- Can i install CAS on existing SCCM 2007 Server?

No it is recommended to install on new (hardware) box

When do we need a local Distribution Point? In SCCM 2012?

 

Below are the three key points to consider a local distribution Point’s

• BITS not enough to control the WAN traffic
• Multicast for Operating System Deployment
• To stream APP-V Applications

Ok..  Now when we do not need a local Distribution points in SCCM 2012?

Below are the key considerations…

• Clients are well managed with-in BITIS provided control for WAN traffic
• If BranchCache deployed(below points are pre-requirements for BranchCache)
  • DP’s on 2008 R2
  • Vista Sp2 with KB960568 and above OS’s(windows7 & 8)

Note:- Distribution Point role can be enabled on Client OS or Server OS.
Note:- Branch Distrubution Point Role is removed in SCCM 2012.

When do we need a Secondary Site – SCCM 2012

 

Below are the three key considerations to setup a secondary site.

• To manage Upward-flowing WAN traffic
• Tiered content Routing for deep network topologies
• No local administrators
  

When do I need SCCM 2012 Primary Site?

To Manage Clients/Devices
Add More Primary sites for

• To scale more than 100,000 Clients
• Reduce impact of primary site failures in case of DR(Disaster recovery)
• Local Point of Connectivity for Administration & Political Reasons
• Content Regulations

Ok….. When you do not need a primary site compared with SCCM 20007 ?

• Decentralized administration
• Logical data segmentation
• Client settings
• Language Settings
• Content routing for deep hierarchies

What is Empower Users in SCCM 2012

Enabling any device from any where

What is Empower Users in SCCM 2012

Enabling any device from any where

Changes from SCCM 2012 to SCCM 2012 SP1

Below are the changes from SCCM 2012 to SCCM 2012 SP1

Changes from SCCM 2012 to SCCM 2012 SP1

Below are the changes from SCCM 2012 to SCCM 2012 SP1

What is Windows To Go?

Windows To Go is a feature in Windows 8 Enterprise that allows Windows 8 Enterprise to boot and run from mass storage devices such as USB flash drives and external hard disk drives.It is a fully manageable corporate Windows 8 environment. Using Group Policy, Windows Store can be enabled for a Windows To Go workspace (limited to one PC) and Store apps can be used on that workspace.

Is windows 8 supported for sccm ?

Yes from sccm 2012 sp1. The bad news is windows xp no more supported.

Read this related to windows 8 support .... Into

One of the most significant changes is support for Windows 8 for Configuration Manager clients. Configuration Manager SP1 supports Windows 8 in the following ways:

You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go.

You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles.

You can configure new deployment types for Windows 8 applications, which support stand-alone applications (.appx files) and links to the Windows Store.

Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected.

What is not changed in sccm 2012 when compared with sccm 2007 ?

Wake on LAN

Windows Embedded devices

The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager.

What is Application management in sccm ?

Provides a set of tools and resources that can help you create, manage, deploy, and monitor applications in the enterprise.

Why you want sccm ?

You can perform all below with help of sccm:

Deploy operating systems, software applications, and software updates.

Monitor and remediate computers for compliance settings.

Monitor hardware and software inventory.

Remotely administer computers.

Windows XP to Windows 7 -task Sequence High Level

These are the some high level steps in the Task Sequence.

use USMT=>request store=>run additional commands like taking backup of some applications..may be Lotus notesècapture user state/scan state èrelease state storeèdisable bitlocker if activatedèset Migration Flag to MigratedèStart System in PEè Partition Diskèactivate/Enable AHCIèEnable or Set BIOS password è Enable TMP for Bitlocker pre-requirementèRestart Computer èActivate TPMèrestart ComputerèRemove Bios PasswordèApply OSèwindows SettingsèNetwork SettingsèApply Drivers(use WQL or Thin Installer or HP SoftPaq or Dynamic Drivers Apply with CAB File packagesèSetup SCCM ClientèFix any issues related to SCCM Client like run auto discovery of site codeèBIOS version check and updateèrestartèinstall Few Runtime app’s like Adobe Flash/Shockwave/or any softwaresè install other apps like fonts/AV/Adobe/VPNClient/Customise Settings like Branding/look and feelèSet USMT Store options with /config: config.xml fileèRequest state StoreèRestore user storeèrun any custom configs like Lotus Notesèreleases state Storeè Enable Bitlocker encryption/Prepare Bitlocker Partition(c:\windows\system32\bdeHDcfg.exe -target default –quiet)èInstall any updatesèFinal Restart.

WAIK renamed to Windows ADK

Windows Automated Installation Kit (Windows AIK or WAIK) is a collection of tools
It has renamed to "Windows ADK" New name from Windows 8.

http://technet.microsoft.com/en-us/library/hh824947.aspx
 

PXE-E53: No boot filename received

PXE-E53: No boot filename received

everythink ok.. when checked
- Both the Boot Images are sent to WDS

Found one red Event in the application Events with event ID 258

executed below command to resolve the issue..

wdsutil /initialize-server /REMINST:"E:\remoteinstall"

PXE boot issue : DHCP.......................

We might get the error when trying to boot the client pxe boot as dhcp.......... Lot of dots with no dhcp ip to the pxe client...

Solution would be check the wds windows deployment service status or give a try to restart the service

Disable services on list of servers

Below script will be useful for disabling the services

'create a file called list.Txt
Set Fso = CreateObject("Scripting.FileSystemObject")
Set InputFile = fso.OpenTextFile("list.Txt")
Do While Not (InputFile.atEndOfStream)
sComputer = InputFile.ReadLine
aTargetSvcs= Array("WDSServer")
'For list of services use below...
'arrTargetSvcs = Array("service1", "service2", "service3")


Set oWMIService = GetObject("winmgmts:" & "{impersonationlevel=impersonate}!\\" _
 & sComputer & "\root\cimv2")
Set cServices = oWMIService.ExecQuery("SELECT * FROM Win32_Service")

For Each oService In cServices
 For Each sTargetSvc In aTargetSvcs
  If LCase(oService.Name) = LCase(sTargetSvc) Then
  
   If oService.State <> "Stopped" Then
    oService.StopService()   
   End If
   If oService.StartMode <> "Disabled" Then   
    oService.ChangeStartMode("Disabled")
   End If 
  End If 
 Next
Next
loop
MsgBox "Done"

 

Microsoft System Center products list

Microsoft System Center is a set of server products aimed specifically at helping corporate IT administrators manage a network of Windows Server and client desktop systems.

1.    System Center Advisor – Software as a service offering that helps change or assess the configuration of Microsoft Servers software over the Internet

2.    System Center App Controller - Unified management for public and private clouds, including cloud-based virtual machines and services

3.    System Center Configuration Manager – Configuration management, hardware/software asset management, patch deployment tools for Windows desktops (previously Systems Management Server)

4.    System Center Data Protection Manager – Continuous data protection and data recovery
System Center Endpoint Protection - Anti-malware and security solutions for Microsoft products

5.    System Center Essentials – Combined features of Operations Manager and Windows Software Update Service (WSUS), aimed at small and medium sized businesses
System Center Mobile Device Manager – Mobile device management (PDAs, smartphones, etc.)

6.    System Center Opalis - Opalis is an automation platform for orchestrating and integrating IT tools to decrease the cost of datacenter operations while improving the reliability of IT processes. It enables IT organizations to automate best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). Opalis operates through workflow processes that coordinate System Center and other management tools to automate incident response, change and compliance, and service-lifecycle management processes.

7.    System Center Orchestrator - (formerly Opalis) for orchestration and automation solutions

8.    System Center Operations Manager – Services and application monitoring

9.    System Center Reporting Manager

10.  System Center Service Manager – Ties in with SCOM, SCCM for asset tracking as well as incident, problem, change and configuration management (code name: Service Desk)

11. System Center Virtual Machine Manager 2008 R2 – Virtual machine management and datacenter virtualization

 

SMSTS.ini

Debugging for sccm logs with in the winpe to enable... use  SMSTS.ini  file.


 SMSTS.ini

During an OSD Task Sequence, when the PC boots into WinPE from the Boot Image, the SMSTS.log settings are not controlled via the same registry keys as in the full Windows OS. Instead the SMSTS.log settings are controlled via entries in a file called SMSTS.ini file which resides in the Windows directory of WinPE.
In order to change the logging options for the SMSTS.log file while in WinPE, the SMSTS.ini files has to be either created or modified with the appropriate parameters. If no SMSTS.ini file exists in the Windows directory of WinPE, then default values are used. By default, the SMSTS.ini file does not exist in the default Boot Images of ConfigMgr and therefore the default options are used.
The logging options and values that can be modified are:

DEBUGLOGGING
ENABLELOGGING
LOGLEVEL
LOGMAXHISTORY
LOGMAXSIZE

The value names are basically the same as the registry value names from the full OS, but without the preceding CCM prefix. Similar to logging in the full OS, for the purposes of the SMSTS.log and OSD, the only three parameters that usually are changed are LOGLEVEL, LOGMAXHISTORY, LOGMAXSIZE. The value of LOGMAXSIZE is specified in bytes.
To modify the values, in NotePad, create a SMSTS.ini file with a [Logging] section that contains the parameters that need to be modified. The file then needs to be injected in the Windows directory of the Boot Image. The SMSTS.ini file has to be in place BEFORE the Task Sequence begins in WinPE. For this reason, the SMSTS.ini file cannot be added or copied to the appropriate location as part of the Task Sequence.
For example, to change the SMSTS.log file size to 5MB, set the log level to the most verbose level, and increase the amount of rolled over/historical logs to 3, the following would be the contents of the SMSTS.ini file:

[Logging]
LOGLEVEL=0
LOGMAXSIZE=5242880
LOGMAXHISTORY=3

Note: The logging options in the SMSTS.ini file are case sensitive and should be entered in all uppercase.
Injecting the SMSTS.ini file into the Boot Image
ConfigMgr stores files to be injected into the Boot Images under the following two directories on the site server:

x86 Boot Images
\OSD\bin\i386

x64 Boot Image
\OSD\bin\x64

The files located in the above two directories are not necessarily automatically injected into the Boot images. An XML file is used which defines which files need to be injected, where the files are located within the BIN directory, and where they need to be copied to within the WinPE Boot Image. The name of this XML file is osdinjection.xml. It is located in the following directory on the site server:

\bin\i386

Please note that the above directory is NOT the same as where the files to be injected reside. Additionally only one osdinjection.xml file is needed for both x86 and x64 Boot Images.
To inject the SMSTS.ini file into the Boot Images:

1. Using NotePad, create an SMSTS.ini file with the desired parameters. When saving the file in NotePad, make sure it has the extension of .ini and not .txt.
2. Copy the SMSTS.ini file created in Step #1 into the appropriate directories on the ConfigMgr site server where the Boot Images are located. The file has to be copied to two separate directories - one for x86 Boot Image and one for x64 Boot Images.
   
   The directories to copy the file to are:
   
   \OSD\bin\i386
   
   and
   
   \OSD\bin\x64
3. Once the SMSTS.ini file is copied to the appropriate directories on the ConfigMgr site server, navigate to the following directory:
   
   \bin\i386
4. Create a backup of the file osdinjection.xml located in the \bin\i386 directory.
5. Open the original osdinjection.xml file in NotePad. Add sections to both the i386 and x64 portions of the osdinjection.xml file specifying to inject the SMSTS.ini file into the Windows directory of the x86 and x64 Boot Image:
• For the x86 Boot Image, find the section:
  
  
  false
  bin\i386
  sms\bin\i386

Add the following section immediately after the above section but before the line containing :


false
bin\i386
Windows

For the x64 Boot Image, find the section:


false
bin\x64
sms\bin\x64

Add the following section immediately after the above section but before the line containing

:


false
bin\x64
Windows

Save the osdinjection.xml file in NotePad.

In the ConfigMgr 2007 console, navigate to "Site Database" --> "Computer Management" --> "Operating System Deployment" --> "Boot Images".

Right click on the desired Boot Image to be updated with the SMSTS.ini file and choose "Update Distribution Points".

In the "Summary" page of the "Manage Distribution Points Wizard" window, click on the "Next >" button and allow the Boot Image to be rebuilt.

Once the Boot Image is finished rebuilding, in the "Wizard Complete" page of the "Manage Distribution Points Wizard" window, click on the "Close" button.

Repeat Steps 8-10 for each Boot Image in the environment.

Once the Distribution Points have finished updating for each Boot Image, each Boot Image should have the updated log settings for the SMSTS.log.
As an option, instead of using the above process, after the SMSTS.ini has been created, it can be manually injected into the Windows directory of the Boot Image using ImageX or DISM. However using the above process preserves and does not modify the original Boot Image (boot.wim), so it is the preferred method.

read here more for enable http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/12/how-to-change-logging-options-for-smsts-log-in-system-center-configuration-manager-2007.aspx

location of smsts.log file

Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log

Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log

Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log

After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log

After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log

How many Days Left to back you?

'PS: Days Left...

Wscript.Echo "Today Date MM-DD-YY: " & Date 
Wscript.Echo "Days Until ur Day in Months: " & DateDiff("m", Date, "24/4/2013")
Wscript.Echo "Days Until ur Day in Days: " & DateDiff("D", Date, "24/4/2013")
Wscript.Echo "Days Until ur Day in Weeks: " & DateDiff("w", Date, "24/4/2013")
Wscript.Echo "Hello..."

'write(DateDiff("m",fromDate,toDate,vbMonday))

All the Microsoft Updates Till Date

Here you can download all the list of updates from this link it will show from 1998 to TillDate... Auto Updated this excel sheet by Microsoft
http://go.microsoft.com/fwlink/?LinkID=245778

For more Security related info visit http://technet.microsoft.com/en-us/security/bulletin/

Enjoy..

Bulk SCCM Client Troubleshooting Approch

Site Name	Site 1	Comments
Discovery	What are The OU's Targeted? In AD	Are they missing any in OU's IN AD ??
From AD	In above Ou's Howmany Computers are there? (From AD)	may be a difference in SCCM vs AD
in SCCM	Now List howmany in SCCM	may be a difference in SCCM vs AD
Run the AD stale Computers Command	Use this link http://configmgr2oo7.blogspot.sg/2010/09/for-finding-90-days-old-computers-in-ad.html	Computers that are not connected in network or not logged on more than 90 means  computer not there in network and SCCM treats as Stale and it will not discover
Get the difference of computers(AD-StaleAD-in Totall SCCM)	Totall??
Now get the Totall non SCCM Clients show in your clients report and fix by using below two tools
Use these script to install the SCCM Client on remote computers
-remotly install on many systems once by using these scripts	http://configmgr2oo7.blogspot.sg/2009/01/sccm-client-installation-script-batch.html http://sccmcat.codeplex.com/	USE SCCM Client action tools ..need to configure the .ini file as per your requirement check the blog
- Single computer based tool	http://sourceforge.net/projects/smsclictr/	If it is a one computer use this tool
Catagorise the problems lile	Ping Online & offline computers with this script	to get the status of computes use this scrip may be usefull before you start work
WMI & Admin$ issues	http://configmgr2oo7.blogspot.sg/2008/11/wmi-connectivity-check.html	WMI & Admin$ is key to deploy clients
Once the clinet installation completed check the log	CCMsetup.log,execmgr.log, Clientidmanager.log	check the logs
	Check all these case's before start working http://configmgr2oo7.blogspot.sg/2010/03/client-troublshooting-checks-check-list.html

Virtual LAB Microsoft Page

All Virtual LABs http://technet.microsoft.com/en-us/virtuallabs/bb539977

Virtual LABS : System Center 2012 Configuration Manager

System Center 2012 Configuration Manager

• TechNet Virtual Lab: System Center 2012: System Center 2012 Orchestrator: Policy to Runbook Migration Tips
• TechNet Radio: Virtual Lab Insider - An Introduction to System Center 2012 Configuration Manager Video!
• TechNet Virtual Lab: Introduction to System Center 2012 Configuration Manager
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Role Based Administration
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Hierarchy Install
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Settings Management
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Application Management
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Content Management
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Managing Clients
• TechNet Virtual Lab: System Center 2012 Configuration Manager: OSD Bare Metal
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Advanced Software Distribution
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Basic Software Distribution
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Software Updates
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Endpoint Protection RC
• TechNet Virtual Lab: System Center 2012 Configuration Manager: Migrating from Configuration Manager 2007 to Configuration Manager 2012