Just a quick not to explain what happened with our install of this:
We were upgrading from the BSID Black Shield ID 2.7 Windows Agent software on a Windows 2008 R2 machine but keeping the current (for now) Blackshield 2.7 installation of the administration and SQL installs. Our new remote desktop server was a new 2012 R2 box and we installed the x64 Windows 8.1 Safenet agent as described in the install notes.
The installation went as planned and asked for the NetBIOS names of the two authentication servers which we entered as requested.
When it came to testing however the system described the user authentication as having failed.
When we checked the logs of the authentication servers running BSID 2.7 there was no entry and when we ran the Windows Agent software on the Remote Desktop machine it only showed the 'Help' tab rather than the rest.
The simple solution was that when we right-clicked the software and 'ran as administrator' the system reported that part of the registry concerning the software was corrupt and had to be removed. We agreed to this by clicking OK and were then presented with all the tabs as normal and were able to populate the correct server names as required. the system now appears to authenticate as expected...
After installing Office 365 as per the post below the Windows 2012 R2 Remote Desktop VM the system indicated that it had to restart to activate office 365 and so this is what I did.
The system then decided it had to perform updates during the restart which was fine and it continued to get to 30% where it stayed for 24hrs. Assuming that there was no choice the machine was restarted again and this time the whole system got to configuring updates at 6% and stayed there for 3 days.
Every time the server was reset this was the outcome.
Having looked through a few suggestions I performed the following:
1. Amended the 'Automatic Start action' on virtual machine settings so that secure boot was disabled
2. Started up the troubleshooting option from the startup repair and chose the command prompt whereupon I performed the following:
3. Renamed the softwaredistribution folder to softwaredistribution.old on the assumption that a new folder will be created when the windowsupdate service next tries a download.
4. Searched for all pending.xml.* files in Windows\WinSXS and deleted them
5. Ran 'dism /image:C:\ /cleanup-image /revertpendingactions' to clear any awaiting updates.
6. Created a blank pending.xml file in WinSXS (not sure if this made a difference but it was a piece of advice seen here: https://social.technet.microsoft.com/Forums/en-US/7364c2ff-1d52-4767-bfec-d97d42921d5c/interrupted-vm-stuck?forum=winserverhyperv) which they did using 'echo > pending.xml' whilst in Windows\WinSXS\ and then rebooted.
The VM undid all of the updates and started up and the Office 365 on Remote Desktop Virtual Machine asked for an email address with which to activate - only took 6 days then!!!