CCMEXEC.COM – System Center blog

CCMEXEC.COM – by Jörgen Nilsson

I have written a couple of scripts before to install the SCCM 2007 console which is a challenge with R3 and hotfixes e.t.c. In System Center 2012 Configuration Manager this has now changed, it is really simple to install the Admin Console unattended.

There is no need to run Setup and use an unattended file anymore, the setup files for the Adminconsole is located on the Primary Site Server in the Configuration Manager installation folder under Tools\ConsoleSetup. In that folder there are two files ConsoleSetup.exe and Adminconsole.msi(if you install more languages there will be more files)

Compared to using the ConfigMgr2012 installation media you will save a lot of disk space on the DP’s using this method.

Configmgr2012

The installation must be done using the ConsoleSetup.exe as it provides more functionality than simply running the AdminConsole.MSI file.

Here is how to do it:

  1. Simply copy the whole ConsoleSetup Directory to my package source share
  2. Create a new Application and Manually enter the information needed.
  3. Name it for instance AdminConsole with Script Installer(Native) as the deployment type.
  4. As detection method use Windows Installer and select the Adminconsole.msi file.
  5. In the Command Line use the following:
    “consolesetup.exe /q TargetDir=”C:\Program Files\ConfigMgr” EnableSQM=0 DefaultSiteServerName=Siteserver1.contoso.com”
  6. Replace Siteserver1.contoso.com with the FQDN for your site.
  7. Deploy it to the collection of your choice and you are finished.

Incredibly simple!!

Don’t forget that the AdminConsole requires the Full .Net Framework 4 to be installed before so either add it as a dependency or requirement, dependent on how you have designed you application management.

For more information including how to install the AdminConsole in different languages see Technet :http://technet.microsoft.com/en-in/library/gg712320(en-us).aspx

In some scenarios you may want for instance servicedesk or helpdesk personnel run the Configuration Manager 2012 Remote Control without having to install the Admin Console and grant them permissions to use the Admin Console when they really only need to run Remote Control.

Here is how to do it, the following files are needed.

From the directory where the AdminConsole is installed, example: E:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\i386, copy the following files:

Remote1In the directory 0000409 you need one file as well.

Remote2Copy the whole directory with these files present to the computer you want to run Remote Control from so you have a folder structure like this:
RemoteControlAnd then simply launch the CmRcViewer.exe and you are good to go:

Remote3

Important information, if you want the standalone Remote Viewer to report back to the SCCM Site Server which client is remote controlled and by who, you can add the registry value below on the client as well. Thanks to Luis Baños for the comment.

For 32 bits

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr10\AdminUI\Connection]
“Server”=”Site Server Name”

For 64 bits
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Connection]
“Server”=”Site Server Name”

– Specifies the name of the site

The offline documentation for System Center 2012 Configuration Manager is available for download! It is available in three formats:

  • CHM (as part of the Help Update Wizard msi) – last updated May 23, 2012
  • DOCX – last updated May 23, 2012
  • PDF – last updated May 23, 2012

It is a great resource to have locally and easy to search, be sure to check it out!

http://www.microsoft.com/en-us/download/details.aspx?id=29901

Hi,

This article was released a couple of days ago and can be good to know about.

From the MS KB:

“A PXE enabled Distribution Point will generate a number of files under C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 for each PXE request that it services on the network. This occurs whether the device sending the PXE request has a Task Sequence deployed to it or not. The generation of files will continue and may consume available hard disk space.”

For more information see the whole article: http://support.microsoft.com/kb/2713467

There was a question asked on the Technet forum today on how to make the builtin report in SCCM 2007 “Computers not inventoried recently (in a specified number of days)” to be filtered per Collection and prompt for a CollectionID.

The updated report looks like this, the changes made are in bold letters:

SELECT INST.SMS_Installed_Sites0, SYS.Netbios_Name0, SYS.User_Domain0, SYS.User_Name0, @varcollection as 'Collection', SYS.Resource_Domain_OR_Workgr0, HWSCAN.LastHWScan, DateDiff(Day,

CASE WHEN IsNULL(HWSCAN.LastHWScan,'1/1/1980') > IsNULL(SWSCAN.LastScanDate,'1/1/1980')

THEN HWSCAN.LastHWScan

ELSE SWSCAN.LastScanDate

END

,GetDate()) AS C053,

SWSCAN.LastScanDate, SWSCAN.LastCollectedFileScanDate

FROM v_R_System SYS

LEFT JOIN v_GS_LastSoftwareScan SWSCAN on SYS.ResourceID = SWSCAN.ResourceID

LEFT JOIN v_GS_WORKSTATION_STATUS HWSCAN on SYS.ResourceID = HWSCAN.ResourceID

LEFT OUTER JOIN v_RA_System_SMSInstalledSites INST ON SYS.ResourceID = INST.ResourceID

Left join v_FullCollectionMembership FCM on FCM.ResourceID = SYS.ResourceID

WHERE

DateDiff(Day,

CASE WHEN IsNULL(HWSCAN.LastHWScan,'1/1/1980') > IsNULL(SWSCAN.LastScanDate,'1/1/1980')

THEN HWSCAN.LastHWScan

ELSE SWSCAN.LastScanDate

END

,GetDate()) >= @variable

AND Client0=1 and FCM.CollectionID = @varcollection

Order By INST.SMS_Installed_Sites0, SYS.Netbios_Name0

To implement it either change the report or paste this in a new report and create to Prompts, one for Days called variable and one for CollectionID called varcollection.
query

There is no prompt query for the original Report ID:74 as it is days it asks for, the prompt query for CollectionID can be found here:

begin

if (@__filterwildcard = '')

select distinct CollectionID, Name from v_Collection order by Name

else

select distinct CollectionID, Name from v_Collection

WHERE CollectionID like @__filterwildcard

order by Name

end

In some scenarios where you would install System Center 2012 Configuration Manager you install the languages you need, but when your company is expanding you will need to install additional languages. In ConfigMgr 2012 we don’t have any International Client Packs which was the case for earlier versions, instead the languages are selected and installed during setup.

So how do I add a new client language afterwards? Or add support for running the Configuration Manager Console in a different language? It is done by using the “Configuration Manager Setup” which can be found on the Start menu or by simply running install from the installation source.

When the setup starts select the “Perform site maintenance or reset this Site” in the following wizard you can then add languages as you need them.

Here is a step-by-step guide:

  1. Start Configuration Manager Setup either from the start menu or the installation source.
  2. Select the “Perform site maintenance or reset Site” optionAddlanguage_!
  3. Then you get the option to Modify language configuration, it is also here you can convert from an eval installation and enter a license.Addlanguage_2
  4. In the next dialog we need to either download the prerequisite files again or point to the directory where they where used for the intial installation of the Site Server.Addlanguage_3
  5. The next screen offers the option to server languages, here you can add language support for the Configuration Manager Console.Addlanguage_4
  6. Then we get to the dialog were we can add Client language support, in my case I want to add Swedish
    Addlanguage_5
  7. Then we are ready to complete the installation, Note: that a Site reset will occur
    Addlanguage_6
  8. Adding Swedish client language support took 8 seconds! :D
    Addlanguage_7After the installation of the language support is done the ConfigMgr clients that should have the new updated language must have the client reinstalled. This can be done using any preferred client deployment method.
    Done!

I wrote a post a while back on how to install the SCCM 2007 Admin Console including R3 and required hotfixes: http://ccmexec.com/2012/01/unattended-installation-of-sccm-2007-admin-console-including-r3/

In that post i also promised to write a post on how to install the SCCM 2007 Admin Console + R3 + FEP.
It turned out to be a bit of a challenge as the FEP installation is either 32 or 64 bit depending on the operating system you install the admin console on. After a re-write here is the updated script, I used the RTM version of FEP and included the Update Rollup 1 in the script, so if you are using the updated media remove the part in the script and the folder for the KB.

The script has been tested on Windows 7 32 & 64 bit, the SCCM console will be installed to “C:\program Files\Configuration Manager 2007″ or “C:\program files(x86)\Configuration Manager 2007″ depending on the operating system architecture.

To implement it the following steps are needed:

  1. Download the ZIP-file containing the script and folder structure: Adminconsole_sp2_r3
  2. Unzip the files and folder to a catalog which will be used as source folder.
  3. Copy the necessary source files to the different directories from the original media:
    adminconsooleinstall_FEP1 Tip: you can skip the “WAIK” folder in the Configuration Manager 2007 Sp2 source files, then you will save a lot of disk space.
  4. As the FEP files and updates are both 32 and 64 bits the FEP_Console folder is divided in a 32 and 64 bit folder:
    adminconsooleinstall_FEP4
  5. The same goes for the FEP Update rollup 1 update, although they are not named the same and can be placed int the same folder. The update can be downloaded here: http://support.microsoft.com/kb/2551095
  6. adminconsooleinstall_FEP5When all the source files are copied to their correct location, create a package using the folder created earlier with folder containing the “Install_FEP.vbs” as source folder.
  7. On the “Reporting” tab for the newly created package enter the below information, as the hotfix for SCCM 2007 R3 restarts many services including SMS Agent Host the script will generate a .MIF file which is the only way of reporting back that the installation was successful:
    adminconsooleinstall_FEP3
  8. Distribute the content to the DP’s
  9. Create a new program with the following command line “cscript.exe fep_install.vbs”
    adminconsooleinstall_FEP2
  10. Then advertise the program to a test collection and verify that everything is working as expected.

I hope it will be useful!

Wrote this as an answer to a Technet forum question, it will list all Microsoft Office applications for a specific subnet. It can easily be changed to filter on more than one subnet and different applications.

select ip.IP_Subnets0 [Subnet], sys.Name0 [Name], DisplayName0
from v_R_System sys
join v_RA_System_IPSubnets ip on ip.ResourceID = sys.ResourceID join v_GS_ADD_REMOVE_PROGRAMS on v_GS_ADD_REMOVE_PROGRAMS.ResourceID =  sys.ResourceID
Where IP_Subnets0 = '192.168.1.0' and Displayname0 like 'Microsoft Office%'
order by ip.IP_Subnets0, sys.Name0

select ip.IP_Subnets0 [Subnet], sys.Name0 [Name], DisplayName0

from v_R_System sys

join v_RA_System_IPSubnets ip on ip.ResourceID = sys.ResourceID join v_GS_ADD_REMOVE_PROGRAMS on v_GS_ADD_REMOVE_PROGRAMS.ResourceID =  sys.ResourceID

Where IP_Subnets0 = '192.168.1.0' and Displayname0 like 'Microsoft Office%'

order by ip.IP_Subnets0, sys.Name0