Workdocs Drive does not install

Question

Environment:  
- Two Workspaces running in same VPC with Internet access via NAT GW and IGW  
   - AWS Workspace running on Windows Server 2008 R2 Datacenter  presenting a Win 7 desktop  
   - AWS Workspace running on Windows Server 2016 presenting a Win 10 desktop  
- Region us-west-2  
- AWS Workdocs Drive installed and working in Win10 Workspace (after roughly 3 hours of tweaking rights and browsers etc -- yeah, I'm complaining)  
- AWS Workdocs Drive seems to install on the Win 7 Workspace and I get the icon for completing the install, but....  
  
Next step should be to run the Workdocs Drive installer that brings up the login screen for the desired Workdocs instance.  
  
Problem:  
The login screen never appears. Instead....  
- Opening on the Workdocs Drive icon as Administrator results in the tray icon showing up with the message "Authenticating User..."   
- The MS Message Queuing Service is started as are its components, MQAC, RPC, and Windows Event log  
- The Event log shows the following errors:  
   - The only negative event taking place when the installation starts is a warning that mentions a need to restart.   
   - Informational events state that the installation of the drive was successful  
      -- Since there was no pop-up message displayed I restarted the Workspace instance  
   - Upon restart the Tray Icon still displays the message "Authenticating user"  
   -  the Event log shows two Errors from the Source "Amazon Workspaces":  
      --  "Error when trying to start service HighlanderCGH."  
      -- "Line 296. Cannot find any service with service name 'HighlanderCGH'."  
  
I'm flummoxed.  Any useful actionable advice is welcome.  
  
Thanks in advance  
Abev  
  
Edited by: albevier on Jun 22, 2019 10:25 AM

Answer

I noticed while installing workdocs drive on a few workspace instances that sometimes it would hang forever during the install process. Eventually I gave up and from the local workspace app I restarted the workspace and the next try worked fine.

Answer

BTW, I did get it to "install" after much tearing of hair.  Never could figure out the error but I created a new workspace and was able to install without error.

Answer

Hi albevier:  
  
Thank for being AWS customer and choosing WorkSpaces and WorkDocs.  
let us follow-up with you offline to understand why your setup for WorkDocs client previous instance of WorkSpaces didn't work.  
  
Thanks

Answer

Hi george-tempo:  
  
I have sent a DM to you to collect additional information for your setup. If there are pending software updates on those few WorkSpace instances, WorkDocs Drive installation will not complete until restart.  
  
We will be able to review the setup and help unblock your team  
  
Thanks

Answer

After much mucking about for several months and trying to share documents between the two workspaces (sometimes successful, sometimes not) with many "Workdocs Drive" applications hangs, I decided that I would move on.  Conclusion: Workdocs Drive is not ready for prime time.

Workdocs Drive does not install

Relevant content