C
cwa107
Guest
My organization has recently deployed build 1709 and I'm noticing what I believe to be a recent change in behavior specific to client devices that run this build.
I run a particular client application under the context of a service account. This application is deployed via SCCM and during the installation process, I set a number of keys within the service account's profile in the HKU hive, specific to proxy settings. I'm noticing that on clients running build 1709 and newer, that as soon as the application is terminated, the SID for this profile no longer appears in the HKU hive. I don't use a roaming profile for this account and to my knowledge, we do not apply any GPOs that are forcing this deletion. It also doesn't seem to affect Win7 devices that are still in the environment.
As my responsibility is specific to this application, I don't really pay a lot of attention to changes in the various Win10 builds. Is this behavior by design, and if so, how do I work around it?
More...
I run a particular client application under the context of a service account. This application is deployed via SCCM and during the installation process, I set a number of keys within the service account's profile in the HKU hive, specific to proxy settings. I'm noticing that on clients running build 1709 and newer, that as soon as the application is terminated, the SID for this profile no longer appears in the HKU hive. I don't use a roaming profile for this account and to my knowledge, we do not apply any GPOs that are forcing this deletion. It also doesn't seem to affect Win7 devices that are still in the environment.
As my responsibility is specific to this application, I don't really pay a lot of attention to changes in the various Win10 builds. Is this behavior by design, and if so, how do I work around it?
More...