You are browsing the archive for 2010 February.

Preparing for the MVP summit 2010

12:42 pm in Uncategorized by Kenny Buntinx [MVP]

Hi All,

Just getting myself ready for the MVP summit in Seattle next week, as our other 2 SCUG MVP’s ( Kim Oppalfens & Alexandre Verkinderen ) .

For me it is going to be an exciting event for me , as it is my first MVP summit I’ll be attending since my nomination in July 2009.

For those of you that don’t know what the MVP summit is, It is a week full of working, talking and discussing together with our MVP pears , but also with the (In my case) SCCM product group.

I’m really looking forward to meet with members of the Microsoft product groups and directly learn from those people who are responsible for the individual product features and I see this as a real honor.

So if the blogging level is a bit low on SCUG.be next week , you will know why this is ….

 

Hope it Helps ,

Kenny Buntinx

HP ProLiant Hardware Inventory Tool for Configuration Manager 2007 (howto)

1:15 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

Yesterday , I ran into a customer who wanted me to extend there Hardware inventory with there Compaq and HP Server equipment such as ILO Serial number , physical Memory slots  , etc. Instead of making me sweating , I found the HP ProLiant Hardware Inventory Tool for Configuration Manager 2007 on the HP website : http://www.hp.com/support

The HP ProLiant Hardware Inventory Tool for Configuration Manager 2007 uses the HP Insight Management Agents to obtain HP-specific hardware information from System Center Configuration Manager 2007 client servers and adds this information to the database of the site server. The inventory tool runs on each specified client, creating a series of intermediate .MIF text files, which contains the information about specific client servers. The Configuration Manager Hardware Inventory Agent processes these files and sends them to the site server to update the appropriate database.

1. Go to the downloaded files and run the “HPProLiantHwInvToolForConfigMgr01_0.exe”

image

This will implement certain default collections , packages and advertisments. You could modify those or start from scratch like I did .

2. Do not forget to activate your HW inventory and to select : “Collect _NOIDMIF Files” .

The Inventory Tool generates the .MIF files on each node. The .MIF files are not automatically populated to the site server database.To ensure that the .MIF files are collected, you must enable the NOIDMIF files option in the Hardware Inventory Client Agent Properties as shown in the picture below :

image

3. Create your package or modify the default created one . Look at the default created program and modify according the screenshots below :

image

On the General Tab :

image

On the Environment Tab : “When ether or not a user is logged in”

image

On the Advanced Tab : “Suppress program notifications”

image

4. Create your collection where you going to target your program to.

image

Create a dynamic membership based on the following criteria :

Computer System Model lowercase is like %proliant%

image

5. Create your advertisment and on the shedule tab , rerun on weekly basis on your previous created target collection .

image

The inventory tool obtains the information and then displays it in the Configuration Manager Resource Explorer for the client server. In the example below you will see that there are field added , such like HP …

image

In this example , the HP Prolaint Software and Firmware :

image

In this example , the HP smart array Physical Drive :

image

Hope it Helps ,

 

Kenny Buntinx

App-V : Sequencing the SCCM 2007 Console ( howto )

1:00 pm in AdminUi, AppV, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, Installation, MMC updates, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, Virtual machine by Kenny Buntinx [MVP]

More and more customers are demanding a swift and easy install of the SCCM console , especially when it comes to upgrade your consoles when a new service pack comes along.

As my customers also have App-V in the house , witch is part of MDOP 2009 by the way , I was also interested to make the console virtualised.

After a few rounds of trying , I did not succeed in creating a virtualized SCCM console as an App-V package

Therefore , I want to explain to you all how to do it . But I couldn’t have done it without the help of Richard Ruiz from MSFT and a blog post on the technet forums.

Prerequisites : To make it yourself easy , please prepare a blank machine ( base XP SP3 with latest software updates ) into a virtualized world where you can use snapshots and revert to the original state as much as you want . I will save you an enormous amount of time.

Procedure :

1. Install all prerequisites (e.g. MMC 3.0, etc.) and your SCCM 2007 SP2 Console natively on your clean WinXP SP3 workstation, to the exact location you will be sequencing to. In this example we used D:\SCCMSP2 (stick to the 8.3 format)
2. Export the following keys and save them to a central location:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{6de537a5-7a1c-4fa4-ac3a-1b6fc1036560}]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{a77b774c-ce32-4ab0-982a-6bb3c078e5c1}]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\AdminUI\QueryProcessors\WQL]

3. Turn Off your virtualized machine and delete all changes made (VHD) or if you use a physical machine , reimage your sequencer to a clean state. 
4. Install your App-V Sequencer and create your folder D:\SCCMSP2 (used in our example)
5. Install all your prerequisites for your SCCM 2007 SP2 Console (e.g. MMC 3.0, etc.) natively 
6. Start your sequencer and when you reach the “begin monitoring” and the sequencer flips to the background , start installing your SCCM 2007 SP2 Console in the previous defined path (in this case D:\SCCMSP2).

7. You could if you want install additions such as the famous “SCCM Right click tools” from Rick Houchins at http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx

8. If you have R2 , install R2 to the same folder , ae D:\SCCMSP2

9. After your installation is complete  and before you stop monitoring, import the 3 previously exported registry keys. 
10. Launch the Console and test functionality, then complete the installation.If you have installed the right click tools , you also need to test all functionallity ! 
11. During the Application Wizard, ensure the shortcut exe path is set to the Q: or adapt the VFS path as necessary and launch the MMC to test functionality at this phase.
12. Finish the sequence and save it. 
13. Modify the OSD to include the following dependency:

———————–code snippet——————————————
<DEPENDENCY>
<SCRIPT TIMING="POST" EVENT="STREAM" PROTECT="TRUE" WAIT="TRUE" TIMEOUT="0">
<SCRIPTBODY LANGUAGE="Batch">
echo off \n
copy /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Manifests %windir%\WinSxS\Manifests \n
xcopy /S /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Policies %windir%\WinSxS\Policies \n
</SCRIPTBODY>
</SCRIPT>
</DEPENDENCY>

———————–code snippet——————————————

14. Publish your APP-V sequenced SCCM console  and test the functionality on your App-V Client.

Hope it Helps ,

Kenny Buntinx

SCCM Hotfix available: KB977203 – User state migration fails on a SCCM 2007 SP1 or SP2 client after you install security update 974571

7:30 pm in Uncategorized by Kenny Buntinx [MVP]

The actually workaround before this hotfix came out, was is to uninstall the 974571 hotfix on computers before running USMT task sequence. This workaround works fine but was not sufficient for many customers (The opposite would have been funny ).

Consider the following scenario:

  • You install the System Center Configuration Manager 2007 Service Pack 1 (SP1) client or the System Center Configuration Manager 2007 Service Pack 2 (SP2) client.
  • You install security update 974571 on this computer.
  • A SCCM task sequence runs on this client. This task sequence includes the Capture User State task sequence step and the Restore User State task sequence step.

In this scenario, user state migration fails. At the same time, the following error message is logged in the Ccmexec.log file:

Failed to import the client certificate store (0x80092024) OSDSMPClient

For all the details including a download link to the hotfix see the following new Knowledge Base article:

KB977203 – User state migration fails on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client after you install security update 974571

 

Hope it Helps ,

Kenny Buntinx

SCCM : Deploying Windows 7 on a VMware ESX environment ( howto )

3:13 pm in ConfigMgr, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, Drivers, Installation, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, script, Vmware, Windows 7 by Kenny Buntinx [MVP]

Hi ,

Did you ever wanted to build a reference image of your physical workstations onto your VMware ESX environment ( yes , some customers have a firm grip on vmware …) so that people could play around ?

In my previous post , I explained already on how to perform this for Vmware workstation and the process isn’t that much different. see

http://scug.be/blogs/sccm/archive/2009/04/20/sccm2007-osd-customising-your-task-sequence-for-building-a-client-os-on-your-vmware-workstation-6-0-or-later.aspx

Well , I have a lot of customers demanding for this scenario as well and here is how you get started :

Prerequisite: Make sure that you have at least ESX 3.5 update 5 !

Step 1 : Download the drivers of the “Intel PRO Network adapter” from the Intel site ( www.intel.com)

Step 2 : Copy the drivers to a folder from the extracted VMware tools on your SCCM Primary server & import those drivers into the driver database . Make sure to assign a category to it .It could be perfectly VMware like in the example below.

 image

Step 3 : When done , alter your Windows 7 deployment task sequence and add a “auto apply driver step”

Step 4 : Limit the driver scope to the Vmware category earlier defined as shown below.When done , click OK.

image

Step 5 : Make sure that your settings in your VMware are representing the following settings.

For Windows 7 32 bit :

TRUVO-0020

For Windows 7 64 bit :

TRUVO-0021

Step 6 : Once done , you boot your machine in PXE and start staging . That’s it . However do not forget to add your VMWARE Tools into your tasksequence .

TRUVO-0019

Hope it Helps ,

Kenny Buntinx

SCCM : Windows 7 deployments & unattended.xml

10:32 am in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

How can I customize my Windows 7 deployment , such as the regional settings, Firewall , internet explorer , keyboard settings? Even if you are using SCCM & task sequences you still want to customize your windows 7 image thru a unattend.xml file .

As I had trouble to find some examples to start with , I will post mine for Windows 7 x86 and x64 .

Now you can add or customise many more changes to your Unattend.xml file and use them to apply changes to Windows 7 during your task sequence installation. Of course SCCM will modify the Unattend.xml file to add the values you have specified during the task sequence such as your product key , user & company name , local admin pasword , etc .

Here you will see my custom Unattend.xml file for x86 :

-*-*-*-*-*-*-CODE SNIPPET-*-*-*-*-*-*-

<?xml version="1.0" encoding="utf-8"?>
<!–
    Unattended installation file for Windows 7 x86. Place in the root directory of a USB drive.
    Important! Before using, change the Product Key and Administrator’s password.
    Make sure the partition number and physical disk number are correct for your system.
–>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <EnableLUA>false</EnableLUA>
           </component>
           <component name="Networking-MPSSVC-Svc" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
           </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OEMInformation>
                <HelpCustomized>false</HelpCustomized>
            </OEMInformation>
            <RegisteredOwner></RegisteredOwner>
        </component>
        <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <fDenyTSConnections>false</fDenyTSConnections>
        </component>
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DisableAccelerators>true</DisableAccelerators>
            <DisableOOBAccelerators>true</DisableOOBAccelerators>
            <SuggestedSitesEnabled>false</SuggestedSitesEnabled>
            <Home_Page>about:home</Home_Page>
            <QuickLinkList>
                <QuickLinkItem wcm:action="add">
                    <QuickLinkName>Bing</QuickLinkName>
                    <QuickLinkUrl>http://www.bing.com</QuickLinkUrl>
                    <QLID>1</QLID>
                </QuickLinkItem>
                </QuickLinkList>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>2</ProtectYourPC>
                <HideEULAPage>true</HideEULAPage>
                <SkipMachineOOBE>true</SkipMachineOOBE>
                   <SkipUserOOBE>true</SkipUserOOBE>
            </OOBE>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>%OSDInputLocale%</InputLocale>
            <SystemLocale>%OSDSystemLocale%</SystemLocale>
            <UILanguage>%OSDUILanguage%</UILanguage>
            <UserLocale>%OSDUserLocale%</UserLocale>
    </component>
    </settings>
</unattend>

-*-*-*-*-*-*-CODE SNIPPET-*-*-*-*-*-*-

Here you will see my custom Unattend.xml file for x64 :

-*-*-*-*-*-*-CODE SNIPPET-*-*-*-*-*-*-

<?xml version="1.0" encoding="utf-8"?>
<!–
    Unattended installation file for Windows 7 x64. Place in the root directory of a USB drive.
    Important! Before using, change the Product Key and Administrator’s password.
    Make sure the partition number and physical disk number are correct for your system.
–>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <EnableLUA>false</EnableLUA>
           </component>
           <component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
           </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OEMInformation>
                <HelpCustomized>false</HelpCustomized>
            </OEMInformation>
            <RegisteredOwner></RegisteredOwner>
        </component>
        <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <fDenyTSConnections>false</fDenyTSConnections>
        </component>
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DisableAccelerators>true</DisableAccelerators>
            <DisableOOBAccelerators>true</DisableOOBAccelerators>
            <SuggestedSitesEnabled>false</SuggestedSitesEnabled>
            <Home_Page>about:home</Home_Page>
            <QuickLinkList>
                <QuickLinkItem wcm:action="add">
                    <QuickLinkName>Bing</QuickLinkName>
                    <QuickLinkUrl>http://www.bing.com</QuickLinkUrl>
                    <QLID>1</QLID>
                </QuickLinkItem>
                </QuickLinkList>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>2</ProtectYourPC>
                <HideEULAPage>true</HideEULAPage>
                <SkipMachineOOBE>true</SkipMachineOOBE>
                   <SkipUserOOBE>true</SkipUserOOBE>
            </OOBE>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>%OSDInputLocale%</InputLocale>
            <SystemLocale>%OSDSystemLocale%</SystemLocale>
            <UILanguage>%OSDUILanguage%</UILanguage>
            <UserLocale>%OSDUserLocale%</UserLocale>
    </component>
    </settings>
</unattend>

-*-*-*-*-*-*-CODE SNIPPET-*-*-*-*-*-*-

You can add your unattended.xml files now into a package and use them in your SCCM task sequence as shown below .

image

In order to use the unattended.xml that where containing the variables for the regional , keyboard , etc settings as shown below we need to assign some variables to our collection first.

image

On your collection , you add collection variables as shown in the picture below. This gives you the flexibility to create multiple collections with different keyboard layouts , if you for example are a international company.

image

 

Hope it Helps ,

 

Kenny Buntinx