Category Archives: Microsoft System Center

CM 2012 – Application Catalog – Color Themes

For this article, I decided to write about something a little lighter… color choices within the CM 2012 Application Catalog.  If your company likes to have a specific color dominant within corporate websites, perhaps you can preemptively change the color theme of your Application Catalog to match this color before you are asked to do so.

If you navigate to the properties page of the Application Catalog website point and then select the Customization tab, you will see a line labeled “Website theme:” followed by a box showing a blue square and the word “Blue.”  (I’ve cut out a lot of the blank space in the picture below.) Blue is the default color of the Application Catalog.

Customization Tab

This box is a drop-down selector for other default colors, plus a color palatte for creating a custom color theme.  Click on the box and the drop-down selections shown below will appear.  If you wish to create a custom color, click on “More colors…” at the bottom of the list.  After you have completed selecting a color, click the “Apply” button and then click okay.  The Application Catalog will reflect the selected color upon next being loaded by a client.  (I discuss more about custom colors as well as a useful tool that can be used for that the end of the article.)

Color Palette

Here are the colors in order of selection from the above drop-down menu.

Blue:

Blue

Magenta:

Magenta

Purple:

Purple

Teal:

Teal

Lime:

Lime

Brown:

Brown

Pink:

Pink

Orange:

Orange

Red:

Red

Green:

Green

Customizing colors for the Application Catalog utilizes a standard color palette with which you should be familiar.  After selecting “More colors…” from the Website theme drop-down selector, a standard color palette will appear.

Alternative Colors

If none of these alternate colors closely match what you need, clicking on the “Define Custom Colors” button at the bottom will bring up a custom color palette, again, which should be familiar.

Alternative Colors 2

The tool I prefer to use for discovering RGB numbers for corporate colors is a free tool named Instant Eyedropper available from SpiceBrains.  Here is the site for the Instant Eyedropper tool itself.  The download link is in the upper right-hand corner.  After installing this tool, an icon will appear in the system tray (Windows 7 is shown in these examples) as a small color wheel.  I’ve put a red square around the icon in the picture below.

System Tray

Right-clicking the icon brings up color type selections and options.  For using color palettes as shown above, select the RGB color type.

Instant Eyedropper 01

Now that the color type is selected, go back to the system tray, left-click-hold the left mouse button and a color point measurer will appear.  Continue to hold the left mouse button and drag the color point measurer over the color you want to read.  The RGB colors numbers will show and you can then copy these into your custom color palette!

Instant Eyedropper 02

Honestly, this is one of the coolest free tools for graphics that I’ve seen in a long time.  One thing to note – if you have multiple monitors, you must use monitor one.  Dragging the color point measurer to any monitor but monitor one will yield a color of 255 255 255 (black) – not sure why, but it does, so avoid that.  Enjoy!

Adaptiva OneSite – Configuration – Setting Preferred Clients

I’m sure that at one point in most technical careers, people have run into those networks which are similar to a spider’s web, spun by a drunk black widow. The illustration below is tame compared to what I’ve encountered, but it will serve a purpose for this article. The Main Office symbol represents a Configuration Manager Primary Site, the Office ### symbols represent locations housing Distribution Points, and the lettered symbols represent smaller sites and branch offices.

clip_image002[4]

When designing a Configuration Manager infrastructure, the network topology is very important in determining where to put additional Primary Sites, Secondary Sites, and Distribution Points, based on network layout, link speeds, endpoint populations, and other factors. You can leverage your Configuration Manager infrastructure for OneSite and using preferred client settings is a way to achieve a certain amount of network traffic isolation with respect to content pre-staging and downloads. Referring to the diagram above, the Office ### sites have been made parent sites to those smaller down-line sites for the purposes of this exercise.

Keep in mind that OneSite content download requests may flow up a topology but stop at the top of the hierarchy (Central Office). A OneSite preferred client is one that will handle all content requests from down-line clients, provided the content is present, prior to the request being sent to the Central Office site. That being said, looking at the diagram below (which is a portion of the first diagram presented), a case could be made for setting the preferred client key on Office 003 and Office 004 for their child sites.

clip_image004[4]

Setting a preferred client within OneSite will force down-line clients to look to the preferred client first before traversing up-line in the network topology when requesting content. Here is how to create a client setting which will set this variable within the environment.

From within Adaptiva Workbench, starting at the Home perspective, expand Workbench perspectives, expand Misc and then select the System Configuration Perspective from the result choices.

clip_image005[4]

After the System Configuration Perspective screen loads, create a new client settings policy by selecting “Create New Client Settings Policy.” The Custom Client Settings Policy Editor panel will load to the right.

clip_image006[4]

Within the Custom Client Settings Policy Editor, set an intuitive name for your new policy setting, provide a short description and priority, and set a settings override priority. To the right, click the Add Collection. A drop-down menu will appear, showing collections from your Configuration Manager environment. Select the collection in which you have placed those OneSite clients you wish to be set as preferred clients for specific down-line branches of your OneSite network topology. (This section is located in the top panel of the Policy Editor screen.)

clip_image008[4]

Within the System config settings panel (located at the bottom of the Policy Editor screen), expand SystemConfig, expand Contentsystem, then drag Client type from the left, into and over the SystemConfig setting in section labeled “Overridden client settings by this policy” until you see a “+” sign appear, then release the mouse button to add the attribute. Within the “Overridden client settings by this policy,” expand Contentsystem and select Client type. In the far right section, change the “New value” to 1. Click the Apply button at the top of this panel.

clip_image010[4]

Click the Save icon in the top left of the Custom Client Settings Policy Editor section and your policy will be saved and applied to the CM collection you designated earlier. In the future, if additional preferred clients are needed, simply add them to the same CM collection.

CM 2012 – Configuration – Custom Client Settings for SUP

A client recently requested preliminary design for moving security updates from WSUS to CM 2012.  There were several requirements for the move as well:  1) SUP would need to be tested on a small group of clients initially;  2) WSUS would need to remain in parallel during the process in order to keep current desktop/laptop clients and servers patched; 3) WSUS would need to remain in place after the move as the server team would continue to use it until their conversion to CM 2012.

I’m only going to focus on how custom client settings were used to segment out the test group from the main body of desktops and laptops.  (There were Group Policy and other adjustments which had to be made as well, but they are not part of this discussion.)

First, I created a test collection to house the initial software updates test group.

CCSSUP01

Current Default Client settings have Software Updates turned off.

CCSSUP02

I created a custom client device setting specifically targeted at software updates.  You can do this by navigating to Administration > [expand] Overview > [expand] Site Configuration > [select] Client Settings, then either right-click on Client Settings and select “Create Custom Client Device Settings” or click the same-named icon in the top ribbon.

On the General tab of the resulting screen, I named the Custom Device Settings “Software Updates – Enabled” and checked the Software Updates box.  Checking this box reveals the Software Updates tab in the left panel.

CCSSUP03

On the Software Updates tab, I enabled software updates on clients (1 in the picture below), set bundling of updates having deadlines within 1 day of any update which has reached its deadline. (2 and 3 in the picture below) Save the custom client setting by clicking OK and then deploy it to the test collection.  I set the priority of the setting to 1.  If this is your first custom setting, it will default to a priority of 1.  You can change the priority of any custom setting by right-clicking on the setting and using the Increase or Decrease Priority selections from the drop-down menu.  Remember that the lower the priority number, the higher the priority in settings application on the client machine.

CCSSUP04

The newly deployed shows up under the deployments tab of the custom settings.

CCSSUP06

Force a Machine Policy Retrieval & Evaluation Cycle on the machines located in the test collection and the new custom settings will be applied.  You can check this by looking at the Components tab of the Configuration Manager control panel applet.

CCSSUP08

Initiate a Software Updates Scan Cycle on the machines located in the test collection and then spot-check the WUAHandler.log file on those machines to validate that the clients are pointing to the correct SUP server and that the scan is not encountering any errors which need addressing.  You should see something similar to the below entries in the log file.

Enabling WUA Managed server policy to use server: [YOUR SERVER HERE]
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan.

If you feel so inclined, use a tool such as Roger Zanders Client Center to check things out. (http://sccmclictr.codeplex.com/  –  don’t forget to donate!)

CCSSUP10

CM 2012–Configuration – Software Update Point Settings

I’ve had this question posed a number of times, “How do I change the Software Update Point settings after I’ve installed SUP?”  If you’re new to the CM 2012 console, finding where to configure additional settings can be somewhat challenging at times.

Navigate to Administration > Site Configuration > Sites > the site which has SUP installed
Right-click on the site and select Configure Site Components > Software Update Point

Step 01

Choose the tab which contains the items you want to configure. In the picture below, I drew arrows to the update classifications tab and the products tab.  When you are finished, click Apply and OK.

Step 02

CM 2012 – Troubleshooting – The Create Application Wizard completed with errors

I have set up a lab within Hyper-V for various System Center Products and I wanted to run through some scenarios with SCCM 2007 to CM 2012 migrations. There are about twelve or so servers setup to simulate a domain, DNS, DHCP, etc…. the basic things needed to do system and scenario testing and extra servers for playing around. So, I set up an SCCM 2007 environment, complete with clients, packages, etc., all working fine. I also set up a CM 2012 environment in native mode and a SQL 2012 server running on a separate server. I left off some of the extra roles such as EPP, SUP, SMP, etc., as I wanted to test basic raw functionality during a migration. My plan was to run through several migrations of various types to learn as much as possible.

Much to my satisfaction, after a few eventful evenings involving PKI, certificates and order of installation for IIS components, I had a CM 2012 system with a nice green column of checkmarks within the System and Component Status displays. My next order of business was to test some functionality before performing the test migration, so I started with application creation. I chose a pretty simple application, the Microsoft Config Manager 2012 Toolkit (SP1), went through the default steps and made no custom changes, only to receive this error message: (This is an isolated test environment, so I really don’t care if server names are displayed – figured I’d say that before I received a pm or something.)

The Create Application Wizard completed with errors
The Create Application Wizard completed with errors

There were no error details other than the line indicating that the SMS Provider reported an error – so I checked the SMSProv.log file. The first error generated was very long so I’ll omit most of the body of the error and provide the front and back ends. In addition, here are the three error messages which followed as well.

———————————————————–

error 14: SQL Error Message Failed to generate documents:A .NET Framework error occurred during execution of user-defined routine or aggregate “fnGenerateLanternDocumentsTable”:
… (omission of large part of message)
ExitCode Code=”1618″/></p1:ExitCodes><p1:UserInteractionMode>Hidden</p1:UserInteractionMode></p1:CustomData></p1:Installer></p1:DeploymentType></AppMgmtDigest> SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

ERROR CCISource::InsertObject returned 14 SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspconfigurationitem.cpp(2152) : There is a failure while generating lantern documents for this configuration item~*~* SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

*~*~There is a failure while generating lantern documents for this configuration item ~*~* SMS Provider 9/5/2013 5:03:28 PM 3704 (0x0E78)

———————————————————–

I searched for several hours trying to find any references to the errors I was receiving or issues between .NET 4 and CM 2012. There were several pleas for help, but no solid solutions. Then I decided to start searching on security update conflicts and came across this post:

http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx

My first attempt to test the cause of the issue was to uninstall KB 2840628, which did not change anything, even after rebooting both the SQL server and the primary site server. I was going to employ the security settings work around, then I read the details of the KB article, which indicated that the update had been republished 8/13. I had installed the update on the SQL server on 8/8, so I installed the new update, rebooted both the SQL server and the primary site server and all is working fine.

I just thought I would post this in the event others may be experiencing this issue.