none
Long File Names for Update Rollup - Can they be renamed? RRS feed

  • Question

  • I have some questions about the files included in Update Rollups for DPM. It seems that there are always four files included in the Rollups. For example, these are the files from DPM 2012 R2 Update Rollup 3:

    • Detectoid for System Center 2012 R2 - Data Protection Manager Server-all-dataprotectionmanager2012r2-kb2966014_9f7ca4d5c695d550cdbb66aca36c693a392423be.exe
    • Detectoid for System Center 2012 R2 - Data Protection Manager UI-all-dpmmanagementshell-kb2966014_35fbc489fe14a5b81a6b9dba3a72fbfbbca8b21b.exe
    • Detectoid for System Center 2012 R2 - Data Protection Manager UI-all-dpmmanagementshell-kb2966014_22194522dff61a4a92c4e13c54e6f1f748882840.exe
    • Detectoid for System Center 2012 R2 - DPM Central Console Server-all-dpmcentralconsoleserver-kb2966014_f4ba66d1b7bb2280a80d37ebcf9442cb6ee10d0c.exe

    Questions:

    • Since these file names are so long, we sometimes get an error in Windows Explorer that it cannot copy the files because the total path is too long. Can we safely rename these files to shorter names? If we do, will that cause them to not install correctly?
    • Why are there two Data Protection Manager UI files, and what is the difference between them?

    Thank you.

    Friday, August 22, 2014 12:05 PM

All replies

  • Hi,

    Yes, you can safely rename the files because they self-extract themselves before installing the update.  I believe there is a 32bit and 64bit version of the management shell.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, August 23, 2014 4:44 PM
    Moderator
  • Thank you. In the Update Rollups, we notice that one of the two management shell files is always slightly larger than the other file. Is this a way that we can identify the 32-bit version and the 64-bit version? There doesn’t seem to be any other clear way to identify them.

    Monday, August 25, 2014 5:30 PM