Internet Explorer 11 x64 How to Enable

http://winaero.com/blog/how-to-enable-64-bit-internet-explorer-processes/

Creating Volume Licensed App-V Office 2016 package using ODT

Although MS have withdrawn the option to create a Volume Licensed version of Office 2016 it is still possible to do by the power of the internet :)

Near the bottom of this article is a post by Robert Gijsen on Monday, April 10, 2017.  I have tested his instructions successfully.
https://social.technet.microsoft.com/Forums/office/en-US/367938d8-9210-4c8f-aa5e-c8de41c0a7ca/odt-2016-invalid-product-proplusvolume-specified?forum=Office2016setupdeploy

Robert has provided the older ODT version for download here:  THANK YOU !
https://1drv.ms/u/s!ApkCUv0wQm8UgwFgwRzJXD4N3H-R

Getting this done was not easy.  I would advise keeping the paths as short and simple as possible. Also I did seem to get success by making sure that HKCU\Software\Microsoft\Office\ClickToRun had been deleted or renamed after a run attempt.

Here is my ODT setup.exe configuration file:

<Configuration>

  <Add OfficeClientEdition="32" Channel="Current">
    <Product ID="ProPlusVolume">
      <Language ID="en-us" />
    </Product>
    <Product ID="VisioProXVolume">
      <Language ID="en-us" />
    </Product>
    <Product ID="ProjectProXVolume">
      <Language ID="en-us" />
    </Product>
  </Add>

  <!-- Updates disabled while an update folder location is decided. -->
  <Updates Enabled="FALSE" Channel="Current" /> -->

  <!-- Install Mode Settings -->
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Level="Standard" Path="%windir%\custom\installlogs" />

  <!-- Packager Mode Settings - Sets the App-V Package GUID -->
  <Property Name="PACKAGEGUID" Value="PutYourGUIDHERE"/>
 
</Configuration>

Run
setup /download <FullPathToXMLConfigFile>

Create the folder where the App-V package will be output to.

Then
setup /packager <FullPathToXMLConfigFile> <App-VPackageOutputFolderPath>

if that fails then you can do the magic command posted here by Trausti Sigurbjörnsson
A failure results in HKCU\Software\Microsoft\Office\ClickToRun\LastScerarioResult = Failure

browse to C:\Users\<user>\Appdata\Local\Temp and Copy "Microsoft Office" folder to "C:\Temp" and then rename it to MSO

After That run following command:
C:\Temp\MSO\root\flattener\flattener.exe /Source:"C:\Temp\MSO" /Dest:"C:\Temp\Office 2016 AppV" /Version:"16.0.8067.2115" /ProductReleaseIDs:"ProPlusVolume,VisioProXVolume,ProjectProXVolume" /Cultures:"en-US,x-none" /Platform:"x86"

For the above command you can determine the version number by checking in the registry for the versions written during the OfficeClickToRun.exe phase.

HKCU\Software\Microsoft\Office\ClickToRun\ProductReleaseIDs\2601BB9E-AEBE-441E-A166-5652BF9B61C3\ProjectProXVolume.16\en-us\Version


Error Code Meanings
error 0-1010 (0)  - check your XML in the XML config file.

The App-V package requires the App-V Client setting EnablePackageScripts = 1.  This is because there are scripts coded into the AppVXManifest.xml file within the .appv package file.  MSI installers are being called to install integration components such as the KMS server licensing items.

Globally Unique Identifiers (GUIDs) How Unique are they?

GUIDs are used as identification tags to identify and track things.  The clue is in the name.  They are unique, however because each one is a id within a defined set, it is theoretically possible to get a duplicate GUID. How possible? - well as "unique" suggests, it is nearly impossible.

What is a GUID?
A GUID is a set of 32 characters each of which has a hexadecimal value (0-f).  The are arranged in the format
21EC2020-3AEA-4069-A2DD-08002B30309D
They are typically randomly generated.

Each of the 32 characters is made up of 4 bits so the number of bits in the GUID is 4x32=128

6 of the bits are reserved to designate that GUID is random.

The remaining 122 bits (128-6=122) can either be 1 or 0.  This means there are 2 to the power 122 (2^122) combinations.

How many possible GUIDs are there?

2^122 which is approximately 5.3×10³⁶
At this point it becomes a waste of time and space to use long hand notation.  These types of numbers are generally referred to in science as large numbers.  What? You'd still like to see the actual number? Oh OK its
5,316,911,983,139,663,491,615,228,241,121,400,000

So at this point you need something to compare that with to get a feel for how big that number is.  Here's a few numbers in order of size to get an idea.

In ascending order then:
The mass of planet earth in Kilograms
6 x 10²⁴

Number of atoms in the average human body.
7 x 10²⁷

The mass of the Earths Sun in Kilograms
2 x 10³⁰

The number of water molecules in an olympic size swimming pool
1.34 x 10³²

Number of possible GUIDs
 5.3×10³⁶

Number of atoms that make up the planet earth.
1 x 10⁵⁰


http://physicsoftheuniverse.com/numbers.html

http://mrdee.blogspot.co.uk/2005/11/how-many-guid-combinations-are-there.html

Dynamic Configuration

https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/appv-v5/about-app-v-51-dynamic-configuration


COM Mode
https://blogs.technet.microsoft.com/gladiatormsft/2013/09/11/app-v-on-com-isolation-and-interaction/

Disk Change Please.

Create a System Image Backup, then boot from a system repair disc and restore the image easy? Only if the new disk and the old disk are the same size.

If the new disk is smaller it is necessary to shrink the existing large disk down to a size which can fit on the new smaller disk.  The problem with shrinking is that some files are immovable which limits the amount the drive can be shrunk by.

If you run a shrink operation, it will advise how much space can be shrunk by.  In the event log a 259 event will detail the type of immovable file which is acting as a block on shrinking further.  The types of things which create immovable items are, Windows Search (turn off), Hibernation, and the most likely; System Protection, delete the restore points and related items.

Once these have been addressed, there is the option of, emptying the recycle bins and defragmenting the drive but this is unlikely to improve the shrink potential very much.

Shrinking can take a while so just leave it to get on with it.

Once the shrink has been completed, create a system image on an external drive.  I bet you're thinking you're good now right? Forget it.

You STILL won't be able restore that system image.  Can't do it to a smaller disk see? Even when a load of it is unallocated and blank.  But what you do have is a backup of the partitions in that system image :)

This forum thread saved my bacon
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f15bfe2f-e265-479a-afa3-f055530c97f5/windows-server-backup-0x80042407-seriously?forum=winserverfiles

You can easily create a System Repair Disk within Windows 10.  You can then boot from that to a command line where the command line tools are available.  Diskpart for disk partitioning and Wbadmin for backup/restore.

In Summary

Obtain the version information of your required backup.
wbadmin get versions –backuptarget:<X:>

Obtain the sizes of your backed up partitions for your required version
wbadmin get items –version:<versioned> -backuptarget:<X:>

Use DiskPart commands or other tools to create the same sized partitions on the disk you are going to restore to.  Also use the tool to list the partitions so that you can correctly specify the recovery target.

Make use of the wbadmin help and example commands to see how to construct the commands.  They can be lengthy and accuracy is essential especially with the -items parameter.


Wbadmin start recovery –version:<versionid> -backuptarget:<x:> -itemType:Volume –items:\\?\Volume\<GUID>  -recoverytarget:D:

Once you have restored the data, you need to ensure the boot system is correctly configured.  You can try the Startup-Repair tool on the System Repair Disk although I did not have much luck with that.  DiskPart can set the active partition for you.  After that you may have to spend some time with bootrec.exe and/or bcdedit to fine tune it.  After a bit of playing I managed to get it to boot although it was not easy.  I have to admit I do not know exactly how it fixed it to boot correctly !