We all know about what is SCCM client center tool and what it does.

Roger Zander who has developed this application (SCCM Client Center) basically to troubleshoot SMS/SCCM 2007 Client related Issues.This also provides lot many features to troubleshoot all kind sccm client related issues more http://sccmcat.codeplex.com/.

Download Client center Tool for Configuration manager 2007 from http://sourceforge.net/projects/smsclictr/

Download download Client center Tool for Configuration manager 2012 http://myitforum.com/cs2/blogs/rzander/archive/2012/05/22/client-center-for-configuration-manager-2012.aspx

How do you run this tool with different user if logged in account do not have enough rights?

You can run this tool by holding alt+Shift to get run as different user but every time I do not prefer to go with this option rather I save the credentials (multiple Accounts you can do I suppose) on the tool

so when ever you launch the tool,you can select which account do you use to connect to target computer.

From your sccm client center tool,on the right top corner you see options—>select User

Enter the Username and Password and click Save Button. This way you can save multiple Accounts to connect to target computer if logged on user do not have enough rights.

Close the Tool and Reopen it again to select the authentication to connect to target computer.

Select the Account to connect to Target Computer

Until Next !

Summary:

In this post, Chris focused on helping many of us get started in testing your environment by not requiring you to do it against your packages/programs.   Instead, Chris provided you with files you can use to test PCM and get familiar with it.  This will allow you to go through the various scenarios that PCM solves for you.

In the past few months, we’ve received a lot of requests to help many of you focus on “testing” the new Package Conversion Manager (PCM) that is available in the Microsoft Download Center.  It is rather trivial to actually download PCM and install in your production environment yet for many it is very scary to do so.  You *can* safely do this without concerns as we do not modify any System Center Configuration Manager 2012 database settings during install.  Instead, we simply update the Administration Console to enable the functionality.  The backend database pieces are part of Configuration Manager 2012 that you received already.  As such, we reference PCM as a Configuration Manager 2012 Feature Pack.

In today’s post, I want to help many of you get started by providing you some files that will import some basic packages/programs into your Configuration Manager 2012 system.  Beyond this, I wanted to enable you to test our collection intent functionality enabling you to easily move WQL query targets to the new Application Model’s Global Conditions & Requirements.

Lastly, I’ve also attached a tool (PPDAC) that allow you to easily “clean” the system and run through various times to get the hang of it.  This tool is available as-is and isn’t supported by Microsoft.

Read the complete post on Chris Blog http://blogs.technet.com/b/chrad/archive/2012/10/07/kicking-the-tires-for-configuration-manager-2012-s-package-conversion-manager-pcm.aspx

Client Center tool is designed for IT Professionals to troubleshoot SCCM/CM12 Client related Issues. The Client Center for Configuration Manager provides a quick and easy overview of client settings, including running services and Agent settings in a good easy to use, user interface.

Here you go with Client center Beta Version : http://sccmclictr.codeplex.com/

when you try to install this app, It always connects to Internet to install the app else will Fail.

How to use this application without connecting to Internet ?

On the Computer where you installed the click once application,files resides on the below path.

Go to the computer where the application is installed and look for this path.

C:\Users\Username\AppData\Local\Apps\2.0\VXYT5QN6.KNV\R4TKLVQN.5TR\sccm..tion_0000000000000000_0000.0000_5f09e27d38cfe83a\

Create Shortcut for SCCMCliCtrWPF.exe and use it.

P.S:Red indicates they are replaced.

Thanks to John Marcum.

Connecting to Resource Explorer of Computer is always not good(takes time) to Search for computer in SCCM collection

and move further.Some times you may not find the computer in the collection where you are looking at then you comeback

and look in All desktops and servers which may take time  to load all computers and then offers you to search for computer.

Come up with Simple Batch script that prompt you to enter Computer name and it takes you to Resource Explorer of Computer.

You may require to edit the fields in Red Color for SCCM Installation Folder,SCCM server name and sitecode

:start
@echo off
CLS
Title Resource Explorer By ESKONR
> temp.vbs ECHO WScript.Echo InputBox( "To which Computer would you like to connect?", "Resource Explorer by ESKONR", "Enter Computer Name" )
FOR /F "tokens=*" %%A IN (‘CSCRIPT.EXE //NoLogo temp.vbs’) DO SET dator=%%A
DEL temp.vbs
F:
cd \SCCM\AdminUI\bin
SET var=’%dator%’
start resourceexplorer.msc -s -sms:ResExplrQuery="SELECT ResourceID FROM SMS_R_SYSTEM WHERE NAME = %var%" -sms:connection=\\%SCCM SERVER%\root\sms\site_%SITECODE%
exit
:end

Thanks to my Old Friend Marcus!

Until Then!

In My Previous post , we get to connect Resource Explorer of Computer without Using SCCM Console in SCCM 2007.http://eskonr.com/2012/12/sccm-configmgr-2007-open-resource-explorer-without-sccm-console/

You can use the same script for sccm 2012 but with littlie changes to the folder names and File names.

Here is the Batch script to connect to resource Explorer of Client Computer in SCCM 2012 without Launching SCCM 2012 Console.

Change the Values in Red Color.

:start
@echo off
CLS
Title Resource Explorer by ESKONR
> temp.vbs ECHO WScript.Echo InputBox( "To which Computer would you like to connect?", "Resource Explorer By ESKONR", "Enter Computer Name" )
FOR /F "tokens=*" %%A IN (‘CSCRIPT.EXE //NoLogo temp.vbs’) DO SET dator=%%A
DEL temp.vbs
F:
cd \SMS\AdminConsole\bin
SET var=’%dator%’
start resourceexplorer.exe -s -sms:ResExplrQuery="SELECT ResourceID FROM SMS_R_SYSTEM WHERE NAME = %var%" -sms:connection=\\Server\root\sms\site_%Sitecode%
exit
:end

Until Next!

Just saw an Email update from Myitforum list about the Release of Configuration Manager 2012 Automation RC is out now.

Few months back,he announced the release of Configmgr 2012 Automation Beta here.

To know more about what does the scripts do, http://wmug.co.uk/wmug/b/dotraphael/archive/2012/09/28/project-cm12-automation-beta-is-coming.aspx

To Download the scripts http://cm12automation.codeplex.com/releases/view/100135

Raphael is working on uploading the videos on YouTube on this also he will update his blog page once everything is there…

Hope you like it !

Long ago ,written SCCM report to list packages not used for 6 months as part of Package Archival process http://eskonr.com/2012/11/sccm-configmgr-package-archival-process-cleanup-activity/ .This report tells you to take further action to clean or move to Archive folder to wait for some more months before it goes for Deletion.

What next ? Delete these packages from Assigned DPs to get some disk space ?

You may find several scripts to do this task on the internet but, i  find this is easy for me to get this activity done.

Identify list of package which you want to remove ,pipe them to notepad .You can do more customizations if needed.

‘Script to delete packages from its assigned Distribution Points.

strComputer =inputBox("Please Enter the SMS provider OR Site where the packages are created" , "SCCM Server name")
Set FSO = CreateObject("Scripting.FileSystemObject")
Set packages=fso.OpenTextFile("C:\PACKAGESTODELETE.txt",1,true)
Set objoutputfile=fso.OpenTextFile("C:\DP_results.txt",2,true)

Do While packages.AtEndOfLine <> True
    ‘read the next line
    package = packages.Readline

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\SMS\site_CEN")
if err.number<>0 then
    msgbox "server connection failed"
    wscript.quit
end if
Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_DistributionPoint where packageid=’" & Package & "’")
For Each objItem in colItems
        ‘Wscript.Echo "ServerNALPath: " & objItem.ServerNALPath
objoutputfile.WriteLine ( package & vbTab & " will be deleteting from" & VBTAB & objItem.ServerNALPath)

objitem.Delete_

If Err.number <> 0 Then

objoutputfile.WriteLine ( "Failed to delete" & vbTab & package & "from" &  vbTab & objItem.ServerNALPath)
      End If
    Next

loop

msgbox "Done"

Note: Please Replace the quotes.

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

In SCCM 2007 ,to initiate machine policy /hardware inventory and other actions on client,we use vb script/wmic/Powershell/Right click Tools and other tools like Client center,collection commander etc.Some organizations do not like to install any of these tools thus only use script to achieve it.

The most common Script that is used to trigger policy agent on SCCM 2007 clients remotely is blogged here

In Configuration Manager 2012,we have something called fast channel (Client notification) to download Machine Policy.

If you are looking for something similar for CM12 what we performed on SCCM 2007 clients remotely,you can use below Vb script.

The below VB script is written to Trigger Hardware inventory agent on clients:

‘Declare Variables
On Error Resume Next
Set sho = CreateObject("WScript.Shell")
strSystemRoot = sho.expandenvironmentstrings("%SystemRoot%")
strCurrentDir = Left(Wscript.ScriptFullName, (InstrRev(Wscript.ScriptFullName, "\") -1))
‘ Get a connection to the "root\ccm\invagt" namespace (where the Inventory agent lives)
Dim oLocator
Set oLocator = CreateObject("WbemScripting.SWbemLocator")
Dim oServices
Set oServices = oLocator.ConnectServer( , "root\ccm\invagt")
‘Reset SMS Hardware Inventory Action to force a full HW Inventory Action
sInventoryActionID = "{00000000-0000-0000-0000-000000000101}"
‘ Delete the specified InventoryActionStatus instance
oServices.Delete "InventoryActionStatus.InventoryActionID=""" & sInventoryActionID & """"
‘Pause 3 seconds To allow the action to complete.
wscript.sleep 3000
‘Run a SMS Hardware Inventory
Set cpApplet = CreateObject("CPAPPLET.CPAppletMgr")
Set actions = cpApplet.GetClientActions
For Each action In actions
If Instr(action.Name,"Hardware Inventory Collection") > 0 Then
action.PerformAction
End If
Next

Note:Replace the quotes used in the script as they converted to fancy quotes.

If you want to run other actions,please replace the ActionID and Action name as given below:

• Software Metering Usage Report :00000000-0000-0000-0000-000000000106
• Request & Evaluate Machine Policy :8EF4D77C-8A23-45c8-BEC3-630827704F51
• Updates Source Scan :00000000-0000-0000-0000-000000000113
• Request & Evaluate User Policy:3A88A2F3-0C39-45fa-8959-81F21BF500CE
• Hardware Inventory Collection:00000000-0000-0000-0000-000000000101
• Software Inventory Collection:00000000-0000-0000-0000-000000000102
• Application Global Evaluation:00000000-0000-0000-0000-000000000123
• Software Updates Assignments Evaluation:00000000-0000-0000-0000-000000000108
• Discovery Data Collection:00000000-0000-0000-0000-000000000103
• MSI Product Source Update:00000000-0000-0000-0000-000000000107
• Standard File Collection:00000000-0000-0000-0000-000000000104

To Know How to run this script on remote clients using psexec ? Read blog post http://eskonr.com/2011/01/script-to-trigger-sccm-machine-policy-or-hardware-inventory-action-agent-on-sccm-clients/

SCCM Configmgr 2012 script to Trigger Machine policy inventory and other actions on Clients is a post from: Eswar Koneti's Blog

In this blog post,we are going to see how to manage workgroup/ DMZ 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.

There are some limitation while managing the workgroup computers listed below:

Limitations:

• Workgroup clients cannot locate management points from AD and instead we must use DNS, WINS or another Management Point.
• Global Roaming is not supported because clients cannot query AD for site information.
• AD discovery cannot discover computers in workgroups.
• You cannot deploy software to users of Workgroup computers.
• You cannot use client push installation method to install client on workgroup computers.
• Workgroup clients cannot use Kerberos for authentication so might require manual approval.
• Workgroup client cannot be configured as a Distribution Point. SCCM 2012 requires that distribution point computer be members of a Domain.

 Site Assignment:

• After you install the Client, it must join a configmgr primary site before it can be managed. The site that a client joined is referred to as its assigned site.
• Clients cannot be assigned to CAS or secondary Site.
• A client is considered to be unmanaged when it is installed but not assigned to a site or is assigned to a site but cannot communicate with a management Point.

Manual Vs. Auto assignment:

• Auto assignment will not work for workgroup clients
• To manually assign the workgroup clients SMSSITECODE installation property must be used
• Ccmsetup.exe SMSSITECODE=PRI SMSMP=cm12pri.eskonr.com
• Use SMSMP property to specify management point or use DNSSUFFIX for the clients to automatically locate MP from DNS.
• Ccmsetup.exe SMSSITECODE=PRI DNSSUFFIX=eskonr.com

Client approval:

• You can either choose to approve all automatically (not recommended) or manually approve each workgroup client from site setting properties.

Softwares to Workgroup clients:

• Setup Network Access Account
• If boundaries and boundary groups are configured properly clients can automatically locate Distribution Points.
• If boundaries and Boundary Groups are not configured, you should setup the deployment option
• Package properties: Deployment option: download content from DO and run locally which means all these clients will fall under SLOW.

Note : The above information is captured from Taj mohammed session.

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 on this blog post.

Do the below steps on Work Group machine.

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.

Note:if your local administrator account is disabled for other reasons,use the account which as local admin rights on the workgroup computer.

Note: By Default ,windows 7 and later Operating Systems,GPO setting set to Classic-Local Users Authenticate themselves.

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options–>Network access: Sharing and security model for local accounts

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

Update: If you are trying to manage Windows XP Workgroup computers,GPO setting is not set to classic by Default and it is required to change it manually or via scripting else you keep on prompting for password that never works.

Thanks to Niall for finding the GPO setting on WinXP computers.

Hope it helps!

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

Did you ever get into disk Space Issues while copying,Decompressing PCK files in Configuration Manager 2007 ? Packages are failed due to not enough disk space ?

couple of options to get out of it are 1) Add Extra Drives or Increase the Disk on the Drive if you are into VM 2) manage with the existing disk by doing some alteration to it like moving the PCK files or Delete them.

OR Move to Configuration manager 2012 which no longer use PCK storage and uses Single Instance Storage ,More about why should move from CM07 to CM12 http://eskonr.com/2013/01/why-should-we-move-from-sccm-configmgr-2007-to-2012/ and

Single Instance Storage http://blogs.technet.com/b/hhoy/archive/2012/05/31/an-adventure-in-the-sccmcontentlib-single-instance-store.aspx

If you want to move the PCK files to different drive rather deleting them,Please refer this post http://eskonr.com/2012/10/how-to-move-pck-files-to-different-drive/, For Deletion,continue reading.

As We all Know,The PCK files are stored on the drive letter that you specify in the hierarchy settings—>software Distribution.

If you found ,the PCK drive do not have enough disk,try to change the Drive letter to different drive which has more disk space and creating NO_SMS_ON_DRIVE.SMS on the root of the drive to not use for decompressing of the packages,and moving forward,You will no longer have PCK file issues.

But if you are having Many Packages that are not updated since years,probably it is good Idea delete the PCK for these packages.

Note:If you later update these packages,Entire PCK files will get copied over the network to the site server,Please pay attention on it.

I Wrote a Script that checks all the drives if smspkg share exists or not ,If so check the PCK modifiedDate and then Delete if older than 2 Years.

‘ Author:               Eswar Koneti
‘ Title: Script to Delete the PCK files on all the exisiting Drives that are older than 2 Years (730 Days)

Set objfso = CreateObject ("Scripting.FileSystemObject")
Set servers = objfso.OpenTextFile ("C:\Scripts\servers.txt", 1)
Set objoutputfile = objfso.OpenTextFile ("C:\Scripts\PCKResults.txt", 2, True)
do While Not servers.AtEndOfStream
strcomputer=servers.readline
Set objWMIService = GetObject("winmgmts:\\" & strComputer)
If Err.Number <> 0 Then
    objoutputfile.WriteLine (strcomputer & " is not Up or something went wrong with WMI")
    Err.Clear
   Else
    strDays= 500
    Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_LogicalDisk")
           For Each objdrive in colItems
        drive=left(objDrive.caption,1)
    If (objfso.FolderExists("\\" & strComputer & "\"+Drive &"$\smspkg\")) Then   
        set recive = objfso.GetFolder("\\" & strComputer & "\"+Drive &"$\smspkg\")
         Set colFiles = recive.Files
            For Each objFile in colFiles
            filename=objfile
            if (right(FileName, 4) = ".PCK") then
                     If DateDiff("d", objFile.DateLastModified, Date) > strDays Then
                    objoutputfile.WriteLine objfile & vbtab & "exist on "& vbtab & strComputer & vbtab & "modified date:" & vbtab & objFile.DateLastModified & vbtab & "Size (MB):" & vbtab & int(objFile.Size/1048576)
              objfso.DeleteFile objfile,TRUE
              objoutputfile.WriteLine strComputer & vbTab & "Deleted"
                end if
            end if
            Next
        End if
Next
end if
loop
msgbox "script is completed"

Change the quotes as they converted to Fancy by Blog OR use the script from RSS Feeds.

Until next,

SCCM 2007 Script to Delete Old PCK files from SMSPKG folder Avoid Disk Space issues is a post from: Eswar Koneti's Blog

Microsoft released System center 2012 R2 Configuration manager tool kit which contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager both clients and server.

List of tools available after you install the Configmgr 2012 R2 tool kit are listed below:

Note:* mark represents the the tool is new in R2 and its requires Configmgr 2012 R2 for full functionality.

Client Based Tools:

• Client Spy – A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on System Center 2012 Configuration Manager clients.
• Configuration Manager Trace Log Viewer – A tool used to view log files created by Configuration Manager components and agents.
• Deployment Monitoring Tool – The Deployment Monitoring Tool is a graphical user interface designed help troubleshoot Applications, Updates, and Baseline deployments on System Center 2012 Configuration Manager clients.
• Policy Spy – A policy viewer that helps you review and troubleshoot the policy system on System Center 2012 Configuration Manager clients.
• Power Viewer Tool – A tool to view the status of power management feature on System Center 2012 Configuration Manager clients.
• Send Schedule Tool – A tool used to trigger a schedule on a client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.
• Wakeup Spy – A tool that provides a view of the power state of Configuration Manager client computers and which operate as managers or manages.

Server Based Tools:

• * DP Job Manager – A tool that helps troubleshoot and manage ongoing content distribution jobs to Configuration Manager distribution points.
• * Collection Evaluation Viewer – A tool that assists in troubleshooting collection evaluation related issues by viewing collection evaluation details.
• * Content Library Explorer – A tool that assists in troubleshooting issues with and viewing the contents of the content library.
• Security Configuration Wizard Template for Microsoft System Center 2012 R2 Configuration Manager – The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server’s role or roles, and disables functionality that is not required.
• Content Library Transfer – A tool that transfers content from one disk drive to another.
• Content Ownership Tool – A tool that changes ownership of orphaned packages (packages without an owner site server).
• Role-based Administration Modeling and Auditing Tool – This tool helps administrators to model and audit RBA configurations.
• Run Metering Summarization Tool – The purpose of this tool is to run the metering summarization task to analyze raw metering data

Download the tool Via http://www.microsoft.com/en-us/download/details.aspx?id=36213

SCCM Configmgr 2012 R2 Toolkit Available for download is a post from: Eswar Koneti's Blog

Configmgr 2012 allow admins to specify the Client Settings at collection level to control the behavior and functionality of the clients.

You can create as many number of Custom Client Device/User settings (9999) which you can apply onto collections(Device/User).

What happens if client is member of multiple collections that have client settings ? All the Custom Client settings that you create are chosen with the priority. Higher the priority(1) will take over the settings with lower priority(10000).

If you are going to have multiple client agent settings,focus attention else you will see undesired results.

By Default,Configmgr will Configure default client settings at Hierarchy Level with priority 10000 (low) which is applied to every User and Device.To know more about Client Settings refer TechNet http://technet.microsoft.com/en-us/library/gg682067.aspx

Now,lets jump into the subject line. After the Configmgr 2012 Installation ,Default Client settings is configured with necessary changes,in this case,Remote tools is configured ‘Permitted viewers of remote control and remote assistance’ with AD security groups allowing users, who are member of this AD security group can do Remote control from Configmgr.

These settings(remote Control) will be then applied to every Client (both workstations and servers) in next policy interval.what happens when this is applied ?

It will create Local security group called ‘ConfigMgr Remote Control Users’ by providing necessary DCOM permissions to this group.You can verify the remote control properties via wmi or registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control)

so far so good ,but recently I had requirement from server Team to deny the remote control on servers –the other way,Remote control is not allowed using Configmgr.

The course of action would be ,to create custom device settings and disable the remote tools ? I have done this but after sometime,server team comeback saying,there are still AD security groups part of local group.

Disabling the remote tools will deny user to do remote control from configmgr but you are also supposed to remove the entries from both registry and local Security Group for server team .

Simply Disabling the Remote tools will not help you in this case,so I have to test with different options to meet the server guys requirement and below goes for you.

Case 1: Disable ‘Enable Remote control On clients’ without removal of permitted viewers ?—In this case,remote tools will be disabled on the client but you will have both security groups from registry and Local group(ConfigMgr Remote Control Users).

Case 2: Disable ‘Enable Remote control On clients’ with removal of permitted viewers ?—In this case,remote tools will be disabled on the client by removing the entries from registry but not from Local group(ConfigMgr Remote Control Users).

Case 3:Enable ‘Enable Remote control On clients’ with removal of permitted viewers ? In this case,Remote tools will be enabled but it will delete the entries from both registry and as well local Group (ConfigMgr Remote Control Users).

Note: I am not describing about other remote tool options here like ‘Manage remote desktop settings’ ,’Play sound on client’ etc.

I chosen option 3 in this case .

Questions via comments section(Leave a Reply).

Configmgr 2012:Custom Client Device Settings What happens when you enable or disable Remote control On Clients is a post from: Eswar Koneti's Blog

Client Center tool is designed for IT Professionals to troubleshoot SCCM/CM12 Client related Issues. The Client Center for Configuration Manager provides a quick and easy overview of client settings, including running services and Agent settings in a good easy to use, user interface.

Here you go with Client center Beta Version : http://sccmclictr.codeplex.com/

when you try to install this app, It always connects to Internet to install the app else will Fail.

How to use this application without connecting to Internet ?

On the Computer where you installed the click once application,files resides on the below path.

Go to the computer where the application is installed and look for this path.

C:\Users\Username\AppData\Local\Apps\2.0\VXYT5QN6.KNV\R4TKLVQN.5TR\sccm..tion_0000000000000000_0000.0000_5f09e27d38cfe83a\

Create Shortcut for SCCMCliCtrWPF.exe and use it.

P.S:Red indicates they are replaced.

Thanks to John Marcum.

Use #SCCM / #Configmgr 2012 Client Center without connecting to Internet is a post from: Eswar Koneti's Blog

Did you ever had difficulties importing, exporting or migrating the reports from Configuration manager 2007  (SSRS ) to Configuration manager 2012 ? If so,how do you migrate reports to Configmgr 2012 ?

To get the SSRS Reports from Configmgr 2007 to Configmgr 2012,you will have to download each report (.RDL) manually and upload it your Configmgr 2012 SSRS Folder. If you have bunch of reports ,what do you do ? Doing this task manually is tedious and involves lot of time.

This blog post discuss about how to migrate reports ,download,upload your custom reports to Configmgr SSRS folder.

During my Search ,I found a tool called ReportSync that does the following activities .

• Sync reports between two SSRS servers.
• Download RDL Files from SSRS  to local PC.
• Upload RDL files to a SSRS server
• Attach datasources automatically on upload(Data source name given in the report must exist on server)

I use this tool oftenly while working with SSRS Reports since it gives me the flexibility to upload multiple reports to specific folder in SSRS. (Default via SSRS browser allows only one at a time).

Download the tool from https://code.google.com/p/reportsync/

Run the Tool

This tool contains 2 fields 1) Source SSRS Web service and 2 ) Destination SSRS Web service.

As I said before,you can use this tool download SSRS Reports to local Drive,migrate reports between the SSRS Servers,upload the reports from Drive.

If you want to download the Reports (.RDL) files from your SSRS server (Configmgr 2007 or 2012 ),enter the source URL ,User hat has permissions to connect to SSRS,Password in Source URL Web Service and click on Load.

How to get the right SSRS URL that has been configured in your environment ?

From your Configmgr server or SQL Server,Launch Reporting services Configuration manager tool and look for Web service URL

After you run the tool ,It takes few seconds or minute to load the reports from your SSRS Folder .

Select the report that you want ,provide the local path to store these reports (.RDL files) and click on Download.

Each category what you see in this tool will be created as Folder in yours local Path.

Reports folder look like this :

You can also try to upload your customized reports to Destination server ,sync and do other functions with this tool.

Hope it helps!

Configmgr 2012 allow admins to specify the Client Settings at collection level to control the behavior and functionality of the clients.

You can create as many number of Custom Client Device/User settings (9999) which you can apply onto collections(Device/User).

What happens if client is member of multiple collections that have client settings ? All the Custom Client settings that you create are chosen with the priority. Higher the priority(1) will take over the settings with lower priority(10000).

If you are going to have multiple client agent settings,focus attention else you will see undesired results.

By Default,Configmgr will Configure default client settings at Hierarchy Level with priority 10000 (low) which is applied to every User and Device.To know more about Client Settings refer TechNet http://technet.microsoft.com/en-us/library/gg682067.aspx

Now,lets jump into the subject line. After the Configmgr 2012 Installation ,Default Client settings is configured with necessary changes,in this case,Remote tools is configured ‘Permitted viewers of remote control and remote assistance’ with AD security groups allowing users, who are member of this AD security group can do Remote control from Configmgr.

These settings(remote Control) will be then applied to every Client (both workstations and servers) in next policy interval.what happens when this is applied ?

It will create Local security group called ‘ConfigMgr Remote Control Users’ by providing necessary DCOM permissions to this group.You can verify the remote control properties via wmi or registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control)

so far so good ,but recently I had requirement from server Team to deny the remote control on servers --the other way,Remote control is not allowed using Configmgr.

The course of action would be ,to create custom device settings and disable the remote tools ? I have done this but after sometime,server team comeback saying,there are still AD security groups part of local group.

Disabling the remote tools will deny user to do remote control from configmgr but you are also supposed to remove the entries from both registry and local Security Group for server team .

Simply Disabling the Remote tools will not help you in this case,so I have to test with different options to meet the server guys requirement and below goes for you.

Case 1: Disable ‘Enable Remote control On clients’ without removal of permitted viewers ?---In this case,remote tools will be disabled on the client but you will have both security groups from registry and Local group(ConfigMgr Remote Control Users).

Case 2: Disable ‘Enable Remote control On clients’ with removal of permitted viewers ?—In this case,remote tools will be disabled on the client by removing the entries from registry but not from Local group(ConfigMgr Remote Control Users).

Case 3:Enable ‘Enable Remote control On clients’ with removal of permitted viewers ? In this case,Remote tools will be enabled but it will delete the entries from both registry and as well local Group (ConfigMgr Remote Control Users).

Note: I am not describing about other remote tool options here like ‘Manage remote desktop settings’ ,’Play sound on client’ etc.

I chosen option 3 in this case .

Questions via comments section(Leave a Reply).

Microsoft released SCCM Configmgr Upgrade Assessment Tool that provides administrative users with information that they can use to determine if the computers that are managed by System Center Configuration Manager can run Windows 7, Windows 8 or Windows 10.

The Upgrade Assessment Tool provides the following functionality:

• Retrieves device driver compatibility information for installed peripheral devices and creates reports that you can use to determine which device drivers need to be upgraded to support the Windows operating system.
• Allows you to see which computers meet the recommended system requirements for Windows operating systems and to customize these requirements for your environments.
• Creates summary reports that you can use to see an enterprise wide view of operating system upgrade readiness.
• Allows you to create dynamic collections for an operating system deployment. The collection query rules can be based on system requirements, application compatibility status, and device driver status.

Before you install this tool,you must have the following applications/software's to be in place .

• The site server must be running one of the following configmgr Versions:

Configmgr 2012 SP2 with CU 3
Configmgr 2012 R2 SP1 with CU3
Configmgr (current branch) Version 1602 or Higher

• Configuration Manager clients can run one of the following:

Configmgr 2012 SP1 or higher
Configmgr 2012 R2 or higher
Configmgr (current branch) version 1511 or higher

• You must have a reporting services point to view the compatibility information from clients.
• You must have one or more distribution points to deploy the ACT inventory collection package to clients.
• Clients must run hardware inventory.
• Application Compatibility Toolkit (ACT) 6.1
• Microsoft .NET Framework 4.5.2.

More information and download this tool from https://www.microsoft.com/en-us/download/details.aspx?id=37145