8of9

Eswar Thank you for your reply - great blog post. However, I don't think I can find the field I want in there? I am talking about the "User Documentation" field within the "Application Catalog" tab in the properties of an Application, rather than in the deployment type.

Hello guys We've just made some changes to our estate and I am trying to query through SQL applications that have information within the "User documentation" field under the "Application Catalog" tab, but the SQL tables/views i'm looking in don't have any data populated. We use the Application Catalog tab for manual installs for applications but we don't have it enabled, which i'm guessing is why the tables are blank. Has anybody queried this type of information before? I have searched in vCatalogAppModelProperties, v_CatalogClassicAppProperties, v_UserAppsLocalizedPropsForCatalog as well as many of the CI tables. Thanks for any help.

From your smsts.log 'App policy for 'VMWare Remote Console Plug-in 5.1' not received. Make sure the application is marked for dynamic app install' For that particular application, if is isn't deployed, do you have "Allow this application to be installed from the Install Application task sequence action without being deployed" ticked in the application properties? Does the Install Applications section run if you temporarily remove the above application from the Task Sequence?

"Cannot read source file C:\_smstasksequence\packages\p0100041\win7_ent_x64_base.wim, Win32 Error = 1117" Do you have any other .wim images that apply okay? And is the content up-to-date on the Distribution Point?

Garth Thank you for the reply and clarification. I'll look into that.

Hello I'm currently experiencing an issue when performing Migration Jobs between two primary SCCM sites. When performing a migration from Site A (Site Code STA) to Site B (STB), the migration completes successfully but the "PkgID" of the application still has the "old" site code. So for example, If I am migration NotePad++ from Site A to Site B, I would go into Site B, create the migration job and watch it all go through. I would then change the content source in the deployment type to Site B's repository and distribute the content. If I then look at the PkgID either in SQL or in the site server logs I would expect to see STB12345 but instead I get STA09876 The workaround I have found is to migrate the application without a "Deployment Type" and only add that in once it has been migrated across. I just wondered if anybody could shed any light or if anybody had any advice Thank you