<C-drive> folder token not capturing

[TomH201110141]

Hello Community,

I have a problem with the hidden folder token "<C-Drive>". When using this like in example:

[IncludeFolderTrees]
<C-Drive>\TEST

It does not capture newly created files. Only files which exist at the moment of the login are captured into the zip-archive.

Example:

Login to desktop and you find a folder and file c:\TEST\file1.txt. You create a second file c:\TEST\file2.txt

After logoff you find in the zip-archive only the file1.txt file. The file2.txt is missing.

Does anyone know why??

[TomH201110141]

Doesn't anyone have an idea?

[DEMdev]

Hi @TomH201110141,

As a test: Does this behave differently if you try this using DirectFlex instead of at logon and logoff?

And as another test: What do you see in the log if you use something like

   [IncludeFiles]
   <C-Drive>\TEST\file1.txt
   <C-Drive>\TEST\file2.txt

?

[TomH201110141]

Hi @DEMdev 

I have tested now three different scenarios with curious results:

Golden Image contains c:\TEST\file1.txt

1. scenario:

with DirectFlex: (as trigger for import I have taken C:\Program Files\Windows Photo Viewer\ImagingDevices.exe)

Export when last executable exits: everything works like expected - all changes (additional files, changes in files) are saved.

2. scenario: (I have taken the zip-file from szenarion 1 - it now contains 3 files: file1.txt, file2.txt, file3.txt)

with DirectFlex: (as trigger for import I have taken C:\Program Files\Windows Photo Viewer\ImagingDevices.exe)

Import: it works - test.zip (file1.txt, file2.txt, file3.txt) - all files are getting imported

Export at logoff: test.zip contains only file1.txt <-- wrong behavior (missing file2.txt and file3.txt and all other changes like writing in files or additional files)

3. scenario: (DirectFlex disabled)

Import at logon: it works - test.zip (file1.txt, file2.txt, file3.txt) - all files are getting imported

Export at logoff: test.zip contains all files untouched (file1.txt, file2.txt and file3.txt) even when I have deleted a file, they still remain in the zip-file, additional files are not saved. The zip-file itself get's a new timestamp from export but it's completly the same like before.

The log itself doesn't show any errors:

Logon:

Importing profile archive 'TEST.zip' (\\XXX\XXX\DEMProfiles\XXX\Archives\Applications\TEST.zip)

Logoff:

2023-06-29 13:05:46.988 [INFO ] Exporting profile using config file 'TEST.INI' (\\XXX\XXX\DEMConfig\general\Applications\TEST.INI)
2023-06-29 13:05:47.012 [INFO ] Exporting file information
2023-06-29 13:05:47.012 [DEBUG] ExportFiles: Recursively processing folder '<C-Drive>\TEST'
2023-06-29 13:05:47.013 [INFO ] Exported file information successfully
2023-06-29 13:05:47.017 [DEBUG] Stored 1 entry in profile archive (size: 0; compressed: 2)
2023-06-29 13:05:47.017 [DEBUG] Backing up '\\XXX\XXX\DEMProfiles\XXX\Archives\Applications\TEST.zip' to '\\XXX\XXX\DEMProfiles\XXX\Backups\Applications\TEST 2023-06-29 999999.zip'

[DEMdev]

Hi @TomH201110141,

Are you using App Volumes, by any chance? If so, this seems to be another case where App Volumes detaches the writable volume before DEM gets to run.

[TomH201110141]

Yes, we are using App Volumes (4.10.1.9 - 2303.1) but without writable volumes. 
DEM is version 10.9.0.1105 - 2303. 

[DEMdev]

Hi @TomH201110141,

If you're not using a writable volume, App Volumes uses an "implicit" writable. I don't know much about App Volumes; is adding exclusions to snapvol.cfg possible if you don't use a writable?

[TomH201110141]

I did a quick test (scenario 1 and 2) by uninstalling the App Volumes agent and indeed without the agent the behaviour changed back to normality - all changes are captured in the zip-file. 

Shall I exclude the folder c:\test\ or what do you mean?