Laurent,

Thanks you.  I tried comparing the permissions on teh fields themselves.  I will look at the filters.  For some reason I believed the filters to start with AST and only looked there.  I will check now.

Okay, that makes sense.  I thought something didn't install correctly. Checking now...

Laurent,

You pointed me in the right direction.

There are two main Active Links that change the added fields on the AST:ComputerSystem form.  They are:

ASI:SHR:LockDown_CommonFields_1xx

ASI:SHR:CI_300_ChangeFieldsToReadOnly_xx

I personally do not like modifying much of the OOTB design, so I created these new active links:

ASI:SHR:LockDown_CommonFields_130 (Last one was *_120)

Associated Forms:  AST:ComputerSystem

Primary Form:  AST:ComputerSystem

State: Enabled

Execution Order:  130 (Matched the number of the title)

If Action - - Change Field - - Field Name - - Read Only

ASI:SHR:CI_300_ChangeFieldsToReadOnly_45 (Last one was *_44)

Associated Forms:  AST:ComputerSystem

Primary Form:  AST:ComputerSystem

State: Enabled

Execution Order:  300 (Match the others)

Run If Qualification:  $OPERATION$ = "DIALOG"

If Action - - Change Field - - Field Name - - Read Only

After creating these I found that each were related to a Active Link Guide.  They are:

ASI:SHR:CI_WindowOpen

ASI:SHR:LockDown

I added the newly created active links to these guides.  Then I restarted my services.  The fields are now read only for basic users.