How to Identify the computers which has What version of BITS(Background intelligence Transfer service) installed onto it.

Background Intelligent Transfer Service (BITS) transfers files (downloads or uploads) between a client and server and provides progress information related to the transfers. You can also download files from a peer and it is Needed in

• Asynchronously transfer files in the foreground or background.
• Preserve the responsiveness of other network applications.
• Automatically resume file transfers after network disconnects and computer restarts.

To determine the version of BITS on the client computer,check the version of QMgr.dll. To find the version number of the DLL:

• Locate QMgr.dll in %windir%\System32.
• Right-click QMgr.dll and click Properties.
• Click the Version tab.

The following table lists the versions of BITS and their corresponding QMgr.dll file version numbers.

To get these details by SCCM client into Database for creation of collection or reports ,first you will have to do some changes to site settings for Software inventory Client Agent.

From site management—>client Agent—>software inventory client Agent Properties—>GO to Inventory collection Tab and click on start Burst to specify the File name which gives the File version for BITS.

Provide the name of the file as Qmgr.dll  and click on set for providing the location path where to search this file from.

click on Variable or Path and Type %windir%\System32 and unselect Subdirectories(you don’t want to search all the subdirectories for this file really). Clck ok and Uncheck Exclude Files in Windows Directory since we are looking for File which is from Windows Directory which should be included. click Ok to finish the configuration.

On the next policy interval,client should start receiving the new changes which you made for this agent and start collecting the DLL file details and sent to Site server.

Below is the collection Query to determine the BITS versions on the target computer.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on
SMS_G_System_SoftwareFile.ResourceId = SMS_R_System.ResourceId where
SMS_G_System_SoftwareFile.FileName = "qmgr.dll" and SMS_G_System_SoftwareFile.FileVersion > "7.%"

If your boss ask to get list of laptops which are managed by SMS or SCCM.what do you do and how do you get that. Right click on computer and go to resource explorer to identify the computer is Laptop or Desktop ?

You can identify if the computer is Laptop or Desktop based on its chassis Types.

Below are listed the Chassis types available to create SCCM collection or reports.

For Laptops Chassis Types : 8 , 9, 10, 11, 12, 14, 18, 21

For Desktop Chassis Type : 3, 4, 5, 6, 7, 15, 16

For server Chassis  Type: 23

Below is the collection to list all the computers which are laptops which fall in above Chassis type.

You can also replace the values with Desktop computers or servers also you can use joins to club these with AD groups for deploying the applications based on this.

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes in ( "8", "9", "10", "11", "12", "14", "18", "21" )

Here are some sample reports/queries available which you can make use of it

http://myitforum.com/cs2/blogs/snorman/archive/2007/09/18/count-of-chassis-types-by-collection.aspx

The Microsoft Enterprise Desktop Virtualization v2 Beta Refresh is now available for download on the Microsoft Connect site. The updated software provides fixes to customer reported issues and new features including Workspace packager updates which add additional options for customizing the MED-V computer names.

NOTE:  The MED-V_HostAgent_setup.exe replaces the MED-V client install MSI and the MED-V_WorkspacePackager_setup.exe replaces the MED-V console install MSI.   This change simplifies the install and deployment of these components as they now detect install the correct architecture in a single install.  All of the command line options provided for the MSI’s in the previous installs are still supported for these installers.”

The Guest Agent MSI no longer has to be installed by the administrator on the Windows XP image. The Guest Agent is now installed automatically as part of first time setup. For more information see the MED-V Release Candidate Release Notes.

Please read the release notes for important information about upgrading and the rename of the MED-V Installers.

 Release Candidate Release Notes 

 https://connect.microsoft.com/medv/content/content.aspx?ContentID=23311

Download Release Candidate software  :

http://connect.microsoft.com/medv/Downloads/DownloadDetails.aspx?DownloadID=32936

Wishing you all a merry time lighting up your Christmas Tree and A Happy New Year 2011.
Ciao you all in New Year 2011

Computers that are running on virtual(Virtual PC or VMware etc) will have an entry in win32_computersystem with attribute model in WMI.

You can create a collection to using table called SMS_G_System_COMPUTER_SYSTEM.

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,
SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System
inner join SMS_G_System_COMPUTER_SYSTEM on
SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId
where SMS_G_System_COMPUTER_SYSTEM.Model like "%Virtual%"

To list all physical computers ,create another collection using operator not in from above collection like below:

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System where SMS_R_System.ResourceId not in (select SMS_R_SYSTEM.ResourceID from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Model like "%Virtual%")

Hope it helps.

Create New SCCM collection and paste the below query into it.

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%" and SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC"

Also need report :look at here http://myitforum.com/cs2/blogs/skissinger/archive/2009/06/23/32bit-vs-64bit-report.aspx

Today I was looking at Packages to see how many packages are created without any distribution Points added. This might help you in identifying whether these packages are really needed to be in SCCM or

archive them. This below report will help you in achieving this.

select PackageID,Name,Version,SourceDate from v_Package where PackageID not in (select packageid from v_PackageStatusDistPointsSumm)

Note : Some packages might use just command line (script based) and they do not have any distribution Points . Double Verify them before you take any action)

If you have any issues with distribution of any packages to child sites or if you are in multi-tier hierarchy,You get face issues with packages not replicating to child sites due to several reasons and they will be retrying n (specific) number of times until they get right version of PCK file.

Preload is Our Friend to fix Package replication issues in better way. To know more about Preload Tool  and its usage http://blogs.technet.com/b/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx

How do you copy the PCK files ? Via Network Share ? sending them Via disk if you have large number of packages (this may happen when building new site) or different method ?

I use Robocopy oftenly if there are any Big Packages(more than 1GB or even less you can use) to copy even if there are any network breakage/Restart, it keeps retry.

Here is the syntax used to copy the PCK file.

robocopy sourcename Destination [Filename /Z

Ex: robocopy \\CM07\f$\smspkg  G:\smspkg\ Cen00C01.pck /z

/Z : copy files in restartable mode

To know more about Robocopy ,use Robocopy /?

Download Robocopy from here

Problem : Someone has Created package/Package’s (bulk) and distributed to sites/DP’s and these packages are in large size(more than 1GB).

You get notification from network Team or other teams about bandwidth issues.You may have to identify what packages are in process of sending to DPs and should also check how much % leftover to take further actions.(Stop sending the packages now and initiate it later sometime during night). You can also Use Senderanalyzer http://eskonr.com/2012/09/troubleshooting-sccm-configmgr-packages/ tool but sometimes packageID will be blank.

There are couple of logs and inbox folders to verify this.

Lets look at logs file first and then go with inbox folders to stop the sending files.

From sender.log :

when you create packages and send to child sites,package will be decompressed into .PCK and send which you can see from sender.log something like below :

Attempt to write 1048576 bytes to \\inhydcmS01.eskonr.com\SMS_SITE\2000OKA1.PCK at position 285944832

Wrote 1048576 bytes to \\inhydcms01.com\SMS_SITE\2000OKA1.PCK at position 285944832

Where KA1(2000OKA1.PCK) is sitecode from which the file is being generated and sending.

  2000O(2000OKA1.PCK) is the random generated number.

with the help of PCK file name,we can find what is the package ID from schedule.log.

Open Schedule.log on the server and search with PCK file name (2000OKA1) .You get something like below :

Send Request 2000OKA1 JobID: 00000018   DestSite: HY1   FinalSite:      State:  Pending   Status:            Action:    None   Total size:   3259244k   Remaining:   3259244k   Heartbeat: 21:41   Start: 12:00   Finish:   12:00   Retry:         SWD PkgID: ESK00006   SWD Pkg Version:   1

With this ,you can take necessary action whether you want to stop sending the package or continue it.

If you want to terminate /stop the files which are being transferred /Queue ,you can simply delete the job from schedule.box and its corresponding send request files ( this is not recommended way of doing it).

More about Understanding Site to Site Communication in SMS/SCCM ,you can refer steve rachui’s blog http://blogs.msdn.com/b/steverac/archive/2010/07/16/understanding-site-to-site-communication-in-sms-sccm.aspx

This is Continuation to previous post package archival process.up on the query results,I would not delete the packages from console directly rather i delete them from its assigned Distribution points and move them to Archive folder and let be there for sometime until for sometime incase if it is required.

If you have large number of packages,you may find difficult in moving the packages by identifying where they reside (if you have subfolders).If you have less packages <10,you may use the report to know the root path of the package  and then right click on the package Move to archive folder by appending Retired to the existing package name to know package is retired.

If you have multiple packages,moving one by one is not easy thus you require something like script or tools.

Moving package using script may require to get the Source folder ContainerID number of  the packages(Folder of the package)  and Destination Folder ContainerID(Archival folder ID).

Here is the SQL query for the list of moving packages to know their Source Folder ContanerID.

From the package clean up report,if you get multiple packages,just place them in IN condition separated by comma (,).

I have packageID cen00004 which i need to move to archive folder with containerID=4 from SQL query below

select  B.ContainerNodeID,B.NAME,A.InstanceKey from dbo.FolderMembers a,.dbo.Folders b where
a.ContainerNodeID=b.ContainerNodeID and b.Name like ‘%archive%’

Replace the folder name if you have other one.

Now we have list of packages with their source ContainerNodeID(which is nothing  but the package FolderID).

Create a VB script with below syntax with input of all package IDs separated by commas with their source folder and destination folder.

Note : Please replace quotes (‘”) as they are replaced by fancy.

Option Explicit
‘On error resume next

Dim strSMSServer, strSMSSiteCode, strPackageIDs
Dim intSourceFolder, intDestFolder, intObjectType
Dim loc, objSMS
Dim objFolder
Dim arrPackageIDs
Dim retval

strSMSServer   = "SCCM server Name"
strSMSSiteCode = "SiteCode"
strPackageIDs  = inputbox("Please input packageIDs separated by commas","List of packages to be moved")

intSourceFolder =inputbox("Please input Source folder ContainerID number", "Source ContainerID")  ‘This ID is what you see in above SQL query to move all packages from the same folder test =1.
intDestFolder   =4 ‘Destination Folder for Archived packages :In this case,My archive package folder is 4.

intObjectType   = 2  ’2=Package for type of object .This scripts works only for standard software distribution packages.

Set loc         = CreateObject("WbemScripting.SWbemLocator")
Set objSMS      = loc.ConnectServer(strSMSServer, "root\SMS\site_" & strSMSSiteCode)

Set objFolder = objSMS.Get("SMS_ObjectContainerItem")
arrPackageIDs = Split(strPackageIDs, ",")

retval = objFolder.MoveMembers(arrPackageIDs, intSourceFolder , intDestFolder , intObjectType)
If Err.Number <> 0 Then
    msgbox Err.Description
End If

MSGBOX "Script is completed"

You may get multiple packages with different source Folders.So you will have to run the script to move bulk packages from each source folder to Destination at one go.

It is better than moving one by one package each time.

Hope it helps!

Quick Update from Microsoft about System Center 2012 R2 Preview is available for Download from MSDN /Evaluation(below).

This prerelease version is not supported in a production environment and is for testing only. 

This prerelease version does not support an upgrade from previous versions of System Center 2012 Configuration Manager. Install this prerelease version as a new installation of Configuration Manager. In addition, Configuration Manager does not support the import of objects between different versions of Configuration Manager.

To know more about Release notes and Known Issues with SCCM 2012 R2 Preview Release http://technet.microsoft.com/library/dn236347.aspx

I have just extracted all the direct download links for the System Center 2012 R2 components that will save time without Sign in Required.

Content is in Size 680 MB after Unzip.

Download the Evolution products directly using below links.

Download Configmgr / SCCM 2012 R2 from here

Other System Center 2012 R2 Components are

Download SCOM 2012 R2 from here

Download SCVMM 2012 R2 from here

Download SCSM 2012 R2 from Here

Download SCO 2012 R2 from here

Download SCDPM 2012 R2 from Here

Download SCAC 2012 R2 from Here

Download Windows server 2012 R2 from Here

Update: David oBrien blogged about New Features about SCCM 2012 R2 (whats new in SCCM 2012 R2) http://www.david-obrien.net/2013/06/25/configmgr-2012-r2-whats-new/

For more information check http://www.microsoft.com/en-us/server-cloud/system-center/system-center-2012-r2-configuration-manager.aspx

To know more about what’s new in SCCM 2012 R2,read Henks blog http://henkhoogendoorn.blogspot.de/2013/06/updates-and-new-features-in-configmgr.html

By Default,Client Cache information is not collected by Configuration Manager.You should do some customizations to get it working.

This blog post talks about how to create Custom MOF file and import into SCCM as custom hardware inventory class which will be applied onto clients as policy to get the information from WMI .

Save the below code into file with file_name.mof.

[ SMS_Report (TRUE),
  SMS_Group_Name ("SMS Advanced Client Cache"),
  SMS_Class_ID ("SMS_ADVANCED_CLIENT_CACHE"),
  Namespace ("\\\\\\\\.\\\\root\\\\ccm\\\\softmgmtagent") ]
class CacheConfig : SMS_Class_Template
{
    [ SMS_Report (TRUE), key ]
    String     ConfigKey;
    [ SMS_Report (TRUE) ]
    Boolean     InUse;
    [ SMS_Report (TRUE) ]
    String     Location;
    [ SMS_Report (TRUE) ]
    UInt32     Size;
};

Note:Please Replace the Quotes (‘”) ,blog converts them to fancy.

Open Configmgr 2012 Console,Move onto Administration pane—>Client Settings ,you see Default Client settings.

Note :Don’t try to do it on custom client hardware inventory settings which you have created ,If you do so,it will not work.

Below is error code what you get if you try to import to Custom hardware inventory settings.

“The following classes for which you are trying to import settings do not exist.  Import the required class definitions and then try to import the settings again.”

Always import /Add the custom hardware inventory classes onto Default Client settings .These changes will be automatically flow into Custom client hardware inventory settings.

Click on Set Classes and then Click on Import

Select the MOF file that we created above.

Select what is required for you.

Monitor dataldr.log on the site server if these changes successfully processed or not ?

From above we conclude that,these changes are inserted into Database.

You can also verify from UI ,select what fields you required and what not .

From the SCCM client machine,you see the following changes when the hardware inventory schedule runs:

Inventoryagent.log

Below is the collection, you can create to know how man clients do not meet the required cache size.

select *  from  SMS_R_System inner join SMS_G_System_SMS_ADVANCED_CLIENT_CACHE on SMS_G_System_SMS_ADVANCED_CLIENT_CACHE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SMS_ADVANCED_CLIENT_CACHE.Size < 10240 

Thanks to MOF Master Sherry for providing the MOF file.

#SCCM / #Configmgr How to get Client Cache Size using MOF file for Reporting is a post from: Eswar Koneti's Blog

Various tools,scripts are available to add,delete and refresh packages(Standard software Packages only) on the Distribution Points but i feel this is easy to compare with others what i have seen so far in Configuration Manager 2007.

If you have single package to do any specific action like add,delete ,refresh ,you can do it Via Console but what if you build new site and you are required to add the bunch of packages in SCCM 2007,do it Via Console or Script based ?

I will be using tool called dpmod written by Bernard White in a batch script with the help of excel sheet.

This process requires 3 files to be in one folder. 1)dpmod.exe 2)add.bat and 3) run_add.bat

–> Download the installer file,Run it to get dpmod.exe.

–> For a single package to take action,you can do with command line:

dpmod.exe  -addpkg PRI00001 \\INCHDP01 -sdk INHYCM01

PRI00001=PackageID

INCHDP01=Target site to receive Packages.

INHYCM01=Central Site where packages Created.

3.For multiple packages,you can not add line by line to the batch file as we did above

How to achieve it in simple way?

You can Download the excel sheet from here and change the values for PackageID,Target Site and Central /Primary Site to get batch script.

If you have multiple packages for multiple sites,you can add them to excel sheet .

Take the last column “batch script results” and paste it into add.bat

Create 3rd file which is run_add.bat with following command:

cd D:\Tools\Dpmod

D:

add.bat >>.\add.log

You are done now. when you execute run_add.bat ,it will create log file for you with results which package has been added and which not.

You can also do the same for refresh package,delete package for multiple packages on multiple sites at one Go.

SCCM Configmgr Script Tool Add Delete Refresh packages on Distribution Points is a post from: Eswar Koneti's Blog

Are you Migrating your Existing SCCM /Configuration Manager Infrastructure to Configuration manager 2012 ,if so, You will have to look at your Packages whether  they UNC path or Local Drive Path since Migration of Packages using Local Drive(Non UNC) can not done.

Before you Migrate the Packages from CM07,you will have to ensure all of them are using UNC Path.

How to Know which are Local Drive ?

Here is Simple SQL query /SCCM report to know how many packages not using UNC Path.

select PkgID,Name,Version,Language,Source from SMSPackages where Source not like ‘\\%’ and Source not like ”

Note:Please change the quotes,they are converted to fancy by Blog.

To change the Drive letter to UNC path,you can either use Coretech Tool or Scripting methods to update it.

The Consequences changing the Source Path:

You need to test and plan these package sources updates. Updating a package source will start a package update on all the distribution points. For even a medium size site this can take several hours.

SCCM 2012 Migration Report Packages not using UNC Path is a post from: Eswar Koneti's Blog

Testing the basic Functions of Newly Build Configuration Manager 2012 primary and Secondary Sites by its SCCM clients to see if they work or not.

Have installed Configuration manager client on windows 7,windows 8 and server OS .Created Configmgr 2007 toolkit V2 package,distributed to DP’s and deployed to these machines.

Did Machine Policy on the clients,new application shown in Software Center,till now everything is good as expected.

When i look at the status of this app from Software Center,it failed.Why ? Download of Content did not happen.

Next is to look at DataTransferService.log records all BITS communication OR Package Access relation issues.

I find something in Red Color.

Error sending DAV request. HTTP code 600, status ”

GetDirectoryList_HTTP mapping original error 0x80072efe to 0x800704cf.

failed in winhttpreceiveresponse API Errorcode=0x2efe

successfully sent location services HTTP failure message

What does the above error codes mean?

0x80072efe/0x2efe:The connection with the server was terminated abnormally

0x800704cf:The network location cannot be reached. For information about network troubleshooting, see Windows Help.

With the above error codes,we can predict ,client had some issues connecting to DP server to download the content.

Note:I am  using Custom port (CCMHTTPPORT:port that the client should use when communicating over HTTP to site system servers) rather default port 80 while installing SCCM client.

I did telnet from client to DP server to see if it works (by default telnet is not enabled win 7 and later OS,you will need to enable it from programs and features) but failed to do so. Tried self telnet on DP server,it works.

Issue seems to be Firewall which is blocking the communication on custom port from clients.

Solution:

You will have to add the custom port (ccmhttp) to the firewall (if it is enabled) on windows server to allow communication from clients.

Follow the TechNet Guide how to add port to windows firewall http://technet.microsoft.com/en-us/library/ms175043.aspx

If you are running on windows server 2012,Use the batch script to fix it.

@echo =========  ccmhttpport  ===================
netsh advfirewall firewall add rule name = "ccmhttpport 800" dir = in protocol = tcp action = allow localport = 800 profile = DOMAIN

Telnet works good now.

Back to Client workstation,,Control panel,Configuration Manager applet–>Trigger Application Deployment Evaluation Cycle

Run the application now from Software Center, It ran.

Long Story but Simple Fix

SCCM Configmgr 2012 Clients failed to download Content using Custom Port “Error sending DAV request. HTTP code 600” is a post from: Eswar Koneti's Blog

In My Previous post,I blogged about SCCM Report list packages that do not use UNC path (i.e package Uses local Drive) and this is not good if you are migrating the packages from SCCM 2007 to Configuration Manager 2012.

After you get list of packages that use local drive,you will have to change them to UNC .

Note: This script will change the source path from Local drive(D:) to UNC path(\\servername\) for all the list of given packages at one Go.

For ex: Current pkg source path: D:\applications\adobe 9.2 Eng ,change to UNC: \\servername\applications\Adobe 9.2 Eng

If you have different UNC path for each package and not same what i have, modify the script.

You can either use custom Tools like package source changer from coretech OR Powershell or other scripts.

I wrote Simple Script that works only for Standard Software Distribution Packages but not for Software Update /OSD/ Driver packages.

Pipe the list of packages from the report to pkgs.txt.

strComputer = "SCCM Server name"

Set objfso = CreateObject ("Scripting.filesystemObject")
Set pkgs = objfso.OpenTextFile ("C:\pkgs.txt", 1)
Set outputList = objfso.OpenTextFile ("C:\outputList.txt", 2, True)

Do While Not pkgs.AtEndOfStream
pkgName = pkgs.ReadLine

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\SMS\site_CEN")

Set colItems = objWMIService.ExecQuery( _
    "SELECT * FROM SMS_Package WHERE PackageID = ‘" & pkgName & "’")

For Each objItem in colItems
‘        Wscript.Echo "PkgSourcePath: " & objItem.PkgSourcePath
outputList.WriteLine pkgName & vbTab & "Old Path"& vbTab & objItem.PkgSourcePath

tmp = replace((objItem.PkgSourcePath),"D:", "\\servername") 
objItem.PkgSourcePath = tmp
  objItem.put_

outputList.WriteLine pkgName & vbTab & "New Path" & vbTab & objItem.PkgSourcePath

Next

loop

After you change the package source path,packages will start updating on all the Sites where ever it was targeted previously.So please be careful while doing this task because of network traffic.

Hope it helps!

SCCM Configmgr 2007 Replace Source Package path from Local Drive to UNC path for list of packages is a post from: Eswar Koneti's Blog

In this blog post,we are going to see how to manage workgroup computers using SCCM Configmgr 2012. The procedure involves working with lmhost and host files on both sccm server and work group machines.

Technet library is not so clear on how to manage workgroup computers http://technet.microsoft.com/en-us/library/bb680962.aspx.

In my earlier post,we saw how to manage work group computers using SCCM Configmgr 2007.http://www.windows-noob.com/forums/index.php?/topic/2029-managing-workgroup-computers-in-sccm-sms-environment/

Before installing SCCM client on workgroup machines,we do some configurations on the workgroup computer.

If you are managed workgroup computer using previous versions earlier ,you find the steps more or like same.

Do the below steps on Work Group.

Disable the Firewall,If you don’t want to disable,allow the required ports http://technet.microsoft.com/en-us/library/hh427328.aspx

Go to the control Panel–>Network Connections–>Local Area Network
Go to Internet TCP IP Protocol .Click on Properties—> click on Advanced —>Go to DNS Tab .
add the DNS suffix as shown below.

Next to DNS,WINS Tab,select ‘Enable NetBIOS Over TCP\IP

Next Go to C:\Windows\System32\drivers\etc

open lmhost file with admin rights using notepad

copy the below lines to the host file

192.168.1.10 SGCMCEN                        #PRE
192.168.1.10 "MP_PRI         \0x1A"      #PRE

Where SGCMCEN is SCCM site name and PRI is Site code

Make sure you have 20 characters (Including blank Spaces) between the quotes .

Note:am not adding SLP entries to lmhost file since SLP is integrated into MP in CM12.

save as “lmhost” in C:\Windows\System32\drivers\etc

open cmd with admin rights again and run the below commands

nbtstat –R

nbtstat -c

You see the changes are loaded into cache.

Next is to have local administrator Account for remote control using SCCM 2012 .If you do not have this account,remote control will not work.

Now we are done with the required changes for the client installation.

Copy the sccm client installation files to local drive on work Group machine.

Run the command prompt with local admin rights .

use the below command to install sccm client.

ccmsetup.exe /source:C:\client SMSSITECODE=PRI SMSMP=sgcmcen.cm12lab.com DNSSUFFIX=cm12lab.com

monitor ccmsetup.log from C:\Windows\ccmsetup\Logs

notice from ccmsetup.log installation is completed.

lets look at configuration manager applet from control panel

go to Site and try to discover the site to see if it work or not

look at Actions Tab if all the agents are loaded or not

This is because ,client is not approved in SCCM yet.

go back to console and approve it.

Right click on the computer and approve.

Go back to the client,see if you see more than 2 actions or not.

If you have issues appearing the client in console,you will have to check clientIDmanagerStartup.log,clientlocation.log and locationservices.log

Till now we find to manage the Workgroup SCCM client is able to communicate MP,getting policies etc.

Now we see if Application Deployment,Remote Tools and Other functions work not.

Try to create simple application or if you already have any ,Deploy it to workgroup computer.

Note: Make sure you configured Network Access Account to access resources from domain for the workgroup computer.

I deployed 7zip application and it appears in software center.

run the installation

You see it is successfully ran.

same way,you can also deploy software updates,packages and what else you can,Do it.

What next ,Remote Control ?

For this to happen,you need to add the workgroup IP address,hostname in your sccm server host file(C:\windows\system32\drivers\etc\hosts

After you do this,try to do remote control of the Workgroup computer from sccm console,you get prompt for authentication since domain cred wont work.

workgroup hostname\administrator and password.

On the workgroup computer,you see something like this ,you can change the settings to not ask user permission in client agent settings.

Hope it helps!

SCCM Configmgr 2012 Manage Workgroup Computers for Deployment,Remote tools etc is a post from: Eswar Koneti's Blog

By Default,Configuration Manager 2012 will create publish the reports to Configmgr_SiteCode (Ex:Configmgr_P01) Folder in Report Manager if you have not changed the default path name while installing Configuration Manager.

How do i Deploy the Custom reports to my Own Folder in Configmgr 2012 ?

In this blog post,I will show you how to create Custom Folders and publish reports to them.

For this post, I have created 2 folders one is custom reports\Eswar under Configmgr_P01 and other is Custom.

Note: Reports what you create and publish to Default path(Configmgr_sitecode) can be seen from the SCCM console,other reports which are outside of this default path(Configmgr_sitecode) can not be seen from Console.You should move them later to Configmgr_Sitecode folder if at all you need them.

In this blog post,I will be using tool called BI for Visual Studio to create SSRS reports and publish them to report server.You can also upload the RDL which is created using the the BI tool into report server.

While publishing reports using the tools to report manager ,you basically need to have 2 elements 1) Targetreportfolder  2)TargetServerURL

I have created report called Status of All Packages using Visual Studio 2010.

How to Deploy /Publish :

Note:This is One time Activity for each project to deploy reports.If you think,these reports should be published to other folders,try to edit it again.If you are creating reports under the same project name,no need to edit every time .

Right click on report project what you have created and select properties.

If you are not able to see the project,go to View—>Solution Explorer

Right Click on the project (Shared DS):

TargetDataSourceFolder: If you are using SharedDataSource then you need to have the folder name to publish it otherwise you can leave it as Default . I prefer not to use Shared Datasource.

TargetreportFolder:This is where your reports can be seen from the Target manager.give the path as Configmgr_PRI\custom reports\Eswar .If you want to publish to Custom Folder,Use Custom name.

TargetserverURL: http://SCCMServername/reportserver

After you are done with it,go back to the solution Explorer,right click on the report you want to publish–>Deploy

you can see the status of this report,whether it is deployed or not using output window.

go back to your report manager ,check if the reports are published or not ?

How to create Custom Category folder in SCCM Configmgr 2012 console http://eskonr.com/2013/01/how-to-create-new-category-folder-in-sccm-configmgr-2012-reports/

How to change the SSRS DataSource:  http://be.enhansoft.com/post/2010/08/26/How-to-Change-the-SSRS-Datasource.aspx

SCCM Configmgr 2012 :How to deploy / Manage reports to specific Folder in report Manager is a post from: Eswar Koneti's Blog

Inventory report for laptops who have webcam feature ?

You can use this report both on SCCM 2007 and Configmgr 2012 Environment.

select cs.name0 [Computer name],
cs.username0 [Last loggedin User],
os.Caption0 [OS],os.InstallDate0 [OS Installed Date],
cs.Manufacturer0,cs.Model0 ,
WS.LastHWScan [Reported Date to SCCM]
from v_GS_COMPUTER_SYSTEM cs,v_GS_SYSTEM_ENCLOSURE se,v_GS_OPERATING_SYSTEM OS,  v_GS_WORKSTATION_STATUS WS
where cs.ResourceID=se.ResourceID and
cs.ResourceID=OS.ResourceID and
cs.ResourceID=WS.ResourceID and
se.ResourceID in (select ResourceID from v_GS_SYSTEM_DEVICES where Name0  like ‘%camera%’ or Name0 like ‘%webcam%’)
and SE.ChassisTypes0 in ( ’8′,’9′,’10′,’11′,’12′,’14′,’18′,’21′)
group by cs.Name0,cs.UserName0,cs.Manufacturer0,cs.Model0,OS.Caption0,OS.InstallDate0,WS.LastHWScan

Note: There reports are created for for Dell and Lenovo models only.Webcam name differs from manufacture to manufacture,so if you have other models like hp,ThinkPad etc,you should look at resource explorer—>hardware –>system devices for the webcam name.

Who do not have: use Not in syntax:

select cs.name0 [Computer name],
cs.username0 [Last loggedin User],
os.Caption0 [OS],os.InstallDate0 [OS Installed Date],
cs.Manufacturer0,cs.Model0 ,
WS.LastHWScan [Reported Date to SCCM]
from v_GS_COMPUTER_SYSTEM cs,v_GS_SYSTEM_ENCLOSURE se,v_GS_OPERATING_SYSTEM OS,  v_GS_WORKSTATION_STATUS WS
where cs.ResourceID=se.ResourceID and
cs.ResourceID=OS.ResourceID and
cs.ResourceID=WS.ResourceID and
se.ResourceID not in (select ResourceID from v_GS_SYSTEM_DEVICES where Name0  like ‘%camera%’ or Name0 like ‘%webcam%’)
and SE.ChassisTypes0 in ( ’8′,’9′,’10′,’11′,’12′,’14′,’18′,’21′)
group by cs.Name0,cs.UserName0,cs.Manufacturer0,cs.Model0,OS.Caption0,OS.InstallDate0,WS.LastHWScan

SSRS Report:

To create collection,follow the blog post how to create http://eskonr.com/2010/11/sccm-collection-to-list-all-the-laptop-computers-2/

SCCM Configmgr report:Inventory for Webcam Devices ? is a post from: Eswar Koneti's Blog

Microsoft just released Cumulative Update 3 for System Center 2012 Configuration Manager (Configmgr) SP1.This update fixes issues on OSD,Powershell,Software Distribution,Windows In tune,Endpoint Protection,Site Systems,Reporting,Software Updates.

Supported Platforms:

This update adds support for Windows 8.1-based client computers in Microsoft System Center 2012 Configuration Manager Service Pack 1. Windows 8.1 is added to the supported platform list for the following features:

• Software distribution
• Software update management
• Compliance Settings

To download the Update and know more about issues that are fixed,Please refer http://support.microsoft.com/kb/2882125.

Note: This update do not require Restart.

SCCM Configmgr 2012 SP1 CU3 is available to Download is a post from: Eswar Koneti's Blog