kmssetup.cmd constantly running in the background in AL 2001/1912 LTSR

[Nick Panaccio]

I'm testing my new 1912 LTSR VDA (W10 1809) on App Layering 2001, and kmssetup.cmd is constantly running in the background (after calling StartCCMEXEC.cmd), so it never actually finishes processing. I do not have SCCM installed on this VDA, and the registry keys it's looking for don't actually exist, so I have no idea why the log file says otherwise. I've validated this behavior in three different images that have App Layering 2001 installed. Has anyone else seen something similar? I've opened a case with Citrix, but figured this was worth posting here, as well. Attached are the relevant logs.

kmssetup.log StartCCMEXEC.log

[Raymond Colon]

There is a hotfix available, since my initial post, or you can manually edit the file, kmssetup.cmd.

[Raymond Colon]

Please open a case, since we recently discovered and fixed this issue

[Nick Panaccio]

14 hours ago, Raymond Colon said:

Please open a case, since we recently discovered and fixed this issue

I currently have a case open, and was told that the fix would be released in the next App Layering release. The workaround is to simply comment out the CCMEXEC stuff in kmssetup.cmd. Is there another fix that I'd be able to get without having to wait for the next build?

[Nick Panaccio]

I asked earlier today and was told there was no hotfix and to simply REM out the lines. Is the hotfix anything more than kmssetup.cmd? While testing the kmssetup from 1901 seems to work fine, I'm not a fan of the workaround. I just asked the tech who has my ticket if he can provide the hotfix.

[Nick Panaccio]

17 hours ago, Raymond Colon said:

There is a hotfix available, since my initial post, or you can manually edit the file, kmssetup.cmd.

 

I just installed the hotfix (upgraded the ELM and published a new image), but it did not resolve the issue for me. Back to the drawing board, I guess.

[Nick Panaccio]

In case anyone stumbles across this thread, there is both an ELM appliance upgrade hotfix as well as a machine tools hotfix. Once the new machine tools were extracted, the issue was resolved.

[Raymond Colon]

Sorry for not responding sooner. Actually, just the new OS machine tools executable fixes the issue. The ELM upgrade does not fix the issue, but will not cause any issues if applied. Thus you were not told, or should not have been, to rollback.

[Raymond Colon]

If anyone prefers to alter the scripts and wait for the next GA, public release, which will include the new machine tools, below is what we are recommending be done. 

1) Add a version to the OS layer

2) Edit c:\windows\setup\scripts\kmsdir\StartCCMEXE.cmd

3) Search for the line, "set VALUE_NAME-Start"

 

4) Add beneath that the three lines
          set ValueName=
          set ValueType=
          set ValueValue=

5) Save the file

 

6)  Finalize the layer

 

7) Edit the existing image template or create a new template and use the new OS layer version

[Mike Kelly1709153237]

On 2/6/2020 at 10:25 AM, Raymond Colon said:

If anyone prefers to alter the scripts and wait for the next GA, public release, which will include the new machine tools, below is what we are recommending be done. 

1) Add a version to the OS layer

2) Edit c:\windows\setup\scripts\kmsdir\StartCCMEXE.cmd

3) Search for the line, "set VALUE_NAME-Start"

 

4) Add beneath that the three lines
          set ValueName=
          set ValueType=
          set ValueValue=

5) Save the file

 

6)  Finalize the layer

 

7) Edit the existing image template or create a new template and use the new OS layer version

Is there an ETA on the public release of this fix?

[Raymond Colon]

It is available, now. The fix is in the OS machine tools.

[Nick Panaccio]

Specifically in build 2003: https://www.citrix.com/downloads/citrix-app-layering/product-software/citrix-app-layering-2003.html

[Mike Kelly1709153237]

1 hour ago, Raymond Colon said:

It is available, now. The fix is in the OS machine tools.

 

Interesting, I wonder why this fix wasn't called out specifically on the "Fixed issues" list?

[Nick Panaccio]

4 minutes ago, Mike Kelly1709153237 said:

 

Interesting, I wonder why this fix wasn't called out specifically on the "Fixed issues" list?

I see it called out - third bullet point: https://docs.citrix.com/en-us/citrix-app-layering/4/fixed-issues.html

• An issue that had caused the StartCCMEXEC.cmd script to continually grow the log file, StartCCMExec.txt, even when CCMExec is not installed, has been fixed. To fix this issue for your deployment, download the new OS Machine Tools folder for 20.3, and replace the current version of the StartCCMEXEC.cmd file with the new one. (UNI-77471)

 

The issue was the StartCCMEXEC.cmd file, ultimately. I can confirm that the file in this new package is the same as the private hotfix I have installed (20.1.0.18).