locked
App-V packages fail to migrate - Normal packages migrate just fine RRS feed

  • Question

  • Hi,

    We are in the middle of transition from one service provider to a new one. Currently the old provider still manages SCCM 2007. We (the new provider) have built new CM2012 environment in the same domain and are in the point where we are migrating objects and collections from 2007 to 2012.

    We have successfully migrated all the normal software packages, collections, images, driver packages that we need. The problem is that customer has over 120 App-V packages in sccm 2007 and while trying to migrate these the migration fails for all packages with this error

                                                                    [Worker]:                         Migrating object ... SMS_MIGRATION_MANAGER 12/15/2015 7:52:43 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Migrating object App-V CUSTOMER Fina 1.3 EN_x64_CTX_R03 with ID: SMS_Package.PackageID='SITECODE0067A' ... SMS_MIGRATION_MANAGER 12/15/2015 7:52:43 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Set the status of the job entity App-V CUSTOMER Fina 1.3 EN_x64_CTX_R03 to Running. SMS_MIGRATION_MANAGER 12/15/2015 7:52:43 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Migrating AppV package CUSTOMER Fina (SMS_Package.PackageID=SITECODE0067A) SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation is about to start ... SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation succeed, current user identity is: domain\username SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Successfully connected to share \\sourceserver\app-V$\_Citrix\CUSTOMER Fina 1.3 EN_x64_CTX_R03 SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Successfully disconnected from share \\sourceserver\app-V$\_Citrix\CUSTOMER Fina 1.3 EN_x64_CTX_R03 SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation is reverted. SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation is about to start ... SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation succeed, current user identity is: domain\username SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Successfully connected to share \\sourceserver\app-V$\_Citrix\CUSTOMER Fina 1.3 EN_x64_CTX_R03 SMS_MIGRATION_MANAGER 12/15/2015 7:52:44 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Successfully disconnected from share \\sourceserver\app-V$\_Citrix\CUSTOMER Fina 1.3 EN_x64_CTX_R03 SMS_MIGRATION_MANAGER 12/15/2015 7:52:45 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Impersonation is reverted. SMS_MIGRATION_MANAGER 12/15/2015 7:52:45 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Set the status of the entity App-V CUSTOMER Fina 1.3 EN_x64_CTX_R03 to Failed. SMS_MIGRATION_MANAGER 12/15/2015 7:52:45 AM 8700 (0x21FC)
                                                                    [Worker]:                                 Set the status of the job entity App-V CUSTOMER Fina 1.3 EN_x64_CTX_R03 to Failed. SMS_MIGRATION_MANAGER 12/15/2015 7:52:45 AM 8700 (0x21FC)
                                                                    ERROR: [Worker]:                         System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.     at System.Security.Cryptography.SHA256Managed..ctor()     --- End of inner exception stack trace ---     at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)     at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)     at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)     at System.Security.Cryptography.SHA256.Create(String hashName)     at Microsoft.ConfigurationManagement.ApplicationManagement.Icon..ctor(Image src, String id)     at Microsoft.ConfigurationManagement.ApplicationManagement.AppvContentImporter.UpdateDeploymentType(DeploymentType dt, String contentFile, Object context)     at Microsoft.ConfigurationManagement.ApplicationManagement.AppvContentImporter.CreateDeploymentType(String contentFile, Object context)     at Microsoft.ConfigurationManagement.MigrationManager.AppVMigrator.MigrateAppVPackages(String objectPath, String contentDest)     at Microsoft.ConfigurationManagement.MigrationManager.AppVMigrator.MigrateObject(MIG_Entity entity)     at Microsoft.ConfigurationManagement.MigrationManager.Migrator.<get_ExecutionPlan>d__0.MoveNext() SMS_MIGRATION_MANAGER 12/15/2015 7:52:45 AM 8700 (0x21FC)

    Now, the error here points to a GPO setting for System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing security setting. I asked the old provider to check whether this setting is applied to the source site for App-V packages, but it is not. Anyone have any other ideas where this setting might cause issues for migration if its enabled? Or if its something else all together thats causing AppV failing during migration?

    -Jaime


    Tuesday, December 15, 2015 6:40 AM

All replies

  • I asked the old provider to check whether this setting is applied to the source site for App-V packages, but it is not.


    What exactly did he check? \\sourceserver?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, December 15, 2015 6:59 AM
  • Yes, he checked the setting from the source server. This server acts as the source for both the normal packages as well all the App-V packages.

    -Jaime

    Tuesday, December 15, 2015 10:13 AM