search

DeploymentArtist / SWP1

Sample Files for Stealing with Pride - Volume 1 - Advanced OSD Customizations for MDT 2013 and ConfigMgr 2012 R2. Written by Johan Arwidmark and Maik Koster
MIT License
51 stars 34 forks source link

EventPub #8

Open itamartz opened 1 year ago

itamartz commented 1 year ago

Hi, We setup in our environment the monitor and set the url in the costume ini. When we start the lite touch on 4 pc, in a 2 min between each one, the refresh option, we see all of them with the same id.

Can you explain what going on ??? Tnx. Itamar

MaikKoster commented 1 year ago

Hey Itamar, can you please provide some more details? Are you talking about the MDT Monitoring, or some custom monitoring based on the sample that was provided?

Each deployment should have a unique ID. This deployment specific ID is stored in task sequence variable LTIGUID and is not created on the client computer, rather taken as response from the first call to the monitoring service. All further calls from the same machine during the same deployment to the monitoring service will use the ID that was returned from the first call.

If deployments of different computers show up with the same id, it's very likely that it's not properly generating a random id, when being called with no ID. In the sample that we provided, you can see a sample implementation of this behavior in the lines 19-22 of this file https://github.com/DeploymentArtist/SWP1/blob/master/MDTMonitoring/MonitoringDemoCSharp/Controllers/MDTMonitorEventController.cs. Another possibility is, that you have added a value for LTIGUID to your customsettings.ini. In this case, all your deployments will use the same ID on the monitoring side.

itamartz commented 1 year ago

Hi, Thank you for your quick response. I use the build in MDT web service, so I will take a Look for the task variable you say.

BR. Itamar

On Fri, Jul 28, 2023, 22:59 Maik Koster @.***> wrote:

Hey Itamar, can you please provide some more details? Are you talking about the MDT Monitoring, or some custom monitoring based on the sample that was provided?

Each deployment should have a unique ID. This deployment specific ID is stored in task sequence variable LTIGUID and is not created on the client computer, rather taken as response from the first call to the monitoring service. All further calls from the same machine during the same deployment to the monitoring service will use the ID that was returned from the first call.

If deployments of different computers show up with the same id, it's very likely that it's not properly generating a random id, when being called with no ID. In the sample that we provided, you can see a sample implementation of this behavior in the lines 19-22 of this file https://github.com/DeploymentArtist/SWP1/blob/master/MDTMonitoring/MonitoringDemoCSharp/Controllers/MDTMonitorEventController.cs. Another possibility is, that you have added a value for LTIGUID to your customsettings.ini. In this case, all your deployments will use the same ID on the monitoring side.

— Reply to this email directly, view it on GitHub https://github.com/DeploymentArtist/SWP1/issues/8#issuecomment-1656247558, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNZ6J5NFBH3KWC27LQXHFLXSQK3PANCNFSM6AAAAAA23VVYYI . You are receiving this because you authored the thread.Message ID: @.***>

itamartz commented 1 year ago

I just look on one of my bdd log and not found any lt..Guid.

This variable only show if my deployment share have the monitor on ?

In the problematic environment we see that id 5 it's set for all the computer we start using the manual mount of the share drive and if I start 2 vm from cd, each get it on id.

In the mmc we see this one line for id 5 with 4 vm inside(refreshing we see different name) and 2 line one per vm

On Sat, Jul 29, 2023, 22:23 Itamar Tziger @.***> wrote:

Hi, Thank you for your quick response. I use the build in MDT web service, so I will take a Look for the task variable you say.

BR. Itamar

On Fri, Jul 28, 2023, 22:59 Maik Koster @.***> wrote:

Hey Itamar, can you please provide some more details? Are you talking about the MDT Monitoring, or some custom monitoring based on the sample that was provided?

Each deployment should have a unique ID. This deployment specific ID is stored in task sequence variable LTIGUID and is not created on the client computer, rather taken as response from the first call to the monitoring service. All further calls from the same machine during the same deployment to the monitoring service will use the ID that was returned from the first call.

If deployments of different computers show up with the same id, it's very likely that it's not properly generating a random id, when being called with no ID. In the sample that we provided, you can see a sample implementation of this behavior in the lines 19-22 of this file https://github.com/DeploymentArtist/SWP1/blob/master/MDTMonitoring/MonitoringDemoCSharp/Controllers/MDTMonitorEventController.cs. Another possibility is, that you have added a value for LTIGUID to your customsettings.ini. In this case, all your deployments will use the same ID on the monitoring side.

— Reply to this email directly, view it on GitHub https://github.com/DeploymentArtist/SWP1/issues/8#issuecomment-1656247558, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNZ6J5NFBH3KWC27LQXHFLXSQK3PANCNFSM6AAAAAA23VVYYI . You are receiving this because you authored the thread.Message ID: @.***>