...

• 5/11/15Mon: Tested out with Zack and all looked good.
  • Acrobat DC still not loaded up, however.
• Info from Friday morning, 5/8/15, with KeeneS:
  • May switch Acrobat to the Serialized Creative Cloud.
  • Serialized Creative Cloud replacing current virtual application deployment this weekend, for Monday (5/11/15).
    

Issues Oliver is having

NEW reported issue to CIT, as of 5/14/15 (Thur)

I reused ticket number INC000001364135.

Cannot reset client to factory settings via base Linux OS. Nor access man

Not fixed, but getting closer. I can now get to the base Linux OS's System Information at the log-in dialog. That contains some helpful info, but provides no controls.

Once a VDI session is connected, one can press a key combination to get to the base Linux OS with more options/ controls:

• CTRL+ALT+DOWN ARROW

I ensured I got the most current config (*.ini) by booting the thin client from a CIT DHCP network.

Oddly, one can't get to those controls from the log-in dialog. (That is, the CTRL+ALT+DOWN ARROW does nothing at the log-in screen,) Not good, since should not have to have a running VDI session to access controls of the base OS, including ones to start a new session!

• This will matter if we have to do thin client support. :-)

Access include System Information (duh!), System Settings, and Home. But other options are grayed out since I’m not Admin.

• Within that access, there is still no option to revert to factory settings using that interface.
• Nor does it provide access to other things, such as some options within Settings, nor Add Connection and Global Connection Settings, FWIW.

What is the Admin name and Password? Or, is that giving me too many keys, if the same across Desktop Everywheare? I don’t like being locked out of my own hardware, naturally.

Workaround I found involved pulling the network cable on boot-up. That not ideal. Instead, want to be able to do within the base Linux OS, as I used to be able to do with this system before getting CIT's *.ini configuration.

Reported issue to CIT, as of 5/8/15:

5/14/15Thur: Update from Oliver's testing, reported to Keene today:

• Still not working. Now not even launching and failing. No indication it’s even trying to run.

Update from later that day:

• We recently discovered that Box Edit was not installed in “all users” style on the master.  It’s been fixed for tomorrow morning’s recompose.

Box Edit sync client not able to start.

...