Henk's blog statistics (part 2)

Almost a year ago I posted statistics on my blog. Because it's nice to have some statistics, and posting blogs for almost 4 years now, let's do it again. This because the amount of visitors and pageviews is still increasing. Hope you like my posts on Microsoft Configuration Manager, Operations Manager and other topics. Here we go!

Google Blogger:
First post: 13 October 2010
Number of posts: 384 (included this one)
Posts a year: 158 (2013) 75 (2014) > and growing

Most viewed: PXE Boot files in RemoteInstall folder explained
Most comments: Multicast error 0x80091007 during deployment
Most likes (+1): Updates and New Features in ConfigMgr 2012 R2

Most pageviews 'all time'

Pageviews a day: ± 1.200 - 1.300
Pageviews last month: ± 32.000
Pageviews all time: ± 780.000

Google Analytics:
Visitors a day: ± 500 - 600
Visitors last month: ± 12.000
Visitors last year: ± 110.000

Country pageviews 'all time'

Most search keywords: system center 2012
Most traffic sources: www.google.com
Most audience: United States

Since last year Google Analytics is installed, so therefore more statistics! Hope to reach 1.000.000 pageviews next year :)

Google Analytics 'last year'

Blogpost: Statistics 2013

Sources for statistics: Analytics & ClustrMaps

The software distribution policy was not found (Error 87D02004)

Just when you thought you seen every error message in ConfigMgr, I have some news for you. Today I recognized a new error; never seen it before actually. On a Windows 7 SP1 task sequence, which was running fine, it went wrong on first package after Windows during a new deployment. When looking in the smsts.log the following line was seen: The software distribution policy was not found. (Error: 87D02004). What's that?

Looking on the web I found the following post: Windows Noob
It mentions: I have just changed all the packages to Applications. Another option is to use Run Command Line for the packages.

So I changed all packages (10 of them) to install by Run Command Line and it went fine after all.
When looking in some more logfiles there were some interesting things seen, exactly during the same timestamp):
-ClientIDManagerStartup.log (during the package error, ConfigMgr was still busy with client configuration)
-LocationServices.log (during the package error, ConfigMgr was busy with finding a Management point)
-Execmgr.log (during the package error, ConfigMgr could not find policy in WMI for the specific package)

Trick is you need to put a "Restart computer" step after ConfigMgr client installation, so it has more time to finish configuration and find a Management point. The policy will be find afterwards also. Because we are talking about a Workgroup join here, it's also a good idea to put some extra parameters during the ConfigMgr client installation step. That will be SMSMP=<FQDN> FSP=<FQDN> DNSSUFFIX=<?>

Hope it helps!

Microsoft Unified Technology Event for Enterprises is coming!

After ending Microsoft Management Summit (MMS) last year, now same will be happen to Microsoft TechEd. No worries, this time a new event is scheduled, which will be the successor of both events. It's called "Unified Technology Event for Enterprises" or UTEE if you like. So TechEd Europe in October 2014, Barcelona will be last one in the series. Let's hear what Microsoft has to say about this:

 

If you’ve attended TechEd, SharePoint Conference, Microsoft Exchange Conference, Lync Conference, Project Conference or Microsoft Management Summit, this the place for you to be. It’s everything you’ve come to know and love and more. You’ll find what you’re familiar with and you’ll learn more about Office 365, Microsoft Lync, Microsoft Exchange, Microsoft SharePoint, Microsoft Project, Microsoft Visio, Microsoft Azure, Windows Server, Microsoft System Center, Windows Intune, Microsoft SQL Server, Visual Studio, and Windows and lots more.

Sounds huge isn't it? There will be One single event in May 2015, Chicago. If there will be additional events in the rest of the world isn't clear to me. The only Microsoft-owned events left will be WPC, BUILD, and UTEE for it seems. All other conferences will be rolled up into this new one. More details about UUTE will be revealed in September. Note that "Unified Technology Event for Enterprises" is not the official name for the event, the final name has not yet been revealed. I'm curious what the new name will be.. Let's call it UNIFY or MANAGE.

See you in May 2015, Chicago hopefully! :-)

Source: Server & Cloud blog

Strange issue in Monitoring status after OS deployment

Last months I did a lot of ConfigMgr 2012 R2 implementations. Nothing to worry about if you ask me, except for a few things. When doing a lot of OS deployments (on Windows 7 SP1), the Monitoring status is not as it should be. Let me explain what I'm seeing. When doing deployments (task sequence), I recommend to have a look at Monitoring (deployment) status. There you have a good overview of progress on al kind of deployments. More about that can be found here: OS deployment monitoring in ConfigMgr 2012 R2.

Within last months (never seen it before actually) deployments are not Always successful. You will see the following lines in Status Message Viewer (for a specific system):
-11171: The task sequence manager successfully completed execution of the task sequence.
-10804: The ConfigMgr client was reassigned. The previous site code was "". The new site code is "###". (few minutes later)
-10018: Deployment "########" from site "###" was rejected because the client's platform is not supported. (few minutes later)

 

What happens is that after a successful deployment (which is Message ID 11171) another deployment is starting (?) for it seems, and this is generating a rejected deployment (which is Message ID 10018). So it's succesful, and then it's rejected afterwards? Therefore no successful status message is displayed in ConfigMgr console anymore. At one customer this is the case on ALL (re-)deployments on systems. At another customer this happens to 1 on 10 systems, at both new deployments and re-deployments.

At the moment I have contacted Microsoft support for this. They are still investigating the issue, so hope I have more information soon. When anyone recognizes above issue, I kindly like to hear more about it. Maybe it's a bug, but I don't know at the moment..

Some people saying (Microsoft support included) I must change task sequence properties to support all platforms. When looking at the issue this may be the case. Strang thing is I never change this option, so it's on "Run on any platform" as Always. Hope that anyone can tell me how to solve this! Otherwise MS will tell me soon hopefully ;)

Update 8-9-2014: As mentioned by Microsoft and Robert Kloek in comments, a workaround can be used to get the job done. Just deploy the task sequence to "ConfigMgr clients, Media and PXE" instead of using "Media and PXE only". That way a successful message is showed in the end, and not the "Requirements not met" message. This seems to be a change to me, but it helps for sure!

How to create a collection based on a Message ID 11171

At some customer they were asking me how to create a collection in ConfigMgr, based on a Message ID. In this case this must be Message ID 11171, which tells me that systems are deployed successfully. I did a lot of try outs, but none was successful after all. Let's have a look.

In this case some OS deployments are successful, some are in progress, in error, requirements not met, or unknown status. Because the information is in the ConfigMgr database, it must be easy (I guess) to show this information in collections as well. Strange thing is, I couldn't find it on all WQL options available..

After a few tries I did created a query which showed me some information. Unlucky me it showed around 240 systems, where Monitoring status showed me around 650 systems successful. Why not showing ALL systems deployed successfully? Limiting collection was "All Systems" which is limiting to, well.. ALL systems ;)

Let's have a look at the query used:

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

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  
 JOIN sms_statusmessage ON sms_R_System.netbios_name0 = sms_statusmessage.machinename   
 JOIN sms_StatMsgInsStrings ON sms_statusmessage.RecordID = sms_StatMsgInsStrings.RecordID  
WHERE sms_statusmessage.messageid = "11171" 
AND sms_StatMsgInsStrings.InsStrValue = "The task sequence manager successfully completed execution of the task sequence"

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

Does anyone knows how long this information can be used on collection membership? Because both Monitoring status and Reporting services are showing me around 650 systems, this must be possible in collection membership to? Hope to find a WQL query for doing that soon! When possible in WQL options I like to hear it also ;) 

Event 10102, Health Service Modules, PerfDataSource warnings

On a ConfigMgr server at customer location I did see a lot of Event 10102, Health Service Modules, PerfDataSource warnings. Every 75 minutes, there were a lot of warnings detected, and customer want me to resolve this. Let's have a look.

A warning was looking like this:
In PerfDataSource, could not resolve counter SMS Inbox, File Current Count, swmproc.box>usage. Module will not be unloaded.
One or more workflows were affected by this. 
Workflow name: Microsoft.SystemCenter2012.ConfigurationManager.Perf_Threshold_Site_server_SWM_inbox_backlog_monitor
Instance name: ConfigMgr Primary Site Server - <removed>
Instance ID: {ECB782E3-F42F-23D2-C609-65CC8B78BA48}
Management group: <removed>

Because this message was coming from Operations Manager, and the OpsMgr Action account was configured on local system, I thought it would be a good idea to have a look at local administrator permissions. Long story short, I added both ConfigMgr SYSTEM account and SQL service account to the ConfigMgr server local administrator permissions, and after reboot no warnings were there anymore. In the end it was a security issue after all. Hope it helps!

OSD TS Fails during package download (WinHttpSendRequest failed 0x80072ee2)

During deployments last day on A VMware VDI environment (with a hugh task sequence) OSD was failing on a random package installation everytime. This on a ConfigMgr 2012 SP1 CU4 environment with around 50+ packages in the deployment task sequence.
Upgrading the environment from SP1 to CU4 didn't solve the issue. Upgrading the environment to R2 CU2 isn't the solution also, when I must believe the MS TechNet forums. Case is there is a bug in ConfigMgr, so deployment can be broken on a random package installation. That's no fun at all.

Errors during deployment are:
- WinHttpSendRequest failed
- WinHttpRequest failed 80072ee2
- DownloadFile failed 80072ee2
- Error downloading file from http://<package location>:80
- DownloadFiles failed 80072ee2

Looking on the forums I found the following post: Microsoft TechNet
It's mentioning the following:
We got a reply from Microsoft. The issue as been verified in their lab, and they are working on a proper solution.
The workaround suggested by them is as follows:
Create two Task Sequence Variables at the very top of the TS, right below "Execute Task Sequence"
SMSTSDownloadRetryCount = 5
SMSTSDownloadRetryDelay = 15
I've done this myself, and the TS now completes.

So after all it's a bug!? Looking on Microsoft TechNet again you can see that both variables are available only on "System Center 2012 R2 Configuration Manager". Leaves me in an unsuccessful situation, where I must upgrade (again) to R2 CU2 this time, to make usage of the variables in the task sequence. Not so good Microsoft.

Note: After migrating to R2 CU2 and multiple deployments I can confirm that deployment is working fine with above variables.

Delete multiple Packages in Configuration Manager 2012 SP1

Sometimes it's needed to delete multiple software packages in the ConfigMgr console. By default this isn't possible, when selecting multiple packages this option will be greyed out. In my case it was needed to delete around 50 packages.

By deleting a package you must select multiple clicks also, this because you have:
1) Click Delete
2) Click Next
3) Click No, I know that I want to delete this package
4) Click Next
5) Click Next
6) Click Close

You don't want to do that for over 50 packages, which are 300+ clicks then. Just have a look at a easier way. From within the ConfigMgr console start "Connect via Windows PowerShell".

Then type in the following command:
Remove-CMPackage -Name "Package name" -Force

You can also type Remove-CMPackage and click Enter. Then you can enter as many Package ID's as you want and press enter twice. Then you must press enter for every package that you want to delete.

Way better then 6 clicks for every package if you ask me! ;)

Install Cumulative Update 2 for ConfigMgr 2012 R2

Today I had time to install Cumulative Update 2 (CU2) for ConfigMgr 2012 R2. KB2970177 (CU2) solves a lot of issues in ConfigMgr and is therefore highly recommended. More about CU2 improvements in another blogpost. No need to install CU1 anymore, because it's integrated in CU2 (which is same as other cumulative update packs before). No need to install the latest Endpoint Protection anti-malware platform update also (which is from March 2014 at the moment). This one is integrated in KB2970177 (CU2) as well.

After installation, which is default as always, there will be update packages created and the version will be updated (5.0.7958.1303). To be better safe then sorry do a restart of the ConfigMgr server after patching. Still strange that Microsoft is saying it isn't needed (TechNet), but the installation wizard mentions it is needed! :)

After setup you have the benefit of all updates and hotfixes. Don't forget to update other ConfigMgr servers, consoles and clients as well. You can find packages for that in the console after the update.

Certificate untrusted after changing IP-address of ConfigMgr server

When changing the IP-address of the ConfigMgr server it's needed to register certificates for the site server and boot media again. This is done by default during ConfigMgr installation and configuration, but not after changing the IP-address on the server. Just have a look in the ConfigMgr console, Administration, Security, Certificates.

Here you will see multiple certificates which are partly blocked and unblocked. Just open the unblocked ones, and install certificates when needed. In my case this was needed on all unblocked ones! Just install them for "Local Machine" and "Trusted Root Certification Authorities" in the wizard, and you will be fine after that.

Install Certificate

Mission accomplished

After that communication on site systems and deployment is running fine again. No further issues after the IP-address change at all.

Veeam Backup & Replication v7 (Patch 4)

Sponsor post

Patch 4 for Veeam Backup & Replication v7 is now available and contains a host of resolved issues as well as new features and enhancements, including:

• VMware Virtual SAN (VSAN) support: Added full VSAN support and enhanced the intelligent load-balancing engine to account for VSAN specifics, minimizing backup traffic on a VSAN cluster network, and thus reducing impact from backup activities on the production environment.
• Microsoft SQL Server 2014 support: Added support for SQL Server 2014 as the protected guest workload and the back-end database for backup and Enterprise Manager servers.
• License key auto update: Added an automated license key update option to the license Information dialog. When enabled, backup server will start checking the Veeam licensing server for an updated license key periodically. Once the new key is available, it will be downloaded and installed automatically, eliminating the need for manual import.

 

For a complete list of new features and resolved issues, and to download Patch 4, check out the following Veeam KB article: KB1891.

Learn more & Download

Cumulative Update 2 for ConfigMgr 2012 R2 released

Last week (on June 21, 2014) Cumulative Update (CU) 2 for ConfigMgr 2012 R2 is released. It contains 20 updates and hotfixes included. No need to install CU1 anymore when using this one.
 
Here's a list of issues that are fixed, there are quite a lot of them:
- Administrator Console (2 fixes)
- Application Virtualization (2 fixes)
- Operating system deployment (5 fixes)
- Asset Intelligence (1 fix)
- Mobile device management (1 fix)
- Software distribution (3 fixes)
- Site systems (4 fixes)
- Configuration Manager SDK (1 fix)
- Client (1 fix)
 
In addition to various issue fixes, this update also includes the following:
- An updated Cumulative Update Setup Wrapper (Installer)
- Updated list of supported Linux and UNIX clients
 
Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

This update replaces Cumulative Update 1 for System Center 2012 Configuration Manager R2 

For more information or download the update have a look here: Microsoft Support

Cumulative Update 4 for ConfigMgr 2012 SP1 released

On January 28, 2014 (missed that one) Cumulative Update (CU) 4 for ConfigMgr 2012 SP1 is released. Missed that because I'm doing ConfigMgr 2012 R2 implementations a lot, but that's no excuse ;) It contains 13 fixes and/or improvements this time.

Today I'm installing this update because of a lot of issues on a ConfigMgr 2012 SP1 environment. Therefore it's still a valid installation, because there's no SP2 available.
 
Here's a list of the issues that are fixed:
- Software distribution (4 fixes)
- Operating system deployment (4 fixes)
- Administrator console (1 fix)
- Application Virtualization (2 fixes)
- Endpoint Protection (1 fix)
- Site Server (1 fix) 
 
Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

This update replaces Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 1
 
For more information or download the update have a look here: Microsoft Support

Installing remote distribution point failed with 0x80041001

Last week I installed multiple remote distribution points on Windows Server 2008 R2 systems. The installation went to be fine, but no files were replicated on disk. This because of multiple distribution errors, which can be found in the distmgr.log:
-CSendFileAction::AddFile failed; 0x80041001
-CSendFileAction::SendFiles failed; 0x80041001
 

 
I did choose "Install and configure IIS if required by Configuration Manager" during installation, but IIS was installed already on servers. I did install BITS on servers also, because this seems to be needed (installation can be failing otherwise). Strange thing, because BITS is no prerequisite at all? What I did NOT however is installing RDC as a prerequisite. Therefore files couldn't be replicated after all.

Note: With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS.
 
Note: The Remote Differential Compression (RDC) feature is a set of application programming interfaces (APIs) that applications can use to determine if a set of files have changed, and if so, to detect which portions of the files contain the changes. RDC detects insertions, removals, and rearrangements of data in files, which enables an application to replicate only the changed portions of a file. This is useful when replicating files over a limited-bandwidth network such as a wide area network (WAN) connection.
 
Let's have a look for all prerequisites also, for a distribution point you need: 

• Application Development (IIS)
• ISAPI Extensions
• Security (IIS)
• Windows Authentication
• IIS 6 Management Compatibility (IIS)
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility
• BITS (feature)
• RDC (feature)

Source: Supported Configurations for Configuration Manager