Thursday, 26 March 2015

GLOSSARY OF TERMS

Reference

Description

AD

Active Directory

Apps

Applications

ASG

ASG Group

AV

Anti-Virus

BAU

Business As Usual

BOM

Bill of Materials

CPU

Central Processing Unit

CMPT

Component

Config

Configuration

CU

Cumulative Update

DFS

Distributed File System

DFS-N

DFS Namespace

DMZ

De-Militarised Zone

DNS

Domain Name Services

DP

Distribution Point

DR

Disaster Recovery

Gb

Gigabit

GB

GigaByte

Gbps

Gigabit per second

GC

Global Catalogue (server)

GHz

GigaHertz

GPO

Group Policy Object

HDD

Hard Drive

HP

Hewlett Packard

HTTP

Hyper Text Transfer Protocol

IIS

Internet Information Services

ILO

Integrated Lights Out

IP

Internet Protocol

ITIL

Information Technology Infrastructure Library

KB

KiloByte

LAN

Local Area Network

LDAP

Lightweight Directory Access Protocol

LTM

Logical Technology Model

Mb

Megabit

MB

MegaByte

Mbps

Megabit(s) per second

Med

Medium

MS

Microsoft

NIC

Network Interface Card

OU

Organisational Unit

OS

Operating System

OSD

Operating System Deployment

PC

Personal Computer

PDC

Primary Data Centre

PKI

Public Key Infrastructure

PM

Project Manager

PPTP

Point to Point Tunnelling Protocol

PTM

Physical Technology Model

PXE

Preboot Execution Environment

R2

Release 2

RACI

Responsible, Accountable, Consulted, Informed.

RAM

Random Access Memory

RDP

Remote Desktop Protocol

ROM

Rough Order of Magnitude

RPC

Remote Procedure Call

RPO

Recovery Point Objective

RTO

Recovery Time Objective

SAS

Serial Attached SCSI

SCCM

System Centre Configuration Manager

SCEP

Simple Certificate Enrolment Protocol

SCSI

Small Computer System Interface

SFF

Small Form Factor

SMB

Server Message Block

SOE

Standard Operating Environment

SQL

Refers to Microsoft SQL Server.

SSL

Secure Sockets Layer

TB

TeraByte

TBC

To Be Confirmed

UAT

User Acceptance Testing

USB

Universal Serial Bus

VLAN

Virtual LAN

VM

Virtual Machine

VMDK

Virtual Machine Disk

W

Watt

WAN

Wide Area Network

WID

Windows Integrated Database

WFM

Work Force Management

WSUS

Windows Server Update Services

 

Microsoft SQL Server ANTI-VIRUS EXCLUSIONS

Area

Folder / Process

File / folders to Exclude

SQL Server data files

E:\*

 *.mdf

       *.ldf

        *.ndf

SQL Server backup files

F:\*

        *.bak

       *.trn

Full-Text catalog files

D:\ Program Files\Microsoft SQL Server\MSSQL\FTDATA

         *.*

Processes to exclude

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\SQLServr.exe

 D:\Program Files\Microsoft SQL Server\ MSRS11.MSSQLSERVER\Reporting Services\ReportServer\Bin\ReportingServicesService.exe

 D:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER \OLAP\Bin\MSMDSrv.exe

 



Area

Folder / Process

File / folders to Exclude

SCCM 2012 R2

F:\SMS_ConfigMgr

·         Install.map

F:\SMS_ConfigMgr\Inboxes

*.adc, *.box, *.ccr,   *.cfg, *.cmn, *.ct0, *.ct1, *.ct2, *.dat, *.dc, *.ddr, *.i*, *.ins, *.ist,   *.job, *.lkp, *.lo_, *.log, *.mif, *.mof, *.nal, *.ncf, *.nhm, *.ofn, *.ofr,   *.p*, *.pcf, *.pck, *.pdf, *.pkg, *.pkn, *.rpl, *.rpt, *.sca, *.scd, *.scu,   *.sha, *.sic, *.sid, *.srq, *.srs, *.ssu, *.svf, *.tmp, *.udc

F:\SMSPKG

*.*

F:\SMSPKGF$

*.*

F:\SMSPKGSIG

*.*

F:\SMSSIG$

*.*

F:\SCCMContentLib

*.*

F:\SMS_CCM\ServiceData

*.msg,

 *.que,

*.xml

SCCM 2012 R2 Logs

F:\SMS_ConfigMgr \Logs

*.Log

F:\SMS_CCM\Logs

*.Log

SCCM 2012 R2 processes to exclude

·         F:\SMS_CCM\Ccmexec.exe

·         F:\SMS_ConfigMgr\bin\X64\Smsexec.exe

·         F:\SMS_ConfigMgr\bin\X64\Sitecomp.exe

·         F:\SMS_ConfigMgr\bin\X64\Smswriter.exe

·         F:\SMS_ConfigMgr\bin\X64\Smssqlbkup.exe

·         C:\WINDOWS\CCM\RemCtrl\CmRcService.exe

 

SCCM OSD

C:\Windows\TEMP\BootImages (and subfolders)

*.*

F:\ConfigMgr_OfflineImageServicing (and subfolders)

*.*

Servers to apply these exclusions;

 

SCCM 2012 R2 Anti-Virus Exclusions

SCCM Client Anti-Virus Exclusions

AV exclusions for all clients should be applied as described in the Microsoft knowledge base article http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/ and detailed in "

This should be included in the global AV client policy applied to all client machines in the environment.

Area

Folder / Process

File / folders to Exclude

SCCM Client

%windir%\ccmcache (and subfolders)

*.*

SCCM Client Anti-Virus Exclusions

 


Windows Anti-Virus EXCLUSIONS For SCCM 2012

Windows Anti-Virus EXCLUSIONS For SCCM 2012

AV Windows 2012 exclusions should be applied to all servers delivered by the project as described in the Microsoft knowledge base article http://support.microsoft.com/kb/822158 and detailed in "Table:  Windows Anti-Virus Exclusions".

Area

Folder

File / folders to Exclude

Windows Update or Automatic Update database files

%windir%\SoftwareDistribution\Datastore

·         Datastore.edb

Windows Update or Automatic Update log files

%windir%\SoftwareDistribution\Datastore\Logs

·         Edb*.jrs

·         Edb.chk

·         Tmp.edb

Windows Security files

%windir%\Security\Database

·         *.edb

·         *.sdb

·         *.log

·         *.chk

·         *.jrs

Group Policy user registry information

%allusersprofile%\

·         NTUser.pol

Group Policy client settings files

·         %SystemRoot%\System32\GroupPolicy\Machine\

·         %SystemRoot%\System32\GroupPolicy\User\

·         Registry.pol

 

1E Nomad Decisions - Design side with SCCM 2012

1E Nomad Decisions

·         1E Agent will be installed on the ConfigMgr 2012 Distribution Points and all PC Device endpoints.

·         Application and Software Update Packages must be enabled for 1E Nomad in ConfigMgr 2012.

·         1E Nomad settings will be enabled for Application and Updates in ConfigMgr 2012.

·         1E ActiveEfficiency database will be used to define the groups of subnets to be treated as a single location.

SCCM Server System Role Sizing Constraints

SCCM Server System Role Sizing Constraints

ConfigMgr 2012 R2 stand-alone primary server supports all site system roles on the same server, decisions to which role and how many are required within the stand-alone ConfigMgr 2012 R2 site depends on the number of devices the server will manage and features the site will support.

The following information about the support limits of each client-facing site system role.


Management Point Each primary site management point can support up to 25,000 computer clients and up to 10,000 Mac computer clients.


Distribution Point Individually, each primary site supports up to 250 distribution points and each distribution point can support up to 4,000 clients.


Software Update Point A software update point that is installed on the site server can support up to 25,000 clients. A software update point that is installed on a computer that is remote from the site server can support up to 100,000 clients.


Fallback Status Point Each fallback status point can support up to 100,000 clients.


Application Catalog Website Point Each instance of this site system role supports up to 50,000 clients, which provides service for the whole hierarchy.


Application Catalog Web Service Point Each instance of this site system role supports up to 50,000 clients.

SCCM Clients are not showing up in collection in Primary site

Problem:

==============

Clients are not showing up in collection in Primary site, Information:

================

1.     Central site's site code CEN

2.     Primary site server's site code = 'P01'  site with issue.

3.     A few more primary site, working fine.


Troubleshooting:

================

·         You informed he had to reinstall SCCM site in P01.

·         He now he can't see computer in a particular collection.

·         This collection was created in Central site.

·         Its a query based collection that pulls up clients based on OU membership.

·         We went back to P01 site and found the ADGroup discovery is not enabled.

·         And OU membership information is pulled with ADgroup discovery.

·         We enabled ADgroup discovery in P01,

·         It took about 10 minutes and showed completed in ADgrpdis.log

·         However when we updated the collection membership it showed only 67 clients.

·         We checked and found the client is there in all systems collection of P01 site.'

·         We checked the query and pulls information depending on OU and must be active.

·         WE found clients are active.

·         We decided to run query directly in WMI.

·         We went to Run and put "WBEMTEST" on P01 site sever

·         That opened up WMI tester

·         WE connected to "root\sms\site_<sitecode> and opened up Query and ran the query that was in Collection properties.

"select

SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSU

niqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from

SMS_R_System where SMS_R_System.SystemOUName =

"CORP.IRCO.COM/INDTECH/AGS/WORKSTATIONS" and SMS_R_System.Active = 1"

 

·         We could see about 856 Clients.

·         We updated the collection membership found 327 clients there as well.

·         In central site we could see about 340 clients however some client could be old.

·         We could also see clients getting advertisements.

Issues with DFSR Replication

Problem:

========
Issues with DFSR Replication.
Resolution
=========

Getting event ID's 5041,5012 & 4208, 4202 on DFSR Replication partner
Checked and found Staging Area was out of space, Suggested you to increase the size of the Staging path.
Restarted the DFSR Service on both the partners and waited for replication to happen.
we ran the DFSR Diagnostic Tool and found below hotfix missing and we installed the same

======================================================================
NOT INSTALLED 928569 FIX: The first CLR thread pool worker thread is never initialized...
NOT INSTALLED 931685 Files are copied over the network even though the versions of the...
NOT INSTALLED 933061 An update is available that improves the stability of the Windows...
======================================================================

More Information
===============

Managing DFS Replication -


DFS Replication Properties -

Windows Server 2003 R2: Branch Server Management – Distributed File System (DFS) Virtual Lab
US&CountryCode=US

Troubleshooting and Debugging the Branch Office Technologies