You are browsing the archive for Installation.

Configmgr2007 : Change your packages source path after SCCM site migration with a script

6:39 am in AdminUi, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, SMS, Sms 2003 by Kenny Buntinx [MVP]

A few days ago , I explained in this blogpost “http://scug.be/blogs/sccm/archive/2010/08/10/configmgr-connecting-primary-child-sites-to-central-primary-parent-site-in-and-out-of-same-domain.aspx“ on how I was busy migrating one SCCM 2007 Primary site to another , because we wanted to start with a complete new environment (w2k8 x64) .As there is no supported direct upgrade path, I built an entire new SCCM server with SP2 -R2.I made it a child site of the existing SCCM primary site and let all the packages replicate.

After I solved a problem with locked padlocks on my packages in this blogpost :”http://scug.be/blogs/sccm/archive/2010/08/11/configmgr-locked-packages-after-sccm-site-migration-and-how-to-solve-it.aspx”, I needed to make sure that I would change all my old packages source paths ( a.e \\SCCM01\G$\src\<package folder> into my new package source paths (a.e \\Fileserver1\SCCMSRC\<package folder> that was residing on a DFS share .

To do that I needed a script , as doing +- 100 packages was a little to much work for a lazy admin :-)

I thought I had a great script from the site of Brian S. Tucker , as I used it already multiple times. It turned out that it was useless in this project as I needed to change not only the server name , but the complete path.

Script 1 : If you only need to change the server name in the package source path. Otherwise use my script “script 2” in the section under “script 1” below .

Copy code below this line—————————————————

Dim oWbemServices
If UCase(Right(Wscript.FullName, 11)) = "WSCRIPT.EXE" Then
    Wscript.Echo "This script must be run under CScript."
    Wscript.Quit
End If
If WScript.Arguments.Count <> 1 Then
    WScript.Echo "Wrong number of arguments were passed."
    WScript.Quit
End If
CONNSCCM()

For Each oPackage In oWbemServices.execquery("select * from sms_package")
  sOldPathString = oPackage.pkgsourcepath
  If InStr(sOldPathString,"\\") Then
                iStart = InStr(3,sOldPathString,"\")
                sNewPathString = Right(sOldPathString,(LEN(sOldPathString)-iStart))
                sNewPathString = "\\" & WScript.Arguments(0) & "\" & sNewPathString
                WScript.Echo "Setting Package Path for " & oPackage.Name & " from " & sOldPathString & " to " &  sNewPathString
                oPackage.pkgsourcepath = sNewPathString
                oPackage.put_
  End If
Next

WScript.Echo "Done"

Sub CONNSCCM()
  Set oWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set oWbemServices = oWbemLocator.ConnectServer(".", "root\sms")
  Set oSCCMProvLoc = oWbemServices.InstancesOf("SMS_ProviderLocation")

  For Each oLoc In oSCCMProvLoc
        If oLoc.ProviderForLocalSite = True Then
            Set oWbemServices = oWbemLocator.ConnectServer(oLoc.Machine, "root\sms\site_" + oLoc.SiteCode)
        End If
  Next
End Sub

Copy code above this line—————————————————

Thanks to my fellow Belgium MVP ”Kim Oppalfens” , I was able to alter the above script to my needs and change the complete source path , except for the package source folder .

Script 2 : If you need to change the complete package source path , except the package folder name.

Copy code below this line—————————————————

on error resume next
Dim oWbemServices
Set fs = CreateObject ("Scripting.FileSystemObject")
Set logFile = fs.CreateTextFile ("pkg_log.csv")
CONNSCCM()

For Each oPackage In oWbemServices.execquery("select * from sms_package")
  sOldPathString = oPackage.pkgsourcepath
  If InStr(sOldPathString,"\\") Then 
  arrsrcPath = Split( soldPathString, "\")
  snewpathString = "\\Fileserver1\sccmsrc\" & arrsrcPath(Ubound(ArrSrcPath)-0)

                logFile.Write "Setting Package Path for " & oPackage.Name & " from " & sOldPathString & " to " &  sNewPathString
                logFile.WriteLine ""
                oPackage.pkgsourcepath = sNewPathString
                oPackage.put_
  End If
Next

WScript.Echo "Done"

Sub CONNSCCM()
  Set oWbemLocator = CreateObject("WbemScripting.SWbemLocator")
  Set oWbemServices = oWbemLocator.ConnectServer(".", "root\sms")
  Set oSCCMProvLoc = oWbemServices.InstancesOf("SMS_ProviderLocation")

  For Each oLoc In oSCCMProvLoc
        If oLoc.ProviderForLocalSite = True Then
            Set oWbemServices = oWbemLocator.ConnectServer(oLoc.Machine, "root\sms\site_" + oLoc.SiteCode)
        End If
  Next
End Sub

 

Copy code above this line—————————————————

 

Hope it helps ,

 

Kenny Buntinx

Configmgr : Connecting Primary Child Sites To Central Primary parent site in and out of same domain

1:45 pm in Asset intelligence, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script by Kenny Buntinx [MVP]

Today I was at a customer doing a migration from a Configmgr 2007 with site code APL to a new Configmgr 2007 site with site code ICT. I couldn’t get my new Configmgr site with Site code ICT attached to the central primary. The button for “ set parent site “ was grayed out. I hereby give you my checklist I followed to discover the error . I was stuck for an hour before I realized what was going on .

 

So here are my tips for troubleshooting it :

 

  1. Install your new SCCM 2007 SP(X) as a new primary server to match what you currently have as a SMS 2007 SP(X) Central Primary. Service Pack levels are important and must be thesame !! Releases however could be different ( one could have R2 and the other can be without R2 ).
  2. Add the Server$ account name to the local admin group on each server and give the new server permission as required on the System container in AD.
  3. Make sure that your AD schema is extended.
  4. Check the following settings are enabled (from Advanced tab in site properties) :
  5. · Publish this site in Active Directory Domain Services

    · Require secure key exchange between sites

  6. If these sites are NOT configured with these options ,then you should manually exchange the public keys :
  7. To manually transfer the child site public key to the parent site

    1. While logged on to the child site, open a command prompt and navigate to the location of Preinst.exe.

    2. Run the following command to export the child site’s public key: Preinst /keyforparent

    3. The Preinst /keyforparent command places the public key of the child site in the <site code>.CT4 file located at the root of the system drive.

    4. Move the <site code>.CT4 file to the parent site’s <install directory>\inboxes\hman.box directory.

    To manually transfer the parent site public key to the child site

    1. While logged on to the parent site, open a command prompt and navigate to the location of Preinst.exe.

    2. Run the following command to export the parent site’s public key: Preinst /keyforchild.

    3. The Preinst /keyforchild command places the public key of the parent site in the <site code>.CT5 file located at the root of the system drive.

    4. Move the <site code>.CT5 file to the <install directory>\inboxes\hman.box directory on the child site

  8. On the primary site server, Add the central site server computer account to the local Site to Site connection group Ex. SMS_SiteToSiteConnection_ICT. Then on the central site server, Add the primary site server computer account to the local Site to Site connection group Ex. SMS_SiteToSiteConnection_APL.
  9. And last but not least : If that button “ set parent site “ ïs grayed out , Make sure that there isn’t any Asset intelligence synch point installed on you Primary Child site installed . I was way to quick and was reading over it , as I was thinking that something else was wrong . Dumb Dumb .

 

After removing the AIS point in my hierarchy , the button finally came available .

 

Hope it Helps ,

 

Kenny Buntinx

SCCM 2007 R3 Beta (refresh) Installation (Howto)

6:45 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, R3, Reporting, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, SQL Reporting services, SRS by Kenny Buntinx [MVP]

I have recently deployed Configuration Manager 2007 R3 beta (refresh) in production at my TAP customer. Below I will outline the steps for deploying Configuration Manager 2007 R3 beta.

Disclaimer: You are not allowed to install any beta products in your production environment!!! This is only allowed for selected TAP Customers !!! Always install beta products in lab environments !!!

This blog post highlights R3 the beta upgrade preparation on your SCCM 2007 SP2 environment . You need SP2 in order to be allowed the installation of R3, so if you did not upgraded your environment , this is the first step !

We talk further about the actual server upgrade and validation tasks.

 

1. Prerequisites :

SCCM 2007 SP2 only environment

Below a table with the site roles where this R3 upgrade is applicable if you have SCCM 2007 SP2 installed :

Role

Needed Installs Comments Specific Comments
Site Server (Central Site) Hotfix KB977384 & R3 Installation Always install This site needs to be upgraded first.
Site Server (Primary Site) Hotfix KB977384 & R3 Installation Always install These sites needs to be upgraded secondly.
Site Server (Secondary Site) Hotfix KB977384 & R3 Installation * Always Install These sites needs to be upgraded after the primary sites because you will need certain included R2 features.
Admin Console R3 Installation to make sure that all functionality is present
DP, SUP, SQL DB Server (if remote) Not applicable none
 

SCCM 2007 SP2 R2 environment

Below a table with the site roles where this R3 upgrade is applicable if you have SCCM 2007 R2 already installed :

Role Needed Installs Comments Specific Comments
Site Server (Central Site) Hotfix KB977384 & R3 Installation none This site needs to be upgraded first.
Site Server (Primary Site) Hotfix KB977384 & R3 Installation none These sites needs to be upgraded secondly.
Site Server (Secondary Site) Hotfix KB977384 & R3 Installation * Hotfix must always be installed ! Look below for additional information if you really need to install R3 on your secondary’s
Admin Console R3 Installation to make sure that all functionality is present
DP, SUP, SQL DB Server (if remote) Not applicable none

* Site Server (Secondary Site) :

If you have SCCM 2007 R2 installed on your secondary sites and then :

1. You don’t need to install R3 on secondary sites if you do not use any "Proxy MP" or "AD discovery" feature at your secondary sites if you only use the "Power Mgmt" feature through your organization & run "AD discovery" on your Central or Primary sites.
2. You do need R3 on your secondary sites if you do use the "Proxy MP" functionality or "AD discovery" at your secondary sites.

If you are planning to use these features in secondary sites you need to install R3. Since most customers do use proxy MP role on secondary ,you need to install R3 there as well.

2. Pre-Flight Checks for R3 Beta (refresh) Upgrade

  • Take a  ConfigMgr Site Backup and verify that it is successful.
  • Make sure that ConfigMgr 2007 SP2 is installed correctly and that all site server components are healthy

 

3. Configuration Manager 2007 R3 Beta (refresh) Server Upgrade

 

  • Install the server side hotfix (KB977384) (included in the dowload of the R3 media) .This hotfix, which comes with the R3 of SCCM 2007, is a prerequisite for SCCM 2007 R3. During the installation it also creates a SCCM Package/Program containing a MSP file allowing to update SCCM Advanced Clients Components. This client hotfix package has to be deployed to all ConfigMgr 2007 SP2 clients before power policies can be managed.

image

Click “Next”to continue.

TRUVO-0083

Click “I accept …”to continue and select “Next”to continue.

image

Hit the Ïnstall” button.

TRUVO-0085

The Hotfix starts to install.

image

It will prompt you to create a Package & Program for later deployment to your Configmgr 2007 SP2 clients.

image

During the installation process, when prompted to create a software distribution package for client hotfix deployment, Provide a name for the ConfigMgr package & Program. However your package & program needs to be done thru conformity of your production naming convention & deployment standards. This client hotfix package has to be deployed to all ConfigMgr SP2 clients in the environment before their power policies can be managed

image

Specify the package source & click “Next” to continue.

image

Click “Next” to continue.

image

Click “Finish” to exit.

  • During the hotfix KB977384 installation, the source bits for the client hotfix package will be copied into the client\i386\hotfix\KB977384Beta folder. Look if the bits exists in that folder.

image

  • After successful installation of hotfix KB977384 pre-requisites, execute R3 beta (refresh) installation from the installation source location using SPLASH.HTA. Follow the screenshots below to complete the installation.

image

Click “Next” to continue.

image

Accept the license agreement and Click “Next” to continue.

image

Click “Next” to continue.

image

Click “Next” to continue.

image

image

Click “Finish” to exit.

 

4. Post Configuration Manager 2007 R3 Beta (refresh) Server tasks

  • Open SCCM Console & navigate to Site Database – Site Management – <Site Code> – <Site Name> and view properties to confirm that R3 Installed is “Yes” as shown below

image

  • Verify that the SMS_Def.mof has been appended with R3 specific WMI classes, without any changes to the pre-existing class definitions.

image

image

  • Go to the ConfigMgr Console, navigate to [Site Database] – [Site Management] – [Your site code] – [Your site name] – [Site Settings] – [Client Agents].You will see a new item called “Power Management Client Agent”. Go to the “Power Management Client Agent” properties and check the box “Enable Power Management on Clients”.

image 

  • Install SCCM Reporting Services Point. Power Management in SCCM 2007 R3 contains a number of reports to help you to analyze power consumption and computer power settings in your organization. These Reports require SQL Reporting Services which was introduced in SCCM 2007 R2.If you never worked or used SRS reporting , get used to it , because it will be the only reporting functionality left in Configmgr V.next.

Note : I am not going to explain how to set-up SRS reporting . You can find guidance on Technet or the online help .

image 

Copy SCCM Reports to Reporting Services. Power Management in SCCM 2007 R3 gives you 17 new reports.

image

Click “Next” to Continue.

image

Fill in your credentials and Click “Next” to Continue.

image

Select “Import Report Definition Language Files From Microsoft Signed Cabinet File”.

image

Browse to the "%SCCM installation folder%\Reports\Power Management" folder and select the MicrosoftReportPack.cab file. Click "Open” to Continue.

image

Look if all reports are selected and Click “Next” to Continue.

image

Click “Next” to Continue.

image

Look at the status and see that all reports are imported successfully. Click “Next” to Continue.

image

Look in the SCCM console if the reports exists.You can run all Reports from the SCCM Console now.

 

5. Deploy the MSP file contained into the SCCM Package created by installing the hotfix onto you SCCM 2007 SP2 Clients

After the R3 installation is completed on the site server, the next step is to deploy R3 hotfix to all SP2 clients to use all R3 features.Look for the Client hotfix package & program that where created during installation and must be available under ‘Software Distribution’ and then look for the Packages Node.

  • Validate your Package & Program Properties

TRUVO-0092

  • Deploy your package to all your Distribution points, before deploying the package to all clients.

TRUVO-0093

  • Create your deployment collection(s).Deployments should be done in multiple phases.Start with a Test/Pilot group and the second wave should be per site/region.You could use “Link to Collection” for avoiding creating to much collections.

TRUVO-0094

  • Creation your Advertisements.There are no special requirements in creating advertisements for this deployment.

TRUVO-0095

 

Hope it Helps ,

 

Kenny Buntinx

SCCM : Software Updates are hanging.

7:34 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, Installation, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, Software updates, wsus by Kenny Buntinx [MVP]

Issue :

A XP client keeps failing on 2 updates that are marked as missing , but no errors could be found in the SCCM client logs , neither in the Windows Update Agent.log. You only get this line in the log file :

Update (Site_308CBE75-86C9-4D9D-AC4E-410079CCF8A2/SUM_5bf6aa01-2591-4966-95a6-afa7b5b6ac68) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040656

Solution :

The solution is explained in KB artible : http://support.microsoft.com/kb/956702

Method for Windows 2000, Windows XP, or Windows Server 2003

To resolve this issue, register the Softpub.dll, Wintrust.dll, Initpki.dll, and Mssip32.dll files. To register these files, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type regsvr32 Softpub.dll /s, and then press ENTER.

3. At the command prompt, type regsvr32 Wintrust.dll /s, and then press ENTER.

4. At the command prompt, type regsvr32 Initpki.dll /s, and then press ENTER.

5. At the command prompt, type regsvr32 Mssip32.dll /s, and then press ENTER.

 

After you re-register the above dll’s , you perform a software update scan.From than the updates will install normally.

 

Hope it helps ,

Kenny Buntinx

SCCM OSD Deployment : The IIS Admin service is not starting anymore on a deployed sysprepped Windows Embedded 2009 with IIS 6.0 installed

12:44 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, IIS, Installation, Known Issue, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, script, WES, WES 2009, WES2009, XPe by Kenny Buntinx [MVP]

Lately I have been busy with testing & deploying for a big project some Windows Embedded 2009 devices , called the Advantech ARK –1388 .One requirement from the customer was to have IIS 6.0 installed.We decided to include the IIS 6.0 component into the WES 2009 image with Target builder  ( witch is a tool for building the WES image ), but every time we deployed an image after it had been sysprepped with SCCM, the IIS Admin service would fail to start .

Because this needed to be deployed onto three thousand (3000) WES devices , we contacted Microsoft PSS support for some help. Below you will find our findings and workaround for the issue .

Our problem :

We installed a Windows Embedded 2009 image with IIS 6.0 on a Advantech ARK-1388 and it is running fine.The OS is prepared for system cloning using the sysprep.exe tool ( supported since WES 2009 ).

When we reapplied the master image  with SCCM R2 SP2 and mini-setup was completed, the OS seems to run fine, however the "IIS Admin" service does not start and returns the following error:
"Windows could not start the IIS Admin on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2146893818."

There are no related errors in the Event Logs. IIS cannot be repair-installed using the Add/Remove Programs component of the Control panel.( this was done to see if we could automate a self –repair )

We would like to deploy the WES image using the OSD feature of SCCM 2007 R2 ,but the problem also occurs when customer calls sysprep.exe manually without the usage of SCCM. ( that’s what we thought , SCCM always works great !! :-) )

 

Our environment :

We have a Windows Embedded 2009 image with IIS 6.0
We have a SCCM 2007 R2 SP2 environment

 

The summary of our troubleshooting :

1. Microsoft CSS discussed with the WES and SCCM teams if WES2009 is supported on SCCM 2007 R2. After a discussion they have modified there statement on the web , see http://blogs.technet.com/configmgrteam/archive/2010/01/25/things-you-need-to-know-when-using-windows-embedded-standard-2009.aspx

2. the proposed workarounds from Microsoft (re-installing MSDTC and IIS) from the " WES Resource Kit" didn’t solve the problem.

3. We checked the FBWF status on the sysprepped image. It was still disabled as it should .

4. Microsoft spoke with the IIS team about the issue. Discussion results:
  a) It’s a known problem that IIS doesn’t work after sysprepping the image because of the changes made by sysprep.
  b) Using sysprep on XP Pro is not supported, see KB326779 "Supported IIS configurations for use with Sysprep"
  c) The only supported solution is to install IIS after the sysprep phase. On XP Pro PCs you can run an unattended IIS installation
     using the Sysocmgr command (which can add or remove Windows Components). E.g. as described in
     KB309506 "How To Perform an Unattended Installation of IIS 6.0"
     Here is the catch !! : Unfortunately Sysocmgr.exe is not shipped with the XPe database ===> meaning that it is impossible to install IIS 6.0 after we have deployed our WES 2009 client !

5. As discussed with Microsoft and the IIS team I tried to "repair" the IIS Admin service after the final sysprep boot by using SysOCmgr.We have copied the missing sysocmgr.exe from an XP Pro SP3 PC and I’ve had to insert an XP Pro SP3 CD into the CD drive for the missing files.We don’t believe this workaround can be used by my customer (legal and technical issues).

6. For a test we have used fbreseal instead of sysprep. The IIS Admin service was running after fbreseal.But as I know deployment via SCCM 2007 OSD requires the usage of sysprep and fbreseal cannot be used in this scenario.

 

Our Solution :

Together with the WES product team & Microsoft PSS support we found an easy workaround to get the "IIS Admin" service running again on the sysprepped WES 2009 image.
The workaround switched off the IIS components in the registry and called the FBAOC.exe tool to re-install IIS.It solved the problem on our test devices.

Here’re the details about this workaround:

1. It doesn’t need the XP Pro SP3 CD.
2. It doesn’t need any file from an XP Pro SP3 PC (like sysocmgr.exe).
3. It doesn’t need to collect any IIS files into a special installation location.

The workaround is just:

1. Uses your original SLX file and WES 2009 image which uses the FBOCMgr phase 5550 for the IIS components.
   It means you can run the workaround on your original sysprep-ed images.
2. Changes some IIS registry settings used by the OS to install IIS.
3. Uses a WES-specific command (FBAOC.exe) which is part of your original SLX file and image.
4. Step 2-3 can be executed by the attached files:

  a) MyIIS-Off.reg      for changing the registry

*********************************CODE BEGIN**********************************

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents]
"iis_common"=dword:00000000
"iis_inetmgr"=dword:00000000
"iis_www"=dword:00000000
"iis_www_vdir_scripts"=dword:00000000
"iis_www_vdir_printers"=dword:00000000
"iis_doc"=dword:00000000
"iis_ftp"=dword:00000000

*********************************CODE ENDS**********************************


  b) MyIISinstall.bat   runs the workaround (by using MyIIS-Off.reg)

*********************************CODE BEGIN**********************************

@echo off

echo Changing registry settings…
regedt32 /s \MyIIS-Off.reg

echo Enabling IIS features…
\windows\FBA\FBAoc.exe

echo Done.

*********************************CODE ENDS**********************************

Pls. put the files in the C:\ root folder on your sysprep-ed WES 2009 image and call the MyIISinstall.bat file from a command line.

When running properly the batch file will run for 1-2 minutes and it’ll display 3 output lines:
        Changing registry settings…
        Enabling IIS features…
        Done.

Afterwards the "IIS Admin" service should be running.

So this scenario is not supported on XP Pro. But this workaround is supported.
This is a known problem/limitation on XP Pro. The same problem occurs on WES installations because WES uses exact the same XP Pro binaries.

 

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 : 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

Installing the Service Manager WebPortal

6:38 pm in beta, Installation, SCSM, System Center Service Manager by Kenny Buntinx [MVP]

Hi All,

 

System center service manager beta 2 comes with a webportal to allow for:

  • It to end-user announcements (Send out infrastructure status updates: Eg: Mail functionality temporarily unavailable)
  • Self service end-user password (not implemented in this beta2, will require ilm v3)
  • End-user request for help allows a user to log an incident
  • End-user request software

Below are the steps to get the portal installed:

The portal is based on IIS, so you’ll first have to install IIS.

The webportal needs a default IIS setup, with the following 2 role services added.

  • Asp.Net (and all additional dependant features)
  • Windows authentication
  • IIS 6.0 Metabase compatibility

 

Once you have installed these prerequisites you can start the webportal installation.

First extract the smcdimage_Architecture  and subsequently launch setup.exe.

The window that opens allows you to start the webportal installation.

 

Step 1:

step01

Step 2:

step02

Step 3:

step03

Step 4:

step04

Step 5:

step05

Step 6:

step06

Step 7:

step07

Step 8:

step08

Step 9:

step09

 

That’s it in regards to the installation of the portal, for end-users to be able to use the portal they need to have the ActiveX Webportal client installed.

You can find the ActiveX component in the setup folder of the Cd Image for the architecture of the client systems, the file is called portalclient.msi.

Once all this is done, the only additional step you need is to request a certificate for your System center service manager(SCSM) webportal, but that is food for a next blog post.

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