FSLogix Altitude value changes in compiled image

[Sandy Williams]

I just read a thread about the Altitude value/regkey only really being required if you use Elastic layering which we don't so probably a moot point now but I noticed something odd. 

 

I created a layer for FSLogix and set the Altitude value and sealed that. I created an image to our PVS server with Just OS + FSLogix, and Platform and the value of the altitude key changes.  I don't know what is changing the value, I don't have any GPO's or anything in my platform layer.  Is this normal behavior?  If there a way to see a lot of an image compiling to see what is altering the value?

 

If I publish without platform to my host the value is the one I set.

[Rob Zylowski]

Sounds like it was changed in the platform layer. Add a. Version to that and check.  Buy yes you only need it if you enable elastic layering

[Sandy Williams]

I would have assumed that too however same platform layer applied to other images w/o Fslogix layer and the reg key is completely absent. Stumped.

[Rob Zylowski]

It would have to be another layer that is not common between them and that has a higher priority than your fslogix layer.

[Sandy Williams]

I wish I could delete this thread.  Definately had a blonde moment.  I was looking at Services\frxdrv key not Services\frxdrvvt.  Thanks for replying.. thought I was losing it.

[Rob Zylowski]

no worries glad you figured it out