You are browsing the archive for 2010 January.

Application Compatibility Toolkit Connector Update for Windows 7 deployments

2:06 pm in Uncategorized by Kenny Buntinx [MVP]

To help you accelerate their testing and deployment of applications on Windows 7 , Microsoft has the Application Compatibility Toolkit Connector (ACT Connector) that assists administrators with collecting the necessary computer and application compatibility information to help plan for a Windows deployment.

The ACT Connector provides the following functionality within the Admin console:

  • Inventories installed software applications and creates reports that will assist with determining which applications are Windows compatible.
  • Retrieves device driver compatibility for installed devices and creates reports that will assist with determining which device drivers will need to be upgraded to support the Windows operating system.

 

Read the complete blog post from the product team on http://blogs.technet.com/systemcenter/archive/2010/01/29/application-compatibility-toolkit-connector-update.aspx

Hope it helps ,

Kenny Buntinx

SCCM OSD : HP Quicklaunch application installation integrated in a task sequence

2:56 pm in Uncategorized by Kenny Buntinx [MVP]

My issue today was again a fight to integrate the HP Quick Launch Drivers into my OSD task sequence.

I am installing it as part of  my Windows XP SP3 build ( I know it should be Windows 7 , but at my customer I have to provide still support :-) , and have added the full install for 6.40 into the task sequence. The application fails every time. I am simply using setup –s as stated into the documentation !

I have tried extracting the keyboard filter and button drivers from the installation on a good machine, and added these to the driver repository with a driver package. But they do not install, and the logs just show that the install failed.

After some research , I have read that there were issues with the keyboard filter drivers in earlier versions of the Quick Launch tool where it failed , but it was fixed in release 6.30.

After a lot of searching , here is the real deal :

You should use the following command : SETUP.EXE -s /f2c:\setup.log ( the setup needs to be able to write to a log file on the C:\ drive when you try to install it .

 

image

Hope it Helps ,

Kenny Buntinx

Windows Embedded Standard 2009 support statement for SCCM 2007 updated

6:50 am in embedded, OSD, sccm, SCCM 2007 by Kenny Buntinx [MVP]

Hi All,

 

If any of you happen to be playing around with WES 2009 and System Center Configuration Manager 2007, you might want to have a look at the new blogpost at the ConfigMgr’s product team blog:

http://blogs.technet.com/configmgrteam/archive/2010/01/25/things-you-need-to-know-when-using-windows-embedded-standard-2009.aspx

 

The updated support statement is mentioned there, as are the 2 most important things impacted by this new statement:

  • Write filters are now supported
  • Sysprepped operating systems are now supported, which in turn means that OS deployment for WES 2009 is supported (not for any of the other supported embedded os’s).

 

The article does mention some requirements for all of the above to work though.

Some registry keys need to be excluded from the write filter, and some additional components are needed for OSD and some other SCCM features.

More details in the post mentioned above.

 

Enjoy.

"Everyone is an expert at something"
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm/default.aspx

http://www.linkedin.com/in/kimoppalfens

Packaging tools to Create MSI’s

1:06 pm in Uncategorized by Kenny Buntinx [MVP]

Hi All,

 

Since my sccmautodoc program is getting close to completion I set out to try and see whether I could create an install for it.

Most of the bug reports I received back was from people that didn’t have all the requirements installed. SccmAutoDoc needs the .net framework 3.5, word 2007,and the .Net program interop assemblies for word 2007.

I started of by trying to do this in Visual studio as it contains a setup builder, yet for this poor little techy, having it detect all these dependencies was a bit challenging. Using some blogpost I figured out how to have it test for the .net framework 3.5 and the office 2007 pia’s, but testing for word 2007 was beyond me.

As a result I started my search for a packaging tool, and started of by looking at the 2 market leaders flexera and wise, to quickly find out that even their most basic editions are relatively expensive. Flexera offers a free ConfigMgr edition, but that version installs all tools from the enterprise edition with most of them disabled and giving you a nagging windows box when you try to use them.

 

Subsequently from this post at windowsnetworking.com I found two other contenders, namely, Advanced Installer and Scriptlogic MSI studio. I went to both their websites, and both seemed to offer what I wanted. I eventually went and downloaded advanced installer, as it was hassle free to download and evaluation version of even their enterprise edition. Just click the link and download, no registration required, simple hassle-free, no risk of having a representative contact me to see whether I liked it 2 hours after I downloaded. In short, evaluation software just like the good old days.

Download & install were a breeze, now I needed to make my hands dirty and hammer out my install program. And in contrast to what I expected, my most challenging task in Visual studio (checking whether word 2007 is installed) was as simple as enabling a checkbox in advanced installer. And having the .net framework tested and potentially downloaded when needed didn’t take me more than 5 minutes neither. Integrating the .Net Program interop assemblies took a bit longer, as the download from the internet wouldn’t work. The office 2007 pia download appears to be a self-extracting exe that downloads an msi, that needs to be manually launched after that. On the advanced installer forums I found a post that suggested integrating the msi into your installer, and with that knowledge, it again only took me a couple of minutes to finish off my installer.

 

I am pretty happy with the result, it detects everything you need at install time, and even installs most components for you if you need them (word 2007 excluded obviously).

So if you are looking for an inexpensive packaging solution because you only require a packaging program every so often, have a look at advanced installer, it certainly did what I needed it to do in a pretty intuitive way.

Alternatively have a look at scriptlogic MSI Studio, I haven’t actually used it, as advanced installer was easier to get my hands on, but I have heard good things about it too.

 

Enjoy.

"Everyone is an expert at something"
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm/default.aspx

http://www.linkedin.com/in/kimoppalfens

SCCM SP2 Hotfix KB978021 :The Distribution Manager that is in System Center Configuration Manager 2007 SP2 does not honor the "Number of retries" and "Delay before retrying (minutes)" retry settings

2:51 pm in Uncategorized by Kenny Buntinx [MVP]

The distribution manager (distmgr, the component that is there for distributing the packages to a distribution point) seems not working as we would expect with SP2.

Consider the following scenario:

  • The distribution point role is installed on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
  • You customize the retry settings on the Distribution Point tab for the distribution point. Or, you use the default value for the retry settings.
  • A retry is required after a package distribution fails.

In this scenario, the Distribution Manager does not honor the retry settings on the Distribution Point tab when the Distribution Manager retries the distribution.

You could find the hotfix and KB article on : http://support.microsoft.com/kb/978021/.

 

Hope it Helps ,

Kenny Buntinx

App-V : Updated OS VALUE XML Tag References and Supported Client Versions

7:34 am in AppV, ConfigMgr 2007 R2, ConfigMgr SP2, SCCM 2007 R2, SCCM 2007 SP2, Windows 7 by Kenny Buntinx [MVP]

I was trying to test applications that were sequenced for windows XP on Windows 7 . The problem was that I needed to update the OS VALUE XML in the config file .

I came across an article from Steve Thomas , Senior Support Escalation Engineer at Microsoft with a great list of OS VALUE XML tags linked to the operating systems witch I have used below. You can see the full post at : http://blogs.technet.com/softgrid/archive/2009/10/29/updated-os-value-xml-tag-reference-and-supported-client-versions.aspx

The following table lists the supported OS VALUE element options and the minimum supported client versions for Microsoft SoftGrid and Microsoft Application Virtualization.  This element defines the required operating system. If there are more than one OS element in a particular IMPLEMENTATION tag, it is implied that the software package works with each. If none are present then it is assumed to run on all operating systems:

image

Hope it helps ,

Kenny Buntinx

SCCM Vnext : TAP Nominations are open !

7:24 am in Uncategorized by Kenny Buntinx [MVP]

Finally , the bullet is thru the church… TAP nominations to the SCCM Vnext are open and a lot of people expect great features and improvement made to the product .

Certainly now SCCM Vnext is going to focus more on the “User , device  & connection centric” part .

For myself as MVP this is going to be a very exiting year : learning new technology and helping the product team out with testing the beta products.

To find out more check out the following post on Nexus SC: The System Center Team Blog:

http://blogs.technet.com/systemcenter/archive/2010/01/08/the-next-wave-of-client-management-begins-now.aspx

Link to Nomination Survey is here.
More information about the Microsoft TAP program can be found here.
System Center product information can be found here.

For myself as MVP this is going to be a very exiting year : learning new technology and helping the product team out with testing the beta products.

Hope it Helps ,

Kenny Buntinx

Techdays 2010 Here we (The Scug team) come

1:48 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, configmgr2007, sccm, SCCM 2007, SCCM 2007 R2, sccm2007, SccmAutoDoc, SMS by Kenny Buntinx [MVP]

Hi All,

160x600Just received confirmation that I will have a speaker slot again, for the 4th year in a row at the Belgian Techdays.

So me, and the rest of the Belgian SCUG team will be present to talk to you about System center configuration manager, system center operations manager and even system center service manager by then, as Kurt Vanhoecke our local service manager expert that even got referenced at the service manager product team blog, will most likely be there as well.

My session will be a pretty non-typical SCCM session this year. From my personal experiences, i.o.w. by authoring SccmAutoDoc, I believe I learned a few extra things on ConfigMgr and WMI. Even in the past I have considered knowledge of WMI an incredible asset for any SMS/SCCM admin, but deepdiving into it for SccmAutoDoc has only enhanced that belief.

So without further ado, here comes the session abstract:

Since its first debut System Center Configuration manager and its predecessors have been relying heavily on the Windows Management Instrumentation (WMI) architecture. WMI is omni-present is System Center Configuration Manager, from queries over dynamic collections, through hardware inventory and storing client and Management Point settings and policies, under the hood you will find WMI just about anywhere. Given this omni-presence it should come as no surprise that the stability of WMI at your Site Systems and clients is crucial to a stable System Center Configuration Manager implementation. Knowing WMI, by consequence, is a great asset to any System Center Configuration Administrator. In this session you will learn the ins-and-outs of the WMI architecture in general and how it applies to System Center Configuration Manager. You’ll learn about the available namespaces and classes and the extended WMI Query language (WQL) that is specific to System Center Configuration Manager. This session will cover the tools available to have a peak at WMI yourself as well as to the WMI-related tool called policy spy that comes with the System Center Configuration Manager toolkit. By the end of this session you’ll know what the WMI architecture looks like, how System Center Configuration Manager uses it, and how you can use that knowledge to your advantage, be it to be able to better troubleshoot System Center Configuration Manager issues, better understand the product, or to automate tasks through scripting or programming. In the end this session will make you a better System Center Configuration Manager administrator.

 

I sincerely hope to see you all there, and before I forget, best wishes to everyone reading this.

Kim Oppalfens

System Center Configuration Manager MVP