ThinApps not being read from CIFS share

[CALittle]

We are using Workspace 2.1.0.2100 Build 2099413

We had been storing our ThinApp packages on a NetApp filer using a Virtual Storage Machine and a CIFS volume, as our company is moving away from Windows Servers using SAN storage. Even though the share is created on the NetApp filer instead of a Windows server, we still access it using \\server\ThinApp

This has been working well until we went to integrate Workspace.

Workspace wouldn't read ThinApp packages stored on the CIFS volume. We tried a couple of things, but we couldn't get Workspace to read the CIFS volume until we shared it from a server (Windows 2012 R2).

Is this a know issue (have searched but can't find anything), or have we overlooked something here?

[pbjork]

Sometimes SAN file shares are not truly a Windows CIFS share. They produce something very close but makes Workspace error out when trying to access it. Not sure which SAN file services that works and which doesn't. But I've heard reports about this. Sometimes it's down to privileges. If you do not specify a user and password for ThinApp repository access you must grant read and execute privileges to authenticated users. (Workspace access the share using it's computer account if not specified a username.)

[JaceJ]

I had this exact same problem.  Once I added my filer share to workspace it never synced any apps.  Eventually we dug in the logs and found it was mounting the drive just not recognizing it in sync.

Check this

Log into the workspace VA

cd /mnt

ls

You should see a directory called thinapp

cd thinapp

ls and see if you find the files from your filer share. 

If they show up then I suggest rebooting the appliance.  Once I did that I was able to perform a sync and add my thinapp packages on workspace.

Don't forget you need to add the workspace option in the thinapp.  So we have a separate directory with just apps for workspace \\filername\thinapprepo\workspace.