Change package source path in my GPO [SOLVED + TIP]

[mnpg]

hi all,

my situation is quite simple :

I've deployed a msi throw a gpo, the source of the msi is stocked in a hard disk that has problems (he think the HD will felt soon). (NB : there is no DFS in my case)

Is it possible to change the source path of my package in the GPO (NB : i want to keep the package)? by editing the aas file in sysvol?

thanks in advance for your answers

[mnpg]

hi all,

my situation is quite simple :

I've deployed a msi throw a gpo, the source of the msi is stocked in a hard disk that has problems (he think the HD will felt soon). (NB : there is no DFS in my case)

Is it possible to change the source path of my package in the GPO (NB : i want to keep the package)? by editing the aas file in sysvol?

thanks in advance for your answers

for those which have the same problem, i've found an answer -> Migration Table Editor.

In my case, the process is:

• In GPMC, backup the target GPO in a local folder (it's your "GPO's local backup folder") : right-click the GPO and then click Back Up
• With Migrate Table Editor (found in Program Files/GPMC), click on Tools > Populate from Backup, open the local backup folder and choose the backup GPO.
  Modify the Destination Name by the new UNC path and save the migration table in the backup local folder
• Return in GPMC, Right-click the target GPO (used for the backup and for our update), and then click Import Settings.
  Follow the instructions in the Import Settings Wizard (you have to point the local backup GPO and the migration table file), and then click Finish.

AND ...... The package within the target GPO will have a new source path

ATTENTION : if you'll have transforms files used for the MSI package, take care that you'll have to copy them in the new SPD. (Import settings wizard returns a error if you don't do it)

For more info : http://technet2.microsoft.com/Window...55e531033.mspx

[mnpg]

...
AND ...... The package within the target GPO will have a new source path

The only problem is :
I DON'T KNOW IF PRE-DEPLOYED PACKAGE SOURCELIST WILL BE UPDATED, i mean i don't know if the SourceList path of the deployed package (contains in the registry > HKCR > Installer > Products > ...) is updated.

For new deployments, changes do not affect the installation process.

[AdamV]

Thanks for posting that solution, nice and neat and simple.

I don't know either, but suspect the installation source would remain unchanged.

[mnpg]

...
AND ...... The package within the target GPO will have a new source path

The only problem is :
I DON'T KNOW IF PRE-DEPLOYED PACKAGE SOURCELIST WILL BE UPDATED, i mean i don't know if the SourceList path of the deployed package (contains in the registry > HKCR > Installer > Products > ...) is updated.

For new deployments, changes do not affect the installation process.

I find another way to update the SourceList of pre-deployed packages. I create a VBS launched at startup that update the SourceList with adding the new UNC path

Here an exemple of script (for adding an UNC path)

[code:1]
Const ProductCode= "{31CB5031-C850-416C-B7B2-EEC53356118B}" : 'an exemple of ProductCode
Const SID = "" : 'UserSid must be NULL for per-machine context. UserSid can be null to specified current user, when context is not per-machine.

Const SourcePath="\\xxx\yyy\zzz\"
'Const SourcePath = "http://www/yyy/zzz/"

Const msiInstallSourceType = 1 : 'MSISOURCETYPE_NETWORK
'Const msiInstallSourceType = 2 : 'MSISOURCETYPE_URL

'Const msiInstallContext = 1 : 'Products under managed context.
'Const msiInstallContext = 2 : 'Products under unmanaged context.
Const msiInstallContext = 4 : 'Products under machine context.

Const Index = 0

Dim Installer, Product
Set Installer = CreateObject("WindowsInstaller.Installer& quot;)
Set Product = Installer.Product(ProductCode,SID,msiInstallCo ntext)
Product.SourceListAddSource msiInstallSourceType,SourcePath,Index[/code]

If you prefer URL path for the same product, switch in this script the settings SourcePath and msiInstallSourceType to the others values

NB : in my case, i choose msiInstallContext = 4 (Products under machine context). You'll have to define yours


More info about product object :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/product_object.asp

[PreviousPoster]

Hi,

I guess you know this by now, but I thought I would put this up for anyone else....

I have tried this with some software that is installed to the computer section of the GPO. When you perform this procedure, you don't have to worry about running the script to change the InstallSource property of the pre-deployed installs, as doing this backup and import makes all of the software get re-deployed. As long as you know this, and there isn't too much software to re-install on boot up, then it is still OK to use.

Ian