Config Manager Client on VDI machine not registring in Console

LongLastingFlavor 216 Reputation points
2022-09-12T15:33:41.88+00:00

Hello,

I need to install the Configuration Client on our Citrix Virtual Desktops which are non-persistent. There are a couple websites that pretty much mention the same steps listed on this page...

https://sccmentor.com/2014/04/08/dealing-with-bad-mif-files-in-a-vdi-environment/

I installed the client on the master image then updated 2 Virtual Desktops. In the Configuration Manager Console only the Master Image and one of the Virtual Desktops is registering. The one not registered does have the client installed but i am not sure why it is not appearing. Ultimately i need to install the client on all of the Virtual Desktops and am hoping that once i get this one issue resolved that it will just work for the rest. The Configuration Manager version is 2207 and the VDI machines are running Windows 10. The reason for needing to do this is for the Azure Intune Management.

Any help would be appreciated.

Thank you!

Steve

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,036 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Frank Dong 251 Reputation points
    2022-09-15T07:42:09.727+00:00

    Please check ClientIDManagerStartup.log under c:\windows\ccm\logs. I've seen such case which are caused by machine certificate missing when registering the client to the server, the error is recorded in ClientIDManagerStartup.log.

    For your information, for VDI template machine, before deploying
    you have to delete SMSCFG.INI file under C:\WINDOWS\
    you need to delete Machine Cert store SMS


2 additional answers

Sort by: Most helpful
  1. Rahul Jindal [MVP] 9,881 Reputation points MVP
    2022-09-12T21:01:18.937+00:00

    I will start by checking the client side logs. Clientidmanagerstartup would be a good place to start.

    1 person found this answer helpful.

  2. LongLastingFlavor 216 Reputation points
    2022-09-26T21:37:41.98+00:00

    Ended up working with Microsoft support and the issue has been resolved. The following batch file is what i am using on the Master Image and so far no issues to report.

    @Echo Off
    net stop CcmExec
    sleep 5
    DEL c:\Windows\SMSCFG.ini
    Reg Delete HKLM\software\Microsoft\Systemcertificates\SMS\Certificates /f
    Reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f
    Reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIdValidation /f
    certutil -delstore SMS SMS
    wmic /namespace:\root\ccm\invagt path inventoryActionStatus where InventoryActionID="{00000000-0000-0000-0000-000000000001}" DELETE /NOINTERACTIVE

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.