You are browsing the archive for sccm2007.

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 4.

11:20 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Installation, migration, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, SQL by Kenny Buntinx [MVP]

Today , I will continue explaining my little migration project to migrate away from a standalone Softgrid 4.1 infrastructure towards a fully integrated SCCM2007 SP R2 App-V 4.6 infrastructure . You can read my previous posts right here :

 

Below I will discuss the migration scenario once more in a few bullet points to migrate away from the Softgrid 4.1 standalone environment :

1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2) DONE in Part 1.

2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications. DONE in Part 1.

3. Import all packages into ConfigMgr 2007 SP2 R2 DONE in Part 1.

4. Create all necessary collections and create a dynamic membership query with a AD group name. Partially explained in Part 2 , DONE in Part 3.

5. Create all the necessary advertisements.

6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

So that will leave us to creating all the necessary advertisments (remember 400 Pieces) between the virtual Packages and the necessary collections.

As explained in Part 3, we have created a CSV file with all the necessary information as APP-V package Name , ResourceID & Collection Names. Now we need to add the PackageID , Advertisement Name and CollectionID to the CSV file  ( you can extract that kind of information out of your SQL DB (dbo.v_Package & dbo.v_collections)

image

Figure 1: The modified CSV file added with PackageID, Advertisement Name, CollectionID

Once the CSV file is filled up with the necessary data , we can start working on the script to create those advertisements based on that Csv file , as we need the PackageID , CollectionID and Advertisment Name tables to make it work .

Below I will post the VBS code to read out the csv file and create all advertisements :


 

Stay tuned for Part 5 very soon talking about the actual switch over from Softgrid standalone to Configmgr 2007 R2 SP2. ….

 

Hope it Helps ,

Kenny Buntinx

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 3.

10:41 am in App-V, AppV, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, migration, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, Softgrid by Kenny Buntinx [MVP]

Today , I will continue explaining my little migration project to migrate away from a standalone Softgrid 4.1 infrastrucure towards a fully integrated SCCM2007 SP R2 App-V 4.6 infrastructure . You can read my previous posts right here :

 

Below I will discuss the migration scenario once more in a few bullet points to migrate away from the Softgrid 4.1 standalone environment :

1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2) DONE in Part 1

2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications. DONE in Part 1

3. Import all packages into ConfigMgr 2007 SP2 R2 DONE in Part 1

4. Create all necessary collections and create a dynamic membership query with a AD group name. Partially explained in Part 2 , continued in this section.

5. Create all the necessary advertisements.

6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

So that will leave us to creating all the necessary collections (remember 400 Pieces) and their lovely 400 AD Group Memberships as this was how the Softgrid environment worked (User Group Based) before.

As explained in Part 2, I tried to figure out a way to translate those GUID values into human readable format. It must be possible to read out the AD values with ADSIedit , but as I am not the biggest expert in scripting , it would cost me too much time and so I did it manually (monkey work).

To accomplish Part 3, you will need to pull out of SQL a *.csv file with all your Security group names and resource id’s as shown below .

clip_image001

Figure 1: This is how SCCM stores their security group information in the SQL db ( ResourceID/SecurityGroup)

Then merge the security group information from Softgrid into the excel. When done you should get something like shown below:

 

clip_image003

Figure 2: CSV file with all the necessary information as APP-V package Name , ResourceID & Collection Name

Now we start working on the script to create those collections based on the Csv file , as we need the ResourceID to and CollectionName tables to make it work .

Below I will post the VBS code to read out the csv file and create all collections with all the Security Groups as direct member :

 


 

Stay tuned for Part 4 very soon ….

 

Hope it Helps ,

Kenny Buntinx

ConfigMgr 2007 : PXE Cache Behavior

9:02 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, OSD, PXE, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007 by Kenny Buntinx [MVP]

Config Mgr OS deployments when using PXE boot , you’ve probably had machines that did not want to boot the task sequence as it stated “No task sequence found, booting onto the hard drive”.

This is most likely due to a previous task sequence being advertised to that machine. By default ConfigMgr will cache the PXE advertisement for 60 minutes (Default setting) and then it will expire. Most of the time you can speed up things when restarting the WDS services. Restarting the WDS services ( clearing the cache) isn’t the best solution. In ConfigMgr SP2 the cache expiry can be set in the registry.

  • On an x86 machine the located under:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXE
  • On an x64 machine the registry key is under:
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\SMS\PXE

Create a new DWORD value CacheExpire, and set the desired value in seconds. For example, if you prefer the cache expired in 2 minutes, set the value to 120. If the value is set to 0, then the default 60 minutes value is used.

Note: Setting the value in CacheExpire is only supported in ConfigMgr 2007 SP2.

Be careful if you have R2 installed and unknown computer support enabled because if you set the cache expire value too low and you are using a mandatory task sequence your machine will continuously start the same task sequence every time it reboots.

 

Hope it Helps ,

Kenny Buntinx

SCCM OSD issue with Win7 x86x64 bit deployment : Error 31

10:12 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr Dashboards, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Error 31, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, Windows 7 by Kenny Buntinx [MVP]

Hi,

I was deploying a windows 7 32/64 bit, at a customer but during the step “setup windows and Configmgr” it fails with the following error :

Windows setup failed, code 31

Failed to run the action: Setup Windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows)

Looking further in the SMSTS.log it looks like :

——SMSTSLog—–

Command line for extension .EXE is "%1" %*    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Set command line: "\\<yourSCCMServer>\SMSPKGE$\ABC00014\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Executing command line: "\\<yourSCCMServer>\SMSPKGE$\ABC00014\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Process completed with exit code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Windows Setup completed with exit code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Entering ReleaseSource() for \\<yourSCCMServer>\SMSPKGE$\ABC00014\    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
reference count 1 for the source \\<yourSCCMServer>\SMSPKGE$\ABC00014\ before releasing    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Released the resolved source \\<yourSCCMServer>\SMSPKGE$\ABC00014\    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Windows setup failed, code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Exiting with code 0x80004005    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Process completed with exit code 2147500037    TSManager    4/29/2010 7:45:34 PM    1384 (0x0568)

——SMSTSLog—–

This error (error 31) could have multiple causes in my environment as described into a previous blog post , see http://scug.be/blogs/sccm/archive/2010/10/28/sccm-osd-issue-with-win7-x64-bit-deployment-on-hp-8740w.aspx.

In my particular case , it worked before and now suddenly it didn’t anymore . The only thing I did , was changing my advertisment to another collection. Now that I know my root cause , lets investigate.

Oh , I am using variables in my unattended.xml file to define my different Keyboard settings as described in one of my previous blog posts ( http://scug.be/blogs/sccm/archive/2010/02/02/sccm-windows-7-deployments-amp-unattended-xml.aspx ) . Did I define them on my new collection ? … Damn , No I didn’t …

Solution : After some testing it became clear that the solution was the following “Define my Collection Variables as shown below !”

I

n 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.

It now works back like a charm .

Hope it Helps ,

Kenny Buntinx

SCCM R3 : Power Management In Practice (Lessons Learned)

6:56 am in ConfigMgr, ConfigMgr 2007, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Power Management, R3, sccm, SCCM 2007 R3, sccm2007, Windows 7 by Kenny Buntinx [MVP]

Hi there ,

I have recently deployed Configuration Manager 2007 RTM in production at my TAP customer. Those who attended yesterday my Presentation at the Belgian System Center Day “http://scug.be/blogs/sccm/archive/2010/09/30/announcement-system-center-day-in-belgium.aspx” have seen already the best practices & lessons learned .

I want to thank everyone that has attended our event as it was a great success. The presentations and the links to the recordings will be uploaded very soon , but for those who cannot wait , I’ll post a few teasers below :

 

  • Communication and User Preparation :

We created a communication plan that supported two main objectives:

Drive awareness : Client power management can reduce client computer power consumption, which in turn reduces both the carbon footprint and operational expenses.

Allow users adequate time to decline participation in the program, prior to enforcement:

–Established a four-week period between initial communications and the enforcement of the power management settings.

–Clear communication about the program, the extent of impact, and a link to a process to decline participation were critical to the success of the program. Even though the majority of users would perceive little or no impact, it was key that they reach the few that might.

  • Operational remarks :

 

    • You must Reboot the computer after installing the power mgmt. hotfix.
    • If you create your own Package/Program to install the hotfix, you must select: The program restarts the computer setting, even though the hotfix DOES NOT reboot the computer.
    • If you want to install the power mgmt hotfix during a task sequence for new computers, select “Continue on error”. Put it as the last step of the task sequence.
    • A computer requires an active keyboard/mouse, otherwise it might not go to sleep at all. Mostly this affects KVMs, but we had few examples where a computer is only used remotely (no KVM or a mouse/keyboard) & they don’t fall a sleep.
    • The basic principle: get rid of all your XP machines!
    • Windows XP machines could been switched on for too long. There are multiple processes that can block sleeping!
    • Use correct drivers. Especially display drivers. Fortunately (Vista and higher), R3 report nicely shows those problem machines.
    • It could be very difficult to pinpoint what is the culprit of machines that will not sleep. It could be a client/server app , a remoteApp (TS connection , Citrix , etc ). Regular rebooting helps the situation!
    • Change currency symbol in your reports from $ to €.
    • The following (non limited list) could cause sleeping issues on windows XP or other machines :
    • •Anti Virus scanner

      •Video Card Drivers

      •Report on “Standard VGA Graphics Adapter”

      •Report on “Video Controller”

      •Report on “Video Controller (VGA Compatible)”

      •Check at vendor if Video card supports S3/S4 principle (white brand desktop)

      •Capable hardware with power management features disabled in BIOS ( S3/S4 )

      •HW BIOS version ( Put them on the same level )

 

These lessons learned sections has been build up by sharing our own experiences at our TAP Customers. Thanks to Panu Saukko (MVP) for also sharing his experiences during his TAP assignment with me.

 

Hope it Helps ,

Kenny Buntinx

SCCM OSD issue with Win7 x64 bit deployment on HP 8740W

12:16 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Deployment, Drivers, Installation, Operating System Deployment, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, Windows 7 by Kenny Buntinx [MVP]

Hi,

I was deploying a windows 7 64 bit, at a customer on a HP 8740W , witch is a monster machine ( core I7 , Nvidia Quatro 512 mb graphics , etc ) but during the step “setup windows and Configmgr” it fails with the following error :

Windows setup failed, code 31

Failed to run the action: Setup Windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows)

Looking further in the SMSTS.log it looks like :

——SMSTSLog—–

Command line for extension .EXE is "%1" %*    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Set command line: "\\<yourSCCMServer>\SMSPKGE$\ABC00014\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Executing command line: "\\<yourSCCMServer>\SMSPKGE$\ABC00014\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot    OSDSetupWindows    4/29/2010 7:45:19 PM    1576 (0x0628)
Process completed with exit code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Windows Setup completed with exit code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Entering ReleaseSource() for \\<yourSCCMServer>\SMSPKGE$\ABC00014\    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
reference count 1 for the source \\<yourSCCMServer>\SMSPKGE$\ABC00014\ before releasing    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Released the resolved source \\<yourSCCMServer>\SMSPKGE$\ABC00014\    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Windows setup failed, code 31    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Exiting with code 0x80004005    OSDSetupWindows    4/29/2010 7:45:34 PM    1576 (0x0628)
Process completed with exit code 2147500037    TSManager    4/29/2010 7:45:34 PM    1384 (0x0568)

——SMSTSLog—–

 

This error (error 31) could have multiple causes in my environment. I will summarize them below :

  • As I was deploying from OEM Media  kit ( Yes , I know , companies should have a volume license key ) , it could cause some issues as on the OEM Media there is no such thing as a Pid.txt where the product key is stored . OEM media uses the unique key that has been sticked under your pc/ Laptop
  • A badly written Unattend.xml , but as that xml has been used at other customers as well and posted on my blog , it seems unlikely .
  • The Product key mentioned in the Task Sequence . Checked it , no product key mentioned .This error usual happens though because you are using an MAK key when you should not be using any key during the TS — you can use the KMS client key (this is different than the KMS Server key you get from the MVLS site), but this is not required as your KMS client key is embedded in the OS source files in a file called pid.txt mentioned earlier.
  • Faulty Drivers ….

 

I eliminated very soon 2 of the 4 options and was left over with :

  • As I was deploying from OEM Media  kit ( Yes , I know , companies should have a volume license key ) , it could cause some issues as on the OEM Media there is no such thing as a Pid.txt where the product key is stored . OEM media uses the unique key that has been sticked under your pc/ Laptop
  • Faulty Drivers ….

 

Next step I have disabled the step “Auto apply drivers” and magically the setup continued …. That’s funny  , so it has to be a driver….

Now that I know my root cause , lets investigate. The fun part is that Configmgr has the possibility to disable drivers on an easy way.

After some testing it became clear that the “IDT High Definition Audio Codec” was giving me error 31 because it has been written very crappy !

Solution :

  1. Remove the driver from the database
  2. Create a software Package and launch the setup via Setup.exe in your Task Sequence .

 

It now works like a charm .

 

Hope it Helps ,

Kenny Buntinx

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 2.

11:13 am in App-V, AppV, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, migration, R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, Softgrid, WMI by Kenny Buntinx [MVP]

Yesterday , I have started explaining my little migration project to migrate away from a standalone Softgrid 4.1 infrastrucure towards a fully integrated SCCM2007 SP R2 App-V 4.6 infrastructure . You can read my previous post right here : http://scug.be/blogs/sccm/archive/2010/10/18/softgrid-4-1-migration-towards-configmgr-with-app-v-4-6-integration-the-story-of-automation-part-1.aspx

Below I will discuss the migration scenario once more in a few bullet points to migrate away from the Softgrid 4.1 standalone environment :

  1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2)  DONE in Part 1
  2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications. DONE in Part 1
  3. Import all packages into ConfigMgr 2007 SP2 R2 DONE in Part 1
  4. Create all necessary collections and create a dynamic membership query with a AD group name.
  5. Create all the necessary advertisements.
  6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

So that will leave us to creating all the necessary collections ( remember 400 Pieces ) and their lovely 400 AD Group Memberships as this was how the Softgrid environment worked (User Group Based) before.

You could accomplish this in basically 2 ways , with a Direct or Dynamic collection membership. Both will have different pro’s  & cons and I will try to explain the difference below :

1. Creating a Dynamic collection membership based on the User Group Resource that will point to an AD Security Groups that contains users in AD for Collection Population.

Assuming there is a best case ( not best practice ! ) scenario where  it can take at least a maximum possible latency (In the case below) of = 3hrs 15 minutes

  • AD Replication to happen – 15 minutes.
  • AD Security Group Discovery – 60 minutes (this is a very short setting – default is a day). ( R3 could save you another 55 minutes here with Delta Discovery enabled )

          image

  • As this is a dynamic membership collection , it is bound to a Collection evaluation cycle – 60 minutes (this is a very short setting – default is a day).
  • Configuration Manager Client Policy Refresh – 60 minutes (Default).

2. Creating a Direct collection Membership based on the User Group Resource that will point to an AD Security Groups that contains users in AD for Collection Population.

Assuming there is a worst case scenario where  it can take at least a maximum possible latency (in the case below) of = 60 minutes

  • Configuration Manager Client Policy Refresh – 60 minutes (Default).
  • User may needs to log off and log-on again.

Option nr 1 is not an approach that I’m  in favor off  as it introduces a much higher latency then option nr 2. I can live with the fact that users may need to do a logon/Logoff to receive there applications. As we have decided to go for option nr2 , it is now time to create a script and to do the following :

  1. Create a collection based on the “Virtual app” name that is been extracted out of the manifest.xml found in the folder of the \\<Servername>\VirtualPackageSource\<Package Name> under a allready existing SUB – Collection
  2. When creating the collection , create a direct collection membership with the Application AD Security group Name . (based on the resourceID)

To accomplish step 2 , you will need as prerequisite to turn on AD Security group discovery in your site settings. When done, you could pull out of SQL a *.csv file with all your Security group names and resource id’s as shown below . Please save the file as you will need it in a later phase .

image

Figure 1: This is how SCCM stores their security group information in the SQL db ( ResourceID/SecurityGroup)

Now we start working on the script , as we need the ResourceID to make it work

Below I will post the VBS code to only create 1 collection and link 1 Security Group :


 

Now I need to figure out how to link the ResourceID’s & groups with my softgrid AppID’s & Security Groups ( as shown below )  . However this will not be an easy task as I need to convert a LDAP GUID to a readable security groupname , make the correlation between the previous exported ResourceID/Security group name  and the converted GUID SecurityGroupName/AppID .

image

Figure 2: This is how Softgrid stores their security group information in the SQL db ( AppID/SecurityGroup (GUID))

Stay tuned for Part 3 very soon ….

 

Hope it Helps ,

 

Kenny Buntinx

Softgrid 4.1 migration towards ConfigMgr with App-V 4.6 Integration : The story of automation , Part 1.

8:05 pm in App-V, AppV, ConfigMgr, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, Installation, migration, R3, sccm, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, sccm2007, script, SDK, Softgrid, Toolkit by Kenny Buntinx [MVP]

Today we have reached the second phase of migrating the existing Softgrid 4.1 stand-alone infrastructure towards the already upgraded and optimized System Center Configuration Manager 2007 SP2 R2 that we did in fase 1.

We all know that integrating a standalone Softgrid/App-V infrastructure towards a integrated Configmgr 2007 SP2 R2 – App-V implementation could only be done with a big bang. It is either On or Off. We also know that Softgrid sequenced app’s lower then version 4.5 can cause issues and more important , they are lacking the manifest.xml file that is necessary to create virtual packages in ConfigMgr 2007 SP2 R2.

 

image

 

Below I will discuss the migration scenario in a few bullet points to migrate away from the Softgrid 4.1 standalone environment “

  1. Deploy the new app-V 4.6 clients on all workstations and check for inconsistencies (luckily all packages where sequenced with 4.2)
  2. Pull all existing Softgrid 4.2 sequenced packages thru the new App-V 4.6 Sequencer to avoid any complications.
  3. Import all packages into ConfigMgr 2007 SP2 R2
  4. Create all necessary collections and create a dynamic membership query with a AD group name.
  5. Create all the necessary advertisements.
  6. Switch over from Softgrid standalone to Configmgr 2007 R2 SP2. (Think about network impact !)

 

Step 1 :

As the old Softgrid 4.1 stand-alone infrastructure has around 400 virtual packages , and they need to pass thru the app-V 4.6 sequencer to avoid any inconsistencies or complications , the last thing you want to do is play the monkey and open up all packages in the sequencer and save them manually … For this part I had very good teamplayers that are very skilled VBscript writers , again a big thank you to Ewald Lieuwes ( http://www.wchulseiee.net/) & Wouter Schrijvens …

Below I will post the VBS code written for :

 

  1. Going thru the list of virtual packages stored at E:\Softgrid\<Package Name>….
  2. Open them one by one in the App-V 4.6 sequencer and save then to a new location called F:\App-V\<Package Name> to have a backup!
  3. As you see in this script ,we use E:\, F:\ and U:\. The U:\ is the virtual drive partition (default this is Q:\)
  4. Make sure the virtual drive partition is big enough for all of your packages. In this case, this was limited to 2 GB ( standard as Softgrid 4.1 has this limitation of 2 GB in the size of sequenced apps ). We had to resize this to 50 GB.

 

 The code :


 

Step 2 :

As we need to import all 400 upgraded App-V 4.6 virtual packages into ConfigMgr , the last thing you want to do is play the monkey and create all packages in ConfigMgr 2007 R2 SP2 by hand … For this part I had a very good teamplayers that are very skilled VBscript writers , again a big thank you to Ewald Lieuwes ( http://www.wchulseiee.net/) & Wouter Schrijvens …

 

You could do it by using the ConfigMgr SDK , located at http://www.microsoft.com/downloads/en/details.aspx?familyid=064a995f-ef13-4200-81ad-e3af6218edcc&displaylang=en or you could use a standard base script that is located under <Drive>\<PathWhereYouInstalledSCCM>\Tools\VirtualApp\ManageVappPackage.vbs and wrap another VB script around it to build in some other checks or functionalities.

I used the default script located  under <Drive>\<PathWhereYouInstalledSCCM>\Tools\VirtualApp\ManageVappPackage.vbs and wrap another VB script around it .

Below I will post the VBS code written for :

 

  1. Going thru the list of upgraded 4.6 virtual packages stored at a DFS share \start\sccmsrc\[VIRTUALPACKAGESRC]\">\start\sccmsrc\[VIRTUALPACKAGESRC]\">\start\sccmsrc\[VIRTUALPACKAGESRC]\">\\<YourDomainName>\start\sccmsrc\[VIRTUALPACKAGESRC]\<Package Name>….
  2. Create a Source directory App-V package Folder for SCCM , In this case \\<ServerName\VIRTUALPKG$\<Package Name>… , if not exists.
  3. Import the App-V Package in ConfigMgr and add it to the distribution points , called \\CMSRV and \\CMDPMP
  4. Run this script on your SCCM box where your SCCM provider is installed !!

 

The code :