Page Comparison

DC 4.8.0

Link to the release notes for this release: DC 4.8.0

Known issues

Install (You need to know this before installing)

Install (You need to know this before installing)

Web Install (You need to know this before web installing)

.

Update (You need to know this before updating)

Fix to enable update of Digibatch

Install (Help with troubleshooting)

Update (Help with troubleshooting)

DC 4.7.0

and

DC 4.7.1

Link to the release notes for this release: DC 4.7.0

Known issues

By enabling AD FS embed links from the DAM Center will not work anymore

Install (You need to know this before installing)

Update (You need to know this before updating)

New Features

• There's a new UI for jobs in the DC, which you can access by going to the job system in the DC and "editing" a job. The technical states can be found here in NEK's comment:

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-1349

• There's a new PW reset functionality that implements 2 windows services and 1 web service. They're all in the installer. The web service can be reached at [site]/api/v2, and is needed for MM 4.10.0.
• OOBE is now part of the installer. You cannot update a non-OOBE to an OOBE. The OOBE has all MHM's findings included from the /wiki/spaces/PSBOK/pages/60162102 list.
• The "Template UI" is removed from this release, which (supposedly) means that metadata cannot be extracted as a manifest in this release
  • (This is my current presumption - things might have changed. If you feel that this is not correct, please inform me, so I can edit this entry)
• The installer now includes most requirements - the only ones that aren't in there are .NET 4.6.2 and the windows updates. These are needed for the installation of DC. The reason why these are not included is that they need restarts to function.
• There's a new Search 2 UI, and a documentation regarding it - which can be found here: Draft - Search Editor - DAM v4.7.0. It's highly suggested that you read it.
• A lot of searches are now hidden, as they're not something that anybody should be touching.

DC 4.6.1

• Many, if not all of the 4.6.0 issues still persist in this release. (They can be seen in the table entry above)

• You must still patch the DC if you are updating from a version prior to 4.6.0 (that is 4.5.1 and below). Again, see the table entry above.

• As of 4.6.0, you have to use the new version of the following file: ffmpegtag_H264_main_3.0.xml which is not updated automatically (I think is has to do with batch and DC being decoupled) (Storage\DMM\Profiles\Video)

DC 4.6.0

• You're not able to update without patching (

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-1181

  . see NEK's comment from 26/Oct/16 9:37 AM)
• They have corrected the "greater than" issue - so workflows, where this is implemented, needs to be reversed!
• (This is something that PS can sell) You need to manually add the 1080p download quality to your users/groups to have it enabled in MM/VP. It has already been added to the portals. (Format: 50037 - Video H264 1080p) (It's very likely that all videos in portals must be transcoded.)
• Install URL Rewrite to IIS server (Use this link: http://www.iis.net/downloads/microsoft/url-rewrite [MHM tested LIU])
• The user you are using has to have write access (read access isn't sufficient) to the default upload catalog folder (Constant: DEFAULT_CATALOGFOLDERID)
• (This is still not pinpointed entirely) When creating new Solr search, on PSU/I at lest you need to switch back and forth between ApplicationPoolIdentity and LocalService, as it will not create a core folder without the switch. Recycle or Restarting will not work. Only changing the user works. PSI doesn't have this problem anymore it seems.
• You need to install the new version of the batch system (3.0.1 92 is the newest as of speaking - you need to install .NET 4.6.2 in the batch server)
• You need to unlink the old batch before updating. NEK and JBH have informed me that you mustn't use a pre-4.6.0 on a 3.0.0 batch system. The way I've understood it, there's a risk to the _job-database, which might become broken.
• If the install_config_actualsite isn't properly configured, the update.aspx will display a form where you can input all the information. THIS FORM ISN'T WORKING!!! -

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-980

  (LiU 4.5.1 → 4.6.1 doesn't) (PSI/U 4.6.0 → 4.6.1 works) (UPDATE: Impersonation doesn't work - you should therefore use a non-unc path e.g. C:/... instead of \\)
• Copy template should be looked at, as of this version uploaded content's workflows will not trigger as it did prior to DC 4.6.0
• Copy template has an issue seemingly starting from 4.6.0 → 4.6.1 RC3 (We know that it's an issue on 4.6.1 RC3) which has been fixed in versions greater than 4.6.1 RC3. You have to disable keywords from IPTC. (LBB has done it already, and it works)
• Clean Up still doesn't work on Azure (I've been told) - And it might also have some issues in 4.6.1 RC3 still.
• If you don't install (or already have installed) "Microsoft Visual C++ 2012 Redistributable (x64)" there will be a DFS error regarding default previews in the DC install/update process.
• You need to install .NET 4.6.2 on the batch server
• As of 4.6.0, you have to use the new version of the following file: ffmpegtag_H264_main_3.0.xml which is not updated automatically (I think is has to do with batch and DC being decoupled) (Storage\DMM\Profiles\Video)
• By default you're not able to publish .zip and .xlsx to MM, as there's no profiles set up in the MM's profiles and destinations. - Set up the transcode quality, assign it to a profile, and assign that profile to the MM.

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-1594

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-1590

• In cases where publishing of other than IMAGE assettypes hits the same profile (e.g. PSD files), check if Transcode Settings has Source format IMAGE (should either be "All" or you need to create a new one for the PSD assets (in this example)). The result if NOT doing this is that publishing of PSD files will not produce any file (in this example).
• When you update from an earlier version (e.g. pre DC4.5.0) you may encounter that you have no thumbnails. Please use the script in the following link to fix them:

  Jira Legacy
  server JIRA serverId 6a92bc81-7530-3721-8493-c45e562ab36e key DAM-1263