Flexera Software Customer Community

Flexera Software provides a wide variety of resources for customers to engage other customers, access product resources such as documentation and a Knowledge Base, engage technical support, download licensed products and submit product enhancement suggestions. All of these resources and more are available in the Flexera Software Customer Community. Watch this short video to learn more.

Read More»

Windows as a Service: What Does Windows 10 Mean for Your Business?

“Upgrades may break apps”, that’s the issue that enterprises face every time they introduce new operating systems or platforms into their enterprise environment. Maturing your Application Readiness process will empower your organization to keep up with Windows updates and ensure compatibility and predictability of your application service delivery.

Read More»

Windows Could Not parse or process unattend answer file for pass [specialize] in MDT

Here is an issue that took me a while to track down and resolve. Scenario is a small MDT2013 environment that has been upgraded from MDT 2012 Update 1 and MDT 2012 before that. It has a few TS but the two used mostly are to Deploy Windows 7 64-Bit and Build and Capture. 

Each quarter I do a B&C via this second TS. Nothing has changed in years for this TS. It applies install.WIM (from DVD source), disables System Restore and patches from WSUS. This image is then used in the Deploy TS as the base. So imagine my surprise when it goes through the B&C and I swap it into production and do testing and I get this informative dialog:


“NOOOOOOO” -Darth Vader

Wait, that didn’t happen, I’m a despecialized camper. So I do what anyone does, rinse and repeat and create a new patched WIM. Ugg same error. Do a deploy from the previous quarter WIM and that works so nothing else was changed. Just not the new B&C WIM. What changed? Checking %WINDIR%\Panther\Unattend.XML, this section looks fine without any common problems. Parsing the panther logs didn’t really pull up anything other then that there was a syntax error. Back in Unattend.XML start looking closer. Computer name is under 15 characters (its a VM that gets set to ‘VMHost’), No illegal characters in the computer name, serial key is correct, CS.INI is still good, etc. I bet it was something WSUS was giving it. Hmm, back to unattend.xml to do a diff of the unattend.xml against one used for Windows 8.1 as that did a quarterly update process fine. Found one difference under specialized other then the serial key:


 <IEWelcomeMsg>false</IEWelcomeMsg>  


Deleted this line and problem solved. Took a while to diagnose and fix this issue so thought I’d share. Searching for this setting, others have encountered it and some just comment it out like this.

 <!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->  


There are several ways to fix it. I just modified unattend.xml in \\MDTSERVER\DeploymentShare\Control\TaskSequenceID. I also changed each XML for each TS.


Another way is to go into the Deployment Workbench and right click your task sequence and goto the OSInfo tab and select edit unattend.xml. Wait a while for it to process as it extracts the WIM. Then use windows system image manager (WSIM) and find (ARCHITECTURE)_Microsoft-Windows-IE-InternetExplorer. Then look for IEWelcomeMsg and right click and disable “write image value”, or delete it. Save the unattend and your good to go.  Or open the Unattend.XML in the Control folder directly with WSIM. It was just quicker to edit it with Notepad etc.


Looking at the MDT 2013 templates under %ProgramFiles(x86)%Microsoft Deployment Toolkit\Templates it does not have this setting so MDT 2013 will not create new TS unattends with this and this only affects existing TS created in older versions of MDT. Another reason to create a new TS and migrate steps I suppose. I do that in ConfigMgr each Release or SP and sometimes CU if I suspect it will impact built in Task Sequence steps.


Turns out what the root cause was is they moved from IE9 to IE11 by approving it in WSUS. Starting with IE10, MS deprecated this IEWelcomeMsg setting and replaced with DisableWelcomePage. Additionally, Its deprecated in Windows 8 and up. This is why I deleted it from the XML.


-Kevin Fason

Read More»

You’re Getting Warmer—License Management for Hot, Warm, and Cold Backup Servers

By John Emmitt Managing datacenter server software licenses, as we all know, can be a challenge. One of those challenges is dealing with licensing terms and conditions related to backup servers. First, you have to know—what is the “temperature” of that backup server—hot, warm or cold. Licensing requirements are typically different depending on the type of backup in question. Licensing terms and conditions also vary from publisher to publisher and product to product. Let’s try to define some terms—what do we mean by hot, warm and cold backup (or “standby”) servers? What about Active and Passive Failover? Hot Backup Server…

Read More»

How to Add a Third Deployment Type (Windows 8.x) to an Existing Application

By Garth Jones I am starting to manage my collection of mobile devices by using Intune with ConfigMgr 2012 (CM12), and one of my tests involved deploying applications to these same devices. After creating an application with the first deployment type for Android OS, yesterday I demonstrated how to setup the iPhone deployment type. Today I’ll show you how to...

Read More»

How to install SCCM 2012 Application Catalog

In part 1 of this SCCM 2012 R2 Installation Guide blog series, we planned our hierarchy, prepared our SCCM 2012 R2 Server and Active Directory. In part 2, we installed and configured SQL in order to install SCCM 2012 R2. In part 3, we installed a stand-alone SCCM 2012 R2 Primary site. In the next 16 parts, we will describe… Read More »

The post How to install SCCM 2012 Application Catalog appeared first on System Center Dudes.

Read More»

Create an Application for Different Deployment Types Starting with Android Devices

By Garth Jones I wanted to manage my collection of mobile devices by using Intune with ConfigMgr 2012 (CM12), so I began by setting-up the Intune connector between my CM12 site and Intune. Next, I deployed the Company Portal to all of my test devices. I did this to test the inventory retrieval capabilities (both hardware and software) of Intune...

Read More»

ConfiMgr 2012 R2 Health Check toolkit – Beta 03

Over the past few weeks I have been busy updating the System Center 2012 R2 Configuration Manager HealthCheck Toolkit (CM12R2HealthCheck) to the version 0.03 and today I’m pleased to say that is has been released. What is the System Center 2012 R2 Configuration Manager HealthCheck Toolkit? The System Center 2012 R2 Configuration Manager HealthCheck Toolkit (CM12R2HealthCheck) has been created to check for problem and/or misconfiguration in the SCCM environment and, when possible, will provide you with some solutions for problems. This version contains a series of bug fixes, performance improvements as well as new functionality. We also would like to add the following notes/requirements: We have tested this tool on a single primary site and single primary site with secondary sites. We do expect it to work on a CAS environment, however, we have not been able to test. We have run the tool remotely as well locally on the…

Read the complete blog: http://thedesktopteam.com/blog/raphael/confimgr-2012-r2-health-check-toolkit-beta-03/

Read More»